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

Fixes after testing with GM #974

Merged
merged 7 commits into from
May 25, 2021
Merged

Fixes after testing with GM #974

merged 7 commits into from
May 25, 2021

Conversation

adizere
Copy link
Member

@adizere adizere commented May 21, 2021

Closes: #972

Description


For contributor use:

  • Updated the Unreleased section of CHANGELOG.md with the issue.
  • If applicable: Unit tests written, added test to CI.
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Updated relevant documentation (docs/) and code comments.
  • Re-reviewed Files changed in the Github PR explorer.

@adizere adizere marked this pull request as draft May 21, 2021 14:43
@adizere adizere changed the title Adi/gm tests Fixes after testing with GM May 21, 2021
@adizere adizere marked this pull request as ready for review May 21, 2021 16:15
@@ -273,6 +273,11 @@ impl Supervisor {
}
}

// At least one chain runtime should be alive and kicking, otherwise bail.
Copy link
Collaborator

Choose a reason for hiding this comment

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

funny comment but what does it mean exactly?

Copy link
Member Author

Choose a reason for hiding this comment

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

I meant to say that if the vector of chain runtimes (self.registry) is empty, that means no chain runtime could be instantiated, so the supervisor (i) cannot spawn any worker and (ii) has no subscription to any chain to select on. I'll use more accurate language here!

Copy link
Collaborator

Choose a reason for hiding this comment

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

also #972 (comment)
I am not able to see that panic. What are the steps to see that? I tried to start hermes without any chains started and also tried to kill the chain procs while hermes is running.

Copy link
Collaborator

@ancazamfir ancazamfir left a comment

Choose a reason for hiding this comment

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

Ok, let's merge this so the client worker is fixed. Thanks again for finding this!!!

@adizere adizere merged commit 2cbc7a7 into master May 25, 2021
@adizere adizere deleted the adi/gm_tests branch May 25, 2021 11:53
hu55a1n1 pushed a commit to hu55a1n1/hermes that referenced this pull request Sep 13, 2022
* Fix panic when all chains are unreachable

* Fix for reverse params in client worker.

* FMT fix

* Removed useseless format

* Better comment. Changelog
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.

Hermes 0.3.2 issues after testing with Gaia manager
2 participants