-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎅 Fetch before rebuild #1157
🎅 Fetch before rebuild #1157
Conversation
I don't think this is fixing the issue - the dependencies from the build plan are not passed in anywhere, and these are the ones we need to fetch. A good first step for a fix would be to write a test that replicates the issue in #1110. After we get CI to fail because of that we can then write the correct patch. |
I'm not a fan of ttd i rather write the patch first if i go ahead with this. Should |
This is not about TTD, but rather about replicating the failure in a standard environment (CI). If we can't replicate we can't fix. |
Can the registry be queried as to what is the latest version of a package? |
Why would we need that? We'll need to build with whatever versions the solver returns, which is not always going to be the latest one. |
As new versions get added to the registry, the solver might resolve to something else. I expect the test to start breaking. |
It's entirely possible to have a test that doesn't break over time - we'll need to set the version bounds to be different than what the package set contains. |
In #1110 i don't think it was relevant that an outdated package |
The test passes but i don't think it works correctly. Not sure what is happening |
This has been discussed on Discord, but I'll report here as well: |
Superseed by #1283 |
Fix #1110