Rethrow Panic from runners and narrow gen() result semantics

[adelrodriguez]

This pull request implements critical correctness fixes for error handling and panic semantics across the hardtry library.

Key Changes:

• Panic rethrow behavior: run() and runSync() now rethrow user-thrown Panic instances instead of wrapping them, ensuring panic semantics remain consistent and preventing retry attempts on control errors
• Simplified control error detection: Introduced ControlError base class for CancellationError and TimeoutError, replacing the checkIsControlError() utility function with direct instanceof checks
• Generator failure semantics: gen() now throws unexpected failures unchanged while keeping GenResult narrow to only include explicit yielded/returned error values, avoiding the need to widen the public type with UnhandledException
• Updated documentation: README now clarifies that run() and runSync() never return Panic as a result value

Test Coverage:

• Added tests verifying Panic rethrow behavior in both sync and async execution paths
• Updated generator tests to validate throw-through semantics for unexpected failures
• Ensured retry logic correctly skips Panic instances

This maintains backward compatibility for normal error handling while fixing edge cases where control errors were incorrectly wrapped or returned as values.

[adelrodriguez]

• Fix race condition in TaskExecution abort test with proper synchronization #32
• Rethrow Panic from runners and narrow gen() result semantics #31 👈 (View in Graphite)
• Change driveGen to throw errors instead of returning UnhandledException #30
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Warning

Rate limit exceeded

@adelrodriguez has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 602de436-0c61-482f-933f-b13985c22882

📥 Commits

Reviewing files that changed from the base of the PR and between 6c0cfde and c8ca403.

📒 Files selected for processing (11)

• .plans/01-pr-18-review-triage-checklist.md
• README.md
• src/__tests__/index.test.ts
• src/lib/__tests__/gen.test.ts
• src/lib/__tests__/utils.test.ts
• src/lib/errors.ts
• src/lib/executors/__tests__/run.test.ts
• src/lib/executors/base.ts
• src/lib/executors/run-sync.ts
• src/lib/executors/run.ts
• src/lib/utils.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 03-07-rethrow_panic_from_runners_and_narrow_gen_result_semantics

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[adelrodriguez]

@codex review
@coderabbitai review

[coderabbitai]

@adelrodriguez Sure, I'll review the changes in this PR!

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. More of your lovely PRs please.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[adelrodriguez]

Merge activity

• Mar 7, 6:10 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 7, 6:10 PM UTC: @adelrodriguez merged this pull request with Graphite.