- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 18 2018
Jun 13 2018
Jun 4 2018
Jun 1 2018
May 17 2018
May 9 2018
A few more remarks.
In send_update_notification() we send mail in a loop trying up to 5 times if an error occurrs. But this is the only place where we do this. I think it would make sense to do this in all cases, i.e. in _sendmail(). I see also we don't call smtp.quit() consistently. Once we do this on success only, once we do this on error too.
Looking good, except for the corner-case of an errmsg over an un-"captured" exception.
May 3 2018
May I have a reference?
Apr 19 2018
The weakness in SHA1 is a collision risk, not an active compromise vector.
Apr 17 2018
Apr 9 2018
Mar 12 2018
Mar 8 2018
Feb 7 2018
Jan 24 2018
Jan 12 2018
Jan 5 2018
Nov 28 2017
Nov 10 2017
Oct 30 2017
Oct 16 2017
Oct 13 2017
Oct 2 2017
Sep 11 2017
OK, this is all me ;-)
Sep 8 2017
Sep 5 2017
Aug 27 2017
It's just not getting rebuilt automatically. Let's bump something and therefore trigger a rebuild, so that existing installations receive an update too (now possibly preventing an unstable system from being updated to a stable system).
This needs to be re-evaluated in light of a more recent merge, but there's some questions raised I can see would still need resolving.
I'm sorry, but I'm not sure what feature it is, that is currently lacking, that a Duo backend would add.
Aug 18 2017
No point.
- Use meetingStatus == 1 for the organizer.
Aug 15 2017
- Handle new events
- Return NULL for getEntry(), if there is no such entry.
- Prevent lossy data handling, and preserve the attendee's status
- Update existing events with the new Meeting Status
- Fix mismatch between $existing_event being set and using $event
- Ensure that our new $_attendee is also added back to the list of $event['attendees']
- The organizer is not true by default -- find the organizer, then set ownership
- Respond not with a serverId, instead pretend it is all successful
- Ensure data format transitions retain the additional information wrt. organizer/attendee status
Aug 13 2017
Aug 2 2017
Jul 22 2017
Jul 21 2017
In T1543#38255, @machniak wrote:@vanmeeuwen Does https://git.kolab.org/rP0e8a8276f60b4cf99ef37d9e3b413153d80bcd98 fix this or we plan another solution?
Jul 20 2017
Jul 19 2017
Please see the inline commentary / questions.
Jul 3 2017
Looks good to me. You can remove also COMMASPACE = ', ' line as we don't use this var anymore.