Please check if your PR fulfills the following requirements:
[ ] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[X] Build was run locally and without warnings or errors
[X] All previous and new tests pass
Pull request type
Please check the type of change your PR introduces:
- [X] Bugfix
- [ ] Feature
- [X] Code style update (formatting, renaming, typo fix)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [ ] Other (please describe):
## What is the current behavior?
SIGTSTP signal is not caught, so if the process is paused then the compression and decompression stats are no longer accurate.
Related Issue URL:
What is the new behavior?
SIGTSTP is caught if the system supports it.
SIGTSTP will be blocked/unblocked while the handler is in effect
Does this introduce a breaking change?
[ ] Yes
[X] No
Other information
This can be added for 5.4.2 or 5.5.0. It adds a new string that will need to be translated and its been a "bug" for a long time, so 5.5.0 might be more appropriate.
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces: - [X] Bugfix - [ ] Feature - [X] Code style update (formatting, renaming, typo fix) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior?SIGTSTP signal is not caught, so if the process is paused then the compression and decompression stats are no longer accurate.
Related Issue URL:
What is the new behavior?
Does this introduce a breaking change?
Other information
This can be added for 5.4.2 or 5.5.0. It adds a new string that will need to be translated and its been a "bug" for a long time, so 5.5.0 might be more appropriate.