Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execute keepalive client expectations #48

Closed
werkt opened this issue Jan 16, 2019 · 2 comments
Closed

Execute keepalive client expectations #48

werkt opened this issue Jan 16, 2019 · 2 comments
Assignees

Comments

@werkt
Copy link
Collaborator

werkt commented Jan 16, 2019

We should clarify the expected behavior in the API for streaming responses meant to ensure that an operation is still in progress with long intervals between reported status changes. Namely that operations will be updated with done = false, the operation name in place, and either unchanged since the last update or absent metadata.

@bergsieker bergsieker self-assigned this Jan 16, 2019
@bergsieker
Copy link
Collaborator

Is this a duplicate of #57 or am I missing something?

@bergsieker bergsieker added this to the Remote Execution API v2 milestone Mar 12, 2019
@werkt
Copy link
Collaborator Author

werkt commented Mar 12, 2019

It is, this was probably the result of two successive remote ex API meetings, and forgetting that I had put up a tracker already.

@werkt werkt closed this as completed Mar 12, 2019
santigl pushed a commit to santigl/remote-apis that referenced this issue Aug 26, 2020
* Building Merkle tree into Chunkers

* Addressing comments
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

No branches or pull requests

2 participants