Joystream / Joystream/joystream
Synchronize cache with chain
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Right now, if some content is set as unpublished or if a data object is just outright deleted, or if there is some moderation going on, as will be unlocked by https://github.com/Joystream/joystream/issues/2760. The Argus cache is not synchronized with this currently. This is a problem, because there can be quite substantial urgency in content delivery policy mirroring the state of the chain, for example in being responsive to removal of out-of-policy content. This synch has to work both while node is operating, but also if its booting up and trying to continue with pre-existing cache.
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
Read issue #2760 first to understand the moderation changes, then trace the Argus cache paths for runtime operation and boot-time recovery of pre-existing cache data. Verify how unpublished, deleted, and moderated content changes on the chain are reflected in the cache, including after startup; done means the cache mirrors those chain states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100