[calendar] deny fetch interval < 60000 and set 60000 in this case (prevent fetch loop failed) #3382
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.
Hi, I had the case of some users who set a very small fetchinterval (10 sec for example)
in some cases, it may be that the request did not have time to complete correctly and that the next one has already been sent (generally on start of MM²)
I think that lock min fetchInterval to 60000 is a good idea