Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Conversation

GlenTiki
Copy link
Contributor

Building with-lttng has been broken for 2 years. We should
deprecate and remove this dead code.

Checklist
Affected core subsystem(s)

doc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Feb 24, 2018
@AndreasMadsen
Copy link
Member

AndreasMadsen commented Feb 24, 2018

End-of-Life means that the probes are actually removed. However, this doesn't actually remove them. This is barely a documentation deprecation.

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.

@GlenTiki
Copy link
Contributor Author

@AndreasMadsen I've changed it to Documentation only.

@GlenTiki
Copy link
Contributor Author

If TSC approved, I would be happy to open another PR straight up tearing it out.

@AndreasMadsen AndreasMadsen added the semver-major PRs that contain breaking changes and should be released in the next major version. label Feb 24, 2018
@AndreasMadsen
Copy link
Member

AndreasMadsen commented Feb 24, 2018

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

@ChALkeR
Copy link
Member

ChALkeR commented Feb 24, 2018

Some refs:

@GlenTiki
Copy link
Contributor Author

@ChALkeR And the commit that broke it: f1d2792

@ChALkeR
Copy link
Member

ChALkeR commented Feb 24, 2018

Previous fix attempt (stalled, closed): #9404.

Copy link
Member

@mcollina mcollina left a 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.

Copy link
Member

@TimothyGu TimothyGu left a 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.

@GlenTiki GlenTiki mentioned this pull request Feb 24, 2018
2 tasks
@@ -914,6 +914,14 @@ Type: Runtime

This was never a documented feature.

<a id="DEP0101"></a>
Copy link
Contributor

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?

Copy link
Member

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


Type: Documentation-only

`with-lttng` has been an opt-in compile time option that was broken when trying to compile
Copy link
Contributor

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed

Copy link
Member

@jasnell jasnell left a 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.
GlenTiki added a commit to GlenTiki/node that referenced this pull request Feb 25, 2018
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
@rvagg
Copy link
Member

rvagg commented Feb 26, 2018

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.

Copy link
Member

@gibfahn gibfahn left a 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.

@jasnell
Copy link
Member

jasnell commented Feb 26, 2018

I generally prefer deprecating but given that it's been broken, I'm good with pulling it out.

@GlenTiki
Copy link
Contributor Author

Should this be closed in favour of #18982? Should that PR receive a deprecation PR too?

@mcollina
Copy link
Member

Yes, but the deprecation should be ported there too (I think).

GlenTiki added a commit that referenced this pull request Mar 1, 2018
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]>
GlenTiki added a commit that referenced this pull request Mar 1, 2018
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]>
MayaLekova pushed a commit to MayaLekova/node that referenced this pull request May 8, 2018
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]>
MayaLekova pushed a commit to MayaLekova/node that referenced this pull request May 8, 2018
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. semver-major PRs that contain breaking changes and should be released in the next major version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.