-
I've recently added
The def exec_runtime(filename)
io = IO.popen(binary.split(' ') << filename, **(@popen_options.merge({err: [:child, :out]})))
output = io.read
io.close
if $?.success?
output
else
raise exec_runtime_error(output) # this is the line that is raising, output is `nil` or `''`
end
end And the component and function referenced appear to work correctly. The page where this error has occurred appears to work. It is from a reasonably high traffic site and this error report appears to be very intermittent and rare. I can't reproduce this so I can't file a bug report. Does anyone have suggestions for what to do to debug this further? My main concern is if I scale up the usage of SSR I'm not sure how to diagnose issues when I'm getting no output. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@JaredShay you have an issue in your webpack configuration to build a server bundle. You might post to our community Slack If you'd like ShakaCode to help you out so that you can focus on new features as opposed to configuring Webpack, please book a time with me or email me: justin@shakacode.com. |
Beta Was this translation helpful? Give feedback.
-
@JaredShay try ensuring that you're using
Additionally, there's a possibility that this is being caused by a new webserver worker getting a SSR request before the server-bundle has been compiled. At least, I think that's an edge case we've encountered before. I'm having trouble tracking down any details on it, however. |
Beta Was this translation helpful? Give feedback.
@JaredShay try ensuring that you're using
NodeJS
for yourEXECJS_RUNTIME
.MiniRacer
isn't compatible with certain libraries & javascript features.Additionally, there's a possibility that this is being caused by a new webserver worker getting a SSR request before the server-bundle has been compiled.
At least, I think that's an edge case we've encountered before. I'm having trouble tracking down any details on it, however.