zaqar

Websocket message_delete_many doesn't use pop correctly

Bug #1653525 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Fix Released
Medium
Thomas Herve
zaqar ocata-3

Bug Description

The request specifies that the parameter is called "pop", but it tries to extract "pop_limit" instead. It should use pop.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to zaqar (master)

Fix proposed to branch: master
Review: https://review.openstack.org/416071

Changed in zaqar:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zaqar (master)

Reviewed: https://review.openstack.org/416071
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=39452c9a1caa24bc926c1c23a39a5d184bbcab89
Submitter: Jenkins
Branch: master

commit 39452c9a1caa24bc926c1c23a39a5d184bbcab89
Author: Thomas Herve <email address hidden>
Date: Mon Jan 2 16:41:47 2017 +0100

    Use pop in message_delete_many

    message_delete_many used by websocket incorrected made reference to the
    pop_limit argument, instead of using pop.

    Change-Id: I1c94ad82c3b20cc331045c19d4a9987a701b081b
    Closes-Bug: #1653525

Changed in zaqar:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/zaqar 4.0.0.0b3

This issue was fixed in the openstack/zaqar 4.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.