Makyen

This is something that's happened a few times previously (the error is recognizable and consistent). Our current scanning process requires that if an answer is reported to SD, then the...

Has this code been tested by running it on a test SD instance in a chat room against a fork of the repository? If so, please provide a link to...

Given that this is doing something on GitHub, which isn't necessarily easy to recover from something going drastically wrong and/or possibly causing permanent loss of some data, yes, there needs...

In order to have a commit message that describes the change and not have the confusion of additional commits from merging the master branch into the development branch (sometimes merging...

Overall, working on this made quite a bit more sense when Staging Ground was in private beta, which was when this was proposed. After this was proposed, but prior to...

By "on-site" do you mean "on the global SE Network site" or "on MS"?

One possible solution to this is to break at least some of the check/scan logic out of bodyfetcher.py, such that scanning and reporting initiated from other sources also uses the...

Is there anything in the AJAX response from SE/SO that provides better information? I *thought* it was just forwarding the error declared in the AJAX response, but there might be...

Thanks for informing me. I saw it too as soon as I used SE after the change (which was clearly after you two :-) ). Looks like SE has changed...

@ByteCommander, Thanks for reporting this. It will be resolved in the next version. However, it does bring up an issue as to which header should be primary for those sites...