-
Notifications
You must be signed in to change notification settings - Fork 23
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: tally result id collision #590
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 10, 2025 13:08
6650a4b
to
12cf4cc
Compare
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 10, 2025 13:13
12cf4cc
to
9fb0720
Compare
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 10, 2025 15:08
9fb0720
to
be93a3d
Compare
crisgarner
reviewed
Jan 10, 2025
Thanks! only have a question |
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 20, 2025 08:31
be93a3d
to
d69a1f2
Compare
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 20, 2025 13:39
d69a1f2
to
703573e
Compare
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 20, 2025 15:26
703573e
to
dcbcd07
Compare
kittybest
force-pushed
the
fix/tally-result-id
branch
from
January 21, 2025 17:26
dcbcd07
to
a9ffa0e
Compare
crisgarner
approved these changes
Jan 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
crisgarner
force-pushed
the
fix/tally-result-id
branch
from
January 21, 2025 17:59
a9ffa0e
to
7db119e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is to solve the tallyResult id collision on the subgraph, meanwhile make sure the interface works well after this change.
Because of the rebase issue, this is same PR as #584 & #583 , but branch from the latest
main
branch.Additional Notes
I found that the interface mapping result with tally result never uses the result id, that's why we didn't find this problem before. We need to have 100% confidence that the subgraph returns tally result 1 by 1 following the index of the projects.
(So actually, maybe it's better that we use the
result.id
instead of theindex
of the loop?)see here:
maci-platform/packages/interface/src/server/api/routers/results.ts
Lines 61 to 68 in c0e35af
Related issue(s)
Confirmation
Important
We do not accept minor grammatical fixes (e.g., correcting typos, rewording sentences) unless they significantly improve clarity in technical documentation. These contributions, while appreciated, are not a priority for merging. If there is a grammatical error feel free to message the team.