Skip to content

Conversation

@BrianJKoopman
Copy link
Member

@BrianJKoopman BrianJKoopman commented Jun 18, 2025

As noted in the commit message for 81d89a3, this actually used to block until stream start. When we changed the behavior of ocs to automatically set session.status('running') this no longer blocked. Until then, the agent was setting 'running' after the stream was enabled.

We need to merge simonsobs/socs#898, but this at least gets an example for the usage up.

Feedback welcome.

Resolves #215.

This increased timeout came from #147. Back then, the session.status was
manually set to running, but only after the call to 'stream_g3_on' in the
agent. This meant that check_started would actually block until the stream was
enabled. Now that ocs automatically sets the status to running, this no longer
works, which is why we need this additional check.

check_started should return quickly now, and shouldn't come close to this 60
second timeout.
@BrianJKoopman BrianJKoopman force-pushed the koopman/stream-start-check branch from dd87ffc to cce0c4e Compare August 11, 2025 19:10
@BrianJKoopman BrianJKoopman marked this pull request as ready for review August 11, 2025 19:18
@BrianJKoopman BrianJKoopman merged commit 56bcdd7 into main Aug 11, 2025
6 checks passed
@BrianJKoopman BrianJKoopman deleted the koopman/stream-start-check branch August 11, 2025 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

smurf.stream does not wait fully until streaming is running before returning

1 participant