You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do have a case where in dev mode the app loads heaps of single resources (css/js/etc). Most of those are rather small and in prod they are combined, compressed, etc.
Since the profiler uses uniqid() to create the profile token I see randomly (but consistently) warnings about files/dirs that already exist (using FileProfileStorage). I would expect other storage classes to suffer similarly.
This seems to be a racing condition where two requests do have the same request time in milliseconds.
Are there any reason to not use the more_entropy flag and/or the prefix on the uniqid() call?
Alternatively, are there other ways to avoid this by different means?
The text was updated successfully, but these errors were encountered:
* 2.1:
[FrameworkBundle] Fix code status in dockblock
Fixed test to use Reflection
[Finder] fixed a potential issue on Solaris where INF value is wrong (refs #7269)
Update RouteCompiler.php
[FrameworkBundle] avoids cache:clear to break if new/old folders already exist
[HttpKernel] Fixed possible profiler token collision (closes#7272, closes#7171)
[ClassLoader] tweaked test
[ClassLoader] made DebugClassLoader idempotent
[DomCrawler] Fix relative path handling in links
Conflicts:
src/Symfony/Component/DomCrawler/Link.php
src/Symfony/Component/Finder/Iterator/DepthRangeFilterIterator.php
src/Symfony/Component/Routing/RouteCompiler.php
I do have a case where in dev mode the app loads heaps of single resources (css/js/etc). Most of those are rather small and in prod they are combined, compressed, etc.
Since the profiler uses uniqid() to create the profile token I see randomly (but consistently) warnings about files/dirs that already exist (using FileProfileStorage). I would expect other storage classes to suffer similarly.
This seems to be a racing condition where two requests do have the same request time in milliseconds.
Are there any reason to not use the more_entropy flag and/or the prefix on the uniqid() call?
Alternatively, are there other ways to avoid this by different means?
The text was updated successfully, but these errors were encountered: