Joystream / Joystream/joystream
Updating Category Title is not reflected in Pioneer
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
@secretgir1 commented on Thu May 26 2022
Steps to reproduce:
- Create Category with title "Test"
- Update Category title to "Test 2" via https://polkadot.js.org/apps/?rpc=wss://rpc.joystream.org:9944/#/extrinsics
- Observe forum.CategoryTitleUpdated in explorer https://polkadot.js.org/apps/?rpc=wss://rpc.joystream.org:9944/#/explorer to make sure update happened.
- In Pioneer category shows with old title.
In query node I see old title too.
@bwhm commented on Fri Jun 03 2022
Hey,
If the query node isn't updated either, I'll assume it's because the transaction is:
- Rejected on chain
- Invalid according to the metaprotocol
In any event, that would not be a pioneer problem, but we need to know exactly what the issue is first!
Do you have the blockheight when (3) happened? The link just points to the explorer, so I can't see what happened without knowing the height, and it's hard to find without the time (approx.)...
I assume the category below is the one in question
{
"id": "34",
"title": "Test",
"createdAt": "2022-05-25T19:15:30.000Z",
"updatedAt": "2022-05-25T19:31:12.000Z",
"createdInEvent": {
"inBlock": 904738
}
},
Can it be true that you tried 16min later?
@bwhm commented on Fri Jun 03 2022
"updatedAt": "2022-05-25T19:31:12.000Z",
refers to when it was deleted: https://polkadot.js.org/apps/?rpc=wss://rpc.joystream.org:9944/#/explorer/query/0x0df4889a88a1eab64efdc4e5a14d948f0a4a5262994e6b381a984df70ce8ceba
@dmtrjsg commented on Mon Jun 06 2022
@secretgir1 keeping this issue in New Issues pipeline, while awaiting your response to question from Martin. Thank you in advance.
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 query-node category data and the Pioneer category view, then reproduce the update while recording the chain block height. Compare the on-chain CategoryTitleUpdated event with the query-node record and Pioneer display; done means the new title is propagated and shown consistently, or the failure point is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100