-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
InfiniteLoader doesn't play nice with Vue keep-alive #394
Labels
bug
Something isn't working
Comments
ivelin
added a commit
to BKristenssonAlfsson/ambianic-ui
that referenced
this issue
Jun 2, 2020
it turns out infiniteloader does not play nive with vue keep-alive see issue ambianic#394 for details
Related to an open issue in the infiniteloader repo: |
github-actions bot
pushed a commit
that referenced
this issue
Jun 2, 2020
# [2.4.0](v2.3.3...v2.4.0) (2020-06-02) ### Bug Fixes * Added E2E test ([de1d8e3](de1d8e3)) * Bug in disconnecting / connecting ([c4d27a0](c4d27a0)) * Bug removed ([34c0c6e](34c0c6e)) * Changed disconnection stream ([f457ab4](f457ab4)) * changed text to be more specific ([2674ca7](2674ca7)) * choose edge connection clean up ([d0b563b](d0b563b)) * cosmetic UI changes in settings page ([4596d29](4596d29)) * Fixed merge conflicts ([87907df](87907df)) * fixed tests so timeout was correct ([f616f66](f616f66)) * mapstate to avoid error ([9608cbb](9608cbb)) * merge branch 'master' of https://github.com/ambianic/ambianic-ui into remote-access ([66883b3](66883b3)) * merge branch 'remote-access' of https://github.com/BKristenssonAlfsson/ambianic-ui into remote-access ([ac4c957](ac4c957)) * Redirect to edge connect if connected ([16b1878](16b1878)) * remote pairing code cleanup ([e095212](e095212)) * remove vue keep-alive around timeline vue ([1bde1b1](1bde1b1)), closes [#394](#394) * Removed unused variable ([43c03ec](43c03ec)) * Setting state to false ([d4a8914](d4a8914)) * structure grid system ([cbecd0b](cbecd0b)) * vuetify warnings and initilization of app ([6f3545d](6f3545d)) ### Features * Remote connection ([1a89b66](1a89b66)) * remote first time connectivity ([538a2d1](538a2d1)) * remote first time connectivity ([d038f27](d038f27)) * remote network pairing with ambianic edge ([7c297b1](7c297b1)) * Remote-access changes ([4c6b58a](4c6b58a))
I am having thoughts about the dynamic importing for the timeline component,.. my thoughts might be wrong, so I will try a small test and see... |
It is normal to take 5-10 seconds, because of the way aiortc implements
ICE. Until it supports ICE trickle, it will be that way. With ICE trickle,
I've seen connection times to drop to 1-2 seconds.
If it takes more than 10 seconds, that usually means one of the ICE servers
(STUN or TURN) is down, which is also a related aiortc issue. Instead of
using fallback servers independently, it fails if any of these servers
fail. Also an open issue with aiortc
<aiortc/aioice#4>.
…On Thu, Jun 4, 2020 at 9:11 AM Nasr Galal ***@***.***> wrote:
looks like it is taking long to connect
[image: image]
<https://user-images.githubusercontent.com/24525973/83767419-ed43fc80-a67d-11ea-9a93-05c7e3b4552f.png>
I think it might be better to test it on a good internet connection (I
don't have this option yet 😆 )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#394 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARBUFK36N6MIGAC5HRQHB3RU6TR3ANCNFSM4NQ5DJQA>
.
|
fixed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In review of PR #347 we noticed that when the Ambianic Edge Peer ID changes on the Settings page, that causes a Vue callback into infiniteloader which tries to reference its DOM parent. However since the inifiniteloader is on the timeline page, which is not rendered while the user is on the settings page, there is no DOM parent that infiniteloader can reference at the time.
When we remove the keep-alive wrap around the timeline page, the infiniteloader callback error does not occur.
See exception details below:
The text was updated successfully, but these errors were encountered: