RDKEMW-13945: Fix L2 Issue on RFC Component by madhubabutt · Pull Request #182 · rdkcentral/rfc

madhubabutt · 2026-03-06T08:33:01Z

No description provided.

Copilot

Pull request overview

Enables the RFC WebPA functional test in the L2 test runner script to address the reported L2 gap for the RFC component.

Changes:

Uncomments/enables execution of test_rfc_webpa.py in the L2 test run.

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

Copilot · 2026-03-06T08:35:11Z

run_l2.sh

 pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_override_rfc_prop.json test/functional-tests/tests/test_rfc_override_rfc_prop.py

-#pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py
+pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py


The report filename rfc_rfc_webpa.json is inconsistent with the other report files in this script (which follow rfc_<test_name>.json). Consider renaming it to rfc_webpa.json (or another single-rfc_ prefix) to keep report naming consistent and avoid confusion/accidental mismatches in any report aggregation.

Suggested change

pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py

pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py

Copilot

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

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

Copilot · 2026-03-09T09:37:36Z

test/functional-tests/tests/test_rfc_webpa.py

 def test_WebPA_Set_ACC_Id():
    print("Starting parodus mock process")
-    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID","dataType":0,"value":"412370664406228514"}]}'
+    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"    TESTIMAGE_DEV.bin"}]}'


test_WebPA_Set_ACC_Id now sends a SET for Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload, while the paired GET test still queries ...RFC.Feature.AccountInfo.AccountID. As written, these tests no longer validate a consistent WebPA set/get flow and the test name is misleading; update the SET to target AccountID (as before) or rename/update the GET assertions to match the parameter being set.

Suggested change

payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":" TESTIMAGE_DEV.bin"}]}'

payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID","dataType":0,"value":"412370664406228514"}]}'

Copilot · 2026-03-09T09:37:37Z

test/functional-tests/tests/test_rfc_webpa.py

 def test_WebPA_Set_ACC_Id():
    print("Starting parodus mock process")
-    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID","dataType":0,"value":"412370664406228514"}]}'
+    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"    TESTIMAGE_DEV.bin"}]}'


The SET payload value contains leading whitespace ("value":" TESTIMAGE_DEV.bin"), which is likely to cause brittle behavior (exact-match comparisons, file lookup, or downstream parsing). If whitespace is not intentionally part of the value being tested, trim/remove it (or make the test explicitly assert that trimming behavior is handled).

Suggested change

payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":" TESTIMAGE_DEV.bin"}]}'

payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'

Copilot · 2026-03-09T09:37:37Z

run_l2.sh

-pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_override_rfc_prop.json test/functional-tests/tests/test_rfc_override_rfc_prop.py
-
-#pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py
+./usr/local/bin/parodus  -v


./usr/local/bin/parodus -v uses a relative path (from the repo working directory in CI) and will fail unless the script is run from /. This should be an absolute path (/usr/local/bin/parodus) to match the preceding ls -l /usr/local/bin/parodus and the test code.

Suggested change

./usr/local/bin/parodus -v

/usr/local/bin/parodus -v

Copilot

Pull request overview

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

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

Copilot · 2026-03-09T10:58:57Z

test/functional-tests/tests/test_rfc_webpa.py

 def test_WebPA_Set_ACC_Id():
    print("Starting parodus mock process")
-    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID","dataType":0,"value":"412370664406228514"}]}'
-    command = ["/usr/local/bin/parodus", payload]
+    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'
+    command = ["/tmp/parodus", payload]


test_WebPA_Set_ACC_Id no longer sets the AccountID parameter (it sets X_RDKCENTRAL-COM_FirmwareToDownload instead), but test_WebPA_Get_ACC_Id still asserts an AccountID value (412370664406228514) is returned/logged. As written, the GET test is no longer consistent/self-contained and is likely to fail depending on prior device state. Update the SET payload + expected value to match the GET assertion, or update the GET test/assertions (and test names) to validate the parameter you actually set here.

Copilot · 2026-03-09T10:58:57Z

test/functional-tests/tests/test_rfc_webpa.py

+    payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'
+    command = ["/tmp/parodus", payload]



The test now hard-codes the parodus binary path as /tmp/parodus, which makes it depend on external setup (e.g., run_l2.sh copying the binary first) and can break when this test is executed directly in environments where only /usr/local/bin/parodus exists. Consider resolving the binary via an environment variable with a default, or falling back to /usr/local/bin/parodus when /tmp/parodus is absent.

