• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

thomwiggers / onebot / 34606921941
72%

Build:
DEFAULT BRANCH: develop
Ran 11 Sep 2026 01:54PM UTC
Jobs 5
Files 17
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Sep 2026 01:53PM UTC coverage: 71.595% (+1.9%) from 69.703%
34606921941

push

github

web-flow
Fix Spotify OAuth callback crash for untracked users, add .whoami (#264)

* fix(spotify): don't crash callback when user isn't tracked

Users who only ever talk to the bot in a query were never added to
active_users, because on_privmsg bails out on any target that isn't a
channel the bot is in. get_user() then returns None, and the Spotify
OAuth callback called set_setting() on it, raising AttributeError in the
HTTP handler thread -- after it had already told the browser "Stored
your token".

- users: track users seen in a query (no channel attached), so commands
  and identification work for PM-only users.
- users: only part users from channels they were actually seen in, so a
  query-tracked user isn't dropped when the bot leaves a channel.
- users: the nickserv id function no longer looks itself up via
  get_user(), which had the same None dereference.
- spotify: bail out with a 404 when the user is unknown, wait for the
  store to complete before reporting success, only mark a code as seen
  once it worked, and log+500 on unexpected errors instead of leaking a
  traceback to the socket server.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SmGNUYmuLWVF7ptiHtdobe

* fix(users): don't track services talking to us in NOTICEs

Query tracking is for people, not for NickServ. Also exercise the real
User.set_setting path (async identification included) from the Spotify
callback test.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SmGNUYmuLWVF7ptiHtdobe

* feat(users): add a whoami command

Replies with the identity the bot resolved for you (the nickserv
account, what.cd name or hostmask, depending on identify_by) plus the
mask it has on file, so it's obvious whether the bot knows who you are
before a command silently misbehaves.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SmGNUYmuLWV... (continued)

43 of 45 new or added lines in 3 files covered. (95.56%)

1104 of 1542 relevant lines covered (71.6%)

3.58 hits per line

Uncovered Changes

Lines Coverage ∆ File
2
93.49
-0.26% onebot/plugins/users.py
Jobs
ID Job ID Ran Files Coverage
1 run-3.13 - 34606921941.1 11 Sep 2026 01:54PM UTC 17
71.6
GitHub Action Run
2 run-3.14 - 34606921941.2 11 Sep 2026 01:54PM UTC 17
71.54
GitHub Action Run
3 run-3.11 - 34606921941.3 11 Sep 2026 01:54PM UTC 17
71.6
GitHub Action Run
4 run-3.x - 34606921941.4 11 Sep 2026 01:54PM UTC 17
71.54
GitHub Action Run
5 run-3.12 - 34606921941.5 11 Sep 2026 01:54PM UTC 17
71.6
GitHub Action Run
Source Files on build 34606921941
  • Tree
  • List 17
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #34606921941
  • eb7a281a on github
  • Prev Build on develop (#33601700712)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc