nerves-time / nerves_time

Keep time in sync on Nerves devices
Other
23 stars 13 forks source link

Bump muontrap from 0.4.0 to 0.5.0 #34

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Bumps muontrap from 0.4.0 to 0.5.0.

Release notes *Sourced from [muontrap's releases](https://github.com/fhunleth/muontrap/releases).* > ## v0.5.0 > This update contains many changes throughout. If you're using cgroups, please > review the changes as they likely affect your code. For those upgrading from `v0.5.0-rc.0`, > the only change is in italics below for how the exit status is set for commands exiting due to > signals. > > * New features > * Added `:cgroup_base`. The preferred way of using cgroups now is for MuonTrap > to create a sub-cgroup for running the command. This removes the need to > keep track of cgroup paths on your own when you run more than one command at > a time. `:cgroup_path` is still available. > * Almost all inconsistencies between MuonTrap.Daemon and MuonTrap.cmd/3 have > been fixed. As a result, MuonTrap.Daemon detects and raises more exceptions > than previous. It is possible that code that worked before will now break. > * MuonTrap.Daemon sets its exit status based on the process's exit code. > Successful exit codes (exit code 0) exit `:normal` and failed exit codes > (anything else) do not. This makes it possible to use the Supervisor > `:temporary` restart strategy that only restarts failures. > * MuonTrap.Daemon supports a `:name` parameter for setting GenServer names. > * MuonTrap.Daemon `cgget` and `cgset` helpers return ok/error tuples now since > it was too easy to accidentally call them such that they'd raise. > > * Bug fixes > * Forcefully killed processes would get stuck in a zombie state until the kill > timeout expired due to a missing call to wait(2). This has been fixed. > * *Exit status of process killed by a signal reflects that. I.e., a process > killed by a signal exits with a status of 128+signal.* > > ## v0.5.0-rc.0 > This update contains many changes throughout. If you're using cgroups, please > review the changes as they likely affect your code. > > * New features > * Added `:cgroup_base`. The preferred way of using cgroups now is for MuonTrap > to create a sub-cgroup for running the command. This removes the need to > keep track of cgroup paths on your own when you run more than one command at > a time. `:cgroup_path` is still available. > * Almost all inconsistencies between MuonTrap.Daemon and MuonTrap.cmd/3 have > been fixed. As a result, MuonTrap.Daemon detects and raises more exceptions > than previous. It is possible that code that worked before will now break. > * MuonTrap.Daemon sets its exit status based on the process's exit code. > Successful exit codes (exit code 0) exit `:normal` and failed exit codes > (anything else) do not. This makes it possible to use the Supervisor > `:temporary` restart strategy that only restarts failures. > * MuonTrap.Daemon supports a `:name` parameter for setting GenServer names. > * MuonTrap.Daemon `cgget` and `cgset` helpers return ok/error tuples now since > it was too easy to accidentally call them such that they'd raise. > > * Bug fixes > * Forcefully killed processes would get stuck in a zombie state until the kill > ... (truncated)
Changelog *Sourced from [muontrap's changelog](https://github.com/fhunleth/muontrap/blob/master/CHANGELOG.md).* > ## v0.5.0 > > This update contains many changes throughout. If you're using cgroups, please > review the changes as they likely affect your code. > > * New features > * Added `:cgroup_base`. The preferred way of using cgroups now is for MuonTrap > to create a sub-cgroup for running the command. This removes the need to > keep track of cgroup paths on your own when you run more than one command at > a time. `:cgroup_path` is still available. > * Almost all inconsistencies between MuonTrap.Daemon and MuonTrap.cmd/3 have > been fixed. As a result, MuonTrap.Daemon detects and raises more exceptions > than previous. It is possible that code that worked before will now break. > * MuonTrap.Daemon sets its exit status based on the process's exit code. > Successful exit codes (exit code 0) exit `:normal` and failed exit codes > (anything else) do not. This makes it possible to use the Supervisor > `:temporary` restart strategy that only restarts failures. > * MuonTrap.Daemon supports a `:name` parameter for setting GenServer names. > * MuonTrap.Daemon `cgget` and `cgset` helpers return ok/error tuples now since > it was too easy to accidentally call them such that they'd raise. > > * Bug fixes > * Forcefully killed processes would get stuck in a zombie state until the kill > timeout expired due to a missing call to wait(2). This has been fixed. > * Exit status of process killed by a signal reflects that. I.e., a process > killed by a signal exits with a status of 128+signal. > > ## v0.4.4 > > * Bug fixes > * Fixed an issue where environment variable lists passed to MuonTrap.Daemon > had to be charlists rather than Elixir strings like MuonTrap.cmd/3 and > System.cmd/3. > > ## v0.4.3 > > * Bug fixes > * Reverted removal of `child_spec` > > ## v0.4.2 > > * New features > * MuonTrap.Daemon can log stderr now as well as stdout. Pass > `stderr_to_stdout: true` in the options. Thanks to Timmo Verlaan for this > update. > > ## v0.4.1 > > * Improvements > * Move port process build products under `_build`. This fixes an issue where > ... (truncated)
Commits - [`d240d25`](https://github.com/fhunleth/muontrap/commit/d240d25f2a882629ad7c1f7d0758ede4052eb59e) v0.5.0 release - [`8f2903f`](https://github.com/fhunleth/muontrap/commit/8f2903f61e9433fdac1f96fc6eae240a9fdde639) Bump ex_doc and excoveralls - [`80d7a96`](https://github.com/fhunleth/muontrap/commit/80d7a9662073e31990c1fc9e9d02d8c012ec683c) Follow POSIX exit codes for processes killed by signals - [`22275a2`](https://github.com/fhunleth/muontrap/commit/22275a2f6ce493628173a5a6c852cd28b0ca8c65) v0.5.0-rc.0 release - [`1894b2c`](https://github.com/fhunleth/muontrap/commit/1894b2c7b52961b744ea8b13b479be092ed04cfc) Fix race where tests ran before muontrap test app was ready - [`68f5e5e`](https://github.com/fhunleth/muontrap/commit/68f5e5e45f36841fb396f0cc29da919109205cea) Bump default wait timeout to 500 ms - [`7412081`](https://github.com/fhunleth/muontrap/commit/74120815a519a32720b6804d12cd255506593fdf) Rewrite kill code - [`c94b73a`](https://github.com/fhunleth/muontrap/commit/c94b73a42ba158599498729f5cac8b3a18994d4d) Reduce unit test sleep time to 2 minutes - [`069ab1a`](https://github.com/fhunleth/muontrap/commit/069ab1abfdff6d025fa861e02e9729d82031a8df) Minor cleanup; try to stop prints from leaking out - [`68afce5`](https://github.com/fhunleth/muontrap/commit/68afce5d3936c82bd2e38ecd0986ad0f83c39c54) Make timeout to SIGKILL short for unit test - Additional commits viewable in [compare view](https://github.com/fhunleth/muontrap/compare/v0.4.0...v0.5.0)


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.
dependabot-preview[bot] commented 5 years ago

Looks like muontrap is up-to-date now, so this is no longer needed.