You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently added the permissions monitor to most of the CI jobs in the smithy-lang/smithy-rs repo in smithy-lang/smithy-rs#4084. This led to a substantial increase in checkout times. For the (admittedly huge) awslabs/aws-sdk-rust repo this led to both an increase in time and frequent failures. For the two repos we checkout the time diffs were:
smithy-lang/smithy-rs: ~6s -> ~2 minutes
awslabs/aws-sdk-rust: ~2 minutes -> ~1 hour
Checking out the aws-sdk-rust repo would often fail (example run) with the following error:
/usr/bin/git -c protocol.version=2 fetch --prune --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/*
Error: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
Error: fatal: expected 'packfile'
Error: The process '/usr/bin/git' failed with exit code 128
Potentially I could have gotten around this by moving the monitor action after the checkout actions, but the documentation for the monitor specifically says:
Include the Monitor action in every job of your workflow. The actions should be the first step in the job, even before the checkout action.
The text was updated successfully, but these errors were encountered:
Thank you for you report, I wasn't aware of that. I know that installing the monitor takes time and this is a potential overhead for every run. But a significant overhead once the proxy is running is not expected. This needs to be investigated.
Regarding the documentation, you can install it after checkout. It will miss then the needed contents: read for private repositories, but for public repositories the permission is not needed.
I will note that it took the permissions monitor longer to start up on the beta version. ~1 minute vs ~30 seconds in previous runs. But that is a small price to pay for getting back the checkout times.
I recently added the permissions monitor to most of the CI jobs in the smithy-lang/smithy-rs repo in smithy-lang/smithy-rs#4084. This led to a substantial increase in checkout times. For the (admittedly huge)
awslabs/aws-sdk-rust
repo this led to both an increase in time and frequent failures. For the two repos we checkout the time diffs were:smithy-lang/smithy-rs
: ~6s -> ~2 minutesawslabs/aws-sdk-rust
: ~2 minutes -> ~1 hourChecking out the
aws-sdk-rust
repo would often fail (example run) with the following error:Removing the permissions monitor in smithy-lang/smithy-rs#4088 took the checkout times back to normal.
Potentially I could have gotten around this by moving the monitor action after the checkout actions, but the documentation for the monitor specifically says:
The text was updated successfully, but these errors were encountered: