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

Addon prevents https://chat.utwente.io from loading #216

Open
14mRh4X0r opened this issue Mar 27, 2018 · 5 comments
Open

Addon prevents https://chat.utwente.io from loading #216

14mRh4X0r opened this issue Mar 27, 2018 · 5 comments
Labels
fixed-in-rewrite fixed in 2.x (not part of this repo)

Comments

@14mRh4X0r
Copy link

When LanguageTool is loaded, https://chat.utwente.io (the Riot.im web client) fails loading with the following message:

Unhandled rejection value@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:16:13239
value@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:16:11185
componentWillMount@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:129:21424
performInitialMount@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:161:6330
mountComponent@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:161:5495
mountComponent@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:17:6163
performInitialMount@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:161:6612
mountComponent@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:161:5495
mountComponent@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:17:6163
a@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:72:13435
perform@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:36:10936
s@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:72:13656
perform@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:36:10936
batchedUpdates@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:162:157
i@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:14:3727
_renderNewRootComponent@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:72:14929
_renderSubtreeIntoContainer@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:72:15926
render@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:72:16053
e/<@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:1:4786
r@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:85:25587
c/<@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:85:26634
s/</e[t]@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:85:25763
o@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:1:21015
e.exports/l.prototype._promiseFulfilled@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:38:18976
e.exports/i.prototype._settlePromise@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:39:8231
e.exports/i.prototype._settlePromise0@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:39:8827
e.exports/i.prototype._settlePromises@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:39:10157
r.prototype._drainQueue@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:37:25604
r.prototype._drainQueues@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:37:25662
r/this.drainQueues@https://chat.utwente.io/bundles/84814748c8403ed7c1ae/bundle.js:37:23819

Interestingly enough, https://riot.im/app does load up properly.

@danielnaber
Copy link
Member

Thanks for the report. As a workaround, disabling the add-on for this domain should help. You can do that in the add-on settings.

@14mRh4X0r
Copy link
Author

Thanks, I wasn't aware of that feature.
For completeness' sake, the site runs https://github.com/vector-im/riot-web at tag v0.14.0-rc.4, using the tarball attached to the release.

@silvio
Copy link

silvio commented Apr 4, 2018

I search since a month for the cause of this problem. Thanks @14mRh4X0r for finding the root cause.

I have checked this page and tried several versions. With 1.0.13 the problem doesn't happen, with 1.0.28 the problem occurs.

@danielnaber
Copy link
Member

With 1.0.13 the problem doesn't happen, with 1.0.28 the problem occurs.

Can you narrow that down further?

@silvio
Copy link

silvio commented Apr 5, 2018

Hi @danielnaber, I was a bit not precise enough and maybe my problem isn't related to this problem. I was happy to find a solution for my problem.

I have an own riot-web docker container which load the page on all versions, but with being of 1.0.28 I could not send messages anymore. Switching of channels was possible but after that the area where I put my text is gone and was never seen.

I think, it's better to open an own bug for my problem...

@danielnaber danielnaber added the fixed-in-rewrite fixed in 2.x (not part of this repo) label Oct 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed-in-rewrite fixed in 2.x (not part of this repo)
Projects
None yet
Development

No branches or pull requests

3 participants