-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
doc: deprecate lttng #18975
doc: deprecate lttng #18975
Conversation
edit: Ordinarily, one would documentation deprecate a feature first. But given that this feature hasn't worked for two years and no one have complained, we can properly remove it immediately. But I think that requires TSC approval. |
bf74d8f
to
df5df4b
Compare
@AndreasMadsen I've changed it to Documentation only. |
If TSC approved, I would be happy to open another PR straight up tearing it out. |
Should we remove LTTng integration or only document deprecate LTTng integration? LTTng integration have been broken for two years, no one is apparently using it. If we are going to support static tracing points on linux, the vanilla linux tracing points should be used instead. LTTng supports those too, so very little will be lost and it allows for other tracing implementations too. The only advantages of LTTng is that is slightly more performant. /cc @nodejs/tsc |
Some refs:
|
Previous fix attempt (stalled, closed): #9404. |
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.
LGTM.
I’m aso +1 in removing this completely.
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.
+1 on removing all lttng code right now.
doc/api/deprecations.md
Outdated
@@ -914,6 +914,14 @@ Type: Runtime | |||
|
|||
This was never a documented feature. | |||
|
|||
<a id="DEP0101"></a> |
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.
Shouldn't the 0101
here and below be XXXX
until the PR lands?
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.
Yep. DEP00XX
until it lands. The person landing should assign the code
doc/api/deprecations.md
Outdated
|
||
Type: Documentation-only | ||
|
||
`with-lttng` has been an opt-in compile time option that was broken when trying to compile |
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.
I think it would be better to just say the with-lttng
compile time option is deprecated. If there is a recommended alternative, that could be listed here as well.
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.
Agreed
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.
Lgtm with the comments addressed
Building with-lttng has been broken for 2 years. We should deprecate and remove this dead code.
df5df4b
to
c84a31d
Compare
This cleans up and removes lttng support completely. Recent discussion on a PR to deprecate lttng suggested that we remove it completely pending feedback from the TSC. This should be considered a non breaking change, as a recent PR reveals that compiling with this system has been broken for nearly two years. Refs: nodejs#18971 Refs: nodejs#18975 Refs: nodejs#18945
Fine by me, I think nearForm were the last ppl I saw using/promoting it and they're in here with a +1 so I'm onboard with just ripping it out. |
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.
+1 on directly removing given the reasons and consensus in this thread.
I generally prefer deprecating but given that it's been broken, I'm good with pulling it out. |
Should this be closed in favour of #18982? Should that PR receive a deprecation PR too? |
Yes, but the deprecation should be ported there too (I think). |
This cleans up and removes lttng support completely. Recent discussion on a PR to deprecate lttng suggested that we remove it completely pending feedback from the TSC. This should be considered a non breaking change, as a recent PR reveals that compiling with this system has been broken for nearly two years. Refs: #18971 Refs: #18975 Refs: #18945 PR-URL: #18982 Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jackson Tian <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: #18982 Refs: #18971 Refs: #18975 Refs: #18945 Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jackson Tian <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]>
This cleans up and removes lttng support completely. Recent discussion on a PR to deprecate lttng suggested that we remove it completely pending feedback from the TSC. This should be considered a non breaking change, as a recent PR reveals that compiling with this system has been broken for nearly two years. Refs: nodejs#18971 Refs: nodejs#18975 Refs: nodejs#18945 PR-URL: nodejs#18982 Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jackson Tian <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#18982 Refs: nodejs#18971 Refs: nodejs#18975 Refs: nodejs#18945 Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jackson Tian <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]>
Building with-lttng has been broken for 2 years. We should
deprecate and remove this dead code.
Checklist
Affected core subsystem(s)
doc