Navigation does not plot a route
Description
Environment
Attachments
Activity
Jan-Simon Moeller February 25, 2021 at 3:50 PM
Not reproducible.
Edi Feschiyan February 25, 2021 at 10:16 AMEdited
it appears that the issue temporarily appeared only on my side for some weird reason.
I last tested m3ulcb and just powered it off. I just powered the board 2 days later and I cannot reproduce the issue.
No network issues were happening neither with wired nor wireless.
Jan-Simon Moeller February 24, 2021 at 8:52 PM
master/nightly: can't repro
10.0.2 vmdk downloaded: routing works - BUT: mouse clicks need to be 'slow' and 'long press' till the flag shows up
Scott Murray February 24, 2021 at 8:02 PM
I tested the navigation app with:
10.0.2 candidate builds from downloads.automotivelinux.org on Up^2 and RPi4
Locally built Jellyfish HEAD builds for qemux86-64 and h3ulcb-kf on Up^2 and H3+KF
Locally built Jellyfish 10.0.2 manifest build for h3ulcb-kf on H3+KF
and it worked as expected for me in all instances. I can force the "QML RouteModel: Index '0' out of range" error to happen if I start the navigation app, disconnect the Ethernet connection, then attempt to route, but from discussions with he had network connectivity during his testing. So at the moment, I've no good idea on what could be causing the issue he's seeing.
Scott Murray February 23, 2021 at 9:54 PM
Hmm, very strange. It's not obvious to me what in the 3.1.5 update could have broken it, and I believe it worked here. I will see if I can work out what's going on tomorrow.
When trying to plot a navigation route in the application, tap-holding on a spot shows destination marker but does not plot a route, neither location changes when the start button is pressed.
This is looks a like a regression to , however there are a few differences in the journal:
from description -
The warnings in qml/qrc files and argument conversion are missing, however trying to plot navigation results in the same behavior :
another example log - journal.minnow.txt.xz - from minnowboard on 07 September 2020 which has the Index '0' out of range error seems to be the last time it occurred before fixed it.
Affects all boards.