nextcloud / nextcloud/calendar
Handle backend rate limits gracefully
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Use this app with https://github.com/nextcloud/server/pull/43732
- Create too many calendars too fast
Expected behavior
Human readable error explaining the situation
Actual behaviour
Generic error that doesn't say much
Calendar app version
No response
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
No response
Updated from an older installed version or fresh install
None
List of activated apps
No response
Nextcloud configuration
No response
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using nextcloud/server pull request 43732 by creating calendars rapidly, then trace where the generic error is surfaced in the Calendar app. Done means backend rate-limit responses produce a human-readable explanation instead of the current generic error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100