fix: fix spo journey test #1132
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix SPO journey tests and auto-calculate init_timestamp
What Changed
• Auto-calculate init_timestamp: Dynamically calculate based on current network state instead of hardcoding, eliminating manual config updates after network restarts
• Fix epoch mapping errors: Handle None returns from find_mc_epoch() to prevent TypeError crashes
• Fix participation validation: Properly remove all entries per producer (not just one) since participation data contains multiple entries with different block counts
link
to the issue.
Checklist
changelog.mdfor affected crate