Merge main to feature/lsp #18223
Open
Merge main to feature/lsp #18223
+759
−352
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
…ase/dev17.13 Merge release/dev17.12 to release/dev17.13
Merge main to release/dev17.13
… Build ID 2555417 (#17854)
Merge main to release/dev17.13
Merge main to release/dev17.13
…ase/dev17.13 Merge release/dev17.12 to release/dev17.13
Merge main to release/dev17.13
Merge main to release/dev17.13
Merge main to release/dev17.13
Merge main to release/dev17.13
Merge main to release/dev17.13
…ase/dev17.13 Merge release/dev17.12 to release/dev17.13
Merge main to release/dev17.13
… Build ID 2567162 (#17912) * Localized file check-in by OneLocBuild Task: Build definition ID 499: Build ID 2567162 * Localized file check-in by OneLocBuild Task: Build definition ID 499: Build ID 2567162
Merge main to release/dev17.13
Merge main to release/dev17.13
* Backport :: Bugfix :: Support `ldelem.u8`, `ldelem.u` opcode aliases (#18081) (#18096) * Streamlining test deps a bit (#18022) * Streamlining test deps a bit * up * Format ILVerify output a bit (#18120) * fix for race condition in FileIndex.fileIndexOfFile (#18008) * fix for race condition in FileIndex.fileIndexOfFile * fantomas * fixed ilverify baselines (just a single line number changed) * add release notes entry * FileToIndex: Added unlocked read so that lock is entered for new files only * update ilverify baselines (changed line numbers only) * Fix ILVerify --------- Co-authored-by: Petr <[email protected]> Co-authored-by: Vlad Zarytovskii <[email protected]> * Update F# build version to 200 * Fix how much is trimmed from an interp string part (#18123) * Fix how much is trimmed from an interp string part Only trim last 2 characters if they are "%s" and the '%' is not escaped * Add release note --------- Co-authored-by: Adam Boniecki <[email protected]> * Sink: report SynPat.ArrayOrList type (#18127) --------- Co-authored-by: Tomas Grosup <[email protected]> Co-authored-by: Petr <[email protected]> Co-authored-by: Martin <[email protected]> Co-authored-by: Vlad Zarytovskii <[email protected]> Co-authored-by: Adam Boniecki <[email protected]> Co-authored-by: Adam Boniecki <[email protected]> Co-authored-by: Alex Berezhnykh <[email protected]> Co-authored-by: Kevin Ransom (msft) <[email protected]>
Merge main to release/dev17.13
Merge main to release/dev17.13
Merge main to release/dev17.13
Merge main to release/dev17.13
Merge main to 17.13
Merge release/dev17.13 to main
* fix AsyncLazy cancellation * baselines
|
⚠ This PR has merge conflicts. @0101 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an automatically generated pull request from main into feature/lsp.
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-to-feature/lsp git reset --hard upstream/feature/lsp git merge upstream/main # Fix merge conflicts git commit git push upstream merges/main-to-feature/lsp --force