ALC-9005: Internal error

Something failed in a way Alcuin did not expect. This is a bug in Alcuin, not something you did wrong.

What you see

The message appears where you made the request: in a query tab’s result area, in a panel, or in a toast. It is the raw text of the failure, so it reads like a programmer’s note, for example count returned no row, or a JavaScript error such as Cannot read properties of undefined.

Errors from Postgres itself are not this code. They carry their own SQLSTATE, which the Postgres error codes appendix explains.

Why it happens

• A bug in Alcuin: a case the code did not handle.
• A network failure reported in a way Alcuin does not recognize. The usual socket errors, such as ECONNRESET or ETIMEDOUT, are ALC-1002 instead.

What to do

1. Try again. If the network was the cause, it may work the second time.
2. If it happens again, choose Help → Save Diagnostics Bundle… (also in the command palette as Save a diagnostics bundle…) and save the file. When the failure is an unexpected JavaScript error, the engine writes where it happened to its log, without the message, so the bundle helps.
3. Read the bundle before you share it. Logs and the diagnostics bundle lists what it holds.
4. Open an issue at Alcuin’s GitHub issues. Include:
   • the exact message,
   • what you clicked or ran, and in which view,
   • your Postgres version and your operating system,
   • the bundle.

Copy error in a query tab copies the code, the internal name and the message, ready to paste: ALC-9005 (ENGINE_INTERNAL): and then the message.

Internal name

The engine reports this as ENGINE_INTERNAL. Quote either name in an issue.