Skip to content

Improve links in readme to AW project - #1

Merged
Mossaka merged 1 commit into
mainfrom
idan/improve-readme-aw-callout
Oct 22, 2025
Merged

Improve links in readme to AW project#1
Mossaka merged 1 commit into
mainfrom
idan/improve-readme-aw-callout

Conversation

@idan

@idan idan commented Oct 22, 2025

Copy link
Copy Markdown
Contributor

The only link to AW was at the bottom of the readme, I created a callout block near the top to supply more context.

CleanShot 2025-10-22 at 10 28 55@2x

@Mossaka
Mossaka merged commit 9bb4ba0 into main Oct 22, 2025
16 of 18 checks passed
Copilot AI added a commit that referenced this pull request Jun 13, 2026
Extract concerns #1 (log/state dir setup) and #2 (chroot home
bind-mount prep) with their four private helpers into a new
src/workdir-setup.ts module.

- src/log-paths.ts: export LogPaths interface
- src/workdir-setup.ts: new module with prepareWorkDirectories()
- src/config-writer.ts: remove extracted code; call
  prepareWorkDirectories(); shrinks from 431 to ~194 lines
- src/workdir-setup.test.ts: 16 direct unit tests for the new module

Closes #4878
lpcox added a commit that referenced this pull request Jun 13, 2026
…orchestrator (#4896)

* Initial plan

* refactor: extract workdir setup from writeConfigs into workdir-setup.ts

Extract concerns #1 (log/state dir setup) and #2 (chroot home
bind-mount prep) with their four private helpers into a new
src/workdir-setup.ts module.

- src/log-paths.ts: export LogPaths interface
- src/workdir-setup.ts: new module with prepareWorkDirectories()
- src/config-writer.ts: remove extracted code; call
  prepareWorkDirectories(); shrinks from 431 to ~194 lines
- src/workdir-setup.test.ts: 16 direct unit tests for the new module

Closes #4878

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Landon Cox <landon.cox@microsoft.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
lpcox added a commit that referenced this pull request Jun 26, 2026
Token-optimization pass on the Contribution Check workflow (ranked #1
by total AIC). All review data is already pre-fetched in `steps:`, so
the agent only needs to read three context files and emit a single
`add_comment` (or noop) safe-output.

Changes:
- tools: disable GitHub tools (`github: false`) instead of the previous
  `gh-proxy`/`pull_requests` config. NOTE: simply *removing* the tools
  block makes gh-aw auto-inject a read-only GitHub MCP server with a
  *broader* toolset (context,repos,issues,pull_requests), which is the
  opposite of the optimization goal. Explicit `github: false` drops the
  github-mcp-server and cli-proxy containers entirely and prevents the
  ~5.3 stray GitHub API calls/run the agent was making despite the
  prompt forbidding them. (lock file shrinks ~150 lines.) Keep `edit:`
  so the agent can read the pre-fetched files.
- strict: false -> true (also required removing the internal
  `sandbox.mcp.version` key, which strict mode disallows).
- max-turns: 5 -> 3 (linear task: read files -> compare -> comment).
- Prompt: add an explicit "only add_comment or noop" tool constraint.
- Recompiled contribution-check.lock.yml; updated the workflow test's
  max-turns assertion 5 -> 3.

Out of scope: recommendation #1 (all Copilot runs report null
token_usage) is a separate, systemic api-proxy telemetry-export
investigation, not a per-workflow change.

Refs #5558

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
lpcox added a commit that referenced this pull request Jul 17, 2026
…6328)

* fix: diagnose ARC/DinD DNS isolation and quiet rootless chmod noise

Addresses two of the ARC/DinD implementation gaps from #6326.

Gap 3 — DinD-spawned containers cannot resolve Kubernetes DNS names:
When the external DIFC proxy is addressed by a Kubernetes Service name
(e.g. awmg-cli-proxy), the cli-proxy fails with getaddrinfo EAI_AGAIN
because containers on the DinD Docker network do not reach the Kubernetes
cluster DNS resolver. The previous 'could not connect to the external DIFC
proxy' error hid this root cause. Add detectDnsResolutionFailure() which
scans cli-proxy logs for EAI_AGAIN/ENOTFOUND and, when found, augments the
startup error with an actionable DNS-isolation explanation and fix guidance
(address by IP, or configure dockerd --dns).

Gap 4 — post-job chmod noise on rootless/non-privileged runners:
The best-effort artifact permission repair emitted an alarming [WARN] when
the repair container was denied CHOWN/chmod (Operation not permitted) on
restricted runners. The agent has already finished and artifacts remain
readable by the owning user, so downgrade benign permission errors to debug
while keeping WARN for genuine, unexpected failures.

Adds unit tests for both paths. Remaining gaps (#1 topology auto-defaults,
#2 network-isolation smoke-test coverage) are larger and tracked in #6326.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b593fd45-255a-49a2-9d21-fd78108650a2

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* fix: pre-register internal proxy DNS on ARC/DinD and gVisor

The agent and topology peers resolve the compose-internal proxy sidecars
(squid-proxy, api-proxy, cli-proxy) by hostname via Docker's embedded DNS
(127.0.0.11). That resolver is unreachable from gVisor's userspace netstack
and on ARC/DinD runners (the DinD network doesn't forward lookups to the
Kubernetes resolver), producing getaddrinfo EAI_AGAIN failures.

Static /etc/hosts pre-registration already existed but only fired for gVisor
and omitted cli-proxy. This:

- Extends the topology hosts patch to run for all network-isolation runs
  (covering ARC/DinD), not just gVisor.
- Adds the missing cli-proxy entry on both the gVisor compose path and the
  network-isolation runtime path.
- Factors the service-name -> IP mapping into a single shared helper
  (buildInternalServiceHosts) so the gVisor and ARC/DinD paths no longer
  duplicate the service list or inclusion logic.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b593fd45-255a-49a2-9d21-fd78108650a2

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

This is wrong

🦎🔮 gVisor + Codex smoke test by Smoke gVisor Codex
Add label test-gvisor-codex to run again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants