Repository navigation
1.1.0: send waiting events to a daemon that registers - #83
Merged
Merged
Conversation
An event raised with no daemon registered (the 10 s launchd takes to start one again after an upgrade, a start or a SIGTERM), or whose hook ended with its daemon, waited for its deadline with nothing to answer it.
…d the changelog for 1.0.9
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The next release is 1.1.0, not 1.0.9: the app's and the extension's version, the changelog's heading and the comment that dates the resend.
An event raised while a daemon registers reaches it on its own and again in the resend of the events still waiting, and its agent ran twice for one connection, the second answer refused as spent. The daemon keeps the events it has taken until their deadline and skips one it already has (hooks_skipped, already_received).
The install script, the site's release, the install guides, the README, the plan and the npm package name 1.1.0. The script pins Blackice-1.1.0.zip of build 64, from 491b61f, the candidate (SHA-256 194e7d8f...3138). Nothing in macos/ changes, so the tag can go on this commit.
brew upgrade boots the daemon out and deletes its LaunchAgent, since Homebrew runs the cask's uninstall launchctl on an upgrade too, and start left it so: after brew upgrade from 1.0.7 to 1.0.8 on 16 November it said "blackice is on in ask mode, fx answers" with no daemon, and three events were not sent. A start that replaced the extension of another build now loads the LaunchAgent when the configuration has hooks and launchd no longer has it. Any other start leaves it as it is and says in ask mode that the hooks need it.
The install script pins Blackice-1.1.0.zip of build 65, from 17f4e4c, the candidate (SHA-256 f26bb83c...80f0). Nothing in macos/ changes, so the tag can go on this commit.
P5-24: events sent again to a daemon that registers, after a SIGKILL, a SIGTERM while a hook ran and an upgrade's start; start loads the daemon again after Homebrew removed its LaunchAgent, where 1.0.8's start left none; a first install of 1.0.8 from the site; 16 hours of use on builds 63 and 64; the fault tests on build 65, of which the run's files show 28 of 29 checks again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two fixes for 1.0.9, from the test of the 1.0.8 candidate (evidence/P5-23):
stopandstartsay to run the command in a terminal on the Mac when macOS needs an administrator and cannot ask (over ssh).Built with warnings as errors and 653 tests pass on the Mac. Draft: the first one changes the extension, so it needs a signed build and a run on the Mac (a connection waiting while the daemon is killed, answered by the new one) before it merges.