You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2022. It is now read-only.
Adding an Event argument to the main() method and to the TeosDaemon constructor would allow for a more reliable synchronization mechanism.
A similar method could be used for all other processes as long as they are run via multiprocessing.Process.
The text was updated successfully, but these errors were encountered:
I tried to do some work in the 214-bootstrap-signal branch; it's easy to do it using an Event for processes that we create with multiprocessing.Process, but I didn't manage to use a simple method to synchronize with subprocesses created in other ways, like the api process created with gunicorn using popen. I tried to create a pipe using os.pipe, but getting an OSError: [Errno 9] Bad file descriptor when I tried to open it in the child process.
Currently, there is no way of knowing when the TeosDaemon is fully initialized and ready once
start
is called, therefore the e2e tests just wait for a timeout, which occasionally led to failures like this when the timeout is too short: https://app.circleci.com/pipelines/github/talaia-labs/python-teos/789/workflows/7301bb92-7e0b-4e64-ae1d-bccaef33f89c/jobs/1096Adding an Event argument to the
main()
method and to theTeosDaemon
constructor would allow for a more reliable synchronization mechanism.A similar method could be used for all other processes as long as they are run via
multiprocessing.Process
.The text was updated successfully, but these errors were encountered: