Seve - i suspect bun 1.2.22 introduced some cha...
i suspect bun 1.2.22 introduced some changes that cause a lot of segmentation faults
9 Replies
there's a bunch of code that's basically no longer working on the backend and we can't update the backend (CC @DOPΣ this is why we don't have some of those org updates)
bun is not working from me , some sharp error
yea it's pretty bad
in core and other repos
fml, yea we can't pause development but this means rewriting every workflow to fix the bun version unless they patch this fast
can u check #Abse - @Seve I'
Though I would report to bun! They are asking for a minimal reproduction environment or script, but the segfaults are so random, and the stack trace is also random every time!
yea i reported it but i can't give them a simple repro, even though i can consistently get it on our backend
the backend is so complex that the repro takes a ton of setup
which version of the bun are you gus using, I am still getting crash in version 1.2.20 the latest is 1.2.24
it's working agian, just had to remove the node_modules from the latest bun version
We are now getting test failures because of this issue https://github.com/tscircuit/eval/pull/1079. I suggest bringing the bun version down to 1.2.20, that is what I tested on, and it worked!