incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Van Steenburgh" <>
Subject [allura:tickets] #6530 Improve error handling / reporting on tool importer failure
Date Tue, 03 Sep 2013 20:19:59 GMT
Refactored error handling into a context manager which posts an event, but allows the exc to
propagate up.

New commits on forge, googlecodewikiimporter, and tracwikiimporter repos.


** [tickets:#6530] Improve error handling / reporting on tool importer failure**

**Status:** code-review
**Labels:** import 
**Created:** Wed Aug 07, 2013 08:46 PM UTC by Cory Johns
**Last Updated:** Tue Sep 03, 2013 03:38 PM UTC
**Owner:** Tim Van Steenburgh

Currently, if a tool importer fails, the only record of the failure is in the monq_task record.
 Failures need to be caught and the users notified in some way.  A catch-all should be put
in place in the `import_tool` task, but individual tools may want to handle reporting differently,
such as the repo clone failure notification that is already in place and we need to ensure
that the catch-all doesn't duplicate any per-tool handling.

Partial imports also need to be considered and we might want to decide if a partially failed
import is worth rolling back the entire tool import or if the importer should handle a failed
ticket, e.g., gracefully and continue to import the rest of the tickets if possible.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message