Tobias Bieniek
Tobias Bieniek
unfortunately this is a bit hard to debug without a reproduction project 😞
After discussing this with the cargo team on [Zulip](https://rust-lang.zulipchat.com/#narrow/stream/318791-t-crates-io/topic/Old.20cargoes.20failing.20to.20parse.20the.20index/near/340396777), we decided that the easiest way forward is to move all features into `feature2` if we detect that any feature uses...
as mentioned on Slack, part of it is that instance initializers now run for every test (previously only acceptance tests), which can cause a slight slowdown. but you are right...
@cibernox if you look at the repro repo the initializers don't seem to be the problem. Ember Data is causing a bit of startup slowness, but even with it removed...
@rwjblue I only worked on the `template-only-glimmer-components` part. The `application-template-wrapper` might still need adjustments.
the normalized manifests would certainly make things easier in the future. unfortunately they won't help if we want to backfill the information for existing crate files though. > crates.io is...
not entirely yet. we still need to expose the data on the API level and backfill the database, but it should be done soon :)
I've just seen this issue here for the first time, but independently I've come to the same solution in PR #45. Works pretty well for me and it also works...
@steffenschaefer this has been resolved by 21a3a3b
what do we need this for? how will this help the user in the end?