Repeat after me:
- Initial conditions
- Expected behavior
- Actual behavior
- Steps to reproduce, if known.
#BugReporting #BugReport #BugReports
#SoftwareEngineering #SoftwareDevelopment
#BugReports
If I could block Jira from accepting any bug report that contained the phrase "has issues" anywhere, I would.
Learn how to write a good goddamned bug report. If it didn't "have issues" there wouldn't be a need of a report.
Clearly state the expected and actual behaviors.
#BugReports #Software #SoftwareDevelopment #SoftwareEngineering
"Anyone know where to submit a bug report for the official Mastodon iOS app?"
That would be here:
Github, Mastodon, mastodon-ios Issues
You'll need your own login, I do believe
I don't know who needs to hear this, but "has issues" is NOT a problem description, and you deserve to have your bug report disregarded and summarily closed.
#software #softwareEngineering #softwareDevelopment #bugReport #bugReports
Them: what do you do for fun?
Me: oh, you know, games, movies, TV
Me actually: https://github.com/osmandapp/OsmAnd/issues/21967#issue-2876784180
Having another strange issue (this time not network related).
If I attach an external Keyboard (Keychron Q8 ISO-DE) to my MacBook Air M2, it has a wrong Layout. The key on the left, next to shift should be "<" and ">" but is "^" and "°" - it's working fine on the internal keyboard. But it looks, like the system recognizes both keyboards as ANSI whereas it's ISO.
Removing `/Library/Preferences/com.apple.keyboardtype.plist` and going through the keyboard-identification-wizard didn't help (as in: didn't changed anything).
Created an Bugreport, which is open since weeks: FB16272721 - may a friendly apple employee jump in?
#apple #keyboard #keybindings #keyboards #appleemployee #bug #bugs #bugreporting #bugreports
Tom’s Hardware: Alleged 7-Zip arbitrary code execution exploit leaked to Twitter — the 7-Zip author claims this exploit not only isn’t real but was generated by AI . “Yesterday, user @NSA_Employee39 allegedly posted a zero-day exploit for the popular open-source file decompression utility 7-Zip on Twitter, only to have 7-Zip author Igor Pavlov swiftly dismiss it as a fake report. Other […]
#Opensource #maintainers are drowning in junk #bugreports written by #AI
#Python #security #developer-in-residence decries use of bots that 'cannot understand code' https://www.theregister.com/2024/12/10/ai_slop_bug_reports/ #slop #AISlop
Bis zum #Burnout: #OpenSource-Entwickler von #KI-#BugReports genervt | heise online https://www.heise.de/news/Bis-zum-Burn-out-Open-Source-Entwickler-von-KI-Bug-Reports-genervt-10195951.html
Annoying bug on the #BlueSky #Android app. Better than what came before (long text got clipped) but still annoying. #BugReports
@Quinnypig you quote a reply to #Canonical #BugReports?
Many, many years ago, this was with Bugzilla in the early 2000s, I got my first automated lecture on what constitutes a good bug report. I probably didn’t pay attention. Since then, I’ve seen this list countless times, in various levels of detail, across a broad array of systems:
- What did you do?
- What happened?
- What did you expect to happen?
Over the last few years I’ve come to realize that this list is irreducible, if you’re losing one item you lose important context, and represents a kind of deep wisdom:
- What Did You Do? — If we cannot see the steps that brought you into the situation, it’ll be hard to find the place in the program where it happens. It’ll also set up our mental model of the program in question to see what we think should happen.
Preferably this should be detailed and reliable enough to reproduce the problem on our side. Things that cannot be reliably reproduced are very hard to fix, because you’ll never truly know if they’re gone. - What happened? — This gives context on what happened for you, which might be different for us, indicating some other issue. In some cases this is what we thought should happen, so this also gives a clear statement to set up the next point.
- What did you expect to happen? — Stating how your expectation differs from reality is what makes this a bug. You’re not reporting issues where the system does what you expected it should do. But this expectation might differ from what we were expecting. The issue need not be in the code or the implementation, but might be somewhere else. Maybe the documentation gave you a wrong idea on what should happen?
Sometimes a bug report can be succinct but still contain all three items: “I clicked on save. It did not save. I expected it to save.” Though in this case the first part really should be longer, because this is probably something that only happens under certain circumstances. And even if part 3 is only “I expected it to work”, that’s good to write out.
Bug reports consisting of a single screenshot, for example of an error message, are often not helpful. They, more or less, cover part 2, but leave out important context. It may not be obvious from the screenshot on how to get there. And it’s as likely as not that we think that this is the expected behavior. You should state why you think this error message is, as it were, in error.
The three parts of a good bug report are interlocking. Like describing the way to the train station to a stranger. You’re not going to describe it as “Turn left second street, go right first street, go right third street.” You’re giving context: “Go down this street and turn left at the second intersection, right behind the flower shop. You should see the church in front of you, turn immediately right and go into the small alley. If you then turn right at the third street you should see the train station in the distance.”
This is redundant. But redundancy is good. It allows for error checking and correction. It allows for there to be errors in both the environment and in its mental model or description thereof.
So, repeat after me: What did you do? What happened? What did you expect to happen?
I can't believe it took me this long, but apparently, I'm just lucky in regards to bugs in software. I just reported my first ever bug to the #KDE team.
Woke up to about 15-20 Dr Konqi windows after Plasma Shell crashed repeatedly during the night. Most of the windows were non-responsive but the last one was usable, even though it soft-froze a few times while I was entering the data.
Support, QA, and engineering people of the world, banish these phrases from your vocabulary:
- Doesn't work
- Not working
- Has issues
None of these phrases communicate any information at all. If it was working, you wouldn't be opening a bug report about it.
Instead, describe what is wrong with the behavior of the thing.
In today's Nice Micro Monday episode, I provide you with a long rant about the software distribution models on Linux and what I think are the remaining issues that need to be solved.
PeerTube link in the reply post.
Does anyone know how to reach a human at #NextDNS? I'm a paying customer, but I'm unable to sign up for their support forums due to an error (yes, they require a *second* login). They also don't have a "security.txt" file that I can use.
They're blocking my domain to tell me they're not blocking my domain. Literally. I've reset all my #DNS caches and even slept for eight hours, to no avail.
I restored to emailing the owner of the company through the email address on his GitHub profile. It's that mis-managed over there. I think I want my money back.
(Note: I changed Firefox to use Cloudflare's DoH to post this.)
#securitytxt #bugreports #softwaredevelopment #itsalwaysdns #support
#kdeneon #bugreports #kdeplasma6
Bug Reports nach Suche mit Stichwort "KDE Neon".
https://bugs.kde.org/buglist.cgi?quicksearch=KDE%20Neon%20
Sieht so aus, als wenn ich mindestens noch einen Monat warte. Und dann nochmal nachschauen.
Aktuell liest sich das wie "dein Laptop ist tot nach dem Upgrade" 😬😳
Aber ich bin neugierig. Vllt zieh ich mir ne USB Live Version für den Stick, nur um mal n Blick reinwerfen zu können, ohne es zu installieren.
Mal schauen.
general bug reporting PSA: dont be worried about "taking dev time" with bug reports, all bug reports are welcome even if you might feel its odd.
Just make sure to:
- write what you did and what happened
- if it's a crash, share logs with debug symbols
- be patient
- if you can show screenshot/video, that's awesome!
If it's a duplicate bug, it's easy to close it. Duplicate bugs also help often to see how many people are having some issue and help us prioritize.
Sometimes your bugreport might just be the missing link or the weird edgecase we're looking for to fix something that appears only rarely!
So yes report all the bugs! We can't squash them otherwise.
Das schlimmste, finde ich, beim Erstellen von #bugreports z.B. bei #Github
Man macht sich mühe, alle gewünschen Punkte auszufüllen, stößt den/die Dev's soweit wie es das eigene Wissen und/oder die Zeit erlaubt mit der Nase auf das Problem bzw. dessen Lösung, und dann...
...
...
passiert einfach nix. Garnix. Über Wochen. Nichtmal eine Antwort. Zumindest keine vom Team, nur von Leuten die das gleiche Problem haben.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst