Skip to content
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

HipChat Cloud import fails (rooms -> channels) #8474

Closed
matthewandrews opened this issue Oct 13, 2017 · 3 comments
Closed

HipChat Cloud import fails (rooms -> channels) #8474

matthewandrews opened this issue Oct 13, 2017 · 3 comments
Assignees
Projects
Milestone

Comments

@matthewandrews
Copy link

Description:

Importing a HipChat (Cloud, not Enterprise) export file fails. Debug shows that the HipChat rooms have not been parsed (users and messages may be OK).

Server Setup Information:

  • Version of Rocket.Chat Server: 0.58.4
  • Operating System: Linux 64 bit (Ubuntu 16.04)
  • Deployment Method(snap/docker/tar/etc): snap
  • Number of Running Instances: 1
  • Node Version: 4.8.4

Steps to Reproduce:

  1. Generate an export file from a HipChat Cloud group.
  2. In Rocket.chat, go to Administration > Import and hit the HipChat button (not HipChat Enterprise).
  3. Hit the 'Choose File...' button and select the HipChat export file for upload.

Expected behavior:

Import to succeed, with users and channels created, and channels populated with messages.

Actual behavior:

Error message on screen: "The file uploaded isn't a valid HipChat export file".
Logs show that the users and messages appear to have been parsed successfully, but no channels ("rooms" in HipChat terms) have been parsed.

Relevant logs:

Server log (debug level):

[34mI20171013-14:20:42.330(11) [34mHipChat Importer ➔ debug Uploaded file information is: { ext: 'zip', mime: 'application/zip' } 
[34mI20171013-14:20:42.332(11) [34mHipChat Importer ➔ debug Expected file type is: application/zip 
[34mI20171013-14:20:42.335(11) [34mHipChat Importer ➔ debug HipChat is now at importer_preparing_started. 
[34mI20171013-14:20:43.826(11) [34mHipChat Importer ➔ debug HipChat is now at importer_preparing_channels. 
[34mI20171013-14:20:45.218(11) [34mHipChat Importer ➔ debug HipChat is now at importer_preparing_users. 
[34mI20171013-14:20:45.245(11) [34mHipChat Importer ➔ debug HipChat is now at importer_preparing_messages. 
[34mI20171013-14:21:07.739(11) [35mHipChat Importer ➔ warn The loaded users count 59, the loaded channels 0, and the loaded messages 56035 
[34mI20171013-14:21:07.745(11) [34mHipChat Importer ➔ debug HipChat is now at importer_import_failed. 
@dasgarner
Copy link

dasgarner commented Jan 23, 2018

I also have this issue

I'm no expert but I think the const on this line is re-declaring tempRooms in a local scope, and therefore the tempRooms declared above is always empty.

Edit: and indeed it should be let tempRooms rather than const

@fnerdwq
Copy link

fnerdwq commented Apr 10, 2018

@dasgarner indeed the tempRooms definition as const seems to be the problem. It works for me fixing this w/o let and this from const to let.

@graywolf336
Copy link
Contributor

graywolf336 commented May 18, 2018

Sad that this has slipped under the radar :(

It's been broke for over a year due to the coffeescript to javascript conversion by @rodrigok https://github.com/RocketChat/Rocket.Chat/blame/8bee5761a78c83da7cdb52650daf3cd226906ace/packages/rocketchat-importer-hipchat/server.js

@frdmn frdmn added this to the 0.65.0 milestone May 24, 2018
@frdmn frdmn added this to Desirable in May/2018 via automation May 24, 2018
@frdmn frdmn moved this from Desirable to Backlog in May/2018 May 24, 2018
@theorenck theorenck modified the milestones: 0.65.0, 0.66.0 Jun 4, 2018
@theorenck theorenck removed this from Backlog in May/2018 Jun 4, 2018
@theorenck theorenck added this to Desireable in June/2018 via automation Jun 4, 2018
@theorenck theorenck moved this from Desireable to Backlog in June/2018 Jun 4, 2018
@Hudell Hudell self-assigned this Jun 13, 2018
June/2018 automation moved this from Backlog to Closed Jun 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
June/2018
  
Closed
Development

No branches or pull requests

8 participants