Pickles refused however they come; a string temperature passes again
CI / test (push) Failing after 7m17s
CI / test (push) Failing after 7m17s
From review. A mirror set already on the node is looked at again, not trusted for having been fetched once; Pickled cuts a query or a fragment from any source, hf: too; .pt2 is a pickle. The flag check reads a flag as the engine does: underscores as dashes and any beginning of a refused flag as that flag, since argparse takes --trust-remote for --trust-remote-code; SGLang refuses --load-format, which would undo the agent's safetensors. TripoSR's preset says allow_pickle: without it the preset could not be added and the presets pass failed on it each time. A shared ComfyUI environment's hidden entry takes its first member's allow_pickle, as it takes its source. The GenAI trace attributes made temperature and top_p typed fields of the request's parse, so "0.7" as a string was a 400; they are read loosely, as they are read only for the trace. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
44451bacd9
commit
fd94265e08
12 files changed
+124
-10
No files matched your search
+4
-2
@@ -891,8 +891,9 @@ files were checked, can say so:
|
||||
allow_pickle: true
|
||||
```
|
||||
|
||||
A file put on the machine by hand, as a path, is the operator's own and is not
|
||||
looked at.
|
||||
A local path is judged by its name as any source is; a local directory is
|
||||
not looked into, nor a model an engine downloads itself other than by its
|
||||
Hugging Face id (an adapter by id, TensorRT-LLM's checkpoints).
|
||||
|
||||
Put them where the node can read them. `scp`, a shared filesystem, or the
|
||||
engine's own downloader are all valid, and which you want depends on how many
|
||||
@@ -2326,6 +2327,7 @@ triposr`. What that adds is this entry, and its workflow is built in:
|
||||
```yaml
|
||||
- name: triposr
|
||||
source: hf:stabilityai/TripoSR/model.ckpt
|
||||
allow_pickle: true # published as this checkpoint only
|
||||
comfyui:
|
||||
workflow: triposr # built in; a model of your own names a JSON file on every control plane
|
||||
output: meshes
|
||||
|
||||
Reference in new issue
Block a user