Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Non-blocking resolution of variables assumes mutable model

See original GitHub issue

The following commit (3601af0b2) assumes that the Map model provided by Spring Framework is mutable (it is not). This has been raised and is currently discussed in SPR-17407.

Issue Analytics

State:
Created 5 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

bclozelcommented, Oct 22, 2018

Ah, silly me. Yes you’re right, this is done on the functional side only with DefaultRenderingResponseBuilder.

0reactions

danielfernandezcommented, Oct 22, 2018

Already in 3.0.11-SNAPSHOT

Top Results From Across the Web

The Python Language Reference | Matthew Towers' homepage

The description of exactly what things are called mutable is a little confusing. At first: “Objects whose values can change are called mutable, ......

Be Aware of the Traps of Condition Variables - Modernes C++

Today, I write a scary post about condition variables. You should be aware of these issues of condition variables. The C++ core guideline...

Chapter 9. Concurrency with Shared Variables

Our concurrent, duplicate-suppressing, non-blocking cache is complete. The implementation of Memo above uses a mutex to guard a map variable that is shared...

Java concurrency (multi-threading) - Tutorial - Vogella.com

The Java memory model guarantees that each thread entering a synchronized block of code sees the effects of all previous modifications that were...

Web on Reactive Stack - Spring

At the programming-model level, Java 8 enabled Spring WebFlux to offer ... WebFlux (and non-blocking servers in general), it is assumed that ...