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

Hotchillee - Slack import making content disappear #20691

Closed
tom-gouldson opened this issue Feb 11, 2021 · 0 comments · Fixed by #20216
Closed

Hotchillee - Slack import making content disappear #20691

tom-gouldson opened this issue Feb 11, 2021 · 0 comments · Fixed by #20216

Comments

@tom-gouldson
Copy link

tom-gouldson commented Feb 11, 2021

Context
Hotchillee is looking to move its Digital cycling club communications from Slack to a Rocketchat based app. In doing so it hopes to maintain the user experience as much as possible so as not to confuse its user base while using Rocketchats white labelling capability to give it Hotchillee brand and feel. As part of this Hotchillee looks to retain all the historic chat from Slack to make it as seamless as possible for users transferring to the new platform (similar to when Facebook does a major UX overhaul - all the data remains but the look and feel is different and new features are added but it’s still familiar enough not to alienate users).

Description:

Some imported Slack data appears to be triggering a bug wherein content suddenly disappears when a user clicks 'Thread' anywhere in that channel. That is to say the content is still on Rocketchat (others users can see it) but once a User clicks ‘Thread’ the channel goes blank and can only be recovered through refreshing the screen in Browser or re-installing the Hotchillee App on mobile.

This was diagnosed as a Slack import issue through the following steps:

Imported the slack export to 17th Dec (the last import before the problems began). The import worked fine, and there were no issues with channels or threads with disappearing content.
Next we tried a full incremental import of slack data to Feb 1st. It complained of a duplicate record and failed to complete the import. That means incremental overlapping imports no longer work (see separate bug).
Then we rebuilt the install of rocket back to brand spanking new again and imported the full slack export to 1st Feb. It imported fine, but the content in threads disappearing is back.

Steps to reproduce:

  1. Go to https://community.hotchillee.cc/channel/general_chat
  2. Click on 'Thread' anywhere
  3. Content should have disappeared

Expected behavior:

The thread to appear in the side panel and the main content to remain in the main panel and stay there.

Actual behavior:

Content disappeared (see attached video).

Server Setup Information:

  • Version of Rocket.Chat Server: 3.11.0
  • Operating System:
  • Deployment Method: Docker on Kubernetes via Helm
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 12.18.4
  • MongoDB Version: 4.2.12
  • Apps Engine Version. 1.22.1

Will edit and add more shortly

Client Setup Information

  • Desktop App or Browser Version: Both. Browsers were Chrome and Safari
  • Operating System: Mac OS

Additional context

Not applicable

Relevant logs:

Javascript console error: db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401 TypeError: Cannot destructure property 'username' of 'e' as it is null.
at db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1814
at Array.filter ()
at db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1814
at String.replace ()
at replaceUsers (db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1814)
at r.parse (db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1814)
at m (db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1814)
at eval (/app/threads/client/components/ThreadComponent.tsx:1)
at Object.Ma [as useMemo] (db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401)
at r.useMemo (db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1377)
wf @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Ff.r.payload @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Oc @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
nf @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
ji @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Hi @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Ui @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Ai @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
(anonymous) @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
r.unstable_runWithPriority @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1419
sc @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
_c @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
dc @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Xi @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
r.unstable_runWithPriority @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1419
sc @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
Ki @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
(anonymous) @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1401
z @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1419
k.port1.onmessage @ db742d1d32bcad874d80b83e57e68ec8c9ebd1e2.js?meteor_js_resource=true:1419

Disappearing.content.in.thread.video.mov
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant