-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
While testing the agl-demo-control-panel, errors of the form:
Nov 28 23:03:29 qemux86-64 python3[307]: ERROR:asyncio:Exception in callback PollerCompletionQueue._handle_events(<_UnixSelecto...e debug=False>)()
Nov 28 23:03:29 qemux86-64 python3[307]: handle: <Handle PollerCompletionQueue._handle_events(<_UnixSelecto...e debug=False>)()>
Nov 28 23:03:29 qemux86-64 python3[307]: Traceback (most recent call last):
Nov 28 23:03:29 qemux86-64 python3[307]: File "/usr/lib/python3.10/asyncio/events.py", line 80, in _run
Nov 28 23:03:29 qemux86-64 python3[307]: self._context.run(self._callback, *self._args)
Nov 28 23:03:29 qemux86-64 python3[307]: File "src/python/grpcio/grpc/_cython/_cygrpc/aio/completion_queue.pyx.pxi", line 147, in grpc._cython.cygrpc.PollerCompletionQueue._handle_events
Nov 28 23:03:29 qemux86-64 python3[307]: BlockingIOError: [Errno 11] Resource temporarily unavailable
Nov 28 23:03:29 qemux86-64 python3[307]: ERROR:root:Error during gRPC subscription: ({'code': 16, 'reason': 'unauthenticated', 'message': 'Invalid auth token: DecodeError("InvalidToken")'}, [])
were seen when trying to connect to the remote databroker. After some digging, this error is from the gRPC-specific code that subscribes to the set of signals that are tracked, which is separate from the kuksa-client common API calls used to set signal values. From some code inspection, it looks like the VSSClient API expects the token file contents, not the token file path, and the code in agl-demo-control-panel needs to be fixed.