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 #11696
Merged
sonalivdeshpande
merged 7 commits into
next
from
main-next-eebd39d52fb612214f6d91b83ffd229c8c016300
Aug 30, 2022
Merged
Automation: Main Next Integrate #11696
sonalivdeshpande
merged 7 commits into
next
from
main-next-eebd39d52fb612214f6d91b83ffd229c8c016300
Aug 30, 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
* Update fluid-fetch documentation
…#11652) The tinylicious tests infrequently but consistently fail with 502 error code. The node (Axios) server socket timeout is 15s, whereas the underlying socket closes by default after 5s of inactivity. This PR switches to using agentkeepalive package to force the Node server to understand and close connections idle sockets after 4 seconds so that Node doesn't try to use an already closed socket.
The solutions to this type checking issue come with their own issues so it was decided to keep things in their current state and work towards keeping JsonableTree out of public APIs as well as rely on testing to catch these issues.
* Print errors at the end of the memory tests * Consolidate log statements
…y-inspector-table (#11569)
⯅ @fluid-example/bundle-size-tests: +15.29 KB
Baseline commit: b32d301 |
sonalivdeshpande
approved these changes
Aug 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: dds: propertydds
area: dds
Issues related to distributed data structures
area: server
Server related issues (routerlicious)
base: next
PRs targeted against next branch
community-contribution
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).