Conversation
7ttp
marked this pull request as ready for review
October 2, 2026 21:23
7ttp
added this pull request to stack #6969
October 2, 2026 21:25
Contributor
There was a problem hiding this comment.
🤖 AI Review
Verified all four findings and merged the duplicate cleanup reports into three entries. Two findings are confirmed, including a temp-file leak that predates this PR. The claimed cleanup regression is refuted: an in-memory comparison using the trusted bundled Effect implementation showed that both versions propagate cleanup rejection as a defect.
Findings
| Severity | Location | Category | Sources | Claim |
|---|---|---|---|---|
| 🟡 MINOR | apps/cli/src/shared/functions/download.ts:666 |
error-handling |
claude | A writeAll failure leaves the already-created .supabase-download-.tmp file in the destination directory. |
| 🟡 MINOR | apps/cli/src/shared/functions/download.errors.ts:48 |
telemetry |
codex | FunctionEszipDownloadError lacks the required actionability getter and stable fingerprint declaration for an app-owned untagged error class. |
Refuted findings (kept for transparency, not posted as review comments)
apps/cli/src/shared/functions/download.ts:686(error-handling): The PR introduces a regression where failed rename cleanup becomes a defect, replacing the typed download error and bypassing partial-download reporting; previously cleanup failure was ignored.
Refuted: The current defect behavior exists, but it is not introduced by this PR. Effect.promise turns promise rejection into a defect, and Effect.ignore suppresses typed failures only. Executing both cleanup compositions with the trusted bundled Effect implementation produced the same Die reason carrying the cleanup error. The old implementation therefore also lost the rename error and bypassed typed partial-download reporting.
Stats
Claude findings: 2 · Codex findings: 2 · Confirmed: 2 · Refuted: 1 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
brings the
functionsdownload, delete, config and shared helpers under the effect lintwhats introduced?
download,delete,functions-api,functions.sharedandfunctions-configmodules join the allow list file by file, so the rest ofshared/functionswaits for the later PRs in this stackdownloadruns on theFileSystemandPathservices instead ofnode:fsandnode:path, with a posixPathfor container and API pathswx, renames into place and is removed when the rename failsErrorfailures on the eszip path become an untaggedFunctionEszipDownloadErrorwith the same telemetrySchema, so a malformed response now readsExpected a valid JSON stringinstead of the parser messagedownloadFunctionsanddeleteFunctionbecomeEffect.fnwith the same span namesref