-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Closed migrators not removed from conda-smithy's cache #1833
Comments
Maybe this would make sense to do as part of this cache refreshing step conda-smithy/conda_smithy/configure_feedstock.py Line 2259 in f1456a3
|
A workaround for this would be to purge the local migrator cache and try again For my system, this looks like...
|
I do a lot of local rerendering, so this bug has caused me a lot of confusion. Is there any way we can prioritize fixing this? It is disorienting when the local rerendering doesn't match the bot's rerendering. I know I can simply delete the local cache, but that is exactly the thing I will forget to remember to do when I am in a hurry. xref: conda-forge/tiledb-feedstock#298 (comment), conda-forge/tiledb-feedstock#296 (comment) Also note that deleting |
PRs welcome. You probably need to delete the folder at conda-smithy/conda_smithy/configure_feedstock.py Line 2535 in 92b4ada
|
@jakirkham what did you mean to end this sentence with?
In what are the closed migrators left? I noticed smithy hung in this codepath, which made me create #1972 - not sure if this is related or not. |
In the local cache directory, which on Ubuntu is |
When a migrator is closed, conda-smithy still hangs onto the migrator in cache and doesn't remove it. As a result re-rendering locally can leave closed migrators in
One possible fix would be for conda-smithy to recheck its cache contents against the migrator source and remove any that are no longer included upstream
The text was updated successfully, but these errors were encountered: