| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
work with viewer 2.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
on the target system for an iar load
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
as well
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
OSP resolved ID if newer CreationData is not present.
This should resolve issues where the creator for rezzed objects was being shown as "Unknown user" where previous behaviour was to show the OSP resolved account.
This is being done by parsing the serialized objects and updating the CreatorID if no CreationData exists. This operation might be expensive for sculpties where the sculpt texture is inlined with the object data. Will just have to see.
This relies on the IAR streaming inventory data before asset data (as is currently the case). Will need to introduce more stringent checks for file order on loading (much like JAR zips must start with the manifest file).
This is for IAR loading only. Tests updated to check this behaviour.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
format rather than 'xml2'
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
constructing the tar manually
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
intention (i.e. OSPA resolution, which is still active).
Will need to write a separate test for the simplest case where creator accounts with appropriate uuids exist on iar load.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
into a new test TestLoadIarToInventoryPaths()
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This version removes the NUnit.Framework.SyntaxHelpers namespace, so any modules with their own tests will need to delete this using statement.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This version fixes a bug so that MySqlCommand.CommandTimeout = 0 now correctly sets an infinite command timeout. This might help with failures on long-running migrations.
The mysql.data.dll v2 is used from the mysql package (as opposed to v4). The v4 version (probably standing for NET 4.0) does not work under mono 2.6.7, which is still commonly used.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
test case parent
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
preserving service instances between tests. This wasn't being used anyway and just leads to hard to diagnose test failures.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
static dictionaries on NullUserAccountData instance instead to stop user accounts being carried over between tests
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
message origins.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
can be overwritten in subclasses. That way extensions can decide in which assembly migration resources should be looked up. This is just a refactor -- no functional changes whatsoever.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
recreating it every time
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
false
Implement test for ClearMediaEntry()
|
|\ \ \ \ \ \ |
|
| | | | | | | |
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
AgentUpdate messages. Should improve throttles and reprioritization
when an avatar is moving.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
media texture.
We weren't setting the TextureEntryFace.MediaFlags = true when a media texture was set directly via a script. This was being done when the viewer was setting them directly.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
inconsistently. (maybe related to mantis #5386)
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
CACHE] section is missing or just the particular config values
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
there is a [FLOTSAM ASSET CACHE] section present at all, use the same default all the time
this simplifies the code
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
the default
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
asset cache to try using Double.MaxValue, which would cause the underlying OpenMetaverse.ExpiringCache to choke.
There is probably an underlying bug to fix in ExpiringCache.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
trace so that we get somewhat better diagnostics on windows
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
object rather than the owner of the inventory item. In theory,
this shouldn't happen unless you are using grid-wide library
for inventory.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
child agents in neighbor regions. This means you can extend
the view on a simulator beyond the default 3x3 regions.
This uses a region default draw distance and should be
replaced at some point by the avatar specified draw distance.
That will require more careful, dynamic recomputation of child
agents every time the draw distance changes.
WARNING: this is experimental and has known instabilities. specifically
all regions "within site" should be running the same default draw distance
or agents will not be closed correctly.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The in-memory storage of region data that is used by default with SQLite now handles wildcards in region names in the same way as SQL queries do with other databases.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This test was non-viable. Keeping inactive T021_TestCrossToNewRegion() around for now since it's still useful for reference purposes in constructing a future working test.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Calling async code in automated tests is never a good idea - things become very fragile very quickly
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
this is done differently elsewhere
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Stop tests setting up a capabilities module by default
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
rather than causing a null reference on the normal log line
This also extends the TestChildAgentEstablished() test to actually activate the EntityTransferModule, though the test is not yet viable
|
| | | | | | |
|