The Official Status Thread
-
@ben_lubar Your own screenshot has a giant green tag that reads "Open", genius.
-
@blakeyrat said in The Official Status Thread:
@ben_lubar Your own screenshot has a giant green tag that reads "Open", genius.
I'm going to frame this reply and put it on my wall.
-
@ben_lubar You're trying to prove to me that the bug is closed by showing me a duplicate bug that's open.
Frame what you want. I guess I'll just reopen those bugs since, apparently, they've instantaneously regressed after you closed them.
EDIT: congratulations, you've successfully trolled me by closing my bugs for no reason and making me put in duplicates. Please go die in a fire now. Thank you.
-
@blakeyrat said in The Official Status Thread:
@ben_lubar said in The Official Status Thread:
I'm moving bugs to the bug trackers where they can actually be fixed, and fixing the ones that I can fix.
You're not moving the bugs, you're closing perfectly valid bugs. Adding a link to another bug in a completely different bug tracker doesn't somehow magically fix the issue.
They aren't fixed.
I'm with Blakeyrat here. Standard practice would be to add a comment "filed an issue in node nodeBB, <link to issue>, awaiting for response." and not closing it.
If you (BenL) wants to filter what issues are waiting for node db, add a tag ( a label in github).
At the very least it should avoid filling duplicate issues.
edit: clarified 'you'
-
@Lorne-Kates said in The Official Status Thread:
You just said touch screen. Wasn't sure what platform. Or well, maybe they'll port it.
Ah yeah, no hard feelings. ;) There seems to be a touch-friendly version of VLC in the Windows store, bit it's rather *ahem* touchy when resuming from standby and the default audio device is temporarily unavailable...
@blakeyrat said in The Official Status Thread:
closing bugs in TheDailyWTF bug tracker that aren't fixed.
Correction: He's moving them into the main tracker, since they're issues with the Core, not necessarily just our own instance if it.
And 'd by an hour of course by the guy himself...
@cabrito said in The Official Status Thread:
Standard practice would be to add a comment "filed an issue in node nodeBB, <link to="" issue=""/>, awaiting for response." and not closing it.
If you want to filter what issues are waiting for node db, add a tag ( a label in github).Is that not what's happening?
I'm confused...
-
@Tsaukpaetra Look up-left, the red closed
-
@cabrito said in The Official Status Thread:
filed an issue in node nodeBB, <link to="" issue=""/>, awaiting for response.
But Ben L doesn't do that. He's utterly ignored my "don't show mobile mode on desktop computers" bug, it hasn't been reported upstream. I don't know what he's supposed to be doing, but so far the strategy seems to be "wait for another person entirely to file the bug elsewhere, then wait about 6 weeks, then close the bug even though it's not fixed."
@Tsaukpaetra said in The Official Status Thread:
Correction: He's moving them into the main tracker,
That one appears to have actually been moved. Mine weren't. They were "someone else entirely filed a duplicate bug in an entirely different bug tracker."
@Tsaukpaetra said in The Official Status Thread:
I'm confused...
I am too. Your screenshot shows he moved it to NodeBB's bugtracker, then immediately closed it?
If he closed it, how are we expecting the NodeBB developers to actually fix it?
-
@blakeyrat said in The Official Status Thread:
I am too. Your screenshot shows he moved it to NodeBB's bugtracker, then immediately closed it?
If he closed it, how are we expecting the NodeBB developers to actually fix it?Wait, does closed on our end equate to closed on their end?
To me, this is essentially the equivalent of a 301 Redirect: Go see the progress of this issue on the actual tracker for the product.
I'm sorry that your expectations of cross-repo tickets doesn't seem to fit the integration standards of Blakeyism, but I'm not sure what's wrong here.
-
@Tsaukpaetra said in The Official Status Thread:
Wait, does closed on our end equate to closed on their end?
Unless GitHub uses a definition of the word "moved" that nobody else uses? I guess with such an open source-y website, it's conceivable they use "moved" when they mean "copied"?
@Tsaukpaetra said in The Official Status Thread:
I'm sorry that your expectations of cross-repo tickets doesn't seem to fit the integration standards of Blakeyism, but I'm not sure what's wrong here.
It's really simple. The bugs were marked closed. They are not fixed.
-
@Yamikuronue said in The Official Status Thread:
I'm a mother!
Am I too late to wish you a happy mothers day?
-
@blakeyrat said in The Official Status Thread:
Unless GitHub uses a definition of the word "moved" that nobody else uses? I guess with such an open source-y website, it's conceivable they use "moved" when they mean "copied"?
I'll use an analogy to explain my reasoning.
Let's suppose each of these bug trackers is represented by a physical hard drive each (for kicks, we'll call them
A:
andB:
).
Let's further suppose that it has been decided that a particular file onA:
needs to go toB:
. So we issue amove A:\DontSh~1.bug B:\DontSh~1.bug
command.
What do you expect to happen?What actually happens (because of course the analogy isn't perfect and breaks down):
- The system locates that file and (realizing that the file source and destination is on separate disks) initiates a copy. This of course creates a shiny new file entry (with its own ID and everything) on the target disk and finishes the copy. Most attributes survive the trip, but not all.
- Once the copy has finished, the system of course deletes the entry for the original file (read: marks closed) so that future lists for the file don't find it (since, of course it's moved to the other drive, why would you expect it to be on the first after that?).
- All is well within the world, because your file is moved as expected.
What I think you're expecting should happen (because obviously bugtrackers aren't filesystems):
- The system recognizes that the two disks are permanently affixed in the same machine (read: bugtracker website). This is important!
- The system initiates a copy of the file like normal, but since the disks are in the same system and everything, all of the data and attributes move over nicely and (since this is one whole cohesive system) the though the file still gets a new ID (because they are after all on different disks).
- Oh, there was a nice flag set on the command,
-linkback
, so the system replaces the source file entry with a symbolic link so that anyone looking forA:\DontSh~1.bug
is actually readingB:\DontSh~1.bug
transparently (despite it looking like it's still on driveA:
) - Of course, people working on drive
B:
will do the things needed for the file, but the people keeping watch on driveA:
mostly only care to see what ends up happening to the file, so it's "there" but "not actually there".
So in other words, it sounds like you want the "our version" of the bug to be linked with the "this is what will actually be worked on by the NodeBB team" version of the bug, so things like ticket status can be viewed on our side instead of you needing to click through to their side?
I can't imagine someone willing to spend their time manually watching all of these tickets, because I'm sure that the trackers don't support such a linkage like that.
-
@blakeyrat said in The Official Status Thread:
It's really simple. The bugs were marked closed. They are not fixed.
Why should TDWTF keep all the bugs open that they're not responsible for fixing? They've noted the issue and sent it off to the team who can fix it... on a different bug tracker. If you care that much about the issues follow the links to the opened tickets.
-
-
@Boner said in The Official Status Thread:
@Lorne-Kates said in The Official Status Thread:
statusbolded text****
Emptied the camera's sd card. Delete blurry / dupes. organized the rest.
The "Molly" folder is 3.6 gigs. She's 10 days old.
I'm gonna need a bigger hard drive.
Remember - everything you do for child 1 you have to do for all subsequent children.
Easy: By Child#2, he will have a new camera, so two or three pictures should be sufficient to fill 3.6GB.
-
STATUS The week hasn't started well. I had yoghurt for breakfast and some of it got stuck in my mustache. It was like that for two hours before I saw myself in the mirror.
-
STATUS:
Go home webstorm, yo drunk.
-
Status:
Konversation, you're not helping!
-
@Mikael_Svahnberg said in The Official Status Thread:
so two or three pictures should be sufficient to fill 3.6GB.
And play count the hairs
-
-
Thanks, I guess, Wikipedia...
-
@Tsaukpaetra That's a really fucking long way of saying, "the idiots who designed GitHub used the word 'move' when they meant 'copy'."
-
Status: This must be a troll, surely:
-
@Lingerance said in The Official Status Thread:
Why should TDWTF keep all the bugs open that they're not responsible for fixing?
Because we're fixing bugs independently of the NodeBB team. Boomzilla was working on disabling the mobile mode thing just a couple days ago, for example.
@Lingerance said in The Official Status Thread:
They've noted the issue and sent it off to the team who can fix it... on a different bug tracker.
But that doesn't make it fixed. Therefore, it should remain open.
This is a very simple concept you people are making extremely complicated.
-
Status: Just found this in a class definition:
QString m_channelerIDName;
Channeler? What? What the hell was I smoking at the time? And why didn't I buy more after I ran out?
-
@dkf said in The Official Status Thread:
@mott555 said in The Official Status Thread:
Boost's UDP library does not work unless the computer has a default gateway configured.
Virtually all networking doesn't work unless you have a default gateway. It's just the identity of the service that things hop to first when the other endpoint isn't on the “same network” (in some relevant sense) and is usually a router or firewall machine. It doesn't change what user-level code does at all. If the lack of a default gateway is causing problems, you're probably dealing with a misconfigured network that is describing things that are supposed to be local as non-local (triggering sending via a gateway instead of direct).
The only exception to this is if you're using multicasting. Which is much deeper voodoo.
Yes, there's multicasting going on. But I don't think the UDP sends that were bombing out were multicasts. Not sure, it wasn't my application, it just kind of fell on me to make it work on an isolated, unconnected network which is what the customer will be doing.
It was strange to me because the final network has no gateway. It is not connected to any other network. No routers, no Internet, everything lives on one little isolated subnet. Having no gateway configured in the domain server's DHCP options seemed like the right thing to do and having DHCP hand out a non-existent gateway seems like Doing It Wrong™.
-
Status: I just received an email telling me the Overwatch public beta is open.
Today.
"Open until May 9".
-
Status: Root canal success! With the help of two valium. Life is pretty damn good right now and I'm not going into work. Screw them.
-
@Yamikuronue watch out for the comedown. Post Valium blues can be brutal
-
@Jaloopa Good thing I'm taking the day off :) I've informed my husband.
-
@blakeyrat said in The Official Status Thread:
So... that's a lie.
Go to hell. Or stop calling me a liar. Ben said they were moved.
-
-
@Yamikuronue said in The Official Status Thread:
I'm not going into work. Screw them.
I'm just posting to approve of this message.
-
-
@blakeyrat said in The Official Status Thread:
Unless GitHub uses a definition of the word "moved" that nobody else uses?
You're certainly one to do that all over the place. One would think you'd be used to it.
-
@blakeyrat said in The Official Status Thread:
That'll teach you to trust.
Who said I trusted. I simply took him at his word, because I don't care enough to check.
-
Status: I really don't want to go to work, but I have absolutely no reason not to.
-
@blakeyrat Pop some valium? :D
-
@Yamikuronue said in The Official Status Thread:
Pop some valium?
I don't have any.
Seriously, the best reason I can think of to go to work is "well the new week bonuses of Gems of War starts, and I could level-up to rank 1 on the bus." That's all I got.
-
@Yamikuronue said in The Official Status Thread:
valium
A mother's best friend.
(Okay, I'll stop now)
-
@Luhmann said in The Official Status Thread:
@Mikael_Svahnberg said in The Official Status Thread:
so two or three pictures should be sufficient to fill 3.6GB.
And play count the hairs
I'm not buying a new camera until I can play "count the DNA strands in 3D"
-
I got to see what a nerve looks like. Have you ever seen that? It's awesome. The human body is amazing.
I probably shouldn't work on my next feature article right now, or tag Mafia... Sorry @Mafia-Players
-
@Lorne-Kates said in The Official Status Thread:
I'm not buying a new camera until I can play "count the DNA strands in 3D"
hmm.... a full 3d VR camera? with microscopic resolution?
DO WANT
-
@accalia If we're talking DNA strands, that's nanoscopic ;)
-
@RaceProUK even better!
-
@accalia Gah. My retinas.
-
@blakeyrat said in The Official Status Thread:
@accalia Gah. My retinas.
they burn with all the fires of a thousand hells?
this this poor fool who ignored the warnings on his laser pointer.
-
Status: With some new hires, somehow we're short in computer mice in the office. I heard rumors of a secret stash of new mice and went to investigate.
I found these "new" mice still in their original packaging. The box states "Designed specifically for Windows 95" and they come with a 3.5" floppy disk with drivers.
-
@mott555 said in The Official Status Thread:
I found these "new" mice still in their original packaging. The box states "Designed specifically for Windows 95" and they come with a 3.5" floppy disk with drivers.
Send them to me for my "wall of warning to other mice"
-
Status: Happy day-after-mothers-day, @Yamikuronue!
-
@ben_lubar Yay! now if I could get an answer about the custom skin question I'd be in heaven