Skip to article frontmatterSkip to article content

Improve nbgitpuller error handling

Sub-issues
  • #7084 - Identify common nbgitpuller errors

  • #7082 - Add access to a Jupyter frontend following an nbgitpuller error

  • #7083 - Redesign nbgitpuller error handling response for link-consumers

  • #7085 - Design and integrate dedicated error handlers

  • #7104 - Write a blog post about the nbgitpuller error handling work

Participate in the issue: github.com/2i2c-org/infrastructure/issues/6442

Context

Replace technical error messages with human-readable feedback and provide an “escape hatch” link to the Jupyter environment so that non-technical users like students aren’t stranded when nbgitpuller links fail. See the Statement of Work for details.

What we need to do

Improve nbgitpuller error handling as per this SoW


Status: Upcoming P&S initiatives

Funding Status: Co-funded

Back to: All Initiatives