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
Can't alter timeout for filter processes #250
Comments
+1 |
+1... I'm using an Amazon EC2 small instance am experiencing the same thing during an assetic:dump in a Capistrano deployment. I am using less, cssrewrite and yui_css compressor filters. |
+1 |
Same thing (using Symfony 2.2-dev). Fixing this would be very helpful. @kriswallsmith, thanks for starting working on this in the last few days, I'm sure that many developers will be very glad to see something like
or
in their |
+1, same issues on compass filter |
👍 , same issue with compass and sprites generation |
This has been fixed in AsseticBundle. |
@kriswallsmith is it fixed for all filters including closure or just for compass? |
If the filter extends https://github.com/kriswallsmith/assetic/blob/master/src/Assetic/Filter/BaseProcessFilter.php#L31 you can set the timeout for the process. Closure is not .. |
Using Symfony 2.1 Beta, when I do
php app/console assetic:dump --env=prod --no-debug
I getThis is because the filters (Google Closure in my case) build a process using
Symfony\Component\Process\ProcessBuilder
and then call$pb->getProcess()
to get the actual process. Unless you call$pb->setTimeout()
before calling$pb->getProcess()
the process has the default timeout of 60 seconds. This isn't long enough to compile my JavaScript on the Amazon EC2 micro instance I'm using as a test server.Ideally this would be configurable somehow, but failing that I think it should be longer.
The text was updated successfully, but these errors were encountered: