beat.core issueshttps://gitlab.idiap.ch/beat/beat.core/-/issues2017-08-06T11:17:03Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/44Agent is unprotected in case the user sends to many "nxt" commands2017-08-06T11:17:03ZAndré AnjosAgent is unprotected in case the user sends to many "nxt" commandsWe should put in place:
1. A check in the agent side (around line 150), that prevents the agent to measure the length of `None'
2. A new protocol reply possibility for an erroneous condition on the `nxt` operation.
We should put in place:
1. A check in the agent side (around line 150), that prevents the agent to measure the length of `None'
2. A new protocol reply possibility for an erroneous condition on the `nxt` operation.
BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/42[io] Execute externally currently requires twisted (async.run)2017-08-06T11:17:03ZLaurent EL SHAFEY[io] Execute externally currently requires twisted (async.run)With the introduction of the new I/O framework, the execution of a job requires to launch the I/O daemon (that will launch and control the user process). This daemon currently needs twisted (async.run) to be executed, while we would idea...With the introduction of the new I/O framework, the execution of a job requires to launch the I/O daemon (that will launch and control the user process). This daemon currently needs twisted (async.run) to be executed, while we would ideally prefer not to have such a dependency in beat.core.
To fix this, an optimal decapsulation of the communication via pipes from the I/O daemon would be required, as well as its integration into beat.core.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/41[io] Optimization of I/O when using pipes2017-08-06T11:17:03ZLaurent EL SHAFEY[io] Optimization of I/O when using pipesWith the introduction of communication via pipes between the user process and the daemon, it may happen that a chunk of data is decoded from a baseformat and then re-encoded (into a baseformat) to send it through pipe. This is the case, ...With the introduction of communication via pipes between the user process and the daemon, it may happen that a chunk of data is decoded from a baseformat and then re-encoded (into a baseformat) to send it through pipe. This is the case, when next() is called: a chunk of data is then read using a CachedDataSource (that will decode from a baseformat) and then sent through a pipe (and hence will be re-encoded into a baseformat). This is of course suboptimal and may be fixed by specializing the CachedDataSource.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/40Cleanup of executor/dataformats/algorithms/libraries/schema loading2017-08-06T11:17:03ZAndré AnjosCleanup of executor/dataformats/algorithms/libraries/schema loadingAs of today, we moved the definition of these objects and functions to beat.backend.python. The backend does not need to be able to validate objects, only to load them and instantiate a runner. We should revise and clean-up this relation...As of today, we moved the definition of these objects and functions to beat.backend.python. The backend does not need to be able to validate objects, only to load them and instantiate a runner. We should revise and clean-up this relationship.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/39inputs/outputs cleanup w.r.t beat.backend.python2017-08-06T11:17:03ZAndré Anjosinputs/outputs cleanup w.r.t beat.backend.pythonAs of today there is some functionality of beat.backend.python that is duplicated in this package. We should clean-up and organised it so there is no repetition of code, respecting a good DRY principle.As of today there is some functionality of beat.backend.python that is duplicated in this package. We should clean-up and organised it so there is no repetition of code, respecting a good DRY principle.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/38discover_environments() does not crash when the same environment/version is d...2017-08-06T11:17:03ZLaurent EL SHAFEYdiscover_environments() does not crash when the same environment/version is detected multiple timesWhile this should raise an exception.While this should raise an exception.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/34JSON declarations should be versioned2017-08-06T11:17:03ZAndré AnjosJSON declarations should be versionedWe should include a version field on the JSON declaration to allow for changes on the declaration to co-exist.We should include a version field on the JSON declaration to allow for changes on the declaration to co-exist.BTAS TutorialAndré AnjosAndré Anjos