Skip to content

Fix hak check for matrix-seshat#33030

Merged
t3chguy merged 1 commit intodevelopfrom
t3chguy/fix-hak-check
Apr 2, 2026
Merged

Fix hak check for matrix-seshat#33030
t3chguy merged 1 commit intodevelopfrom
t3chguy/fix-hak-check

Conversation

@t3chguy
Copy link
Copy Markdown
Member

@t3chguy t3chguy commented Apr 2, 2026

@t3chguy t3chguy added the T-Task Tasks for the team like planning label Apr 2, 2026
@t3chguy t3chguy self-assigned this Apr 2, 2026
@t3chguy t3chguy marked this pull request as ready for review April 2, 2026 09:26
@t3chguy t3chguy requested a review from a team as a code owner April 2, 2026 09:26
@t3chguy t3chguy added this pull request to the merge queue Apr 2, 2026
@richvdh
Copy link
Copy Markdown
Member

richvdh commented Apr 2, 2026

For future reference/issue search, the error message was:

> node scripts/hak/index.ts

hak check: matrix-seshat
Error: spawn python ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at processTicksAndRejections (node:internal/process/task_queues:90:21)

@richvdh
Copy link
Copy Markdown
Member

richvdh commented Apr 2, 2026

Do we know what changed to necessitate this?

Merged via the queue into develop with commit 0a8ef85 Apr 2, 2026
73 checks passed
@t3chguy t3chguy deleted the t3chguy/fix-hak-check branch April 2, 2026 10:24
@t3chguy
Copy link
Copy Markdown
Member Author

t3chguy commented Apr 2, 2026

Something on github's parter images, seems like python is sometimes not symlinked to python3. It isn't consistent and hard to validate. Nowadays node-gyp seems to be able to use either python or python3 so checking for either tool should be the way to go.

@t3chguy t3chguy added the backport staging Label to automatically backport PR to staging branch label Apr 7, 2026
@RiotRobot
Copy link
Copy Markdown
Contributor

The backport to staging failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-staging staging
# Navigate to the new working tree
cd .worktrees/backport-staging
# Create a new branch
git switch --create backport-33030-to-staging
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0a8ef85f2f8237aa67e866e7eba8985e47ff9b86
# Push it to GitHub
git push --set-upstream origin backport-33030-to-staging
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-staging

Then, create a pull request where the base branch is staging and the compare/head branch is backport-33030-to-staging.

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

Labels

backport staging Label to automatically backport PR to staging branch T-Task Tasks for the team like planning

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants