Jump to content

Monty Linden

Lindens
  • Posts

    520
  • Joined

Everything posted by Monty Linden

  1. Caspertech support should be able to help. Start there if anything is amiss...
  2. Drop a viewer enhancement request into feedback. We should be able to manage LMs like browsers manage BMs. (Probably)
  3. I created an explicit Canny issue for the missing EAC messages so that it can be tracked and possibly fixed separately from the EventQueue problems. https://feedback.secondlife.com/server-bugs/p/simulator-http-setup-missing-establishagentcommunication-messages
  4. The 'feedback' issues (Canny) represent new development including a new external service. That doesn't happen in days (when I said 'slow,' I really meant slow). That's why you need to follow through with a support ticket and maybe a bug report in feedback. These have faster return times (but not always with the response residents want).
  5. With a mix of failing and succeeding accounts on the same machine, backend systems, usually inventory, are at work. A support ticket is the way to start.
  6. I'd expect the viewer to composite the information sources to produce lists and visual feedback (caveat: never dug into this system before). New inventoried LMs certainly show up for me. But I can also imagine that stale inventory cache would leave things around to be found by the map code. The LM list in the world map also appears to index by name and so non-identical LMs with the same name might be considered identical to the map. This looks like a grand opportunity for filing some Canny bugs!
  7. Notecard-based return receipts mapping object to location might be a nice touch...
  8. There is an order to it. The idea being to slough off suitable victim objects when limits are encountered. But the specification is complicated and subject to change without notice. If you experience something that seems at odds with sensible victimhood, just file a bug because it needs attention from time to time (and I believe has received some recently). Such bug reports should have as much detail as possible (region, parcel, location, time, date in the Mayan calendar, etc.). This thing is a function of 47 or more variables.
  9. Are you kidding? We have to share trouser pockets here...
  10. Ditto. Follow Henri's advice on this one....
  11. For transparency, I made some Canny issues for this: LSL llHTTPRequest Supported Search API These are bug/feature requests and so the response time on them is going to be slow. Fast responses come from support tickets and elsewhere. But people should be able to comment and upvote on the issues.
  12. Bwahaha, we used a lot of phlogiston back in those days. Those appliances are long gone. Along with the Isilons and more. I'm surprised the URL patterns still worked or that anything on that page still applies. I'm trying to bracket when the externally-visible behavior changed. I'm not web but I'm not seeing a cause...
  13. Yes, without cookies, it just goes into a redirect loop.
  14. Well, it was late and so I didn't (and still don't) have all the answers. There will probably be some issues filed on this (and I'll mention them here). And I'm going to run down some other answers. The Search API page is notable for having last been edited in 2011. (Almost typed 1911.) The curl command (now edited) isn't a solution for you, @VirtualKitten. But it is a tool that allows you to see what is occurring. The exciting thing is that it also exposes some bugs in curl (which we use internally). Curl 7.64.0 and 7.66.0 handle cookies slightly differently and we may be triggering something. @VirtualKitten, when did this stop working for you?
  15. Well, I can answer what the root error cause is (though several are involved in this case): URLRequest Error: 47, Number of redirects hit maximum amount, http://search.secondlife.com/?query_term=Galadriel%27s&search_type=standard&collection_chosen=events&maturity=gma Too many redirects and that information isn't passed back in any useful way.
  16. DNS chains are silently followed and wouldn't cause this problem (ignoring TLS cert validation for the moment). If you run your search query through a 'curl' command such as: curl --http1.1 -v -L -o /dev/null 'https://search.secondlife.com?query_term=Galadriel%27s&search_type=standard&collection_chosen=events&maturity=gma' you will see the sequence of visits that are made as the request gathers state information into cookies. There are a number of possible reasons for llHttpRequest failing on this: cookie management during the request redirect count (3xx codes) other limits (header length, response body length)
  17. One discovery: search absolutely requires the use of cookies. The llHttpRequest APIs are likely not helping in this area so this may very well require some enhancement.
  18. I think I agree that this should be better available. The support ticket is one way to try to kick things. You might also want to go to https://feedback.secondlife.com/ and file a bug or feature request on this. I noticed the redirection chain is going through an auth endpoint and is doing a good amount of cookie churn to pass context along. There may be a way to start in the middle of the chain and get a search result back easily.
  19. Necropost! Doubly so as oz is no longer here. A quick check with 'curl' shows that that URL needs to go through about seven 3XX redirects to finally produce output and the final response is about 24KB. I suspect http-out limits are generating a 499 error and extended error status would provide more information. (I haven't checked this - just throwing it back out there.)
  20. There is a possible fix for late EAC taking shape in one of the active projects. It might over-generate messages but a change is coming. Schedule unknown as yet.
  21. Oh, it's almost certainly true. It's what you get with evolution through a series of errors rather than design. The simulator didn't spec or implement the right thing. The viewer made an adaptation keeping old caps around. Simulator then had to follow the viewer keeping old caps alive per viewer spec so implements weak persistence and caching. That cache doesn't always work as expected with undocumented lifetimes, etc., and the viewer adapts freezing the evolved spec at a new behavior. Repeat. The texture and mesh caps are 'local' resources that will supply grid-wide data, even before CDN, so likely showed up here first. Inventory and other APIs have similar looks-local-acts-global scope. But some really are local and you need those caps. Or you end up using another simulator as proxy. I really do tip my cap to the OS people for trying to chase this moving target with very little help from us...
  22. It's us. Things are recovering. But never trust that aws status...
  23. Yep, another possibility. For development work, I cheat. I just disable encryption everywhere and work in cleartext. That doesn't work on Aditi.
×
×
  • Create New...