| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
location of the user's UAS. This corrects an earlier design which had some cases pointing to the profile server. WARNING: CONFIGURATION CHANGES in both the sims (*Common.ini) and the Robust configs (Robust.HG.ini). Please check diff of the example files, but basically all vars that were pointing to profile should point to the UAS instead and should be called HomeURI.
|
|
|
|
|
|
|
|
Make them conform with service side commands.
This stops them appearing twice when Hypergrid is enabled.
|
|
harmonise the same commands on the simulator side.
No functional change.
|
|
Update basic profile to use the replaceable interface, making configuration less error-prone. Add support to query avatar's home user account and profile service for regions usng the updated OpenProfileModule with Hypergrid.
|
|
hunting. No functional changes.
|
|
[GridService]. Changed all HG-related .inis, including HyperSimianGrid. No changes in user-facing inis.
|
|
robust UserAccount service would result is LocalToGrid at the sim being false.
|
|
This should make bi-directional hypergrid work.
|
|
|
|
on get_agent_home in UAS.
|
|
|
|
|
|
otakup0pe
|
|
|
|
|
|
wide use will have to wait a few releases. So the sims are still calling GET for now.
|
|
|
|
|
|
with Simian
|
|
This is the message a region sends to its neighbours when it comes up
|
|
57956c4b-ff2e-4fc1-9995-613c6256cc98>: Invalid character 'O' in input string messages
These are just the result of an attempt to canonicalize received messages - it's not important that we constantly log them.
Also finally get the deregister grid service message working properly
|
|
(e.g. 1000, 1000) rather than meter positions (256000, 256000)
|
|
|
|
regeneration.
Maptile storage appears orthogonal to region registration
|
|
|
|
constructed it
|
|
|
|
server with a fatal exception.
Now, such excpetions are caught by an exception handler and just an error message is shown.
This was the kind of exception causing these fatal server crashes:
APPLICATION EXCEPTION DETECTED: System.UnhandledExceptionEventArgs^M
^M
Exception: System.ArgumentOutOfRangeException: Argument is out of range.
Parameter name: offset exceeds the size of buffer
at System.Net.Sockets.NetworkStream.BeginRead (System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback callback, System.Object state) [0x00000] in <filename unknown>:0
at HttpServer.HttpClientContext.OnReceive (IAsyncResult ar) [0x00000] in <filename unknown>:0 ^M
^M
Application is terminating: True^M
|
|
start a new line.
|
|
not a target size. Mono 2.10 appears to try to allocate the full buffer which
immediately crashes. Tested on mono 2.6.7 and 2.10.5
|
|
This reverts commit d30971fdc243886b8fc614c7f869530db87e10f2.
|
|
|
|
These are disabled by default, as before. Please only turn these on in secure grids, since they allow the same facilities as the existing SetPassword call (also disabled by default)
These facilities can be helpful when integrating external systems, in addition to the existing option of adapting an IAuthenticationService or using WebLoginKey
|
|
UserAccountService
Default is false, as before.
Enabling AllowCreateUser in [UserAccountService] for ROBUST allows avatars to be created via an http call, with viewer 2 appropriate bits and pieces.
Only Ruths can be created at present.
Please don't rely on the config since at some point CreateUser will be moved to a separate co-ordinating service.
|
|
|
|
|
|
let all instances of UserAccountService have all its service references properly initialized, and register console commands on only one.
|
|
spam, so it should not load unless HG is desired.
|
|
GridService.RegisterRegion()
Allowing regions with UUID.Zero causes problems elsewhere according to http://opensimulator.org/mantis/view.php?id=3426
It's probably a bad idea to allow these in any case.
|
|
http://opensimulator.org/mantis/view.php?id=3426
|
|
This method is used by externasl/3rd party management tools to
create users and they depend on us to generate the UUID.
|
|
depending on the first two digits of the asset id.
|
|
This should fix recent issues with 3rd party apps that use the
old interface w/o breaking the new one.
|
|
UUID to be specified to override the randomly generated one.
This can be useful in some migration cases where recreating user accounts with known IDs will preserve region scene object ownership.
|
|
When a slider parameter is changed, the viewer uploads a new shape (or other asset) and the item is updated to point to it.
Viewer 1 uploaded the data in the initial request itself, so the asset references was almost always correctly updated.
However, viewer 3/2 always uploads data in a subsequent xfer, which exposed a race condition where the viewer would make the item update before the asset had uploaded.
This commit shuffles the order of operations to avoid this race, the item is updated with the new asset id instead of the old one while the upload was still taking place.
A second race had to be fixed where avatar appearance would also be updated with the old asset id rather than the new one.
This was fixed by updating the avatar appearance ids when the appearance was actually saved, rather than when the wearables update was made.
|
|
5035).
Using the RemoteAdmin API to close then recreate a region would fail if the estate name had not changed. If the estate name /was/ changed then the existing estate would be renamed rather than a new one being created. The problem really arose from a lack of distinction in the data storage layer between creating new estates and loading existing ones.
|