Copilot

Pull request overview

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

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

Copilot · 2026-03-09T11:18:24Z

run_l2.sh

 cp ./rfcMgr/gtest/mocks/tr181store.ini /opt/secure/RFC/tr181store.ini

-rbuscli set Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Control.ConfigSetTime uint32 1763118860
+ls -l   /usr/local/bin/parodus


ls -l /usr/local/bin/parodus is a debug-only step and doesn't contribute to setting up or running the tests. It adds noise to CI logs and will print an error if the file is missing (even though the script continues). Consider removing it or turning it into an explicit existence check that fails fast with a clear message.

Suggested change

ls -l /usr/local/bin/parodus

if [ ! -x /usr/local/bin/parodus ]; then

echo "Error: /usr/local/bin/parodus not found or not executable." >&2

exit 1

fi

Copilot · 2026-03-09T11:18:24Z

test/functional-tests/tests/test_rfc_webpa.py

 def test_WebPA_Get_ACC_Id():
    print("Starting parodus mock process")
    payload ='{"command":"GET","names":["Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID"]}'
-    command = ["/usr/local/bin/parodus", payload]
+    command = ["/tmp/parodus", payload]



Hard-coding the WebPA client path to /tmp/parodus makes this test dependent on external setup (e.g., run_l2.sh copying the binary). When running pytest directly, /tmp/parodus may not exist and the test will fail before exercising RFC/WebPA behavior. Consider using the canonical install location (or an env/configurable path) and/or have the test/fixture prepare the binary.

Copilot

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

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

Copilot · 2026-03-09T12:09:14Z

test/functional-tests/tests/test_rfc_webpa.py

@@ -36,7 +36,7 @@ def test_WebPA_Set_ACC_Id():
 def test_WebPA_Get_ACC_Id():
    print("Starting parodus mock process")
    payload ='{"command":"GET","names":["Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID"]}'
-    command = ["/usr/local/bin/parodus", payload]
+    command = ["/tmp/parodus", payload]



The parodus binary path is hard-coded as /tmp/parodus in multiple places. Since this is an execution dependency, consider centralizing it (e.g., a constant in rfc_test_helper.py or a fixture/env var) so future path changes don’t require editing multiple tests.

Copilot · 2026-03-09T12:09:15Z

.github/workflows/L2-tests.yml

+      - name: Enable core dump
+        run: ulimit -c unlimited
+


ulimit -c unlimited is executed on the GitHub runner, but the RFC build/tests run inside the native-platform container. This ulimit won’t affect processes inside the container, so it won’t enable core dumps where you need them. Set the ulimit on docker run (e.g., --ulimit core=-1) or run ulimit via docker exec in the same container/session that launches parodus.

Copilot · 2026-03-09T12:09:15Z

.github/workflows/L2-tests.yml

+
+      - name: Run test
+        run: |
+          /usr/local/bin/parodus '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'


The Run test step invokes /usr/local/bin/parodus directly on the GitHub runner, but earlier steps indicate parodus exists inside the native-platform container (and run_l2.sh copies it to /tmp/parodus inside that container). This step will not exercise the containerized environment and is likely to fail if the runner doesn’t have that binary. Run the command via docker exec native-platform ... (and use the same binary path you prepared).

Suggested change

/usr/local/bin/parodus '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'

docker exec native-platform /tmp/parodus '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'

Copilot · 2026-03-09T12:09:15Z

.github/workflows/L2-tests.yml

+      - name: Print stacktrace
+        if: failure()
+        run: |
+          core=$(ls core* 2>/dev/null | head -n1)
+          if [ -n "$core" ]; then
+            gdb -batch -ex "bt full" /tmp/parodus $core
+          fi


The stacktrace step looks for core* files on the GitHub runner and runs gdb ... /tmp/parodus $core, but /tmp/parodus is created inside the native-platform container (per run_l2.sh) and any core dump would also be inside that container’s filesystem. Additionally, this workflow doesn’t install gdb, so the step may fail even if a core exists. To make this work reliably, collect the core/binary from the container (e.g., docker cp) and either run gdb in the container or install gdb on the runner before invoking it.

Copilot · 2026-03-09T12:09:15Z

run_l2.sh

-pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_xconf_reboot.json test/functional-tests/tests/test_rfc_xconf_reboot.py
-
-pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_override_rfc_prop.json test/functional-tests/tests/test_rfc_override_rfc_prop.py
+cp /usr/local/bin/parodus  /tmp/parodus


