Explore >> Select a destination
|
You are here 
|
michieldemey.be | ||
| | | | |
thefragens.com
|
|
| | | | | ||
| | | | |
rgoswami.me
|
|
| | | | | A meta-post on a presentation at the Scientific Computing in Rust 2024 annual workshop Background Details Title bless : transparently logging program outputs bless repo (Github) Workshop listing conference site Blurb: We introduce bless, a tool geared towards multiple runs of codes in flux. The key idea is to use Rust's logging libraries to transparently annotate outputs and additionally use a MongoDB database to store the output and metadata. We find this raises interesting problems while handling the outputs of MPI commands asynchronously. Additionally we provide alternatives to (PROG 2>&1) | tee blah.out, with the ability to use a configuration file and prepare a tar.gz of outputs and inputs. This is invaluable when working with minor changes to multiple codebases, as is typical in the early stages of a scientific project. | |
| | | | |
jamesward.com
|
|
| | | | | ||
| | | | |
brandonrozek.com
|
|
| | | Git is designed to be decentralized. However, many people treat it as a centralized solution by depending on services such as GitHub. What we've seen through the youtube-dl debacle is that repositories that we depend on can be taken down. This isn't to say that GitHub is evil and that we should move to Bitbucket, Gitlab, Source Hut, etc. But this is more of a commentary on what happens when we depend on one service to host our code. | ||
