fix: follow up on added bidding zones datasets#2007
Merged
lkstrp merged 9 commits intoPyPSA:masterfrom Jan 26, 2026
Merged
Conversation
lkstrp
force-pushed
the
fix-bidding-zones
branch
from
9cc68b5 to
2903b14
Compare
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow up on #1991
EDIT:
Actually not an issue of PyPSA-Eur, but of the storage plugin and the different compression which cloudflare uses (which proxies the bucket)
Fix in PyPSA/snakemake-storage-plugin-cached-http#3
This PR introduces cache invalidation based on new datasets, which explains why this was not caught in the first place. And also adds the missed path changes