Versioned catalogs
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Catalogs don't like to get overwritten, because write_file will error if it notices there's a duplicate catalog. The goal is, instead of erroring for a named catalog, the old one must be versioned using its hash. Once the old catalog is moved, the new one can take its place with no error so long as the new file is different from the old file. An error should still occur for hashed catalogs, since those are content-addressable, and so there's no reason to do the same work twice.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from bitmask-stack/carbonado-node
-
Production Node Epic Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Refactor Routes Open
bitmask-stack/carbonado-node#49 · 1 assignee ·
-
LDK integration Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
File expiration Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bitmask-stack/carbonado-node#44 · 1 assignee ·
All issues in bitmask-stack/carbonado-node
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100