CalDavBackend: check if timerange is array before accessing #23497
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Simon Spannagel <simonspa@kth.se>
kesselb
approved these changes
Oct 19, 2020
nickvergessen
approved these changes
Oct 19, 2020
|
/backport to stable20 |
|
/backport to stable19 |
|
/backport to stable18 |
This was referenced Oct 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #20784. Some CalDav clients (such as Evolution/GNOME contacts) seem to send
time-range: falseinstead of not adding thetime-rangekeyword at all, so we need to check if it is an array before actually using it.