Jan

Results 71 comments of Jan

See below results after adding a test set ![Screenshot 2022-09-12 at 12 13 33](https://user-images.githubusercontent.com/18519371/189629578-31e6ff03-997e-4d02-ae13-82397edb6272.png) ![Screenshot 2022-09-12 at 12 15 29](https://user-images.githubusercontent.com/18519371/189629714-48120ea7-b0c4-4058-b2f8-fe3412c62421.png) ![Screenshot 2022-09-12 at 12 15 37](https://user-images.githubusercontent.com/18519371/189629718-d8b4958a-ca53-466a-ad35-482e4433ed36.png)

Note that this might be due to the fact that we are working on a mounted remote file system

A couple of related ideas: * Write to the `.jsonl` more regularly (maybe not necessary) * Check whether any entries already exist in the `.jsonl` and if yes, make sure...

I would also say that there is Option 3: Not using `*` at all. ## Option 1 comment For the record, I was the one who introduced this logic. And...

> This being said, are there any other practical reasons to favour one of the three options mentioned so far? > > * `run(file_name, *, verbose)` > * `run(*, file_name,...

> I was trying to find a way to get a list of arguments from in instance of `ArgumentParser`, and I couldn't find a straightforward way... The tests using `inspect`...

@FrancescoCasalegno The wording of this issue is actually really confusing. What I meant is type annotating our entire existing codebase. By incrementally I meant that this can be split up...

So it turns out that using "Self hosted runners" is not recommended for public repositories. https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners > We recommend that you only use self-hosted runners with private repositories. This is...

See below a script that could be turned into a **github action**. ## What is the goal? Replace the manual process that we need to go through when reviewing PRs...

> This is a must-have! > > One comment: > > > Potential reproducibility + environment issues (we do not want to run this inside of a docker container) >...