Skip to content

Merge main-vs-deps to release/dev17.3#60314

Merged
dotnet-bot merged 113 commits intorelease/dev17.3from
merges/main-vs-deps-to-release/dev17.3
Mar 27, 2022
Merged

Merge main-vs-deps to release/dev17.3#60314
dotnet-bot merged 113 commits intorelease/dev17.3from
merges/main-vs-deps-to-release/dev17.3

Conversation

@dotnet-bot
Copy link
Copy Markdown
Collaborator

This is an automatically generated pull request from main-vs-deps into release/dev17.3.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout -t upstream/merges/main-vs-deps-to-release/dev17.3
git reset --hard upstream/release/dev17.3
git merge upstream/main-vs-deps
# Fix merge conflicts
git commit
git push upstream merges/main-vs-deps-to-release/dev17.3 --force

sharwell and others added 30 commits January 14, 2022 15:29
Even if it might be stale. the completion list would be computed with cached data and cache refresh would be done in background.
Even if it might be stale. the completion list would be computed with cached data and cache refresh would be done in background.
This can be used to tweak test behavior to make it deterministic
…ionOptions.cs

Co-authored-by: Sam Harwell <sam@tunnelvisionlabs.com>
CyrusNajmabadi and others added 12 commits March 23, 2022 10:26
Fix issue when multiple different diagnostics share a single fixer
* Fix our x86 test execution

The transition to `dotnet test` seems to have broken our unit tests that
depend on executing on an x86 architecture. This fixes that by using the
`--arch` argument to the `dotnet test` execution.

This was made more general to facilitate our future arm64 work in this
area

* Disable test failing on x64

* fix the test

* Apply suggestions from code review

Co-authored-by: Sam Harwell <sam@tunnelvisionlabs.com>

* Disable test on spanish

* Test fixes

Co-authored-by: Sam Harwell <sam@tunnelvisionlabs.com>
Add analyzer/fixer that notifies people about explicit (but hidden) casts the compiler generates for foreach-statements.
This was being resized constantly after opening Orchard Core, allocating about 2 GB. The fact that is being called this many times appears to be another bug that I'm following up on.
Co-authored-by: Youssef Victor <youssefvictor00@gmail.com>
Create solution on the main thread in integration tests
@dotnet-bot dotnet-bot requested a review from a team as a code owner March 24, 2022 23:57
@allisonchou allisonchou removed the Merge Conflicts There are merge conflicts with the base branch. label Mar 25, 2022
@dotnet-bot dotnet-bot merged commit 09f6d30 into release/dev17.3 Mar 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.