this reverts 9df80fbde19e561699af33b591e4fdb6c7bbf9cf
fixing the crash by requiring EMail.php (from AWL)
Note: this isn't called when inviting people yet, only when replying to
an external organizer or when cancelling a meeting with external
attendees. Actually sending these emails instead of just logging them
also requires setting $c->iMIP->send_email = 1;
Prometheus metrics (and database 1.3.2)
This adds support for a /metrics.php endpoint which can be scraped by Prometheus for collecting monitoring and performance data. The metrics can work in two different ways.
Firstly, they can work as a simple set of ever-increasing counters. This is the basic mode, using PostgreSQL database sequences for the underlying data, and hence the new database version associated here.
Alternatively, they can work with memcache to build a more detailed performance picture with more advanced metrics about requests and processing.
If you enable memcache enough to get metrics, you will also get detailed result caching in DAViCal, which seems to work well, but if strange things start to happen that disappear when cache is disabled then it would be great if you could file a detailed bug report.
See merge request !32
There's a long-standing annoyance about catching errors in the early
stages of startup - sometimes they seem to disappear nowhere and yet
nothing works. This fixes at least part of that.
Pass in the refresh interval to fetch_external
If we don't pass in the refresh interval then a default of 1 hour is used, this
isn't really what is intended. (Fixes#92)
See merge request !22
DTSTART/DTEND can be DATE values instead of DATE-TIME. Our database uses
TIMESTAMP WITH TIME ZONE as field type, which seems to accept 19011224
but not values before 1900, such as 18961224. This patch changes values
between 1000 and 1900 to DATE-TIME by adding "T000000Z"
Patch contributed by Benedikt Spranger <b.spranger@linutronix.de>
Patch limited to dates between 1000 and 1900 by Florian Schlichting
<fsfs@debian.org>
This reverts commit 3ab7787f7b2c6bebccbacb31396f77f09aa93f09.
The correct fix for the underlying issue which this attempted
to work around was applied in the AWL/XMLElement Render method.
["correct fix" likely refers to awl commits
4b56e64bc7127a12df737f157e36fd2de19391dd,
2589e71e18e6ced753500afe0197995290fac52c,
aafbd7b1e6ffb59166d57725102f2f5a817a8590 and
46b112f85711732b62e70f2fb40b866423bbf3b5
picked from github handle-remote-attendees branch]
As can be seen from the reporter's debug output, the problem is that
the POST goes to .../?add-member, whereas davical expects / works with /
redirects to ?add_member (note the underscore). So we have davical treat
?add-member the same as ?add_member
