Bug 259330

Summary:	textproc/opensearch-dashboards: Depends on but does not support node14
Product:	Ports & Packages	Reporter:	Tomoyuki Sakurai <trombik1973>
Component:	Individual Port(s)	Assignee:	opensearch
Status:	Closed Overcome By Events
Severity:	Affects Many People	CC:	admin, grahamperrin, romain
Priority:	---	Keywords:	needs-patch, needs-qa
Version:	Latest	Flags:	bugzilla: maintainer-feedback? (opensearch) koobs: merge-quarterly?
Hardware:	Any
OS:	Any
See Also:	https://github.com/opensearch-project/OpenSearch-Dashboards/issues/835 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257558

Description Tomoyuki Sakurai 2021-10-20 23:55:33 UTC

this bug is a placeholder for those who wrongly think textproc/opensearch-dashboards is usable.

the port is broken in that:

1. the upstream does not support node14
2. the upstream will not support node14 (https://github.com/opensearch-project/OpenSearch-Dashboards/issues/835)
3. the port sweeps its own bugs under the rug by using "node --no-warnings"

in bug 257558, it was reported that "opensearch" was working "for about 3 weeks without any issues", but nothing was mentioned about opensearch-dashboards.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257558

for starters, opensearch-dashboards does not log anything because of incompatibility with node14. i have not investigated what _possibly_ works, and what not, however, it is apparent from the upgrade plan in the GitHub Issue that the number of incompatibilities is huge. it is not conceivable that the port would work.

Comment 1 Sven Ruediger 2021-10-21 04:35:40 UTC

Could you please be a little more precise about the issues you have with Dashboards?
The broken logging is a known issue with node14. If you see any other issues please report them here or on Github.


https://github.com/opensearch-project/OpenSearch-Dashboards/pull/678

Comment 2 Tomoyuki Sakurai 2021-10-21 06:10:25 UTC

(In reply to Sven R from comment #1)

> The broken logging is a known issue with node14

any other _known_ issues? i do not think pkg-message said anything.

> If you see any other issues please report them here or on Github.

are you a developer at amazon?

if yes:

are you representing the team? your statement does not agree with statements in the issue i mentioned. do you have a consensus in the team?

if no:

the team at amazon is taking the upgrade as a serious matter, it seems. the upgrade path looks bumpy. while they are publicly stating that they will not support node14, issues with node14 will not be accepted. i would be surprised otherwise. i do not want to bother them while they are working on the upgrade. if port maintainers decide to ignore support policy, that is not their problem.

i do understand porting is not an easy task. however, if your port is not ready, tell users so with a big warning especially when you are crossing red tape.