MGS1040: magus.yaml has a key this magus does not know
A config file carries a key the running magus does not recognize, and every command stops before it loads the workspace:
[MGS1040] magus.yaml has keys this magus does not know:
- env (lines 16, 21, 26)
- concurrencyy (line 3; did you mean "concurrency"?)
This magus (v0.4.3) is older than the workspace needs (>= 0.4.4).
Fix it:
- released binary: magus self update
see: https://eli.gladman.cc/magus/reference/codes/magusfile/MGS1040/
Each unknown key is listed once with every line it appears on, at every level of the file, not only the top. The version gap and its fixes are stated once, after the list.
Why
Until v0.5.0 an unknown key was a warning (config: unknown or unexpected keys in config file) and the load carried on without it. The value you wrote was dropped, and a
workspace that looked configured ran on the defaults. A value magus will not honor must
never look like one it applied, so the load now fails instead. A file that loaded under
v0.4.x with that warning fails under v0.5.0 with this code.
What to do
Read each key's line. It takes one of three forms:
-
did you mean "..."?The key is a near miss of one magus knows. Rename it:# before concurrencyy: 4 # after concurrency: 4 -
renamed to "..."magus still knows the setting under a new name. Rename the key. -
Line numbers only. Nothing known is close. Either the key belongs to a newer magus than the one running, so run one of the fixes listed after the keys (the message names this binary's version and the workspace's
required_version), or the key is not a magus setting at all and the fix is to delete it.
magus doctor reports the same keys under its config-file check without running
anything else. docs/reference/config lists every key magus reads.