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

Names of some users are removed #341

Open
aminlatifi opened this issue Jan 3, 2021 · 7 comments
Open

Names of some users are removed #341

aminlatifi opened this issue Jan 3, 2021 · 7 comments

Comments

@aminlatifi
Copy link
Member

image

@aminlatifi aminlatifi changed the title Names of users are removed!! Simulation Script? Names of users are removed!! Jan 3, 2021
@aminlatifi aminlatifi changed the title Names of users are removed!! Names of some users are removed Jan 3, 2021
@aminlatifi
Copy link
Member Author

It happened to my account to and I filled it again.
@mohammadranjbarz I looked in simulation script and didn't see any part related to User entity creating or patching. Am I right?

@mohammadranjbarz
Copy link
Collaborator

@aminlatifi Yes you are right I think it's not related to simualtion script, as in develop I ran multiple time these days but the name didn't change

@aminlatifi aminlatifi added this to the Sprint #1 Jan 4-14 milestone Jan 4, 2021
@mohammadranjbarz
Copy link
Collaborator

@aminlatifi
I've an idea for knowing if simulation does this or not,
You can edit your name in beta and run simulation script and then again check your name has been changed or not ( I say checking with your account because I don't have this problem"

@mohammadranjbarz
Copy link
Collaborator

@aminlatifi

I investigated on feathers-giveth and simulation, and we don't update the user's name unless in PATCH /users that it's right,
so we can tell that the updated name didn't happen through the feathers

@GriffGreen
Copy link
Member

Maybe add some logs to the database to understand how this rewrite happened....

@GriffGreen
Copy link
Member

hopefully the upgrade will fix it

@aminlatifi
Copy link
Member Author

Our plan on mongodb service provider (MongoDB Atlas) doesn't include profiling, and logging db commands is part of the profiling service.
We are thinking about hosing DB ourselves for improving performance, if that happen we don't need upgrading our plan on MongoDB Atlas

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

No branches or pull requests

3 participants