-
Notifications
You must be signed in to change notification settings - Fork 566
Conversation
- add ip-addresses for localnet-setup generation - add localnet-setup folder to keep localnet-setup-artifacts - map localnet-setup-artifacts to containers - change start-docker.sh to pick up generated testnet artifacts
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.
lgtm
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! Looks like this only works if the repository is on the $GOPATH
, can you fix that? Otherwise, LGTM
Thank you for the feedback. |
@fedekunze would be happy to get additional info about your finding. |
…et-show-logstream, fix localnet-unsafe-reset and localnet-clean, add comments
having some issues running
|
@fedekunze thank you! Added 6d52409. Can you retry? |
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.
tested ACK 💯
@khoslaventures feel free to leave an additional review, or I can merge it by EOD, and then we can address your comments later on a follow-up PR 👍 |
@khoslaventures apart from the Windows portions I tried to address your points. IMO we should remove the Windows parts. There are additional-points (a few already visible as issues #339, #370) which are necessary to fix if Windows should be fully supported. @leejw51crypto what do you think about that since you have created the issues? Is it an option to use WSL2? |
@simonpfeifhofer can you pull the latest changes? I enabled auto-merge |
@fedekunze done. |
@fedekunze please let me know if there is still something which is missing in your opinion. |
@simonpfeifhofer I enabled auto-merge but it seems that you need to update your configuration as an external contributor to accept upstream rebasing (when the branch needs to be updated) |
@fedekunze: Because of the policy on the repository that out-of-date-branches cannot be merged it's necessary to update the branch every time a PR gets merged into main. I've done this three times. Unfortunately in the meantime other PRs have been merged. At the current point in time the branch is up to date, but the workflows need approval by a maintainer and if they complete successfully the PR will be auto-merged successfully. Do you refer to the setting |
@simonpfeifhofer I will add some changes to the contributor guidelines to prevent this from happening again. I was referring to this doc to allow changes from maintainers: |
* Problem: no unit test for native action Solution: - add unit test * test nested cases
Closes: #310
Description
For contributor use:
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerFor admin use:
WIP
,R4R
,docs
, etc)