Under some (yet unknown) circumstances (mostly on exceptions) logs don't get displayed in ROXcomposer GUI after some point in sending a message through a pipeline.
The problem arised during testing a Word2Vec service. The unit-tests worked fine and logs had been displayed, but the Log page in the GUI showed nothing after the watched service has crashed. Neither exceptions nor logs were visible. Physical logs where present and readable in ROXcomposers ./logs/services folder.
The API that sends the logs to the GUI returns a "200 OK" HTTP status when opening the log page.
We assume that the problem is not in ROXcomposer GUI but instead in ROXcomposer's LogObserver.
Under some (yet unknown) circumstances (mostly on exceptions) logs don't get displayed in ROXcomposer GUI after some point in sending a message through a pipeline.
The problem arised during testing a Word2Vec service. The unit-tests worked fine and logs had been displayed, but the Log page in the GUI showed nothing after the watched service has crashed. Neither exceptions nor logs were visible. Physical logs where present and readable in ROXcomposers ./logs/services folder.
The API that sends the logs to the GUI returns a "200 OK" HTTP status when opening the log page.
We assume that the problem is not in ROXcomposer GUI but instead in ROXcomposer's LogObserver.