-
Notifications
You must be signed in to change notification settings - Fork 8
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
Running dive bridge btp --chainA icon --chainB eth fails #53
Comments
This seems to have occurred because I had run DIVE, then updated Kurtosis, then ran a clean and ran DIVE again. This was resolved by manually deleting all volumes that persisted after the clean. |
@CyrusVorwald , Also @shreyasbhat0 , it seems like there might be a bug or two in the
|
I downgraded kurtosis from v0.80.13 to v0.80.12 to demonstrate the issue. ❯ brew install kurtosis-tech/tap/kurtosis-cli@0.80.12
An error occurred removing enclave container with ID '41fe7f3dfd05f10d343c3aabc4f00453193364ff2a7b7d0b21ca88aa74ec7901' An error occurred removing enclave container with ID 'e86c00c9cdce68abc539801565ef704de59e4f8ae7a7ba1d5e8a3ccd12f7be80' goroutine 1 [running]: |
I have attached the logs, although I'm not sure it shows |
Thank you @CyrusVorwald ! Can you try @shreyasbhat0 , it looks like there's a panic happening in the Dive CLI; maybe something to do with processing the error response from Kurtosis?
|
Tracking on our side as kurtosis-tech/kurtosis#959 |
❯ kurtosis clean -a ❯ dive bridge btp --chainA icon --chainB eth |
Looks like the second clean is working, per what we've seen in the past with zombie processes. @shreyasbhat0 , going to have to turn this one over to you as I was able to spot this in the Kurtosis API container logs - looks like it's something related to contract deployment:
|
Thanks for taking a look @mieubrisse |
Noted , will reproduce these bugs from my end and fix it soon . Also dive cli isn't creating its own volumes . Also @mieubrisse is it good practice to destroy enclave if any starlark run fails ? so that when any error happens we just destroy enclave and rerun whole package again . |
Sure , I take a look on this too |
Hey @CyrusVorwald ! I'll ping this thread again when my "fix" is merged and released |
Hey @CyrusVorwald ! |
Haven't been able to replicate either recently, but if it pops up again I'll post. Thanks @gbouv ! |
feat: logging by enclave name
Running dive bridge btp --chainA icon --chainB eth fails. On second run, it immediately states the setup completed. However, dive.json is empty.
❯ dive bridge btp --chainA icon --chainB eth
FATA[2023-07-21 00:46:10] Starlark Run Failed
❯ dive bridge btp --chainA icon --chainB eth
BTP Bridge Setup Completed between icon and eth. Please find service details in current working directory(dive.json)
❯ cat dive.json
The text was updated successfully, but these errors were encountered: