5 ms·

Good grief that issue is a clusterfuck of bozos. Sometimes I wish there was a GitHub with entry exam. "A library you use has a bug, you find a find a 3 month o

by arp242 2y ago

Good grief that issue is a clusterfuck of bozos. Sometimes I wish there was a GitHub with entry exam. "A library you use has a bug, you find a find a 3 month old bug report for your exact issue. Do you 1) add a comment with "me too", 2) express your frustration this issue hasn't been fixed yet, 3) demand the maintainers fix it as soon as possible as it's causing issues for you, or 4) do nothing". Only half joking.

__mharrison__ 2y ago
What is the passing answer?
rowanG077 2y ago
I actually find that hugely helpful that so many people are actually actively expressing they are hitting this. It's not easy to be able to get an idea what issues people are actually hitting with anything you have made. An issue being bumped with essentially "me too" is a highly valuable signal.
- hkt 2y ago
  Reactions, though.
- stingraycharles 2y ago
  It’s not just that, it’s people commenting “this is unacceptable” and “I hate this library” that add very little value. Also, you can upvote issues as well / leave reactions without leaving comments. It ensures a better signal:noise ratio in the actual discussion.
- arp242 2y ago
  Do you really think the maintainers don't understand that "doesn't work with Python 3.13" isn't going to affect tons of people? There's some bozo asking "any news? I cant downgrade because another lib requirement" just two days after the maintainer wrote several paragraphs explaining how difficult it is to make it work with Python 3.13. This adds no value for anyone and is just noise. Anyone interested in actual useful information (workarounds, pointers on how to help) has to wade though a firehose of useless nonsense to get at anything remotely useful. Any seriously discussions of maintainers wanting to discuss things is constantly interrupted by the seagulls from Finding Nemo: "fix? fix? fix? fix? fix?"" Never mind the demanding nature of some people in that thread. Just upvote. That's why this entire feature was added.
  - rowanG077 2y ago
    Considering the python ecosystem is not keen on staying updated anyway, I wouldn't be surprised a maintainer doesn't realize a new python version not working is that important.
  - madars 2y ago
    After seeing "Jigar Kumar" cognitive exploits on xz mailing list a maintainer would be excused (and I'd even say, encouraged) to just ignore pressure tactics altogether. It's an open source project - if it works great, if it breaks, you get to keep both pieces.
  - throwaway519 2y ago
    To the non-technical founder, this is doing something. They will not move to ~~mocking up~~ sketching a wireframe of something.
  - deleted 2y ago
    [deleted]
  - aftbit 2y ago
    [flagged]
- barotalomey 2y ago
  That's why github added emoji reactions many years ago, so you can express "me too" without spamming the notification systems. https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/ https://github.blog/news-insights/product-news/add-reactions...
  - paganel 2y ago
    [flagged]
    - qwertox 2y ago
      Maybe then GitHub should add a text-based expression for people like you. Like Google does in Gmail, where you can turn off the icons for the "archive", "report spam" actions so that the text is shown instead. I'm sure this would add a lot of value to GitHub /s Or you ask your OS vendor (or each website operator) to also ship an optional set of emoticons with less childish images. Start a petition and I'll sign it.
    - padjo 2y ago
      Emoji being associated with infancy is a thing that only exists in your brain and only because young people were early adopters of emoji about 15 years ago. Emoji are just as valid a means of communication as any other.
      - anonym29 2y ago
        It's definitey not only in their brain, it's in my brain, too. On a related note: Emoticon > Emoji. Bring back B~), get rid of those silly newfangled unicode monstrosities.
        genewitch 2y ago
        Element and discord and the Samsung default keyboard try to :coloncode: any emoticons you type. This is on desktop and mobile, since the two apps are electron. \>. <
bagels 2y ago
You're missing 5) Do 1, 2, and 3 6) Submit a a tested pull request with a fix
- efitz 2y ago
  Except when you do 6 the maintainer rejects the request and says that it wasn’t a bug at all, and everyone is stuck with the bug.
