Implement bug-report command

[rethinkdb]

Implement bug-report command

[al3xandru]

1. Is there any way this command would also retrieve the last error/crash info?
2. In other bug reports I've noticed that we usually need more info to look into a crash (like a core, data files, etc.). It might make sense to simplify the process of submitting these too.

[jdoliner]

I think the really important thing this needs to do is bundle up the core file, database files and the version and somehow transfer those files to us.

I think automatically submitting to github is a bit dubious presumably we're either going to need them to enter their username and password which is a security risk or somehow make rethinkdb emulate being a github app. If my database asked me to do either of these just to file a bug I don't think I'd trust it and probably would just go and file the bug my

[coffeemug]

Hmm, I didn't consider that. I suppose another option is to have it push the bug report to a url on our server, and we can then submit it to github with a 'rethinkdb-bug' account and give them the url. That would probably be nicer.

[al3xandru]

Looks like @jdoliner and I agree on what needs to be transfered. We also want to make sure that if we transfer any database files to us the user is aware of that and allows us to do it.

[jdoliner]

That sounds good. I'm not sure if systems exist for holding on to the core files etc. (I believe the term for them is artifacts of the bug.) Back when I was using sourceforge it had artifacts in the bug tracker I believe. But of course it was pretty muddlesome to use because sourceforge.

[jdoliner]

Also this should go without saying but there's no way this should be part of the rethinkdb main binary. It should be a separate script.

[sophiebits]

(Just FYI) At Khan Academy, we have a user called @KhanBugz which issues for our repo khan-exercises are filed from:

Khan/khan-exercises#33571

Our issue tracker is horribly polluted because it's really easy to submit an issue from the website, but I'd imagine that a similar approach would work here.

[coffeemug]

That's great, I think we'll go with this. Thanks @spicyj.

[jdoliner]

This is currently blocked on not having a solution for where to upload these files to.

[coffeemug]

Ack.

[coffeemug]

@jdoliner -- can you post the flow of the command here (assuming it's defined by now) so we can critique?

[jdoliner]

The flow I have right now is just:

rethinkdb report [whatever arguments you invoked rethinkdb with]

Then you get a scary looking warning saying that this will transfer your data to RethinkDB and not to do it if you have sensitive data present. You have to type "yes" to continue otherwise it aborts.

[srh]

Closing, we want Github issues to be tied to a specific user so that we can ask follow-up questions, and (a wild guess appears!) nobody wants to develop or host this open proxy for posting to Github.