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 6 months ago by evenwicht@lemmy.sdf.org to c/softwarequality@infosec.pub

0 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.

no comments (yet)

sorted by: hot top new old

there doesn't seem to be anything here

this post was submitted on 23 Dec 2025

1 points (100.0% liked)

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

60 readers

2 users here now

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

testing
bug reporting
project management, policies and procedures
bug bounties
culture (conducive to quality or contrary thereto)
design
programming languages
code transparency

!broken_software@lemmings.world

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

!bugs@sopuli.xyz

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 9 months ago

MODERATORS

daveyOsborn@infosec.pub