Search Issue Tracker
Fixed
Votes
0
Found in
Issue ID
867010
Regression
No
Caching MoveCache and GetCachedVersions with invalid arguments don't throw any exceptions or log any messages
To reproduce:
1. Pull and update assetbundle/caching-api/tests
2. Build locally or get a build from katana of that branch (build of assetbundle/caching-api should also work fine)
3. Open playmode tests project (unity\Tests\PlaymodeTests\Caching)
4. Run playmode tests, look at failing tests of MoveCache and GetCachedVersions
Caching MoveCache and GetCachedVersions with invalid arguments don't throw any exceptions or log any messages, so there is no way for user to know whether it succeeded or not.
Example 1:
-- Caching.GetCachedVersions("SomeInvalidNonExistingBundleName", new List<Hash128>())
Succeeds without any log or exception, where clearly this should not work.
Example 2:
-- Caching.MoveCacheBefore(Caching.defaultCache, new Cache());
This tries to move default cache before som invalid non-existing cache, and it succeeds. Maybe there is hidden if condition for that, but we should throw exceptions in that case.
Reproduced on version:
5.6.0b3 (0e1c848baeef)
Wed, 21 Dec 2016 07:00:20 GMT
Branch: assetbundle/caching-api
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment