fix saslprep codepoint generation

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Our fork of saslprep, `devtools-shared/saslprep`, generates codepoints and compresses them while during the build step.  This is then written to a source code file as a base64 encoded string.  The saslprep library imports this source code file.

      Sometime recently, the gzip compression started returning a different output value for the compressed codepoints.  The current suspicion is that the difference is in a zlip header / magic compression value and that the data itself is the same.

      We should investigate the changes and determine the following:

      • When/why did the generated codepoints change? 
      • Which version of the generated codepoints should we use?

            Assignee:
            Unassigned
            Reporter:
            Bailey Pearson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: