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.

Sign up for GitHub

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

Jump to bottom

improve waitContainerToCatchUp to work with storages that do not provide checkpointSequenceNumber #8063

Closed
Tracked by #7995
vladsud opened this issue Oct 30, 2021 · 1 comment
Closed
Tracked by #7995

improve waitContainerToCatchUp to work with storages that do not provide checkpointSequenceNumber #8063

vladsud opened this issue Oct 30, 2021 · 1 comment
Assignees
@vladsud
Labels
ado Issue is tracked in the internal Azure DevOps backlog api status: stale

Comments

@vladsud
Copy link
Contributor

vladsud commented Oct 30, 2021

This likely should be used in #7884 as well for "read"'s "connected" event.
@vladsud vladsud added the bug Something isn't working label Oct 30, 2021
@vladsud vladsud added this to the November 2021 milestone Oct 30, 2021
@vladsud vladsud self-assigned this Oct 30, 2021
@curtisman curtisman added api and removed bug Something isn't working labels Nov 2, 2021
@vladsud vladsud modified the milestones: November 2021, December 2021 Nov 29, 2021
@vladsud vladsud mentioned this issue Dec 6, 2021
Closed
8 tasks
@vladsud vladsud modified the milestones: December 2021, January 2022 Dec 6, 2021
@vladsud vladsud modified the milestones: January 2022, Future Jan 30, 2022
@curtisman curtisman added the ado Issue is tracked in the internal Azure DevOps backlog label Jun 17, 2022
@microsoft-github-policy-service
Copy link
Contributor

This PR has been automatically marked as stale because it has had no activity for 60 days. It will be closed if no further activity occurs within 8 days of this comment. Thank you for your contributions to Fluid Framework!

@microsoft-github-policy-service microsoft-github-policy-service bot removed this from the Future milestone Apr 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vladsud vladsud

Labels
ado Issue is tracked in the internal Azure DevOps backlog api status: stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@curtisman @vladsud