Uncaught errors appear as empty strings in logs #230

New issue

Closed

opened 2026-07-19 02:33:21 +00:00 by TenType · 0 comments

TenType commented

2026-07-19 02:33:21 +00:00

(Migrated from codeberg.org)

Steps to Reproduce

Open any command file, say, ping.ts. Insert a line that throws an error, such as

throw new Error("up");

or even

throw "up";

Run the command. In logs, we get the line Error executing command: (with nothing after it).

We should get some sort of object or message that contains "up" instead of empty output.

Suspected Issue

These errors are detected in src/events/interactionCreate.ts. The bug is probably in line 37.

Line 57 and line 87 may also be affected by this issue.

### Steps to Reproduce Open any command file, say, `ping.ts`. Insert a line that throws an error, such as ```ts throw new Error("up"); ``` or even ```ts throw "up"; ``` Run the command. In logs, we get the line `Error executing command: ` (with nothing after it). We should get some sort of object or message that contains `"up"` instead of empty output. ### Suspected Issue These errors are detected in `src/events/interactionCreate.ts`. The bug is probably in [line 37](https://codeberg.org/ScottyLabs/dalmatian/src/commit/083ef0a7d7b0cfd31d13a4c9793435a6563f63fe/src/events/interactionCreate.ts#L37). [Line 57](https://codeberg.org/ScottyLabs/dalmatian/src/commit/083ef0a7d7b0cfd31d13a4c9793435a6563f63fe/src/events/interactionCreate.ts#L57) and [line 87](https://codeberg.org/ScottyLabs/dalmatian/src/commit/083ef0a7d7b0cfd31d13a4c9793435a6563f63fe/src/events/interactionCreate.ts#L87) may also be affected by this issue.