Code Monkey home page Code Monkey logo

Comments (12)

Nickhoyer avatar Nickhoyer commented on July 18, 2024 4

I have the same issue. Seems to be fixed in November in #738 but there hasn't been any releases to npm.

@porsager is there any reason there hasn't been any releases to npm?

from postgres.

porsager avatar porsager commented on July 18, 2024 4

v3.4.4 released

from postgres.

porsager avatar porsager commented on July 18, 2024 2

You can install from github by using porsager/postgres#commithash

from postgres.

Jarred-Sumner avatar Jarred-Sumner commented on July 18, 2024 2

The fix for this will land in Bun v1.1.7, which we aim to release in a few hours

from postgres.

porsager avatar porsager commented on July 18, 2024 1

You should go thumb up that issue on bun ;) oven-sh/bun#7325

from postgres.

amjed-ali-k avatar amjed-ali-k commented on July 18, 2024

@porsager Kindly release new version to npm. or a beta version.

from postgres.

porsager avatar porsager commented on July 18, 2024

I have the same issue. Seems to be fixed in November in #738 but there hasn't been any releases to npm.

@porsager is there any reason there hasn't been any releases to npm?

No other reason than limited time on my end 😔

from postgres.

evelant avatar evelant commented on July 18, 2024

@porsager a new bug may have been introduced, now when calling postgres.end({timeout: 30}) it never completes until the timeout on my Bun app

from postgres.

porsager avatar porsager commented on July 18, 2024

please test with node and let me know if there's an issue. If there is only an issue with bun you need to file it in the bun repo.

from postgres.

evelant avatar evelant commented on July 18, 2024

@porsager I'll see if I can reproduce with node, but at least on Bun this is definitely a regression between 3.4.3 and 3.4.4. I rolled back to 3.4.3 and the connection terminates instantly instead of waiting for the timeout.

from postgres.

porsager avatar porsager commented on July 18, 2024

right, the "workaround" solving the previous bun error probably shouldn't have been made, and instead solved in bun instead 😅

So from now on I'm not taking bug reports from bun anymore 😜 Bun has stated "many" times, that things working in node should work in bun, and bug reports should go to the bun repo then.

from postgres.

amjed-ali-k avatar amjed-ali-k commented on July 18, 2024

@porsager
seems that "workaround" might be the issue. getting this so frequently now.

Bun 1.1.0 | PostgresJs 3.4.4 | drizzle-orm 0.30.6

image

from postgres.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.