Reset state in js-bson when building startup snapshot

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • bson-7.3.0
    • Affects Version/s: None
    • Component/s: BSON
    • 2
    • Not Needed
    • None
    • Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      This package can now use v8's addDeserializeCallback to reset internal state
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      Just mentioning this should be enough for people who care about this feature.
      3. Which versions of the driver/connector does this apply to?
      This an update in bson, not in the Node Driver directly.

      Show
      1. What would you like to communicate to the user about this feature? This package can now use v8's addDeserializeCallback to reset internal state 2. Would you like the user to see examples of the syntax and/or executable code and its output? Just mentioning this should be enough for people who care about this feature. 3. Which versions of the driver/connector does this apply to? This an update in bson, not in the Node Driver directly.
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a... Node.js user
      I want... the BSON library to reset state when building startup snapshots
      So that... my processes don't all share the same "unique" id

      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

            Assignee:
            Anna Henningsen
            Reporter:
            Anna Henningsen
            Pavel Safronov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: