Surface failure logs in email

[keith]

I got an email with an error like:

Failed to publish entry for keith/[email protected] to the Bazel Central Registry.

An unknown error occurred. Please report an issue here: https://github.com/bazel-contrib/publish-to-bcr/issues.

It would be nice if the rest of the info was accessible somewhere so I could debug more

[kormide]

Here's the error I'm seeing in the logs:

remote: Permission to keith/bazel-central-registry.git denied to publish-to-bcr[bot].
fatal: unable to access 'https://github.com/keith/bazel-central-registry.git/': The requested URL returned error: 403

I try not to post stack traces. This is a case where I should have a friendly error that gets sent in the email.

Re. the above issue, is the app installed to your fork of the BCR?

[keith]

Yep the app is installed:

Note it has worked before bazelbuild/bazel-central-registry#868, I believe without any changes on my side

[kormide]

Ah, I think I've seen this before. I suspect it's just an intermittent GitHub error. I think the solution is to add some retry logic on the push. I'll leave this ticket open to track that, as well as better error messaging here.

[keith]

Thanks!

[brentleyjones]

I just got the same. Is there a way to force a resubmit?

[kormide]

I just got the same. Is there a way to force a resubmit?

Captured the specific bug in #97. There isn't currently a way to resubmit (tracked here), except to delete then re-create the GitHub release, or to just release a new patch version.

[arijit-sen]

I am facing a similar issue with private repos. The app works correctly with the public repos but when the repo is made private, whenever I release it throws the unknown error. Can someone confirm on the same?

[kormide]

I am facing a similar issue with private repos. The app works correctly with the public repos but when the repo is made private, whenever I release it throws the unknown error. Can someone confirm on the same?

@arijit-sen the error that caused your entries to fail was related to this issue–I sent you an email about it a while back. Beyond that issue, I can't whether it works with private repos because I haven't tested this case. Do you want to try again and we can see what happens?

[kormide]

Now that retries for pushing to the fork has landed, the original issues causing the "unknown error" emails in this thread have all been addressed. Closing.