-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Measurement Plug-In Generated Client to Resolve with the Corresponding Measurement Service Version #925
Conversation
Test Results 40 files ± 0 40 suites ±0 53m 51s ⏱️ + 1m 13s Results for commit 1386842. ± Comparison against base commit 113b166. This pull request removes 1 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following #907, in a separate PR please consider moving the version of the test measurements from __init__.py to its corresponding .serviceconfig
.
packages/service/ni_measurement_plugin_sdk_service/discovery/_client.py
Outdated
Show resolved
Hide resolved
packages/generator/ni_measurement_plugin_sdk_generator/client/__init__.py
Show resolved
Hide resolved
packages/generator/ni_measurement_plugin_sdk_generator/client/__init__.py
Show resolved
Hide resolved
@Jotheeswaran-Nandagopal @Avinash2Suresh I think part of what's going on with the build failures is that our virtualenv caching uses the poetry.lock as a key, and this doesn't change when you modify files in https://github.com/ni/measurement-plugin-python/blob/main/.github/workflows/run_system_tests.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're updating the version of the service pkg, then please update the version of the generator and SDK packages as well.
As per the updates in #911, I have moved the |
@bkeryan I have updated the package versions as service package is updated, in order to resolve the pipeline failure caused by our virtualenv caching. |
…sponding Measurement Service Version (#925) * fix: update resolve service api and its dependencies * fix: formatting * fix: update resolve service * fix: add deployment_target * fix: update version of service * fix: update version and revert the unwanted changes * fix: revert unwanted change * fix: update poetry * fix: formatting * fix: update version of test measurements in service config (cherry picked from commit 90d3ab7)
…nt to Resolve with the Corresponding Measurement Service Version (#938) Update Measurement Plug-In Generated Client to Resolve with the Corresponding Measurement Service Version (#925) * fix: update resolve service api and its dependencies * fix: formatting * fix: update resolve service * fix: add deployment_target * fix: update version of service * fix: update version and revert the unwanted changes * fix: revert unwanted change * fix: update poetry * fix: formatting * fix: update version of test measurements in service config (cherry picked from commit 90d3ab7)
|
What does this Pull Request accomplish?
version
as a parameter in theresolve_service
API of the discovery client with respect to the latest change in ni-apis.resolve_service
API with version parameter.Mako
template of Measurement Plug-In Client generator to resolve the service with the version of the measurement.Why should this Pull Request be merged?
The
ResolveServiceRequest
has been updated in the ni-apis, withversion
.As, multiple versions of same measurement can be registered simultaneously, the resolve service will fetch the service with latest version, if the version is not specified while resolving. So, when a user creates a client with version
1.0.0.0
and later, run themeasure()
API in client with higher version2.0.0.0
of registered measurement, the service location will be resolved without any error, as the version is not checked. With this, if the configurations are updated in new version of measurement, this will result in error during measure call.With the implementation in this Pull Request (adding version), client will be generated for the latest version (as multiple versions are not supported at present). During the measurement process in the generated client, measurement service will be resolved with the version of the generated client. If the version mismatch is captured, throw error appropriately.
What testing has been done?