Dependabot PR creation problem

Following the most recent release of a go module, open-policy-agent/opa v0.30.0, I was hoping another project using it (opa-envoy-plugin) would see a dependabot upgrade PR.

I’ve been manually triggering the update check, and it reported as having failed. However, the logs don’t indicate what’s wrong, see The only weirdness I find is that there’s a 30 minute gap between the last log from proxy and the next timestamp from updater.

For a fuller picture, another project (conftest) has had its bump PR created, and the logs look similar, except that there’s not such a long time span between proxy and updater: Note that this run wasn’t manually triggered but happened by schedule.

Has anybody experienced a similar thing? Is there anything we can do about it?

Thanks in advance :smiley:

Just an update, it seems like the problem has been resolved for opa-envoy-plugin updating its opa dependency: there have been bump PRs submitted for the last two opa releases.

However, it seems to have re-appeared in opa, updating its wasmtime-go dependency:

  proxy | 2021/08/03 19:43:26 [035] * authenticating github api request
  proxy | 2021/08/03 19:43:26 [035] 200
updater | INFO <job_177138016> Submitting pull request for creation
  proxy | 2021/08/03 20:23:30 [037] WARN: Cannot read TLS response from mitm'd server read tcp> read: connection reset by peer
updater | time="2021-08-03T20:23:30Z" level=info msg="task complete" container_id=job-177138016-updater exit_code=137 job_id=177138016 step=updater
updater | time="2021-08-03T20:23:31Z" level=warning msg="timeout running job" error="waiting for updater: waiting for container: context deadline exceeded" job_id=177138016

looks like it’s now attempting to do something for 40 minutes, and fails.