Dustin J. Mitchell
Dustin J. Mitchell
It seems like ```rust #[distributed_slice(FOO)] #[linkme(crate=::mycrate::linkme)] static BENCH_DESERIALIZE: fn(&mut Bencher) = bench_deserialize; ``` causes `distributed_slice` to refer to the linkme crate as `::mycrate::linkme`. But, I don't see this documented anywhere....
This is a bit of a frustrating design on anyhow's part! I've verified by making `sync()` return an error that this does, indeed, include all of the details.
From #3361. @davidhelbig did the Taskchampion part of this in https://github.com/GothenburgBitFactory/taskchampion/issues/367. Once #3209 is done, the remainder needs to be done in this repo: > * changing the name of...
### Discussed in https://github.com/GothenburgBitFactory/taskwarrior/discussions/3307 Originally posted by **gour** March 28, 2024 Hello! While anticipating 3.0 to arrive into my distribution, I wonder if it should improve time to complete `burndown`...
In #3395, there's an error with sync, but only the context of the error appears, not the actual error: https://github.com/GothenburgBitFactory/taskchampion/blob/5168f0b86415826aa84f70d1e072b6364dd431aa/taskchampion/src/replica.rs#L233 Let's figure out where that info is getting lost (my...
It would be great if the various output from `log::foo!()` in Rust was visible when running `task`, based on some Taskwarrior config. I think `log` has some global configuration that...
### Discussed in https://github.com/GothenburgBitFactory/taskwarrior/discussions/3309 Originally posted by **RedEtherbloom** March 28, 2024 Is there currently a way to access the taskchampion documentation online? The [link](https://gothenburgbitfactory.github.io/taskwarrior/taskchampion/) in the README.md atm 404s. Is...
When sync to `taskwarrior-sync-server` fails, we get pretty terse messages, if anything. Those should at least include the information from the HTTP response signalling the error.
The C++ style and formatting in Taskwarrior is unusual, and difficult to keep up with by hand or in reviews. Let's let computers do the work for us! Ideally clangd-format...
The `task export` from 2.6.2 just sort of blasts out the bytes it finds in `*.data`, regardless of whether those are valid utf-8 (and thus valid JSON). We can't change...