How to post issues to GitHub? [Lua]

Hi Guys!

I want to make it so when my OS crashes it will automatically report the error and version to GitHub.

Thanks!

- House

You'll need your own (real) server, and write software for the server to do this. Note that anyone can post an issue and abuse through the user you'll set up to post issues on the operating system's user's behalf. Here's a brief outline on what you need to do.

First, you need to authenticate the server. You can do this:
- via OAuth: https://developer.github.com/v3/oauth/
- or with a user token: https://github.com/settings/tokens/new
- or with a password: https://developer.github.com/v3/auth/#basic-authentication

Then you simply call the create issue endpoint:
https://developer.github.com/v3/issues/#create-an-issue

I dunno if it would be a great idea, because if a users system crashes often (maybe if it often reboots), then you get hundred of issues.
Also, the user should know that it will be reported.

Sewbacca, on 12 October 2016 - 04:11 PM said:

I dunno if it would be a great idea, because if a users system crashes often (maybe if it often reboots), then you get hundred of issues.
Also, the user should know that it will be reported.

Well, you would simply not post the issue if an open issue exists with the same name/error. It is difficult, but effective against repeat automatic bug reports.

Hbomb_79, on 12 October 2016 - 08:44 PM said:

Sewbacca, on 12 October 2016 - 04:11 PM said:

I dunno if it would be a great idea, because if a users system crashes often (maybe if it often reboots), then you get hundred of issues.
Also, the user should know that it will be reported.

Well, you would simply not post the issue if an open issue exists with the same name/error. It is difficult, but effective against repeat automatic bug reports.

Okay, but what is, if someone edits the code and occur variable errors like error(tostring({}))?

Sewbacca, on 12 October 2016 - 10:23 PM said:

Okay, but what is, if someone edits the code and occur variable errors like error(tostring({}))?

That's simple. If the MD5 of the file doesn't match, don't post the issue because the user has modified it or are using an older version.

KingofGamesYami, on 12 October 2016 - 11:09 PM said:

Sewbacca, on 12 October 2016 - 10:23 PM said:

Okay, but what is, if someone edits the code and occur variable errors like error(tostring({}))?

That's simple. If the MD5 of the file doesn't match, don't post the issue because the user has modified it or are using an older version.

but then you've to create MD5 hashes form all OS files, and comparing to all versions, existing (He wanted to get all errors from all versions). Reporting the error would take much time.

Sewbacca, on 13 October 2016 - 12:53 PM said:

but then you've to create MD5 hashes form all OS files, and comparing to all versions, existing (He wanted to get all errors from all versions). Reporting the error would take much time.

It would be a single command (under Linux) to md5 all files in a directory, let me check my zsh history for the command.

EDIT: The command is: find . -type f -exec md5sum {} \; > dir.md5

Admicos, on 13 October 2016 - 12:55 PM said:

Sewbacca, on 13 October 2016 - 12:53 PM said:

but then you've to create MD5 hashes form all OS files, and comparing to all versions, existing (He wanted to get all errors from all versions). Reporting the error would take much time.

It would be a single command (under Linux) to md5 all files in a directory, let me check my zsh history for the command.

A single command which takes some minutes.

Sewbacca, on 13 October 2016 - 12:56 PM said:

A single command which takes some minutes.

It will take minutes if you have gigantic files, but then a CC os probably doesn't have any files that is that large.

Admicos, on 13 October 2016 - 01:02 PM said:

Sewbacca, on 13 October 2016 - 12:56 PM said:

A single command which takes some minutes.

It will take minutes if you have gigantic files, but then a CC os probably doesn't have any files that is that large.

Also you can hash the native files, delete them (except the md5 hash) and post many bugs.

You don't have to hash anything at all. If someone really wants to mess this up they can claim to have the correct file by submitting the correct md5. They just have to bypass your Lua code and call the API on their own.

H4X0RZ, on 16 October 2016 - 08:19 PM said:

You don't have to hash anything at all. If someone really wants to mess this up they can claim to have the correct file by submitting the correct md5. They just have to bypass your Lua code and call the API on their own.

The idea here is to prevent someone's stupidity from auto-reporting errors they created, not to prevent against malicious intent. We've already established that the github account will be fully accessible by anyone who looks at the code.

KingofGamesYami, on 16 October 2016 - 09:18 PM said:

H4X0RZ, on 16 October 2016 - 08:19 PM said:

You don't have to hash anything at all. If someone really wants to mess this up they can claim to have the correct file by submitting the correct md5. They just have to bypass your Lua code and call the API on their own.

The idea here is to prevent someone's stupidity from auto-reporting errors they created, not to prevent against malicious intent. We've already established that the github account will be fully accessible by anyone who looks at the code.

Oh, okay. I should read the whole post next time. Sorry :/