Skip to content

better logging of safe outputs - #679

Merged
dsyme merged 6 commits into
mainfrom
pelikhan/aw-logs-parser
Sep 10, 2025
Merged

better logging of safe outputs#679
dsyme merged 6 commits into
mainfrom
pelikhan/aw-logs-parser

Conversation

@pelikhan

@pelikhan pelikhan commented Sep 10, 2025

Copy link
Copy Markdown
Collaborator
  • Improving logging of safe outputs
  • escape control character in repair mode

- Updated the workflow steps to print agent output to the step summary with improved formatting.
- Changed the step name from "Collect agent output" to "Print Agent output" for clarity.
- Added a check to ensure a newline is added after the output content if it doesn't end with one.
- Introduced a new step to upload the agent output file, ensuring it runs regardless of previous step outcomes.
- Replaced the previous output printing logic with a sanitized version that focuses on processed output.
- Consistently updated all relevant workflow files to reflect these changes.
@pelikhan pelikhan changed the title Refactor agent output handling in GitHub workflows better logging of safe outputs Sep 10, 2025
@dsyme
dsyme merged commit 464e8d4 into main Sep 10, 2025
9 checks passed
@dsyme
dsyme deleted the pelikhan/aw-logs-parser branch September 10, 2025 19:09
github-actions Bot added a commit that referenced this pull request Sep 13, 2026
Reviewed recent compiler changes and open code-scanning alerts against
compiler-threat-detection-spec.md conformance scope. No new CTR-* rule
was warranted; all reviewed findings are already-covered classes,
out-of-scope files, stale/false-positive claims, or non-security
smoke-test noise.

Add Section 7.4 Mapping Audit (2026-09-13) recording:
- #681/#678/#676/#675 (go/allocation-size-overflow): same in-process,
  schema-bounded capacity-hint class already assessed 2026-09-09/10.
- #679 (go/useless-assignment-to-field), #674/#669/#668/#667
  (go/bad-redirect-check): pkg/cli/ findings outside conformance scope.
- #663 (js/http-to-file-access): scripts/ build tooling, out of scope,
  already carries an in-code CodeQL suppression rationale comment.
- #652/#651 (workflow-go-graphql-injection-sprintf): stale against
  current pkg/cli/project_command.go, which already passes owner via
  GraphQL named variables, not fmt.Sprintf string interpolation.
- #657 (workflow-security-finding-1): explicit smoke-test dummy alert.
- #680 (workflow-out-of-context): stray commit artifacts
  (test_dup_import binary, tmp/smoke_test_22524436360.go,
  {outname}.f) — commit hygiene, not a compiler threat-detection gap.

Bump spec to 1.0.35 with Section 2 sync-table row and Section 10
change-log entry (audit-only, no CTR rule or lock-file change).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants