Hi, I don't know if this issue would better fit into devs forum, but let's try here first.
I experienced some problems with AsseticBundle with use_controller = true: the requests to the asset resources include some SQLite errors in their output: <b>Warning</b>: SQLite3Stmt::execute() [<a href='sqlite3stmt.execute'>sqlite3stmt.execute</a>]: Unable to execute statement: database is locked in <b>/usr/lib/php5/symfony/src/Symfony/ Component/HttpKernel/Profiler/SqliteProfilerStorage.php</b> on line <b>161</b> This might be something to do with the concurrency: as the browser does multiple concurrent requests to the server, some of them fails due database is locked for another request. I checked out the cached asset files from app/cache/dev/assetic/* and they are built correctly, without any errors. I tried to switch off the profiler from Symfony2 config_dev.yml, but no luck either (that is pretty strange). I was also wondering if there should be possibility to switch off profiler per route: all assetic routes could be then committed without profiler. Best regards, Ville -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
