Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Adding server version always in the command display #1137

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

yardov
Copy link
Contributor

@yardov yardov commented Dec 4, 2024

Is quite important to know what version of the server is running and not only when the --version is passed.

What does this Pull Request accomplish?

The server when executed will always display the version running.

Why should this Pull Request be merged?

All software needs to have a way to know the version running irrespective if a tag was passed. This ensure in our customers that they know the correct version is running.

Ideally, this should be queryable by a client but that's a task for another day.

What testing has been done?

None.

Is quite important to know what version of the server is running and not only when the --version is passed.
@@ -88,6 +88,15 @@ static void RunServer(const ServerConfiguration& config)
config.config_file_path.c_str());
}

std::string string_kNiDeviceGrpcBranchName(nidevice_grpc::kNiDeviceGrpcBranchName);
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is the same logic as in the --version case. Please create a static function in this file. that is then called in both places so the logic for both of these will always stay consistent.

std::string string_kNiDeviceGrpcBranchName(nidevice_grpc::kNiDeviceGrpcBranchName);

@maxxboehme
Copy link
Collaborator

@yardov planning to create a release branch of grpc-device 2.9.0 on the 18th. If want this change in the 2.9.0 release please make sure to continue progress on the PR.

@christag-ni
Copy link
Contributor

We are planning to create a release branch on the 18th, and your PR will need to be completed before then for the changes to be in effect. Do you want these changes included in this release?

@christag-ni
Copy link
Contributor

I'll be creating the release branch at 11:30 CST.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants