fix: restore HTTPS_PROXY and fix smoke-chroot checkout #530

Mossaka · 2026-02-05T21:33:56Z

Summary

Fixes two regressions from recent agent-authored PRs that are breaking CI on main.

Fix 1: Restore HTTPS_PROXY (fixes Examples Test, Chroot Edge Cases, Chroot Package Managers)

PR #524 removed both HTTP_PROXY and HTTPS_PROXY from the agent container. This was over-broad:

HTTP (port 80): Works via iptables DNAT → Squid port 3129 (intercept mode). No HTTP_PROXY needed.
HTTPS (port 443): Requires CONNECT method through Squid's forward-proxy port 3128. DNAT to the intercept port can't handle TLS. HTTPS_PROXY is required.

Changes:

Restore HTTPS_PROXY in the agent environment pointing to squid:3128
Remove HTTPS_PROXY/https_proxy from the EXCLUDED_ENV_VARS set (keep HTTP_PROXY/http_proxy excluded)

Fix 2: Fix Smoke Chroot sparse checkout (fixes Smoke Chroot `tsc` build)

PR #527 recompiled lock files, but the smoke-chroot workflow got compiled with a sparse checkout (.github/.agents only). The agent job then runs npm ci && npm run build which needs src/, package.json, etc.

Changes:

Add actions/checkout step to smoke-chroot.md source → compiler skips sparse checkout
Recompiled smoke-chroot.lock.yml with --action-mode release --action-tag v0.42.0

Fixes #529

Test plan

🤖 Generated with Claude Code

github-actions · 2026-02-05T21:34:11Z

Chroot tests failed Smoke Chroot failed - See logs for details.

github-actions · 2026-02-05T21:34:12Z

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

github-actions · 2026-02-05T21:34:15Z

🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

github-actions · 2026-02-05T21:34:48Z

⚠️ Coverage Regression Detected

This PR decreases test coverage. Please add tests to maintain coverage levels.

Overall Coverage

Metric	Base	PR	Delta
Lines	82.10%	82.07%	📉 -0.03%
Statements	82.14%	82.10%	📉 -0.04%
Functions	81.95%	81.95%	➡️ +0.00%
Branches	75.44%	75.34%	📉 -0.10%

📁 Per-file Coverage Changes (1 files)

File	Lines (Before → After)	Statements (Before → After)
`src/docker-manager.ts`	82.9% → 82.7% (-0.17%)	82.2% → 82.0% (-0.16%)

Coverage comparison generated by scripts/ci/compare-coverage.ts

github-actions · 2026-02-05T21:36:41Z

Go Build Test Results

Project	Download	Tests	Status
color	✅	1/1	PASS
env	✅	1/1	PASS
uuid	✅	1/1	PASS

Overall: PASS

All Go projects successfully downloaded dependencies and passed their tests.

AI generated by Build Test Go

github-actions · 2026-02-05T21:36:47Z

Deno Build Test Results

Project	Tests	Status
oak	1/1	✅ PASS
std	1/1	✅ PASS

Overall: ✅ PASS

All Deno tests passed successfully.

AI generated by Build Test Deno

github-actions · 2026-02-05T21:36:53Z

Smoke Test Results

Last 2 Merged PRs:

fix: mount /etc/hosts in chroot mode and handle missing resolv.conf #522: fix: mount /etc/hosts in chroot mode and handle missing resolv.conf
fix: add env capture for Rust and Java in chroot mode #517: fix: add env capture for Rust and Java in chroot mode

Tests:

✅ GitHub MCP: Retrieved PR data
✅ Playwright: Loaded GitHub homepage (title: "GitHub · Change is constant. GitHub keeps you ahead. · GitHub")
✅ File Writing: Created /tmp/gh-aw/agent/smoke-test-copilot-21729338588.txt
✅ Bash Tool: Verified file content

Overall Status: PASS

cc @Mossaka

