Till Rohrmann comments

Results 160 comments of


                                            Till Rohrmann

Add integration tests for control plane logic

@pcholakov what's the status of this issue? Shall we mark it as done for the scope of the preview version?

Add integration tests for control plane logic

I will remove it from the preview umbrella issue then.

helm chart improvements

Thanks a lot for your feedback and suggestions @Fran-Rg. This is very valuable. We will try to improve the helm chart. If you want to get your hands dirty (and...

Flakey test: Run SDK-Python integration tests / Features integration test alwaysSuspending => Combinators => Test the first successful awakeable should be returned

Thanks for reporting this issue @lsytj0413. There is another test run where the same test fails: https://github.com/restatedev/restate/actions/runs/14488849773/job/40642088210 with the same error.

Flakey test: Run SDK-Python integration tests / Features integration test alwaysSuspending => Combinators => Test the first successful awakeable should be returned

What's interesting is that the test fails not in all profiles and also not deterministically which I would have expected if a `TypeError` occurs.

Flakey test: Run SDK-Python integration tests / Features integration test alwaysSuspending => Combinators => Test the first successful awakeable should be returned

I think the `TypeError` is red herring. The underlying problem seems to be that in some cases, we take roughly 10s to start processing the incoming invocations. If this happens,...

Flakey test: Run SDK-Python integration tests / Features integration test alwaysSuspending => Combinators => Test the first successful awakeable should be returned

For fixing the test code, I've created https://github.com/restatedev/sdk-python/issues/78.

Flakey test: Run SDK-Python integration tests / Features integration test alwaysSuspending => Combinators => Test the first successful awakeable should be returned

The failed KafkaIngress test here seems to show the same symptoms: https://github.com/restatedev/restate/actions/runs/14511275278/job/40711599370.

fix(3088): disable pgsql endpoint by default

I think you are right that we shouldn't change the system's behavior in a bug fix release. Technically we are printing a deprecation warning if the user opens a connection...

fix(3088): disable pgsql endpoint by default

> 1. v1.3.x：we only printing a deprecation warning when server is starting and the user opens a connection with the pgsql client > 2. v1.4.0：disable pgsql endpoint by defaults, and...