Skip to content

v0.7.0

Choose a tag to compare

@zw008 zw008 released this 10 Aug 03:57
· 24 commits to main since this release

Fixed

  • purge_queue could never have worked against a real RabbitMQ. The management-API client sent Accept: application/json, but the purge endpoint (DELETE /api/queues/{vhost}/{name}/contents) answers 204 No Content and offers no JSON representation, so content negotiation failed and the broker returned 406 with an empty body — on every purge, on every server. Accept is now application/json, */*; every other endpoint (GETs, PUT declare, DELETE queue, DELETE policy) was enumerated against a live broker and behaves identically either way. Verified on RabbitMQ 3.13.7 by purging a real 9-message backlog.
  • A 406 now explains itself. The broker sends no body with a 406, so the generic branch produced a message with nothing in it — and, because the platform label already ends in "API", it read "RabbitMQ management API API error". There is now a 406 branch naming content negotiation as the cause, and the generic branch no longer doubles the word.
  • Two more integer quantities stayed integers (bug class #2): a node's memUsedBytes / memLimitBytes came back as floats (161222656.0) while the diskFreeBytes beside them was an int — one payload disagreeing with itself — and the per-peer channels count rendered as 1.0 for one channel, from a 0.0 accumulator seed. Both found on a live broker; regression tests assert the type.
  • Write-path integer quantities stay integers (bug class #2/#4). ops/writes.py still rendered whole-second and count fields through the float helper num() — kill_client's priorState.ageSeconds came back as 49.0, and the RabbitMQ purge/policy captures rendered messages and priority as floats too. It was missed in the earlier read-path sweep (the module did not even import as_int) and was inconsistent with list_clients, which already rendered the identical CLIENT LIST age field as an int. Now uses as_int; a regression test asserts the type (equality cannot catch 49 == 49.0). Found live while verifying kill-client against a real blocked BLPOP client on Redis 7.4.