RocketChat / RocketChat/Rocket.Chat
Slack import problems
Open
Nobody has claimed this yet.
feat: import
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Rocketchat Stable docker release 0.71.1 link from your Github returns a 404 error. Using the stable, I see it is having difficulty importing 43mb zip containing around 700,000 channels/messages from Slack. I recommend breaking the Slack exports into no more than a few megabytes or they will crash browser tabs in Chrome or Firefox. These smaller archives of around 70,000 messages/channels still crash constantly while importing. Can confirm browser tabs crashed on different computers attempted with different browsers.
Server has 4-core, 24gb of ram, 10gb connection.
- Cannot find a command that will import Slack data without using webui.
- Cannot find any method for cancelling a hanging, timed out import; all I see is the three dot waiting animation until I go from selecting an import file to being able to start the import/selection process.
- Deselect Deleted Users does not do anything within import menu. I have to manually deselect each deleted user.
- Slack data import failures happen with a tiny pop up notification from Rocket.chat, which disappears after 4 seconds and is very frustrating. You can only notice it if you are literally looking at that exact import page in those 4 seconds... otherwise you must dig into logs.
- After import failure, admin is dropped back to "Select a Slack file to import" screen under administration, which is confusing because you cannot tell whether the import succeeded or failed. Why does an import error notification not remain on the screen within the import administration tab?
- No ability to resume an import after failure. I'm surprised Rocket.chat doesn't attempt to resume the import.
- Even a several megabyte zip takes approximately 1.5 - 3 hours to import.
- Node uses only a single cpu core at 100% during import.
- RAM usage spike during import will crash a Chrome or Firefox tab if imported Slack is even a few megabytes in size. Tabs crashed while testing with different laptops and different operating systems, each computer had at least 8gb ram.
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.
Assessment
This issue has not been assessed yet.