mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-03 00:46:57 -05:00
Invalid cached avatar type for user 1, size 40. Expected CachedAvatar #804
Labels
No labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
question
security
support
upstream issue
waiting for reply
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vikunja-go-vikunja#804
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @rhclayto on GitHub (Feb 9, 2026).
Pre-submission checklist
Description
I updated to 1.1.0 & began receiving these messages in the logs:
The string value there is a really long sequence, I have only included the first few characters.
I am using Gravatar (my own provider, as noted at the issue where I created the feature to have configurable gravatar URLs).
When I go to the avatar section of the settings GUI, I have no option to select avatar method, only the following text:
However, it is not the case that my avatar provider is sending an avatar URL. My provider, our own Authelia instance, does not send the picture claim. At an earlier time I had this same issue but I was able to work around it by excluding the picture claim from the claims sent by Authelia to Vikunja. I am now seeing this behavior again, even though there is no picture claim.
It seems that it might not be a good idea in the first place for the SSO feature to assume that if a pricture claim is present in the OIDC provider's response that the user necessrily wants it to take precedence over any other avatar method, & remove the ability to choose an avatar method. I looked into doing a PR for that but it seemed a little too complicated a change for me to make with the time I have available.
But in the second place, it seems like a bug for the SSO feature to override your avatar preference when there is no provided avatar URL in the OIDC response.
Vikunja Version
v1.1.0
Browser and version
Firefox/Chrome latest
Can you reproduce the bug on the Vikunja demo site?
Please select
Screenshots
No response
@winkelement commented on GitHub (Feb 10, 2026):
I can confirm this.
Vikunja 1.0 | OIDC Provider Google (via dex)
@kolaente commented on GitHub (Feb 11, 2026):
are you using redis?
@rhclayto commented on GitHub (Feb 11, 2026):
I am using res, yes.
@winkelement commented on GitHub (Feb 12, 2026):
Same here (using Valkey).
This is how the data looks inside the KV db:
@kolaente commented on GitHub (Feb 12, 2026):
Does it work without redis?
@winkelement commented on GitHub (Feb 27, 2026):
No error message with redis disabled for me.