Skip to content
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

saw-remote-api: Reach parity with SAWScript for global option settings #1538

Merged
merged 2 commits into from
Dec 10, 2021

Conversation

RyanGlScott
Copy link
Contributor

This PR contains two commits that bring saw-remote-api and the Python saw-client library within feature parity of what SAWScript can do with its global settings (e.g., {enable,disable}_lax_pointer_ordering). I have included the commit messages of each individual commit below.

saw-client: Support setting SAW options

This adds a set_option function to the saw_client module that controls whether various global SAW options should be enabled or disabled. The possible options that can be controlled are found in the saw_client.option module.

Fixes #1493.

Add What4 eval to saw-remote-api and saw-client

The infrastructure for doing so was already in place in saw-remote-api, and thanks to #1493, the infrastructure for adding this functionality in the Python saw-client library is now in place as well.

Fixes #1537.

@RyanGlScott RyanGlScott requested review from pnwamk and m-yac December 8, 2021 12:19
@RyanGlScott RyanGlScott added type: enhancement Issues describing an improvement to an existing feature or capability subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings labels Dec 8, 2021
Copy link
Contributor

@m-yac m-yac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I have one suggestion, but it's not critical.

This adds a `set_option` function to the `saw_client` module that controls
whether various global SAW options should be enabled or disabled. The possible
options that can be controlled are found in the `saw_client.option` module.

Fixes #1493.
The infrastructure for doing so was already in place in `saw-remote-api`, and
thanks to #1493, the infrastructure for adding this functionality in the
Python `saw-client` library is now in place as well.

Fixes #1537.
@RyanGlScott RyanGlScott added the PR: ready to merge Magic flag for pull requests to ask Mergify to merge given an approval and a successful CI run label Dec 10, 2021
@mergify mergify bot merged commit a07c01c into master Dec 10, 2021
@mergify mergify bot deleted the T1493 branch December 10, 2021 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: ready to merge Magic flag for pull requests to ask Mergify to merge given an approval and a successful CI run subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings type: enhancement Issues describing an improvement to an existing feature or capability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

saw-remote-api: Add the ability to toggle what4_eval Allow setting SAW options from Python client
2 participants