diff options
| author | Matthias Radestock <matthias@rabbitmq.com> | 2012-03-22 15:15:56 +0000 |
|---|---|---|
| committer | Matthias Radestock <matthias@rabbitmq.com> | 2012-03-22 15:15:56 +0000 |
| commit | 9506c29260675298a13a7bc73567e61c8f1b0b2b (patch) | |
| tree | 616156b73c2e40bc2532cbc766af3d59331c1114 /scripts/rabbitmqctl | |
| parent | d32586f256e3c1d2e498805d92ed247396397d41 (diff) | |
| download | rabbitmq-server-git-9506c29260675298a13a7bc73567e61c8f1b0b2b.tar.gz | |
fix a possible leak
it's not clear whether we can actually end up in the 'none' branch,
but assuming it exists for a reason, we should certainly clear the
dict entry there too.
We don't actually need to clear the entry in the {value, ...} branch,
since handle_confirm will do that. But clearing in all cases is more
obviously correct.
Diffstat (limited to 'scripts/rabbitmqctl')
0 files changed, 0 insertions, 0 deletions