Joystream / Joystream/joystream
QuarsLab Assessment Review
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Some general points
- MEDIUM_1 - update substrate and old dependencies
Updating to newer version of substrate is certainly in the roadmap for carthage and mainnet - https://github.com/Joystream/joystream/issues/3487
We could also bump versions of substrate dependencies withcargo-update
Perhaps we can add cargo audit step to our CI checks - as an informative check - INFO_1 -
#[transactional]I believe this will be available in substrate v3+ so we should certainly make use of it - 5.1.3 Benchmarking - We certainly have made progress here but still many pallets are incomplete.
- Currently we have a github action that builds runtime with benchmarks features and generates weights. This happens on every PR. It takes several hours and always times out. We should re-visit this. It doesn't make sense to generate weights on every PR. Instead this should be a manual invocation that generates and checks in the newly generated weights. It should also be performed on the "reference" hardware.
- LOW_8 - content::delete_post - extrinsic does not exist
- INFO_8 - content::create_post - extrinsic does not exit
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 .github/workflows/joystream-node.yml and the assessment points concerning Substrate dependencies, transactional support, benchmarking, and the content extrinsics. The scope is currently a collection of separate tasks; done would require defining and completing the selected dependency, CI benchmarking, and pallet changes rather than addressing a single specified edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- blockchain, build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100