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 #2335] Cant delete user CLI #6644

New Issue
Closed
opened 2026-04-20 17:14:18 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-20 17:14:18 -05:00
Owner
Copy Link

Originally created by @Revenger on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2335

Pre-submission checklist

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

Description

Sent a delete command to my test users ID 3 and 4 without he -n command.
Now I am trying with the -n to delete the test users don't have a live email nor is the email smpt postfix etc server being used on Vikunja and my local services.
I get a error now saying the user doesn't exist when its still showing up.
Both ID 3 and 4 are showing this.

Accounts are still working in the webui.

Also the test for confirmation should be presented in uppercase in the description text.

Vikunja Version

2.1.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Image
Originally created by @Revenger on GitHub (Mar 2, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2335 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Sent a delete command to my test users ID 3 and 4 without he -n command. Now I am trying with the -n to delete the test users don't have a live email nor is the email smpt postfix etc server being used on Vikunja and my local services. I get a error now saying the user doesn't exist when its still showing up. Both ID 3 and 4 are showing this. Accounts are still working in the webui. Also the test for confirmation should be presented in uppercase in the description text. ### Vikunja Version 2.1.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots <img width="1147" height="320" alt="Image" src="https://github.com/user-attachments/assets/3a35ee74-0d1a-4a03-99ed-7e4f2df64185" />
GiteaMirror commented 2026-04-20 17:14:19 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 2, 2026):

Is the sqlite database that's logged in the console the one that you're actually using?

<!-- gh-comment-id:3985256672 --> @kolaente commented on GitHub (Mar 2, 2026): Is the sqlite database that's logged in the console the one that you're actually using?
GiteaMirror commented 2026-04-20 17:14:19 -05:00
Author
Owner
Copy Link

@Revenger commented on GitHub (Mar 2, 2026):

Should be the same one.
I created the users using the cli commands just half a hour or so earlier and logged in with that user to do the test of my other report.
And haven't touched any config for the SQL stuff.
Also showing the list and trying to delete the commands were right back to back in the console.

First command try to delete was without the -n then I realised it sends a message to confirm so tried with -n and got that.

<!-- gh-comment-id:3985601941 --> @Revenger commented on GitHub (Mar 2, 2026): Should be the same one. I created the users using the cli commands just half a hour or so earlier and logged in with that user to do the test of my other report. And haven't touched any config for the SQL stuff. Also showing the list and trying to delete the commands were right back to back in the console. First command try to delete was without the -n then I realised it sends a message to confirm so tried with -n and got that.
GiteaMirror commented 2026-04-20 17:14:19 -05:00
Author
Owner
Copy Link

@urmel1960 commented on GitHub (Mar 2, 2026):

Having the same issue with 2.1:

time=2026-03-02T21:35:26.183Z level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-03-02T21:35:26.184Z level=INFO msg="Running migrations…"
time=2026-03-02T21:35:26.207Z level=INFO msg="Ran all migrations successfully."
You requested to delete the user immediately. Are you sure?
To confirm, please type "yes, I confirm" in all uppercase:
YES, I CONFIRM
time=2026-03-02T21:35:32.268Z level=ERROR msg="Error removing the user: User does not exist [user id: 2]"

<!-- gh-comment-id:3987066922 --> @urmel1960 commented on GitHub (Mar 2, 2026): Having the same issue with 2.1: > time=2026-03-02T21:35:26.183Z level=INFO msg="Using config file: /etc/vikunja/config.yml" time=2026-03-02T21:35:26.184Z level=INFO msg="Running migrations…" time=2026-03-02T21:35:26.207Z level=INFO msg="Ran all migrations successfully." You requested to delete the user immediately. Are you sure? To confirm, please type "yes, I confirm" in all uppercase: YES, I CONFIRM time=2026-03-02T21:35:32.268Z level=ERROR msg="Error removing the user: User does not exist [user id: 2]"
GiteaMirror commented 2026-04-20 17:14:20 -05:00
Author
Owner
Copy Link

@chau-intl commented on GitHub (Mar 3, 2026):

I also have the same issue with 2.1 but running on PostgreSQL.

<!-- gh-comment-id:3989412391 --> @chau-intl commented on GitHub (Mar 3, 2026): I also have the same issue with 2.1 but running on PostgreSQL.
GiteaMirror commented 2026-04-20 17:14:21 -05:00
Author
Owner
Copy Link

@tink-bot commented on GitHub (Mar 10, 2026):

Fixed in #2386 — the user row was being deleted before the notification was sent, and ShouldNotify() tried to look up the (now-deleted) user, causing the error.

<!-- gh-comment-id:4034917432 --> @tink-bot commented on GitHub (Mar 10, 2026): Fixed in #2386 — the user row was being deleted before the notification was sent, and `ShouldNotify()` tried to look up the (now-deleted) user, causing the error.
GiteaMirror commented 2026-04-20 17:14:21 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Mar 10, 2026):

This issue has been fixed in #2386, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4034918056 --> @vikunja-bot-app[bot] commented on GitHub (Mar 10, 2026): This issue has been fixed in #2386, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 17:14:22 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Mar 10, 2026):

This issue has been fixed in #2386, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4034944317 --> @vikunja-bot-app[bot] commented on GitHub (Mar 10, 2026): This issue has been fixed in #2386, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
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
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#6644
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?