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. |
mcollina
left a comment
There was a problem hiding this comment.
LGTM.
I’m aso +1 in removing this completely.
TimothyGu
left a comment
There was a problem hiding this comment.
+1 on removing all lttng code right now.
doc/api/deprecations.md
Outdated
There was a problem hiding this comment.
Shouldn't the 0101 here and below be XXXX until the PR lands?
There was a problem hiding this comment.
Yep. DEP00XX until it lands. The person landing should assign the code
doc/api/deprecations.md
Outdated
There was a problem hiding this comment.
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.
jasnell
left a comment
There was a problem hiding this comment.
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. |
gibfahn
left a comment
There was a problem hiding this comment.
+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 <timothygu99@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #18982 Refs: #18971 Refs: #18975 Refs: #18945 Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
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 <timothygu99@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#18982 Refs: nodejs#18971 Refs: nodejs#18975 Refs: nodejs#18945 Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jackson Tian <shyvo1987@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Building with-lttng has been broken for 2 years. We should
deprecate and remove this dead code.
Checklist
Affected core subsystem(s)
doc