Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: ensure faculty is saved on user create #664

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

tymees
Copy link
Member

@tymees tymees commented Apr 25, 2024

Re #611

Note: once again this PR targets acceptation, as I deem this fix important enough to deploy quickly. It can be cleanly applied to develop too tho, if that's what ya'll prefer

I've tested if the problem is related to the first login, and while I was skeptical it really was this problem, it does seem to be. So, this PR adds one line of code to ensure the user model is saved first. As this 'field' is the last to be 'set', it should be save to do. (And even if that's not the case, our try/catch will prevent any real problems for the user).

I'm still a bit mystified why the percentage of users without a faculty set is this high if it's only a problem for initial logins... But this fix should at least aleviate the problem a bit.

@tymees tymees requested review from miggol and EdoStorm96 April 25, 2024 15:39
Copy link
Contributor

@miggol miggol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting! I'm curious to see if this completely fixes it or if some faculty errors still remain.

@tymees tymees merged commit d2f4256 into acceptation Jun 12, 2024
4 checks passed
@tymees tymees deleted the fix/faculty-not-saved branch June 12, 2024 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants