Cachers that specify path_overrides don't track

Open
#116 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by tracing how cacher paths are translated to the store full path, especially for cachers with path_overrides and inline cachers. Compare the assumptions about subdir, prefix, and name with the cases described in this issue and the related #113 context. Done means path-overridden cachers track correctly without requiring those path components.

Written by the indexing model from the issue text.

Description

bug

This is due to the difficulty in doing the path translation to the store full path. This is (unfortunately) going to plague #113

This is partially because the path translation assumes always strictly having the subdir/prefix/name etc, and we get none of those esp if it's an inline cacher or similar.

We should probably note that using the string templating in cachers is pretty specifically only for things like raw data processing that we never want per-parameter set, or will effectively never want in a full store anyway

Dominant language
Python
Stars
18
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ORNL/curifactory

All issues in ORNL/curifactory

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.