You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I experience an issue with SseEmitter in spring-framework 6.2.x vs 6.1.x. I am trying to complete an SseEmitter in the onTimeout callback in order to have a 200 http status code. This works fine in spring-framework 6.1.x and spring-boot 3.3.x, but breaks with spring-framework 6.2.x and spring-boot 3.4.x.
The commit that break this behaviour is the following e67f892.
In the past even when completion was already set, the completion handlers were still executed, when explicitly calling the complete method, this is not the case anymore and in case of onTimeout the completion has been set to true already before calling the callback.
The code looks something like the following, where I expect a 200 status code after the 1s timeout, because I explicitly complete the emitter in the onTimeout callback:
Hi all,
I experience an issue with SseEmitter in spring-framework
6.2.x
vs6.1.x
. I am trying to complete an SseEmitter in theonTimeout
callback in order to have a 200 http status code. This works fine in spring-framework6.1.x
and spring-boot3.3.x
, but breaks with spring-framework6.2.x
and spring-boot3.4.x
.The commit that break this behaviour is the following e67f892.
In the past even when completion was already set, the completion handlers were still executed, when explicitly calling the complete method, this is not the case anymore and in case of
onTimeout
the completion has been set to true already before calling the callback.I have provided a sample project here https://github.com/stevijo/sse-emitter
The code looks something like the following, where I expect a 200 status code after the 1s timeout, because I explicitly complete the emitter in the onTimeout callback:
The text was updated successfully, but these errors were encountered: