Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mat
mat
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • mat
  • matmat
  • Issues
  • #11528

Closed
Open
Opened Mar 19, 2017 by intrigeri@intrigeriMaintainer

Please communicate to the user any failure in the Nautilus extension

I did a blame-free post-mortem of https://bugs.debian.org/858058 (aka. #11527). It happened because of the combination of a number of small failures and missing pieces:

  • lack of automated QA for this feature: requested autopkgtests in Debian on https://bugs.debian.org/858204, upstream tests would be welcome as well but that's not what this ticket is about
  • lack of manual QA for this feature: I'll ignore this for now, hoping that automated QA is implemented soon enough; if this doesn't happen we should probably consider documenting a manual test suite in our release process doc
  • developers not testing the code they just refactored: I don't think we can do much about this, except learning from this sad experience
  • menu_activate_cb in nautilus/nautilus-mat.py being overly self-confident, and thus not robust enough in face of programming errors => silently failing

This ticket is about the last of these root causes: perhaps menu_activate_cb should wrap all its code in a try/catch block, and display an error dialog to the user if any unhandled exception is raised.

Thoughts?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mat/mat#11528