fix: small changes to aid crisp e2e test to run locally#926
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
WalkthroughTwo development scripts in the CRISP examples are updated. The dev.sh script now invokes concurrently through pnpm. The dev_cipher.sh script modifies address parsing to output raw values and expands cipher node setup for multiple nodes (CN2 and CN3 alongside CN1). Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
🔇 Additional comments (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
A couple of small changes I needed to make to run the CRISP e2e test locally.
So I was trying to get CRISP e2e test running locally.
I had an older python version of
yqinstalled which caused me grief because the -r flag was not present for some reason. I have updated but adding the-rflag solved the issue and is compatible with the new version as otherwise I was getting double quotes getting sent through to the hardhat scripts which broke stuff.'"0x123456"'So it seems to make sense to me to keep the
-rflag as it is simply the default in the latest go version of yq so we can be compatible with both.Secondly concurrently was not available when running the scripts outside of pnpm so it helps to run it through pnpm so I added that too.
Summary by CodeRabbit
Chores
Bug Fixes
New Features