webui-client issueshttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues2022-05-11T23:44:58+02:00https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/70worker: Remove pipe communication2022-05-11T23:44:58+02:00Tomáš Peckaworker: Remove pipe communicationSee https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/issues/223See https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/issues/223Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/50Filter ALT algorithms2022-05-10T19:53:39+02:00Tomáš PeckaFilter ALT algorithmsI don't think we want to map all the provided algorithms from ALT 1:1. For instance, I don't think we need `example::*` algos.
So let's either
* write a filter for some algorithms
* do not link some libs to the result.
This is someth...I don't think we want to map all the provided algorithms from ALT 1:1. For instance, I don't think we need `example::*` algos.
So let's either
* write a filter for some algorithms
* do not link some libs to the result.
This is something that should probably be done in cooperation with #40.BPhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/40algorithms.json should probably be fetched from the server2022-02-20T20:27:07+01:00Tomáš Peckaalgorithms.json should probably be fetched from the server... so we do not have to bundle it into the client and rebuild everytime we want to upgrade backend... so we do not have to bundle it into the client and rebuild everytime we want to upgrade backendTomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/42show algorithm's verbose output2021-11-14T18:44:30+01:00Tomáš Peckashow algorithm's verbose outputTomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/43Worker sometimes fails with pure virtual method called2021-02-07T11:59:30+01:00Tomáš PeckaWorker sometimes fails with pure virtual method calledIt happened twice. This crashes the worker but the job is still in the server's queue.
I started workers in debug mode in production, we shall see whether this happens again.It happened twice. This crashes the worker but the job is still in the server's queue.
I started workers in debug mode in production, we shall see whether this happens again.Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/46Log higher priority messages to stderr2020-11-15T14:39:13+01:00Tomáš PeckaLog higher priority messages to stderrWe forward logs from docker containers to hosts journald in deployment. Docker [apparently](1) logs only stderr messages as critical. However, spdlog logs everything to stdout.
Probably we have to create two sinks for the worker loggers...We forward logs from docker containers to hosts journald in deployment. Docker [apparently](1) logs only stderr messages as critical. However, spdlog logs everything to stdout.
Probably we have to create two sinks for the worker loggers.
[1] https://github.com/docker/docker-ce/blob/96d50fd61df5a62a26609523619f5a5386b7d6db/components/engine/daemon/logger/journald/journald.go#L122Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/44Crashed worker causes the job not to be removed from queue2020-11-07T18:33:10+01:00Tomáš PeckaCrashed worker causes the job not to be removed from queueso the other workers fetch the job and keep themselves busy crashing&restarting ...so the other workers fetch the job and keep themselves busy crashing&restarting ...Tomáš PeckaTomáš Pecka