beaker cli broken after building osmosis binary

osmosis-labs / beaker

Beaker helps streamlining CosmWasm development workflow.

Apache License 2.0

106 stars 30 forks source link

beaker cli broken after building osmosis binary #104

Closed AtticusDavid closed 1 year ago

AtticusDavid commented 2 years ago

Hello all.

I am trying to run testnet on my local machine. So I cloned osmosis-labs/osmosis repository and moved to this commit(https://github.com/osmosis-labs/osmosis/commit/101f3f7a5dd3959a09800fcae334e257a2f373ab). (In order to test estimateSwap feature)

After running local network, I tried to deploy my smart contract which developed with CosmWasm. But there was an issue with beaker cli like below.

reproduce environment:

beaker 0.0.8
go 1.18.1
ubuntu 21 w/ WSL

step to reproduce

install beaker and run beaker console -> it works fine.
git clone https://github.com/osmosis-labs/osmosis and checkout commit (https://github.com/osmosis-labs/osmosis/commit/101f3f7a5dd3959a09800fcae334e257a2f373ab).
do make install
run beaker console again and this shows an error.

iboss-ptk commented 2 years ago

This is weird, running beaker console shouldn't invoke any go code by itself. But it seems to run e2e test...

Is other commands like beaker wasm store-code works alright?

AtticusDavid commented 2 years ago

yup. it seems like other commands (beaker deploy, beaker wasm) work fine. this issue also reproduced in my other laptop(M1 Macbook Air)

iboss-ptk commented 2 years ago

I tried to reproduced, it has issue for different reason, v0.0.8 for beaker console is not published on npm and that's fixed. Could you try again, ideally beaker-console should never invoke any go binary on its own.

Apart from that, if you want to develop on local machine, make localnet-build && make localnet-start might be more suitable for smart contract dev (it runs docker)

triccs commented 1 year ago

I'm getting the same issue except 'beaker console' doesn't work the first time. Not exact same issue but didn't think it was worth opening a new one.

reproduce environment: beaker 0.0.8 go 1.18 ubuntu 18.04 w/ WSL

step to reproduce: install beaker run beaker console

iboss-ptk commented 1 year ago

@triccs do you have npm installed?

triccs commented 1 year ago

@triccs do you have npm installed?

Yes, any use of npm or npx (as shown in the picture) outputs a similiar error.

iboss-ptk commented 1 year ago

Deleted @Gitwilnie comment since it's a phishing (even in gh issue ...)

iboss-ptk commented 1 year ago

@triccs now this is very weird and should not relate to beaker, it might relate to osmosis itself or something wrong with your npm, please create new issue there.

If you later find any issue related to beaker, please open new issue.