Story
Currently, the logging is only relevant to the developer, no logic is setup to track it or propagate it to the user of the gui. This makes edge cases harder to decipher when things go wrong, it also hurts our credibility as providing full provenance and reproducibility. Basic logging is a must, when setting this up we might include a way to view this from the gui (user facing), perhaps even with realtime updates; I'll expand on this and dig deeper in the proposal below.
Proposal
A rolling window will save the tail of the log to the a file and keep it the desired length to not interfere with memory, options in app_info.yaml to set the size of the rolling window. A button then allows you to view this log whenever deired from the gui.
Notes
The scope here is focused on setting up basic logging, this should be done in a way that makes expanding to additional features easier later. Future features might include:
- Bundle logs with data output option.
- View logs from the Dataset page.
- Live viewing option for processes.
Story
Currently, the logging is only relevant to the developer, no logic is setup to track it or propagate it to the user of the gui. This makes edge cases harder to decipher when things go wrong, it also hurts our credibility as providing full provenance and reproducibility. Basic logging is a must, when setting this up we might include a way to view this from the gui (user facing), perhaps even with realtime updates; I'll expand on this and dig deeper in the proposal below.
Proposal
A rolling window will save the tail of the log to the a file and keep it the desired length to not interfere with memory, options in app_info.yaml to set the size of the rolling window. A button then allows you to view this log whenever deired from the gui.
Notes
The scope here is focused on setting up basic logging, this should be done in a way that makes expanding to additional features easier later. Future features might include: