-
Notifications
You must be signed in to change notification settings - Fork 905
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
feat(userspace): deprecate -d
daemonize option
#2677
Conversation
/milestone 0.36.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@incertum Does this PR just correct the comments?
This is not wip and rather "desperation in progress" as it's just a dummy commit somehow, I have no glue really other than it's broken no outputs when using |
Questions:
|
yes same outcome, that is, no outputs. My debugging journey came to the conclusion that somehow we fail to reach the code flow where we pop from the queue when using
I actually synced with SREs and the answer would be no. However, we should keep the pidfile option. That was the one appealing aspect of using @leogr depending on how much engineering resources we have, I am of course ok with keeping it if someone finds a fix. At the same time, it would not be good to keep supporting something that is broken. In addition, removing some older features not urgently needed will be better for all of us maintainers, because we reduce maintenance overhead and make space for new features we urgently do need. Therefore, I would be ok to just remove it without a formal deprecation process since it is already broken in the current release. Again, we can keep the pidfile option without needing If above sounds like a plan I can go ahead and repurpose this PR, else I may just close it as I am not advancing with finding a fix. |
Since using So, I'm in favor to remove it just because not having that option would provide a better UX, regardless of the fact that's broken. Ofc, I wouldn't fix it if we decide to remove it. Also, I totally agree with keeping the
let's see what others think cc @falcosecurity/falco-maintainers |
Sorry, I'm late to the party, agree with removing this! |
fd7d018
to
7308f8b
Compare
-d
daemonize option-d
daemonize option
Removed |
One file is conflicting. Rebase pls. 🙏 |
7308f8b
to
27445dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All these cleanups are really appreciated, thank you!
@@ -51,7 +51,7 @@ falco::app::run_result falco::app::actions::init_outputs(falco::app::state& s) | |||
|
|||
if (s.options.dry_run) | |||
{ | |||
falco_logger::log(LOG_DEBUG, "Skipping daemonizing in dry-run\n"); | |||
falco_logger::log(LOG_DEBUG, "Skipping outputs initialization in dry-run\n"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh cool you have already done it here, ignore my comment in the other PR i don't remember which 😹
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: 43f32110b12100baf0134e85f0f798f6a78a24f5
|
we need a rebase now 🙄 |
Deprecate `-d` option (currently broken). Symptoms included the message queue filling up without popping any messages even though events were handled normally. Maintainers decided to deprecate not needed `-d` option while keeping the useful `pidfile` command args option. Signed-off-by: Melissa Kilby <melissa.kilby.oss@gmail.com>
1fa24f9
to
e3031c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: 0ee2ac67767609a87e2f7a78b5855ac8dbbc6a97
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, incertum, leogr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Symptoms included the message queue filling up without popping any messages even though events were handled normally.
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
Update : feat(userspace): deprecate
-d
daemonize option@falcosecurity/falco-maintainers
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: