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

feat: allow no roundStartEpoch for existing rounds #290

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

bajtos
Copy link
Member

@bajtos bajtos commented May 13, 2024

When the Glif RPC API calls are timing out, or when our system is broken and rounds are not advancing at all, allow the spark-api service to start, even though it cannot obtain the roundStartEpoch of the current round.

When the Glif RPC API calls are timing out, or when our system is broken
and rounds are not advancing at all, allow the spark-api service to
start, even though it cannot obtain the roundStartEpoch of the current
round.

Signed-off-by: Miroslav Bajtoš <oss@bajtos.net>
@bajtos bajtos requested a review from juliangruber May 13, 2024 14:30
Copy link
Member

@juliangruber juliangruber left a comment

Choose a reason for hiding this comment

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

Let's discuss whether to land this PR, but it itself lgtm

@bajtos
Copy link
Member Author

bajtos commented May 14, 2024

I was thinking more about this problem and would like to change the architecture of our round tracking. These incremental changes seem a bit hacky and increase the complexity too much.

The first step on the new journey: #292

@bajtos bajtos marked this pull request as draft May 15, 2024 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

None yet

2 participants