404s on https://proxy.golang.org

Loads of errors like this one (around 1K per hour, 416K last 30 days) and it looks like there is nothing we can do about it, for example:

https://proxy.golang.org/buf.build/gen/go/as-metavision/service/protocolbuffers/go/@v/list contains v1.35.1-20230828104304-96b528b9617f.1 but the release does not exist

404s are sometimes:

not found: temporarily unavailable

https://proxy.golang.org/buf.build/gen/go/as-metavision/service/protocolbuffers/go/@v/v1.35.1-20230828104304-96b528b9617f.1.info

not found: buf.build/gen/go/xxx: reading yyy: 404 Not Found server response: a dependent commit has been deleted

https://proxy.golang.org/buf.build/gen/go/as-metavision/service/protocolbuffers/go/@v/v1.36.0-20231005123640-f6ff0c779521.1.info

Should we do something at the Golang Loader level to stop sending these exceptions to sentry ? Seeing +200K project errors in every sentry weekly reports is a bit depressing

Sentry Issue: SWH-LOADER-CORE-28D

changed the description

IMHO, Sentry should be used for real errors that imply a fix from our side (conf, code, whatever the fix is). If it is expected that sometimes the target is missing and we do not plan to fix an error from our side, it can be discarded from sentry or not sent to it

mentioned in merge request !549 (merged)

closed with commit 2c001345

closed with merge request !549 (merged)