-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
fix: make startTls code compatible with Bun #2119
Merged
Merged
Changes from 4 commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
bca1e28
uplift startTls code to be compatible with current bun
sidorares f4fb55e
more tls refactoring
sidorares 69e3b2f
lint
sidorares e52b5d0
ci: enable tls in bun matrix
sidorares 607a66d
fix ssl tests
sidorares 0bc180c
lint
sidorares 7d327a9
bun: only run 2 basic tests for now
sidorares 47c2b5b
lint
sidorares 84beaa5
don't enable ssl in test running against fake server
sidorares 456a522
fix typo
sidorares 99b0b85
debug failures
sidorares 6c5879c
try bun canary
sidorares 583a317
ci: add osx runner
sidorares 709091b
ci: install docker for osx
sidorares 9b2db14
ci: install docker for osx
sidorares f00b840
ci: install docker for osx
sidorares 3036c51
ci: osx - don't mount config in docker
sidorares fe27ed1
handle ECONNREFUSED in waitDatabaseReady helper
sidorares 585c3f1
comment out instead of early return
sidorares a73e90d
explicitly install lima
sidorares cbb2f94
use connection.end() instead of destroy
sidorares c4e45b8
debug Ssl_cipher assertion
sidorares 7eb32af
more flexible Ssl_cipher assertion
sidorares 1a594f2
initialize packet header befor writing
sidorares f065055
cleanup
sidorares 4c64210
add compression to bun matrix
sidorares 75ae090
only use bun v0.6.13 for non-ssl tests
sidorares File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we probably need to emit this error too or else more people will run into this issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to change event name from "connect" to "secureConnect" as well, looks like node emits both and the first one is deprecated. TLS docs only mention secureConnect - https://nodejs.org/dist/latest-v20.x/docs/api/tls.html#event-secureconnection ( later moved code to the Tls.connect() callback to avoid referencing event name )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might need to investigate further if this is how I should handle errors.
_tlsError
event is still in latest node - https://github.com/nodejs/node/blob/d9438ccbd8f6cbd6c8ebfae84b0f2782d2c1fca7/lib/_tls_wrap.js#L991-L1010 , not sure if documented.