[aw] Java Codegen Agentic Fix reported incomplete result

Start with .github/workflows/java-codegen-fix.md and the Java codegen entry points under java/scripts/codegen. Reproduce the failed run, checking npm dependency and schema generation steps before Maven verification; done means the workflow can regenerate java/sdk/src/generated/java and complete validation without the reported infrastructure failures.

Workflow Failure

Workflow: Java Codegen Agentic Fix
Branch: main
Run: https://github.com/github/copilot-sdk/actions/runs/34369101014

[!WARNING]
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

• Sandbox firewall blocks registry.npmjs.org and repo.maven.apache.org, preventing npm install/schema fetch/codegen regeneration and Maven dependency resolution (central-publishing-maven-plugin). Could not diagnose or validate any fix for PR #2590.

  Attempted to fix Java codegen/build failures on branch sdk/typed-structured-output for PR #2590, but the sandbox's network firewall blocks the required package registries entirely, preventing any diagnosis or fix from being validated:

1. npm ci in java/scripts/codegen fails with 403 Forbidden fetching tsx/json-schema/esbuild tarballs from registry.npmjs.org (Squid proxy denies the CONNECT tunnel with ERR_ACCESS_DENIED). This blocks running npm run fetch:schemas and npm run generate, so I cannot regenerate java/sdk/src/generated/java from the new schemas at all.
2. mvn verify (even after switching JAVA_HOME to the available Temurin 25 JDK, which resolves the JDK-version enforcer failure from the original CI log) fails during project initialization: it cannot resolve org.sonatype.central:central-publishing-maven-plugin:0.11.0 because repo.maven.apache.org is also blocked by the firewall (CONNECT tunnel 403).
3. The only allowed domains in this sandbox's firewall policy are GitHub-related domains (github.com, githubusercontent.com, github-cloud.s3.amazonaws.com, etc.), json-schema.org/schemastore.org, OS package mirrors, and CRL/OCSP endpoints — registry.npmjs.org and repo.maven.apache.org are not in the allowlist.
4. Additionally, ~/.m2 is owned by root so a repository directory can't even be created there by the runner user (worked around by pointing -Dmaven.repo.local elsewhere, but the plugin resolution over the network is the blocking issue).

No code changes were made since I could not validate any fix (mvn verify never got past the dependency-resolution phase, and codegen dependencies could not be installed). The JDK version issue from the original failure log is resolved simply by using JDK 25 (available at /usr/lib/jvm/temurin-25-jdk-amd64) instead of JDK 17 in the build environment — that part is an environment/CI configuration matter, not a code fix. Manual intervention is needed either to run this job with network access to registry.npmjs.org and repo.maven.apache.org allowlisted, or to run it in an environment with those Maven/npm dependencies pre-cached.

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/copilot-sdk/actions/runs/34369101014

[!TIP]

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Java Codegen Agentic Fix · copilot · 63.8 AIC · ◷