TEN-framework / TEN-framework/ten-framework
[BUG]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
Description
thread 'actix-server worker 8' (11876) panicked at /home/runner/work/ten-framework/ten-framework/core/src/ten_rust/src/graph/connection/mod.rs:170:46:
called Result::unwrap() on an Err value: the type of the node must be one of extension/subgraph/selector
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Received interrupt signal, cleaning up workers...
exit status 134
Environment
Docker
Steps to reproduce
TMAN 中当添加一条 cmd命令但是NODE 没有选择时点提交 ，会直接崩溃。
Expected behavior
应该提示没有选择节点吧？
Severity
Critical
Additional Information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at core/src/ten_rust/src/graph/connection/mod.rs:170 and reproduce the crash in Docker through TMAN by submitting a cmd command without selecting a node. Check the surrounding graph connection handling and verify that the submission reports the missing node instead of terminating the worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100