-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: kerberos
-
1
-
Not Needed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We don't fully know why, but on x64 macOS linking kerberos with mongosh fails when using Node.js 24 (log). Not exporting the symbols for these compilation-unit-local variables a) fixes the build and is b) the right choice anyway, since these symbols are not intended to be used externally.
Use Case
As a... mongosh engineer
I want... mongosh to compile on Node.js 24
So that... we don't have to ship an EOL version of Node.js to users
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Is there an opportunity for better cross-driver alignment or testing in this area?
- Is there an opportunity to improve existing documentation on this subject?
Acceptance Criteria
Implementation Requirements
- functional reqs, potential snafus to avoid, performance targets, etc
Testing Requirements
- unit test, spec test sync, etc
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- additional tickets to file, required releases, etc
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward