I am currently trying to improve some of my templates to make them display errors and warnings in the Chunks detail list in a more useful way.
The specific case I am concerned with is the following one:
– a chunk produces an error or a warning and fails to render, it prints an error message, which is catched by onCheckLog()
– the executable returns an exit code != 0 and therefore returns an MTemplateAPI.MTemplateError, which overwrites the much more meaningful error message from onCheckLog()
– what I see in the Chunks Detail view is “Exit code 1 different from expected 0 value” instead of e.g. “Out of memory error” or “Failed to read pixel date from image file …”
So the question is: Is there a way to check in onCheckExitCode() whether or not an error was already returned in onCheckLog() or onCheckLogLine()?
Of course I don’t want to just disable or skip onCheckExitCode(), because there might be cases where the exit code is the only indication of a failed rendering.
Unfortunately at the moment no, but in Muster 9 close to release, we have a completely redesigned error system where you should be able to have a finer control over the errors reporting
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
We use cookies to ensure that we give you the best experience on our website Cookies are also used to send anonymous browsing data to Google Analytics. We give you the option to Refuse our cookies.