GitHub check
Whole log, 32 KB
Current runner version: '2.338.1'
Runner name: 'blacksmith-8vcpu-ubuntu-2404-lf4kz3g47oask5f2'
Runner group name: 'blacksmith scale sets - blacksmith-8vcpu-ubuntu-2404'
Machine name: 'ip-172-31-73-130'
▸ GITHUB_TOKEN Permissions
Actions: read
Contents: read
Metadata: read
Secret source: Actions
Cache mode: write
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v6' (SHA:d23441a48e516b6c34aea4fa41551a30e30af803)
Download action repository 'voidzero-dev/setup-vp@v1' (SHA:250f29ce396baf5e8f24498e17c0dfdebabc26eb)
Setting BLACKSMITH_ACTIONS_RESULTS_URL to https://results-receiver.actions.githubusercontent.com/
Complete job name: Announce release on Discord
A job started hook has been configured by the self-hosted runner administrator
▸ Run '/setup.sh'
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 156
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 409
BLACKSMITH_CHECK_RUN_ID: 121010831838
BLACKSMITH_JOB_DISPLAY_NAME: Announce release on Discord
GITHUB_ACTIONS_CACHE_MODE: write
Logging daemon started (blacksmithd for logs)
Results daemon started (blacksmithd for results)
Background adoption and SSH setup started (PID: 3102)
----------------------------------------
View this job: https://app.blacksmith.sh/pingdotgg/runs/40139677692/jobs/121010831838
SSH Access (using your GitHub SSH key):
ssh -p 64000 runner@blacksmith-8vcpu-ubuntu-2404-lf4kz3g47oask5f2.vm.blacksmith.sh
No GitHub SSH key? Add one at:
https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
----------------------------------------
VM ID: blacksmith-8vcpu-ubuntu-2404-lf4kz3g47oask5f2
Host: production-152.236.40.16-x8664
Host Agent PID: 3930625
Host Agent Git SHA: 1637818df
Host CPU Manufacturer: AuthenticAMD
Blacksmith Host Generation: gen 2
Petname: production-star-gorilla-463e84c4
Region: us-east
Rootfs Version: ubuntu24-full-x64-081926
OS Version: Ubuntu 24.04.4 LTS
Enabling Blacksmith transparent cache
▸ Run actions/checkout@v6
with:
ref: 3cc31ed27c8956b36cee35a50509fb7c6869592b
sparse-checkout: /*
!/.repos/
sparse-checkout-cone-mode: false
repository: pingdotgg/t3code
token: ***
ssh-strict: true
ssh-user: git
persist-credentials: true
clean: true
fetch-depth: 1
fetch-tags: false
show-progress: true
lfs: false
submodules: false
set-safe-directory: true
allow-unsafe-pr-checkout: false
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 156
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 409
GITHUB_REPO_NAME: pingdotgg/t3code
Syncing repository: pingdotgg/t3code
▸ Getting Git version info
Working directory is '/home/runner/_work/t3code/t3code'
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/b83d248a-2279-43fe-8821-f3e497388a9c' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/local/bin/git config --global --add safe.directory /home/runner/_work/t3code/t3code
Deleting the contents of '/home/runner/_work/t3code/t3code'
▸ Determining repository object format
▸ Initializing the repository
[command]/usr/local/bin/git init /home/runner/_work/t3code/t3code
hint: Using 'master' as the name for the initial branch. This default branch name
hint: will change to "main" in Git 3.0. To configure the initial branch name
hint: to use in all of your new repositories, which will suppress this warning,
hint: call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
hint:
hint: Disable this message with "git config set advice.defaultBranchName false"
Initialized empty Git repository in /home/runner/_work/t3code/t3code/.git/
[command]/usr/local/bin/git remote add origin https://github.com/pingdotgg/t3code
▸ Disabling automatic garbage collection
[command]/usr/local/bin/git config --local gc.auto 0
▸ Setting up auth
Removing SSH command configuration
[command]/usr/local/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/local/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
Removing HTTP extra header
[command]/usr/local/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/local/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
Removing includeIf entries pointing to credentials config files
[command]/usr/local/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/local/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
[command]/usr/local/bin/git config --file /home/runner/_work/_temp/git-credentials-5cfa40c7-e8f9-4f24-a2c3-1d1e61dc530b.config http.https://github.com/.extraheader AUTHORIZATION: basic ***
[command]/usr/local/bin/git config --local includeIf.gitdir:/home/runner/_work/t3code/t3code/.git.path /home/runner/_work/_temp/git-credentials-5cfa40c7-e8f9-4f24-a2c3-1d1e61dc530b.config
[command]/usr/local/bin/git config --local includeIf.gitdir:/home/runner/_work/t3code/t3code/.git/worktrees/*.path /home/runner/_work/_temp/git-credentials-5cfa40c7-e8f9-4f24-a2c3-1d1e61dc530b.config
[command]/usr/local/bin/git config --local includeIf.gitdir:/github/workspace/.git.path /github/runner_temp/git-credentials-5cfa40c7-e8f9-4f24-a2c3-1d1e61dc530b.config
[command]/usr/local/bin/git config --local includeIf.gitdir:/github/workspace/.git/worktrees/*.path /github/runner_temp/git-credentials-5cfa40c7-e8f9-4f24-a2c3-1d1e61dc530b.config
▸ Fetching the repository
[command]/usr/local/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --filter=blob:none --depth=1 origin 3cc31ed27c8956b36cee35a50509fb7c6869592b
From https://github.com/pingdotgg/t3code
* branch 3cc31ed27c8956b36cee35a50509fb7c6869592b -> FETCH_HEAD
[command]/usr/local/bin/git rev-parse --verify --quiet 3cc31ed27c8956b36cee35a50509fb7c6869592b^{object}
3cc31ed27c8956b36cee35a50509fb7c6869592b
▸ Determining the checkout info
▸ Setting up sparse checkout
[command]/usr/local/bin/git config core.sparseCheckout true
[command]/usr/local/bin/git rev-parse --git-path info/sparse-checkout
.git/info/sparse-checkout
▸ Checking out the ref
[command]/usr/local/bin/git checkout --progress --force 3cc31ed27c8956b36cee35a50509fb7c6869592b
Updating files: 0% (1/6404)
Updating files: 1% (65/6404)
Updating files: 2% (129/6404)
Updating files: 3% (193/6404)
Updating files: 4% (257/6404)
Updating files: 5% (321/6404)
Updating files: 6% (385/6404)
Updating files: 7% (449/6404)
Updating files: 8% (513/6404)
Updating files: 9% (577/6404)
Updating files: 10% (641/6404)
Updating files: 11% (705/6404)
Updating files: 12% (769/6404)
Updating files: 13% (833/6404)
Updating files: 14% (897/6404)
Updating files: 15% (961/6404)
Updating files: 16% (1025/6404)
Updating files: 17% (1089/6404)
Updating files: 18% (1153/6404)
Updating files: 19% (1217/6404)
Updating files: 20% (1281/6404)
Updating files: 21% (1345/6404)
Updating files: 22% (1409/6404)
Updating files: 23% (1473/6404)
Updating files: 24% (1537/6404)
Updating files: 25% (1601/6404)
Updating files: 26% (1666/6404)
Updating files: 27% (1730/6404)
Updating files: 28% (1794/6404)
Updating files: 29% (1858/6404)
Updating files: 30% (1922/6404)
Updating files: 31% (1986/6404)
Updating files: 32% (2050/6404)
Updating files: 33% (2114/6404)
Updating files: 34% (2178/6404)
Updating files: 35% (2242/6404)
Updating files: 36% (2306/6404)
Updating files: 37% (2370/6404)
Updating files: 38% (2434/6404)
Updating files: 39% (2498/6404)
Updating files: 40% (2562/6404)
Updating files: 41% (2626/6404)
Updating files: 42% (2690/6404)
Updating files: 43% (2754/6404)
Updating files: 44% (2818/6404)
Updating files: 45% (2882/6404)
Updating files: 46% (2946/6404)
Updating files: 47% (3010/6404)
Updating files: 48% (3074/6404)
Updating files: 49% (3138/6404)
Updating files: 50% (3202/6404)
Updating files: 51% (3267/6404)
Updating files: 52% (3331/6404)
Updating files: 53% (3395/6404)
Updating files: 54% (3459/6404)
Updating files: 55% (3523/6404)
Updating files: 56% (3587/6404)
Updating files: 57% (3651/6404)
Updating files: 58% (3715/6404)
Updating files: 59% (3779/6404)
Updating files: 60% (3843/6404)
Updating files: 61% (3907/6404)
Updating files: 62% (3971/6404)
Updating files: 63% (4035/6404)
Updating files: 64% (4099/6404)
Updating files: 65% (4163/6404)
Updating files: 66% (4227/6404)
Updating files: 67% (4291/6404)
Updating files: 68% (4355/6404)
Updating files: 69% (4419/6404)
Updating files: 70% (4483/6404)
Updating files: 71% (4547/6404)
Updating files: 72% (4611/6404)
Updating files: 73% (4675/6404)
Updating files: 74% (4739/6404)
Updating files: 75% (4803/6404)
Updating files: 76% (4868/6404)
Updating files: 77% (4932/6404)
Updating files: 78% (4996/6404)
Updating files: 79% (5060/6404)
Updating files: 80% (5124/6404)
Updating files: 81% (5188/6404)
Updating files: 82% (5252/6404)
Updating files: 83% (5316/6404)
Updating files: 84% (5380/6404)
Updating files: 85% (5444/6404)
Updating files: 86% (5508/6404)
Updating files: 87% (5572/6404)
Updating files: 88% (5636/6404)
Updating files: 89% (5700/6404)
Updating files: 90% (5764/6404)
Updating files: 91% (5828/6404)
Updating files: 92% (5892/6404)
Updating files: 93% (5956/6404)
Updating files: 94% (6020/6404)
Updating files: 95% (6084/6404)
Updating files: 96% (6148/6404)
Updating files: 97% (6212/6404)
Updating files: 98% (6276/6404)
Updating files: 99% (6340/6404)
Updating files: 100% (6404/6404)
Updating files: 100% (6404/6404), done.
Note: switching to '3cc31ed27c8956b36cee35a50509fb7c6869592b'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 3cc31ed fix(server): websocket tickets name the route they open (#24554)
[command]/usr/local/bin/git log -1 --format=%H
3cc31ed27c8956b36cee35a50509fb7c6869592b
▸ Run voidzero-dev/setup-vp@v1
with:
node-version-file: package.json
cache: true
run-install: args:
- --filter=@t3tools/scripts...
sfw: false
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 156
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 409
GITHUB_REPO_NAME: pingdotgg/t3code
Resolved Node.js version '26.12.1' from package.json
Resolved Vite+ version '1.3.0' from package.json
Installing Vite+@1.3.0...
[command]/usr/bin/bash -c set -o pipefail; curl -fsSL --connect-timeout 5 --max-time 15 https://viteplus.dev/install.sh | bash
info: installing vite-plus@1.3.0...
info: Preparing Node.js and pnpm...
info: Installing dependencies...
✓ Dependencies installed.
Setup:
Preparing vite-plus environment.
Created Shims:
/home/runner/.vite-plus/bin/node
/home/runner/.vite-plus/bin/npm
/home/runner/.vite-plus/bin/npx
/home/runner/.vite-plus/bin/pnpm
/home/runner/.vite-plus/bin/pnpx
/home/runner/.vite-plus/bin/pn
/home/runner/.vite-plus/bin/pnx
/home/runner/.vite-plus/bin/yarn
/home/runner/.vite-plus/bin/yarnpkg
/home/runner/.vite-plus/bin/bun
/home/runner/.vite-plus/bin/bunx
/home/runner/.vite-plus/bin/vpx
/home/runner/.vite-plus/bin/vpr
Next Steps:
For Bash, run:
. "/home/runner/.vite-plus/env"
If your ~/.bashrc does not already load Vite+, add this command for interactive non-login Bash sessions.
Login Bash shells must also load the command through their login profile.
Restart an already-running IDE to load its environment. Run `vp env doctor` to verify.
✓ Vite+ setup complete.
Setting up Node.js 26.12.1 via vp env use...
[command]/home/runner/.vite-plus/bin/vp env use 26.12.1
Installing Node.js v26.12.1...
Using Node.js v26.12.1 (resolved from 26.12.1)
Auto-detected lock file: pnpm-lock.yaml
Using lock file: /home/runner/_work/t3code/t3code/pnpm-lock.yaml
Resolving dependency cache directory in: /home/runner/_work/t3code/t3code
Cache hit for: vite-plus-Linux-x64-pnpm-aaa3dc2d814f35ee60c0b24e3c85d37cf61157c4a332ca88272b32053aa0f57a
Received 402653184 of 1188978906 (33.9%), 366.8 MBs/sec
Received 1073741824 of 1188978906 (90.3%), 485.1 MBs/sec
Received 1188978906 of 1188978906 (100.0%), 494.9 MBs/sec
Cache Size: ~1134 MB (1188978906 B)
[command]/usr/bin/tar -xf /home/runner/_work/_temp/468e23f5-3640-456f-9a05-a3996fbea208/cache.tzst -P -C /home/runner/_work/t3code/t3code --use-compress-program unzstd
Cache restored successfully
Cache restored from key: vite-plus-Linux-x64-pnpm-aaa3dc2d814f35ee60c0b24e3c85d37cf61157c4a332ca88272b32053aa0f57a
▸ Running vp install --filter=@t3tools/scripts... in /home/runner/_work/t3code/t3code...
[command]/home/runner/.vite-plus/bin/vp install --filter=@t3tools/scripts...
Scope: 4 of 34 workspace projects
? Verifying lockfile against supply-chain policies (2088 entries)...
✓ Lockfile passes supply-chain policies (2088 entries in 1.6s)
Lockfile is up to date, resolution step is skipped
Packages are hard linked from the content-addressable store to the virtual store.
Content-addressable store is at: /home/runner/.local/share/pnpm/store/v11
Virtual store is at: node_modules/.pnpm
Packages: +324
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 324, reused 324, downloaded 0, added 324, done
. prepare$ vp config --no-agent
. prepare: Done
devDependencies:
+ @coderabbitai/config 1.1.0
+ @shadcn/lint 0.1.5
+ @types/node 24.12.4
+ knip 6.34.0
+ typescript <- @tsc-rs/typescript 0.8.0
+ vite-plus 1.3.0
Done in 2s using pnpm v12.14.0
Successfully ran vp install --filter=@t3tools/scripts...
vp v1.3.0
Local vite-plus:
vite-plus v1.3.0
Tools:
vite v8.3.4
rolldown v1.2.14
vitest v5.0.5
oxfmt v0.73.0
oxlint v1.88.0
oxlint-tsgolint v7.0.2004
tsdown v0.23.1
Environment:
Package manager pnpm v12.14.0
Node.js v26.12.1 (.session-node-version)
▸ Run if [ "$RELEASE_CHANNEL" = 'nightly' ]; then
if [ "$RELEASE_CHANNEL" = 'nightly' ]; then
if ! gh release view "$RELEASE_TAG" --json body --jq '.body // ""' > "$RUNNER_TEMP/discord-release-notes.md"; then
: > "$RUNNER_TEMP/discord-release-notes.md"
echo '::warning::Could not read published release notes; announcing without a changelog.'
fi
else
: > "$RUNNER_TEMP/discord-release-notes.md"
fi
shell: /usr/bin/bash -e {0}
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 156
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 409
GITHUB_REPO_NAME: pingdotgg/t3code
GH_TOKEN: ***
GH_REPO: pingdotgg/t3code
RELEASE_TAG: v0.1.3-nightly.20261024.3643
RELEASE_CHANNEL: nightly
▸ Run node scripts/notify-discord-release.ts prerelease \
node scripts/notify-discord-release.ts prerelease \
--role-id "$DISCORD_MENTION_ROLE_ID" \
--release-name "T3 Code Nightly 0.1.3-nightly.20261024.3643 (3cc31ed27c89)" \
--release-version "0.1.3-nightly.20261024.3643" \
--tag "v0.1.3-nightly.20261024.3643" \
--release-url "https://github.com/pingdotgg/t3code/releases/tag/v0.1.3-nightly.20261024.3643" \
--release-notes-file "$RUNNER_TEMP/discord-release-notes.md"
shell: /usr/bin/bash -e {0}
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 156
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 409
GITHUB_REPO_NAME: pingdotgg/t3code
DISCORD_MENTION_ROLE_ID: ***
DISCORD_WEBHOOK_URL: ***
[22:53:39.024] INFO (#1): discord release announcement starting
target: prerelease
roleIdProvided: true
roleIdLength: 19
releaseName: T3 Code Nightly 0.1.3-nightly.20261024.3643 (3cc31ed27c89)
version: 0.1.3-nightly.20261024.3643
tag: v0.1.3-nightly.20261024.3643
releaseUrl: URL {
href: 'https://github.com/pingdotgg/t3code/releases/tag/v0.1.3-nightly.20261024.3643',
origin: 'https://github.com',
protocol: 'https:',
username: '',
password: '',
host: 'github.com',
hostname: 'github.com',
port: '',
pathname: '/pingdotgg/t3code/releases/tag/v0.1.3-nightly.20261024.3643',
search: '',
searchParams: URLSearchParams {},
hash: ''
}
[22:53:39.026] INFO (#1): discord release announcement payloads built
messageCount: 1
[22:53:39.027] INFO (#1): discord webhook request dispatching
configured: true
origin: https://discord.com
pathnameSegmentCount: 4
contentLength: 26
embedCount: 1
allowedRoleMentionCount: 1
hasRoleMentionSyntax: true
[22:53:39.217] INFO (#1): discord webhook response received
status: 200
ok: true
[22:53:39.218] INFO (#1): discord release announcement completed
Post job cleanup.
Cache hit on primary key "vite-plus-Linux-x64-pnpm-aaa3dc2d814f35ee60c0b24e3c85d37cf61157c4a332ca88272b32053aa0f57a". Skipping save.
Post job cleanup.
[command]/usr/local/bin/git version
git version 2.55.0
Temporarily overriding HOME='/home/runner/_work/_temp/18c7ff9d-2131-4f77-907e-ac77d9d52109' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/local/bin/git config --global --add safe.directory /home/runner/_work/t3code/t3code
Removing SSH command configuration
[command]/usr/local/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/local/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
fatal: No url found for submodule path '.repos/alchemy-effect/submodules/distilled' in .gitmodules
Warning: The process '/usr/local/bin/git' failed with exit code 128
A job completed hook has been configured by the self-hosted runner administrator
▸ Run '/job_completed.sh'
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
BLACKSMITH_RUNNER_MESSAGE_WAIT_MS: 156
BLACKSMITH_RUNNER_ACQUIRE_JOB_MS: 409
BLACKSMITH_CHECK_RUN_ID: 121010831838
BLACKSMITH_JOB_DISPLAY_NAME: Announce release on Discord
GITHUB_ACTIONS_CACHE_MODE: write
Warning: environment evidence observer stop unavailable
Docker container cache not activated, skipping hash computation.
No active SSH sessions detected. Proceeding with shutdown immediately.
Cleaning up orphan processes