Denis Pisarev

> Code Tells You How, Comments Tell You Why. This is one of the approaches. Another one is that the code should implement the (low-level) spec. And the parts of...

I faced this bug with "Text will be here" and unresponsive extension v62. Then I found fixes https://github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/issues/459#issuecomment-2044686278 and https://github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/issues/459#issuecomment-2138858968. So I first checked what was in `~/.cache/[email protected]/registry.txt` and it...

And the first input would be `error: doctest is not supported for nextest` while running `cargo llvm-cov nextest ... --doctests`. Cc https://github.com/taiki-e/cargo-llvm-cov/issues/2

As far as I understood from https://github.com/taiki-e/cargo-llvm-cov/pull/269/files#diff-b2812f19576dd53d0c35b107a322f58a00fce6977f4b5976e1961853982af3ccR357-R362 it's not handling the case when `cargo llvm-cov nextest` is used with flags `--config-file --profile `. This is rather specific case, when nextest...

It wouldn't work in the case if a non-default profile from nextest is used in i.e. CI. That way, without catching `--profile` nextest will go with a default profile. And...

you're right, tested both: ``` root@526ea96919f8:/builds/# cargo llvm-cov --verbose --no-report --include-build-script nextest --color always --no-fail-fast --locked --workspace --profile ci Running `/usr/local/rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/cargo nextest run --manifest-path /builds/Cargo.toml --target-dir /builds/target/llvm-cov-target --color always --no-fail-fast...

> Oh, do nextest seem to change the directory to which build artifacts are written? If so, surely the current cargo-llvm-cov cannot handle that. no, by default it writes to...

As per https://nexte.st/book/configuration.html: ``` The default configuration shipped with cargo-nextest is: [store] # The directory under the workspace root at which nextest-related files are # written. Profile-specific storage is currently...

Another one: (context: https://github.com/taiki-e/cargo-llvm-cov/issues/265#issuecomment-1527508505 and https://github.com/taiki-e/cargo-llvm-cov/issues/265#issuecomment-1532042501) `--partition` https://nexte.st/book/partitioning.html. The idea is that the tests are divided (randomly with `count` and deterministically with `hash`) to run on the separate machines. This...

> It does not seem to be the directory to which cargo build artifacts are written when the --target-dir option is passed. [Altered](https://github.com/TriplEight/cargo-llvm-cov/compare/main...dev) your test a bit to [see](https://github.com/TriplEight/cargo-llvm-cov/actions/runs/4876022175/jobs/8698978928#step:11:108) what's...