[client] Fix prioritization of requested Oauth scopes #2575
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
31s
checks
/
readme-snippets
13s
Matrix: checks / test
Annotations
1 error, 31 warnings, and 8 notices
checks / test (3.11, lowest-direct, windows-latest)
Process completed with exit code 1.
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Cz6yaAAAAAC0ndR4wF0ZRJuntR401cvSQkwyQUEyMDMwMTA5MDE3AEVkZ2U=
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Lj6yaAAAAAC/PL+vCNc6R7Fu+rdHxeXOQkwyQUEyMDMwMTA5MDE3AEVkZ2U=
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QT6yaAAAAADxV+5zDkbOTa0qSMenUGRmRE0yRURHRTA5MTcARWRnZQ==
|
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QT6yaAAAAADIYUYEUeumQIZAzgxh14ScRE0yRURHRTEwMTQARWRnZQ==
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Qz6yaAAAAACEPxsGTF8uRIc99jei0RUoQ0hJMzBFREdFMDQxMgBFZGdl
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, highest, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Qz6yaAAAAAAhWjd/ZoV3TJb4Nhz7phORQ0hJMzBFREdFMDMxMgBFZGdl
|
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, highest, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0TD6yaAAAAAA7uVeFBGHISrtxiG9FV3+ZUEhYMzFFREdFMDIwOABFZGdl
|
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, highest, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Sz6yaAAAAABlLcrXB/NzToyb79I+nr17UEhYMzFFREdFMDUwOABFZGdl
|
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Yz6yaAAAAADj6fFYUYylQbx/xNn/NDFSUEFPRURHRTA2MTAARWRnZQ==
|
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, highest, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Zj6yaAAAAADk36Gb60OnT5jWToGcBmzhQlkzRURHRTA1MTAARWRnZQ==
|
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, highest, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0aD6yaAAAAACvsbzwp6zESaSvTFbMMmB2QkwyQUEyMDMwMTA5MDI1AEVkZ2U=
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0bD6yaAAAAAD2/cpDJlNzRJv2xM9NYC+MQkwyQUEyMDMwMTA2MDUzAEVkZ2U=
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, highest, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0bD6yaAAAAAAd4PwjkjsETq8zxKPjsH/FQkwyQUEyMDMwMTA4MDExAEVkZ2U=
|
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dj6yaAAAAAC/H1xOYUxfTpZkHHN0BaFvQkwyQUEyMDMwMTA4MDI3AEVkZ2U=
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0lz6yaAAAAAAURApwf5BRS4verZCaGCNiUEhYMzFFREdFMDIxMQBFZGdl
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, lowest-direct, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.10, highest, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.11, highest, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.13, highest, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.13, lowest-direct, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.12, highest, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.12, lowest-direct, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
checks / test (3.10, lowest-direct, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|