Can't use queue.pop

Bug #1446679 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python client library for Zaqar
Fix Released
Undecided
Unassigned

Bug Description

When trying to use queue.pop with a client on 1.0 version, the client fails with the following error:

  File "/opt/stack/python-zaqarclient/zaqarclient/queues/v1/queues.py", line 198, in pop
    msgs = core.message_pop(trans, req, self._name, count=count)
  File "/opt/stack/python-zaqarclient/zaqarclient/queues/v1/core.py", line 339, in message_pop
    transport.send(request)
  File "/opt/stack/python-zaqarclient/zaqarclient/transport/http.py", line 106, in send
    raise self.http_to_zaqar[resp.status_code](msg)
zaqarclient.transport.errors.MalformedRequest: The "ids" query parameter is required.

If we bum the version to 1.1, it fails with a different error:

  File "/opt/stack/python-zaqarclient/zaqarclient/queues/v1/iterator.py", line 98, in __next__
    args = self._listing_response.pop(0)
AttributeError: 'NoneType' object has no attribute 'pop'

The first one should probably fails with a better error. The second one should just work, I think :).

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-zaqarclient (master)

Reviewed: https://review.openstack.org/177792
Committed: https://git.openstack.org/cgit/openstack/python-zaqarclient/commit/?id=0047c541169747064b57464d6dcd0c07958c27e9
Submitter: Jenkins
Branch: master

commit 0047c541169747064b57464d6dcd0c07958c27e9
Author: Thomas Herve <email address hidden>
Date: Mon Apr 27 16:33:51 2015 +0200

    Fix handling of 1.1 API

    This fixes various behaviors of the client talking to the v1.1 API, and
    enables functional tests for queues.

    Change-Id: Icd30e32a17247790dfd57d6420d67f9140020db6
    Closes-Bug: #1446677
    Closes-Bug: #1446679

Changed in python-zaqarclient:
status: New → Fix Committed
Changed in python-zaqarclient:
milestone: none → 0.2.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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