Any idea what happened with this package: http://repo.clojars.org/cljsjs/react-select/ https://clojars.org/cljsjs/react-select ? rc.10 is uploaded to the repo, but it is not shown on web Deploy threw this error:

Could not transfer metadata cljsjs:react-select/maven-metadata.xml from/to clojars (): Access denied to: , ReasonPhrase: Forbidden - Serialized task failed.

@juhoteperi Interesting, I'm not sure what that's about. The maven-metadata.xml shows 1.0.0-rc.10, do you happen to still have the full output of the deploy attempt?

https://circleci.com/gh/cljsjs/packages/2692 (not sure if you can see the output)

I can see the output, thanks

I don't see any errors in clojars' log, nor in sentry, so it's unclear why this failed

The "Serialized task failed" makes me think it had a problem writing to the db, possibly

Is that message from Clojars backend?

yes

to support transactional deploys, we use the writing of the metadata file as a trigger to copy the tmp repo where we store your upload over to the real repo

and do the validation/db updates at that point

so this failure is likely unrelated to the metadata file itself

It looks like the release is there, but not listed in the db, so it doesn't show in the UI: https://clojars.org/repo/cljsjs/react-select/1.0.0-rc.10/

Would you be willing to try releasing an rc11 to see if this was a temporary issue?

building 1.0.0-rc.10-1 now (rc10 is the version of upstream package, don't want to touch that)

ah, understood

Strange that the logs wouldn't contain this exception

agreed :(

repo routes seem to correctly catch-and-rethrow the exception, and repo routes are wrapped with repo/wrap-exceptions which should report them

Worked now: https://clojars.org/cljsjs/react-select

Glad it worked. Yeah, I agree - that should have gotten logged to stdout and to sentry, but it didn't go to either

aha... I see it

Any exception from repo routes is added :report? false metadata: https://github.com/clojars/clojars-web/blob/master/src/clojars/routes/repo.clj#L82 , which disables reporting https://github.com/clojars/clojars-web/blob/master/src/clojars/errors.clj#L85

Maybe that is to skip errors caused by e.g. trying to deploy same version again

good catch, we shouldn't be doing that for all errors, the intent there was to not report validation errors to sentry, since those are user errors

would you mind filing an issue for that?

Yeah I'll open one

thanks!