- matheusmoreira 2y ago
  Pull requests should not be normalized. The guy in charge of the code base has complete knowledge of it and can always do a better job than randoms making ad hoc changes to quick fix their own problems. Complaining about bugs and missing features is much easier. It's less of a headache and requires less effort and time investment. Truth is developers don't want to end up maintaining other people's code anyways. It's gotten to the point I roll my eyes whenever I see people saying "patches welcome". Chances are they're not as welcome as you would think. "Show us the code", and when you do... Nothing. Submitting a pull request is no guarantee that they'll accept it. Hell it's no guarantee they'll even give you the time of day. You can put in a whole lot of effort and still end up getting refused or even straight up ignored. Even if it's an unambiguous improvement on the status quo. They'll commit code that literally returns "not implemented" directly to master and actually ship it out to users. Your pull request will certainly be held to much higher standards though. And that's if they engage with you in an attempt to get your patches merged. They might just decide to ignore your patch and redo all the work themselves, which is exactly what all the complainers wanted them to do in the first place! If they're really nice they'll even credit you in the commit message! If you're gonna put in effort into someone else's project, just fork it straight up and make it your own project. Don't waste time with upstream. Don't wait for their blessing. Just start making your own version better for you. Don't even submit it back, they can pull it themselves if they want to.
  - bagels 2y ago
    Boo to you. I've up-streamed patches to scipy and a few other python packages. Nobody ever said no to genuine high quality bug reports that were coupled with good fixes. Not saying that will happen every time, but if you're unsure, ask how receptive they are.
Hasnep 2y ago
The Refined GitHub extension [1] automatically hides comments that add nothing to the discussion. [2] [1] https://github.com/refined-github/refined-github https://github.com/refined-github/refined-github [2] https://github-production-user-asset-6210df.s3.amazonaws.com/83146190/258220965-4743b9b9-2aef-41b3-a905-ccf8d7beb74e.png https://github-production-user-asset-6210df.s3.amazonaws.com...
- bityard 2y ago
  Wow, that extension is a gold mine of much needed GitHub functionality
raverbashing 2y ago
Geez honestly This seems to be the issue https://github.com/explosion/spaCy/issues/13658#issuecomment-2797841747 https://github.com/explosion/spaCy/issues/13658#issuecomment... And you depend on opinionated libraries that break with newer versions. Why? Well because f you that's why! Because our library is not just a tool, it's a lifestyle Though it seems that Pydantic 1x does support 3.13 https://docs.pydantic.dev/1.10/changelog/#v11020-2025-01-07 https://docs.pydantic.dev/1.10/changelog/#v11020-2025-01-07

by arp242 2y ago

__mharrison__ 2y ago

What is the passing answer?

rowanG077 2y ago

I actually find that hugely helpful that so many people are actually actively expressing they are hitting this. It's not easy to be able to get an idea what issues people are actually hitting with anything you have made. An issue being bumped with essentially "me too" is a highly valuable signal.

hkt 2y ago
Reactions, though.
stingraycharles 2y ago
It’s not just that, it’s people commenting “this is unacceptable” and “I hate this library” that add very little value. Also, you can upvote issues as well / leave reactions without leaving comments. It ensures a better signal:noise ratio in the actual discussion.
arp242 2y ago
Do you really think the maintainers don't understand that "doesn't work with Python 3.13" isn't going to affect tons of people? There's some bozo asking "any news? I cant downgrade because another lib requirement" just two days after the maintainer wrote several paragraphs explaining how difficult it is to make it work with Python 3.13. This adds no value for anyone and is just noise. Anyone interested in actual useful information (workarounds, pointers on how to help) has to wade though a firehose of useless nonsense to get at anything remotely useful. Any seriously discussions of maintainers wanting to discuss things is constantly interrupted by the seagulls from Finding Nemo: "fix? fix? fix? fix? fix?"" Never mind the demanding nature of some people in that thread. Just upvote. That's why this entire feature was added.
- rowanG077 2y ago
  Considering the python ecosystem is not keen on staying updated anyway, I wouldn't be surprised a maintainer doesn't realize a new python version not working is that important.
