Make `FirstEvent` configurable to better support public chain with multi-party
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- blockchain, cli
Research direction
Start in internal/stacks/stack_manager.go around line 988, where the FireFly batch pin contract event starts at block 0, and trace how the generated firefly_core YAML receives its indexing configuration. Determine how FirstEvent should be exposed as configuration and verify that indexing begins at the requested block without manual YAML edits.
Written by the indexing model from the issue text.
Description
As per the discussion here: https://discord.com/channels/905194001349627914/1306104244486668369/1306929797296816200, Firefly-cli currently hard code the starting block of the Firefly batch pin contract event to 0 to ensure no events could be missed. But this is impractical when using multi-party mode with a public chain: https://github.com/hyperledger/firefly-cli/blob/14e7721bf8cca1fc6b2b217d00a5d79926a17af2/internal/stacks/stack_manager.go#L988
Workaround
The currently workaround is to update the firefly_core yaml generated manually to start indexing the events from a desired block number. (hint: newest can be used if you don't care about missing events which breaks integrity of indexed data)
An enhancement would be making the FirstEvent configurable
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/cli#339 · 7 comments ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
All issues in hyperledger-firefly/cli
Similar issues
-
[Bug]: APIGW request ID headers are inconsistent between server and clientPossibly taken @zouxingyuks claimed this today. Openproduct/backlog
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TencentBlueKing/bk-nodemgr#3782 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
praetorianer777/Dynamo#53 ·
Maintainers usually reply within 1 day
-
internal test setup
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SAP/terraform-provider-scc#430 ·
-
internal test setup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SAP/terraform-provider-btp#1743 ·
Maintainers usually reply within 1 day