Skip to content

Conversation

@dotnet-bot
Copy link
Contributor

This is an automatically generated pull request from release/dev17.12 into main.

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/release/dev17.12-to-main
git reset --hard upstream/main
git merge upstream/release/dev17.12
# Fix merge conflicts
git commit
git push upstream merges/release/dev17.12-to-main --force

davidwengier and others added 5 commits August 28, 2024 16:59
Fixes #10759

Initially when investigating this I was digging into buffer versions and
race conditions, but now that the editor fix is in, and we are self
versioned, the bug stood out much more obviously: A character offset was
being passed in to a parameter that expected a length 🤦‍♂️

Sadly none of the `RazorCustomMessageTarget` code is testable. Cohosting
will make this trivial though, as we would simply create a new
`Document` with the provisional change, and drop it on the floor when
we're finished.
* Change UseConsolidatedMvcViews to default to true
* Update baselines
* Update LSP test
Fixes integration test failures in Find All References.

Roslyns LSP types got much more spec compliant in
dotnet/roslyn#73911 and we were never sending
the `Context` property in our request, so deserialization failed on
their end.
@dotnet-bot dotnet-bot requested review from a team as code owners August 28, 2024 18:03
@dotnet-bot dotnet-bot added area-infrastructure auto-merge Squash merge once all PR checks are complete and reviewers have approved labels Aug 28, 2024
@dotnet-bot dotnet-bot enabled auto-merge August 28, 2024 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-infrastructure auto-merge Squash merge once all PR checks are complete and reviewers have approved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants