Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge release/dev17.5 to release/dev17.6 #8360

Merged
11 commits merged into from
Mar 1, 2023

Conversation

dotnet-bot
Copy link
Contributor

This is an automatically generated pull request from release/dev17.5 into release/dev17.6.

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

allisonchou and others added 10 commits December 2, 2022 11:53
[Infra] Bring `release/dev17.5` branch up to date
Include Compiler features in Project Engine
Due to the way we decided to implement bind get,set,after, customers can run into situations where their components render many more times than expected, which results in confusion and performance degradation.

This was due to the fact that we chose to rely on EventCallback to implement this feature and we did not realize there were some side effects associated with it.

The APIs we are adding bypass the whole EventCallback infrastructure (simplifying the implementation too) and fix the issue.

This change updates the compiler to rely on the new runtime APIs

(cherry picked from commit 9ce52f1afbfb819fc8499a590385200b97b13f33)

Co-authored-by: Javier Calvarro Nelson <[email protected]>
* Add a test

* Visit assemblies in search for view components
@dotnet-bot dotnet-bot requested review from a team as code owners March 1, 2023 15:02
@dotnet-bot dotnet-bot added area-infrastructure auto-merge Squash merge once all PR checks are complete and reviewers have approved Merge Conflicts labels Mar 1, 2023
@dotnet-bot
Copy link
Contributor Author

⚠ This PR has merge conflicts. @davidwengier @Cosifne

@ghost
Copy link

ghost commented Mar 1, 2023

Hello @dotnet-bot!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 12 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@jjonescz
Copy link
Member

jjonescz commented Mar 1, 2023

This has already been merged (twice)

And then closed in #8359.

But the bot keeps creating the same PR for some reason...

But maybe I merged it wrong. Will try again.

@ghost ghost merged commit 62594a3 into release/dev17.6 Mar 1, 2023
@ghost ghost deleted the merges/release/dev17.5-to-release/dev17.6 branch March 1, 2023 16:28
@davidwengier
Copy link
Contributor

Weird, I just found one of these PRs and resolved the conflicts too. Didn't realise it was the 3rd or 4th one! Hopefully it doesn't reappear again

This pull request was closed.
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 Merge Conflicts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants