| Thread Previous • Date Previous • Date Next • Thread Next |
On 2019-05-29 05:47, Maciej Suminski wrote:
If everything works as expected, then you should be able to see your reports in my test project bug tracker [1]. The crash reporter should receive link to the new bug report in the HTTP response, so I guess it could be shown to the user. Once we are confident with the crash reporter, I will modify the HTTPrequest handler to create bug reports directly in the KiCad bug tracker.Cheers, Orson 1. https://bugs.launchpad.net/kicad-git-test/+bugs?field.tag=crash-reporter&orderby=-id&start=0
Hi Orson-Still can't get the server to respond. I captured the response data in KiCad:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator at root@xxxxxxxxxxxx to inform them of the time this error occurred, and the actions you performed just before this error.</p> <p>More information about this error may be available in the server error log.</p> </body></html>The response when using curl on the commandline works fine and it logs the bug report.
-Seth
| Thread Previous • Date Previous • Date Next • Thread Next |
