xotcl-request-monitor

  • last updated 25 mins ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
some more fine-tuning

Make use of extended functionality of OrderedComposite->orderby with -type argument

bumped version number to 0.64

Improve rebustness in error situations.

This change makes sure to always provide initialized aggregated values in case

that "dump read" fails to initialized these.

Make the initial population of the request-monitor counters more robust

switch from xo::db::sql to acs::dc interface

  1. … 11 more files in changeset.
improve description of package parameters

protect against a potential division by zero

use ns_baseunit for time span calculation

  1. … 1 more file in changeset.
improve spelling

  1. … 1 more file in changeset.
fix release dates in .info files

  1. … 82 more files in changeset.
release work

  1. … 204 more files in changeset.
trim potentially partial lines

Add the "/dotlrn" path without tailing slash to the exception list

This will cause just a redirect, but if the server is in a bad state, even this might take long.

bump version numbers of 5.9|5.10 packages to 5.10.0b1

adjust dependencies

  1. … 87 more files in changeset.
minor cleanup for returnurls

  1. … 1 more file in changeset.
reduce verbosity

avoid site-map lookups from the DB when the connections is already closed. This avoids hard DB-errors when the URL contains invalid characters

Sanitize bogus URLs such as "//" or e.g. dotlrn URL lookup would fail

Not clear if this should happen already at the ns_conn level or somewhere in the site_node api

strengthen page contract, add breadcrums

restrict permissions of ip-info page

use tcl "max" idiom

Fix typo

make end of options explicit

  1. … 41 more files in changeset.
add unmapping of slow-pool request for requests mapped via scheduled procedures

undo slow-pool mapping after some time (default 12h)

improve documentation

drop FK on community_id for cases, where communities are frequently dropped.

we do not want to loose statistics in these cases

file upgrade-0.60-0.61.sql was initially added on branch oacs-5-10.

    • -0
    • +0
    ./sql/postgresql/upgrade/upgrade-0.60-0.61.sql
reduce verbosity (set verbose_blocking per default to 0), improve speed of dump creation

New method to cleanup all data associated with a community in the throttle object:

if a community is deleted when a user is accessing it, some leftover information will be kept in the object. At the next request this will be interpreted as the community having been left and the system will try to track this event into request_monitor_community_activities. Depending on who comes first, we might try to insert a tuple in the table for an object that does not exist anymore.

Hence, we use this method to cleanup all community info before the actual deletion in dotlrn (happening only downstream).