| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
see commit for reasoning
|
|
|
|
|
|
|
|
|
| |
Note that, as it looks, the directive was already broken in previous v5 versions.
So while I solved what looked like a (intentional) regression from the
performance tuning, I actually solved a previous regression as well ;)
I have also added new test cases to the testbench in order to capture such
problems in the future. This version does now look pretty good in shape.
|
|
|
|
|
|
|
| |
at least in important cases (not for non-direct action queues and some
other minor things). This version is definitely buggy, but may be tried
with success on a non-production system. I will continue to work on the
correctness, but needed to commit now to get a baseline.
|
|
|
|
|
|
|
|
| |
Now, the full batch is passed down to the rule, which then enqueues
the elements as single messages. Note that this code has some known
defects and needs more changes until it is correct again. This is
primarily a commit to be able to return to a known-(somewhat)-good
state.
|
|
|
|
|
| |
as well as some work in preparation of storing doAction params inside
the batch
|
|
|
|
|
| |
We do now enqueue those objects that are left unprocessed. This enables
us to delete the full batch, what is exactly what we need to do.
|
| |
|
|
|
|
|
|
| |
... on the way to the ultra-reliable queue modes (redesign doc). This
version does not really work, but is a good commit point. Next comes
queue size calculation. DA mode does not yet work.
|
|
|
|
| |
... passed initial tests, but of course more are needed
|
|
... now that we know what we need from a theoretical POV.
|