Diagnostic text and logs

When DataMind Oda reports something technical, the text it shows you is already written in Oda's own wording. This page covers what is rewritten, where the rewrites apply, and where the original text is kept.

What is rewritten

The rewrites cover the software's own names, its paths and the place it was built in. They run in a fixed order, so a line can pass through several of them.

• Parts of the software. A part of Oda reads as oda/<name>. A message about a part that cannot be loaded therefore reads like Cannot find package 'oda/browser-use'.
• Paths. A path that points inside the installed software is shortened to the part inside it, written with forward slashes. Folders that only exist on your computer are dropped.
• Build locations. A line that points into the place where Oda was built keeps only the file name and its position: at resolveBareSpecifier (sea-main.js:3001:14).
• Labels. A leading label that carried the command's own name is removed from the line. A label that names a part of the software appears in Oda's wording, as in oda/api-remotes: failed.
• The software's own name. A word that named the software on its own is written as oda, Oda or ODA, matching its capitalisation. A launch failure reads spawn oda ENOENT, a trace flag reads --oda-trace, and a profile name reads oda.profile. Longer words that merely contain the letters are left as they are.

Where the rewording applies

• Where you read or copy. Messages, failure output and details you copy are shown in Oda's wording. It is a display change only: the rewrite never changes what Oda does.
• Not to models or logs. Text that goes to a model is not passed through the rewrite, and the log files Oda keeps on your computer keep the original wording.
• Stable when repeated. Text that is already in Oda's wording is not changed again, so the same problem shows the same wording every time.
• Kept as they are. Names of models, and the addresses that identify model services, keep their spelling.

Reading the text you see

1. Keep the message exactly as it appears. What you see is already in Oda's wording, so it needs no cleaning up before you report it.
2. Expect oda/<name> for parts of the software, shortened paths, and build locations reduced to a file name and position. These short forms are normal in shown text.
3. If you need the original wording to compare, the log files on your computer keep it. A difference between the two in names and paths is expected.

Failure output when Oda starts is written the same way; Startup and diagnostics covers how to read a failed start.

Questions, answered

Why does a failure line say spawn oda ENOENT?

A program Oda tried to start was not found by the system; ENOENT is the short code for that. The word oda is the software's own name, written in Oda's wording because it stood alone. Keep the line exactly as shown when you report it.

Why do names like --oda-trace and oda.profile carry Oda's name?

By the same rule: a single word that named the software is written as oda, Oda or ODA. A flag therefore reads --oda-trace and a profile name reads oda.profile. The rest of the name is unchanged, and longer words that merely contain the letters are left as they are.

Why is the command's name missing from the start of a line?

A label that carried the command's own name at the start of a line is removed before the text is shown. The rest of the line is unchanged, so nothing else about the message is affected.

Why is technical text rewritten at all?

The text comes from inside the app and carries the software's internal names and build locations, which only mean something inside the software. Before you read or copy it, those names are put into Oda's own wording, so a message you keep or report uses the same names the product does.

If the same problem happens again, will the text look the same?

Yes. The rewrite is stable: text that is already in Oda's wording is not changed again, and repeating the same action shows the same wording.

I need a message's original wording. Where does it stay?

The log files Oda keeps on your computer are not rewritten, so the original wording stays there. The app always shows the reworded form, so a difference between a message and the same entry in a log file is expected; keep the app's form as shown when you report it.

A message says Oda must be updated. What do I do?

Take the update from the notice (Update now); the notice carries the link that opens the update dialog. If it will not install, the steps are in Update DataMind Oda; update, sign-in and access messages are collected on Updates and troubleshooting.