The Official Status Thread
-
You need to start slow, allow time to get all warmed up and ready to go before you insert them.
No one posted ?
Very disappointing....
-
TIL you can't just rename a database in MySQL. All you can do is create a new one and copy over the data.
-
How about backing it up, then restoring the backup under a new name?
Not really any faster I guess.
-
Status: Everything is broken in a rather obvious way, such that for the most important type of thing, we can't get to the screens that show it in our app, because somehow a collection gets modified mid .Any()
-
If it were MyISAM, there might be a way but you're probably doing the smart thing with InnoDB.
-
How about backing it up, then restoring the backup under a new name?
Not really any faster I guess.
It's a dev database. I just deleted it and re-run the migrations.
I'd be pretty pissed if I needed to rename a schema in production, though.
-
Status****meme: I
###Fucking
##Hate
#RestAssuredExpected: is <1> Actual: 1
FFFFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!
-
You could use a DBMS that doesn't suck.
Although renaming the database in MS SQL Server doesn't rename the underlying files, so it's a bit confusing. But it works.
-
uhm what?
lines, disk space? you are really willing to trade readability for that?
-
Status: Ok I don't expect quality from Discourse, but the simple act of "scrolling up with the mouse scrollwheel" has been broken now for at least a solid week. Jesus Christ. Let's migrate already.
-
Ok I don't expect quality from Discourse, but the simple act of "scrolling up with the mouse scrollwheel" has been broken now for at least a
solid weekyear.FTFM
-
It used to work in small threads. Now it doesn't work in ANY threads. Discourse goes on some crazy scrolling-spree where it keeps going up for some arbitrary number of posts so you utterly lose your place.
-
I have had that issue in all threads for at least a year now. I guess you were just lucky enough to not regularly run in to it. It did not matter the thread size. Anything more than a few screens and it would regularly shit itself and keep jumping in leaps and bounds towards the top.
-
Oh. I figured that was something with my mouse. And also with my touchscreen, because I get it on mobile, too....
-
The only thing wrong with those is that you use them to navigate Discourse.
-
How about if you load a specific post and press the bottom button in the "pager" it doesn't go to either the bottom post or the last read post, but to the bottom of the current infiniscroll page and loads the next.
Infuriating.
-
^so much that. Apparently last doesn't mean last in Discoworld
-
1TBS is easily readable.
-
And also with my touchscreen, because I get it on mobile, too....
It always happened on Windows Phone, one of the reasons I never even attempt to use this site with mobile anymore.
-
Yeah, Android is the same now. I can only assume the all holy and mighty iOS isn't because if it was we'd probably actually see some movement on the issue....
-
-
butand then you'll have the "else with ears" which isuglyelegant and efficient} else {
FTFY
-
-
Android is the same now.
I'm lucky, I don't allow the "Smooth coasting" scroll method when scrolling in discourse. This is done by scrolling, then halting my pointing implement for > 75 Ms, and then releasing the scroll (which means the scroll velocity should be reduced to zero by that time).
Of course, it doesn't precisely fix jellypotatoes when loading all posts, but with practice (and infinipatience), you too can enjoy the saucemess that is infiniscroll!
-
-
It has become very efficient at giving us joy.
-
efficient
i think you got it wrong, the thing your code does should be efficient. not the text representation of it
-
i think you got it wrong, the thing your code does should be efficient. not the text representation of it
The text representation should not be overly large, either.
} else {
is so incredibly inefficient, both visually and, compared to
}else{
uses 2 extra characters, which can easily result in significant amounts of wasted space once you have a substantial number of if-else's.
But it's still better than replacing a \t with four spaces.
-
Status PHB pressuring me to finish the project at Friday, I have no idea where the data for some stuff should come from, coworkers discussing the interpretation of the vague subjective specification we received, and just received the 5th version of it, that's still far from being final.
But we're just ignoring PHB and his ridiculous deadline anyway.
-
Status: Something's wrong. What the fuck is going on?
-
Status: Tomorrow's a release date, of which I have two things to be pushed to production (which are disabled and not scheduled to run, and can't run outside the schedule, long story).
(No, I'm not the red dude, my profile icon doesn't show up in
LyncSkype for Business unless there's multiple people on the convo)
-
Status: I'm finally out of amber!
Now I just have to...
Okay, I quit.
-
MMO Status: We managed to kill the last two dragons and Keaghan, but my friends didn't do all the prereqs, so I'm in Season 2 and they aren't yet. On the bright side, I'm still 70 and all the 70 equipment is worse than the stuff you make out of the dragons, so we'll be fighting them all several times.
Also, I think leaving my PC ingame all night and all day this time will get me to the number of login tickets required to get that event exclusive strawberry underwear finally.
...What?
-
-
-
-
So that is where you draw the line?
-
Vindictus is a very odd game. Your armor breaks randomly as you take large hits, so they make money selling better underwear among other things. Interestingly, mechanically the game is incredibly good. Very deep but punishing combat.
-
-
-
Gave the guy Mott's excellent CSV task.
"You must go to the nearest CSV and, without spending any money, obtain enough cough syrup and acetaminophen to make $500 worth of street-level drugs. We'll be watching. You have one hour."
-
I think you mean CVS.
-
Yeah, Android is the same now. I can only assume the all holy and mighty iOS isn't because if it was we'd probably actually see some movement on the issue....
Sure. Even on iOS, you'd see it move down. Then up. Then freeze. Then down down down then freeze. Then downupdownup and finally come to rest on a post 15 beyond where you were aiming for.
-
You suck?
-
I'm curious how it's both.
It's a really really really well-done episode of a stupid show.
-
Status: Billing dept forwards me an email from a customer who wants to "not pay the networking portion of the maintenance bill because we could never get it to work." I'm like ..oh yeah, I remember these guys. A year ago when we were doing implementation they said repeatedly they couldn't get our software working in client/server mode. I repeatedly offered to GoToMeeting and get it figured out and was told "no thanks, it just won't work" by their IT guy. So I call the billing person and tell her the slightly-longer version of this and say "and by the way he's lying." I forget what specifically prompted me to say that. She just shrugged and said she'd credit the networking portion of their bill and if they called in for help on that, I could tell them I wasn't allowed to help them. I'm fine with that.
I get off the phone and see another forward from her where she offers to have our technical people, i.e., me, work with them, and he replied "no thanks, we spent a lot of time with them and they told us the software couldn't do that."
Lying sack of shit. I want to call him and tell him that.
Anyone want to speculate on why they'd do that other than "I don't like the software?" This is a plain old c/s application like a million others, that works on hundreds of other clients--I've done dozens and dozens of these installs myself for our customer base, and I literally use the software in c/s mode every single weekday.
-
Status: Now Data's on Frasier!!! And he has the Data makeup, too, except his eyes aren't yellow.
-
It's actually working, and they don't want to spend the money.
So, it's never worked since they day they bought it, and you need to get out there to fix it right now without charging them, and then they might think about paying the original invoice (spoiler: it'll be broken again when the bill comes due!)
-
It's actually working, and they don't want to spend the money.
The part of the invoice they're bitching about is one of the smallest ones! (I'm assuming, based on my knowledge of the product components, and rough pricing.) Plus, they way they must be running if they're telling the truth that it doesn't work means either one person's running the software in single-user mode on her own PC, or people are logging in to the server to use it, and IT doesn't usually like that.
The way billing works, we charge by module for functionality, and we also charge based on Progress database licensing components, which is similar: the database server, client access licenses, development environment, and so on. CALs are, like I said, probably the cheapest piece.
-
hey @FrostCat. how often is published RWBY?
that was a pretty big cliffhanger