12
Most devs do not realise the s/w and docs need to be consistent. When bug reports are approached assuming a SUE (stupid user error), devs irrationally conclude there is no bug. (github.com)
submitted 2 months ago* (last edited 2 months ago) by evenwicht@lemmy.sdf.org to c/softwarequality@infosec.pub
1 comments fedilink hide all child comments

I just encountered the same confusion as others in the linked thread. The pipx tool has this in the man page:

       --pip-args PIP_ARGS
              Arbitrary pip arguments to pass directly to pip install/upgrade commands

So of course I had a space after --pip-args. It failed because the software does not work as documented. Someone reported this in 2019. The software is still inconsistent with the docs. Yet someone closed the bug report.

Re-opening or requesting re-opening requires licking Microsoft’s boots. I’m done with MS Github logins.

UPDATE: prime example of someone who thinks inconsistent docs are “not a bug” in a crossposted thread.

top 1 comments
sorted by: hot top controversial new old
[-] JakenVeina@midwest.social 2 points 2 months ago

Call it whatever you want, "bug" or not, it's an issue that needs action taken, and no action has yet been taken. Brushing you off like this is not acceptable.

this post was submitted on 23 Dec 2025
12 points (100.0% liked)

Software Quality Assurance (FOSS and non-FOSS) 🛡✓

55 readers
1 users here now

This is a place to broadly discuss anything related to software QA, such as:

Related:

To report specific bugs, consider the following related community instead of posting here:

I would suggest only posting about specific bugs in !softwarequality@infosec.pub if it’s not merely a bug to report but rather to showcase an example for a broader philosophical discussion.

Or perhaps if a bug has notable infosec consequences, it’s also worth discussing in !softwarequality@infosec.pub.

founded 5 months ago
MODERATORS
daveyOsborn@infosec.pub