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

[dnceng-bot] Branch runtime/main can't be mirrored to Azdo fast forward branch #104021

Closed
dotnet-maestro-bot opened this issue Jun 26, 2024 · 6 comments

Comments

@dotnet-maestro-bot
Copy link
Contributor

Branch main in dotnet/runtime repo can't be mirrored from GitHub to Azure DevOps main via fast forward.
There was unexpected error during the mirroring process.

unpacking the sent packfile failed on the remote
this tool can't detect it, but typical reason is
VS403654: The push was rejected because it contains one or more secrets.

Problem need to be resolved to unblock the code flow.

You can troubleshoot the issue by:

  • checking the logs of the mirroring process in the mirroring pipeline.
  • by trying to mirror the branch manually
  • you can disable the mirroring of the branch in the configuration file.
  • you can ask @dotnet/dnceng for help or read the documentation.
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jun 26, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jun 26, 2024
@akoeplinger akoeplinger added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jun 26, 2024
@MichalStrehovsky
Copy link
Member

This is complaining about files touched in d4fe4a7. Cc @bartonjs

commit: d4fe4a7e987584bfa4904dd1027a873029b2005d
paths: 
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2710,1-26) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2723,1-26) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2745,1-29) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2752,1-30) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2802,1-26) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2881,1-30) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(2964,1-26) : SEC101/013 : PemPrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(57,149-13) : SEC101/055 : Pkcs12PrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(1476,41-55) : SEC101/055 : Pkcs12PrivateKey
/src/libraries/Common/tests/System/Security/Cryptography/X509Certificates/TestData.cs(3443,13-26) : SEC101/055 : Pkcs12PrivateKey)
error: failed to push some refs to 'https://dev.azure.com/dnceng/internal/_git/dotnet-runtime'

Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@akoeplinger
Copy link
Member

I think we just need to update

"src/libraries/System.Security.Cryptography/tests/X509Certificates/TestData.cs",

@jkoritzinsky
Copy link
Member

You'll also need to push a "credscan ignore push" commit as CredScan won't let you push any commits containing credentials, even if later commits suppress it.

@bartonjs
Copy link
Member

If I understand the logs, this is fixed now. But, in case I don't understand the logs, I'm not pushing the close button.

@akoeplinger
Copy link
Member

Yes this is fixed now.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Jun 26, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants