nextcloud / nextcloud/calendar
Importing bigger .ICS files only imports part of it
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Export your old calendars
- Reimport a big .ics file (>= 100KB) e.g. create a new calendar
- Wait, till NC notifies about a timeout and counts down to refresh the page (here it was ~20secs)
Expected behaviour
The importer should deal with every file (size) that was also create by NC sucessfully. This is essential for user backups and user doesn't noticed, that he gets a corrupted reimport (and might start working on the calendar).
Actual behaviour
You don't see any hint about the ongoing import, but only a message that the page will be refrehed.
I managed to splitup the files till ~ 50kb to workaround this bug. This seems to be a regression and I noticed a similar problem to the contacts import.
Calendar app
Calendar app version: 2.0.4 (but same behaviour on NC 19.0 before)
CalDAV-clients used: -
Client configuration
Browser: Firefox 80
Operating system: Linux Mint 10
Server configuration
Operating system: Centos
Web server: nginx
Database: mariadb
PHP version: (e.g. 7.0.3)
Nextcloud Version: 19.0.2
Updated from an older installed version or fresh install: fresh
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
Start by reproducing the large-file import with the reported calendar app and Nextcloud versions, comparing a file around 50KB with one at least 100KB. Trace the calendar importer and timeout behavior to determine why the import stops early; done means the complete file imports successfully without a misleading refresh notification, with the regression and contacts-import behavior checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100