Closed bkeryan closed 1 year ago
We are seeing the same bug in the ADAS offering. We are not doing anything with ML but if we create a client on RT that connects to the server (also on RT) we get this printed to the screen. The client and server still seem to function correctly.
@ni-sujain Is there a planned next build/release that will include this fix?
FYI @gaoruhao
@twaltersp We will be doing a release for oneof datatype support in some days. This fix might come along with that release
Bug Report
If you build a measurement service into an EXE and statically register it with the MeasurementLink discovery service, it logs "ERROR: THIS POINTER IS NOT REGISTERED".
This error comes from https://github.com/ni/grpc-labview/blob/master/src/pointer_manager.h
It is looking up the client context from
contextId
. This parameter is optional, so leaving it unwired should not log errors.Repro or Code Sample
Build MeasurementLink example measurements into EXEs. Copy the build output to
C:\ProgramData\National Instruments\MeasurementLink\Services
Run the measures in InstrumentStudio. Look atC:\ProgramData\National Instruments\MeasurementLink\Logs\DiscoveryService.txt
Expected Behavior
Does not log unexpected errors.
Current Behavior
Logs unexpected errors:
Context
Testing a new example MeasurementLink service
Your Environment
ni-measurement-service
version: 1.0.1grpc-labview
version: 1.0.0.1AB#2427675