5 ms·

Sometimes I feel guilty closing even low quality issues like those :(

• Demiurge 11y ago
  There should be no guilt on either side. Sometimes putting time into investigating the stack trace isn't worth it for the user. However, reporting it still a good idea because the developer might recognize a regression or another angle at a bug being already experienced. If not, it's not a big deal to dismiss.
  • enraged_camel 11y ago
    I don't agree. The reporting party should feel guilty about not putting effort into providing system information and troubleshooting further and reporting their findings. This is exactly why Stack Overflow works so well: low quality questions are downvoted mercilessly, and closed if they aren't improved within a short time period. It is also why automated reporting tools provide a good amount of contextual information along with the error and stack trace. Furthermore, not including a description of the issue along with the stack trace makes it impossible for other users to determine if they are experiencing the same issue or something else (since it is possible for two different bugs to produce the same stack trace, or even the same error message).
    • bryanlarsen 11y ago
      The alternative to a low quality bug report is usually no bug report. Démiurge is spot on.
  • mizzao 11y ago
    I suppose this is true, but in my experience a low quality bug report is usually either user error or not familiar to the developer. In both of those cases more investigation would help, and often the user corrects him/herself. Only in rare cases does the developer have a magic fix for a (not even formatted) stack trace.