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

no logs in 1.0.0 #2506

New Issue
Closed
opened 2026-03-22 14:09:40 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-03-22 14:09:40 -05:00
Owner
Copy Link

Originally created by @asarubbo on GitHub (Jan 29, 2026).

Pre-submission checklist

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

Description

I'm migrating from 0.24.6 to 1.0.0

my config.yml related to logs is:

log:
  path: /opt/vikunjia-logs/
  enabled: true
  standard: "file"
  level: "DEBUG"
  format: "text"
  database: "file"
  databaselevel: "ERROR"
  http: "file"
  echo: "file"
  events: "file"
  eventslevel: "DEBUG"

However in 1.0.0 I can see only standard.log

Vikunja Version

1.0.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @asarubbo on GitHub (Jan 29, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description I'm migrating from 0.24.6 to 1.0.0 my config.yml related to logs is: ``` log: path: /opt/vikunjia-logs/ enabled: true standard: "file" level: "DEBUG" format: "text" database: "file" databaselevel: "ERROR" http: "file" echo: "file" events: "file" eventslevel: "DEBUG" ``` However in 1.0.0 I can see only `standard.log` ### Vikunja Version 1.0.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:09:41 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 8, 2026):

Seems like this was a regression caused by the refactor to slog, will be fixed in https://github.com/go-vikunja/vikunja/pull/2206

@kolaente commented on GitHub (Feb 8, 2026): Seems like this was a regression caused by the refactor to `slog`, will be fixed in https://github.com/go-vikunja/vikunja/pull/2206
GiteaMirror commented 2026-03-22 14:09:41 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Feb 8, 2026):

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

@vikunja-bot-app[bot] commented on GitHub (Feb 8, 2026): This issue has been fixed in #2206, 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-03-22 14:09:42 -05:00
Author
Owner
Copy Link

@asarubbo commented on GitHub (Mar 3, 2026):

I'm on 1.1.0 and now I can see the logs, however the http.log is missing the IP address.

0.24.6:

2026-03-03T11:38:10+01:00: WEB  ▶ $IP  POST 200 /api/v1/tasks/5777 7.147044ms - Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0

1.1.0:

time=2026-03-03T11:18:56.357+01:00 level=INFO component=http method=GET uri=/api/v1/user status=200 latency=593.792µs

Is there something I'm missing? The config.yml is still the same

@asarubbo commented on GitHub (Mar 3, 2026): I'm on 1.1.0 and now I can see the logs, however the `http.log` is missing the IP address. 0.24.6: ``` 2026-03-03T11:38:10+01:00: WEB ▶ $IP POST 200 /api/v1/tasks/5777 7.147044ms - Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0 ``` 1.1.0: ``` time=2026-03-03T11:18:56.357+01:00 level=INFO component=http method=GET uri=/api/v1/user status=200 latency=593.792µs ``` Is there something I'm missing? The `config.yml` is still the same
GiteaMirror commented 2026-03-22 14:09:43 -05:00
Author
Owner
Copy Link

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

Is this the same with 2.1.0?

@kolaente commented on GitHub (Mar 3, 2026): Is this the same with 2.1.0?
GiteaMirror commented 2026-03-22 14:09:44 -05:00
Author
Owner
Copy Link

@asarubbo commented on GitHub (Mar 3, 2026):

Is this the same with 2.1.0?

yes, it is the same

@asarubbo commented on GitHub (Mar 3, 2026): > Is this the same with 2.1.0? yes, it is the same
GiteaMirror commented 2026-03-22 14:09:46 -05:00
Author
Owner
Copy Link

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

Remote IP not showing up will be fixed in https://github.com/go-vikunja/vikunja/pull/2362

@kolaente commented on GitHub (Mar 4, 2026): Remote IP not showing up will be fixed in https://github.com/go-vikunja/vikunja/pull/2362
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#2506
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?