github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2650] vikunja_user_count is not updated after successful API registration #6721

New Issue
Open
opened 2026-04-20 17:18:08 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:18:08 -05:00
Owner
Copy Link

Originally created by @booxter on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2650

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

vikunja_user_count does not update after successful user creation through the regular registration API.

I reproduced this on the public demo instance at https://try.vikunja.io:

  1. GET /api/v1/metrics returned:
    vikunja_user_count 107
  2. POST /api/v1/register succeeded with 200 OK
  3. the response returned a newly created user:
    • username: codex-demo-reg-20260416-2356
    • id: 218
    • created: 2026-04-17T01:54:09+02:00
  4. GET /api/v1/metrics still returned:
    vikunja_user_count 107
  5. after waiting a few seconds, the metric was still unchanged

So the registration API creates the user successfully, but the metric does not reflect the new user count.

Vikunja Version

Public demo: v2.3.0-101-10ec3b55

I also investigated this locally against checkout 10ec3b55b01e083268747c15ee383059f6408695.

Browser and version

N/A

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

N/A

Originally created by @booxter on GitHub (Apr 16, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2650 ## Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ## Description `vikunja_user_count` does not update after successful user creation through the regular registration API. I reproduced this on the public demo instance at `https://try.vikunja.io`: 1. `GET /api/v1/metrics` returned: `vikunja_user_count 107` 2. `POST /api/v1/register` succeeded with `200 OK` 3. the response returned a newly created user: - username: `codex-demo-reg-20260416-2356` - id: `218` - created: `2026-04-17T01:54:09+02:00` 4. `GET /api/v1/metrics` still returned: `vikunja_user_count 107` 5. after waiting a few seconds, the metric was still unchanged So the registration API creates the user successfully, but the metric does not reflect the new user count. ## Vikunja Version Public demo: `v2.3.0-101-10ec3b55` I also investigated this locally against checkout `10ec3b55b01e083268747c15ee383059f6408695`. ## Browser and version N/A ## Can you reproduce the bug on the Vikunja demo site? Yes ## Screenshots N/A
GiteaMirror added the concern/regressionarea/apiarea/auth labels 2026-04-20 17:18:08 -05:00
GiteaMirror commented 2026-04-20 17:18:09 -05:00
Author
Owner
Copy Link

@booxter commented on GitHub (Apr 16, 2026):

One note: I think there's a separate path to miss metrics update - through CLI that would need a different treatment from what I just posted in https://github.com/go-vikunja/vikunja/pull/2651

<!-- gh-comment-id:4264236024 --> @booxter commented on GitHub (Apr 16, 2026): One note: I think there's a separate path to miss metrics update - through CLI that would need a different treatment from what I just posted in https://github.com/go-vikunja/vikunja/pull/2651
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/api area/auth concern/regression
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6721
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?