-
Notifications
You must be signed in to change notification settings - Fork 432
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
Private proxy fix #1941
Private proxy fix #1941
Conversation
@stevenyoungs I think we should not allow proxies to return None from the |
Returning |
I've paired down this PR to just fixing bugs in proxies. |
The LivingProxyDb is going to require a rewrite. And I think there is an error when one proxy is on top of another. I'll go ahead and turn off draft, and do a major rewrite when @stevenyoungs is done. |
@Nick-Hall, this could go into 6.0 as it is just a regular bug fix. |
Originally reported here: https://gramps-project.org/bugs/view.php?id=12886 |
When we revise the proxies to make sure they work correctly (sanitize all, proper proxy layering, no need to check for None, etc) we also need to look at caching the results. When I exported 2 people, one person was sanitized 6 times, and the other 3 times. Sanitizing is an expensive process and there is no need to do it more than once. [I would put this note in a github issue if we turned those on. I see issues as being for developers, not a replacement for mantis]. |
The change looks good to me. Here are some observations from looking at the code around his change.
|
I just made this function to work and look exactly like the others. I am re-writing private and living proxies completely so I wouldn't worry about the details of this sanitize function. |
Yes. Keep bug fixes simple. |
109348c
to
e041e53
Compare
This PR fixes a missing sanitize method in the
PrivateProxyDb