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

Running bun bun.lockb crashes on certain repo's #11535

Closed
cskiwi opened this issue Jun 2, 2024 · 5 comments · Fixed by #11545
Closed

Running bun bun.lockb crashes on certain repo's #11535

cskiwi opened this issue Jun 2, 2024 · 5 comments · Fixed by #11545
Assignees
Labels
bug Something isn't working

Comments

@cskiwi
Copy link

cskiwi commented Jun 2, 2024

What version of Bun is running?

1.1.12+43f0913c3

What platform is your computer?

Microsoft Windows NT 10.0.22621.0 x64

What steps can reproduce the bug?

I'm trying to figure out why my bun bun.lockb command crashes on certain repo's because this is causing an error when using nx, because they read the contents of the file for determening change detection.

Thread on nx's github: nrwl/nx#26053
Example package.json that doesn't work: https://gist.github.com/cskiwi/0791fbd77c3845327ec37f6e2222f912

What is the expected behavior?

That the bun bun.lockb would always have an output

What do you see instead?

he "nx/js/dependencies-and-lockfile" plugin threw an error while creating nodes from bun.lockb:
    Error: Command failed: bun <redacted>\bun.lockb
    ============================================================
    Bun v1.1.12 (43f0913c) Windows x64
    Args: "bun" "<redacted>\bun.lockb"
    Elapsed: 5ms | User: 0ms | Sys: 0ms
    RSS: 23.47MB | Peak: 23.47MB | Commit: 62.63MB | Faults: 5881
    
    panic(main thread): Internal assertion failure
    oh no: Bun has crashed. This indicates a bug in Bun, not your code.

    To send a redacted crash report to Bun's team,
    please file a GitHub issue using the link below:

     https://bun.report/1.1.12/wa143f0913AAghg+L+3pzIwi67F+8vC2mn1Fw7r1Fmty2Fqi4BiiJow6y+CA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg


        at genericNodeError (node:internal/errors:983:15)
        at wrappedFn (node:internal/errors:537:14)
        at checkExecSyncError (node:child_process:889:11)
        at execSync (node:child_process:961:15)
        at Array.exports.createNodes (<redacted>\node_modules\nx\src\plugins\js\index.js:40:44)
        at <redacted>\node_modules\nx\src\project-graph\plugins\utils.js:49:54
        at Array.map (<anonymous>)
        at runCreateNodesInParallel (<redacted>\node_modules\nx\src\project-graph\plugins\utils.js:47:34)
        at LoadedNxPlugin.createNodes (<redacted>\node_modules\nx\src\project-graph\plugins\internal-api.js:23:74)
        at createProjectConfigurations (<redacted>\node_modules\nx\src\project-graph\utils\project-configuration-utils.js:253:17

Additional information

This doesn't seem to happen on linux, but does on windows and most likely on mac (the user in thread did get some different errors, but might be related)

@cskiwi cskiwi added the bug Something isn't working label Jun 2, 2024
@dylan-conway dylan-conway self-assigned this Jun 2, 2024
@cskiwi
Copy link
Author

cskiwi commented Jun 7, 2024

@Jarred-Sumner Was this released already? Because I'm still having this issue on windows 11 (not on 10 though)
Running 1.1.12+43f0913c3

Tried:

  • Reinstalling bun
  • Running on the canary build

@Jarred-Sumner
Copy link
Collaborator

@cskiwi can you run bun upgrade --canary and try again?

@cskiwi
Copy link
Author

cskiwi commented Jun 7, 2024

@Jarred-Sumner not sure why it worked just now (tried with canary less then an hour ago), however it seems to be working now. Thanks!

@Jarred-Sumner
Copy link
Collaborator

is it possible you installed with scoop or npm or a package manager where you end with multiple copies of bun installed?

@cskiwi
Copy link
Author

cskiwi commented Jun 7, 2024

Not sure, installed bun some time ago for the first time. Might be that I changed methods. But it would be highly unlikely.

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

Successfully merging a pull request may close this issue.

3 participants