Rebase with Develop branch by yuvaramachandran-gurusamy · Pull Request #138 · rdkcentral/xdialserver

yuvaramachandran-gurusamy · 2025-03-07T18:24:28Z

No description provided.

RDKECMF-213 Add CODEOWNERS file

Signed-off-by: apatel859 <amit_patel5@comcast.com>

RDKEMW-254: libsoup3 support

DELIA-67407: Code syncup main to develop

Rebase with Develop Branch

…p_set_friendlyname Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

RDKTV-35185: Add sync between ssdp_http_server_callback and gdial_ssdp_set_friendlyname

rdkcmf-jenkins · 2025-03-07T19:56:18Z

Sanity tests for ['BCM 7216OTT Refboard VA'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/74436/

rdkcmf-jenkins · 2025-03-07T20:06:21Z

Sanity tests for ['BCM 7216OTT Refboard VA'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/74438/

rdkcmf-jenkins · 2025-03-07T20:06:43Z

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/74441/

rdkcmf-jenkins · 2025-03-07T20:26:12Z

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/74445/

Develop

Reason for change: Fix issues identified within xcast Test Procedure: Risks: low Priority: P1 Signed-off-by:Hayden Gfeller <Hayden_Gfeller@comcast.com>

…ialserver into feature/RDKEMW-2033

Reason for change: Implemented setManufacturerName and setModelName APIs for DIAL Server name configuration maintained the additional data url to specific app Test Procedure: DIAL should work Risks: None Priority: P1 Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

…4_Dial_Args_1 RDK-55044: Implement DIAL requirement to use on EU product

rdkcmf-jenkins · 2025-03-25T18:15:59Z

Sanity tests for ['BCM 7216OTT Refboard VA'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/76081/

rdkcmf-jenkins · 2025-03-25T18:35:58Z

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/76083/

Develop

RDKEMW-2033 : Coverity

rdkcmf-jenkins · 2025-04-01T16:24:57Z

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/76587/

rdkcmf-jenkins · 2025-04-01T16:24:59Z

Sanity tests for ['BCM 7216OTT Refboard VA'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/76586/

Reason for change: Added DISABLE_SECURITY_TOKEN Flag to disable the WPEFrameworkSecurity Token generation changes Test Procedure: please referred from the ticket Risks: Medium Signed-off-by: Thamim Razith <ThamimRazith_AbbasAli@comcast.com>

RDKEMW-2278: Removal of WPEFrameworkSecurity Agent Utility

rdkcmf-jenkins · 2025-04-22T21:16:29Z

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/78187/

rdkcmf-jenkins · 2025-04-22T21:16:59Z

Sanity tests for ['BCM 7216OTT Refboard VA'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/78190/

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

…129_Coverity RDKEMW-4129: Prepare native build environment

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

…129_CoverityTest RDKEMW-4129: Test

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

…alserver into topic/RDKEMW-4129_CoverityTest Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

…129_CoverityTest RDKEMW-4129: Prepare native build environment for Coverity

Signed-off-by: apatel859 <amit_patel5@comcast.com>

RDKEMW-4129: Prepare native build environment for Coverity

rdkcmf-jenkins · 2025-06-09T19:18:06Z

Sanity tests for ['RPI4 IPSTB'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/81787/

RDKEMW-2854 : Fix the double free issue on call to onApplicationStateChanged api

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

* RDKEMW-6891: Coverity errors fix for xdial * Update gdial.cpp Fixed review comments

* RDKEMW-9964: Removing onStopped GDial notification handling Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com> * RDKEMW-9964: Fixed coverity issues Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com> * RDKEMW-9964: Fixed coverity issues Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com> * RDKEMW-9964: Fixed coverity issues Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com> --------- Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

…s issues in xdial (#182) * RDKEMW-11024 - Using copilot identify and fix the static code analysis issues in xdial Reason for Change: Resolving the static code issues scanned by copilot Test Procedure: Compiled and Verified Risks: Low Priority: P1 version: minor Signed-off-by: smohap466 <srinibas_mohapatra@comcast.com> --------- Signed-off-by: smohap466 <srinibas_mohapatra@comcast.com> Co-authored-by: smohap466 <srinibas_mohapatra@comcast.com> Co-authored-by: dkumar798 <dinesh_kumar2@comcast.com>

github-actions · 2025-12-05T01:57:16Z

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

6 out of 7 committers have signed the CLA.
✅ (scthunderbolt)[https://github.com/scthunderbolt]
✅ (sbarre01)[https://github.com/sbarre01]
✅ (yuvaramachandran-gurusamy)[https://github.com/yuvaramachandran-gurusamy]
✅ (hgfell683)[https://github.com/hgfell683]
✅ (mukesh972)[https://github.com/mukesh972]
✅ (agampa263)[https://github.com/agampa263]
❌ @srinibas15
_{You can retrigger this bot by commenting recheck in this Pull Request.}_{Posted by the CLA Assistant Lite bot.}

* RDKEMW-12059: Fix Coverity identified issues

* RDKEMW-12555 : Fix coveirty workflow scan in xdialserver repo Reason for Change: Fix coveirty scan workflow failure in xdialserver repo Test Procedure: Verify coveirty workflow Risks: Low Priority: P1 version: minor Signed-off-by:AkshayKumar_Gampa AkshayKumar_Gampa@comcast.com * RDKEMW-12555 : Fix coveirty workflow scan in xdialserver repo Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This pull request contains a rebase from the develop branch that introduces significant new features and improvements to the xdialserver component, including manufacturer/model name configuration support, UUID-based app routing, security token handling improvements, and thread safety enhancements.

Changes:

Added manufacturer and model name dynamic configuration support with callback mechanisms
Implemented UUID-based application routing per boot cycle for improved security
Enhanced thread safety with mutex protection for SSDP server operations
Added security token disable option and libsoup-3.0 support in build system

Reviewed changes

Copilot reviewed 32 out of 32 changed files in this pull request and generated 14 comments.

Show a summary per file

File	Description
stubs/securityagent/SecurityTokenUtil.*	New stub implementation for security token retrieval
stubs/iarm_stubs.cpp	New IARM bus stub implementations for testing
server/plat/gdialappcache.*	Added null pointer initialization and move semantics improvements
server/plat/gdial_app_registry.c	Implemented UUID generation for application registry per boot
server/plat/gdial.*	Major refactoring adding manufacturer/model name callbacks and security token handling
server/plat/gdial-plat-.	Platform layer updates for new manufacturer/model name features
server/plat/gdial-ssdp.c	Added mutex protection and dynamic manufacturer/model name support
server/plat/gdial-rest.c	Implemented UUID-based application routing and path parsing changes
server/include/*.h	Interface updates for new callback types and function signatures
server/gdialservice.*	Service layer implementation of manufacturer/model name configuration
server/gdialserver_ut.cpp	Unit test updates for interface changes
server/plat/CMakeLists.txt	Added DISABLE_SECURITY_TOKEN build option and libsoup-3.0 support
.github/workflows/native_full_build.yml	New CI/CD workflow for native builds
build_dependencies.sh	Build script for setting up dependencies
cov_build.sh	Coverage build script
.github/CODEOWNERS	Code ownership configuration

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-20T16:25:10Z

stubs/securityagent/SecurityTokenUtil.cpp

+		if(!memcpy(buffer,payload.c_str(),len))
+			return -1;
+		return 0;


The memcpy return value check is incorrect. memcpy always returns the destination pointer (buffer), which will be non-null if the buffer parameter is valid. This check will always be false. Additionally, the function should return the length of the token on success (the actual length copied), not 0. Returning 0 violates the documented post-condition that "return value 0 should not occur".

Copilot · 2026-01-20T16:25:10Z

server/plat/gdial.cpp

+         if(ret>0)
         {
-           controllerRemoteObject = new JSONRPC::LinkType<Core::JSON::IElement>(std::string());
-         } else {
-           string sToken = (char*)buffer;
-           string query = "token=" + sToken;
-           GDIAL_LOGINFO("Security token = %s ",query.c_str());
-           controllerRemoteObject = new JSONRPC::LinkType<Core::JSON::IElement>(std::string(), false, query);
+           sToken = (char*)buffer;
+           query = "token=" + sToken;
+           GDIAL_LOGINFO("Security token[%s] ",query.c_str());
         }


The security token logic has been inverted incorrectly. The condition now checks if ret > 0 (success) when it should check if ret < 0 (failure) based on the GetSecurityToken API contract. According to the SecurityTokenUtil.h documentation, the return value should be less than 0 on failure and greater than 0 on success. The original check for ret < 0 was correct for detecting failures.

Copilot · 2026-01-20T16:25:11Z

server/gdial-rest.c

  g_free(remote_address_str);
  GDialRestServer *gdial_rest_server = (GDIAL_REST_SERVER(user_data));
-  gchar **elements = g_strsplit(&path[1], "/", 4);
+  gchar **elements = g_strsplit(&path[1], "/", 3);


The split count has been changed from 4 to 3, but this may break existing functionality. The code previously handled 4 path components and now only handles 3. This change affects how the path elements are parsed and indexed in the subsequent logic (lines 719-737), where indices have been shifted. This needs careful verification that all path parsing scenarios are still handled correctly.

Suggested change

gchar **elements = g_strsplit(&path[1], "/", 3);

gchar **elements = g_strsplit(&path[1], "/", 0);

Copilot · 2026-01-20T16:25:11Z

server/gdial-rest.c

  }
  else {
    g_object_unref(app);
+    // FIX(Copilot): Set app to NULL after unref to prevent use-after-free


The comment "FIX(Copilot): Set app to NULL after unref to prevent use-after-free" should be removed before merging. Such development-process comments don't belong in production code. The actual code change (setting app = NULL) is good practice, but the comment format is inappropriate.

Suggested change

// FIX(Copilot): Set app to NULL after unref to prevent use-after-free

Copilot · 2026-01-20T16:25:11Z

server/gdial-rest.c

-          g_printerr("Warn: app_name too long\r\n");
+    if (j == 0) {
+        ret = g_strlcpy(base, elements[i], sizeof(base));
+	if (ret >= sizeof(base)) {


Case-inconsistent indentation with tab character. Line 721 uses a tab character while surrounding code uses spaces, creating inconsistent formatting.

Suggested change

if (ret >= sizeof(base)) {

if (ret >= sizeof(base)) {

Copilot · 2026-01-20T16:25:13Z

server/plat/CMakeLists.txt

 add_library(gdial-plat SHARED ${GDIAL_PLAT_LIB_SOURCE_FILES})
-target_link_Libraries(gdial-plat PRIVATE ${GLIB_LIBRARIES} ${GOBJECT_LIBRARIES} -lpthread -lWPEFrameworkCore -lWPEFrameworkDefinitions -lWPEFrameworkCOM -lWPEFrameworkPlugins -lWPEFrameworkSecurityUtil -lIARMBus)
+if(DISABLE_SECURITY_TOKEN)
+  target_link_Libraries(gdial-plat PRIVATE ${GLIB_LIBRARIES} ${GOBJECT_LIBRARIES} -lpthread -lWPEFrameworkCore -lWPEFrameworkDefinitions -lWPEFrameworkCOM -lWPEFrameworkPlugins -lIARMBus -luuid)


Incorrect case sensitivity in CMake function names. Line 78 uses 'target_link_Libraries' (capital L) while line 81 uses 'target_link_libraries' (lowercase l). CMake function names are case-insensitive, but this inconsistency indicates a typo. For consistency with CMake conventions and the rest of the file, both should use lowercase 'target_link_libraries'.

Suggested change

target_link_Libraries(gdial-plat PRIVATE ${GLIB_LIBRARIES} ${GOBJECT_LIBRARIES} -lpthread -lWPEFrameworkCore -lWPEFrameworkDefinitions -lWPEFrameworkCOM -lWPEFrameworkPlugins -lIARMBus -luuid)

target_link_libraries(gdial-plat PRIVATE ${GLIB_LIBRARIES} ${GOBJECT_LIBRARIES} -lpthread -lWPEFrameworkCore -lWPEFrameworkDefinitions -lWPEFrameworkCOM -lWPEFrameworkPlugins -lIARMBus -luuid)

Copilot · 2026-01-20T16:25:13Z

stubs/securityagent/SecurityTokenUtil.cpp

+	 *
+	 * Parameters
+	 *  maxLength   - holds the maximum uint8_t length of the buffer
+	 *  Id          - Buffer to hold the token.


The documentation comment for the 'buffer' parameter is inconsistent between the header and implementation files. The header file states "Buffer to hold the token" while the implementation incorrectly states "Id - Buffer to hold the token". The parameter name should be 'buffer', not 'Id'.

Copilot · 2026-01-20T16:25:14Z

server/plat/gdial.cpp

+    GDIAL_LOGTRACE("Entering ...");
+    if ((nullptr == GDialObjHandle)||(nullptr == model))
+    {
+        GDIAL_LOGERROR("NULL GDialObjHandle[%p] manufacturer[%p]",GDialObjHandle,model);


The parameter name in the error log message is incorrect. The function parameter is named 'model' but the error message refers to it as 'manufacturer'. This should be 'model' to match the parameter name and avoid confusion during debugging.

Suggested change

GDIAL_LOGERROR("NULL GDialObjHandle[%p] manufacturer[%p]",GDialObjHandle,model);

GDIAL_LOGERROR("NULL GDialObjHandle[%p] model[%p]", GDialObjHandle, model);

Copilot · 2026-01-20T16:25:14Z

server/plat/gdial.hpp

 void gdial_register_friendlyname_cb(gdial_friendlyname_cb cb);
 void gdial_register_registerapps_cb(gdial_registerapps_cb cb);
+void gdial_register_manufacturername_cb(gdial_manufacturername_cb cb);
+void gdial_register_modelname_cb(gdial_manufacturername_cb cb);


The callback typedef 'gdial_modelname_cb' is defined to use 'gdial_manufacturername_cb' type instead of its own distinct type. While they may have the same signature, this creates confusion and should be properly defined as its own typedef for clarity and future maintainability.

Suggested change

void gdial_register_modelname_cb(gdial_manufacturername_cb cb);

void gdial_register_modelname_cb(gdial_modelname_cb cb);

Copilot · 2026-01-20T16:25:14Z

server/gdial-ssdp.c

+    else
+    {
+        GDIAL_LOGERROR("Failed to allocate memory for response_headers");
+        soup_message_set_status(msg, SOUP_STATUS_INTERNAL_SERVER_ERROR);


Potential deadlock in error path. If application_url_str allocation fails (line 146), the function sets an error status but the mutex acquired at line 93 is not released before returning. This will cause a deadlock on the next call to this function.

Suggested change

soup_message_set_status(msg, SOUP_STATUS_INTERNAL_SERVER_ERROR);

soup_message_set_status(msg, SOUP_STATUS_INTERNAL_SERVER_ERROR);

pthread_mutex_unlock(&ssdpServerEventSync);

return;

scthunderbolt and others added 8 commits December 17, 2024 15:48

RDKECMF-213 Add CODEOWNERS file

65a7559

Merge pull request #125 from rdkcentral/feature/test-workflows

f710c87

RDKECMF-213 Add CODEOWNERS file

RDKEMW-254: libsoup3 support

8efac8e

Signed-off-by: apatel859 <amit_patel5@comcast.com>

Merge pull request #128 from rdkcentral/RDKEMW-254-xdial-libsoup24

fda6ec5

RDKEMW-254: libsoup3 support

Merge pull request #132 from rdkcentral/main

d16879c

DELIA-67407: Code syncup main to develop

Merge pull request #2 from rdkcentral/develop

33ed34b

Rebase with Develop Branch

RDKTV-35185: Add sync between ssdp_http_server_callback and gdial_ssd…

55650a2

…p_set_friendlyname Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Merge pull request #139 from yuvaramachandran-gurusamy/develop

f6c6d7d

RDKTV-35185: Add sync between ssdp_http_server_callback and gdial_ssdp_set_friendlyname

hgfell683 and others added 6 commits March 17, 2025 13:10

Merge pull request #1 from rdkcentral/develop

42da7af

Develop

RDKEMW-2033: Fix coverity related issue

84b8951

Reason for change: Fix issues identified within xcast Test Procedure: Risks: low Priority: P1 Signed-off-by:Hayden Gfeller <Hayden_Gfeller@comcast.com>

Merge branch 'feature/RDKEMW-2033' of https://github.com/hgfell683/xd…

36f386d

…ialserver into feature/RDKEMW-2033

RDK-56672: Fix parsing issue while restrict addtionalData url per app

a503f9e

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Merge pull request #144 from yuvaramachandran-gurusamy/topic/RDK-5504…

974beb6

…4_Dial_Args_1 RDK-55044: Implement DIAL requirement to use on EU product

hgfell683 and others added 2 commits March 26, 2025 12:54

Merge pull request #2 from rdkcentral/develop

4a4ea54

Develop

Merge pull request #141 from hgfell683/feature/RDKEMW-2033

a52d864

RDKEMW-2033 : Coverity

tabbas651 and others added 2 commits April 14, 2025 15:25

Merge pull request #148 from tabbas651/develop

8a97f28

RDKEMW-2278: Removal of WPEFrameworkSecurity Agent Utility

yuvaramachandran-gurusamy and others added 2 commits June 5, 2025 18:44

RDKEMW-4129: Prepare native build environment

81f4b89

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Merge pull request #151 from yuvaramachandran-gurusamy/topic/RDKEMW-4…

024882a

…129_Coverity RDKEMW-4129: Prepare native build environment

yuvaramachandran-gurusamy and others added 7 commits June 5, 2025 23:11

RDKEMW-4129: Test

6750eba

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Merge pull request #152 from yuvaramachandran-gurusamy/topic/RDKEMW-4…

82a6e05

…129_CoverityTest RDKEMW-4129: Test

RDKEMW-4129: Prepare native build script

83a1518

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Merge branch 'topic/RDKEMW-4129' of https://github.com/rdkcentral/xdi…

a1da8a4

…alserver into topic/RDKEMW-4129_CoverityTest Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

Merge pull request #156 from yuvaramachandran-gurusamy/topic/RDKEMW-4…

33b4866

…129_CoverityTest RDKEMW-4129: Prepare native build environment for Coverity

remmove duplicates from build_xxx script

c66ef14

Signed-off-by: apatel859 <amit_patel5@comcast.com>

Merge pull request #157 from rdkcentral/topic/RDKEMW-4129-2

8cb0f37

RDKEMW-4129: Prepare native build environment for Coverity

ssitar583 and others added 5 commits June 26, 2025 11:19

Update gdial.cpp

7302ede

Merge pull request #161 from ssitar583/develop

25a6735

RDKEMW-2854 : Fix the double free issue on call to onApplicationStateChanged api

RDKEMW-5927: Crash fix during soup_uri_to_string API call (#163)

3202ca6

Signed-off-by: yuvaramachandran_gurusamy <yuvaramachandran_gurusamy@comcast.com>

RDKEMW-6891:Coverity errors fix for xdial (#166)

206d137

* RDKEMW-6891: Coverity errors fix for xdial * Update gdial.cpp Fixed review comments

apatel859 requested a review from a team as a code owner November 12, 2025 01:01

dkumar798 and others added 2 commits January 8, 2026 12:35

RDKEMW-12059: Fix Coverity identified issues (#183)

29f6789

* RDKEMW-12059: Fix Coverity identified issues

Copilot AI review requested due to automatic review settings January 20, 2026 16:21

Copilot started reviewing on behalf of apatel859 January 20, 2026 16:21 View session

Copilot AI reviewed Jan 20, 2026

View reviewed changes

	gchar **elements = g_strsplit(&path[1], "/", 3);
	gchar **elements = g_strsplit(&path[1], "/", 0);

	target_link_Libraries(gdial-plat PRIVATE ${GLIB_LIBRARIES} ${GOBJECT_LIBRARIES} -lpthread -lWPEFrameworkCore -lWPEFrameworkDefinitions -lWPEFrameworkCOM -lWPEFrameworkPlugins -lIARMBus -luuid)
	target_link_libraries(gdial-plat PRIVATE ${GLIB_LIBRARIES} ${GOBJECT_LIBRARIES} -lpthread -lWPEFrameworkCore -lWPEFrameworkDefinitions -lWPEFrameworkCOM -lWPEFrameworkPlugins -lIARMBus -luuid)

	GDIAL_LOGERROR("NULL GDialObjHandle[%p] manufacturer[%p]",GDialObjHandle,model);
	GDIAL_LOGERROR("NULL GDialObjHandle[%p] model[%p]", GDialObjHandle, model);

	void gdial_register_modelname_cb(gdial_manufacturername_cb cb);
	void gdial_register_modelname_cb(gdial_modelname_cb cb);

Conversation

yuvaramachandran-gurusamy commented Mar 7, 2025

Uh oh!

rdkcmf-jenkins commented Mar 7, 2025

Uh oh!

rdkcmf-jenkins commented Mar 7, 2025

Uh oh!

rdkcmf-jenkins commented Mar 7, 2025

Uh oh!

rdkcmf-jenkins commented Mar 7, 2025

Uh oh!

rdkcmf-jenkins commented Mar 25, 2025

Uh oh!

rdkcmf-jenkins commented Mar 25, 2025

Uh oh!

rdkcmf-jenkins commented Apr 1, 2025

Uh oh!

rdkcmf-jenkins commented Apr 1, 2025

Uh oh!

rdkcmf-jenkins commented Apr 22, 2025

Uh oh!

rdkcmf-jenkins commented Apr 22, 2025

Uh oh!

rdkcmf-jenkins commented Jun 9, 2025

Uh oh!

github-actions bot commented Dec 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants

github-actions bot commented Dec 5, 2025 •

edited

Loading