Create link oopses for some bug reports

Bug #1197186 reported by Brian Murray
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Errors
Fix Released
High
Martin Pitt

Bug Description

Here is an oops I ran into when trying to create a bug for the following bucket.

oops - https://oops.canonical.com/oops/?oopsid=OOPS-e54efa27e6bd107118b6af850ac4dc5d
bucket - https://errors.ubuntu.com/problem/68e576567769567a41a8363ced0b6322a2230066

The bucket seems to have some unicode in it:

'/usr/bin/update\u002Dmanager:python: ../../src/xcb_io.c:529: _XAllocID: Zusicherung \u005C302\u005C273ret !\u003D inval_id\u005C302\u005C253 nicht erf\u005C303\u005C274llt.'

I wonder if there is an issue when posting to Launchpad with this as the bug title.

Related branches

Changed in errors:
importance: Undecided → Low
Changed in errors:
importance: Low → High
Revision history for this message
Brian Murray (brian-murray) wrote :

The CreateBugResource in errors/api/resources.py actually calls create_bug() from daisy's launchpad.py code. However, this might just be a matter of cleaning up the bucket before handing it to create_bug().

Revision history for this message
Brian Murray (brian-murray) wrote :

There is another example of this in the duplicate report.

Revision history for this message
Martin Pitt (pitti) wrote :

I can reproduce this now.

Changed in errors:
assignee: nobody → Martin Pitt (pitti)
status: New → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

For a dupe signature with just \ I get the exact same trace as in https://oops.canonical.com/oops/?oopsid=OOPS-e54efa27e6bd107118b6af850ac4dc5d.

However, with some more UTF-8 fun I get a different one:

  DuplicateSignature: foo!☺-'\"&ab

yields

  File "/usr/lib/python2.7/dist-packages/tastypie/resources.py", line 217, in wrapper
    response = callback(request, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/tastypie/resources.py", line 459, in dispatch_list
    return self.dispatch('list', request, **kwargs)
  File "/srv/errors.staging.ubuntu.com/devel/errors/errors/metrics.py", line 40, in wrapper
    result = view(*args, **kwargs)
  File "/srv/errors.staging.ubuntu.com/devel/errors/errors/api/resources.py", line 94, in dispatch
    return Resource.dispatch(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/tastypie/resources.py", line 491, in dispatch
    response = method(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/tastypie/resources.py", line 1357, in post_list
    updated_bundle = self.obj_create(bundle, **self.remove_api_resource_names(kwargs))
  File "/srv/errors.staging.ubuntu.com/devel/errors/errors/api/resources.py", line 345, in obj_create
    metadata = cassandra.get_metadata_for_bucket(bucket)
  File "/srv/errors.staging.ubuntu.com/devel/errors/errors/cassandra.py", line 309, in get_metadata_for_bucket
    return bucketmetadata_cf.get(bucketid, column_finish='~')
  File "/usr/lib/pymodules/python2.7/pycassa/columnfamily.py", line 652, in get
    read_consistency_level or self.read_consistency_level)
  File "/usr/lib/pymodules/python2.7/pycassa/pool.py", line 589, in execute
    return getattr(conn, f)(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/pycassa/pool.py", line 125, in new_f
    result = f(self, *args, **kwargs)
  File "/usr/lib/pymodules/python2.7/pycassa/cassandra/Cassandra.py", line 579, in get_slice
    self.send_get_slice(key, column_parent, predicate, consistency_level)
  File "/usr/lib/pymodules/python2.7/pycassa/cassandra/Cassandra.py", line 589, in send_get_slice
    args.write(self._oprot)
  File "/usr/lib/pymodules/python2.7/pycassa/cassandra/Cassandra.py", line 3322, in write
    oprot.trans.write(fastbinary.encode_binary(self, (self.__class__, self.thrift_spec)))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u263a' in position 4: ordinal not in range(128)

We should fix both issues.

Martin Pitt (pitti)
Changed in errors:
status: In Progress → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

It's not actually deployed yet.

Changed in errors:
status: Fix Released → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

This now works with the bug from the description, thanks!

Changed in errors:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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