| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
cosmetics
|
| | |
|
| |
|
|
| |
issues a qos = 0, we can't have the limiter exiting. Thus limit needs to become a call, plus associated changes. Note that we *have* to know whether or not the limiter is about to stop - if we just wait for the exit signal then there's a race with a new qos setting being sent to an expiring limiter and the limiter thus getting lost. Also, the channel *must* be responsible for telling the queues to forget the limiter, otherwise again there's a race between a new limiter starting up and telling the queues about it, and the old limiter dying and telling the queues they're unlimited. This is why the limit_queues function cannot be moved into the limiter - the channel must drive this.
|
| |
|
|
|
|
|
| |
This really is more of a principled change than of practical
significance since we are unlikely to end up with channels having
mailboxes full of conserve_memory messages.
The change brings 'default' closer to the 'bug21673' branch
|
| |
|
|
|
| |
We change all '8' to '7' - this has no effect but brings 'default'
closer to 'bug21673'
|
| |\ |
|
| |/ |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
[rabbit_tests:test_pg_local()|| _ <- lists:seq(1,10000)]. With this, it's still not brilliant - but then it actually can't be fixed properly, without extending pg_local. This fix is "good enough" to stop my machine barfing on it, though it is still racy - "we" could process our monitors and go onto the final pg_local test before pg_local processes the monitors in its mailbox (well, actually before the monitors *arrive* in its mailbox).
|
| |\ \
| |/
|/| |
|
| |/
|
|
|
|
|
| |
The Windows-only issue addressed in bug22282 requires the use of
spawn_executable, which was introduced in OTP R13. But for other
platforms we'd like to continue to support R12, and so we should stick
to plain spawn.
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to know the REAL_WEB_URL in order to generate the protsfile
and index the resulting macports tree, and all this has to happen at
deploy time. So there is no point in distinguishing the indexing
step.
|
| | | |
| | |
| | |
| | | |
anyway (well actually fromdos) so todos should work on all systems currently
|
| | |\ \
| | |/
| |/| |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
when handling channel closure in the queue process, don't do any
unnecessary work when we end up auto-deleting the queue.
Specifically we don't rollback any transaction or attempt to deliver
any messages. The formmer happens in the termination code
anyway. The latter is a change in behaviour, but one that is permitted
by the spec, and arguably deleting the queue as quickly as possible.
The bug21673 branch already has changes along similar lines.
|
| | | |
| | |
| | |
| | | |
to shrink the diff with bug21673
|
| |/ /
| |
| |
| |
| |
| |
| | |
...in all cased where it refers to the state of a message rather than
an event that has just occured
A similar rename was done in the bug21673 branch, so this change
brings default closer to that
|
| |\ \ |
|
| | | | |
|
| | |/
|/|
| |
| | |
these bring it more in line with the bug21673 branch
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
rabbitmq-multi would fail to start rabbitmq-server.bat if the path had
parentheses in the first few characters of a path component (but not
after the few few characters, due to short names being involved; so
cases such as 'Program Files (x86)' do not trigger the issue).
This fix makes rabbitmq-multi run rabbitmq-server.bat indirectly via
cmd.exe, working around the erlang issue from bug20526. So we no
longer need to involve short names, and by sprinkling double quotes in
the right places we can handle parentheses too.
To test this properly you need a path component with both spaces and
parentheses in the first few characters, e.g. "foo ()".
|
| | |\ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
It will be more trouble than it is worth to preserve this with
deferred expansion.
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
if it's not set
|
| | | |_|/
| |/| |
| | | |
| | | | |
output
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | | |
suggests that -E is needed to preserve environment. Manually checked and indeed it is. Hence added -E to the one call of sudo in entire codebase
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | |\ \ \
| |/ / /
|/| | |
| | | | |
in order to resolve merge conflict going the other way
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
which was previously hanging at best and causing things to explode at
worst
|