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

most, or all, searches of room content fail (with CORS-related errors) #5517

Closed
grahamperrin opened this issue Nov 5, 2017 · 4 comments
Closed
Labels
P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@grahamperrin
Copy link

I see leak-oriented #5373 and #5374 and more recent #4541 … I find a more general problem; searches no longer succeed.

(I can't recall when I last had a search result.)

@grahamperrin
Copy link
Author

Comparative test results

Android 6.0.1, Riot.im 0.7.03 (G-da8a7535b)

  1. sought mentioned in the Riot room
  2. sought GELI in #freebsd on IRC
  3. sought quantum in #firefox on moznet

Three of three searches succeeded.

https://riot.im/develop/ in SeaMonkey 2.49.1

  1. tab opened by a Control-Click on my bookmarks toolbar bookmark for https://riot.im/develop/
  2. whilst waiting for the usual page to load (asynchronous progress indicator, spinning occasionally), the light theme changes to dark (my preference) with a coincidental change of the URL to https://riot.im/develop/#/room/#designUX:matrix.org

– so there's some parallel with an adjacent bug report by me, although I can't tell whether it's coincidence or a direct relationship between the two:

This apparent redirect is novel, I'll test in a third browser to tell whether anything like it can be reproduced. (Too soon to raise a separate issue, or change the title of this one …)

@grahamperrin
Copy link
Author

Briefly:

  • a handful of rough notes at https://matrix.to/#/!DgvjtOljKujDBrxyHk:matrix.org/$15098836412065611Gngpt:matrix.org
  • on this FreeBSD-based desktop, I'm now temporarily using Chromium 61.0.3163.100 (Developer Build) (64-bit), not my preferred browser but I'm happy enough
  • I'm resisting the temptation to clear cookies etc. from the Firefox and SeaMonkey environments – just in case someone at Riot and/or Matrix has a keen interest in how things might have got in this state.
[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~% uname -v
FreeBSD 12.0-CURRENT #0 r320869: Mon Jul 10 13:57:55 UTC 2017     [email protected]:/usr/obj/usr/src/sys/GENERIC 
[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~% pkg info firefox | grep -i version
Version        : 56.0.2_6,1
[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~% pkg info seamonkey | grep Version
Version        : 2.49.1_4
[grahamperrin@momh167-gjp4-hpelitebook8570p-freebsd] ~% 

Comparative test results

Chromium

  1. sought mention in https://riot.im/app/#/room/#riot:matrix.orgfail
  2. sought mentioned in the same room – success
  3. sought GELI in https://riot.im/app/#/room/#freenode_#freebsd:matrix.org – success (~293 results)
  4. sought quantum in https://riot.im/app/#/room/#mozilla_#firefox:matrix.org – success (~238 results) and whilst awaiting those results in a background tab in (KDE Plasma 5) virtual desktop 4 of 12, I used virtual desktop 5 to launch Firefox 56.0.2, await load of extensions in the initial window, check for updates, decline the update to Diigo Toolbar, and begin appending a session with probably twelve-hundred-and-something tabs across thirteen windows (ignoring the first)
  5. sought Philips in https://riot.im/app/#/room/#freenode_#kde-freebsd:matrix.org and whilst awaiting results (and whilst Firefox was busy loading stuff), Control-Page Down in Chromium to put the 'searching' tab to the background, tappity tappity type and Control-Page Up and: success.

@grahamperrin
Copy link
Author

Chromium

– 2017-11-05 ~14:55

@lampholder lampholder added T-Defect P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Nov 23, 2017
@grahamperrin
Copy link
Author

The search that failed at #5517 (comment) above now succeeds,and the results appeared reasonably quickly.

Re: #5666 (comment) as we have closure there, so I'm closing here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants