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.
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
Protorev: Update timing for pool updating and dev fee payout #4827
Protorev: Update timing for pool updating and dev fee payout #4827
Changes from 33 commits
df18e54
5bacd9e
1f2f3dc
955b2aa
9189461
efbd26e
744d22e
49c7eaf
104720a
c8f8ff3
865161c
3b490ee
e7b0047
2653b70
f457bed
2474ad6
17a85bf
5ebb8b6
212ec42
666e53b
de3c073
ad69aa4
179fbcb
97a6ea8
127dc5b
da4efca
314d1c4
43b0abb
e68be34
f0a88c9
b069fa1
6723370
af008b7
61b7c83
3be7cbc
7f8f1e9
0d63186
4957aff
783e448
fced67d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I would prefer it if this is handled properly. I know the process for updating e2e is cumbersome. However, handling this in the right way and e2e testing will save us time during the upgrade if any issues occur.
The process for setting this account in e2e is the following:
osmosis/tests/e2e/initialization/config.go
Lines 234 to 237 in 1e56cc6
v15.x
osmosis/tests/e2e/containers/config.go
Line 27 in 1e56cc6
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.
@p0mvn @stackman27 The PR for steps 1-2 is ready for review: #5312
If I understand correctly, once the above PR is merged, I will then be able to get the docker tag and then update the tag in this PR, to continue forward.
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.
hi @NotJeremyLiu is this PR r4r now. I think just needs rebasing right?
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.
@stackman27 I just updated the tag and removed the failing test, letting it run through workflow to see if all is good
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.
Let's remove now?
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.
This is unused now. Please submit separate PR if agreed. Not going to block merge on this