-
Notifications
You must be signed in to change notification settings - Fork 56
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.
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
Some runtime options are applied too late #103
Comments
That's probably my bad. I changed the startup order so the command-line option parser could invoke methods on BeesContext, but that means BeesContext's constructor now runs before we've parsed the The stuff in BeesContext that emits log messages should probably be moved to the |
BTW: This also messes with |
Do not touch BeesContext until really needed. As a safety, move its initialization after cmdline parsing. Then follow the proven design of adding the needed default value and apply it to BeesContext later. Also, let's set a flag when initialization after cmdline parsing is done so we know if we already want to log an exit code. Fixes: commit 23f3e4e Closes: Zygo#103 Signed-off-by: Kai Krakow <[email protected]>
Some options like
--no-timestamps
are applied too late, bees may already have logged something:Note how it first prepends the timestamps and logs a different pid.tid format, then switches to
--no-timestamps
.The text was updated successfully, but these errors were encountered: