-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Enable runtime closure verification #41698
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
Merged
NikolaMilosavljevic
merged 8 commits into
dotnet:master
from
NikolaMilosavljevic:verify.closure
Sep 3, 2020
Merged
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
65656e7
Enable closure validation
NikolaMilosavljevic 58cf696
Ensure dependency graph directory exists
NikolaMilosavljevic d4395af
Netstandard should not be ignored
NikolaMilosavljevic 7a42449
Ensure Reports dir exists; VerifyClosure change moved to Arcade
NikolaMilosavljevic d184666
Merge branch 'verify.closure' of https://github.com/nikolamilosavljev…
NikolaMilosavljevic 52d24f5
Upgrade SharedFramework.SDK package to pick up a change for VerifyClo…
NikolaMilosavljevic 2df9482
Merge branch 'master' into verify.closure
NikolaMilosavljevic 47aeaf8
Merge branch 'master' into verify.closure
NikolaMilosavljevic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is just temporary rather than forking the whole thing, just have a single target:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually need to override the target to update it's condition as well, to run if new property is set -
ShouldVerifyClosure. CurrentlyVerifyClosureonly runs ifSkipValidatePackageis false: https://github.com/dotnet/arcade/blob/e11b8486ad155fab13e788a268755c0ca60d3609/src/Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk/targets/framework.packaging.targets#L170There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we can’t get the arcade update instead? Would it take too long? Could you manually update just the package with this fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've heard that there is a freeze on whole Arcade update, but I'll ask if a single package would be allowed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heard back - we can get update in RC2. I will update
VerifyClosuretarget inMicrosoft.DotNet.Build.Tasks.SharedFramework.Sdkin Arcade, and remove the target override from my PR. But, I will pick your suggestion for a new target to createReportsdirectory, which works around an issue inVerifyClosuretask: dotnet/arcade#6090. The task is in a different Arcade package and they want to minimize the number of changes now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ericstj I will also move your suggested new target into Arcade next to VerifyClosure target. We can, then, remove this target when VerifyClosure task is fixed - with a single PR in Arcade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will keep
EnsureDepenedencyGraphDirin runtime repo -PackageReportDiris runtime-specific property, it doesn't make sense for this to be in Arcade.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arcade fix is in: dotnet/arcade#6101
This (runtime) fix can be merged and closure validation would start working once we pick up new
Microsoft.DotNet.Build.Tasks.SharedFramework.Sdkpackage.@ericstj @jkoritzinsky this is safe to merge once you approve the changes.