|
I haven't had any issues with EBS volumes, what are you alluding to?
|
# ? Aug 23, 2012 21:38 |
|
|
# ? May 28, 2024 14:39 |
|
Hard NOP Life posted:I haven't had any issues with EBS volumes, what are you alluding to? This is a joke, right? https://status.heroku.com/incidents/151 and http://storagemojo.com/2011/04/29/amazons-ebs-outage/ http://blog.reddit.com/2011/03/why-reddit-was-down-for-6-of-last-24.html http://gigaom.com/cloud/did-amazons-web-services-go-down/ http://venturebeat.com/2012/06/29/amazon-outage-netflix-instagram-pinterest/
|
# ? Aug 24, 2012 05:26 |
|
I've had a bunch of EBS volumes fail on me personally. I still love EC2, you just have to remember you're still on a machine somewhere and it can still fail, so have snapshots and hot/warm spares ready for important services. Or even better, geodiversify your poo poo.
|
# ? Aug 24, 2012 14:58 |
|
dexter posted:This is a joke, right? This was fascinating, thank you for that. I had heard about the EC2 outage, but I didn't know it had been caused by EBS.
|
# ? Aug 24, 2012 22:38 |
|
Hard NOP Life posted:This was fascinating, thank you for that. I had heard about the EC2 outage, but I didn't know it had been caused by EBS. Yeah, EBS is notoriously unreliable and Amazon keeps tight wraps on the underlying technology (just like everything else being EC2.) As long as you design your systems around the fact that stuff will fail and replicate your data/serve traffic from multiple regions you should be safe on AWS.
|
# ? Aug 25, 2012 01:05 |
|
dexter posted:Yeah, EBS is notoriously unreliable and Amazon keeps tight wraps on the underlying technology (just like everything else being EC2.) As long as you design your systems around the fact that stuff will fail and replicate your data/serve traffic from multiple regions you should be safe on AWS. That is: so long as you buy lots and lots of server time from Amazon you'll be fine.
|
# ? Aug 26, 2012 11:52 |
|
Zombywuf posted:That is: so long as you buy lots and lots of server time from Amazon you'll be fine. It just means that you need to plan to have n+1 geographic redundancy or a hot DR site just as if you were renting/leasing/buying physical servers.
|
# ? Aug 29, 2012 04:32 |
|
dexter posted:It just means that you need to plan to have n+1 geographic redundancy or a hot DR site just as if you were renting/leasing/buying physical servers. When you own your own SAN a backup plan is much much easier. It's also easier to recover from failure if you machines don't wipe themselves on reboot.
|
# ? Aug 29, 2012 09:58 |
|
Sigh
|
# ? Aug 29, 2012 15:16 |
|
epalm posted:Sigh Even worse than the 16 character limit, think about what "enter the first 16" implies
|
# ? Aug 29, 2012 15:17 |
|
Found this in production today.code:
|
# ? Aug 29, 2012 15:37 |
|
Adobe just released a new ActionScript compiler that has some support for inlining. Among other things, it cannot inline methods that have a try statement. This is their example code for that situation:ActionScript code:
|
# ? Aug 29, 2012 16:18 |
|
Aleksei Vasiliev posted:Adobe just released a new ActionScript compiler that has some support for inlining. Among other things, it cannot inline methods that have a try statement. This is their example code for that situation: Kind of a lovely example, but as an example of what not to do, it works on multiple levels! Does that even compile?
|
# ? Aug 29, 2012 16:22 |
|
Gigantic Slut Man posted:Even worse than the 16 character limit, think about what "enter the first 16" implies It's probably not as bad as my gut reaction, but my gut says it's pretty bad. I'd hope that it takes the first 16 characters and hashes those. They're just being honest about the back end only accepting 16 character passwords now. Granted if they ARE hashing passwords, why would there need to be a limit at all?
|
# ? Aug 29, 2012 16:29 |
|
Gigantic Slut Man posted:Even worse than the 16 character limit, think about what "enter the first 16" implies Well, it depends: did they just change this rule? It's possible that they've just been hashing the first 16 characters all along. Still not as bad as my bank. Those stupid motherfuckers require a six-character password of letters and numbers, so it can be integrated with their phone banking system (using the same password). The person responsible for that choice needs a sound beating, I should think.
|
# ? Aug 29, 2012 16:29 |
|
Gigantic Slut Man posted:Even worse than the 16 character limit, think about what "enter the first 16" implies The notification hopefully means that they're working on removing the limit without breaking old accounts.
|
# ? Aug 29, 2012 17:05 |
|
the littlest prince posted:Does that even compile? Yeah, it always returns zero though.
|
# ? Aug 29, 2012 18:01 |
|
Aleksei Vasiliev posted:Adobe just released a new ActionScript compiler that has some support for inlining. Among other things, it cannot inline methods that have a try statement. This is their example code for that situation: To be fair, those really awkward examples are what a compiler writer deals with all day.
|
# ? Aug 29, 2012 18:14 |
|
Yes, I realize they were silently truncating before. Still a horror. Edit: Also, my alma mater moved their alumni email to MS hosted Outlook and I had to make a new password there. Had to be exactly 16 characters. I'm not sure if that's a school limitation or an MS one but it seems really dumb. Bunny Cuddlin fucked around with this message at 01:30 on Aug 30, 2012 |
# ? Aug 30, 2012 01:18 |
|
For most bullshit web apps it's probably more secure to have 4 character passwords and then freeze the account after 3 attempts -- that way if you lose the database you don't reveal your users' email passwords.
|
# ? Aug 30, 2012 01:35 |
|
shrughes posted:For most bullshit web apps it's probably more secure to have 4 character passwords and then freeze the account after 3 attempts -- that way if you lose the database you don't reveal your users' email passwords. You could then save some database space by making the password a FK to a password table. (1, 1234), (2,abcd)... I think that should do it.
|
# ? Aug 30, 2012 13:18 |
I was once asked to look at why user registration for a custom web community was acting strange. Well, it was an ASP Classic thing, using an Access database, but most importantly: User names were not unique. You could have two users with the same name as long as they had different passwords. Actually, trying to recall this, I don't even think that was checked during user creation... Of course, as a result, some people had multiple almost-identical accounts. (Naturally the passwords were stored in plain text.)
|
|
# ? Aug 30, 2012 13:41 |
|
nielsm posted:I was once asked to look at why user registration for a custom web community was acting strange. Well, it was an ASP Classic thing, using an Access database, but most importantly: User names were not unique. You could have two users with the same name as long as they had different passwords. Actually, trying to recall this, I don't even think that was checked during user creation... Of course, as a result, some people had multiple almost-identical accounts. Hot new ERP service NetSuite also does this. Isnt it magical?
|
# ? Aug 30, 2012 20:31 |
|
nielsm posted:I was once asked to look at why user registration for a custom web community was acting strange. Well, it was an ASP Classic thing, using an Access database, but most importantly: User names were not unique. You could have two users with the same name as long as they had different passwords. Actually, trying to recall this, I don't even think that was checked during user creation... Of course, as a result, some people had multiple almost-identical accounts. (Naturally the passwords were stored in plain text.) Weird; I had to update a customer login system based on .Net classic that had the same problem. I found it right away though;
|
# ? Aug 31, 2012 02:49 |
|
Aleksei Vasiliev posted:what an excellent example of try statement use
|
# ? Aug 31, 2012 05:26 |
|
It bears repeating, forever.PHP code:
|
# ? Aug 31, 2012 22:54 |
|
Golbez posted:It bears repeating, forever. When you compare an int and a string to see if they are equal (==) PHP attempts to convert the string to a number. If you did var_dump(0 === "0.00") you would get false. === is identical (ie. equality with type checking) I can see why this sucks, but these idiosyncrasies can be avoided with the use of === instead of ==.
|
# ? Sep 1, 2012 02:09 |
|
Java code:
|
# ? Sep 1, 2012 02:15 |
|
I hope there's a better comment than that explaining why. That's the sort of stuff I'd find in my last job's code base that would leave me staring at the screen for ages.
|
# ? Sep 1, 2012 05:39 |
|
At least the sentence is complete. I've torn my hair out so many times over comments in legacy code with an unspecified "it" or "this".
|
# ? Sep 1, 2012 06:57 |
|
Gazpacho posted:At least the sentence is complete. I've torn my hair out so many times over comments in legacy code with an unspecified "it" or "this". Every time I write comments, I always have to check my pronouns to make sure it's blatantly obvious what any pronoun means. Pronouns are worthless in code though, fwiw.
|
# ? Sep 1, 2012 10:09 |
|
Chopper posted:The boolean of a string is true in PHP. The boolean of any non-zero integer is true. The boolean of 0 is false. I ran into this when dealing with output from a mysql query, where everything is returned as a string. And since this was a decimal field in the table, zero was "0.00", which isn't boolean false but is equal to zero, and the array_filter() was keeping it in. I understand how it works, that doesn't mean i have to like that php is intransitive. The only times in my code where I use == are when dealing with something that may have come from a query or a web form, which (at least with the mysql library) are always strings.
|
# ? Sep 1, 2012 15:27 |
|
Chopper posted:I can see why this sucks, but these idiosyncrasies can be avoided with the use of === instead of ==. In a car with a stuck accelerator you can effectively control the speed with the clutch but that doesn't mean you shouldn't get out of the car and stop driving it at the first opportunity.
|
# ? Sep 1, 2012 20:46 |
|
Gigantic Slut Man posted:In a car with a stuck accelerator you can effectively control the speed with the clutch but that doesn't mean you shouldn't get out of the car and stop driving it at the first opportunity. The sensible thing to do would be to drive it straight through the dealers front door and scream at them to fix it.
|
# ? Sep 1, 2012 21:08 |
|
I haven't used mysqli in years and have never used PDO, but I'm hoping they return things from the database in a native type rather than casting everything to string? If that's the case then it's my own fault for using mysql (not by design, inherited a system and upgrading to mysqli has not been in the priority list). If it's not the case then my complaint stands, I *hate* having to use == when dealing with queries and form input, it's either that or casting all over the place. ... Which really I should probably be doing in the first place, at least with form input.
|
# ? Sep 1, 2012 21:15 |
|
While I understand that there are many design horrors in PHP, and to a lesser extent Javascript, this hand-wringing over implicit conversion reminds me of the arguments when I was learning BASIC against using = for assignment (as well as comparison), because some poor stupid programmer might flip out over a statement like X = X + 1. Similarly Dijkstra argued that no language should have lazy logical and/or operators because they do not have exact mathematical precedents and therefore programmers can never possibly understand them. Gazpacho fucked around with this message at 03:55 on Sep 2, 2012 |
# ? Sep 2, 2012 03:53 |
|
Gazpacho posted:While I understand that there are many design horrors in PHP, and to a lesser extent Javascript, this hand-wringing over implicit conversion reminds me of the arguments when I was learning BASIC against using = for assignment (as well as comparison), because some poor stupid programmer might flip out over a statement like X = X + 1. Implicit conversion isn't always bad if it follows a consistent set of rules and behaves fairly intuitively. For example, in C, any pointer type can be implicitly converted into a void *, and nobody has a problem with this. For a more related example, Perl does fairly aggressive coercion too, but it includes a separate set of comparison operators for strings than it does for numbers, so you don't need to worry about any weird type coercion rules when you're trying to compare something string-wise vs numerically.
|
# ? Sep 2, 2012 07:19 |
|
Golbez posted:I ran into this when dealing with output from a mysql query, where everything is returned as a string. And since this was a decimal field in the table, zero was "0.00", which isn't boolean false but is equal to zero, and the array_filter() was keeping it in. FWIW you can pass a callback to array_filter which uses strict comparison. Having said that, this kind of poo poo (PHP builtins using == and not === by default) bites me all the god drat time.
|
# ? Sep 2, 2012 08:02 |
|
Gazpacho posted:While I understand that there are many design horrors in PHP, and to a lesser extent Javascript, this hand-wringing over implicit conversion reminds me of the arguments when I was learning BASIC against using = for assignment (as well as comparison), because some poor stupid programmer might flip out over a statement like X = X + 1. I always liked X + 1 -> X as an assignment syntax.
|
# ? Sep 2, 2012 10:19 |
|
|
# ? May 28, 2024 14:39 |
|
qntm posted:I always liked X + 1 -> X as an assignment syntax. You can already do it that way by using the "go-to" operator: code:
geonetix fucked around with this message at 11:26 on Sep 2, 2012 |
# ? Sep 2, 2012 11:02 |