Re: [opensource-dev] Server Side Avatar Appearance pile-on test
On Wed, 20 Feb 2013 15:54:42 -0500, Nyx Linden wrote: > Please use our latest viewer as it has additional statistics gathering > code that will allow us to calculate load patterns and measure the > improvements expected for later releases. > > Let me know if there are any questions! Greetings, Today, I'm having troubles on Aditi SunshineTest resgions: the server-side baking seems broken. Whether I use LL's latest Sunshine viewer(*) v3.4.5.270409 or the Cool VL Viewer v1.26.7, which both used to work just fine before, I get "bad requests (400)" errors, like so: WARNING: RequestAgentUpdateAppearanceResponder::errorWithContent: appearance update request failed, status: 400 reason: Bad Request DEBUG: RequestAgentUpdateAppearanceResponder::errorWithContent: content: INFO: RequestAgentUpdateAppearanceResponder::onFailure: retrying (SecondLife v3.4.5.270409 for Windows) or: WARNING: RequestAgentUpdateAppearanceResponder::error: Appearance update request failed, status: 400 reason: Bad Request INFO: RequestAgentUpdateAppearanceResponder::error: Retrying... (Cool VL Viewer v1.26.7.11, either Linux or Windows builds) Was something changed that is not yet propagated to the sunshine-external sources repository (the last commit in it dates back from 8 days ago) ?... If the answer is "yes", then please commit the necessary changes today... Regards, Henri. (*) The Linux build is still impossible to run for me because it requires GLIBCXX_3.4.15: "bin/do-not-directly-run-secondlife-bin: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by bin/do-not-directly-run-secondlife-bin)" when my system got libstdc++.so.5.0.7 (g++ v3.3.6) and libstdc++.so.6.0.13 (g++ v4.4.3). Why don't you build the Sunshine viewer on the same build system as for the other viewer branches (which all run fine on my system) ?... ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] Server Side Avatar Appearance pile-on test
We saw similar errors for some users at the pile-on yesterday, it appears to be account-specific (some people can reproduce others cannot). There are a few commits that have not been pushed to sunshine-external yet, but nothing that should affect the behavior so fundamentally. We're going to be looking into this issue today, I'll send another email if we think we have a fix. Thanks for the report! -Nyx On Fri, Feb 22, 2013 at 4:29 AM, Henri Beauchamp wrote: > On Wed, 20 Feb 2013 15:54:42 -0500, Nyx Linden wrote: > > > Please use our latest viewer as it has additional statistics gathering > > code that will allow us to calculate load patterns and measure the > > improvements expected for later releases. > > > > Let me know if there are any questions! > > Greetings, > > Today, I'm having troubles on Aditi SunshineTest resgions: the > server-side baking seems broken. Whether I use LL's latest Sunshine > viewer(*) v3.4.5.270409 or the Cool VL Viewer v1.26.7, which both > used to work just fine before, I get "bad requests (400)" errors, > like so: > > WARNING: RequestAgentUpdateAppearanceResponder::errorWithContent: > appearance update request failed, status: 400 reason: Bad > Request > DEBUG: RequestAgentUpdateAppearanceResponder::errorWithContent: >content: > > > INFO: RequestAgentUpdateAppearanceResponder::onFailure: retrying > (SecondLife v3.4.5.270409 for Windows) > > or: > WARNING: RequestAgentUpdateAppearanceResponder::error: Appearance > update request failed, status: 400 reason: Bad Request > INFO: RequestAgentUpdateAppearanceResponder::error: Retrying... > (Cool VL Viewer v1.26.7.11, either Linux or Windows builds) > > Was something changed that is not yet propagated to the > sunshine-external sources repository (the last commit in it dates > back from 8 days ago) ?... If the answer is "yes", then please commit > the necessary changes today... > > Regards, > > Henri. > > (*) The Linux build is still impossible to run for me because it > requires GLIBCXX_3.4.15: "bin/do-not-directly-run-secondlife-bin: > /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found > (required by bin/do-not-directly-run-secondlife-bin)" > when my system got libstdc++.so.5.0.7 (g++ v3.3.6) and > libstdc++.so.6.0.13 (g++ v4.4.3). Why don't you build the Sunshine > viewer on the same build system as for the other viewer branches > (which all run fine on my system) ?... > ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] Server Side Avatar Appearance pile-on test
On Fri, 22 Feb 2013 11:00:19 -0500, Nyx Linden wrote: > We saw similar errors for some users at the pile-on yesterday, it > appears to be account-specific (some people can reproduce others cannot). FYI and for what it is worth, while I managed to make SSB work with one of my alts, after half a dozen of outfit changes with that avatar, I again got "bad requests (400)" errors... > There are a few commits that have not been pushed to sunshine-external > yet,but nothing that should affect the behavior so fundamentally. We're > going to be looking into this issue today, I'll send another email if > we think we have a fix. Thanks. Regards, Henri. ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
[opensource-dev] ok who the *beep* is sarvajeet and why is he spamming the jira?
in the last two hours I've gotten about two dozen jira notifications where one user by the name of "sarvajeet" commented on the jira i question by adding this comment: JEET Add comment to all issues can we please find that person, hunt him down, pour honey on him, and tie him naked to an anthill? ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges