I'm interested in having Rust available in the LHCb environment, in particular since I added lhcb-conddb/lhcb-conditions-database!104 (merged), lhcb/Detector!454 (merged) and https://gitlab.cern.ch/lhcb-core/lb-conddb-schema-check.git
pre-commit
(as of 2.21.0) can use Rust based hooks even if Rust is not available (see https://pre-commit.com/#rust), but is of course better/faster if you have it.
I'm not sure I get what and lb-conda environment would give me. I'm installing Rust on lhcbdev.cern.ch
using their tool rustup
, which can manage multiple versions of the compiler (see lhcb-ops/lbdevops!50).
Actually I just checked and it looks like IT fixed Rust installation on lxplus (at some point they had installed rustc
, the compiler, but not cargo
, the main tool), so this is not really needed. I'll continue to install the latest versions on lhcbdev.cern.ch, but the version in lxplus is not too bad.
Is there a specific motivation? What do you think about having an lb-conda environment instead?
Marco Clemencic (2191ca98) at 16 Feb 13:24
Add Rust from lhcbdev.cern.ch to LHCb environment
Chris Burr (642456d9) at 03 Aug 11:37
Merge branch 'add-lb-telemetry' into 'master'
Chris Burr (1869dbc0) at 03 Aug 11:37
Chris Burr (642456d9) at 03 Aug 11:37
Merge branch 'add-lb-telemetry' into 'master'
... and 9 more commits
Cameron Duncan Mcclymont (1869dbc0) at 02 Aug 17:01
Change table name back
Cameron Duncan Mcclymont (211ba129) at 02 Aug 16:59
Fix payload incorrect
Fixed, payload now looks like:
{"build_num": "2876", "host_os": "linux-64", "flavour": "stable", "override_lbenvroot": "false", "lbenv_prefix": "/cvmfs/lhcb.cern.ch/lib/var/lib/LbEnv/2876/stable/linux-64", "shell": "/usr/bin/tcsh"}
Cameron Duncan Mcclymont (e31e50b4) at 02 Aug 16:26
Update table name
Ah yes you're right, perfect
I'm not sure there is a good way of adding the timeout without adding dependencies or having some very complex code. This timeout is probably good enough.
Hiding any error messages produced
This already has this.
Also in our initial call you mentioned including:
Are you still interested in adding either of these?
I'll change the table name from lbenv_activation
so we have a clean slate. Is lbenv_activations
(with an 's') okay or I can get the existing one deleted and we can reuse the name?
That's working thanks (see recent data plot in Grafana)!
Cameron Duncan Mcclymont (2e1f99f1) at 02 Aug 15:19
Fix quotes in set _payload