Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Acknowledge bug reports in what's new?
See original GitHub issueWe acknowledge bug-fixes in the whats new logs, bug not bug reports. Maybe we could do that?
It does take time and commitment to write a bug report (esp a good one), and it would be a way to show our community that we appreciate that kind of feedback.
e.g. :pr:1234 by X, bug report :issue:4321 by Y
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Everything You Need to Know About Bug Reports - Telerik
Let's cover what a bug report is and its purpose. Bug reports are where support engineers and developers outline errors and end-user encounters....
Read more >Sample Bug Report - Software Testing Help
The Sample, Bug/Defect Report given below will give you an exact idea of how to report a Bug in the Bug Tracking Tool?...
Read more >Bug Life Cycle and Reporting Guidelines
Bug reporting guidelines. If you're a web developer, see How to file a good bug; Make sure the bug is verified with the...
Read more >How to write good bug report: content, tips and tricks - EasyQA
New: When a bug is reported and posted for the first time. · Assigned: After the tester has reported the bug, the lead...
Read more >What is a "radar?" | Apple Developer Forums
You can now submit developer feedback and file bug reports to Apple using the native Feedback Assistant app for iOS and Mac, or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If the author of the bug report spend time investigating and in the end helped solving the issue, even without making the PR – definitely.
For bug reports that say “running this code produces the following exception” I’m not sure that we should. Particularly that a bug can be reported multiple times (cf multiprocessing related issues back at the time).
If the issue contributor is different from the PR contributor and the issue is proper, then we can acknowledge it?