-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Windows] Drush9 updb fails: unable to decode output into JSON #4281
Comments
I can confirm that from the output it looks like the updates have in fact executed successfully, but the problem is located somewhere in the processing of the results. It is likely that this problem is located somewhere outside of the Unfortunately I have no Windows machine available so I cannot dig deeper into this problem. I will unassign so this is free for someone else to pick up. A backtrace could also be helpful to try to pinpoint where the problem occurs. |
Just ran into this, exactly as described in OP. Seeing that wall of orange was a little alarming but I'm happy to know it doesn't affect the database update. |
Hi I just got precisely the same error. When running drush updatedb but also (without the lead in) when running drush cr. |
Just ran into this again with non-escaped quotes in the update message:
I think this may interrupt the updating process after the updates are run but before rebuilding caches since I had to manually run Drupal version : 8.8.8 |
Hmm. It may be that the Drush batch runner or output format systems are not handling those messages with quotes in them |
Also hit this when running updatedb on drush 9.7.2. Environment is Alpine Linux v3.10, someone else hit this on Ubuntu above so it doesn't seem like a Windows only issue. In my case there was no unescaped quotes in the messages, and the updates all returned EDIT: This looks like it could be logging destination related, changing monolog.channel_handlers to syslog seems to fix this. |
I dont see any reports of this with drush 8 or with drush 10. Since Drush 9 is unsupported, I'm going to close this. Please reply if you experience this with either drush8 or drush10. I will reopen the issue. |
I'm running into this issue on drush 10.3.6. In an update hook I am enabling a module. This is generating a message in the logs, which is getting output when running
As per previous comment from @fenstrat, changing the location of the logs fixes the issue. (But this isn't really desirable as we want our logs to output to stdout, so I'm trying to think of another solution). |
If you can change your log message so that it doesn't output |
Hello there. I'm getting the same issue when attempting to run the
Output of
|
This still happens with windows, drush 10.6.1, drupal 9.3.0, running the updb command. |
Yes Same Issue with windows, drush 10.6.1, drupal 9.3.3 |
OK, reopened. Possibly a bug in JSON formatter on Windows. |
Actually, the problem is better tracked at consolidation/site-process#56 |
Describe the bug
I am upgrading my Drupal 8.7 site to Drupal 8.8.
On Windows using mintty/cygwin env (as part of git for windows).
Performing
drush updb -y
all updates were performed. By finishing the update process, drush aborted abnormally.To Reproduce
drush updb -y
(On Windows 10)Expected behavior
drush updb
should finish the database updates an exit normally without an error.Actual behavior
It seems like the database updates were performed normally. Only the output can't decode correctly into JSON due to a syntax error.
There are unescaped quotes at the update messages.
FULL OUTPUT
Workaround
Is there another way to do the desired action?
System Configuration
Additional Information
On Linux the error don't came up. Our jenkins build env and staging env's are Linux mashines and there finishing the database updates normally.
The text was updated successfully, but these errors were encountered: