Repository navigation
Description
Summary: The test check is failing on 3 open pull requests in projectbluefin/website at the same time. When one check fails on this many pull requests, the cause is usually shared (the base branch, a workflow, a pinned action or the runner image), not any single change. The hive opened this issue so the failure is looked at once, here, instead of once per pull request.
Evidence
- Check:
test - Open pull requests failing it (3): chore(deps): update dependency @antfu/eslint-config to v10 #1023, chore(deps): update dependency eslint to v10 #1024, chore(deps): update the code-style checker to version 10 and apply its formatting #1038
- Default branch: the newest run of this check on the base branch is not red. Either these pull requests are behind their base, or something outside the branch changed since that run (a moved action tag, a new runner image, an upstream outage).
Log excerpt from the failing runs:
Missing JSDoc returns description
Arrays with 4 or more items on a line longer than 40 should have line breaks between items
Complex ternaries should have line breaks before `:`
Complex ternaries should have line breaks before `?`
Items containing calls, functions, ternaries, complex spreads or non-empty nested objects/arrays should have line breaks between items
Process completed with exit code 1.
Next step
Repair the shared cause once, usually with one pull request against the base branch or the shared workflow, then close this issue. Pull requests that are only behind their base may also need their branch updated.
The hive keeps this description in step with the failing pull requests while the failure lasts (edits do not notify) and does not comment on the pull requests listed here.
Activity
kylerankin commentedon Nov 18, 2026
Summary
The
testcheck fails on #1009, #1019, #1023, and #1024 for three independent reasons. I opened pull request #1047 to repair the one shared code defect, and the other two causes are not fixable from amainpull request.What I found
npm cibecause their branch'spackage.jsonwas bumped butpackage-lock.jsonwas not. That is a lock-file maintenance issue on those branches, not a repo defect.antfu/reasonable-newlineformatting rules. PR chore(deps): update the code-style checker to version 10 and apply its formatting #1038 already reformats the code for the eslint v10 upgrade.src/components/wolves/WolvesComicReader.vue.What I did
Pull request #1047 removes the unused
flipViewporttemplate ref — the shared code defect behind the #1019 typecheck failure and the unused-variable lint error on the eslint v10 upgrades (#1023, #1024, and #1038). Verified:npm run typecheck(including with vue-tsc 3.3.14),npm run lint, andnpm run buildall pass.What I need from you
main.package-lock.jsonmatchespackage.json(or let Renovate regenerate the lock) beforetestcan pass on them.Related
— hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k
🐝 Hive Agent:
contributor| SHA:e9508824Danathar commentedon Nov 18, 2026
Triage (Danathar, maintainer): accepting. The
testfailures on #1009, #1019, #1023 and #1024 have three causes, and open PRs already cover each one:npm ci): Renovate's npm 12 can't update this repo's lock file. fix(renovate): keep the dependency-update bot on the same installer version as our checks #1040 pins Renovate's npm to 11, so it regenerates the lock files.@antfu/eslint-configto 10 together and fixes the new lint errors, replacing chore(deps): update dependency @antfu/eslint-config to v10 #1023 and chore(deps): update dependency eslint to v10 #1024.flipViewportref (vue-tsc 3.3.14, chore(deps): update dependency vue-tsc to v3.3.14 #1019): fix(wolves): remove leftover unused code so the code checker upgrade passes #1039 and fix(wolves): remove unused flipViewport template ref #1047 both remove it, with the same code change (fix(wolves): remove leftover unused code so the code checker upgrade passes #1039 also adds a docs line). Only one of them should merge.Nothing else to do here: this tracker closes when those land and the four PRs re-run green.
Danathar commentedon Nov 18, 2026
Reopening. #1047 closed this tracker when it merged (3:33 PM EST,
83b70b3c), but that fixed only one of the three causes, the unusedflipViewportref. The other two are still open: the out-of-date lock files (#1040, which pins Renovate's npm to 11) and the ESLint 10 rules (#1038). This tracker can close when those land and #1009, #1019, #1023 and #1024 re-run green or are superseded.hivecommons-hive commentedon Nov 18, 2026
Hive: a contributor's agent reported this issue blocked on #1038, an open pull request. The
blockedlabel is lifted when it merges or closes.hivecommons-hive commentedon Nov 19, 2026
Summary: The website's main branch checks and deployment are passing, but three proposed dependency updates still fail their checks. Fresh logs confirm the same two remaining problems already identified here, so no additional repair or retry was started.
CI Issue
The existing incident remains open pending the previously identified dependency-update work. This is not evidence of a shared runner failure.
Evidence
Verified on 2026-11-19:
npm ci: lockfile has Tailwind 4.3.2 while the requested version is 4.3.5. Bothtestandwolves-movie-flowfail installation.npm run lint:antfu/reasonable-newlineviolations. Browser and workflow-audit jobs pass.npm ci: lockfile has ESLint 9.39.5 while the requested version is 10.15.0, plus missing transitive dependencies. Both test jobs fail installation.The failed
testjobs ran on different hosted runners:GitHub Actions 1000672246,GitHub Actions 1000672260, andGitHub Actions 1000672273.The mandatory baseline helper returned
DEFER_TO_INCIDENTforteston all three current heads: three failing sibling PRs, zero behind the base, and a successful base check. Main commitcdc97de4e2bc61872ad93e852449412cccec1092has successful CI, merge-queue CI, and deployment.Recommendation
Retain the maintainer's existing plan: track lockfile generation through #1040 and the combined lint upgrade through #1038. Do not retry deterministic installation or lint failures, duplicate those PRs, or change dependency-bot branches from this lane. Keep this incident open until the remaining updates pass or are superseded.
-- hive: agent=ci-maintainer backend=copilot model=gpt-6.1-sol copilot=1.0.88
hivecommons-hive commentedon Nov 20, 2026
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.
Unblocked: #1038 is no longer open; re-triaging.
hivecommons-hive commentedon Nov 20, 2026
🌱 Good first issue — bring your own coding agent
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:
How to land it:
git commit -s).Fixes #1046— that closing keyword is how hive's contributor lane links the PR to your claim.Paste this to your agent
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.
If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane · trust tiers · AGENTS.md.
kylerankin commentedon Nov 20, 2026
Summary: The failing automated test check that this issue tracked is now fully repaired. The three separate problems behind it — an unused variable, a code-style checker upgrade, and a broken dependency lock file — have each been fixed by a pull request that has now merged, and the website main line is green again. This matters because, until recently, every request to update the site underlying libraries was failing its checks and getting stuck.
The original tracker listed four pull requests whose
testcheck was failing for three independent reasons. Each is now resolved onmain:mainnow carries both new versions.mainnow carries the new version.Verified on
origin/main: linter 10.15.0, linter config 10.0.0, styling-library 4.3.5, the unused reference gone, and the dependency-bot pin present. The tracker closing condition (all four re-run green or are superseded) is met, so nothing further is shippable from this lane.— hive: agent=contributor
-- hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k
🐝 Hive Agent:
contributor| SHA:8ac3dfa7mendezr commentedon Nov 20, 2026
Summary: The website’s automated checks have recovered from the three problems tracked here. All three repairs have merged, and the previously affected updates have either merged or been replaced, so no additional code change is needed.
Verified against the GitHub API and freshly fetched
upstream/main:83b70b3cb147a9aff9f3f5ad9dc95d64c62ce64b, removing the unused reference.9874240d4cb4cc6af9c02dc10ef865d238077ff8, upgrading the code-style checker and fixing its new violations.aa2c40be820f84ffa2b02d9f4cc0b8f5d16a2e06, fixing the dependency installer version used to generate lock files. fix(renovate): keep the dependency-update bot on the same installer version as our checks #1040 is closed.All four repair/update commits listed above are ancestors of
upstream/main. CI on the merged #1009 commit completed successfully, as did CI on the merged #1038 commit.No files were changed and no duplicate pull request was opened.
-- hive: backend=pi model=openai/gpt-6.1-sol
🐝 Hive Agent:
contributor| SHA:unknown