This repository has been archived by the owner on Dec 20, 2024. It is now read-only.
Fix for week where Copium Capital used the same account for both staging and prod #106
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
fhenneke
pushed a commit
that referenced
this pull request
Aug 14, 2024
Pr #106 was a temporary workaround that is not needed anymore (hoping here we won't need to resync data from these weeks).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The script currently produces an error if the same address was used both for staging and prod submissions. This was indeed the case for Copium Capital that tested colocation in staging before we enabled them with the same account in prod (and disabled them in staging at the same time).
The proposed solution is really to bypass the check just for this one occasion, by pretending that the staging submissions of Copium Capital didn't happen from address
0x008300082C3000009e63680088f8c7f4D3ff2E87, but instead from the old staging address that the core team controls.