[rendering-scripts] Daily Rendering Scripts Verifier — 2026-09-17: blocked by environment access issues #61559
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-09-20T07:58:31.698Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Daily Rendering Scripts Verifier — 2026-09-17
Verification for the most recent agentic workflow run was blocked by two environment-level issues before any parser/render logic could be exercised. No code changes were made — filing this report instead of a PR.
Run audited
.github/workflows/issue-monster.lock.yml), schedule trigger,main, concludedsuccess.agent_id":"pi",agent_model":"copilot/gpt-5.4",engine_versions:{"pi":"0.85.1"}) — parser target isactions/setup/js/parse_pi_log.cjs.Blockers
missing_datafiled).agenticworkflows logs/auditresolvedlogs_path=/tmp/gh-aw/aw-mcp/logs/run-35195988617, but every file in it (agent-stdio.log,agent_output.json,jobs.json,awf-config.json, ...) and the directory itself returnedEACCESvia Read/Glob — persisted across two fresh re-downloads (one mid-run, one aftergh run viewconfirmedconclusion=success). Falling back togh run download/gh api .../artifacts/{id}/zipfor theagentartifact also failed with403 Forbidden. Net effect: thepiparser could not be run against this run's real log data.missing_toolfiled).actions/setup/jshas nonode_modules;npm installfails deterministically because the pinned devDependency@actions/github-scriptresolves via(github.com/redacted) and that clone fails withCould not resolve hostname github.com— even though HTTPS calls togithub.com/api.github.com(viagh) andregistry.npmjs.orgboth succeed from this sandbox. This blocksnpm run test:js -- --run parse_pi_log.test.cjsandrender_template.test.cjs`, the only supported harness path here.What was verified by inspection
parse_pi_log.cjsandparse_pi_log.test.cjs(455 / 324 lines) exist and cover both the legacy flat schema and the v3 streaming schema (isPiV3Schema,transformPiV3Entries), so thepiengine is not an unhandled gap in the parser map.render_template.cjswas not exercised (blocked by Add workflow: githubnext/agentics/weekly-research #2 above); no changes were made to it.Side observation (not investigated further, out of scope for these parser scripts)
agenticworkflows auditreportedengine_config.engine_id: "claude"for this run, which conflicts with the compiled workflow's ownagent_id: "pi"metadata. Possibly a mislabeling in the audit tool's engine-detection fallback — worth a look if it recurs, since it could send a future run of this verifier down the wrong parser.Next actions
/tmp/gh-aw/aw-mcp/logs/run-*permission issue and/or theagent/detectionartifact download 403s are resolved on the infra side.``@actions/github-script``via an HTTPS tarball/registry reference instead ofgit+ssh, sonpm installdoesn't require SSH access togithub.comin restricted sandboxes.Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
api.anthropic.comapi.github.comcodeload.github.comgithub.com[!TIP]
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:See GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions