Closed 6543 closed 2 weeks ago
might be an regression of #2126
Perhaps, related #3328
symptoms: you get just weard behaviour and some functions 'randomly' dont work ..
deleting all of that ward user related stuff (in db) and recreate the user by log in newly do fix it.
Attention: Patch coverage is 68.96552%
with 9 lines
in your changes missing coverage. Please review.
Project coverage is 26.54%. Comparing base (
b0f52b9
) to head (6cd6b54
). Report is 26 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
...re/datastore/migration/018_fix-orgs-users-match.go | 68.96% | 8 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
it only happens on very old accounts
Define "very old" - if it happened on v1 -> v2, I'd not use that adjective here.
Also: #3319 -> can likely be closed then. Great that there is a fix now for this, a bit sad that it took almost a year. However I am not sure whether you discovered this "just recently" or were actually aware of it the whole time but it simply wasn't important enough (?).
anyway it only happens on very old accounts and I did the migrations mannually at codeberg and now at kithara.
Hmm, just for the protocol, I did 20-30 manual corrections at CB throughout this time and was also solely commenting to user requests. Not sure which one you're referring to specifically but unless you did some in the recent days, this sounds a bit unfortunate.
but unless you did some in the recent days,
On monday to be exact
-> #4327
Tearing down https://woodpecker-ci-woodpecker-pr-4307.surge.sh
No idea why the corrupt entrys did exist ... we might should dig into the reason.
anyway it only happens on very old accounts and I did the migrations mannually at codeberg and now at kithara.
so we clearly should run it to catch potential hick-ups ...