Copying the parodus binary directly to /tmp/parodus introduces a classic symlink attack risk if this script runs with elevated privileges. An unprivileged user can create /tmp/parodus as a symlink to a sensitive root-owned file, causing cp to overwrite that target when the script runs, leading to privilege escalation or corruption of critical system files. Use a secure temporary path (e.g., via mktemp) and ensure the destination is not a pre-existing symlink in a world-writable directory.

Suggested change

cp /usr/local/bin/parodus /tmp/parodus

PARODUS_TMP="$(mktemp /tmp/parodus.XXXXXX)"

cp /usr/local/bin/parodus "$PARODUS_TMP"

echo "parodus binary copied to temporary path: $PARODUS_TMP"

Copilot

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (2)

test/functional-tests/tests/test_rfc_webpa.py:51

test_WebPA_Get_ACC_Id asserts the AccountID value 412370664406228514 is present in parodus logs, but this file no longer sets that parameter (the SET test now sets FirmwareToDownload). As-is, this test will be order-dependent or fail when run in isolation. Either restore the AccountID SET in this suite or adjust the GET/assertions to match what the SET test configures.

def test_WebPA_Get_ACC_Id():
    print("Starting parodus mock process")
    payload ='{"command":"GET","names":["Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID"]}'
    command = ["/tmp/parodus", payload]

    result = subprocess.run(command, capture_output=True, text=True)
    assert result.returncode == 0, f"Command failed with error: {result.stderr}"

    STATUS_CODE_MSG = '"statusCode":200'
    assert STATUS_CODE_MSG in grep_paroduslogs(STATUS_CODE_MSG)

    SUCCESS_STATUS_MSG = '"message":"Success"'
    assert SUCCESS_STATUS_MSG in grep_paroduslogs(SUCCESS_STATUS_MSG)

    ACC_ID_MSG = '"value":"412370664406228514"'
    assert ACC_ID_MSG in grep_paroduslogs(ACC_ID_MSG)

run_l2.sh:34

run_l2.sh no longer executes any of the L2 pytest suites (all invocations were removed), so the workflow will produce no JSON reports under $RESULT_DIR and may cause the result upload step to fail or silently skip coverage. Please restore the L2 test execution (or gate the debugging-only behavior behind a flag) so CI still runs the intended test set.

RESULT_DIR="/tmp/rfc_test_report"
mkdir -p "$RESULT_DIR"

cp ./rfc.properties /opt/rfc.properties
cp /opt/certs/client.pem /etc/ssl/certs/client.pem
cp ./rfcMgr/gtest/mocks/tr181store.ini /opt/secure/RFC/tr181store.ini

ls -l   /usr/local/bin/parodus

cp /usr/local/bin/parodus  /tmp/parodus

#pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py

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

Copilot · 2026-03-09T13:04:25Z

.github/workflows/L2-tests.yml

+          run: |
+            pwd
+            ls -l /usr/local/bin
+            file /usr/local/bin/parodus
+            ldd /usr/local/bin/parodus || true


The Debug parodus binary step has invalid YAML indentation: run: is indented under - name: instead of aligned with it. This will prevent the workflow from parsing. Fix the indentation so run is at the same level as name for that step.

Suggested change

run: |

pwd

ls -l /usr/local/bin

file /usr/local/bin/parodus

ldd /usr/local/bin/parodus || true

run: |

pwd

ls -l /usr/local/bin

file /usr/local/bin/parodus

ldd /usr/local/bin/parodus || true

Copilot

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

run_l2.sh:34

run_l2.sh no longer runs any of the L2 pytest suites (the entire block invoking multiple pytest --json-report ... commands was removed). As a result, the workflow step that calls sh run_l2.sh will stop producing L2 test results, which looks like an unintended functional regression. Reintroduce the test execution block and keep any parodus-copy/debug steps in addition to (not instead of) running the L2 tests.

ls -l   /usr/local/bin/parodus

cp /usr/local/bin/parodus  /tmp/parodus

#pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py

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

Copilot · 2026-03-09T13:12:09Z

.github/workflows/L2-tests.yml

+      - name: Enable core dump
+        run: ulimit -c unlimited
+
+      - name: Debug parodus binary
+        run: |
+          pwd
+          ls -l /usr/local/bin
+          file /usr/local/bin/parodus
+          ldd /usr/local/bin/parodus || true
+
+      - name: Run test
+        run: |
+          cd /usr/local/bin
+          ./parodus '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'
+


