17 ms·

So if I run the same command with all of the parameters you specify and it works correctly, I can close your issue as non-reproducible, right?

djur 6y ago
Sure, as long as you're polite about it (and it would be incumbent on the reporter to be polite as well). It's not your responsibility to help users debug. If you do that often, for issues that are actually more widely reproducible, your software might end up getting a reputation for instability. Whether you care about that or not is up to you.
FartyMcFarter 6y ago
That is up to you. Different people/projects have different standards for how much effort they put into a bug. If you think the issue is unlikely to be an actual bug, that would seem like the correct course to take. If you suspect it might depend on other details and you're keen to investigate more, you could ask for more details. One related thing that many projects do is to have a bug template that asks for details such as software versions, operating system, CPU, etc. This can help a lot in reproducing bugs.
justinclift 6y ago
> So if I run the same command with all of the parameters you specify and it works correctly, I can close your issue as non-reproducible, right? Depends how you want your project to be perceived. If you don't give a crap, and just want to close issues then sure. ;) If you're interested in finding out why the bug is occurring in such a strange way, and potentially solving the problem... then working with the user to figure out the cause (whether it's their fault or not) is going to be more useful. :) If you're the only maintainer of your project though, and it happens a lot then personally I'm not sure what the right approach is. The projects I'm involved with do have it happen, but it's not that often. So we're not too burned out by those things.

17 ms·

So if I run the same command with all of the parameters you specify and it works correctly, I can close your issue as non-reproducible, right?

by rmrfrmrf 6y ago

djur 6y ago
Sure, as long as you're polite about it (and it would be incumbent on the reporter to be polite as well). It's not your responsibility to help users debug. If you do that often, for issues that are actually more widely reproducible, your software might end up getting a reputation for instability. Whether you care about that or not is up to you.
FartyMcFarter 6y ago
That is up to you. Different people/projects have different standards for how much effort they put into a bug. If you think the issue is unlikely to be an actual bug, that would seem like the correct course to take. If you suspect it might depend on other details and you're keen to investigate more, you could ask for more details. One related thing that many projects do is to have a bug template that asks for details such as software versions, operating system, CPU, etc. This can help a lot in reproducing bugs.
justinclift 6y ago
> So if I run the same command with all of the parameters you specify and it works correctly, I can close your issue as non-reproducible, right? Depends how you want your project to be perceived. If you don't give a crap, and just want to close issues then sure. ;) If you're interested in finding out why the bug is occurring in such a strange way, and potentially solving the problem... then working with the user to figure out the cause (whether it's their fault or not) is going to be more useful. :) If you're the only maintainer of your project though, and it happens a lot then personally I'm not sure what the right approach is. The projects I'm involved with do have it happen, but it's not that often. So we're not too burned out by those things.