-
Notifications
You must be signed in to change notification settings - Fork 77
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
Cannot create a string longer than 0x1fffffe8 characters #208
Comments
|
Depending on the actual code we might be able to circumvent the issue by using Nonetheless, could you provide more context @dugajean ? We had reports related to Wordpress before, but overall it seemed to be working properly. Is there anything different in your application, that could be related? |
@AlexZeitler This is happening on my machine. I have 8 GB of RAM. This never happened on my other machine though, so it could be resources related. But then again, I think it should work on every machie. @Steveb-p Like I mentioned above, this is coming from The exact line of code throwing is in I believe that simply buffering would solve this issue rather than trying to read a gigantic string at once. Like you said. That's the most common suggestion for this error around the internet. |
Any news here? This is still happening sometimes, unfortunately. |
@AlexZeitler Here's the docker-compose file
|
This is just a matter of the string becoming too large to process. |
As far as I know, we are not performing any pre-processing for the service declaration file (configuration). We pass the file name as-is as a parameter to the So more likely culprit would be the output of a container. I'll need to check what we can do to store it in a different manner. |
@Steveb-p How's this looking? |
This is happening on this method call:
The full error looks like this:
Can't help with the actual source because this is coming from a 3rd party library that I'm using. Right here:
https://github.com/WordPress/gutenberg/blob/trunk/packages/env/lib/commands/start.js#L115
Help would be appreciated.
The text was updated successfully, but these errors were encountered: