2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs address misleading error messages that blame an API key when Vertex AI authentication failures occur, since Vertex uses service accounts rather than API keys.
Open issues1
- Issue#121295Vertex AI 401/403 is reported as "rejected your API key" (Vertex uses a service account, not a key)
Open PRs1
- PR#121311fix(agent): clarify Vertex authentication guidance
1 PR closed without merging
From the close comments: stale or abandoned 1
- #121576 fix(vertex): name the service account on 401 and 403, not an API key · stale or abandoned
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging