| Age | Commit message (Collapse) | Author |
|---|
|
|
|
in llpolymorph
|
|
|
|
cleanup.
Our logging holds on to a changing bit of memory between operations and the memory
leak detection I'm using senses this and complains. So, for now, disable the
final memory check on Mac & Linux, leave it active on Windows. Solve this for
real some other day. Add try/catch blocks to do cleanup in unit tests that go
wrong so that we don't get a cascade of assertion failures when subsequent tests
find singletons still alive.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
dictionaries
|
|
|
|
|
|
|
|
|
|
|
|
|
|
settings.xml
|
|
http://hg.lindenlab.com/nat/viewer-maint-1144/ to resolve build issues.
|
|
|
|
lure informing the inviter that the guest cannot access the region because of their maturity level.
|
|
|
|
lure.
|
|
|
|
|
|
take out items from the list
|
|
surprised me. Added a retry queue similar to ready queue to the
policy object which is sorted by retry time. Currently do five
retries (after the initial try) delayed by .25, .5, 1, 2 and 5
seconds. Removed the retry logic from the lltexturefetch module.
Upped the waiting time in the unit test for the retries. People
won't like this but tough, need tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
color for user messages
|
|
who want to try IPV6 can still override at will using CURLOPT_IPRESOLVE.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
