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

Set initial memory value after sending SIGINT #14

Closed
jon-rei opened this issue Sep 1, 2022 · 1 comment
Closed

Set initial memory value after sending SIGINT #14

jon-rei opened this issue Sep 1, 2022 · 1 comment
Labels
enhancement New feature or request released

Comments

@jon-rei
Copy link
Contributor

jon-rei commented Sep 1, 2022 •
edited
Loading

It would be nice if the tool could set the "Memory value before test start" value after a SIGINT (sending Ctrl + c in the terminal) was sent to the console.

Maybe this can help while implementing it: https://dev.to/joashxu/go-graceful-sigint-killing-6if
@janritter janritter added the enhancement New feature or request label Sep 1, 2022
janritter added a commit that referenced this issue Sep 10, 2022
@janritter
refactor(#14): improved error handling parts of change memory code
574307b
janritter added a commit that referenced this issue Sep 10, 2022
@janritter
Merge pull request #21 from janritter/feat/#14/reset-memory-on-sigint
2b67c85 
Reset memory on ctrl + c
janritter pushed a commit that referenced this issue Sep 10, 2022
@semantic-release-bot
chore(release): 0.5.0 [skip ci]
d328260 
# [0.5.0](0.4.1...0.5.0) (2022-09-10)

### Features

* **#14:** reset memory to pre-test value after canceling the tool with ctrl + c - resolves [#14](#14) ([28b96e3](28b96e3))
@janritter
Copy link
Owner

🎉 This issue has been resolved in version 0.5.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@janritter @jon-rei