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

fix: ChainReader fails on find_intersect_point without agency #1852

Merged
merged 4 commits into from
Jul 24, 2024

Conversation

jpraynaud
Copy link
Member

@jpraynaud jpraynaud commented Jul 23, 2024

Content

This PR includes a fix to the Chain Reader:
when the Chain Sync client does not have agency (i.e. is waiting for the server to callback), the find intersect point call to the Chain Sync is not allowed and is now skipped in the find_intersect_point function of the Chain Reader.

Pre-submit checklist

  • Branch
    • Tests are provided (if possible)
    • Crates versions are updated (if relevant)
    • CHANGELOG file is updated (if relevant)
    • Commit sequence broadly makes sense
    • Key commits have useful messages
  • PR
    • No clippy warnings in the CI
    • Self-reviewed the diff
    • Useful pull request description
    • Reviewer requested

Issue(s)

Closes #1836

@jpraynaud jpraynaud self-assigned this Jul 23, 2024
Copy link

github-actions bot commented Jul 23, 2024

Test Results

    4 files  ±0     52 suites  ±0   9m 1s ⏱️ +8s
1 157 tests ±0  1 157 ✅ ±0  0 💤 ±0  0 ❌ ±0 
1 323 runs  ±0  1 323 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 8f88564. ± Comparison against base commit 0e21965.

♻️ This comment has been updated with latest results.

@jpraynaud jpraynaud temporarily deployed to testing-preview July 23, 2024 16:52 — with GitHub Actions Inactive
@jpraynaud jpraynaud temporarily deployed to testing-sanchonet July 23, 2024 16:52 — with GitHub Actions Inactive
Copy link
Collaborator

@falcucci falcucci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left just a comment but to take or leave it.

LGTM

When the chain sync client does not have agency (i.e. is waiting for the server to callback),
the find intersect point triggered is not allowed and is now skipped.
@jpraynaud jpraynaud force-pushed the jpraynaud/1836-fix-chain-reader-stuck-error branch from 08f1a36 to eda8aa5 Compare July 23, 2024 18:06
@jpraynaud jpraynaud temporarily deployed to testing-preview July 23, 2024 18:15 — with GitHub Actions Inactive
@jpraynaud jpraynaud temporarily deployed to testing-sanchonet July 23, 2024 18:15 — with GitHub Actions Inactive
- 'mithril-common' from '0.4.34' to '0.4.35'.
@jpraynaud jpraynaud force-pushed the jpraynaud/1836-fix-chain-reader-stuck-error branch from eda8aa5 to 8f88564 Compare July 24, 2024 08:00
@jpraynaud jpraynaud temporarily deployed to testing-preview July 24, 2024 08:07 — with GitHub Actions Inactive
@jpraynaud jpraynaud temporarily deployed to testing-sanchonet July 24, 2024 08:07 — with GitHub Actions Inactive
@jpraynaud jpraynaud merged commit 3b6557b into main Jul 24, 2024
40 checks passed
@jpraynaud jpraynaud deleted the jpraynaud/1836-fix-chain-reader-stuck-error branch July 24, 2024 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ChainReader is stuck in Agency is theirs error
4 participants