-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import of Hipchat export (tar.gz) is failing with invalid format #11355
Comments
as i just figured out, there is a new hipchat version (2.4.0). I will update the system and will recheck the import |
even with Hipchat 2.4.0 and the export from that system i am getting the exact same error |
I'm getting a lot of errors:
I've looked into source and debugged
because
Maybe it is problem with 'tar-stream' package. |
It looks like the importer takes chunks out of the tar stream and tries to JSON parse them. But to get correct JSON the entire file is needed at once. Maybe the the chunks first needs to be collected in a temp file and then parsed? |
But I assume it worked before
W dniu pon., 30.07.2018 o 10:19 Jakob Lundberg <notifications@github.com>
napisał(a):
… It looks like the importer takes chunks out of the tar stream and tries to
JSON parse them. But to get correct JSON the entire file is needed at once.
Maybe the the chunks first needs to be collected in a temp file and then
parsed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11355 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXy-UZwNR8ZHmkqkjR3IwJCdIzIBi_Hks5uLs-KgaJpZM4VDsIt>
.
|
And loading json into file means it must be loaded into memory after so
file step is unnecessary. U think the better way is to use json stream
package.
… But I assume it worked before
W dniu pon., 30.07.2018 o 10:19 Jakob Lundberg ***@***.***>
napisał(a):
> It looks like the importer takes chunks out of the tar stream and tries
> to JSON parse them. But to get correct JSON the entire file is needed at
> once. Maybe the the chunks first needs to be collected in a temp file and
> then parsed?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#11355 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFXy-UZwNR8ZHmkqkjR3IwJCdIzIBi_Hks5uLs-KgaJpZM4VDsIt>
> .
>
|
Well loading everything into memory is also possible. Here is how it could work |
Still, this is very memory consuming way. I think that is would be better to use JSON Stream, something in the way like:
In this approach tar-stream streams file contents while Json Strem tries to assemble them on the fly. "header" is still available so could be used to detect which file is being read. |
Is there something how i can support you (i am not a developer). So i guess there will be more users in the next months which are migrating from Hipchat Server to Rocket.Chat (like we are doing) |
@piotrkochan Will you make a pull request with your solution? Otherwise I can make one with my simple "load entire file into memory" approach. |
Rocket.chat I'm still getting invalid import file type error. New export from Atlassian HipChat 2.4.1 (2018.07.19.134050) |
@jakob-lundberg sorry I can't |
i see same error It happens when i try to upload 950Mb file. But when i try to upload 24Mb then this stage is ok. but then everything stops on following My small archive contains only users and rooms and no massages and no attachments |
i found in the code if (tempUsers.length === 0 || tempRooms.length === 0 || messagesCount === 0) { it looks like i canot import without messages. but with messages my file is too large. i will try to copy several messages from be archive to small |
I recommend upload file WITHOUT ATTACHMENTS. Rocket will download them
online
pon., 24 wrz 2018 o 14:00 artem-levashov <notifications@github.com>
napisał(a):
… i found in the code if (tempUsers.length === 0 || tempRooms.length === 0
|| messagesCount === 0) {
... return }
it looks like i canot import without messages. but with messages my file
is too large. i will try to copy several messages from be archive to small
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11355 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXy-TqWrQF909rDbN0O5KzL2WXkI52-ks5ueMlPgaJpZM4VDsIt>
.
|
with history of only 1 room import works and i`m able now to select what i want to import (but unfortunatly here is also problem - Buttons Uncheck deleted and archived are not working - need to unchek each item manualy.) so here is still big problem for me how to transfer history. my full history wihtout attachments has size 950Mb in archive - it is about 3 years of using hipchat. it looks like Rocket do not wait while such big size will be uploaded. I think a lot of people needs it to work - the February is close :-) |
I'm stuck with the same problem. |
Bump - the same issue here. |
@marcinkorzycki RocketChat 0.73.0 introduced some Hipchat Enterprise importer improvements (#12985), did You tried it? |
I have the same problem when trying to import from Stride. I have a tar,gz file that I can see all users, rooms etc. I can select the file and in the GUI I see all users and rooms but the buttons doesn't work. Please try to fix this ASAP since only a few weeks left before HipChat/Stride is closed and Slack is not an option for us. |
We're having exactly the same issue. any news on this? The Stride end date is coming close and Rocket is exactly what we need... |
We was able to move from hipchat to rocket only by longway workaround. We have dowloaded history by small periods. Each file was no more then 100mb maybe less. We spent about 1.5 weeks to upload history of 2 years. |
Well, we're trying to import only the chat rooms + users and that's around a 2mb file... so file size is not the issue |
In the new version 0.74 that is coming I saw there was something fixed for HipChat import. From the support they told us that they only support import from HipChat not Stride, I think it's the same format of the export file though. Anyway, we have give up and are moving to Slack, quite good offer the first year for the paid plan. |
Check room topics. We had problem with import when russian letters was used in room name. I had to rename rooms before transfer. Dont forget to chekc deleted rooms also. |
Antoher problem was with users with same email but different names. Check that you dont have inactive users with same emailn as active |
All known hipchat import issues have been fixed with the release of version 0.74.3. If anybody runs into any issue with it, please open a new issue. |
Rocket.Chat Version: 0.65.1 (snap installation)
Host-System: Debian GNU Linux Stretch
I created an export of my current Hipchat Installation (Atlassian HipChat 2.2.9 (2018.01.23.110010)). This is a standalone installation and not the cloud version.
The export was an AES encrypted file (around 950MB)
hipchat-2018-07-05_09-30-12.tar.gz.aes: openssl enc'd data with salted password
I decrypted the file with
openssl aes-256-cbc -d -in /home/mbasse/hipchat-2018-07-05_09-30-12.tar.gz.aes -out /home/mbasse/hipchat-2018-07-05_09-30-12.tar.gz -pass pass:******
So i got the tar.gz file
hipchat-2018-07-05_09-30-12.tar.gz: gzip compressed data, was "hipchat-2018-07-05_09-30-12.tar", last modified: Thu Jul 5 09:30:12 2018, max compression
I was able to open the tar.gz file with my local file browser. I was also able to extract it.
I tried to import the file with these 2 options (because i dont know what the difference between Hipchat and Hipchat Enterprise is
FQDN/admin/import/prepare/hipchat
and also
FQDN/admin/import/prepare/hipchatenterprise
In both cases i got after some seconds the error message "Ungültiges Importformat" (english: invalidf import format)
I hope these information are useful. If you need further information please feel free to ask.
Greetings from Germany
Michael
The text was updated successfully, but these errors were encountered: