overengineeringstudio / overengineeringstudio/effect-utils
genie:run task caching doesn't invalidate when .genie.ts source files change
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
Problem
dt genie:run reports "Cached" even after modifying a .genie.ts source file. The task's cache key doesn't appear to include the content hash of .genie.ts inputs, so changes to source files are silently ignored.
Reproduction
- Edit a
.genie.tsfile (e.g. change a value) - Run
dt genie:run - Observe "Cached" — the generated output is not regenerated
Workaround
Run bun bin/genie.tsx --writeable directly to bypass the task cache.
Expected
genie:run should detect that its .genie.ts inputs changed and regenerate the output files.
Filed by Claude on behalf of @schickling
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dt genie:run entry point and bin/genie.tsx, comparing the cached task path with the direct bun bin/genie.tsx --writeable path. Trace how .genie.ts inputs contribute to the cache key, then verify that editing one causes genie:run to regenerate output instead of reporting "Cached".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, typescript
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100