-
Notifications
You must be signed in to change notification settings - Fork 197
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
Nexenio/overhaul vault pr #1053
Nexenio/overhaul vault pr #1053
Conversation
a60fa64
to
b4805cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. It looks like everything made it into the PR. There are some newer modifications in nexenio-dev, but for now this is fine and is ready to get integrated!
Do you know whats up with the tests? I will probably investigate it tomorrow |
b4805cb
to
bc0f7e0
Compare
Hey @ademariag , I tried fixing the tests already but there is some issue with the container. We tried a basic script in github actions, with just starting the container und trying to curl it, and even that fails. Maybe the ci is blocking some ports? |
Have these tests ever worked? As in connecting to a container? |
Yeah, they did. And for some reason for some commits they still work. I don't have any clue what causes them to fail, because locally everything works fine |
f88b62e
to
2f5744a
Compare
I think I fixed it. the issue is that "container == running" is not the same as vault being able to receive a connection. So I have added a try-catch |
Fixes for PR #958
Proposed Changes