-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(feeshare): Developer Incentives #144
Conversation
This reverts commit d5bb6e1.
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.
Great job m8 and gz on the lead dev role @ Juno :)
Do NOT merge this branch @ZaradarBH, @nghuyenthevinh2000, @Reecepbcups: Something is going on. I tried different environments to run this branch - failed. There is some runtime issue going on with this feature. The nodes wont start on genesis transactions. |
thanks you so much for testing this out, what is the log? |
@Reecepbcups @ZaradarBH @nghuyenthevinh2000 @inon-man: In
This must be replaced by the following snippet:
This moves the It might very well be that the liveness test fails nevertheless. But then its not because the node fails to start up but rather because expanding the local testnet from 4 to 6 nodes introduced a bug with this test. I guess, we should work on it in another branch. Btw: Do we need migration handler for this? On the mainnet the parameter space for this is not yet initialized, or is it? Another question: Why is only one workflow (snyk test) running on this branch? |
@nghuyenthevinh2000: The nodes simply did not start up on genesis: Resolved with: |
@fragwuerdig , nice find m8! I think the workflow issue might be because the PR branch belongs to an external org, it might be messing with the GH action configuration. Havnt looked into it. FYI I created an issue for the liveliness bug so we can all look into that together next week. #171 |
@Reecepbcups I have another commit for this branch (merging main into this branch to resolve conflicts). I don't know exactly why I could push ed35c8c. But it's clear that I cannot push anymore... Do you changed any permissions on your forked repo? Can you allow me to push commits? |
@fragwuerdig Thanks for this! I missed running a local instance I got so caught up in my Juno upgrade. Can confirm the reordering works I did not change any permissions no. I have allow edits by maintainers on and have not touched anything since this PR was opened. So unless this org changed permissions, not sure why this is the case |
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.
Code looks good and best to merge this after sdk 45 upgrade
@Reecepbcups any chance you can find time to bring this branch up-2-date with main so we can merge the PR after the 2.0 release? :) |
Co-authored-by: nghuyenthevinh2000 <nghuyenthevinh@gmail.com> Co-authored-by: Till Ziegler <tz@schoeneweide.tk> Co-authored-by: vincent <vincent.ch.cn@gmail.com> Co-authored-by: chengwenxi <22697326+chengwenxi@users.noreply.github.com> Co-authored-by: alchemist-ti <134163224+alchemist-ti@users.noreply.github.com>
This PR is in replace of #75 & builds on main properly