[BUG-9353] Unable to save outfit #16863
Comments
Whirly Fizzle commented at 2015-05-28T06:28:13Z, updated at 2015-05-28T09:01:47Z Kaitlyn has this same problem on Firestorm viewer since we released with the AIS3/SSA polishing fixes. What happens is, when Kaitlyn saves her new outfit, the outfit will seemingly save and show as a new outfit in Appearance panel but the outfit folder does not contain any items, it says: "There are no items in this outfit". This is not an isolated case - we have had a lot of reports of this problem on our 4.7.1 release but Kaitlyn was the first person willing to test on the LL viewer and report it here. There appear to be 2 flavours to this bug - see Observed 1 and Observed 2 on http://jira.phoenixviewer.com/browse/FIRE-16100 Kaitlyn has the Observed 2 behaviour - her saved outfit within the My Outfits folder of inventory remains empty. Other TPVs which have released with the AIS3/SSA polishing fixes are also getting reports of the same problem, for example Alchemy: https://alchemy.atlassian.net/browse/ALCH-209 Kaitlyn is going to update this issue with images showing the Appearance panel displaying the "There are no items in this outfit" text and the empty Outfits folder in inventory and her log files after reproducing this on the LL viewer. |
Kaitlyn Imtiaz commented at 2015-05-28T08:50:01Z It was suggested that I change FSUseAis3Api in the debug settings to false. I'll need to test it for awhile before I'm convinced it's fixed, but as of now, it has let me save an outfit. |
Whirly Fizzle commented at 2015-05-28T09:00:33Z Yes, setting FSUseAis3Api to FALSE in the Firestorm debug settings has so far fixed everyone with this problem - the fix is instant, no relog even is needed. The LL viewer used to have a debug setting for disabling the AIS3 cap, but it was removed. |
Kaitlyn Imtiaz commented at 2015-05-28T09:59:09Z Logs |
Kaitlyn Imtiaz commented at 2015-05-28T10:01:36Z This time when I saved the outfit, it still showed in the outfits tab there were no items but in the outfits folder itself, items were there. |
Alexa Linden commented at 2015-05-28T16:32:03Z, updated at 2015-05-28T16:32:13Z Hi Kaitlyn, I had our Devs take a look at your log. Thank you for attaching it! From what we're seeing, there seems to be a bad item in the outfits you're trying to save that is causing this failure. Have you purchased something recently that you're now wearing? A good test would be to see what outfits save correctly and which don't... or take a failing outfit and slowly remove items from it and try saving until it saves successfully. If you're able to nail down what item is causing this, we'd be curious to know it it causes the failed outfit save everytime. Also, when you look at Worn items in your inventory, is there any odd messaging next to it (item not found). Please let us know and I'll continue to follow this Jira :) |
Whirly Fizzle commented at 2015-05-29T06:36:59Z Kaitlyn's log shows the same failure error that we've seen in Firestorm users logs, who could consistently reproduce this problem, the "broken_linked_ids" & "error_description':'Cannot link to non-existent items." in... 2015-05-28T09:53:46Z WARNING: AISCommand::httpFailure: [PUT:https://sim10047.agni.lindenlab.com:12043/cap/fe4e0293-2a91-6217-d9b3-78a98bd4e280/category/78c7379d-3926-be6f-8ddf-4afb8ed1bbe1/links?tid=29097cfa-e982-dd0f-f6bf-703ca1f69a44] [status:400] [reason:Bad Request] [content-type:'application/llsd+xml'] [content:{'broken_linked_ids':[u566cb59e-ef60-41d7-bfa6-e0f293fbea40],'error_code':i3,'error_description':'Cannot link to non-existent items.','error_filename':'categories.py','error_function':'CategoryAPI._get_links','error_line_number':i884,'type':i24}]
2015-05-28T09:53:46Z INFO: LLAdaptiveRetryPolicy::onFailureCommon: Non-server error 400, will not retry ..for example in this case: http://jira.phoenixviewer.com/browse/FIRE-15901 (logs are on that issue).I managed to reproduce this problem twice tonight where I saved a new outfit and the appearance panel showed "There are no items in this outfit" and the new outfit folder created in Inventory was empty and remained empty after relog. I was testing BUG-7623 to see if it was fixed - seems to be? I was having a really hard time getting my inventory stuck in a constantly fetching state & I used to be able to reproduce this easily. Here is an image showing the outfit after it failed to save: http://i.imgur.com/InR0CoL.png I attached my log from that session on Firestorm - see Whirly_Firestorm.log The failed outfit save starts at line 1354 newview/lltoastalertpanel.cpp(179) : 2015-05-29T04:22:42Z WARNING: LLToastAlertPanel::LLToastAlertPanel: Alert: Save what I'm wearing as a new Outfit:
llui/llfloater.cpp(768) : 2015-05-29T04:22:44Z INFO: LLFloater::closeFloater: Closing floater toast
llui/llmodaldialog.cpp(129) : 2015-05-29T04:22:44Z WARNING: LLModalDialog::stopModal: LLModalDialog::stopModal not in list!
llxml/llcontrol.h(300) : 2015-05-29T04:22:45Z WARNING: LLControlGroup::get: Control FSDisplaySavedOutfitsCap not found.
newview/lloutfitslist.cpp(636) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::refreshList: OUTFIT RENAME: Outfits folder changed - processing changed categories
newview/lloutfitslist.cpp(907) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::updateOutfitTab: OUTFIT RENAME: Trying to update outfit tab for categoryc582879f-fdbb-bed8-6bb8-11900348e6fa
newview/lloutfitslist.cpp(929) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::updateOutfitTab: OUTFIT RENAME: Updating tab name
newview/lloutfitslist.cpp(649) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::refreshList: OUTFIT RENAME: Outfits folder changed - processing changed categories FINISHED
newview/llappearancemgr.cpp(1633) : 2015-05-29T04:22:45Z INFO: LLAppearanceMgr::slamCategoryLinks: copying 36 items
newview/llaisapi.cpp(310) : 2015-05-29T04:22:45Z INFO: SlamFolderCommand::SlamFolderCommand: https://sim10134.agni.lindenlab.com:12043/cap/8263bed3-d56c-855f-9599-4bdff5e500b7/category/c582879f-fdbb-bed8-6bb8-11900348e6fa/links?tid=c4acc5a6-ede8-c62d-1bdd-00a422c52fae
newview/llinventorymodelbackgroundfetch.cpp(339) : 2015-05-29T04:22:45Z INFO:#Inventory LLInventoryModelBackgroundFetch::setAllFoldersFetched: Inventory background fetch completed
llxml/llcontrol.h(300) : 2015-05-29T04:22:45Z WARNING: LLControlGroup::get: Control FSDisplaySavedOutfitsCap not found.
newview/lloutfitslist.cpp(636) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::refreshList: OUTFIT RENAME: Outfits folder changed - processing changed categories
newview/lloutfitslist.cpp(907) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::updateOutfitTab: OUTFIT RENAME: Trying to update outfit tab for categoryc582879f-fdbb-bed8-6bb8-11900348e6fa
newview/lloutfitslist.cpp(929) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::updateOutfitTab: OUTFIT RENAME: Updating tab name
newview/lloutfitslist.cpp(649) : 2015-05-29T04:22:45Z INFO: LLOutfitsList::refreshList: OUTFIT RENAME: Outfits folder changed - processing changed categories FINISHED
newview/llaisapi.cpp(105) : 2015-05-29T04:22:46Z WARNING:#Inventory AISCommand::httpFailure: [PUT:https://sim10134.agni.lindenlab.com:12043/cap/8263bed3-d56c-855f-9599-4bdff5e500b7/category/c582879f-fdbb-bed8-6bb8-11900348e6fa/links?tid=c4acc5a6-ede8-c62d-1bdd-00a422c52fae] [status:400] [reason:Bad Request] [content-type:'application/llsd+xml'] [content:{'error_code':i0,'error_description':'Duplicate links or invalid link type.','error_filename':'categories.py','error_function':'CategoryAPI._get_links','error_line_number':i829}]
newview/llhttpretrypolicy.cpp(119) : 2015-05-29T04:22:46Z INFO: LLAdaptiveRetryPolicy::onFailureCommon: Non-server error 400, will not retry My error is different from Kaitlyns. My inventory does sometimes just randomly get stuck in a "Fetching..." loop on the LL viewer so next time this happens, I'll try to save an Outfit and see if I can reproduce a failed save & add LL viewer logs here. |
Kaitlyn Imtiaz commented at 2015-05-29T07:12:39Z Do you want me to disable FSUseAis3Api and re-create this issue? Because as of right now, my problem fixed setting FSUseAis3Api to false. |
Whirly Fizzle commented at 2015-05-29T15:36:57Z Heya Kaitlyn, The FSUseAis3Api debug setting will only affect the Firestorm viewer. If you can, please can you do what Alexa asked above while using the LL viewer. |
Kaitlyn Imtiaz commented at 2015-05-29T20:42:31Z On LL Viewer.. I have removed everything, item by item, trying save outfit after each one I took off and I am down to my eyes, my shape and my skin and I still can not save. I do not see anything else under worn. |
Kaitlyn Imtiaz commented at 2015-05-29T21:33:37Z It seems my issue has been resolved. Whirly Fizzle had me do a character test and try to save my outfit that way on the LL viewer. It saved fine. I then added the shape, eyes, hairbase and skin that I had gotten down to previously trying to find the issue, and it saved. So I went ahead and added my entire outfit, and again it saved perfectly. I did a relog, still works. Even went to an old outfit and tried to re-save and that also worked. Seems I'm all fixed. I hope it stays that way! Thanks to Whirly and all your hard work. |
Kaitlyn Imtiaz commented at 2015-06-02T23:20:13Z Well it stayed resolved for a short while :D I'm broken again and having to go back to setting FSUseAis3Api to false. |
Whirly Fizzle commented at 2016-01-29T21:48:58Z, updated at 2016-01-29T21:55:09Z I just got hit by this bug on Second Life 4.0.1 (310054) Jan 14 2016 18:17:17 (Second Life Release) & I can't work out what's wrong with the items in my COF.
|
Whirly Fizzle commented at 2016-01-29T21:59:08Z I did not change anything I was wearing & relogged & attempted to save the same outfit again. |
Saeros Linden commented at 2017-07-07T00:45:07Z Our apologies, it appears this jira has been a victim of a spammer. We’re cleaning up the offending comments, sorry for the mess! |
Steps to Reproduce
Trying to save outfit
Actual Behavior
I tried saving outfit and nothing shows up. I've tried this on FS viewer and SL viewer. I've tried multiple times, and even changed outfits completely to try and save again and it still won't work.
Expected Behavior
I expected it to save my outfit!
Other information
Attachments
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: