-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Expose all references when not restoring #32718
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
Conversation
src/SignalR/common/SignalR.Common/src/Microsoft.AspNetCore.SignalR.Common.csproj
Outdated
Show resolved
Hide resolved
src/SignalR/common/SignalR.Common/src/Microsoft.AspNetCore.SignalR.Common.csproj
Outdated
Show resolved
Hide resolved
1b7248d to
ac705ab
Compare
src/SignalR/common/SignalR.Common/src/Microsoft.AspNetCore.SignalR.Common.csproj
Outdated
Show resolved
Hide resolved
- use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph
- should now be part of the dependency graph automatically
- not a problem unless executing `restore` target
d09a27a to
82a5289
Compare
|
/backport to release/3.1 |
|
Started backporting to release/3.1: https://github.com/dotnet/aspnetcore/actions/runs/865552637 |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
/backport to release/5.0 |
|
Started backporting to release/5.0: https://github.com/dotnet/aspnetcore/actions/runs/865553258 |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
@dougbu an error occurred while backporting to release/3.1, please check the run log for details! Cannot read property 'createComment' of undefined |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
@dougbu an error occurred while backporting to release/5.0, please check the run log for details! Cannot read property 'createComment' of undefined |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
Started backporting to release/3.1: https://github.com/dotnet/aspnetcore/actions/runs/865552637 |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
@dougbu an error occurred while backporting to release/3.1, please check the run log for details! Cannot read property 'createComment' of undefined |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
@akoeplinger something strange is going on. The action is failing even after removing differences between this repo and dotnet/runtime in .github/workflows/backport.yml and eng/actions/backport/*, See #32777 then #32927. I also verified https://octokit.github.io/rest.js/v18#issues-create-comment still matches what we're doing in this action. Any ideas why either the |
|
@akoeplinger I figured it out. Need to use the The other part of the issue here was conflicts when the action attempted to apply the patch. |
Oops, index.js already uses |
|
Let's try this again… |
|
/backport to release/5.0 |
|
Started backporting to release/5.0: https://github.com/dotnet/aspnetcore/actions/runs/872340045 |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
@dougbu backporting to release/5.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph
Using index info to reconstruct a base tree...
M src/DataProtection/DataProtection/src/Microsoft.AspNetCore.DataProtection.csproj
M src/Identity/Extensions.Core/src/Microsoft.Extensions.Identity.Core.csproj
M src/Logging.AzureAppServices/src/Microsoft.Extensions.Logging.AzureAppServices.csproj
M src/Servers/Connections.Abstractions/src/Microsoft.AspNetCore.Connections.Abstractions.csproj
M src/SignalR/clients/csharp/Http.Connections.Client/src/Microsoft.AspNetCore.Http.Connections.Client.csproj
M src/SignalR/common/Http.Connections.Common/src/Microsoft.AspNetCore.Http.Connections.Common.csproj
M src/SignalR/common/SignalR.Common/src/Microsoft.AspNetCore.SignalR.Common.csproj
M src/Testing/src/Microsoft.AspNetCore.Testing.csproj
M src/WebEncoders/src/Microsoft.Extensions.WebEncoders.csproj
Falling back to patching base and 3-way merge...
Auto-merging src/WebEncoders/src/Microsoft.Extensions.WebEncoders.csproj
Auto-merging src/Testing/src/Microsoft.AspNetCore.Testing.csproj
Auto-merging src/SignalR/common/SignalR.Common/src/Microsoft.AspNetCore.SignalR.Common.csproj
Auto-merging src/SignalR/common/Http.Connections.Common/src/Microsoft.AspNetCore.Http.Connections.Common.csproj
Auto-merging src/SignalR/clients/csharp/Http.Connections.Client/src/Microsoft.AspNetCore.Http.Connections.Client.csproj
Auto-merging src/Servers/Connections.Abstractions/src/Microsoft.AspNetCore.Connections.Abstractions.csproj
CONFLICT (content): Merge conflict in src/Servers/Connections.Abstractions/src/Microsoft.AspNetCore.Connections.Abstractions.csproj
Auto-merging src/Logging.AzureAppServices/src/Microsoft.Extensions.Logging.AzureAppServices.csproj
Auto-merging src/Identity/Extensions.Core/src/Microsoft.Extensions.Identity.Core.csproj
Auto-merging src/DataProtection/DataProtection/src/Microsoft.AspNetCore.DataProtection.csproj
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
|
Hi @github-actions[bot]. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
|
FYI - I think I just changed @msftbot to not comment when @github-actions[bot] comments on a closed PR. |
- backport of 0b0bed3 (#32718) * Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph * Remove extra direct references - should now be part of the dependency graph automatically * Avoid errors about non-shared Fx references - not a problem unless executing `restore` target * Special case source builds
- backport of 0b0bed3 (#32718) * Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph * Remove extra direct references - should now be part of the dependency graph automatically * Avoid errors about non-shared Fx references - not a problem unless executing `restore` target * Special case source builds
* [release/5.0] Expose all references when not restoring - backport of 0b0bed3 (#32718) * Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph * Remove extra direct references - should now be part of the dependency graph automatically * Avoid errors about non-shared Fx references - not a problem unless executing `restore` target * Special case source builds
- backport of 0b0bed3 (#32718) * Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph * Remove extra direct references - should now be part of the dependency graph automatically * Avoid errors about non-shared Fx references - not a problem unless executing `restore` target * Special case source builds
- backport of 0b0bed3 (#32718) * Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph * Remove extra direct references - should now be part of the dependency graph automatically * Avoid errors about non-shared Fx references - not a problem unless executing `restore` target * Special case source builds
* [release/3.1] Expose all references when not restoring - backport of 0b0bed3 (#32718) * Expose all references when not restoring - use empty `$(MSBuildRestoreSessionId)` to determine when contributing to dependency graph * Remove extra direct references - should now be part of the dependency graph automatically * Avoid errors about non-shared Fx references - not a problem unless executing `restore` target * Special case source builds * Add workaround for ref/ generation - use `$(CompileUsingReferenceAssemblies)` to avoid new references in generated projects * Limit `_CheckForReferenceBoundaries` to Core TFM - back-ports a very small part of 5266918 - avoid incorrect errors about extra references in shared framework - safe because every `$(IsAspNetCoreApp)` project targets (or multi-targets) `netcoreapp3.1` * Add more `$(MSBuildRestoreSessionId)` checks - additional projects in this branch have TFM-specific references * nit: Remove a few duplicate references - no need to mention Microsoft.AspNetCore.DataProtection twice * Remove excess assemblies from shared Fx - brought in due to improved reference discovery
use empty
$(MSBuildRestoreSessionId)to determine when contributing to dependency graphremove extra direct references