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

Ensure the logFileLocation is set #2984

Merged
merged 3 commits into from
Oct 18, 2023
Merged

Ensure the logFileLocation is set #2984

merged 3 commits into from
Oct 18, 2023

Conversation

aeisenberg
Copy link
Contributor

@aeisenberg aeisenberg commented Oct 16, 2023

logFileLocation was not set after a query finishes running. I don't know when this bug was introduced. I think it goes as far back as the refactor to remove the old query server.

Replace this with a description of the changes your pull request makes.

Checklist

  • CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
  • Issues have been created for any UI or other user-facing changes made by this pull request.
  • [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

`logFileLocation` was not set after a query finishes running. I don't
know when this bug was introduced. I think it goes as far back as
the refactor to remove the old query server.
@aeisenberg aeisenberg requested a review from a team as a code owner October 16, 2023 23:45
Copy link
Contributor

@angelapwen angelapwen left a comment

Choose a reason for hiding this comment

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

:shipit: I think the code scanning warning can be dismissed as the line in question is not actually assigning a value.

@aeisenberg
Copy link
Contributor Author

Thanks for the review. Still need to add a change note.

@aeisenberg
Copy link
Contributor Author

The code scanning warning was legitimate since there was a value being assigned in the constructor parameter list as well as the constructor body. I refactored a bit so there is no warning.

@angelapwen
Copy link
Contributor

The code scanning warning was legitimate since there was a value being assigned in the constructor parameter list as well as the constructor body. I refactored a bit so there is no warning.

Ah I see.. I think the location it showed up on was a bit misleading (because it didn't show on any assignment). Thanks!

@aeisenberg aeisenberg merged commit df55e03 into main Oct 18, 2023
14 checks passed
@aeisenberg aeisenberg deleted the aeisenberg/fix-log-path branch October 18, 2023 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants