Skip to content

Fix misleading "curl init failed" error messages in WiFi EndPoint JSON-RPC calls#396

Draft
Copilot wants to merge 2 commits intotopic/RDKEMW-14755from
copilot/sub-pr-393-another-one
Draft

Fix misleading "curl init failed" error messages in WiFi EndPoint JSON-RPC calls#396
Copilot wants to merge 2 commits intotopic/RDKEMW-14755from
copilot/sub-pr-393-another-one

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 11, 2026

The else branches following getJsonRPCData() calls in refreshCache() logged "curl init failed", which is inaccurate — those branches fire on any empty response, not just curl initialization failures.

Changes

  • Device_WiFi_EndPoint.cpp: Replaced all three instances of "curl init failed" with "JSON-RPC call failed or returned empty response" in the else branches that handle empty getJsonRPCData() return values.
// Before
RDK_LOG(RDK_LOG_ERROR, LOG_TR69HOSTIF, "%s: curl init failed\n", __FUNCTION__);

// After
RDK_LOG(RDK_LOG_ERROR, LOG_TR69HOSTIF, "%s: JSON-RPC call failed or returned empty response\n", __FUNCTION__);

Affected call sites: GetWiFiSignalStrength, GetConnectedSSID, and the preceding RPC call in refreshCache().


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

…int.cpp

Co-authored-by: Vismalskumar0 <188226757+Vismalskumar0@users.noreply.github.com>
Copilot AI changed the title [WIP] Address feedback on crash issue checks from PR review Fix misleading "curl init failed" error messages in WiFi EndPoint JSON-RPC calls Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants