test: util — proxy detection and lazy error recovery

[anandgupta42]

What does this PR do?

1. proxied() — src/util/proxied.ts (6 new tests)

This utility detects whether the user is behind a corporate HTTP proxy by checking HTTP_PROXY, HTTPS_PROXY, http_proxy, and https_proxy environment variables. It had zero tests. It's used by Config and BunProc to decide whether to pass --no-cache to bun/npm install — a false negative would cause stale package installs behind corporate proxies. New coverage includes:

• All four env var spellings (upper and lowercase) individually
• Base case: no proxy vars set → returns false
• Edge case: empty string env var → returns false (falsy, not truthy)
• Proper env var save/restore to avoid test pollution

2. lazy() error recovery and reset — src/util/lazy.ts (2 new tests)

The lazy() utility powers deferred initialization throughout the codebase (Shell, Config, etc.). Existing tests covered memoization and reference identity, but not the error recovery path (lines 7–14: if the init function throws, the value is NOT cached, so the next call retries) or the .reset() method. New coverage includes:

• Throw on first call → retry succeeds on second call → third call uses cache
• .reset() clears cached value, allowing re-initialization

Type of change

• New feature (non-breaking change which adds functionality)

Issue for this PR

N/A — proactive test coverage

How did you verify your code works?

bun test test/util/proxied.test.ts   # 6 pass
bun test test/util/lazy.test.ts      # 5 pass (3 existing + 2 new)

Checklist

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

https://claude.ai/code/session_01EDCRjjHdb1dWvxyAfrLuhw

Summary by CodeRabbit

• Tests
  • Expanded test coverage for lazy initialization with retry behavior and reset functionality.
  • Added comprehensive test suite for proxy detection across environment variables.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 18bf5b31-d4fe-4350-96c4-2d40a9bf8b38

📥 Commits

Reviewing files that changed from the base of the PR and between 9ba2114 and f876f7d.

📒 Files selected for processing (2)

• packages/opencode/test/util/lazy.test.ts
• packages/opencode/test/util/proxied.test.ts

---

📝 Walkthrough

Walkthrough

Tests added for lazy wrapper retry behavior after initialization failures and reset functionality; new test suite created for proxy detection with environment variable management.

Changes

Cohort / File(s)	Summary
Lazy Wrapper Tests packages/opencode/test/util/lazy.test.ts	Added test cases verifying that lazy wrapper retries initialization after failures and caches successful results; also verifies reset() clears cached values and allows re-initialization.
Proxy Detection Tests packages/opencode/test/util/proxied.test.ts	New test suite for proxied() function covering environment variable setup/teardown, behavior with no proxy variables set, behavior with proxy variables set to non-empty URLs, and handling of empty string values.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

contributor

Poem

🐰 With lazy hearts we cache and test,
Retrying failures, proving best—
When proxies hide or reset calls,
Our warren's tests cover all! 🧪✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main changes: adding tests for proxy detection and lazy error recovery utilities.
Description check	✅ Passed	The description comprehensively covers all required template sections with detailed explanations of what was tested, why, and how verification was performed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/hourly-20260327-2311

---

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.}

[anandgupta42]

Consolidated into #545