Google Chat Pub/Sub IAM configuration errors

NousResearch/hermes-agent · cluster 22947 · docs

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 1 PR. Broad area: open items may be separate problems.

These issues concern incorrect IAM principal instructions for Google Chat's Pub/Sub integration, specifically using the wrong service account in topic bindings. Includes a related bug where the misconfiguration may result in unresolved bot_user_id and missing events.

Open issues2

  • Issue#22947[Bug]: google_chat, error in iam binding for topic instructions (use service account of app, not chat-api-push)
  • Issue#68387[Bug]: Google Chat connects successfully but bot_user_id remains unresolved and no events are received

Open PRs1

  • PR#25557fix(docs): correct Google Chat Pub/Sub IAM principal to workspace add-ons SA
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
docs
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.