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

Merge connected reverse engineered keys timelines #122

Open
Divide-By-0 opened this issue Oct 19, 2024 · 2 comments · May be fixed by #126
Open

Merge connected reverse engineered keys timelines #122

Divide-By-0 opened this issue Oct 19, 2024 · 2 comments · May be fixed by #126
Labels
bug Something isn't working low

Comments

@Divide-By-0
Copy link
Member

This case should not exist, it should be merged.

image
@hhuntaa
Copy link

hhuntaa commented Oct 29, 2024

just to be sure do you want to merge them on the frontend or in the database?

hhuntaa added a commit to hhuntaa/archive.prove.email that referenced this issue Oct 29, 2024
fixes zkemail#122, i dont
know if this is exactly what you wanted so you might have to review it,
it merges records with the same values while keeping the earliest first
seen at date with the oldest last seen at date.
@hhuntaa hhuntaa linked a pull request Oct 29, 2024 that will close this issue
@Divide-By-0
Copy link
Member Author

Divide-By-0 commented Nov 27, 2024

Also, while these ones overlap, there are many keys which do not overlap, but if they have the same value, then we should in fact be merging those entries into one.

This should happen at the database level, because we want the API to return values that are as processed as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants