This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
[BUG-8917] Inventory problems on Agni RC Regions running 15.03.20.300032 and Aditi regions running DRTSIM-279 15.03.30.300351 when Http Inventory is disabled. #16485
Labels
Since the RC regions on Agni with the "code clean up around inventory" rolled to 15.03.20.300032 last week, there were 2 inventory problems found.
Problem 1 is fixed on the DRTSIM-279 15.03.30.300351 server version on Aditi
The region Exland is currently running on DRTSIM-279 15.03.30.300351
secondlife://Aditi/secondlife/Exland/128/128/16
As far as I am aware, DRTSIM-279 15.03.30.300351 is the proposed fix for BUG-8877 which is likely to be rolled out to Agni RC regions this week.
Problem 2 is not fixed on DRTSIM-279 15.03.30.300351
This issue is to track Problem 2.
Steps to Reproduce
Note that the same problems are seen on any Agni RC region but I am testing on Exland because the server here contains the proposed fix for BUG-8877.
Clean viewer cache and login to the region Exland on Aditi, secondlife://Aditi/secondlife/Exland/128/128/16, on the current LL release Second Life 3.7.26 (299635) Mar 6 2015 11:35:55 (Second Life Release)
You should have Http Inventory enabled for this session.
Wait for inventory to fetch about 3/4 of the total and then disable Http Inventory (Develop -> Http Inventory) and relog into Exland.
Note how much inventory was fetched before you log out.
Observed Behaviour
After relogging with Http Inventory disabled, observe the following:
Inventory will be in and will remain in a constantly "Fetching..." state showing the inventory count you had when you logged out of Exland the previous session.
See Fig 1 attached.
Even if you had a fully fetched inventory from the previous session, the inventory will still show as "Fetching..." at your full inventory count.
Attempt to rename any modifiable asset within your inventory by right clicking it and choosing Rename.
Observe that Rename is greyed out.
Even if you had a fully fetched inventory from the previous session, rename will still be greyed out.
Attempt to rez any object from inventory on the ground.
Observe you cannot rez anything on the ground - you get the "no-entry" sign.
I suspect this is a side effect of the inventory being stuck in a constantly fetching state.
Observe that your avatar will be a cloud and will never rez even after replacing outfits with an outfit that has fetched all its contents.
Observe that you have no favorite landmarks in the favorites bar of the viewer at all and that the Landmarks folder is missing from Inventory (because it is empty).
Even if you had your landmarks fetched by the time you logged out of the previous session, the Landmarks folder will always be totally empty (and therefore hidden) after relogging with Http Inventory disabled.
Teleport to a region running a normal server version which does not contain the "code clean up around inventory" changes, for example Morris: secondlife://Aditi/secondlife/Morris/209/210/34, which is currently running on Second Life Server 15.03.11.299741
Observe that inventory immediately starts to fetch and finishes fetching normally.
Observe that the landmarks folder is immediately visible in inventory and favorite landmarks populate in the favorites bar.
Observe that you are immediately able to rename modifiable assets within inventory.
Observe that your avatar rezzes a few seconds after landing in the new region.
Teleport back to Exland and clear cache and relog back into Exland.
Http Inventory should be left disabled.
Observe that Inventory will now show either "Fetching 0 items..." or "Fetching Items..." with no zero count given.
It seems random whether it displays the 0 in the item count or not.
Inventory will never fetch until you teleport into a region unaffected by this bug.
Expected Behaviour
If disabling Http Inventory is still going to be supported then when Http Inventory is disabled, inventory should fully fetch, avatar should rez normally, you should be able to rez objects out of inventory and you should be able to rename modifiable assets within inventory.
If disabling Http Inventory is decided to be no longer supported then the option to disable it should be removed from the viewer and those who have it disabled should have their UseHTTPInventory setting forced to TRUE.
Im sure there are more use cases for needing to keep Http Inventory disabled but these are the ones I know of. All of them are pretty rare as far as I know though.
These cases all tend to be account specific and are usually caused by a problem in the affected accounts inventory for example a crazy number of duplicated calling cards.
The ability to disable Http Inventory is useful for these cases to allow the user to stay logged in long enough to fix their inventory problem once the cause is found and once fixed they can enable Http Inventory again.
Not all cases of inventory "corruption" problems can be fixed in this way by the user though - some need to go to LL support to get an inventory fix.
Attachments
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: