feat: throttling, batching websocket requests #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current State of the world
This is the progress object that is sent to the orchestrator,
Currently, it is sent to the orchestrator at each step. If offline, it currently retries 5 times and gives up
This PR does the following:
Changes the logic so:
ClientProgramProofRequest
is now sent every 3 minutes, and not every stepproof_duration_millis
andsteps_proven in memory
and updateClientProgramProofRequest
with the new variables.ClientProgramProofRequest
objects being sent to the orchestrator