Closed drscotthawley closed 1 year ago
UPDATE: Seems that that supposed error message that MyST detects from latexmk is either a false flag (ie latexmk command did NOT fail) or else...IDK.
But in any case, the error can be ignored. The new PDF file has been created and looks fine.
I think that tasks to do from this are better show the error messages that latex knows about if there is a failure, and have some better language around the errors saying that "everything might actually just be fine". LaTeX likes to complain about a lot, and we are only adapting to their error code status of the program is non-zero.
We could also show the shell log output, which will be a bit better than what is posted here!
I think we can also react to a few of the things in the logs for common errors and actually suggest some things to try. For example, I just went through and found this biber issue, which is "error code 2", having a friendly myst UI on top (1) shows errors; and (2) that actually suggests an action to take would be ideal.
Also -- if this happens again to you @drscotthawley, looking at the my-document.shell.log
is usually a bit better! We will make that clearer on the myst side!
The error messages and confusion of where to look should now be improved:
LaTeX is really really bad at error messages and logs. Hopefully this helps bypass the actions that you listed in the problem (open the logs, scroll, find and deduplicate the errors and warnings, maybe nothing is wrong anyways).
This has been released as myst-cli@0.1.9
! 🚀
Thanks again for your help, please open other issues as you find them.
Describe the bug
context When I do
myst build --pdf
expectation I expected to get my pdf.
bug Instead I get error messages from MyST but can find no corresponding errors in the log file
Here's an error message I ran into...
problem This is a problem for peopl who go and inspect the log file
_build/temp/mystyC3WIo/my-document.log
in hopes of seeing what the error was, who then see NO errors in the log file, will be unable to debug what MyST is complaining about. Thus they will not be able to resolve the problem.Reproduce the bug
myst build --pdf
.Here is the log file:
List your environment