AI generated by Smoke Copilot

github-actions · 2026-02-05T21:36:54Z

Node.js Build Test Results

Project	Install	Tests	Status
clsx	✅	PASS	✅ PASS
execa	✅	PASS	✅ PASS
p-limit	✅	PASS	✅ PASS

Overall: ✅ PASS

All Node.js projects installed dependencies successfully and passed their test suites.

AI generated by Build Test Node.js

github-actions · 2026-02-05T21:37:14Z

C++ Build Test Results

Project	CMake	Build	Status
fmt	✅	✅	PASS
json	✅	✅	PASS

Overall: PASS ✅

All C++ projects built successfully.

AI generated by Build Test C++

github-actions · 2026-02-05T21:37:15Z

Smoke Test: Claude Engine - PASS ✅

Last 2 merged PRs:

fix: mount /etc/hosts in chroot mode and handle missing resolv.conf
fix: recompile lock files with release action mode

Test results:

✅ GitHub MCP
✅ Playwright (GitHub homepage title verified)
✅ File writing (/tmp/gh-aw/agent/smoke-test-claude-21729338577.txt)
✅ Bash tool

Status: PASS

AI generated by Smoke Claude

github-actions · 2026-02-05T21:37:53Z

Build Test: Bun - FAILED ❌

Project	Install	Tests	Status
elysia	❌	-	FAIL
hono	❌	-	FAIL

Overall: FAIL ❌

Error Details

Bun Installation: ✅ Successfully installed v1.3.8

Environment Issue: Bun is crashing in the execution environment with core dumps:

bun install fails with: error: An internal error occurred (NotDir)
bun test crashes with: Aborted (core dumped) (exit code 134)

Root Cause: The execution environment appears to be missing critical system resources:

No /proc/cpuinfo available during installation
No /proc/version available
No /etc/os-release available
Bun crashes when attempting file system operations

This appears to be a compatibility issue between Bun v1.3.8 and the restricted container environment. Bun may require full Linux kernel interfaces (procfs) that are not available in this execution context.

AI generated by Build Test Bun

Copilot

Pull request overview

This PR fixes two critical regressions introduced by recent PRs #524 and #527 that broke CI workflows on the main branch.

Changes:

