The Official Status Thread
-
A guy tries to do his job and what does he get?
MOD ABUSE.
Sad times are these when a passing troll can abuse at will the hard working moderators.
-
What are you talking about? I'm not complaining about you moving it, I just couldn't figure out what the fuck you moved, to where, or why. That's Discourse's fault, as I originally said.
Get over yourself.
-
What are you talking about?
Just making a joke. I was amused.
Why did the @blakeyrat go to the other topic?
Because discourse gave him the wrong link.
-
Crazy moon language.
-
@mott555 said:
sync
That's your problem right there. Syncs always fail in millions of possible ways.
Just drag and drop stuff to a folder on your music device if you can, and change your music device if you can't.
I had a broken iPod once - it worked almost right, but kept randomly losing connection on sync. And apparently on iPods, a failed sync means not only a rollback of the whole import in the DB, but also classifying already copied files as garbage instead of deleting them.
That's what I originally did and it didn't work. The files were on my phone but the music player couldn't find them. It seems I have to use Windows Media Player's sync to work.
In fact I think that's what originally caused all the duplication. I copied everything over, didn't work, then did a sync but all the files were already there, and all hell broke loose.
-
Status:
this is going to bite me somedayCOALESCE(sum( (basic) * !basic_paid ), 0) as basic
-
C:\Windows\Temp
TR is even having that directory. A matching solution would be to make a small ramdisk, pointing TEMP to that drive, and a scheduled task to wipe the contents of the drive periodically.
-
I've been sent a box of lollipops by a (potential) supplier.
I wonder if that would've surprised @Onyx.
-
-
Crazy moon language.
Given the number of times you've said that, apparently everyone but you speaks it. You oughtta consider learning it yourself, lest you sound like the stereotypical Ugly American.
-
Status: Just reset a cow-orker's password. A minute later she's calling me up asking why Outlook is bitching. Well, just like every other time you've changed your password for the last 6.5 years, Outlook takes a little while to sync passwords, and until it does, you lose access to your email.
-
Status: Been given a 256GB SSD which I'm not expected to pay the £50 for until after payday.
-
@Boner said:
I've been sent a box of lollipops by a (potential) supplier.
I wonder if that would've surprised @Onyx.
Why am I mentioned? There's a joke in there somewhere, isn't there?
Notice: My brain is utterly broken. And I still have shit to do. Nothing that isn't immediately obvious will be understood tonight.
-
My brain is utterly broken. And I still have shit to do. Nothing that isn't immediately obvious will be understood
tonightfour days from now.FTFY
-
Why am I mentioned? There's a joke in there somewhere, isn't there?
Because of your post right before his.
-
Oh...
Yeah, hours of frustration are a to memory.
-
Status: TIL that Python packaging is finicky shit that is absolutely bloody awful when it blows up in your face, particularly because of the inflexibility of the version coupling that its peculiar mode of pre-compilation induces. Makes me appreciate just how much better some of the other languages out there (yes, including both C# and Java) manage this stuff. Yes, I fixed my problems, but the amount of attention required to do so made it very hard to pick up the thread of the training again.
Why do I keep ending up taking training where I feel like I know more about what I'm being trained on than everyone else in the room? When I go somewhere to learn, I want to actually learn stuff, damnit! (Other people, including the trainer, were having the version problem I encountered; I was the only person who managed to sort it out.)
-
Status: Waiting to go into a conference call about an Access VBA thiing I had to work on this morning because of what I can only see as a scope change the client hadn't let us know about until after I gave them what I did.
-
TIL that Python packaging is finicky shit that is absolutely bloody awful when it blows up in your face,
Yeah, the whole setuptools ecosystem suffers badly from initially being a relatively early player in the space, leading to early-player mistakes that are "baked in" and hard to extricate yourself from.
-
I exported 20 posts to an existing topic: Colonial Slavery: Sins of Our Past
-
Why the hell has Discourse decided to notify me of a like in a post from January that already had 21 likes?
-
If a post gets Jeffed, you get a fresh notification when it's next Liked.
-
Yeah, the whole setuptools ecosystem suffers badly from initially being a relatively early player in the space, leading to early-player mistakes that are "baked in" and hard to extricate yourself from.
It was not just that. I've probably got at least 5 versions of python on this system (it's hard to be sure, but it might be as high as 19 or as low as 4), and which one gets used and what they work with is rather nasty. It's just very easy to end up with a set of packages that insist on not working with each other.
I don't want armed hostilities between the pieces of software I'm using!
-
Might be simpler to use VMs.
-
And install even more copies of Python? What could possibly go wrong with that?
-
Virtualenv seems to work well enough for me; then again, I don't deal with native C modules nearly as much as you do...
-
Yowza...just noticed a beard whisker that was split 4 ways.
INB4
-
I don't deal with native C modules nearly as much as you do...
I was just trying to get numpy working with a plotting library (whose name I've already forgotten ) and sympy. Some of those are pretty well-known…
-
Status: Everytime I go to meta.d I stumble across some new post by Jeff that confuses me...
https://meta.discourse.org/t/posting-photos-from-smartphone-into-discourse-mobile/29328/3?u=kuroSo... has any of you guys ever heard of something like serverside resizing? I feel like that would be quite the cool idea... like somebody sends you a big picture and you just resize is on the server.... ONCE....
Sadly the only possible way for this to work is to send it back full size to everyone watching the picture and actually do clientside resizing...Filed Under: Sometimes I think Jeff is a troll....
-
-
You idiot!!!!
ImageMagick is only for making grey images darker...
-
endarken.d - powered by discourse?
-
endarken.d - powered by discourse feat. ImageMagicktm
FTFY
Filed Under: also, since it's quoted, it now has a darker background... so you could also say it I DTFY
-
Sadly the only possible way for this to work is to send it back full size to everyone watching the picture and actually do clientside resizing...
Why? All templates are rendered clientside in Discourse. So, when you parse the template, set the
src
attribute of the image to a different one depending on the screen size. The image won't load until you inject the template into DOM anyway.
-
Status: Git is a piece of shit.
Ok so we have a dumb repo where the "autocrlf" has to be set to "false" or shit will break. Every goddamned time I upgrade my buggy shitty assy piece of crap motherfucking assfuck Git client, this gets reset to "true". Git keeps this fucking setting in like 3 different places, and of course the one that randomly becomes wrong is the one it uses.
So a co-worker pointed out we could make a "gitattributes" file that travels with the repo and basically just sets the setting automatically for everybody when they check it out. Wow. That sounds almost not-shit. So I look into it, and come across this "helpful" page:
This page also mentions autocrlf setting, and mentions gitattributes and all is good except... uh... WTF!? Their example gitattributes file doesn't contain the keyword "autocrlf" anywhere in it. In fact, it doesn't contain any settings that seem to match what "autocrlf" does-- and yet the article says I can use gitattributes to overri-daOIRD hiwae risadji HIURweaiuG head hurts
So from their demo file, I know I can set files to one of the following:
- text=auto
- text
- text eol-crlf
- binary
Great. WHICH FUCKING ONE OF THOSE IS EQUIVALENT TO "AUTOCRLF = FALSE" YOU STUPID WANKER FUCK!!!
-
Great. WHICH FUCKING ONE OF THOSE IS EQUIVALENT TO "AUTOCRLF = FALSE" YOU STUPID WANKER FUCK!!!
text
This attribute enables and controls end-of-line normalization. When a text file is normalized, its line endings are converted to LF in the repository. To control what line ending style is used in the working directory, use the eol attribute for a single file and the core.eol configuration variable for all text files.Set
Setting the text attribute on a path enables end-of-line normalization and marks the path as a text file. End-of-line conversion takes place without guessing the content type.Unset
Unsetting the text attribute on a path tells Git not to attempt any end-of-line conversion upon checkin or checkout.Set to string value "auto"
When text is set to "auto", the path is marked for automatic end-of-line normalization. If Git decides that the content is text, its line endings are normalized to LF on checkin.Unspecified
If the text attribute is unspecified, Git uses the core.autocrlf configuration variable to determine if the file should be converted.Any other value causes Git to act as if text has been left unspecified.
So, unset? Which seems to be done with a minus sign (
-text
)?
-
according to about 5 minutes of googling looks like
* binary
is the directive you want in your gitattributes file to have git stop messing about with line endings on the files full stop.
* text eol=lf
will force git to use LF line endings if that's what you want
or if you want to force CRLF line endings:
* text eol=crlf
you could replace that * with a extension glob if it's only some extesnions that cause you trouble.
source: https://help.github.com/articles/dealing-with-line-endings/
hope that helps! have a fantastic day!
-
Ok but the point is, if I'm overriding the setting "autocrlf" why isn't the override also called "autocrlf"?
It sounds like none of the 4 options do exactly the same thing, although binary is closest. But then will using "binary" prevent Git from doing diffs, because now it's like, "derp! I can't diff binary files!"
And of course the real complaint here is:
Couldn't there just, for once, be ONE SMALL THING about Git that's actually well-designed?! JUST ONE THING!?
-
I get your point. And if
-text
does what it seems to be doing from those docs, that should handle the diff issue.I'm not disagreeing with you here, it's crappy. But I was interested in how they mangled it so I took some time to google it. And while I was at it I pasted what is hopefully a solution.
-
But then will using "binary" prevent Git from doing diffs
according to the documentation i linked this is true. the binary directive is an alias for
-text -diff
so if these files produce sensible diffs but need line endings preserved you just need to specify-text
-
Status: Browsing meta.d and I noticed that the URL is updating as I scroll through a topic. Shit. Go to preferences to make sure everything is set correctly:
Belgium, looks like some settings are missing. Same section here on WTDWTF (missing settings highlighted):
Is this a sign of things to come?
-
hmmmmm.... @riking, is this true?
if so i need to buy some hipwaders for when that hits here and certain denizens find out their edit history is public now...
-
No.
- "Let other users view my post revisions" is dependent on a site setting (edit history is visible by default, with only expunge available)
- Don't update URL is a plugin
-
ah.
/me cancels the order for hipwaders.
muchas gracias
-
Loving the desktop notifications, by the way
-
/me cancels the order for hipwaders.
I wouldn't be so hasty to cancel; you never know when they might come in handy ;)
-
that reminds me i need to finish that set of changes to socksite and deploy the desktop notifications to servercooties.com
i also need to grab the raw data and make some fun graphs with them. make some uptime statistics and stuff.
-
No.
- "Let other users view my post revisions" is dependent on a site setting (edit history is visible by default, with only expunge available)
- Don't update URL is a plugin
Oh, good. Though I could have sworn that Don't update URL was at least installed at meta.d …
-
Don't update URL is a plugin
That has a bug that has existed for a long time, that it doesn't correctly reflect what you have it set to.
-
That has a bug that has existed for a long time, that it doesn't correctly reflect what you have it set to.
And since Sam is the plugin author, I reported the bug: