[robobun]

Behaviour change: none

Problem

• Three items cannot run, or hold a value that nothing reads. Progress.dont_print_on_dumb is false in every Progress. Tag::infer makes two hosted-git lookups that cannot change its answer. Five variants of bun_jsc::Error are never constructed.
• rustc does not report them. Its dead_code lint skips a pub field and the variants of a pub enum.

Fix

• Delete them: 40 lines removed in 3 files, none added.
• Correct because no code on main reads, sets or constructs them, and the 12 CI targets compile without them.
• Verified on this head: bun bd, bun run rust:check-all, cargo clippy, cargo check --workspace --all-targets, cargo fmt --check, 4 test files (Notes).
• Self-reviewed: 22 concerns raised, 22 addressed. The first push removed 435 lines: the rest collides with open pull requests (Notes).

Background

• Tag::infer classifies a dependency specifier. For a git:// or git+http(s):// URL it also asked HostedGitInfo::from_url. hgi_to_tag maps that result to Tag::Github only for a shortcut such as github:user/repo, which these URLs never are. Every other result is Tag::Git, which the next statement returns.
• No other design was weighed: a deletion has one place.

Downsides

• None found. Checked: a trial merge with each other open pull request adds no conflict, and none uses a removed name (Notes).

Notes

Removed

1. bun_core::Progress.dont_print_on_dumb (src/bun_core/Progress.rs): the field, its default, and the early return in refresh_with_held_lock that tests it. No code sets it, so it is false in every Progress. The last tree with the Zig sources (d4514457e8^) never set it either.
2. Tag::infer in src/install/dependency.rs: the two HostedGitInfo::from_url lookups for git:// and git+http(s):// inputs.
   • hgi_to_tag returns Tag::Github only when the representation is Shortcut.
   • from_url gives Shortcut only for the protocols github:, gist:, gitlab:, bitbucket: and sourcehut:, or for a user/repo shorthand.
   • is_github_shorthand rejects an input with a : before a #, and normalize_protocol reads git:, git+http: or git+https: from these inputs.
   • So the lookup gives Tag::Git or fails, and both cases reach return Tag::Git.
3. Five variants of bun_jsc::Error that nothing constructs (src/jsc/error.rs): InvalidDataURL, InvalidURL, TarballFailedToExtract, MissingDebugInfo, EndOfFile, with their name() arms. Other crates have variants with the same names in their own Error enums. The enum has no repr and no conversion from a number or a string.

Open pull requests

• Compared at 2026-10-31 23:10 UTC, with main at 89fbb78, with the heads of all 5,931 other open pull requests, drafts and every author included. Earlier comparisons ran on 2026-10-18, 2026-10-20 and 2026-10-21.
• A trial merge of each head with main and with this branch (git merge-tree) shows that the branch adds no conflicted file and no conflict hunk.
• None adds a use of a removed name. The added lines of every head were searched for dont_print_on_dumb and for the five variant names in bun_jsc.
• Two items went back after the PR opened, because an open pull request started to collide with them: the Result of ModuleInfo::finalize (Build every runtime ES module's record from the transpiler output instead of a second JSC parse #35605) and SignResult.request_payer (s3: add tagging option and route write headers through one carrier #46746, s3: send the contentDisposition given to file() or new S3Client(), and keep contentEncoding on the upload call #46863). Both are in the list below.

Found dead in this run, and left alone

The first push of this PR removed 24 items (435 lines). My check of the open pull requests was too weak then: it compared only the lines that they remove or change. The trial merge above, run for that first head, adds a conflicted file to 32 open pull requests (11 of them merge clean today) and more conflict hunks to 20, 49 pull requests in total. Open pull requests also use eight of the removed items. Each item below has no reader or constructor on main and compiled away on 12 targets. A later run can take it when its blocker lands or closes. The blockers are as of 2026-10-18, except where a bullet gives a later date.

An open pull request uses the item:

• The Result of ModuleInfo::finalize in js_printer, which is never Err, with the error arms of its three callers. It was in this PR until 2026-10-20. Build every runtime ES module's record from the transpiler output instead of a second JSC parse #35605 now adds a caller that tests the Result, and it edits the function.
• BundleOptions.code_coverage, which bun test --coverage sets and nothing reads: bun test: count code that runs in a Worker under --coverage #43283 and bun test: ignore the next original source line in coverage #44228 read it. Remove dead code from the class generator: the unreachable DOMJIT paths #43840 held it for the same reason.
• The thread-local IS_MAIN_THREAD_VM, set_is_main_thread_vm and its six writes: fuzzilli: run every REPRL program on a fresh global object #42027 adds a call.
• bun_jsc::Error::ParserError: Import C: .c files as modules, compiled by Bun and JavaScriptCore's B3 #42671 constructs it.
• ImportWatcher::None in src/jsc/hot_reloader.rs: watcher: watch a file before it is read, not after it is parsed #42749, watcher: add a stat-polling backend for --watch and --hot #42750 and bun test --watch: run a test file that is added after the first run #42810 each add an arm for it.
• picohttp::Request.minor_version and bytes_read: HTTP client: remove unsafe from src/http (h1/h2/h3 client, proxy tunnel, HTTP thread, keep-alive pool) #40385 and picohttp: add lifetime parameter to Header #31179 build a Request with both. http: replace picohttpparser with a Rust parser; classify headers once and build fetch Response headers lazily #37132 rewrites the struct.
• bun_core::strings::Encoding::{Ascii, Utf16}: Escape 16-bit strings and object keys like 8-bit ones (console.log, bun:test, JS printer) #42320 and Deduplicate bundler dispatch and output glue, the JS string escaper, and the exports-map retry #31998 add arms for them.
• In src/runtime/api/cron.rs, the Result of xml_escape, alloc_print_z and the XML and calendar helpers, with nine "Out of memory" arms (about 120 lines): fix(cron): preserve DOM/DOW syntactic restriction in OS-registered jobs #29143, fix(cron): write macOS launchd logs to ~/Library/Logs, not /tmp #29144 and fix(cron): set working directory to caller's cwd at registration time #29147 call them with ? or map_err. filter_crontab has the same shape.

The removal adds a merge conflict to an open pull request:

• SignResult.request_payer, which sign_request writes and nothing reads. It was in this PR until 2026-10-31. s3: add tagging option and route write headers through one carrier #46746 and s3: send the contentDisposition given to file() or new S3Client(), and keep contentEncoding on the upload call #46863 now edit the lines next to its store.
• In bun_jsc::Error: impl From<ErrorCode> and impl From<bun_uws::ConnectError>, with the variants ErrorCode and FailedToOpenSocket that only they construct. Another sweep found them on 2026-10-31, and the workspace compiles without them. Rewrite the uSockets core in Rust #34037 edits the second impl, Remove dead code from the WebCore bindings and 20 Rust crates #40525 removes the variants next to ErrorCode, and Throw when a V8 heap snapshot is too large to serialize #46893 adds a variant next to FailedToOpenSocket.
• The parser's Options.transform_only: bun test: Vitest compatibility #44833, bun:dom and the Vitest work in one tree (not for merging) #45415, Remove dead code from bun_bundler, the JS parser, the help command, and PackageJSONEditor #44687, parser: require the tsconfig options in ParserOptions::init, fix scanImports on decorators and accessor fields #45557.
• The parser's Options.keep_names (always true): js_parser: validate TypeScript class member modifiers like esbuild #40817, Delete the schema::api mirror types and bun_api; one loader numbering across Rust/C++/JS #37095.
• The one_shot parameter of io::Poll::register_for_epoll and Flags::OneShot: Remove dead code from js_printer, bun_io, and UpdateRequest #44293, Replace boolean flag parameters with two-variant enums #37180, FileSink, Bun.write: remove unsafe from FileSink.rs and blob/write_file.rs #40213, Blob, Bun.file: remove unsafe from Blob.rs, read_file.rs, copy_file.rs and Store.rs #40221, S3 client + Bun.WebView host: remove unsafe from webcore/s3 and webview #40252, webcore: remove unsafe from Response/Request/Body/ReadableStream/FileReader/Sink #40411, fix(io): emulate EPOLLONESHOT with DEL + ADD #40473, io: hand ReadFile/WriteFile to the io thread through the owner's pointer, not &mut self.io_request #37787.
• BundleOptions.preserve_extensions: Make --preserve-symlinks and --preserve-symlinks-main work in the runtime and bundler #36757.
• SignResult.acl: s3: sign without fixed-size buffers, write each output once #45440. SignResult.storage_class sits between the same lines and is also only written.
• EventLoop.waker: Remove libuv on Windows #42819.
• The const generic KIND of ArrayBuffer::alloc with Bun__allocUint8ArrayForCopy: Make unrooted JSValues, views across JS re-entry, and JSC buffer-ownership contracts compile errors #34230, Bun.DurableObject #42984, Rename Zig-prefixed identifiers to Bun/Rust equivalents #30747, Remove cross-crate layering workarounds #33152. Remove dead code from react_compiler, the WebCore/IDL bindings, install_jsc, node-fallbacks, and misc crates #39420 kept the Uint8Array arm on purpose, so that alloc mirrors create. Remove dead code from JSWebSocket, ArrayBuffer::alloc, and Subprocess #46140 is now open and removes Bun__allocUint8ArrayForCopy.
• Scanner.exclusion_names in bun test: bun test --watch: run a test file that is added after the first run #42810.
• The locals phase and did_succeed in read_file_with_options: fs.readFile: honor AbortSignal between read chunks #36259, node:fs: stop a readFile of a pipe or device when its worker is terminated #40207.
• WrappedIterator.name_filter on non-Windows targets: Resolve readdir entries of unknown type in the remaining consumers (create, bin links, bunx, fs.watch, cp, ls, init) #38961.
• Bits::drain() in codec_gif.rs: Add space, channels, and hasAlpha to Bun.Image metadata() #31899 edits the test line beside the comment that names it.
• The thread-local EXCEPTION_HOLDER in js_parser_jsc/Macro.rs: macros: run every macro on one dedicated VM thread #40059.
• The image_src and image_title restores in md/ansi_renderer.rs: Bun.markdown.ansi: show image URL and cap Kitty image width #29131.
• G::Comment.loc: js_parser: keep @license and @preserve comments, and keep legal comments across import() #41013.
• Framework.is_built_in_react and FrameworkServerComponents.separate_ssr_graph in the parser's copy of the framework options: Remove cross-crate layering workarounds #33152.

How the candidates were found

• A probe build. In a scratch copy, struct fields got a unique #[deprecated] tag, and cargo check --workspace for Linux, Windows and macOS listed every use site. A field with only initializer and assignment sites is write-only.
• The tagger has a defect: it skips the field after each field that it tags. It tagged 16,242 of about 28,500 fields, so about 43% of the fields were never probed. Two untested neighbours of items above are BundleOptions.debugger and SignResult.storage_class.
• A read-only audit of 51 units of about 10,000 lines each, for write-only state, parameters with one value, results that cannot fail and variants that nothing constructs. Two more readings tried to refute each finding, also against the last Zig tree.
• Also dry: a relink of the debug binary with --gc-sections --print-gc-sections (131 unreachable C-linkage functions, 101 of them already in open pull requests, the rest platform code), clang with -Wunused-function over the C++ bindings, files in no mod tree or build target, unused Cargo dependencies.

Leads, not applied

State with a missing reader or writer. The audit reported these, and I did not verify them:

• virtual_machine::Options.dns_result_order is set for compiled executables and never copied into the VM. Forward --inspect and --dns-result-order to the VM in compiled executables #40703 is open for it.
• bunfig [debug].editor is stored and never read. Bun.openInEditor: use the [debug] editor setting from bunfig.toml #38059 is open for it.
• js_parser: the deferred await and yield errors of arrow arguments go into a copy that is thrown away.
• js_parser: PropertyOpts.declare_range is never set.
• ParseResult.pending_imports is always empty, so nothing feeds the AsyncModule queue.
• Bun.build: Config.dir and Config.css_chunking are never set from JS. bun:ffi cc(): library_dirs is never assigned. bunfig [bundle].packages is stored and never read.
• extract_blob in spawn/stdio.rs compares the stdio slot index with itself.

Unfinished work, not dead code: P::keep_expr_symbol_name returns its argument unchanged. It is the --keep-names hook, and #40503 implements that feature.

The same class as ModuleInfo::finalize, for a later run: Stdio::as_spawn_option, Log::clone_to_with_recycled, and the StreamBuffer and ByteVecExt writes never return Err. JsSinkType::HAS_FLUSH_FROM_JS is true in all six impls. Stdio::Memfd exists only as stdin. Open pull requests edit the same lines (#42819, #43896, #44301, #44493, #45591, #43709, #43737).

Verification

• On this head (57b8496, after a merge of main at 89fbb78): bun bd, cargo check --workspace, cargo check --workspace --all-targets, cargo clippy --workspace --no-deps, cargo fmt --all -- --check, and bun run rust:check-all (12 ok, 0 failed, 0 skipped (of 12)).

Tests, debug build of this head

• test/cli/install/hosted-git-info/from-url.test.ts: 685 pass, 32 skip.
• test/cli/install/bun-install-git-deps.test.ts: 201 pass, 1 skip.
• test/cli/install/migration/yarn-lock-migration.test.ts: 69 pass.
• test/cli/install/bun-add.test.ts: 220 pass.

---

no test proof · iteration 0 · the description declares no behaviour change, so there is no failing test to prove; the existing suite in CI is the check

[robobun]

^{Updated 9:07 PM PT - Oct 31st, 2026}

✅ @robobun, your commit 57b8496c15a14c25fcc83a43611fd6a68f30d4ab passed in Build #136262! 🎉

---

🧪   To try this PR locally:

bunx bun-pr 45974

That installs a local version of the PR into your bun-45974 executable, so you can run:

bun-45974 --bun

[robobun]

Status: ready for review. Nothing has failed in CI. The Buildkite build cannot finish because one lane has no agent.

• This PR deletes code that cannot run or that nothing reads, so there is no repro. The PR body lists each of the three items with its proof.
• GitHub checks on the head 57b8496: all eight are green (cargo clippy, cargo miri test, Format, Source lints, Lint JavaScript, lol-html cargo test, mordant, comment-cop).
• Buildkite build 136262 on the same head, read at 2026-11-01 03:06 UTC: 184 of 188 jobs passed and 0 failed. The other 4 are the darwin any x64 - test-bun shards. No agent of queue=test-darwin, arch=x64 has started them in more than 3 hours, so the build still shows as running.
• The build lists some tests as flaky (most are in test/aot/). Each one passed on a retry or when run alone, and none of them touches the three files of this diff.
• Checked locally on that head: bun bd, bun run rust:check-all (12 of 12), cargo clippy, cargo check --workspace --all-targets, and the four test files that the Notes list.
• A trial merge with the heads of all 5,931 other open pull requests adds no conflict, and none of them uses a removed name. Last comparison: 2026-10-31 23:10 UTC.

[claude]

Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.

Beyond the inline comment, I also checked a few of the deletions for hidden behaviour changes and found none: both register_for_epoll callers passed one_shot=true and the Flags::OneShot reads that remain are on the separate posix_event_loop flag set; HostedGitInfo::from_url on git:///git+http(s):// input never yields a Shortcut representation, so hgi_to_tag could only return Tag::Git; and Bits::drain in the GIF decoder only advanced a cursor that decode_frame returns without reading.

Extended reasoning...

Dead-code sweep across 40 Rust files plus one C++ extern removal, with no security-sensitive surface touched (the cron.rs changes only drop unreachable OOM arms around infallible Vec writes). The one posted finding is a stale SAFETY comment in linker.rs that still names the deleted preserve_extensions field; the ruled-out items above were re-verified from the code rather than the PR description.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

• Last reviewed commit: 57b8496

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• Resume reviews
• Trigger review

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: oven-sh/bun
• Branch: robobun/9b78bd75/dead-code-sweep
• File: .coderabbit.yaml
• Commit: 57b8496
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: a833e150-06c7-4712-b8ba-c895197ad1f1

Commits

Reviewing files that changed from the base of the PR and between 0f2f9e3 and 57b8496.

Files selected for processing: 3

• src/bun_core/Progress.rs
• src/install/dependency.rs
• src/jsc/error.rs

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

Walkthrough

The pull request removes a progress-printing option, changes Git URL tag inference to stop consulting hosted-provider metadata, and removes five variants from the public Error enum and their name mappings.

Changes

Progress Rendering

Layer / File(s)	Summary
Progress refresh behavior src/bun_core/Progress.rs	Progress no longer has the dont_print_on_dumb field or its default. Refresh no longer skips rendering based on that option.

Git Dependency Tag Inference

Layer / File(s)	Summary
Git URL tag selection src/install/dependency.rs	For git:// and recognized git+http(s):// URLs, Tag::infer no longer uses hosted-provider metadata to select a tag. GitHub shorthand still returns Github; other inputs in these branches return Git.

Public Error Variants

Layer / File(s)	Summary
Error variants and name mappings src/jsc/error.rs	The Error enum no longer includes InvalidDataURL, InvalidURL, TarballFailedToExtract, MissingDebugInfo, or EndOfFile. Their name mappings are also removed.

Suggested reviewers: jarred-sumner

Merge Risk: Minimal · up to 57b84

No actionable blocker is established for this cleanup. It appears mergeable subject to normal build and test checks.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely identifies the three main dead-code removals described in the changeset.
Description check		The description explains what the PR changes and provides detailed verification results, including build, lint, formatting, and test checks. It does not use the exact template headings, but it contain…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description explains what the PR changes and provides detailed verification results, including build, lint, formatting, and test checks. It does not use the exact template headings, but it contains the required information.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[robobun]

The review found one stale comment: the SAFETY comment of Linker::options named preserve_extensions, which this PR deletes. f43c374 names rewrite_jest_for_tests in its place, the other field that the one caller reads.

341e416 answers the two comment-length notes: the doc comment of js_printer::Encoding is one line now, and the one on bun_core::printer::write_pre_quoted_string is back to its text from main.

No code changed in these two commits. The diff is now 41 files, +93 and -435 lines.

[claude]

I re-reviewed the current head after the follow-up commits and found no bugs; the stale preserve_extensions reference in the Linker::options SAFETY comment is now updated. Because this sweep spans 41 files including macOS/Windows-only cron paths and Linux epoll code that cannot be type-checked from one target, a human look is still worthwhile.

What was reviewed:

• Tag::infer git-URL fallback: traced HostedGitInfo::from_url → hgi_to_tag; Representation::Shortcut (the only path to Tag::Github) requires a github:-style protocol, which git:///git+http(s):// inputs never produce, so Tag::Git is the only outcome.
• Flags::OneShot removal in src/io/lib.rs: the remaining Flags::OneShot hits are on the separate posix_event_loop::Flags enum; register_for_epoll is pub(crate) with only the two true callers.
• Grepped the whole tree for Bun__allocUint8ArrayForCopy, IS_MAIN_THREAD_VM, ImportWatcher::None, ArrayBuffer::alloc::<, the removed jsc::Error variants and strings::Encoding::{Ascii,Utf16} — no remaining references (the Encoding::Utf16 hits are the separate js_printer, bun_ast::e::StrEncoding and StandaloneModuleGraph enums).
• codec_gif Bits::drain, ansi_renderer src/title restores (fields are .take()n before), the non-Windows drop(iter) in prune.rs, and the node_fs did_succeed/phase locals: confirmed nothing reads the removed state afterwards.

Extended reasoning...

The change is a dead-code removal sweep across 41 files (+93/-435): write-only struct fields, never-constructed enum variants, infallible functions losing Result wrappers, a thread-local, one C++ export, and an always-true epoll parameter. It touches no auth, crypto, or input-validation logic; the s3_signing change only drops two unread SignResult fields and the cron.rs changes only remove unreachable OOM arms. Every removal I could trace statically checks out as dead, and the one nit from the prior review was addressed in f43c374. Deferral rather than approval is because of the size and the amount of cfg-gated macOS/Windows/Linux-only code whose compilation I could not verify here; no CODEOWNERS entry covers the changed files and no third-party objection is open.

[robobun]

I moved this PR back to draft. Do not merge the current head (341e416).

A review of the diff against the heads of the open pull requests found that some of the removed items are used by open work. My first check compared only the lines that open PRs remove or change. It did not search the lines that they add, and it did not run trial merges.

Open PRs that use an item this PR removes (each one merges without a conflict and then does not compile):

• BundleOptions.code_coverage: bun test: count code that runs in a Worker under --coverage #43283 and bun test: ignore the next original source line in coverage #44228 read it.
• VirtualMachine::set_is_main_thread_vm: fuzzilli: run every REPRL program on a fresh global object #42027 calls it.
• bun_jsc::Error::ParserError: Import C: .c files as modules, compiled by Bun and JavaScriptCore's B3 #42671 constructs it.
• ImportWatcher::None: watcher: watch a file before it is read, not after it is parsed #42749, watcher: add a stat-polling backend for --watch and --hot #42750 and bun test --watch: run a test file that is added after the first run #42810 add a match arm for it.

Removals that add a merge conflict to open PRs: the parser's Options.transform_only (#44833, #45415, #45557, #44687), one_shot and Flags::OneShot in bun_io (#44293), BundleOptions.preserve_extensions (#36757), SignResult.acl (#45440), EventLoop.waker (#42819).

I will put these items back on this branch, run the checks again, check the trimmed diff with a trial merge against every open PR head, and then rewrite the description.

[claude]

LGTM — the trimmed-down removal set is behavior-preserving; each deletion checks out against the code.

What was reviewed:

• Traced Tag::infer's dropped HostedGitInfo::from_url fallback: for git:// and git+http(s):// inputs, normalize_protocol yields Git/GitPlusHttp(s), is_github_shorthand rejects on the early :, and correct_url can only produce GitPlusSsh, so Representation::Shortcut (the only route to Tag::Github) is unreachable and the result was always Tag::Git.
• Read ModuleInfo::finalize end to end: no ? or Err, so the three dropped error arms (Alloc mapping, None return, module_info = None; continue) could not run.
• Confirmed the remaining MissingDebugInfo/EndOfFile uses in src/jsc/btjs.rs are bun_crash_handler::Error, and the "InvalidDataURL"/"TarballFailedToExtract" string matches in ResolveMessage.rs/AsyncModule.rs come from bun_install::Error::name(), not the removed bun_jsc variants.
• Checked SignResult.request_payer readers (only the sign_request local and the cache-key struct) and dont_print_on_dumb (no setter anywhere in the repo).

Extended reasoning...

The change is a pure deletion (+4/-58) across six Rust files: a write-only Progress flag and its early-return, an infallible Result wrapper on ModuleInfo::finalize plus its three dead error arms, two always-equivalent hosted-git lookups in Tag::infer, five never-constructed bun_jsc::Error variants, and a write-only SignResult field. It touches the S3 request-signing file but only removes a field that is written and never read; the x-amz-request-payer header emission still reads the local variable and the credentials/options structs keep their own field. Every claimed-dead item was verified by grep and by reading the hosted_git_info parsing path, so there is no behavior change to test. The diff has shrunk substantively since the earlier reviews (later commits restored items colliding with open PRs, mooting the earlier SAFETY-comment nit), no CODEOWNERS entry covers these files, and no CHANGES_REQUESTED review is outstanding.

[robobun]

The trim is done, and the PR is ready for review again at c2b7b22. The title and the description now describe this head.

• The diff is 6 files, 4 lines added and 58 removed. Five items stay: Progress.dont_print_on_dumb, the Result of ModuleInfo::finalize, two lookups in Tag::infer, five variants of bun_jsc::Error, and SignResult.request_payer.
• I ran a trial merge (git merge-tree) of each of the 5,680 other open pull request heads with main and with this branch. The branch adds no conflicted file and no conflict hunk. I also searched the added lines of every head: none uses a removed name.
• The same two checks on the first head of this PR (341e416) show a new conflicted file in 32 open pull requests and more conflict hunks in 20. Every item that collides is back in the tree. The Notes list each one with the pull requests that block it.
• Checks on this head: bun bd, bun run rust:check-all (12 of 12), cargo clippy, cargo check --workspace --all-targets, and nine test files.

[robobun]

I merged main (ea6a2c7) into the branch and took one more item out. The head is now 0f2f9e3: 4 files, 43 lines removed, none added.

• The item that went back is the Result of ModuleInfo::finalize. Build every runtime ES module's record from the transpiler output instead of a second JSC parse #35605 changed after this PR opened: it now adds a caller that tests that Result, and it edits the function. The Notes list the item with the others that wait for an open pull request.
• I compared the branch again with the 607 open pull requests that changed since the first comparison. A trial merge adds no conflict for the four items that stay, and none of those pull requests uses a removed name.
• The 13 commits of main since the old base add no line that names a removed item. On the merged head, bun bd, cargo check --workspace and cargo clippy pass, and the five test files in the Notes pass.
• The last CI run (build 128667, on the old head) had two red jobs, and neither is from this diff: an artifact download that timed out on the darwin aarch64 test lane, and the bake.test.ts restart tests that also flake on main.

[claude]

LGTM — since the last review the branch merged main and put ModuleInfo::finalize back, leaving a 43-line deletion-only diff across four files, and each removed item checks out as dead.

What was reviewed:

• Tag::infer: traced HostedGitInfo::from_url → hgi_to_tag for git:// and git+http(s):// input; Representation::Shortcut only arises from a shortcut protocol or is_github_shorthand, which rejects any input with a : before #, and correct_url can only yield GitPlusSsh, so the removed lookups could never return Tag::Github.
• bun_jsc::Error variants: grepped for Error::, CrateError:: and bun_jsc::CrateError:: constructors/matches workspace-wide; the only MissingDebugInfo/EndOfFile hits are in btjs.rs, which imports bun_crash_handler::Error, and ResolveMessage.rs/AsyncModule.rs match on name() strings sourced from the resolver/install enums.
• SignResult.request_payer (pub(crate)) has no reader in src/s3_signing; the x-amz-request-payer header is still emitted from the local. dont_print_on_dumb has no reference anywhere in the repo, and both Progress literals use ..Default::default().
• Minor: the PR description still says 58 lines in 6 files including finalize; the diff is now 43 lines in 4 files.

Extended reasoning...

The diff removes a never-set Progress field and its early return, two redundant HostedGitInfo::from_url lookups in Tag::infer, five never-constructed bun_jsc::Error variants, and a write-only SignResult.request_payer field. It touches S3 request signing, but only by dropping a field that nothing read; the header emission path is unchanged, and no struct involved is repr(C) or mirrored in C++. The bug hunt ran dry, no CODEOWNERS entry covers these files, and the timeline shows no CHANGES_REQUESTED review; the commits since the last bot review narrowed scope (reverted the finalize change) rather than adding risk. Each deletion was independently confirmed dead by grep and by tracing the hosted-git-info protocol/representation logic, which is what decided approve.

[robobun]

A note on the automated summary above: it lists six removed variants of bun_jsc::Error, with ParserError among them. The diff removes five. ParserError stays in src/jsc/error.rs at the head (0f2f9e3), the variant and its name() arm, because #42671 constructs it. The description is correct as it is.

[robobun]

I merged main (89fbb78) into the branch and compared the diff again with every open pull request. The head is now 57b8496: 3 files, 40 lines removed, none added.

• SignResult.request_payer went back. s3: add tagging option and route write headers through one carrier #46746 and s3: send the contentDisposition given to file() or new S3Client(), and keep contentEncoding on the upload call #46863 opened after this PR, and both edit the lines next to the store of that field. The Notes list the item with the others that wait for an open pull request.
• Another sweep proposed two more removals in bun_jsc::Error for this PR: impl From<ErrorCode> and impl From<bun_uws::ConnectError>, with the variants ErrorCode and FailedToOpenSocket that only they construct. The workspace compiles without them, but the removal adds a merge conflict to Rewrite the uSockets core in Rust #34037, Remove dead code from the WebCore bindings and 20 Rust crates #40525 and Throw when a V8 heap snapshot is too large to serialize #46893. I left them out and added them to the list in the Notes.
• For the three items that stay, a trial merge with the heads of all 5,931 other open pull requests adds no conflict, and none of those pull requests uses a removed name.
• Checks on this head: bun bd, bun run rust:check-all (12 of 12), cargo clippy, cargo check --workspace --all-targets, and four test files.

[claude]

LGTM — the narrowed diff is three pure deletions and each one checks out as behavior-preserving.

What was reviewed:

• Tag::infer: traced git:/git+http(s): inputs through normalize_protocol/correct_url — the protocol is always Git/GitPlusHttp/GitPlusHttps (or GitPlusSsh), never a shortcut, so hgi_to_tag could only return Tag::Git; the hosted-git-info test cases (git://github.com/foo/bar -> default: "git") agree.
• bun_jsc::Error variants: grepped for qualified/aliased constructors and matches, including cfg-gated code — none; the Error::MissingDebugInfo/EndOfFile hits in src/jsc/btjs.rs are bun_crash_handler::Error, and the "InvalidURL"/"TarballFailedToExtract" string arms in ResolveMessage.rs/AsyncModule.rs still fire via the nested Resolver/Url/Install name() delegation.
• Progress.dont_print_on_dumb: no remaining reference anywhere in the tree (Rust, Zig, C++, TS).

Extended reasoning...

The PR now touches only src/bun_core/Progress.rs, src/install/dependency.rs and src/jsc/error.rs, removing 40 lines and adding none: an always-false Progress field and its early return, two HostedGitInfo lookups in Tag::infer that could only yield Tag::Git, and five never-constructed bun_jsc::Error variants with their name() arms. No security-sensitive surface is touched. The prior inline comments from this bot concerned files that have since been dropped from the PR, no other reviewer has an outstanding objection, the hunt ran dry with no findings, and no CODEOWNERS entry covers the changed paths. Each deletion was independently verified against the hosted_git_info parser and repo-wide greps, which decided approve.