| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
This resolves the problem where eyes and hair would turn white on standalone configurations
When a client receives body part information, for some insane reason or other it always ends up uploading this back to the server and then immediately re-requesting it.
This should have been okay since we stored that asset in cache. However, the standalone asset service connector was not checking this cache properly, so every time the client made the request for the asset it has just loaded it would get a big fat null back in the face, causing it to make clothes and hair white.
This bug did not affect grids since they use a different service connector.
|
|
|
|
| |
This should accommodate various timeout problems that exist with the current connection pool code in a more general and standard way.
|
|
|
|
| |
the grid server after running for several hours
|
|
|
|
|
|
| |
Local member in MySQLAssetData
* First pass at applying the using(){} pattern to IDisposable objects. Always use the using pattern on IDisposable objects whenever possible, do not manually call .Close() or .Dispose() unless there is no other way to write the code. This pass mostly covers OpenSim.Data.MySQL, and should have no functional change (tests still pass)
|
| |
|
|
|
|
| |
LICENSE.txt.
|
| |
|
|
|
|
|
|
|
| |
* This fixes adding and updating user profiles in MySQL on platforms that have a commas as a decimal separator
* Thanks Tommil!
|
|
|
|
|
|
| |
* please say if this causes you a problem
|
|
|
|
|
|
|
|
|
| |
from the presence module to the message server, through the user server
and on into the database. This should fix the "Already logged in" issue
that grids see after a sim crashes, or a user crashes out of a sim.
Not yet a 100% solution for friends, but getting there.
|
| |
|
|
|
|
|
|
|
| |
Add more unit tests for user cases
Persist more user fields into mysql that already had columns
defined but weren't getting passed to the mysql manager.
|
|
|
|
|
| |
From: Sean Dague <sdague@gmail.com>
|
|
|
|
|
| |
* Added additional error message when a Object/SOG DB save fails so we can trace why.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on-/offline updates, calling cards for friends.
This adds methods in the DB layer and changes the MessagingServer, so a full
update (incl. UGAIM) is necessary to get it working. Older regions shouldn't
break, nor should older UGAIM break newer regions, but friends/presence will
only work with all concerned parts (UGAIM, source region and destination
region) at this revision (or later).
I added the DB code for MSSQL, too, but couldn't test that.
BEWARE: May contain bugs.
|
|
|
|
|
|
|
|
| |
locks to just before the try/catch/finally block, so that an exception
thrown between taking the lock and entering the try doesn't leave a mutex
locked
|
|
|
|
| |
potential issue when in high load. Related to mantis #2508.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Makes SQLite mimick MySQL default behavior on first
and last name already on db: it does not insert the
new record.
- Added tests for UUID 0 and for new UUID with existing
first and last name.
|
| |
|
| |
|
|
|
|
|
|
|
| |
doesn't work in a world of migrations anyway, and is only cruft that
will confuse people.
|
|
|
|
|
|
|
|
|
| |
Moved intialization of appearance from the SendInitialData
event handler into CompleteMovement handler. That ensures
that m_appearance is initialized before the inventory is
retrieved (so there is a place to check on attachments).
|
| |
|
|
|
|
|
|
|
| |
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
|
|
|
|
|
|
| |
Thank you, cmickeyb, for a patch that corrects the database connection
handling in the multithreaded user server.
|
|
|
|
| |
(Didnt realise this code was being shared with the gridservers)
|
|
|
|
| |
have been delayed for 1000ms. This has been fixed.
|
|
|
|
|
|
|
|
| |
multiple concurrent MySQL threads.
* Implemented SuperManager inside of UserData. This means the userserver when running on MySQL will use 10 connections (+1 system connection) to handle requests, preventing the previous mire of locking resulting in singlethreadedness.
* This requires testing and grids relying on stability should not upgrade to this revision until it's been properly tested.
|
| |
|
|
|
|
|
|
|
|
|
| |
Change user server to handle attachment assets record properly. Ensure
that attachments are not re-rezzed on region crossing. Persistence
will NOT WORK with earliser UGAI!!
Change region server to match.
|
| |
|
|
|
|
|
|
| |
Attachments now save to MySQL. No reattach on login yet.
|
|
|
|
| |
location, same uuid or same internal ip port) then complain loudly and don't start up
|
|
|
|
|
|
|
| |
Plumbs in attachment persistence and adds the tables. Currently MySQL
only, no user functionality yet.
|
| |
|
|
|
|
|
|
|
| |
This will have no effect unless both the UGAI and the region are
this revision or later
|
|
|
|
|
|
|
| |
Thank you, HomerHorwitz, for a patch that corrects and improves TP
to landmark and home position handling.
|
| |
|
|
|
|
|
|
| |
PluginLoader. Fix issue 1871.
|
|
|
|
| |
files. Thanks kerunix_Flan!
|
|
|
|
| |
hard-coded port numbers.
|
|
|
|
|
|
|
|
|
| |
and no schema. It should also work with a non up to date schema as well.
Btw, meetings in which I can get code done are the right kind of meetings.
|
|
|
|
|
|
|
|
| |
data sources besides the grid store. It is only lightly tested
so the less adventurous should wait a couple of checkins before
upgrading.
|
|
|
|
|
|
|
| |
* User tries to log-in but is already logged in. Userserver will send message to simulator user was in to log the user out there.
* From the UserServer, admin types 'logoff-user firstname lastname message'.
* Some regions may not get the message because they're not updated yet.
|
| |
|
|
|
|
|
|
| |
still not convinced this will help, but it was wrong.
|
|
|
|
|
|
|
| |
get saved to the database. There are still issues on wearing things
after a cleared cache that I'm looking at now.
|
| |
|