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

Comment out debug print statements #5200

Merged
merged 1 commit into from
Oct 29, 2024
Merged

Comment out debug print statements #5200

merged 1 commit into from
Oct 29, 2024

Conversation

shorowit
Copy link
Contributor

Pull request overview

Comment out debug print statements

@shorowit shorowit requested a review from jmarrec May 15, 2024 18:40
@shorowit shorowit self-assigned this May 15, 2024
@@ -34,7 +34,7 @@ namespace cli {
app->add_flag(
"-m,--measures_only",
[opt](std::int64_t val) {
fmt::print("val={}\n", val);
// fmt::print("val={}\n", val);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Totally ok here

@@ -78,7 +78,7 @@ RubyEngine::~RubyEngine() {
// ruby_cleanup calls ruby_finalize
int ex = ruby_cleanup(0);
if (ex != 0) {
fmt::print("RubyEngine return code was {}\n", ex);
// fmt::print("RubyEngine return code was {}\n", ex);
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not sure I want this one gone...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It doesn't seem like standard practice to print the exit code? After all, anyone can easily obtain the exit code themself.

Copy link
Collaborator

Choose a reason for hiding this comment

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

The message was to explain why it returned a non zero exit code.

When running something like

at_exit {
exit 12
}

But sure, I suppose that's fine removing it

@jmarrec jmarrec added the Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge. label May 15, 2024
@jmarrec jmarrec added the Ready for Merge Set this once CI is passing and reviews are approved. label Oct 29, 2024
@ci-commercialbuildings
Copy link
Collaborator

ci-commercialbuildings commented Oct 29, 2024

CI Results for eeb4e67:

@jmarrec
Copy link
Collaborator

jmarrec commented Oct 29, 2024

Don't know what CI is tripping on, but this is fine.

@jmarrec jmarrec merged commit ab6e410 into develop Oct 29, 2024
2 of 6 checks passed
@jmarrec jmarrec deleted the comment_debug branch October 29, 2024 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge. Ready for Merge Set this once CI is passing and reviews are approved.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants