The failure log, reachable either through 1) "Insights -> Dependency Graph" and then a "Dependabot" tab or 2) through an action in the "Actions" tab, ends with:
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Process PID: 1373 completed with status: pid 1373 exit 0
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Total execution time: 0.0 seconds
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Started process PID: 1380 with command: {} git config --global --add url.https://github.com/.insteadOf git@github.com/ {}
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Process PID: 1380 completed with status: pid 1380 exit 0
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Total execution time: 0.0 seconds
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Started process PID: 1387 with command: {} git config --global --add url.https://github.com/.insteadOf git://github.com/ {}
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Process PID: 1387 completed with status: pid 1387 exit 0
updater | 2025/07/16 23:43:52 INFO <job_1054618980> Total execution time: 0.0 seconds
updater | /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation_2_7.rb:108:in 'UnboundMethod#bind_call': stack level too deep (SystemStackError)
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation_2_7.rb:108:in 'block in Dependabot::DependabotError#create_validator_method_fast1'
from /home/dependabot/common/lib/dependabot/errors.rb:405:in 'Dependabot::DependabotError#sanitize_message'
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation_2_7.rb:968:in 'UnboundMethod#bind_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation_2_7.rb:968:in 'block in Dependabot::DependabotError#create_validator_method_medium1'
from /home/dependabot/common/lib/dependabot/errors.rb:391:in 'Dependabot::DependabotError#initialize'
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation.rb:179:in 'UnboundMethod#bind_call'
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation.rb:179:in 'T::Private::Methods::CallValidation.validate_call_skip_block_type'
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/sorbet-runtime-0.5.11952/lib/types/private/methods/call_validation.rb:121:in 'block in Dependabot::DependabotError#create_validator_slow_skip_block_type'
... 9348 levels...
from /home/dependabot/dependabot-updater/vendor/ruby/3.4.0/gems/opentelemetry-api-1.5.0/lib/opentelemetry/trace/tracer.rb:37:in 'OpenTelemetry::Trace::Tracer#in_span'
from /home/dependabot/dependabot-updater/lib/dependabot/file_fetcher_command.rb:22:in 'Dependabot::FileFetcherCommand#perform_job'
from /home/dependabot/dependabot-updater/lib/dependabot/base_command.rb:37:in 'Dependabot::BaseCommand#run'
from bin/fetch_files.rb:35:in '<main>'
Failure running container 5d5681d4e399746e2278469748f38feb09c6163dff92e54cfd05b13f9a3df101: Error: Command failed with exit code 1: /bin/sh -c $DEPENDABOT_HOME/dependabot-updater/bin/run fetch_files
Cleaned up container 5d5681d4e399746e2278469748f38feb09c6163dff92e54cfd05b13f9a3df101
proxy | 2025/07/16 23:43:54 0/3 calls cached (0%)
2025/07/16 23:43:54 Posting metrics to remote API endpoint
Error: Dependabot encountered an error performing the update
Error: The updater encountered one or more errors.
For more information see: https://github.com/eisop/jspecify-reference-checker/network/updates/1054618980 (write access to the repository is required to view the log)
🤖 ~ finished: error reported to Dependabot ~
The top-level summary is:
Security update 1054618980
Errored with the message "Dependabot encountered an unknown error"
No PRs affected 33 minutes ago view logs
In 68d9e8f I tried disabling the "usage-demo" sub-project (which depends on the root project and might cause this cycle?), but that didn't fix the issue.
The failure log, reachable either through 1) "Insights -> Dependency Graph" and then a "Dependabot" tab or 2) through an action in the "Actions" tab, ends with:
The top-level summary is:
In 68d9e8f I tried disabling the "usage-demo" sub-project (which depends on the root project and might cause this cycle?), but that didn't fix the issue.