Skip to content

More informative Error reports #3278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
piogor opened this issue Nov 16, 2017 · 1 comment
Closed

More informative Error reports #3278

piogor opened this issue Nov 16, 2017 · 1 comment
Labels
Support Support question

Comments

@piogor
Copy link

piogor commented Nov 16, 2017

Details

  • Project URL: ALL
  • Build URL (if applicable):
  • Read the Docs username (if applicable):

Expected Result

It would be nice if in case of Unknown Error one can get more info, for example full terminal output.
As it was in #3277 pdflatex gets into trouble (hangs) with latex output of Sphinx 1.5.6. This was not possible to find out on the RtD build report since there were no output from pdflatex. Having access to it would make detecting problem easier.

Actual Result

Unknown Error does not produce meaningful information. There are few of such reports: #3277, #3276, #2680 and so...

@RichardLitt RichardLitt added the Improvement Minor improvement to code label Nov 16, 2017
@agjohnson agjohnson added Support Support question and removed Improvement Minor improvement to code labels Nov 16, 2017
@agjohnson
Copy link
Contributor

Giving out a possible traceback would be a security flaw here, so we've made the design decision -- on purpose -- to limit information here. The goal is to spur issue reports where we can actually determine the error cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Support question
Projects
None yet
Development

No branches or pull requests

3 participants