Restores HTTPS_PROXY environment variable in the agent container to fix HTTPS connectivity (required for CONNECT tunneling through Squid's forward proxy port 3128)
Removes HTTPS_PROXY/https_proxy from EXCLUDED_ENV_VARS set (keeping only HTTP_PROXY/http_proxy excluded since HTTP uses iptables intercept mode)
Updates entrypoint.sh logging to clearly distinguish between HTTP intercept mode and HTTPS forward proxy mode
Fixes smoke-chroot workflow by replacing sparse checkout with full repository checkout
Updates test assertions to reflect that HTTPS_PROXY is now explicitly set by AWF

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/docker-manager.ts	Restores `HTTPS_PROXY` setting and removes `https_proxy` from `EXCLUDED_ENV_VARS`
src/docker-manager.test.ts	Updates tests to verify `HTTPS_PROXY` is set and `HTTP_PROXY` remains excluded
containers/agent/entrypoint.sh	Improves proxy configuration logging to distinguish HTTP intercept mode from HTTPS forward proxy
.github/workflows/smoke-chroot.md	Adds full checkout step before build to ensure `src/` directory is available for `npm run build`
.github/workflows/smoke-chroot.lock.yml	Recompiled workflow with full checkout instead of sparse checkout, removes unnecessary permission fix steps

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-05T21:37:55Z

src/docker-manager.ts

-    'HTTP_PROXY',     // Intercept mode handles routing; explicit proxy is unreachable
-    'HTTPS_PROXY',    // Intercept mode handles routing; explicit proxy is unreachable
+    'HTTP_PROXY',     // Intercept mode handles HTTP routing via iptables DNAT
    'http_proxy',     // Lowercase variant


The lowercase variant https_proxy should also be added to the EXCLUDED_ENV_VARS set. While HTTPS_PROXY is explicitly set by AWF, if a user runs with --env-all and has https_proxy set on their host, it will leak into the container and could potentially interfere with the explicit HTTPS_PROXY setting. Some tools check both uppercase and lowercase variants, and having both set with different values could cause confusion or incorrect behavior.

Add 'https_proxy' to the EXCLUDED_ENV_VARS set to match the pattern used for HTTP_PROXY/http_proxy.

Suggested change

'http_proxy', // Lowercase variant

'http_proxy', // Lowercase variant

'https_proxy', // Lowercase HTTPS proxy variant

Copilot · 2026-02-05T21:37:55Z

src/docker-manager.test.ts

+        // HTTP_PROXY must NOT leak from host (intercept mode handles HTTP routing)
        expect(env.HTTP_PROXY).toBeUndefined();
-        expect(env.HTTPS_PROXY).toBeUndefined();
        expect(env.http_proxy).toBeUndefined();
-        expect(env.https_proxy).toBeUndefined();
+        // HTTPS_PROXY is set by AWF (not from host) for CONNECT tunneling
+        expect(env.HTTPS_PROXY).toBe('http://172.30.0.10:3128');


The test should verify that https_proxy (lowercase) doesn't leak from the host when --env-all is used, similar to how http_proxy is checked. Add an assertion: expect(env.https_proxy).toBeUndefined(); after line 971 to ensure the lowercase variant is also properly excluded.

github-actions · 2026-02-05T21:38:21Z

Chroot tests failed Smoke Chroot failed - See logs for details.

github-actions · 2026-02-05T21:38:23Z

📰 DEVELOPING STORY: Smoke Copilot reports failed. Our correspondents are investigating the incident...

github-actions · 2026-02-05T21:38:24Z

💫 TO BE CONTINUED... Smoke Claude failed! Our hero faces unexpected challenges...

github-actions · 2026-02-05T22:36:47Z

🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

github-actions · 2026-02-05T22:36:47Z

📰 DEVELOPING STORY: Smoke Copilot reports was cancelled. Our correspondents are investigating the incident...

github-actions · 2026-02-05T22:36:51Z

Chroot tests failed Smoke Chroot was cancelled - See logs for details.

github-actions · 2026-02-05T22:39:13Z

Chroot tests failed Smoke Chroot was cancelled - See logs for details.

github-actions · 2026-02-05T22:39:27Z

🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

github-actions · 2026-02-05T22:39:29Z

⚠️ Coverage Regression Detected

This PR decreases test coverage. Please add tests to maintain coverage levels.

Overall Coverage

Metric	Base	PR	Delta
Lines	82.10%	82.07%	📉 -0.03%
Statements	82.14%	82.10%	📉 -0.04%
Functions	81.95%	81.95%	➡️ +0.00%
Branches	75.44%	75.34%	📉 -0.10%

📁 Per-file Coverage Changes (1 files)

File	Lines (Before → After)	Statements (Before → After)
`src/docker-manager.ts`	82.9% → 82.7% (-0.17%)	82.2% → 82.0% (-0.16%)

Coverage comparison generated by scripts/ci/compare-coverage.ts

github-actions · 2026-02-05T22:39:34Z

📰 DEVELOPING STORY: Smoke Copilot reports was cancelled. Our correspondents are investigating the incident...

github-actions · 2026-02-05T22:42:01Z

Smoke Test Results

Last 2 merged PRs:

fix: mount /etc/hosts in chroot and fix HTTP blocking test
fix: recompile lock files with release action mode

✅ GitHub MCP (PR fetch)
✅ Playwright (GitHub page title verified)
✅ File Write (/tmp/gh-aw/agent/smoke-test-claude-21731200162.txt)
✅ Bash (file verified)

Status: PASS

AI generated by Smoke Claude

github-actions · 2026-02-05T22:42:10Z

Security Review: HTTPS_PROXY Restoration

I've reviewed PR #530 for security implications. The changes primarily fix CI regressions and are generally safe, but there is one security concern that requires clarification:

⚠️ Concern: HTTPS_PROXY Environment Variable Restoration

File: src/docker-manager.ts:329

Change:

// REMOVED from EXCLUDED_ENV_VARS set:
'HTTPS_PROXY',    // Was: "Intercept mode handles routing; explicit proxy is unreachable"
'https_proxy',    // Lowercase variant

// ADDED to agent environment:
HTTPS_PROXY: `(redacted)

Security Implications:

Positive: The PR correctly identifies that HTTPS traffic requires CONNECT method through Squid's forward proxy port (3128), not just iptables DNAT. This is technically accurate.
Concern: By setting HTTPS_PROXY in the agent container environment, applications will now explicitly send HTTPS traffic through the Squid proxy at port 3128. However, I need clarification on:
- Does the Squid configuration at port 3128 enforce the same domain ACL restrictions as port 3129 (intercept mode)?
- Are both ports configured with identical security policies?
- Could an application bypass restrictions by directly connecting to port 443 instead of respecting HTTPS_PROXY?

Verification Needed:

The iptables rules in containers/agent/setup-iptables.sh should still redirect all port 443 traffic to Squid regardless of HTTPS_PROXY setting. This would provide defense-in-depth. Can you confirm:

Port 443 iptables DNAT rules are still active and enforced?
Both Squid ports (3128 forward proxy and 3129 intercept) have identical domain filtering?

Recommendation:

If both ports have identical ACL enforcement and iptables still redirects port 443, then this change is safe and fixes a legitimate bug. Otherwise, we need to ensure that:

Applications can't bypass the proxy by ignoring HTTPS_PROXY
Direct port 443 connections are still intercepted

Other Changes: All other changes (chroot /etc/hosts copying, Bun installation, workflow checkout steps) are non-security related and look good.

cc @Mossaka - Can you confirm the Squid configuration enforces domain filtering on both ports 3128 and 3129?

AI generated by Security Guard

github-actions · 2026-02-05T22:43:27Z

💫 TO BE CONTINUED... Smoke Claude was cancelled! Our hero faces unexpected challenges...

github-actions · 2026-02-05T22:43:37Z

✅ Coverage Check Passed

Overall Coverage

Metric	Base	PR	Delta
Lines	82.10%	82.12%	📈 +0.02%
Statements	82.14%	82.16%	📈 +0.02%
Functions	81.95%	81.95%	➡️ +0.00%
Branches	75.44%	75.48%	📈 +0.04%

📁 Per-file Coverage Changes (1 files)

File	Lines (Before → After)	Statements (Before → After)
`src/docker-manager.ts`	82.9% → 83.0% (+0.09%)	82.2% → 82.3% (+0.09%)

Coverage comparison generated by scripts/ci/compare-coverage.ts

github-actions · 2026-02-05T22:43:38Z

📰 DEVELOPING STORY: Smoke Copilot reports was cancelled. Our correspondents are investigating the incident...

github-actions · 2026-02-05T22:43:38Z

Chroot tests failed Smoke Chroot was cancelled - See logs for details.

Four fixes for CI failures introduced by recent agent-authored PRs: 1. Restore HTTPS_PROXY in agent container (fixes #529) - HTTPS requires CONNECT method through Squid port 3128 - Only HTTP_PROXY should be removed (intercept mode handles HTTP) 2. Copy container /etc/hosts to chroot (fixes Smoke Copilot) - Docker extra_hosts (host.docker.internal) only in container /etc/hosts - Chroot sees host's /etc/hosts which lacks this entry - Backup/copy/restore pattern like resolv.conf 3. Add .copilot directory permissions step (fixes Smoke Chroot) - sudo install creates root-owned ~/.copilot - Pre-create with runner:runner ownership in smoke-chroot.md 4. Use setup-bun action for Build Test Bun (fixes core dump) - Bun crashes when installed inside chroot (restricted /proc) - Install on host via oven-sh/setup-bun@v2, available in chroot via PATH All smoke/build-test .md files include actions/checkout step for full repo checkout (needed by postprocess local build). Fixes #529 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

github-actions · 2026-02-05T22:45:30Z

Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded.

github-actions · 2026-02-05T22:45:44Z

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

github-actions · 2026-02-05T22:45:44Z

🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨

github-actions · 2026-02-05T22:45:45Z

✅ Coverage Check Passed

Overall Coverage

Metric	Base	PR	Delta
Lines	82.10%	82.12%	📈 +0.02%
Statements	82.14%	82.16%	📈 +0.02%
Functions	81.95%	81.95%	➡️ +0.00%
Branches	75.44%	75.48%	📈 +0.04%

📁 Per-file Coverage Changes (1 files)

File	Lines (Before → After)	Statements (Before → After)
`src/docker-manager.ts`	82.9% → 83.0% (+0.09%)	82.2% → 82.3% (+0.09%)

Coverage comparison generated by scripts/ci/compare-coverage.ts

github-actions · 2026-02-05T22:48:36Z

Smoke Test Results: Claude Engine

Last 2 Merged PRs:

fix: recompile lock files with release action mode #527: fix: recompile lock files with release action mode
chore: recompile workflow lock files for AWF v0.13.5 #526: chore: recompile workflow lock files for AWF v0.13.5

Test Results:

✅ GitHub MCP: Retrieved PRs successfully
✅ Playwright: Page title verified ("GitHub · Change is constant. GitHub keeps you ahead. · GitHub")
✅ File Write: Created /tmp/gh-aw/agent/smoke-test-claude-21731363138.txt
✅ Bash: File verified with content "Smoke test passed for Claude at Thu Feb 5 22:47:02 UTC 2026"

Overall Status: PASS ✅

AI generated by Smoke Claude

Reverts the following PRs which introduced unnecessary complexity: - #520: fix: enable Squid intercept mode for NAT-redirected traffic - v0.13.5 release: chore(release): bump version to 0.13.5 - #524: fix: remove HTTP_PROXY/HTTPS_PROXY env vars from agent container - #526: chore: recompile workflow lock files for AWF v0.13.5 - #527: fix: recompile lock files with release action mode - #522: fix: mount /etc/hosts in chroot and fix HTTP blocking test - #530: fix: restore HTTPS_PROXY, fix chroot hosts/permissions, fix Bun crash - v0.13.6 release: chore(release): bump version to 0.13.6 The intercept mode (#520) was introduced to fix Codex failing with HTTP_PROXY, but the simpler fix is to just not set HTTP_PROXY for Codex. The intercept mode introduced a cascade of breakage: - HTTPS can't be transparently intercepted (needs CONNECT method) - Image version bumps required lock file recompilation - host.docker.internal traffic crashed Squid under load - Multiple PRs needed to fix each regression This reverts to the pre-#520 explicit proxy mode (HTTP_PROXY/HTTPS_PROXY pointing to Squid port 3128) which worked for all engines. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Reverts the following PRs which introduced unnecessary complexity: - #520: fix: enable Squid intercept mode for NAT-redirected traffic - v0.13.5 release: chore(release): bump version to 0.13.5 - #524: fix: remove HTTP_PROXY/HTTPS_PROXY env vars from agent container - #526: chore: recompile workflow lock files for AWF v0.13.5 - #527: fix: recompile lock files with release action mode - #522: fix: mount /etc/hosts in chroot and fix HTTP blocking test - #530: fix: restore HTTPS_PROXY, fix chroot hosts/permissions, fix Bun crash - v0.13.6 release: chore(release): bump version to 0.13.6 The intercept mode (#520) was introduced to fix Codex failing with HTTP_PROXY, but the simpler fix is to just not set HTTP_PROXY for Codex. The intercept mode introduced a cascade of breakage: - HTTPS can't be transparently intercepted (needs CONNECT method) - Image version bumps required lock file recompilation - host.docker.internal traffic crashed Squid under load - Multiple PRs needed to fix each regression This reverts to the pre-#520 explicit proxy mode (HTTP_PROXY/HTTPS_PROXY pointing to Squid port 3128) which worked for all engines. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Copilot AI review requested due to automatic review settings February 5, 2026 21:33

Copilot started reviewing on behalf of Mossaka February 5, 2026 21:34 View session

github-actions bot added build-test-go build-test-deno labels Feb 5, 2026

github-actions bot added smoke-copilot build-test-node build-test-cpp labels Feb 5, 2026

github-actions bot added the smoke-claude label Feb 5, 2026

Copilot AI reviewed Feb 5, 2026

View reviewed changes

Mossaka force-pushed the fix/restore-https-proxy-and-chroot-checkout branch from 05d4767 to 0305b32 Compare February 5, 2026 21:38

Mossaka force-pushed the fix/restore-https-proxy-and-chroot-checkout branch from b8d305b to 0bc514b Compare February 5, 2026 22:38

Mossaka force-pushed the fix/restore-https-proxy-and-chroot-checkout branch from 0bc514b to c2fc697 Compare February 5, 2026 22:42

Mossaka force-pushed the fix/restore-https-proxy-and-chroot-checkout branch from c2fc697 to 3939d46 Compare February 5, 2026 22:44

Mossaka merged commit 8a61f50 into main Feb 5, 2026
93 checks passed

Mossaka deleted the fix/restore-https-proxy-and-chroot-checkout branch February 5, 2026 23:07

Mossaka mentioned this pull request Feb 5, 2026

fix: reduce Smoke Copilot context size to fix safe_outputs #539

Closed

4 tasks

github-actions bot mentioned this pull request Feb 5, 2026

ci: add write permissions for issue monster agent assignment #537

Merged

Mossaka mentioned this pull request Feb 6, 2026

revert: remove Squid intercept mode and all cascading fixes #541

Merged

6 tasks

Mossaka mentioned this pull request Feb 6, 2026

CI: Smoke Chroot fails with .copilot/pkg permission denied #542

Open

	'http_proxy', // Lowercase variant
	'http_proxy', // Lowercase variant
	'https_proxy', // Lowercase HTTPS proxy variant

fix: restore HTTPS_PROXY and fix smoke-chroot checkout #530

fix: restore HTTPS_PROXY and fix smoke-chroot checkout #530

Uh oh!

Conversation

Mossaka commented Feb 5, 2026

Summary

Fix 1: Restore HTTPS_PROXY (fixes Examples Test, Chroot Edge Cases, Chroot Package Managers)

Fix 2: Fix Smoke Chroot sparse checkout (fixes Smoke Chroot tsc build)

Test plan

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Coverage Regression Detected

Overall Coverage

Uh oh!

github-actions bot commented Feb 5, 2026

Go Build Test Results

Uh oh!

github-actions bot commented Feb 5, 2026

Deno Build Test Results

Uh oh!

github-actions bot commented Feb 5, 2026

Smoke Test Results

Uh oh!

github-actions bot commented Feb 5, 2026

Node.js Build Test Results

Uh oh!

github-actions bot commented Feb 5, 2026

C++ Build Test Results

Uh oh!

github-actions bot commented Feb 5, 2026

Smoke Test: Claude Engine - PASS ✅

Uh oh!

github-actions bot commented Feb 5, 2026

Build Test: Bun - FAILED ❌

Error Details

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fix 2: Fix Smoke Chroot sparse checkout (fixes Smoke Chroot `tsc` build)

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading

github-actions bot commented Feb 5, 2026 •

edited

Loading