resgroup/wind-up

Cache is still used even when `wind-up` configuration inputs change

Open

#52 opened on Feb 12, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (11 forks)auto 404
buggood first issue

Repository metrics

Stars
 (28 stars)
PR merge metrics
 (PR metrics pending)

Description

Example

A user has run a wind-up analysis. As part of this analysis, a preprocess.pickle will be created and saved to local cache. The user amends some wind-up configuration inputs (eg amends exclusion_periods_utc on the WindUpConfig) and re-runs the analysis. Currently, the preprocess.pickle cache will be used even though the user inputs have changed, therefore not updating the analysis with the user's new inputs.

Contributor guide

Research direction
Investigate the cache key generation in the preprocessing step. Ensure that all relevant configuration inputs (e.g., exclusion periods utc) are included in the cache key so that changes trigger a cache miss.
Tech stack
python
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65