Transaction is missing event at index 1
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 361
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
Instructions
Head to https://explorer.bitquery.io/flow/tx/49069b2c87d4734e1510e120b2084a083cf24a0e54de595281d4e61e4c4d2719/events to visualize the events of that transaction
Problem
We expect that transactions results returned by the API contain all events.
For tx 49069b2c87d4734e1510e120b2084a083cf24a0e54de595281d4e61e4c4d2719, we can deduce from event indexes that the event at index 1 is missing (there's an event at index 0 and one at index 2).
Contributor guide
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 reproducing transaction 49069b2c87d4734e1510e120b2084a083cf24a0e54de595281d4e61e4c4d2719 using the linked explorer and checking the API's returned event indexes. Trace how transaction results and events are assembled in the Go repository. Done means the API returns the event at index 1 along with the events at indexes 0 and 2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100