Repository navigation
Flushing-related regression in SseServerResponseΒ #36537
Description
While trying to upgrade Spring AI from Spring Boot 4.1.0-M2 to 4.1.0-M3, it broke our integration test WebMvcSseServerTransportProviderIT.
An AI-based analysis seems to point to e0b54e2 as the potential cause, and suggests updating SseServerResponse.DefaultSseBuilder.send(), changing body.flush() to this.outputMessage.flush().
Activity
Fix SSE flushing in SseServerResponse
Pin spring-framework to 7.0.7 to fix flushing regression (#5844)
Pin spring-framework to 7.0.7 to fix flushing regression (spring-projβ¦
Move to Spring Boot 4.0.8 and count each rate-limited request once
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 and fall back when sampling times out
Move to Spring Boot 4.0.8 and count each rate-limited request once
Move to Spring Boot 4.0.8 and count each rate-limited request once
Move to Spring Boot 4.0.8 for the SSE flushing fix
18 remaining items
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 and count each rate-limited request once
Move to Spring Boot 4.0.8 and fall back when sampling times out
Move to Spring Boot 4.0.8 and fall back when sampling times out
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 and fall back when sampling times out
Move to Spring Boot 4.0.8 for the SSE flushing fix
Move to Spring Boot 4.0.8 and fall back when sampling times out
Move to Spring Boot 4.0.8 and fall back when sampling times out
Move to Spring Boot 4.0.8 and count each rate-limited request once
Move to Spring Boot 4.0.8 and count each rate-limited request once