Skip to content

Conversation

@dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from main into main-vs-deps.

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-main-vs-deps
git reset --hard upstream/main-vs-deps
git merge upstream/main
# Fix merge conflicts
git commit
git push upstream merges/main-to-main-vs-deps --force

chsienki and others added 2 commits June 21, 2022 10:06
…-cleanups"

This reverts commit 1c13b39, reversing
changes made to ff8175f.
Revert "Merge pull request #61669 from jasonmalinowski/log-aggregator…
@dotnet-bot dotnet-bot requested a review from a team as a code owner June 24, 2022 16:49
@dotnet-bot dotnet-bot added Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch. labels Jun 24, 2022
@dotnet-bot
Copy link
Collaborator Author

⚠ This PR has merge conflicts. @RikkiGibson

@dotnet-bot dotnet-bot enabled auto-merge June 24, 2022 16:49
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Auto-approval

@JoeRobich JoeRobich removed the Merge Conflicts There are merge conflicts with the base branch. label Jun 24, 2022
@RikkiGibson
Copy link
Member

Tagging @jasonmalinowski for assistance reverting this change

@JoeRobich JoeRobich force-pushed the merges/main-to-main-vs-deps branch from bc2d6c6 to cec4193 Compare June 24, 2022 18:37
var itemList = session.CreateCompletionList(SortCompletionitems(data, cancellationToken));

AsyncCompletionLogger.LogItemManagerSortTicksDataPoint(stopwatch.Elapsed);
AsyncCompletionLogger.LogItemManagerSortTicksDataPoint((int)stopwatch.Elapsed.TotalMilliseconds);
Copy link
Member

Choose a reason for hiding this comment

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

This is where I had goofed and didn't convert the code back to using TotalMilliseconds

Copy link
Member

Choose a reason for hiding this comment

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

Yep that fix is correct.

@RikkiGibson RikkiGibson disabled auto-merge June 24, 2022 21:29
@RikkiGibson RikkiGibson merged commit 0bbbbeb into main-vs-deps Jun 24, 2022
@ghost ghost added this to the Next milestone Jun 24, 2022
@RikkiGibson RikkiGibson deleted the merges/main-to-main-vs-deps branch June 24, 2022 23:32
@RikkiGibson RikkiGibson modified the milestones: Next, 17.3 P3 Jun 28, 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.

6 participants