The new "Enable core dump", "Debug parodus binary", and "Run test" steps run on the GitHub Actions runner host, not inside the native-platform container where RFC/parodus is built/executed. This will likely fail (runner may not have /usr/local/bin/parodus) and ulimit -c unlimited in its own step won’t affect other steps or the container. Run these diagnostics via docker exec native-platform ... (and set ulimit in the same container-executed command where parodus runs).

madhubabutt requested a review from a team as a code owner March 6, 2026 08:33

Copilot AI review requested due to automatic review settings March 6, 2026 08:33

Copilot started reviewing on behalf of madhubabutt March 6, 2026 08:33 View session

Copilot AI reviewed Mar 6, 2026

View reviewed changes

madhubabutt force-pushed the topic/RDKEMW-13945 branch from 49394a7 to 379c655 Compare March 6, 2026 10:38

Copilot AI review requested due to automatic review settings March 9, 2026 09:32

madhubabutt force-pushed the topic/RDKEMW-13945 branch from 379c655 to 5a03df1 Compare March 9, 2026 09:32

Copilot started reviewing on behalf of madhubabutt March 9, 2026 09:33 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

madhubabutt force-pushed the topic/RDKEMW-13945 branch from 5a03df1 to fcfa636 Compare March 9, 2026 10:45

Copilot AI review requested due to automatic review settings March 9, 2026 10:53

madhubabutt force-pushed the topic/RDKEMW-13945 branch from fcfa636 to f525338 Compare March 9, 2026 10:53

Copilot started reviewing on behalf of madhubabutt March 9, 2026 10:54 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

madhubabutt force-pushed the topic/RDKEMW-13945 branch 2 times, most recently from bd8176f to fd92d6a Compare March 9, 2026 11:14

Copilot AI review requested due to automatic review settings March 9, 2026 11:14

Copilot started reviewing on behalf of madhubabutt March 9, 2026 11:14 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

madhubabutt force-pushed the topic/RDKEMW-13945 branch 2 times, most recently from 87283a8 to 7eff2c0 Compare March 9, 2026 12:04

Copilot AI review requested due to automatic review settings March 9, 2026 12:04

Copilot started reviewing on behalf of madhubabutt March 9, 2026 12:05 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

madhubabutt force-pushed the topic/RDKEMW-13945 branch from 7eff2c0 to 6dd49ca Compare March 9, 2026 12:52

Copilot AI review requested due to automatic review settings March 9, 2026 13:01

madhubabutt force-pushed the topic/RDKEMW-13945 branch from 6dd49ca to a4b7d8e Compare March 9, 2026 13:01

Copilot started reviewing on behalf of madhubabutt March 9, 2026 13:01 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

madhubabutt force-pushed the topic/RDKEMW-13945 branch from a4b7d8e to ffa092b Compare March 9, 2026 13:05

RDKEMW-13945: Fix L2 Issue on RFC Component

dda9df5

Copilot AI review requested due to automatic review settings March 9, 2026 13:07

madhubabutt force-pushed the topic/RDKEMW-13945 branch from ffa092b to dda9df5 Compare March 9, 2026 13:07

Copilot started reviewing on behalf of madhubabutt March 9, 2026 13:08 View session

Copilot AI reviewed Mar 9, 2026

View reviewed changes

	pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py
	pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rfc_webpa.json test/functional-tests/tests/test_rfc_webpa.py

	payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":" TESTIMAGE_DEV.bin"}]}'
	payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.AccountInfo.AccountID","dataType":0,"value":"412370664406228514"}]}'

		payload = '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'
		command = ["/tmp/parodus", payload]

-ls -l   /usr/local/bin/parodus
+if [ ! -x /usr/local/bin/parodus ]; then
+    echo "Error: /usr/local/bin/parodus not found or not executable." >&2
+    exit 1
+fi

	/usr/local/bin/parodus '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'
	docker exec native-platform /tmp/parodus '{"command":"SET","parameters":[{"name":"Device.DeviceInfo.X_RDKCENTRAL-COM_FirmwareToDownload","dataType":0,"value":"TESTIMAGE_DEV.bin"}]}'

-cp /usr/local/bin/parodus  /tmp/parodus
+PARODUS_TMP="$(mktemp /tmp/parodus.XXXXXX)"
+cp /usr/local/bin/parodus "$PARODUS_TMP"
+echo "parodus binary copied to temporary path: $PARODUS_TMP"

Conversation

madhubabutt commented Mar 6, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects