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

Different way of handling sync_testnets failure #7035

Merged
merged 21 commits into from
May 17, 2024

Conversation

kamilchodola
Copy link
Contributor

@kamilchodola kamilchodola commented May 16, 2024

Simplified approach which handles well unexpected shutdowns of an containers and exits properly on spcified conditions.

Types of changes

What types of changes does your code introduce?

  • Bugfix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)
  • Breaking change (a change that causes existing functionality not to work as expected)
  • Optimization
  • Refactoring
  • Documentation update
  • Build-related changes
  • Other: Description

Testing

Requires testing

  • Yes
  • No

If yes, did you write tests?

  • Yes
  • No

@kamilchodola kamilchodola requested review from rubo and a team as code owners May 16, 2024 09:42
@kamilchodola kamilchodola merged commit b9fb002 into master May 17, 2024
71 of 73 checks passed
@kamilchodola kamilchodola deleted the kch/forther_sync_testnets_improvements branch May 17, 2024 10:23
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.

2 participants