- madars 2y ago
  After seeing "Jigar Kumar" cognitive exploits on xz mailing list a maintainer would be excused (and I'd even say, encouraged) to just ignore pressure tactics altogether. It's an open source project - if it works great, if it breaks, you get to keep both pieces.
- throwaway519 2y ago
  To the non-technical founder, this is doing something. They will not move to ~~mocking up~~ sketching a wireframe of something.
- deleted 2y ago
  [deleted]
- aftbit 2y ago
  [flagged]
barotalomey 2y ago
That's why github added emoji reactions many years ago, so you can express "me too" without spamming the notification systems. https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/ https://github.blog/news-insights/product-news/add-reactions...
- paganel 2y ago
  [flagged]
  - qwertox 2y ago
    Maybe then GitHub should add a text-based expression for people like you. Like Google does in Gmail, where you can turn off the icons for the "archive", "report spam" actions so that the text is shown instead. I'm sure this would add a lot of value to GitHub /s Or you ask your OS vendor (or each website operator) to also ship an optional set of emoticons with less childish images. Start a petition and I'll sign it.
  - padjo 2y ago
    Emoji being associated with infancy is a thing that only exists in your brain and only because young people were early adopters of emoji about 15 years ago. Emoji are just as valid a means of communication as any other.
    - anonym29 2y ago
      It's definitey not only in their brain, it's in my brain, too. On a related note: Emoticon > Emoji. Bring back B~), get rid of those silly newfangled unicode monstrosities.
      - genewitch 2y ago
        Element and discord and the Samsung default keyboard try to :coloncode: any emoticons you type. This is on desktop and mobile, since the two apps are electron. \>. <

bagels 2y ago

You're missing 5) Do 1, 2, and 3 6) Submit a a tested pull request with a fix

efitz 2y ago
Except when you do 6 the maintainer rejects the request and says that it wasn’t a bug at all, and everyone is stuck with the bug.
matheusmoreira 2y ago
Pull requests should not be normalized. The guy in charge of the code base has complete knowledge of it and can always do a better job than randoms making ad hoc changes to quick fix their own problems. Complaining about bugs and missing features is much easier. It's less of a headache and requires less effort and time investment. Truth is developers don't want to end up maintaining other people's code anyways. It's gotten to the point I roll my eyes whenever I see people saying "patches welcome". Chances are they're not as welcome as you would think. "Show us the code", and when you do... Nothing. Submitting a pull request is no guarantee that they'll accept it. Hell it's no guarantee they'll even give you the time of day. You can put in a whole lot of effort and still end up getting refused or even straight up ignored. Even if it's an unambiguous improvement on the status quo. They'll commit code that literally returns "not implemented" directly to master and actually ship it out to users. Your pull request will certainly be held to much higher standards though. And that's if they engage with you in an attempt to get your patches merged. They might just decide to ignore your patch and redo all the work themselves, which is exactly what all the complainers wanted them to do in the first place! If they're really nice they'll even credit you in the commit message! If you're gonna put in effort into someone else's project, just fork it straight up and make it your own project. Don't waste time with upstream. Don't wait for their blessing. Just start making your own version better for you. Don't even submit it back, they can pull it themselves if they want to.
- bagels 2y ago
  Boo to you. I've up-streamed patches to scipy and a few other python packages. Nobody ever said no to genuine high quality bug reports that were coupled with good fixes. Not saying that will happen every time, but if you're unsure, ask how receptive they are.

Hasnep 2y ago

The Refined GitHub extension [1] automatically hides comments that add nothing to the discussion. [2] [1] https://github.com/refined-github/refined-github https://github.com/refined-github/refined-github [2] https://github-production-user-asset-6210df.s3.amazonaws.com/83146190/258220965-4743b9b9-2aef-41b3-a905-ccf8d7beb74e.png https://github-production-user-asset-6210df.s3.amazonaws.com...

bityard 2y ago
Wow, that extension is a gold mine of much needed GitHub functionality

raverbashing 2y ago

Geez honestly This seems to be the issue https://github.com/explosion/spaCy/issues/13658#issuecomment-2797841747 https://github.com/explosion/spaCy/issues/13658#issuecomment... And you depend on opinionated libraries that break with newer versions. Why? Well because f you that's why! Because our library is not just a tool, it's a lifestyle Though it seems that Pydantic 1x does support 3.13 https://docs.pydantic.dev/1.10/changelog/#v11020-2025-01-07 https://docs.pydantic.dev/1.10/changelog/#v11020-2025-01-07