Slack import problems

[sunjam]

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.

[sunjam]

Switched from Docker "Stable" Tested Rocket.chat to the 0.73.1 release container.

Here is a Gist of my Rocket.chat error log when attempting to import Slack data into Rocketchat 0.73.1 docker release with mongo:latest

Failed_to_load_import data. Where is the documentation for this notification? I do not see anything in the docs.

Also receiving a error when attempting to send messages; see Gist here.

[reetp]

This follows questions on #support

I have mentioned that node only runs single threaded and you may want to look at PM2

I also asked about your laptop connection. Hard wired, wireless, speed etc. Please advise.

[sunjam]

Laptop connections were tested on a few different machines running Qubes, Lubuntu, and MacOS. Browsers tested are Firefox stable and Chromium. Internet connections tested are point-to-point-gigabit laser along with domestic dsl (~10mb upload)

[engelgabriel]

We have decided that was better to delay our v1 release and get the Threads done properly than get the feature out the way it was initially implemented on the develop branch. We have "rebranded" our current implementation of Threads to Discussions (was it creates a new room type) and will implement Threads exactly the same way as Slack does.

In our vision there are 2 different use cases on how to break out of the main conversation: one very easy and organic, with a single click for small side talk, and other, much more structured, that creates a new conversation with its own life cycle.

We have tried to have a single solution for both, and as a result, no one was happy with it.
So we have given up on having a single approach for both use cases and will implement both: the Slack-like industry standard and our brand new one, called Discussions.

#13843

[engelgabriel]

With the new thread implementation that we are working on, we will copy the slack model, so the import will be much easier.

[engelgabriel]

#1112

[pierre-lehnen-rc]

The reported problems were fixed on #16279 except for the item mentioning that Rocket.Chat uses a single CPU core.