RFmx 2026 Q1 API code generation

[RahulBenaka]

What does this Pull Request accomplish?

Updates niRFmxBluetooth in grpc-device-scrapigen to 26.0.0
Updates niRFmxNR in grpc-device-scrapigen to 26.0.0
Updates niRFmxWlan in grpc-device-scrapigen to 26.0.0
Updates the gRPC Scrapigen Device Code for Bluetooth ModAcc attributes and enums
Updates the gRPC Scrapigen Device Code for NR OBW attribute and enum
Updates the gRPC Scrapigen Device Code for WLAN Ofdm attributes, enums and APIs and OfdmModAcc attributes and enums.

Why should this Pull Request be merged?

Updated to match the upcoming release of niRFmxBluetooth to 26.0.0
Updated to match the upcoming release of niRFmxNR 26.0.0
Updated to match the upcoming release of niRFmxWlan 26.0.0

What testing has been done?

Manually inspected generated files.
Copied files from grpc-device-scrapigen/out/rfmxbluetooth/export/ to grpc-device/source/codegen/metadata/nirfmxbluetooth/ and built grpc-device successfully.
Manually inspected nirfmxbluetooth.proto file.
Copied files from grpc-device-scrapigen/out/rfmxnr/export/ to grpc-device/source/codegen/metadata/nirfmxnr/ and built grpc-device successfully.
Manually inspected nirfmxnr.proto file.
Copied files from grpc-device-scrapigen/out/rfmxwlan/export/ to grpc-device/source/codegen/metadata/nirfmxwlan/ and built grpc-device successfully.
Manually inspected nirfmxwlan.proto file.

generated client code that uses the old name will have to be updated when pulling in the new proto. Binary compatibility will be maintained.

[RahulBenaka]

@reckenro @astarche "Validate Python" job in the PR is failing.

I did try to use co-pilot and resolve the error, but I was only able to understand the error. Where should I update the protobuf version so that I can re-run the cmake commands and resolve this issue?

[RahulBenaka]

@reckenro @astarche "Validate Python" job in the PR is failing. I did try to use co-pilot and resolve the error, but I was only able to understand the error. Where should I update the protobuf version so that I can re-run the cmake commands and resolve this issue?

I have resolved the issue. Can you please review?
@reckenro @astarche

[bkeryan]

@reckenro @astarche "Validate Python" job in the PR is failing. I did try to use co-pilot and resolve the error, but I was only able to understand the error. Where should I update the protobuf version so that I can re-run the cmake commands and resolve this issue?

Python stubs generated with protobuf v6 and/or newer versions of grpcio-tools import google.protobuf.runtime_version in order to do some version checks. This submodule did not exist in older protobuf versions, so you get an ImportError before it even gets to the version check.

grpcio-tools 1.49.1 requires protobuf>=4.21.3,<5.0dev, so it cannot coexist with protobuf v5 or v6. However, the generated code from grpcio-tools 1.49.1 works fine with protobuf v5 and v6.

[bkeryan]

Python examples project looks ok to me.

[RahulBenaka]

Python examples project looks ok to me.

But the Validate Python Job in PR is still failing.
I did run poetry update too, but it didn't bring in any new changes. The Job is getting cancelled (not errored out). And it is also not letting run the other build_desktop jobs too. Any idea why this job could be cancelleing out?

@bkeryan @reckenro

[RahulBenaka]

Python examples project looks ok to me.

But the Validate Python Job in PR is still failing. I did run poetry update too, but it didn't bring in any new changes. The Job is getting cancelled (not errored out). And it is also not letting run the other build_desktop jobs too. Any idea why this job could be cancelleing out?

@bkeryan @reckenro

Its resoved now

[bkeryan]

Python examples project looks ok to me.

But the Validate Python Job in PR is still failing. I did run poetry update too, but it didn't bring in any new changes. The Job is getting cancelled (not errored out). And it is also not letting run the other build_desktop jobs too. Any idea why this job could be cancelleing out?
@bkeryan @reckenro

Its resoved now

Ok, I filed a bug about the underlying problem with the build workflows: #1230