PerforceExporter class has try block that obfuscates debugging from crash traceback

Bug #597535 reported by Chris J
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Fast Import
Invalid
Low
Jelmer Vernooij

Bug Description

I found a bug in the bzrp4 fast-import plugin where it would throw an exception from the main() call. This information was obfuscated by a try: around the main() call, without any catch: block. The finally: would run, but it would access a variable that would have been set during a successful try: run, which would then crash, giving the line in the finally: block as the line causing the crash. I would propose removing the try: block completely from bzr-fastimport/exporters/__init__.py: class PerforceExporter: def generate(). At the very least, adding a generic catch: block with enough documentation in the crash dump to diagnose what went wrong.

Tags: p4

Related branches

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Patches are welcome; unfortunately I don't have access to any perforce repositories so I can't test myself.

tags: added: p4
Changed in bzr-fastimport:
status: New → Triaged
importance: Undecided → Low
Jelmer Vernooij (jelmer)
Changed in bzr-fastimport:
status: Triaged → In Progress
assignee: nobody → Jelmer Vernooij (jelmer)
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I'm closing this as invalid as bzr-fastimport is no longer shipping fastexporters for other version control systems.

Changed in bzr-fastimport:
status: In Progress → Invalid
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.