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

Snap for 17.12 P3 #10933

Merged
merged 304 commits into from
Sep 27, 2024
Merged

Conversation

akhera99
Copy link
Member

merge main into release/dev17.12 to update for 17.12 P3. Main is 17.13 P1.

davidwengier and others added 30 commits August 20, 2024 11:01
This commit is just moves, no functionality changes. Minor tweaks to method visibility, and one rename of a static field :)
This probably looks like overkill, but hopefully the next commit will help explain a little about what is going on.
…rsionedDocumentSnapshots

# Conflicts:
#	src/Razor/src/Microsoft.CodeAnalysis.Remote.Razor/ProjectSystem/DocumentContextExtensions.cs
…820.6

Microsoft.SourceBuild.Intermediate.arcade , Microsoft.DotNet.Arcade.Sdk
 From Version 9.0.0-beta.24416.2 -> To Version 9.0.0-beta.24420.6
…ence-packages build 20240819.1

Microsoft.SourceBuild.Intermediate.source-build-reference-packages
 From Version 10.0.0-alpha.1.24415.3 -> To Version 10.0.0-alpha.1.24419.1
…821.2

Microsoft.SourceBuild.Intermediate.arcade , Microsoft.DotNet.Arcade.Sdk
 From Version 9.0.0-beta.24420.6 -> To Version 9.0.0-beta.24421.2
Always felt like a huge potential bug farm. eg, if Html ended up not being first we'd have bugs, working out the Order property (which was weirdly backwards?) was a pain, and the entire formatting engine produces horrible results if the ordering changes anyway.
Doing this separately, and purely mechanically, so make review easier
This was only used for validation as edits pass through the pipeline, but since we now tightly control the pipeline its unnecessary
…821.7

Microsoft.SourceBuild.Intermediate.arcade , Microsoft.DotNet.Arcade.Sdk
 From Version 9.0.0-beta.24421.2 -> To Version 9.0.0-beta.24421.7
davidwengier and others added 22 commits September 19, 2024 08:08
These broke due to Razor comment formatting changes, so just updating
the expected output.
* Delete V2 page directive

* Update inject tests to use real classification passes

* Update model tests to use real classification passes

* Delete duplicated model directives and passes

* Delete duplicated inject extensions, directives and nodes

* Delete duplicate inject target extension
- Update the MVC3 version to optionally not enforce nullability to keep code gen identical

* Remove duplicated taghelper extension methods and metadata

* Remove duplicated diagnostic factories

* Delete duplicated tag helper extensions and intermediate node types

* Delete duplicated component types

* Delete duplicated ViewComponentTypeVisitor

* Delete duplicated viewcomponment taghelper passes
Fixes dotnet#10736

Chris did a good breakdown of what this value is used for dotnet#10736 (comment)
…ence-packages build 20240917.1

Microsoft.SourceBuild.Intermediate.source-build-reference-packages
 From Version 10.0.0-alpha.1.24459.1 -> To Version 10.0.0-alpha.1.24467.1
* Add tests
* Emit the attribute in runtime code, even if it has errors
* Update test baseline
dotnet#10910)

This pull request updates the following dependencies

[marker]: <> (Begin:011df26a-fbd1-45b0-94b9-08db3601dcca)
## From https://github.com/dotnet/source-build-reference-packages
- **Subscription**: 011df26a-fbd1-45b0-94b9-08db3601dcca
- **Build**: 20240917.1
- **Date Produced**: September 17, 2024 2:02:23 PM UTC
- **Commit**: 38a050f3b80b4dfdd0e8f6c772a3e9835674d3b4
- **Branch**: refs/heads/main

[DependencyUpdate]: <> (Begin)

- **Updates**:
-
**Microsoft.SourceBuild.Intermediate.source-build-reference-packages**:
[from 10.0.0-alpha.1.24459.1 to 10.0.0-alpha.1.24467.1][1]

[1]:
dotnet/source-build-reference-packages@08649fe...38a050f

[DependencyUpdate]: <> (End)


[marker]: <> (End:011df26a-fbd1-45b0-94b9-08db3601dcca)
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:
- https://github.com/dotnet/razor/find/release/dev17.12
- https://github.com/dotnet/razor/find/main

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.
``` bash
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
```
* Add test
* Change how we parse runtime whitespace for using directives
* Update added test
* Update baselines
* Update parsing doc
@akhera99 akhera99 requested review from a team as code owners September 27, 2024 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.