[aw] Crane failed #84

Activity

1. github-actions

   added

   agentic-workflows

   on May 21, 2026
2. github-actions commented on May 22, 2026

   

   github-actionsBot

   on May 22, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26306616690 failed.

   🛡️ Protected Files: The code push was refused because the patch modifies protected files (package manifests, agent instruction files, or repository security configuration). This protection guards against unintended supply chain changes.

   Blocked Operations:

   • push_to_pull_request_branch: Cannot push to pull request branch: patch modifies protected files (go.mod, go.sum). Add them to the allowed-files configuration field or set protected-files: fallback-to-issue to create a review issue instead.

   ⚙️ Configure protected-files: fallback-to-issue

   safe-outputs:
     push-to-pull-request-branch:
       protected-files: fallback-to-issue

   Generated from Crane · ● 35.1M · ◷
3. github-actions commented on May 23, 2026

   

   github-actionsBot

   on May 23, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26340613011 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
4. github-actions commented on May 24, 2026

   

   github-actionsBot

   on May 24, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26348453368 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
5. github-actions commented on May 24, 2026

   

   github-actionsBot

   on May 24, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26355204919 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
6. github-actions commented on May 24, 2026

   

   github-actionsBot

   on May 24, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26361633185 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
7. github-actions commented on May 24, 2026

   

   github-actionsBot

   on May 24, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26369710084 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
8. github-actions commented on May 25, 2026

   

   github-actionsBot

   on May 25, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26378433587 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
9. github-actions commented on May 25, 2026

   

   github-actionsBot

   on May 25, 2026 – with GitHub Actions

   ContributorAuthor

   More actions

   Agent job 26390073893 failed.

   🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

   This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

   To fix, recompile the workflow:

   gh aw compile

   Then commit and push the updated .lock.yml file.

   More ways to recompile

   Using the gh-aw MCP server (if configured):

   { "tool": "compile", "arguments": { "validate": true } }

   Recompile all workflows at once:

   gh aw compile --all

   Verify the result:

   gh aw compile --validate

   How to investigate the mismatch

   The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

   • The raw frontmatter text that was used as input
   • Any imported files that were included in the hash
   • The canonical JSON that was fed to SHA-256
   • The resulting hash value

   This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

   This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

   gh aw add <path>@<exact-sha>
   gh aw compile

   How to disable this check

   [!CAUTION]
   Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

   Set stale-check: false in the on: section of your workflow frontmatter:

   on:
     issues:
       types: [opened]
     stale-check: false

   After editing, recompile the workflow: gh aw compile

   Generated from Crane · ◷
10. github-actions commented on May 25, 2026

    

    github-actionsBot

    on May 25, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 26403293723 failed.

    🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

    This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

    To fix, recompile the workflow:

    gh aw compile

    Then commit and push the updated .lock.yml file.

    More ways to recompile

    Using the gh-aw MCP server (if configured):

    { "tool": "compile", "arguments": { "validate": true } }

    Recompile all workflows at once:

    gh aw compile --all

    Verify the result:

    gh aw compile --validate

    How to investigate the mismatch

    The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

    • The raw frontmatter text that was used as input
    • Any imported files that were included in the hash
    • The canonical JSON that was fed to SHA-256
    • The resulting hash value

    This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

    This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

    gh aw add <path>@<exact-sha>
    gh aw compile

    How to disable this check

    [!CAUTION]
    Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

    Set stale-check: false in the on: section of your workflow frontmatter:

    on:
      issues:
        types: [opened]
      stale-check: false

    After editing, recompile the workflow: gh aw compile

    Generated from Crane · ◷
11. github-actions commented on May 25, 2026

    

    github-actionsBot

    on May 25, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 26415404015 failed.

    🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

    This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

    To fix, recompile the workflow:

    gh aw compile

    Then commit and push the updated .lock.yml file.

    More ways to recompile

    Using the gh-aw MCP server (if configured):

    { "tool": "compile", "arguments": { "validate": true } }

    Recompile all workflows at once:

    gh aw compile --all

    Verify the result:

    gh aw compile --validate

    How to investigate the mismatch

    The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

    • The raw frontmatter text that was used as input
    • Any imported files that were included in the hash
    • The canonical JSON that was fed to SHA-256
    • The resulting hash value

    This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

    This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

    gh aw add <path>@<exact-sha>
    gh aw compile

    How to disable this check

    [!CAUTION]
    Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

    Set stale-check: false in the on: section of your workflow frontmatter:

    on:
      issues:
        types: [opened]
      stale-check: false

    After editing, recompile the workflow: gh aw compile

    Generated from Crane · ◷
12. github-actions commented on May 26, 2026

    

    github-actionsBot

    on May 26, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 26426849045 failed.

    🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

    This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

    To fix, recompile the workflow:

    gh aw compile

    Then commit and push the updated .lock.yml file.

    More ways to recompile

    Using the gh-aw MCP server (if configured):

    { "tool": "compile", "arguments": { "validate": true } }

    Recompile all workflows at once:

    gh aw compile --all

    Verify the result:

    gh aw compile --validate

    How to investigate the mismatch

    The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

    • The raw frontmatter text that was used as input
    • Any imported files that were included in the hash
    • The canonical JSON that was fed to SHA-256
    • The resulting hash value

    This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

    This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

    gh aw add <path>@<exact-sha>
    gh aw compile

    How to disable this check

    [!CAUTION]
    Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

    Set stale-check: false in the on: section of your workflow frontmatter:

    on:
      issues:
        types: [opened]
      stale-check: false

    After editing, recompile the workflow: gh aw compile

    Generated from Crane · ◷
13. github-actions commented on May 26, 2026

    

    github-actionsBot

    on May 26, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 26439097480 failed.

    🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

    This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

    To fix, recompile the workflow:

    gh aw compile

    Then commit and push the updated .lock.yml file.

    More ways to recompile

    Using the gh-aw MCP server (if configured):

    { "tool": "compile", "arguments": { "validate": true } }

    Recompile all workflows at once:

    gh aw compile --all

    Verify the result:

    gh aw compile --validate

    How to investigate the mismatch

    The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

    • The raw frontmatter text that was used as input
    • Any imported files that were included in the hash
    • The canonical JSON that was fed to SHA-256
    • The resulting hash value

    This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

    This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

    gh aw add <path>@<exact-sha>
    gh aw compile

    How to disable this check

    [!CAUTION]
    Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

    Set stale-check: false in the on: section of your workflow frontmatter:

    on:
      issues:
        types: [opened]
      stale-check: false

    After editing, recompile the workflow: gh aw compile

    Generated from Crane · ◷
14. github-actions commented on May 26, 2026

    

    github-actionsBot

    on May 26, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 26450820784 failed.

    🔒 Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

    This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

    To fix, recompile the workflow:

    gh aw compile

    Then commit and push the updated .lock.yml file.

    More ways to recompile

    Using the gh-aw MCP server (if configured):

    { "tool": "compile", "arguments": { "validate": true } }

    Recompile all workflows at once:

    gh aw compile --all

    Verify the result:

    gh aw compile --validate

    How to investigate the mismatch

    The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

    • The raw frontmatter text that was used as input
    • Any imported files that were included in the hash
    • The canonical JSON that was fed to SHA-256
    • The resulting hash value

    This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

    This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

    gh aw add <path>@<exact-sha>
    gh aw compile

    How to disable this check

    [!CAUTION]
    Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

    Set stale-check: false in the on: section of your workflow frontmatter:

    on:
      issues:
        types: [opened]
      stale-check: false

    After editing, recompile the workflow: gh aw compile

    Generated from Crane · ◷
15. mrjf commented on May 26, 2026

    

    mrjf

    on May 26, 2026

    Contributor

    More actions

    @Coilot

    gh aw compile
    apm compile

    fix this
16. 198 remaining items

    Load more

    Load more actions

17. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28290025574 failed.

    ⚠️ Code Push Failed: A code push safe output failed, and subsequent safe outputs were cancelled.
    Code Push Errors:

    • push_to_pull_request_branch: Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'crane/crane-migration-python-to-go-full-apm-cli-rewrite': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.

    Generated from Crane · ● 125M · ◷
18. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28291358356 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

      └ 38 lines...
    ● Bring in the test file change from main (shell)
      │ cd /home/runner/work/apm/apm && git checkout origin/main --
      │ tests/unit/test_migration_ci_workflow.py 2>/dev/null
      │ git --no-pager diff HEAD tests/unit/test_migration_ci_workflow.py | head -30
      └ 1 line...
    ● Build Go binary with all fixes (shell)
      │ cd /home/runner/work/apm/apm && go build -o /tmp/gh-aw/agent/apm-go
      │ ./cmd/apm/ 2>&1
      └ 1 line...
    

    Generated from Crane · ● 196.3M · ◷
19. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28292317669 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    ● Check what update cache files are created (shell)
      │ mkdir -p /tmp/fresh-home-6
      │ # First run - should trigger update check
      │ (cd /tmp && HOME=/tmp/fresh-home-6 /home/runner/work/apm/apm/.venv/bin/apm
      │ install --help 2>&1 | head -3)
      │ echo "After first run, ~/.cache or ~/.apm contents:"...
      └ 7 lines...
    Found the root cause: `apm audit` is the first alphabetical command, so it runs with a fresh HOME and triggers Python's update check. The update notice is stripped by `_normalize`, but the trailing blank line isn't. Fix: update `_normalize_cli_output` to strip leading blank lines too:
    ● Edit test_python_behavior_contracts.py +1 -1
      └ tests/parity/test_python_behavior_contracts.py
    

    Generated from Crane · ● 148M · ◷
20. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28293495165 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Failed to get response from the AI model; retried 5 times (total retry wait time: 98.07 seconds) (Request-ID 79a05740-35b3-4236-b5d4-c9decf470b2a) Last error: CAPIError: 429 Maximum effective tokens exceeded (25027747.40 / 25000000).
    Changes   +152 -131
    Duration  41m 21s
    Tokens    ↑ 22.0m • ↓ 118.0k • 21.4m (cached)
    Failed to get response from the AI model; retried 5 times (total retry wait time: 89.13 seconds) (Request-ID 975cb0af-9afd-438e-b377-4352c9fdab78) Last error: CAPIError: 429 Maximum effective tokens exceeded (25027747.40 / 25000000).
    Changes   +152 -131
    Duration  42m 57s
    Failed to get response from the AI model; retried 5 times (total retry wait time: 93.92 seconds) (Request-ID 67be2137-5d62-41c5-93bb-1c624feca885) Last error: CAPIError: 429 Maximum effective tokens exceeded (25027747.40 / 25000000).
    Changes   +152 -131
    Duration  44m 42s
    

    Generated from Crane · ● 225.2M · ◷
21. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28294344303 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    ● Read cmd_mcp.go
      │ cmd/apm/cmd_mcp.go
      └ L110:135 (26 lines read)
    ● Edit cmd_mcp.go +2 -1
      └ cmd/apm/cmd_mcp.go
    Now build and test:
    ● Build Go binary (shell)
      │ cd /home/runner/work/apm/apm && go build -o /tmp/gh-aw/agent/apm-go
      │ ./cmd/apm 2>&1
      └ 1 line...
    

    Generated from Crane · ● 183.9M · ◷
22. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28296433386 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    <system_notification>Background agent fix-help-parity (Fix Go CLI help parity) completed.</system_notification>
    ● Read (General-purpose agent — Fix Go CLI help parity)
      └ Running
    <system_notification>Background agent fix-help-parity (Fix Go CLI help parity) completed.</system_notification>
    ● Read (General-purpose agent — Fix Go CLI help parity)
      └ Running
    <system_notification>Background agent fix-help-parity (Fix Go CLI help parity) completed.</system_notification>
    ● Read (General-purpose agent — Fix Go CLI help parity)
      └ Running
    <system_notification>Background agent fix-help-parity (Fix Go CLI help parity) completed.</system_notification>
    

    Generated from Crane · ● 178.6M · ◷
23. github-actions commented on Jun 27, 2026

    

    github-actionsBot

    on Jun 27, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 28297318792 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

      │ "deps info --help" \...
      └ 475 lines...
    Now let me get the Go output for all failing commands to see exact diffs:
    ● Get exact Go help text for all 29 failing commands (shell)
      │ cd /home/runner/work/apm/apm && for cmd in \
      │ "audit --help" \
      │ "cache prune --help" \
      │ "deps clean --help" \
      │ "deps info --help" \...
      └ 451 lines...
    

    Generated from Crane · ● 142M · ◷
24. github-actions commented on Aug 17, 2026

    

    github-actionsBot

    on Aug 17, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 32037027394 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  19s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  41s
    

    Generated from Crane · ◷
25. github-actions commented on Aug 17, 2026

    

    github-actionsBot

    on Aug 17, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 32037961544 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  19s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  40s
    

    Generated from Crane · ◷
26. github-actions commented on Aug 17, 2026

    

    github-actionsBot

    on Aug 17, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 32039257802 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  19s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  41s
    

    Generated from Crane · ◷
27. github-actions commented on Aug 17, 2026

    

    github-actionsBot

    on Aug 17, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 32041312785 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  18s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  40s
    

    Generated from Crane · ◷
28. github-actions commented on Aug 17, 2026

    

    github-actionsBot

    on Aug 17, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 32044319599 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  19s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  41s
    

    Generated from Crane · ◷
29. github-actions commented on Sep 1, 2026

    

    github-actionsBot

    on Sep 1, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 33461800246 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  18s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  40s
    

    Generated from Crane · ◷
30. github-actions commented on Sep 23, 2026

    

    github-actionsBot

    on Sep 23, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 35889470262 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  7s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  18s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  40s
    

    Generated from Crane · ◷
31. github-actions commented on Oct 10, 2026

    

    github-actionsBot

    on Oct 10, 2026 – with GitHub Actions

    ContributorAuthor

    More actions

    Agent job 38038475043 failed.

    ⚠️ Engine Failure: The copilot engine terminated unexpectedly.

    Last agent output:

    Changes   +0 -0
    Duration  6s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  17s
    Authentication failed with provider at (172.30.0.30/redacted) (HTTP 401).
      Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
    Changes   +0 -0
    Duration  38s
    

    Generated from Crane · ◷