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

Automation: Main Next Integrate #11696

Merged

Conversation

github-actions[bot]
Copy link
Contributor

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:

  • Acknowledge the pull request by adding a comment -- "Actively working on it".
  • Resolve any merge conflicts between this branch and next (and push the resolution to this branch). Merge next into this branch if needed. Do NOT rebase or squash this branch: its history must be preserved.
  • Ensure CI is passing for this PR, fixing any issues. Please don't look into resolving Real service e2e test and Stress test failures as they are non-required CI failures.
  • Once the PR is ready for merge, please add a comment @mentioning the reviewers to get this PR merged in. Thank you!!

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).

tyler-cai-microsoft and others added 6 commits August 25, 2022 16:41
* 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
@github-actions github-actions bot added area: dds Issues related to distributed data structures area: dds: propertydds area: server Server related issues (routerlicious) public api change Changes to a public API base: next PRs targeted against next branch labels Aug 29, 2022
@msfluid-bot
Copy link
Collaborator

@fluid-example/bundle-size-tests: +15.29 KB
Metric NameBaseline SizeCompare SizeSize Diff
aqueduct.js 392.45 KB 393.64 KB +1.2 KB
connectionState.js 680 Bytes 680 Bytes No change
containerRuntime.js 191.92 KB 196.36 KB +4.44 KB
loader.js 151.12 KB 151.06 KB -57 Bytes
map.js 42.63 KB 47.38 KB +4.75 KB
matrix.js 131.63 KB 134.98 KB +3.35 KB
odspDriver.js 150.23 KB 150.11 KB -127 Bytes
odspPrefetchSnapshot.js 38.39 KB 38.35 KB -41 Bytes
sharedString.js 152.42 KB 154.2 KB +1.77 KB
Total Size 1.25 MB 1.27 MB +15.29 KB

Baseline commit: b32d301

Generated by 🚫 dangerJS against 30e7808

@sonalivdeshpande sonalivdeshpande merged commit c146454 into next Aug 30, 2022
@sonalivdeshpande sonalivdeshpande deleted the main-next-eebd39d52fb612214f6d91b83ffd229c8c016300 branch August 30, 2022 02:35
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants