• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MITLibraries / s3-bagit-validator / 14406182936 / 1
91%
main: 90%

Build:
Build:
LAST BUILD BRANCH: v0.1.6
DEFAULT BRANCH: main
Ran 11 Apr 2025 03:07PM UTC
Files 8
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Apr 2025 03:02PM UTC coverage: 91.141% (+0.5%) from 90.646%
14406182936.1

push

github

ghukill
Bubble up handled exceptions into lambda response

Why these changes are being introduced:

It was pointed out that even for some handled exceptions (e.g.
a bad UUID) the error message returned by the Lambda + CLI was
still opaque.  Effort had gone into catching those cases and
providing meaningful python Exceptions, but they weren't getting
returned by the Lambda.

Turns out the CLI has some copy pasta for requests that was
raising an exception based on a HTTP status code, which was
short-circuiting the returning of those curated exceptions.

How this addresses that need:

Remove the .raise_for_status() call in the CLI which allows
the exceptions to get returned in the Lambda response.  Also,
improve exception handling to expose when a UUID is not found.

Side effects of this change:
* Lambda, and by proxy CLI, responses are improved with more
details when something fails

Relevant ticket(s):
* None

535 of 587 relevant lines covered (91.14%)

0.91 hits per line

Source Files on job 14406182936.1
  • Tree
  • List 8
  • Changed 3
  • Source Changed 2
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 14406182936
  • 013112a4 on github
  • Prev Job for on cli-errors-in-response (#14365782822.1)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc