Skip to content
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

Request.signal is undefined when passed an AbortController.signal #1864

Closed
ThatOneBro opened this issue Jan 20, 2023 · 1 comment
Closed
Labels
bug Something isn't working web-api Something that relates to a standard Web API

Comments

@ThatOneBro
Copy link
Contributor

ThatOneBro commented Jan 20, 2023

What version of Bun is running?

0.5.1 (canary)

What platform is your computer?

Darwin 21.6.0 x86_64 i386

What steps can reproduce the bug?

const controller = new AbortController();
const signal = controller.signal;

console.log({
  signal,
  requestSignal: new Request("http://localhost:3000/blog/salt", {
    signal,
  }).signal,
});

What is the expected behavior?

requestSignal should be an AbortSignal like the signal created manually

What do you see instead?

requestSignal is undefined on Request

Additional information

Reported by @SaltyAom (originally reported by @jacob-ebey in #1653)

@ThatOneBro ThatOneBro added the bug Something isn't working label Jan 20, 2023
@Electroid Electroid added the web-api Something that relates to a standard Web API label Jan 20, 2023
@cirospaciari
Copy link
Collaborator

This was fixed by 24d624b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working web-api Something that relates to a standard Web API
Projects
None yet
Development

No branches or pull requests

3 participants