Skip to content

[bulk][split-218 #137] Clean error messages instead of stack traces (bu-9jr) - #47

Closed
relentlesscol wants to merge 1 commit into
mainfrom
polecat/bu-9jr
Closed

[bulk][split-218 #137] Clean error messages instead of stack traces (bu-9jr)#47
relentlesscol wants to merge 1 commit into
mainfrom
polecat/bu-9jr

Conversation

@relentlesscol

Copy link
Copy Markdown
Owner

Summary

Issue awslabs#137. When a command fails due to bad parameters in the driver, show a clean human-readable error message instead of a Python stack trace.

TDD REQUIRED: (1) Write a failing unit test that asserts bad-param errors produce clean messages (no traceback). (2) Implement the error handling. (3) make test must pass. (4) This changes user-facing error output — add e2e test. Single-issue PR.

Files: client/src/runner.py. Tests: tests/client/ + tests/e2e/commands/.

Implementation notes

Implemented: clean error messages in runner.py instead of stack traces (issue awslabs#137). TDD unit tests + e2e test added. All 1328 tests pass.

Refinery handoff

  • Issue: bu-9jr (task, P2)
  • Source branch: polecat/bu-9jr
  • Target: main
  • Rebased on main via Gastown Refinery.

…awslabs#137)

When a command fails due to bad parameters or runtime errors in the
driver, users now see a clean human-readable error message instead of a
raw Python stack trace. The run() method catches exceptions from the job
execution path and calls sys.exit() with a formatted message.

TDD: wrote failing unit tests first, then implemented the fix.
Added e2e tests verifying no tracebacks for common bad-input scenarios.
@relentlesscol

Copy link
Copy Markdown
Owner Author

Promoted to upstream: awslabs#227

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant