Skip to content

[BUG]: Uncaught exception in Bun shell #231

Description

@philmillman

dmno version

0.0.39

Steps to reproduce

hello.ts

import { $ } from "bun";

await $`dmno run -- echo "hello"`

This works fine:
bun run ./hello.ts

This does not:

dmno run -- bun run ./hello.ts

Obviously we want the second option to make use of the single dmno server, otherwise, if our ts file becomes:

import { $ } from "bun";

await $`dmno run -- echo "hello"`
await $`dmno run -- echo "hello2"`
// Parallel fun!
$`dmno run -- echo "hello3"`
$`dmno run -- echo "hello4"`

They're all spinning up dmno servers!

What is expected?

A single dmno server

What is actually happening?

multiple servers

System Info

bun: 1.2.19

Any additional comments?

Looks like Bun.spawn (And I imagine nodejs process spawning) doesn't have this issue.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions