-
Notifications
You must be signed in to change notification settings - Fork 105
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
@cardano-graphql/cli - TypeError: Cannot read property 'trim' of undefined #552
Comments
I'm not able to reproduce this with npx npx @cardano-graphql/[email protected] docker snapshot make
Have you installed the package globally before? If so, try npm uninstall -g @cardano-graphql/[email protected]
npm i -g @cardano-graphql/[email protected] |
It seems to work fine running with npx instead of installing it: I've stuck with @4.0.0 as that's the cardano-graphql version I'm using currently. Not sure if it's good to mix the versions. |
Same issue here (also same stack trace), I'm getting this when trying to rebuild the DB as part of the upgrade from 4.0.0 to 5.0.0 - but for me it fails also with |
It seems it's because
The code then splits this to lines and then splits the lines by 3+ spaces and expects apparently more than one "thing" on the line, but there isn't. Since the variables are called |
...I see now this is actually in a dependency, the culprit is this commit: PDMLab/docker-compose@880d252 It breaks compatibility with Opened an issue upstream: PDMLab/docker-compose#178 |
Co-authored-by: Rhys Bartels-Waller <[email protected]>
👋 Just wanted to let you know that today we've released version Looking forward to your feedback! |
Environment
cardano-graphql: 4.0.0
Platform
Platform version:
Runtime
Runtime version:
Steps to reproduce the bug
sudo npm i -g @cardano-graphql/[email protected]
cd cardano-graphql
sudo cgql docker snapshot make
. Spits out the below:What is the expected behavior?
Not sure, trying it out for the first time, but was expecting it to write backups of the docker volumes or something.
The text was updated successfully, but these errors were encountered: