Closing this, as these metrics are now visible on https://grafana.softwareheritage.org/d/FqGC4zu7z/vlorentz-loader-metrics
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 4 2022
Jun 23 2022
May 30 2022
May 23 2022
oh you're right; this time status is undefined, not success
3.4.1 is deployed everywhere:
root@pergamon:~# clush -b -w @swh-workers -w @swh-workers-large -w @staging-workers 'dpkg -l python3-swh.loader.core' --------------- worker[01-18],worker[0-3].internal.staging.swh.network (22) --------------- Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=======================-====================-============-================================= ii python3-swh.loader.core 3.4.1-1~swh1~bpo10+1 all Software Heritage Loader Core
May 13 2022
May 10 2022
Currently can't do it on GitLab while logged out: https://gitlab.com/gitlab-org/gitlab/-/issues/361952
May 3 2022
Yes; and they should be already supported in SWH (if some places don't, then it's a bug)
Apr 29 2022
Apr 28 2022
Apr 27 2022
Apr 26 2022
Apr 22 2022
Apr 21 2022
Feb 25 2022
After upgrading pergamon and debugging through sentry and cli, the deposit icinga check is back on track.
Triggered back the icinga checks there.
- Fix loader.core debian build [1]
In T3976#79630, @olasd wrote:https://opam.ocaml.org/doc/FAQ.html#Why-does-opam-require-bwrap
"If needed, for special cases like unprivileged containers, sandboxing can be disabled on opam init with the --disable-sandboxing flag (only for non-initialised opam)".
I think that would make sense, as we never execute code from the opam root, we only read metadata files.
"If needed, for special cases like unprivileged containers, sandboxing can be disabled on opam init with the --disable-sandboxing flag (only for non-initialised opam)".
Feb 24 2022
- Fix deposit debian build