Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CloudCallServiceImpl - call methods setting requester.client.id to #client-id sends response to local device
See original GitHub issueI just tried using CloudCallServiceImpl to send CONF-V1 requests to a Kura device. It seems to me that there is a bug in that implementation.
On line 122 it sets the requester.client.id to the topic placeholder #client-id. This in turn is send to the remote Kura device which then replaces it with its own client-id when sending the response. Not the intended outcome. This prevents the response from ever being picked up by the sender - it subscribes to the correct topic beforehand (using the same placeholder on line 110.
Before looking into a fix for this - am I missing something here? The problem with fixing this is that the client-id isn’t available inside that implementation.
I’ve tested with manually providing the correct client-id on line 122 and that works properly.
Hints?
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I thought we were breaking the API in 3.0. If so, we should probably just remove it. If not, should fix the Service at is currently broken.
Closing as all the deprecated API will be removed at the same time