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

[GH-ISSUE #515] Option to return detailed error messages #6208

New Issue
Open
opened 2026-04-20 16:48:22 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 16:48:22 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/515

Original issue by xeruf on 2022-07-17T21:42:11.000Z

As me and my colleagues are encountering a few 500's for some actions, it would be good to not always have to look into the log but have an option that the api returns a short error message (just the error message it is printing to the log anyways) - and of course make the frontend display it.

Original issue on Gitea

@kolaente commented on 2022-07-18T10:26:39.000Z:

I'm not sure about this. I don't think we should report internal errors to the outside because it could give away internals to potential attackers but security through obscurity is always a bad idea.

Why would you want to do that, to make reporting easier?

xeruf commented on 2022-07-18T12:01:09.000Z:

Yes, so users can say more than "I got an internal server error", because currently I have to either reproduce it or ask for a timestamp and plow through the logs.
With a proper error message I could diagnose the issue directly.
Our instance for example only has trusted users anyways through its SSO, so I don't see an issue there.

@kolaente commented on 2022-07-18T20:42:13.000Z:

Malicous users might as well trigger a 500 without being authenticated but that could mitigated by not exposing an internal instance to the public.

Still, I'm a bit hesitant to expose this to the outside. If the primary goal is to make reporting easier, what do you think of a button users can press if an error 500 occures which would send the logged error message to somewhere else? (Either directly to us or store it somewhere were the admin could grab it to post in an issue or something).

Or maybe just change the sentry integration a bit so that it reports all 500s automatically.

xeruf commented on 2022-07-18T21:03:53.000Z:

Can't this work in a way that it only returns details for authenticated users?

Yeah I guess using proper logging capturing is more appropriate (still struggling with loki... https://open.greenhost.net/stackspin/stackspin/-/issues/1340), but I also like empowering users - the error message might help them to find a temporary workaround.

@kolaente commented on 2022-07-19T15:18:49.000Z:

Can't this work in a way that it only returns details for authenticated users?

I think we could do that.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/515 _Original issue by xeruf on 2022-07-17T21:42:11.000Z_ As me and my colleagues are encountering a few 500's for some actions, it would be good to not always have to look into the log but have an option that the api returns a short error message (just the error message it is printing to the log anyways) - and of course make the frontend display it. [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1212) --- _**@kolaente** commented on 2022-07-18T10:26:39.000Z_: I'm not sure about this. I don't think we should report internal errors to the outside because it could give away internals to potential attackers but security through obscurity is always a bad idea. Why would you want to do that, to make reporting easier? --- _**xeruf** commented on 2022-07-18T12:01:09.000Z_: Yes, so users can say more than "I got an internal server error", because currently I have to either reproduce it or ask for a timestamp and plow through the logs. With a proper error message I could diagnose the issue directly. Our instance for example only has trusted users anyways through its SSO, so I don't see an issue there. --- _**@kolaente** commented on 2022-07-18T20:42:13.000Z_: Malicous users might as well trigger a 500 without being authenticated but that could mitigated by not exposing an internal instance to the public. Still, I'm a bit hesitant to expose this to the outside. If the primary goal is to make reporting easier, what do you think of a button users can press if an error 500 occures which would send the logged error message to somewhere else? (Either directly to us or store it somewhere were the admin could grab it to post in an issue or something). Or maybe just change the sentry integration a bit so that it reports all 500s automatically. --- _**xeruf** commented on 2022-07-18T21:03:53.000Z_: Can't this work in a way that it only returns details for authenticated users? Yeah I guess using proper logging capturing is more appropriate (still struggling with loki... https://open.greenhost.net/stackspin/stackspin/-/issues/1340), but I also like empowering users - the error message might help them to find a temporary workaround. --- _**@kolaente** commented on 2022-07-19T15:18:49.000Z_: > Can't this work in a way that it only returns details for authenticated users? I think we could do that.
GiteaMirror added the area/apiarea/frontendconcern/ux labels 2026-04-20 16:48:23 -05:00
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/frontend concern/ux
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#6208
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?