effect's Cause.UnknownException causes issues

[m-radmacher]

What version of Bun is running?

1.1.20+ae1948925

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What steps can reproduce the bug?

Run this script using Bun (you'll need to have the effect@3.5.3 package installed:

import { Config, Console, Effect, Redacted } from "effect";

const getJson = ({ url }: { url: string }) =>
    Effect.tryPromise(() =>
        fetch(url).then((res) => {
            if (!res.ok) {
                console.log("error");
                throw new Error(res.statusText);
            }
            console.log("ok");
            return res.json() as unknown;
        }),
    ).pipe(
        Effect.retry({ times: 2 }),
        Effect.timeout("4 seconds"),
        Effect.catchAll(Console.error),
    );

const program = Effect.gen(function* () {
    const host = "https://dummyjson.com/auth/products/1?delay=1000";

    const unknownResponse = yield* getJson({
        url: host,
    });

  console.log(unknownResponse);
});


Effect.runPromise(program);

What is the expected behavior?

I expected to see an error message and a stack trace.

What do you see instead?

$ bun --watch src/test.ts
error
error
error
[custom formatter threw an exception] <---- this is unexpected
undefined

Additional information

One of the effects members asked me to open this issue to cross-reference. You can find the issue in their repository here: Effect-TS/effect#3270

[190n]

This is happening because some object has a [util.inspect.custom] function which throws. In Bun, passing such an object to util.inspect will throw the error (which is how it works in Node.js too), but using any console functions (or Bun.inspect, but I don't think effect uses that anywhere) will swallow the error and print the message you're seeing.

Do you have a smaller reproduction that doesn't use effect, or could you point me to the part of effect that is creating/logging this object?

[m-radmacher]

I do have a smaller reproduction:

console.error(new Cause.UnknownException(new Error("Foo")))

It also seems that my issue was closed as completed in the effect repository with this PR: Effect-TS/effect#3295

But since that hasn't been released on npm yet, I haven't tried it.