Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Contract deployment heights ignored when starting from genesis #11633

Closed
wwestgarth opened this issue Sep 2, 2024 · 0 comments · Fixed by #11630
Closed

[Bug]: Contract deployment heights ignored when starting from genesis #11633

wwestgarth opened this issue Sep 2, 2024 · 0 comments · Fixed by #11630
Assignees

Comments

@wwestgarth
Copy link
Contributor

Problem encountered

It was noticed on fairground that when starting a network from genesis, the contract deployment heights in the network parameters for the bridges is ignore. This means the node start looking from logs from block height 0 and it takes forever to catch up.

Observed behaviour

Nodes start looking for contract logs from height 0 when starting from genesis.

Expected behaviour

Nodes start looking for contract logs from the height specified in the network parameter when starting from genesis.

Steps to reproduce

1. Submit `xyz` transaction
2. With this payload
3. Query `abc` API
4. Observe the error

Software version

v0.77.0

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response

@wwestgarth wwestgarth added this to the 🏛️🏛️Colosseo II milestone Sep 2, 2024
@wwestgarth wwestgarth self-assigned this Sep 2, 2024
@vega-issues vega-issues moved this to Waiting Review in Core Kanban Sep 2, 2024
@vega-issues vega-issues moved this from Waiting Review to Approved in Core Kanban Sep 2, 2024
@vega-issues vega-issues moved this from Approved to In Review in Core Kanban Sep 2, 2024
@vega-issues vega-issues moved this from In Review to Approved in Core Kanban Sep 2, 2024
@github-project-automation github-project-automation bot moved this from Approved to Merged in Core Kanban Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant