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

mssql throwing "socket must be an instance of net.Socket on attempted connection #8066

Closed
ReeceXW opened this issue Jan 9, 2024 · 3 comments
Labels
bug Something isn't working node.js Compatibility with Node.js APIs

Comments

@ReeceXW
Copy link

ReeceXW commented Jan 9, 2024

What version of Bun is running?

1.0.21+837cbd60d

What platform is your computer?

Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 x86_64

What steps can reproduce the bug?

Initialize a bun project, install mssql, use a basic example like the following:

import * as mssql from "mssql";

await mssql.connect({
    server: "...",
    user: "...",
    password: "...",
    database: "..."
});

What is the expected behavior?

Some sort of success/error response from the database.

What do you see instead?

A connection error

socket must be an instance of net.Socket, code: "ESOCKET"

Additional information

This works running under Node

@ReeceXW ReeceXW added the bug Something isn't working label Jan 9, 2024
@Electroid
Copy link
Contributor

Duplicate of #5147

@Electroid Electroid marked this as a duplicate of #5147 Jan 9, 2024
@Electroid Electroid closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2024
@Electroid Electroid added the node.js Compatibility with Node.js APIs label Jan 9, 2024
@ReeceXW
Copy link
Author

ReeceXW commented Jan 9, 2024

Duplicate of #5147

You've closed this because of an open issue that was totally ignored? A major issue that needs to be addressed

@Electroid
Copy link
Contributor

Duplicate of #5147

You've closed this because of an open issue that was totally ignored? A major issue that needs to be addressed

@ReeceXW It's helpful to close duplicate issues so the context on a particular bug is in one place. That said, I can understand the frustration that this bug has still not been fixed, but indeed we will fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working node.js Compatibility with Node.js APIs
Projects
None yet
Development

No branches or pull requests

2 participants