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.

Sign up for GitHub

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

Jump to bottom

switch to pytest-watcher #109

Merged
merged 1 commit into from
Jun 4, 2024
Merged

switch to pytest-watcher #109

merged 1 commit into from
Jun 4, 2024

Conversation

bengerman13
Copy link
Contributor

Changes proposed in this pull request:

  • switch to pytest-watcher

Things to check

  • For any logging statements, is there any chance that they could be logging sensitive data?
  • Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

Security considerations

None - these changes only affect local unit testing

@bengerman13
switch to pytest-watcher
080a901 
pytest-watch chokes on toml, so we should use pytest-watcher
@bengerman13 bengerman13 requested a review from a team June 3, 2024 22:05
@bengerman13 bengerman13 merged commit aa61903 into main Jun 4, 2024
1 check passed
@bengerman13 bengerman13 deleted the bb/use-other-watcher branch June 4, 2024 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@markdboyd markdboyd markdboyd approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@bengerman13 @markdboyd