Open eduardoj opened 1 month ago
This issue can be closed, as the user in request.creator
is currently in deleted state
.
So... next time this job runs for a deleted user, we should remember throwing an exception is fine...?
Wouldn't it be better if we fix the code so this will not happen again?
So... next time this job runs for a deleted user, we should remember throwing an exception is fine...?
Wouldn't it be better if we fix the code so this will not happen again?
The exception is raised intentionally https://github.com/openSUSE/open-build-service/blob/master/src/api/app/models/user.rb#L233
The exception is raised intentionally https://github.com/openSUSE/open-build-service/blob/master/src/api/app/models/user.rb#L233
Yep. That looks wrong to me. The exception is thrown and the rest of the code is not run, preventing the other users and the groups from being updated.
See this exception on Errbit
Couldn't find User with login = $USER
Summary
Where
delayed_job#BsRequestCleanTasksCacheJob
Occured
Aug 19 12:48pm
Similar
37
Params
Session
Backtrace
Environment