David
David
Hmm, why is CI trying to parse the README as toml? @Freyskeyd
@Freyskeyd Can we move this PR to draft status while waiting for `cargo-readme` to fix the issue?
@Freyskeyd Is `cargo-readme` fixed now you reckon?
> I would prefer `cert-producer` instead of `certificate-producer`. It looks a bit unwieldy in the crate name `topos-certificate-producer-subnet-runtime` I agree that the name is unwieldy. I would not mind settling...
It's not uncommon that no_std crates want their test suites to run in no_std as well. Convincing maintainers to switch to using `#![cfg_attr(not(test), no_std)]` instead may or may not be...
This is what I see too. The "register anywhere" feature seems to be broken on macOS (I'm on Sequoia, `15.0 (24A335)`).
@Fraser999 Did you by any chance dig deeper into this yet? Do you have a hunch about where the problem lies and/or which macOS version broke it?
Yeah the example works for me too, always did. Never figured out how to do it outside the divan crate though. It's such a killer feature, sad it's incomplete.
@jdidion I ran into the [`visibility`](https://crates.io/crates/visibility) crate the other day, which could be helpful to make your workaround less verbose. @nvzqz I did some debugging on this issue; I didn't...
So let get me get this straight: contributors that strive to run a tight ship and use good security practices are the ones that you choose to penalize? That doesn't...