32 Responses to “[Resolved] Issue Tracker and WikiUnavailable” · 1 hmr1000 Says: April 20th, 2008 at 3:28 PM Sounds like a griefer finally got caught and banned to me. I he or you or whoever it was did all the things they are charged with all I can say is good riddance. I really do not think with all that is going on any lindens have time to steal his or your account and go around causing trouble, granted there is alway a possibilty someone else got his or your password and did it though, but if so the fault prob... lire la suite
Lien du post: http://blog.secondlife.com/2008/04/20/issue-tracker-and-wiki-unavailable/
32 Responses to “[Resolved] Issue Tracker and WikiUnavailable” On topic... when the issue tracker’s down, where do we report that to? As you said this ain’t the place for such stuff. Trust me LL won’t address this issue on a blog. It would be wise to worry about your own account and let whoever it is that lost theirs deal with it themselves. Awesome, I was wondering why I couldn’t. Hope get the wiki back again soon, I need it a lot. Issue tickets talk to a concierge they still wont listen. Just take our money and money we work hard for to have virtually a nill service. Surprisingly as it may be, back to the topic at hand - wiki and jira both report timeouts from the provider’s squid. Would be nice if someone would contact said provider...
Friendly greetings in 2008! We’ve been continuing to better our Issue Tracker’s (what is it?) usefulness & accessibility for you. Following vibrant discussion, Rob Linden made several improvements: · A new “meta” state - Meta Issues are useful for tracking groups of related issues. They’re not inherently resolvable, but provide a “big picture” view of things to be aware of. For instance, problems with certain hardware like newer MacBook Pros, or subjective aesthetic concerns about WindLight. You can create a Meta Issue by selecting Issue Type = “Meta Issue” as shown here: · Ability to change issue resolution without reopening - Reopening was a wasteful pain. Now, if an issue’s status needs to be corrected, there’s a “Change resolution” link on the left which can do just that. · Knowledge Base Article of the Week #6 - Jeremy Linden shares pointers to a lot more Issue Tracker info. And yes, I am planning on doing video tutorials on clarifying what continues to confuse and confound about the Issue Tracker, pending better solutions — leave me your suggestions in the comments.
[...] QUICK-Searching the Issue Tracker And this is the promised follow-up to “How to report a bug” — searching the Issue Tracker to find what you care about is easier than you might think it is! Source: Tips of the Week #19: Text chat macros & #20: QUICK-Searching the Issue Tracker [...] I have way too many unnecessary gestures. >:D “As part of the rolling restart we implemented a fix for an issue on the Public Issues Tracker, SVC-997. Ok so firstly I’ll admit that I havnt watched the videos yet - ive just arrived home to find a blog post about a “fix” that has shortened the name and description fields for objects. The post mentions this was a fix to SVC-997, so seeing as how Quick Search is supposed to be so useful, I thought I’d log in to Jira and see what the issue was all about. So I try do a normal search, and select “Find Issues” from the menu bar. I get a form that has every field, from project, componet, Linden Issue number etc, EXCEPT a field for the actual Issue number. So third try... I get creative and browse some random issue that happens to be on the page, then change the issue number in the URL to SVC-997, and Im back to the security error. I have no idea why the length of object name and description fields is such a security issue, especially when its mentioned so prominently (I would assume others affected by this fix would also want to view the issue). As for the Issue Tracker,sorry, no comment.
Second Life is currently experiencing Inventory Issues. It is highly recommended that Residents do not rez or edit any items in their inventory or attachments on their Avatars. Second Life at this time is restricted to Linden Login only until this issue is resolved. We apologize for the inconvenience and thank you for your patience.
[UPDATE 06:43 AM PST] Our Ops team is working on the asset server issue. Until this is resolved, we would recommend you refrain from rezzing, deleting or trying to take any objects inworld. Over the last hour, we’ve found an intermittent issue with our asset servers. The errors you’ll see might include failure to delete or take objects, move objects, timed out requests, inability to save scripts or notecards and to change your clothes.
[Resolved] The issue has been corrected. In order to allow the correction to take effect upon your inventory, please Clear Cache (Edit > Preferences > Network tab > click Clear Cache button), followed by logging out and back in again. Thank you for your understanding while we address this issue as expediently as possible.