Skip to content

Conversation

@dotnet-maestro-bot
Copy link
Contributor

I detected changes in the release/7.0 branch which have not been merged yet to release/7.0-staging. I'm a robot and am configured to help you automatically keep release/7.0-staging up to date, so I've opened this PR.

This PR merges commits made on release/7.0 by the following committers:

  • carlossanlop
  • vseanreesermsft
  • dotnet-maestro[bot]
  • dotnet-bot
  • ManickaP

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

merge button instructions

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/7.0
git pull --ff-only
git checkout release/7.0-staging
git pull --ff-only
git merge --no-ff release/7.0

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git push [email protected]:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0-to-release/7.0-staging'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull https://github.com/dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull [email protected]:dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

dotnet-bot and others added 9 commits July 6, 2023 04:01
**Description:**
Prevent clients from overcoming defined stream limits by sending already closed streams.
MSRC 79848  - Quic and Kestrel ASP.NET Kestrel stream flow control issue causing leak

**Risk:**
Low: the fix postpones releasing stream capacity after the stream is released from memory.

**Validation:**
Added test simulating the repro case.

**Impacted assemblies:**
System.Net.Quic.dll
msquic.dll - native, part of Windows runtime
* Update dependencies from https://github.com/dotnet/xharness build 20230621.1

Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
 From Version 7.0.0-prerelease.23309.1 -> To Version 7.0.0-prerelease.23321.1

* Remove unnecessary spacing from conflict merge

---------

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <[email protected]>
….0-2023-08-08-1042

Merging internal commits for release/7.0
@dotnet-maestro-bot dotnet-maestro-bot force-pushed the merge/release/7.0-to-release/7.0-staging branch from fd26be1 to a2ad4f0 Compare August 8, 2023 20:30
@ghost
Copy link

ghost commented Aug 8, 2023

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

I detected changes in the release/7.0 branch which have not been merged yet to release/7.0-staging. I'm a robot and am configured to help you automatically keep release/7.0-staging up to date, so I've opened this PR.

This PR merges commits made on release/7.0 by the following committers:

  • carlossanlop
  • vseanreesermsft
  • dotnet-maestro[bot]
  • dotnet-bot
  • ManickaP

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

merge button instructions

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/7.0
git pull --ff-only
git checkout release/7.0-staging
git pull --ff-only
git merge --no-ff release/7.0

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git push [email protected]:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0-to-release/7.0-staging'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull https://github.com/dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull [email protected]:dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

Author: dotnet-maestro-bot
Assignees: -
Labels:

area-Infrastructure-libraries

Milestone: -

@carlossanlop carlossanlop added Servicing-approved Approved for servicing release area-codeflow for labeling automated codeflow and removed area-Infrastructure-libraries labels Aug 8, 2023
@carlossanlop carlossanlop added this to the 7.0.x milestone Aug 8, 2023
Copy link
Contributor

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge commit!

@carlossanlop carlossanlop merged commit 09a0d63 into dotnet:release/7.0-staging Aug 9, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Sep 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-codeflow for labeling automated codeflow Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants