Repository navigation
Support unix domain sockets in fetch() - #9097
Conversation
|
❌ @Jarred-Sumner 1 files with test failures on bun-darwin-aarch64: |
|
❌ @Jarred-Sumner 2 files with test failures on linux-x64:
|
|
❌ @Jarred-Sumner 4 files with test failures on linux-x64-baseline:
|
|
Can we keep the naming consistent between |
changed to use |
|
❌ @Jarred-Sumner 1 files with test failures on bun-darwin-x64: |
❌🪟 @Jarred-Sumner, there are 12 test regressions on Windows x86_64
|
| return try this.context(is_ssl).connectSocket(client, client.unix_socket_path); | ||
| } | ||
|
|
||
| if (client.http_proxy) |url| { |
There was a problem hiding this comment.
should we error on Bun__fetch if we try to use http_proxy + unix socket?
There was a problem hiding this comment.
we also need a test for this case
cirospaciari
left a comment
There was a problem hiding this comment.
one comment and test/js/node/stream/node-stream.test.js (SIGTERM) on bun-darwin-aarch64
Co-authored-by: Ciro Spaciari <ciro.spaciari@gmail.com>
|
The node-stream test is a flaky one, I think unrelated to these changes |
|
Please add a test for this:
|
What does this PR do?
This adds an option
"unix"tofetchthat lets you provide a path to a unix domain socket. I'm not sure about this API in particular, but this needs to exist somehowHow did you verify your code works?
Tests in
fetch.unix.test.ts