Error handling in garden-ai publish has a feast or famine dynamic. If a fatal error happens while building your container and you haven't used the --verbose flag, you basically get no explanation of what went wrong. If you do use the verbose flag, then you get some big typer stack traces and if you scroll up a bit in your terminal you can see the error message you needed to see.
How to repro:
Use garden-ai start to make a notebook with a glaring Python error. Divide by 0 or something.
Try to publish it with garden-ai publish with and without --verbose
We should give the right error message to explain where a user should try to fix their notebook without --verbose. With --verbose we should highlight the helpful message and not show irrelevant stack traces.
Error handling in
garden-ai publishhas a feast or famine dynamic. If a fatal error happens while building your container and you haven't used the--verboseflag, you basically get no explanation of what went wrong. If you do use the verbose flag, then you get some big typer stack traces and if you scroll up a bit in your terminal you can see the error message you needed to see.How to repro:
garden-ai publishwith and without --verboseWe should give the right error message to explain where a user should try to fix their notebook without
--verbose. With--verbosewe should highlight the helpful message and not show irrelevant stack traces.Assumptions:
1. 2.
Acceptance Criteria
Given..., when..., then...