docs(spec): presets record themselves in exdata.meta; job-labels backlog item
- no preset field on the server: the client puts preset name + hash into the job's exdata JSON under 'meta', passed through uninterpreted; the worker skips 'meta' silently; 'preset report' filters jobs client-side - drop the local submission log idea - job-labels: independent backlog item (general server-side labels) - bug-1970: note the dropped REST 'tags' field Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
5cfe64218c
commit
a68d2fc965
5 changed files with 40 additions and 12 deletions
|
|
@ -51,6 +51,8 @@ the run limit gets a success reply and a job that does none of it.
|
|||
**Found by:** review during the `application-profile` brief discussion
|
||||
(extra v1 attributes), 2026-10-12.
|
||||
|
||||
UPDATE (2026-10-12): The REST submit model's `Tags []string` (`json:"tags"`, models/jobs.go JobSubmitRequest) is also accepted and dropped: nothing outside models/ reads it, and it is not in preCheckSubmitOptions(). Roadmap item job-labels would reuse or replace it.
|
||||
|
||||
## Environment
|
||||
- OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
|
||||
- libc: n/a: found by source reading, no binary run (host ldd reports glibc 2.40)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue