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

Issue with web site on some devices #55

Closed
CrazyRobMiles opened this issue Oct 24, 2019 · 22 comments
Closed

Issue with web site on some devices #55

CrazyRobMiles opened this issue Oct 24, 2019 · 22 comments

Comments

@CrazyRobMiles
Copy link
Contributor

The map seems to be locking up for some users. Works OK for me on Chrome but locks up with a greyed out display on IE and Safari.

image

@CrazyRobMiles
Copy link
Contributor Author

It looks like it might be this:
image
The message doesn't appear on a working load.

@CrazyRobMiles
Copy link
Contributor Author

Ha. Ignore that. Just done a reload on the working page and it worked fine, with that error. I've had a look at the code and it is just a sensible error message.

@CrazyRobMiles
Copy link
Contributor Author

Tried some different machines and it works OK on them. Maybe an issue with cookies and the migratin of the url to sensors

@bsimmo
Copy link
Member

bsimmo commented Oct 26, 2019

This happens on all of mine, different browser different devices.
theat little box is
tippy-tooltip
it does not go away and close itself.

Everything loads in the background, but it's not usable.

I think it happened with the most recent update (1.3 or the sensor header change)

@BNNorman
Copy link

Works ok on my amazon tablet with Silk browser. Though theres a significant lag between opening a chart and the graph appearing.

@sbrl
Copy link
Collaborator

sbrl commented Oct 27, 2019

Hey! That looks like the first-run tutorial isn't working correctly. The null cell polygons don't really any thing to do with that bit of the code.

Very strange. Which browsers is this in @CrazyRobMiles & @bsimmo? If it's an issue, we might just have to disable the first-run tutorial.

@CrazyRobMiles
Copy link
Contributor Author

I'm not sure if it is a browser thing. I think it is more likely that it uses a cookie to determine if it has displayed or not and gets stuck on devices where it hasn't been displayed. Could the change of url affected where it stores the cookie for the first run tutorial? (or am I just completely misunderstanding how it works?)

@CrazyRobMiles
Copy link
Contributor Author

The first run tutorial is a nice thing to have, but I think we can do without it if it is the cause of the problem.

@BNNorman
Copy link

BNNorman commented Oct 27, 2019

The cookie idea is easy to test. Perhaps ben could flush his out and retry?

@bsimmo
Copy link
Member

bsimmo commented Oct 27, 2019 via email

@BNNorman
Copy link

Hmm, i think you need to bring a failing device to the next meetup otherwise its a lot of guesswork.

@bsimmo
Copy link
Member

bsimmo commented Oct 27, 2019 via email

@CrazyRobMiles
Copy link
Contributor Author

CrazyRobMiles commented Oct 27, 2019 via email

@bsimmo
Copy link
Member

bsimmo commented Oct 29, 2019

Just looked at this on my PC again.
For now you can hit ESC * to bypass the failing tutorial* (the small rectangular box (Chrome/Edge)

For mobile (Android anyway) devices I would suggest not using it or showing it to anyone for now

(*as a side note, you may need to click in the little box and then press ESC)
(*assuming it is that)

@sbrl
Copy link
Collaborator

sbrl commented Oct 29, 2019

Whether the tutorial is launched or not is actually checked by using a localStorage key, not a cookie. This is done here:

https://github.com/ConnectedHumber/Air-Quality-Web/blob/dev/client_src/js/Tour.mjs#L141-L154

I could certainly put it behind a button. Let's try that.

@sbrl
Copy link
Collaborator

sbrl commented Oct 29, 2019

Fixed it. Turns out there was a change in the API in a recent update of Shepard.js, which is used for the tour. It should now be working on the beta version in ~10 minutes.

@sbrl
Copy link
Collaborator

sbrl commented Oct 29, 2019

There, it should be deployed now. Don't forget to reload without cache with Ctrl + Shift + R, and if you want the first-run wizard to appear again try a private browsing window.

If it works for everyone, then I'll release this to stable.

@BNNorman
Copy link

BNNorman commented Oct 30, 2019

beta works fine on my desktop (Windows 10) using Firefox.
However, the 'loading' circles take a long time to end and the charts take a long time to appear.

@bsimmo
Copy link
Member

bsimmo commented Oct 31, 2019

@adamjennison reports it's working for him
it works for me on Win10 Chrome, Edge(EdgeHTML) Edge(Chromium)
and all the mobile Android device I could test on.

Many thanks, could see any other show stoppers (other than the veroni shading area often picking up the wrong sensor value for the wrong area, but I think we have an issue for that, it doesn't make it unusable)

@sbrl
Copy link
Collaborator

sbrl commented Oct 31, 2019

Thanks for checking @BNNorman! Yeah, it is taking a while. It's because of the last_seen SQL query - it takes a long time on the dataset we've acquired lol.

Is there an index on readings.s_or_r? I think it might help

@bsimmo: Thanks. Yeah, I need to debug that.... again.

@sbrl sbrl closed this as completed in 10f136c Nov 2, 2019
@BNNorman
Copy link

BNNorman commented Nov 2, 2019

Yes there is an index on s_or_r. Last seen would be max(s_or_r).

@sbrl
Copy link
Collaborator

sbrl commented Nov 2, 2019

Yeah, that's what it uses, @BNNorman. Hrm, might have to rethink that one :-/

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

No branches or pull requests

4 participants