Joystream / Joystream/joystream
Giza integration tests: Distributor node: Cache cleanup flow
Open
Nobody has claimed this yet.
estimate-3h
giza
network-integration-test
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Preconditions:
- A running Joystream node
- A running query-node
- A running storage node which accepts channel assets and has sufficient limits set to handle the scenario
- A running distributor node which accepts channel assets and has sufficient limits set to handle the scenario
- Distributor lead is hired
Flow
- Create 2 channels (either
MemberorCuratorGroup) with 2 assets each throughjoystream-cli: - Channel 1 assets:
A,B - Channel 2 assets:
C,D - Request the channel assets (
A-D) from distributor node - Remove asset
Bfrom channel 1 (throughcontent:removeChannelAssetsorcontent:updateChannel) - Unassign distribution bucket from 2nd channel's bag
- Wait
xseconds wherex === Distributor node's config.intervals.cacheCleanup(can be exposed via env) - Request channel assets from distributor node (
A-D) - Expect following results:
- Asset A:
200 OK - Asset B:
404 Not Found - Asset C:
421 Misdirected request - Asset D:
421 Misdirected request
- Asset A:
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 by locating the Giza integration tests for the distributor node and the distributor node's config.intervals.cacheCleanup setting; the flow also uses joystream-cli content:removeChannelAssets or content:updateChannel. The test is done when it verifies 200 for A, 404 for removed B, and 421 for C and D after cache cleanup and distribution-bucket removal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100