labofsahil/github-event-dataset-2012 huggingface dataset:
Admittedly more of an edge-case, but with the current setup, users may have a "default" Stored Procedure name and then use messages with the `jdbc_storedProcedureName` header provided to execute other Stored Procedures/Functions. 

Ultimately, it may also boil down to **user-preference**, whether they prefer seeing a SpEL expression or not. Another edge-case might be a scenario where users execute massive amounts of Stored Procedures with the occasional one-off. With the current setup, users have the option to use the less-expensive attribute `storedProcedureName` together with dynamic capabilities. Otherwise I would need to allow both properties `storedProcedureName` (higher priority) and `storedProcedureNameExpression` simultaneously, but that would look strange IMO. 

Maybe these use-cases are far too edgy...tried to cover all the bases :-)
It's all the deeply nested if/else blocks that Sonar doesn't like; maybe you can factor some of it out into a method.

You didn't respond to my first comment line (need to set replyMessage to null when the time runs out) - also applies in the last else block (timeLeft  <=0 and this.receiveTimeout > 0).

I think in both places you can simply set replyMessage to null; because that, too, will make the while exit.
Hi Artem; for your future reference, we should __never__ do blocking calls in tests; if something goes wrong it will hang the build.

Use 

    assertTrue(this.latch.await(10, TimeUnit.SECONDS));

instead.

I will change this while merging.
Looking at all these new classes and interfaces I am still not getting what is the value of all this? Based on the existing code it looks like the following would works just as well. 
```
this.variableResolver = new BeanFactoryGroovyVariableResolver(beanFactory);
```
I mean I see you have that inner class of ControlBusBeanFilter which overrides only one method of BeanFilterAdapter which is getBeanIfMatch(..), but you could avoid all these new strategies and classes by may be defining a very simple Filter component wit a single method called filter and include the logic you currently have in ControlBusBeanFilter in it and that would be all
Not sure what you are trying to say here. I think you can remove from "Keep in mind..."
It looks scary to me as well, but really, I only replaced 0.2.0 with 0.2.1, I don't know why it show up in github as full file replacement... :( I tested using maven, it looks so far so good...
I added the #update method just minutes before you posted that comment. The #update method exists now and #update_password can't be renamed to that name.

Probably the method could be renamed to #update_citizen. What do you think?

Regarding ability to edit email addresses: it could be done but no one has requested that yet (unless your comment was a request?).
It's line-break removal at the end. (When I add/remove stuff at the end of a file, I often don't recall if there should be a newline at the end, and "git diff" is of no help in this case.)
Was this causing you problems?
Without the use of escape characters, the script crashes because it will not find the true path.

Ex: With `D:/ HTTP Server/MyProject`, the script will stop at `D:/HTTP`
if (labelText && self.mapLabel.hidden)
By the way, is it OK to have line breaks like that in .md files? Don't they affect the formatting in some way?
グッディです。
don't need type="text/css" on link rel="stylesheet"
Can you remove the line return ? ``) {``
Nu e tocmai getter funcția asta. Zi-i `properties` și suntem prieteni.
As this class is configurable, the default value should be in the Configuration class
I like that!  Let me try.
I think if there's an error, you should call jqUnit.start() to continue to the next test.
This needs to work with MockFileData to be consistent with anything pre-initialized when creating the MockFileSystem.
You could use an if-else statement instead because the above one-liner looks hard to read.
Was this just created with the dumpdata command? if so, go ahead and merge this in.
You don't want to delete the first request's memory map..
> I never liked documentations built upon code artifacts (like @Indexed):

+1 Agreed. I don't like this either. It kind of works, because it is under "Basic Mapping" and in fact it does not appear in the table of contents, because it is a 4th level heading. For this reason alone you could not move it into 4.1.1.1. 

Still from a consistency POV my prose argument still holds.

 >   it gives no clue about how to achieve things in a reference documentation unless you already know what the feature does 

"indexing interception" speaks imo for itself.
No, at least not in LCR, global rollup/dedup use MP.
Looks like a number of places incorrectly resource sockets also, should be fixed in a separate commit though.
We need to describe what constitues a font family. The API docs contain a good description of this.
well I was thinking about ``advanced_configuration.rst`` file, can you update this file too
Надо бы назвать функцию как-то более конкретно к ее назначению.
``AnnotationRegistry::registerLoader(array($loader, $class))``
Eric says: should be renamed to autowire test
you cant upgrade to the 3.x versions here if you don't want to upgrade to the trunk here
The paragraph before is using tabs.. I couldn't have picked this up just by looking at it. Why aren't all these files de-tabbed?
We are planning on doing that but also wrapping the creation into a Controller function. You will see more after Rowell's changes are put in