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 #11769
Automation: Main Next Integrate #11769
Conversation
#11686) `@fluidframework/counter` is now promoted more directly on our website, including its API docs. This PR is aimed at cleaning up those docs for public consumption. Mostly simple typo fixes and capitalization/punctuation improvements. But it also moves `SharedCounter`'s summary docs away from using embedded Markdown syntax (which is not supported) toward using `@example` tag syntax for its flow examples.
Fix AB 1633 Summary Upload Error
…ors (Some batching improvements part 2) (#11579) This used to be driven by two asserts (0x170 and 0x16f) but the change makes the situation more explicit by closing the container and not relying on the exception handler of who's using the PendingStateManager. And also adds more information to the error.
|
"Actively working on it" |
|
Conflict is in packages/runtime/container-runtime/src/test/pendingStateManager.spec.ts . Looks like @andre4i would be the best contact for resolving it. |
|
Also, the failed |
|
Working on the test failures. Will update the branch accordingly. |
|
PR checks passed. merging it. thanks @CraigMacomber, @andre4i, @alexvy86!! |
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).