Skip to content
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

More useful feedback from validation in dotify:xml-to-obfl #89

Open
bertfrees opened this issue Mar 2, 2016 · 6 comments
Open

More useful feedback from validation in dotify:xml-to-obfl #89

bertfrees opened this issue Mar 2, 2016 · 6 comments
Labels

Comments

@bertfrees
Copy link
Member

Maybe return a proper validation report?

How does this relate to mtmse/pipeline-mod-mtm#9?

CC @joeha480

@joeha480
Copy link
Member

joeha480 commented Mar 2, 2016

@bertfrees If it is the dtbook checks before the OBFL conversion (xslt) we're talking about, then I think this is related to the missing java logging daisy/pipeline-assembly#87

... Or maybe these are printed directly to standard out? I can't check right now how the schematron messages are printed, but I still haven't seen any java logging messages from the GUI so I can't rule that out either.

@bertfrees
Copy link
Member Author

Just to be clear: What Björn is talking about is what he can see in the GUI, the messages under "Execution log". Are you talking about that too? Everything that is logged in Java is send to the detailed log file, accessible through the button "Download detailed log" and only really useful for developers or for including in a bug report or something. The job messages (events) and the log serve two slightly different purposes (but I can understand it causes confusion).

I you haven't seen any Java logging messages in the GUI, that is perfectly normal. But you should have seen them them in the detailed log because the issue has been fixed for a while now (hope that's still the case).

If really what you want is Dotify log messages to go to the "event bus" we'll have to do something special. There are several other improvements that need to be done w.r.t. messaging, I'm planning to address them all in phase 3.

@joeha480
Copy link
Member

joeha480 commented Mar 3, 2016

I am not getting any detailed log what so ever at the moment, so I can't really tell, but I haven't seen any log messages from Dotify at any point in the advanced log.

See for example: jobs/2680/log

@bertfrees
Copy link
Member Author

OK. Just wanted to make sure there were no misunderstandings. I've also noticed that the log file is not accessible at all at the moment, Jostein is looking at it.

@josteinaj
Copy link
Member

yes, related: daisy/pipeline-webui#58

@bertfrees
Copy link
Member Author

With the newest improvements to messaging, all Dotify log messages with level INFO or higher will be send to both execution log and detailed log, and all messages with level DEBUG or higher are send to the detailed log. The level threshold is configurable in configuration files by the way, so if there is a need to include more Dotify messages that would be possible.

This is all in theory. The problem we are having with Dotify messages not ending up in the detailed log might well affect the execution log too.

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

No branches or pull requests

3 participants