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
Automation: Main Next Integrate #11606
Merged
sonalivdeshpande
merged 6 commits into
next
from
main-next-adab60b6aefca4220df573a4f3fed4d48d17884d
Aug 22, 2022
Merged
Automation: Main Next Integrate #11606
sonalivdeshpande
merged 6 commits into
next
from
main-next-adab60b6aefca4220df573a4f3fed4d48d17884d
Aug 22, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With `generateServiceSummary` enabled, scribe will generate a service summary when there no client to save the last pending ops and checkpoint states. However, this can cause it to conflict if a new client joins and start summarizing, causing SummaryNack from mismatch parents. This is impacting e2e test targeting t9s, so for now, disable it in t9s to stabilize the test. [AB#1627](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/1627) is the follow up issue. Pending build/publish a new tinylicious and update dependency before reenable the first for [AB#1454](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/1454)
Need to update tinylicious dependencies to non-release version before we can publish. So use the opportunity to just update to the latest released versions.
* Add e2e test to demo use of flush mode * override flush mode for azure clients * disable new test for local driver * PR feedback
This was referenced Nov 5, 2022
This was referenced Nov 5, 2022
This was referenced Nov 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: build
Build related issues
area: dds
Issues related to distributed data structures
area: framework
Framework is a tag for issues involving the developer framework. Eg Aqueduct
area: runtime
Runtime related issues
area: server
Server related issues (routerlicious)
area: tests
Tests to add, test infrastructure improvements, etc
base: next
PRs targeted against next branch
community-contribution
dependencies
Pull requests that update a dependency file
do-not-squash-merge
main-next-integrate
public api change
Changes to a public API
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.
Main-next integrate PR
The aim of this pull request is to sync main and next branch. The expectation from the assignee is as follows:
For more information about how to resolve merge conflicts and CI failures, visit [this wiki page]
(https://github.com/microsoft/FluidFramework/wiki/Main-next-Automation).