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

Bump: runtime 1.1.30 #544

Merged
merged 2 commits into from
Jan 25, 2024
Merged

Bump: runtime 1.1.30 #544

merged 2 commits into from
Jan 25, 2024

Conversation

johanandren
Copy link
Contributor

Replaces #543

@johanandren
Copy link
Contributor Author

Not sure what was going on, couldn't push to the original auto-bump PR, so created my own branch, but then that commit ended up in the original bump PR anyway somehow. 😕

@johanandren johanandren marked this pull request as ready for review January 25, 2024 11:38
@@ -175,7 +175,7 @@ export class IntegrationTestkit {
'VERSION_CHECK_ON_STARTUP',
process.env.VERSION_CHECK_ON_STARTUP || 'true',
)
.withWaitStrategy(Wait.forLogMessage('Starting Kalix '))
.withWaitStrategy(Wait.forLogMessage('Connecting to '))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Seems the order of discovery and logs changed somewhat in the runtime, causing a deadlock because waiting for the Starting Kalix log output, but that was only logged once discovery completes, and discovery would not complete until the test container proxy port is injected a few lines down from here.

Copy link
Contributor

Choose a reason for hiding this comment

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

that's odd, the line is still there...

Copy link
Contributor

Choose a reason for hiding this comment

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

I mean in the runtime code

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah it logs it but I think it must have been logging it earlier before, and now does it only after discovery completes, but the JS SDK blocks that when in test mode, because it needs to know the test container port before it can continue.

@johanandren
Copy link
Contributor Author

Meh, all green but circle did not report back properly.

@johanandren johanandren reopened this Jan 25, 2024
@johanandren
Copy link
Contributor Author

The same again, all steps of the CI workflow green over at Circle but not reported back here.

@johanandren johanandren merged commit dc8ad00 into main Jan 25, 2024
18 of 19 checks passed
@johanandren johanandren deleted the wip-bump-runtime-1130 branch January 25, 2024 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants