Representative AJAX: Everything wrong with modern webdesign in 562 bytes
-
@blakeyrat closed with the label "sent upstream" seems exceptionally clear to me. Closed because the problem isn't caused by a customization we've added, and there should be no more discussion on Ben L's bug tracker. Sent upstream because the bug is in NodeBB and the discussion should happen on the official NodeBB tracker.
Quit pretending like it's confusing. It's not.
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
closed with the label "sent upstream" seems exceptionally clear to me.
Sending the bug to someone else doesn't magically make it resolved on this website.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Closed because there should be no more discussion on Ben L's bug tracker.
That's not what "close" means in a bug tracker. Never has been.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Sent upstream because the discussion should happen on the official NodeBB tracker.
Except:
- Ben L doesn't always move bugs to the NodeBB tracker for reasons known only to him, so that doesn't happen all the time
- We're fixing bugs independently of the NodeBB tracker, so that doesn't apply to many of our bugs
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Quit pretending like it's confusing. It's not.
Maybe I have a different brain than you do? I wonder if that's possible, that different people have different patterns of thinking...
Hey! Here's an idea. Why doesn't someone EXPLICITLY WRITE DOWN how that bug tracker is to be used, then it won't be confusing to ANYBODY! Wow. What an amazing thought.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Due to them, Ben L was closing bugs that are not fixed.
But they're not bugs for that project. If they're not broken, you can't fix them.
When did you stop beating your wife?
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
But they're not bugs for that project.
Which project?
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
If they're not broken, you can't fix them.
... ok. I guess I can't argue with that?
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Ben L doesn't always move bugs to the NodeBB tracker for reasons known only to him, so that doesn't happen all the time
We're fixing bugs independently of the NodeBB tracker, so that doesn't apply to many of our bugsI'll say it one more time, and then I'm giving up on you.
Ben L's bug tracker is for bugs that we've caused due to our customization and/or our plugins: bugs in code that we've written. The NodeBB bug tracker is for bugs in NodeBB itself: bugs in their code. So when issues get posted one tracker when they should really be in the other one, don't be surprised when they get closed. It's what should happen.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Which project?
The one that the issue tracker is a part of.
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Hey! Here's an idea. Why doesn't someone EXPLICITLY WRITE DOWN how that bug tracker is to be used, then it won't be confusing to ANYBODY! Wow. What an amazing thought.
@ben_lubar: I suggest putting a
README.md
in the project. We should also add our custom CSS / header stuff to track that, too.
-
@AyGeePlus said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Then why are we using it?
Probably because you haven't written a better one.
I hear Jeff has a nifty bug tracker...
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Ben L's bug tracker is for bugs that we've caused due to our customization and/or our plugins: bugs in code that we've written.
Ok.
I'm a normal human being coming to this site. I didn't happen to click into this thread.
How am I made aware of that? How is that communicated to me? Note: "telepathy" is not an acceptable answer.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
The NodeBB bug tracker is for bugs in NodeBB itself: bugs in their code.
But we're fixing some of those without NodeBB involvement. So your little scheme here is already broken-down.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
So when issues get posted one tracker when they should really be in the other one, don't be surprised when they get closed.
They shouldn't get closed until they're resolved.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
It's what should happen.
I vehemently disagree.
But assuming it's what "should" happen: fine! Then just write some explanatory text so I'm aware that "should" happen. So I'm not caught by surprise.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
How am I made aware of that?
Did you notice the label "sent upstream?" What did you think when you saw that?
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
I'm a normal human being coming to this site. I didn't happen to click into this thread.
How am I made aware of that? How is that communicated to me?Well, obviously you follow the blue link at the top that says "File bugs here".
Or click on the other link that says "File NodeBB bugs here..." wait, nope, guess not.
Or you click through the blue link to the whatbugs tracker, and read the self-documenting message there that says "this is only for tdwtf-specific bugs, here's the nodebb tracker"... wait, again, my mistake, that doesn't exit.
....
telepathy.
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
How am I made aware of that?
Did you notice the label "sent upstream?" What did you think when you saw that?
If it says "Sent upstream" and is open, I assume it means it's gone to the base bug tracker, and we're waiting for a fix.
If it says "Sent upstream" and is closed, I assume it means it has been fixed in base, and we've received & integrated that fix into our instance.
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Did you notice the label "sent upstream?"
Well first of all "upstream" is jargon, and particularly awful jargon. (Nothing good comes from upstream. Only piss and turds.)
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
What did you think when you saw that?
- That's a lie, it wasn't "sent" anywhere, it's still here.
- Ok, so it's copied upstream, fine. But it's still a bug here as well.
@Lorne-Kates said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Or you click through the blue link to the whatbugs tracker, and read the self-documenting message there that says "this is only for tdwtf-specific bugs, here's the nodebb tracker"... wait, again, my mistake, that doesn't exit.
Those two things are not mutually-exclusive. A bug with DailyWTF forums is also a bug with NodeBB. (In 99% of cases.) Therefore, it should stay open until it's actually resolved in both places.
@Lorne-Kates said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
If it says "Sent upstream" and is closed, I assume it means it has been fixed in base, and we've received & integrated that fix into our instance.
That is rational thinking to me, but I guess Lorne and I are just mutant freaks.
-
@Lorne-Kates said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
If it says "Sent upstream" and is open, I assume it means it's gone to the base bug tracker, and we're waiting for a fix.
If it says "Sent upstream" and is closed, I assume it means it has been fixed in base, and we've received & integrated that fix into our instance.That's fair. Not how I would have interpreted it, but I like the cut of your tone's jib.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
That's a lie, it wasn't "sent" anywhere, it's still here.
Thanks, Drax.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
I'm a normal human being coming to this site.
That is debatable.
How am I made aware of that? How is that communicated to me? Note: "telepathy" is not an acceptable answer.
You asked, and someone explained it to you. Then you pretended like it was confusing and refused to accept the explanation because you thought you should've been told it upfront.
But we're fixing some of those without NodeBB involvement
Feature requests, if the NodeBB dev team decides they're not bugs and not important enough for them to add, then yeah. We're able to customize it to suit our preferences. But if it looks like a bug and it's in NodeBB itself, then it should go to them first.
They shouldn't get closed until they're resolved.
They're closed because they're a dupe of the open issue on the NodeBB bug tracker. Closing them on Ben L's tracker ensures that the discussion moves to the NodeBB tracker where it should be. If NodeBB decides that it's not a bug and puts it back in our hands, then maybe they can be reopened or restarted on Ben's tracker.
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Thanks, Drax.
I love it when people make fun of me for saying something that literally true.
The message says "sent". It wasn't sent anywhere. It's still exactly where I left it.
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
But if it looks like a bug and it's in NodeBB itself, then it should go to them first.
And if NodeBB decides not to fix it, what's the process for it being moved back from "upstream"?
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
They're closed because they're a dupe of the open issue on the NodeBB bug tracker.
Being a dupe doesn't make it resolved.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Closing them on Ben L's tracker ensures that the discussion moves to the NodeBB tracker where it should be.
Look, he can run it however he wants. But he needs to EXPLAIN HOW IT'S BEING RUN TO PEOPLE USING IT so there's no confusion. That's all I'm saying. Just fucking COMMUNICATE TO ANOTHER HUMAN BEING. I'm not asking for the impossible; just set expectations.
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
If NodeBB decides that it's not a bug and puts it back in our hands, then maybe they can be reopened or restarted on Ben's tracker.
Via... some process which isn't communicated anywhere and possibly doesn't even exist except in this post you just made.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
I love it when people make fun of me for saying something that literally true.
The message says "sent". It wasn't sent anywhere. It's still exactly where I left it.Does it bother you when someone says that something in a TV show or a movie or any other animation "moves?"
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Does it bother you when someone says that something in a TV show or a movie or any other animation "moves?"
No? Should it?
It would if it were, say, this episode:
Because the enterprise was being copied, not moved.
Oh look, a .webp file. Let's see how broken NodeBB is today!
Hey! .webp works again! Woo.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Via... some process which isn't communicated anywhere and possibly doesn't even exist except in this post you just made.
Available to the people that run the project.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
And if NodeBB decides not to fix it, what's the process for it being moved back from "upstream"?
@ben_lubar kind of makes the rules, but would it be safe to say "reopen the issue on our tracker" is the answer to this? I mean... it seems kind of obvious.
Being a dupe doesn't make it resolved.
I don't understand what's getting your panties in such a wad about it. It's a dupe, it gets closed.
-
@RaceProUK said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Available to the people that run the project.
Goddamned.
Yes I know it's possible to re-open a bug. I'm asking what the process is for doing so, and when that decision is made. (When NodeBB ignores it for a week? A month?)
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
I don't understand what's getting your panties in such a wad about it.
Obviously not.
Look, let's go back to the super-simple version, since again people are making this complicated as hell.
What got my panties in such a was was simple this: my bugs were closed when they were not resolved.
Got it? All that information securely in your brain neurons? Good.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
I'm asking what the process is for doing so, and when that decision is made.
Ben presses the button, and when he feels like it
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Oh look, a .webp file. Let's see how broken NodeBB is today!
Hey! .webp works again! Woo.Maybe on your computer, but Chrome is still basically the only browser that supports it. @ben_lubar can we just automatically convert uploaded .webp images to .png?
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
@dkf it seems pretty clear to me. What's wrong with them? You can even search for the label and view all the issues that were sent upstream.
If I see here something that feels as a bug and go to our tracker, I should look at the 'open' issues plus the 'closed' but with that label to see if that had been reported ?
-
better point the link in the forum pages that tells to report in our bug tracker to a post explaining the unexpected workflow
-
too much work, I'd rather look cat videos.
-
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
No? Should it?
As much as you acting confused about the word, "sent," yes. By which I mean, no, not at all.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
What got my panties in such a was was simple this: my bugs were closed when they were not resolved.
Got it? All that information securely in your brain neurons? Good.We get it. I don't know why you don't think we do.
Except that you said that you really are upset because you don't understand the process. Which is weird because people have explained it multiple times now.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
the enterprise was being copied, not moved.
FWIW, alternate timelines do not a copy make.
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
What's wrong with them?
They don't link to the actual upstream bug. Even launchpad does that better.
-
@asdf said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
They don't link to the actual upstream bug
So stick the URL in a comment
-
@asdf said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
What's wrong with them?
They don't link to the actual upstream bug. Even launchpad does that better.
No, but in the couple of representative samples that I looked at, @ben_lubar did that. So I still fail to see the problem.
-
@RaceProUK said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
So stick the URL in a comment
Still not particularly great. In Launchpad, you can link a bug to an upstream bug. The status of the upstream bug is then monitored via the other bug tracker's API and displayed in the bug report. That's how you implement that feature properly, Github basically just ignores the scenario altogether.
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
So I still fail to see the problem.
I have to scroll through the comments, click a link and subscribe to another bug. A sane implementation would allow you to link the two bug reports, so people interested in a bug report don't have to do that manually for every bug which is related to another bug.
-
@asdf said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Github basically just ignores the scenario altogether
Github's issue tracker only really works well for one thing: managing pull requests. For anything else it's severely lacking.
-
@anotherusername said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
I still fail to see the problem.
-
@Yamikuronue
E_HAT_NOTFOUND
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Except that you said that you really are upset because you don't understand the process. Which is weird because people have explained it multiple times now.
Yes and I understand it now, but what you haven't done is put in the information in a place where it would be helpful to anybody else coming into this whole process fresh.
Burying the answer in some bug thread and then this thread isn't a solution to the problem. As long as the problem still exists, I see no reason why I should stop griping about it.
-
@blakeyrat So, seems you're new to the bikeshed? Welcome!
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Yes and I understand it now, but what you haven't done is put in the information in a place where it would be helpful to anybody else coming into this whole process fresh.
I agree. @ben_lubar, I heard somewhere that you're bored. Go write a readme for the what-bugs repo and also put our custom css stuff in there.
-
@boomzilla said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
What did you think when you saw that?
"how can I deliberately misunderstand this in the way that lets me cause the most whaargarbl on the forum?"
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Hey! .webp works again! Woo.
...but apparently not in Edge, so thanks.
-
@FrostCat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
Hey! .webp works again! Woo.
...but apparently not in Edge, so thanks.
Did it ever work in Edge? I thought only Chrome supported it.
-
@FrostCat well I'm adopting the open source mentality where if it works for me, fuck everybody else.
-
@blakeyrat said in Representative AJAX: Everything wrong with modern webdesign in 562 bytes:
well I'm adopting the open source mentality where if it works for me, fuck everybody else.
Does that mean you're going to stop being sour about it, or are you going to more directly emulate Linus Torvalds?