Ed Page

Looking into how to automate testing of a fix. It looks like the current registry tests use a file URL for the registry which causes everything to be immediately available....

Before, crates.io did block until it was published as the calls were being serialized. They switched to the API call enqueuing the publish. The concern I'd have with crates.io transparently...

Testing notes @_**Eh2406|120179** [said](https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/un-tested.20tokent/near/285301041): > @**Ed Page** let's take as a given that we want to leave the logic for publish to happen asynchronously and as direct rights to the...

I'm a bit annoyed with the disparate implementations of fuzzy searching. Its difficult to provide a consistent user experience and is easy to make mistakes like this where you assume...

> So just to make sure I'm on the same page, this issue should be related to the fuzzy searching, and a new issue should be made for the cargo-add-with-vendoring...

I'd propose we do the following 1. Combine the query with fuzzy query methods, where separate 2. Switch from a bool to an enum (`Strict`, `Fuzzy`) 3. Add the following...

#10883 was a refactor that laid the ground work for fixing this. Remaining steps: - Add `QueryKind::Normalized` - Initially, we can make it like Exact for path sources and like...

Going to do a quick brain dump since this has been on my mind... When it comes to evolving features without a breaking change, the biggest hazard is taking functionality...

> FWIW I would expect -foo to disable any features that have foo as a requirement (but other features that were activated because of it to stay on). For this...

> .... also wait we set cfg(feature = "default") I did not know nor expect that I assumed we didn't either but I went and tested it. We only set...