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

remove redundant mount/3 in profile_live, closes #1049 #1050

Merged
merged 5 commits into from
Sep 17, 2024

Conversation

briankariuki
Copy link
Collaborator

I've removed some redundant mount/3 code as its covered by the profile_socket functions. I've tested it both logged in and logged out and it works.

@MICHAELMUNAVU83
Copy link
Collaborator

@briankariuki , This was there for if someone logs out but there is a cache , so the system thinks there is a current_user but there is none , it broke the system , that is why it was there .

@briankariuki
Copy link
Collaborator Author

@briankariuki , This was there for if someone logs out but there is a cache , so the system thinks there is a current_user but there is none , it broke the system , that is why it was there .

How can I recreate this scenario?

@MICHAELMUNAVU83
Copy link
Collaborator

That was the problem actually , it is a sort of scenario we cannot replicate or test for , it happens sometimes when a cache happens , might you know how to simulate a cache

@MICHAELMUNAVU83
Copy link
Collaborator

@briankariuki , here is the issue #677

@wintermeyer
Copy link
Collaborator

@briankariuki , here is the issue #677

With that information @briankariuki can replicate the problem. Build one system. Log in. Reset the database. Et voila!

@wintermeyer
Copy link
Collaborator

But: One can argue that this problem never occurs in the real world since we don't reset production every day. So I would be open to accept this problem since it is only relevant on development systems.

@briankariuki
Copy link
Collaborator Author

But: One can argue that this problem never occurs in the real world.

True. I think we can close this

Copy link
Collaborator

@wintermeyer wintermeyer left a comment

Choose a reason for hiding this comment

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

@briankariuki Please do test this in production when we deploy it and have an eye on it 3-4 days after deployment. I don't want to be surprised by a bug we didn't see coming.

@wintermeyer wintermeyer merged commit 97f166f into animina-dating:main Sep 17, 2024
1 check passed
@wintermeyer
Copy link
Collaborator

@briankariuki I just triggered a deployment to production. You can see the time of the last commit of a production version in the footer (it is encoded in the version number).

@briankariuki
Copy link
Collaborator Author

@briankariuki I just triggered a deployment to production. You can see the time of the last commit of a production version in the footer (it is encoded in the version number).

Will check in a few days

@wintermeyer
Copy link
Collaborator

Will check in a few days

Please do check today too.

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