| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This records how many packets were indicated to be resends by clients
Not 100% reliable since clients can lie about resends, but usually would indicate if clients are not receiving UDP acks at all or in a manner they consider timely.
|
| | |
|
| | |
|
| |
|
|
| |
disconnected.
|
| |
|
|
|
|
|
|
| |
generate syntax error as seen on the LL grid
This is done through the parser and so generates the same syntax error message if any parameters are wrongly specified for this event.
We were already enforcing event names in the parser.
This is only for state_entry so far as an initial test of the approach - appears to work correctly.
|
| |
|
|
| |
j2kDecodeCache folder should be cleared after updating to this revision so that sculpts containing alpha can be re-decoded and successfully meshed.
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
BotManager rather than Environment.Tickcount
Otherwise, since bots are now created all at once, a bunch will get exactly the same tickcount and hence number sequences
|
| | |/
|/| |
|
| |/ |
|
| | |
|
| |
|
|
| |
first added a few commits ago
|
| |
|
|
| |
UploadBakedTextureModule
|
| |
|
|
|
|
| |
This allows one to monitor the total number of messages resent to clients over time.
A constantly increasing stat may indicate a general server network or overloading issue if a fairly high proportion of packets sent
A smaller constantly increasing stat may indicate a problem with a particular client-server connection, would need to check "show queues" in this case.
|
| |\ |
|
| | |
| |
| |
| | |
particle system functionality. Note that this does *not* complete required server side changes for implementing the new particle system
|
| |/ |
|
| |
|
|
| |
rate that is currently only displayed if LogLevel >=1 in [AssetCache] config
|
| | |
|
| |
|
|
|
|
| |
blank response from server or connection failure.
Raise log lines which indicate problems to warning from debug
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
| |
[Startup] section.
These are long unused but confusingly will be seen in the [Startup] section on a "config save".
|
| |
|
|
|
|
|
| |
ObjectProperties UDP replies to viewer
Not yet shown that this is used or resolves a bug where not all textures appear on objects with an "XML with textures" upload from singularity 1.8.3
Proper texture entries are actually present and appear properly on relog, but not on select from viewer until at least one face texture is changed.
|
| | |
|
| |
|
|
| |
Appears to be a never used method.
|
| |
|
|
| |
if we sent immediately)
|
| |
|
|
|
|
| |
static objects.
Reorder collision flag setting code for terrain to fit pattern used elsewhere.
|
| |
|
|
| |
Signed-off-by: teravus <teravus@gmail.com>
|
| |
|
|
| |
(The changes weren't visible before because updates to attachments aren't sent while the attachment is selected.)
|
| | |
|
| |
|
|
| |
duplicate the assembly resolving.
|
| |
|
|
| |
Mono.Security.dll missing. The root of the issue is that the Postgres driver relies on Mono.Security.dll from the mono project. Unfortunately, when using Mono, including the dll in the distribution causes conflicts. This solution puts Mono.Security.dll in bin/lib/NET/ and, if windows .NET is the runtime, informs the assembly loader to load bin/lib/NET/Mono.Security.dll when .NET is scanning for the Mono.Security namespace. On Mono, the included Mono.Security assembly is ignored.
|
| |
|
|
|
|
|
|
|
|
|
| |
the vehicle buoyancy if the vehicle is above its hover height.
This is a known misfeature of this vehicle flag which has been accepted
since it would break too many implementations. The problem is noticed
when creating a jetski-like vehicle that jumps over sand bars. A boat
normally is configured with neutral buoyancy and hovering at water
height. When it jumps the sandbar, it needs to have gravity applied
to get back to water level.
|
| |
|
|
| |
Previously only the first object in the Coalesced Object was rezzed. Now all the objects are rezzed.
|
| |\ |
|
| | |
| |
| |
| | |
* Please test
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added PostGreSQL support
* Added MySQL/MySQLXGroupData.cs
* PostgreSQL data access implementation
* PostgreSQL dll binarie and RegionStore.migrations
* Migrations Scripts from MSSQL to POSTGRES
* Postgres SQL Type fixes
* Postgres SQL Connection string
* Data type issues
* more fixes
* tests and +tests
* UUID x string - FIGHT!
* Fixed PG types to internal csharp types
* More data type fix (PostgreSQL fields are case sensitive) :(
* more field case sensitive fixes
* changed the migration files to be case sensitive for fields.
* fixed fields case
* finished converting, now search for hidden bugs.
* some more fixes
* bool type fixed
* more case fixes;
* creatorID case fixed
* case fields fixed
* fixed default now() for TMStamp fields with don't allow nulls.
* fix case sensitve for Region name and Estate name
* fixed case for names for search
* fix class name Error
* Bug fixed on select and migrations
* Un-Reverting my change due to Postgres issue with the ILIKE function
* Fixed some issued for Diva Distro
* Fixes for integration with Diva Distro
* Added System.Core to prebuild.xml for PG project
* Configured to make DIff for Push to OpenSim Project
* Diffs only to PostgreSQL mods.
|
| | |
|
| |
|
|
| |
specify number of concurrent requests on a service.
|
| | |
|
| |
|
|
|
|
| |
belong there.....)
* Add an IsBlocked(string Key) method so it can be used more generically. (think.. if we want to rate limit login failures, we could have a call in the Login Service to IsBlocked(uuid.ToString()) and ignore the connection if it returns true, if IsBlocked returns false, we could run the login information and if the login fails we could run the Process method to count the login failures.
|
| |
|
|
| |
* Break out common BasicDOSProtector code into separate class.
|
| |
|
|
|
|
|
|
|
| |
HTTP Server handlers. XMLRPC Handler, GenericHttpHandler and <Various>StreamHandler
* Applied the XmlRpcBasicDOSProtector.cs to the login service as both an example, and good practice.
* Applied the BaseStreamHandlerBasicDOSProtector.cs to the friends service as an example of the DOS Protector on StreamHandlers
* Added CircularBuffer, used for CPU and Memory friendly rate monitoring.
* DosProtector has 2 states, 1. Just Check for blocked users and check general velocity, 2. Track velocity per user, It only jumps to 2 if it's getting a lot of requests, and state 1 is about as resource friendly as if it wasn't even there.
|
| |
|
|
| |
the LLSD login code. This sends the data through the normal login channels and spits out a JSON object back that mimics the login response. Feel free to comment on the best way to set this up as a config option.
|
| |
|
|
| |
it easier to write WebSocket service code that is resistant to Denial of Service attacks.
|
| |
|
|
| |
shout-range, at the request of Singularity dev Liru-Dargon
|
