-
Notifications
You must be signed in to change notification settings - Fork 165
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
error with wordmove pull -d #603
Comments
Hi @byron222 , the only thing I can reply is that "it works on my machine". Why didn't you have used the bug reporting issue template? I'd have had much more informations to try to understand your problem. Would you mind to update your issue description? Aside of that: is the command |
Trying to involve @maiorano84 and @nlemoine . I've found some more scenarios related to this issue and probaly related to #597
@byron222 do you feel like your problem could be related to the existence of a |
Reproducing the second error reported by me in
|
Also with a real file adding the
|
Having '@staging':
ssh: xxxx
path: /var/www/xxx
disabled_commands:
- db drop
- db search-replace will get parsed. So the |
That's not just a ruby's parser problem: https://p195.p4.n0.cdn.getcloudapp.com/items/nOueWKe6/Image%202020-06-11%20at%206.41.55%20PM.png?v=5fa4a2d55ea2d1ea7af6b628f49a2c9b |
Hi @pioneerskies Sorry, I forgot to mention it but indeed, the I don't know well enough the yaml standard. However, Symfony also adds a note about special characters: https://symfony.com/doc/current/components/yaml/yaml_format.html#strings |
Other traces from wp-cli repo: wp-cli/wp-cli#4982 Thanks @nlemoine for the feedback :) |
@nlemoine FYI quoting the key is completely valid YAML and it seems to me it's working for both wp-cli and for ruby parser |
@byron222 You need to provide more information in order for us to reasonably be able to help you, otherwise we're just guessing as to what your actual problem is. @pioneerskies had a very comprehensive bug report template that you opted to ignore, but despite that he's already narrowed it down to some possibilities given the limited information we have. Please include the contents of your wp-cli.yml file if you have one, as well as anything else you might have tried or think might be relevant. |
Said that I'm going to close, I'd like to report that from version 6 (currenlty in alpha) Ciao ciao :) |
i got the next error when I pull my database
from /root/.rbenv/versions/2.6.0/lib/ruby/2.6.0/json/common.rb:156:in
parse'/root/.rbenv/versions/2.6.0/lib/ruby/2.6.0/json/common.rb:156:in
parse': 767: unexpected token at '' (JSON::ParserError)
The text was updated successfully, but these errors were encountered: