Passing torch tensor to encoder leads to hang
Open
Nobody has claimed this yet.
bug
- Dominant language
- Jupyter Notebook
- Stars
- 159
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Version
0.5.0
Describe the bug.
If you pass torch tensor to encoder the system will just hang indefinitely. i think it is better to at least throw exception or maybe convert it to cupy array under the hood
Minimum reproducible example
Environment details
Relevant log output
Other/Misc.
No response
Check for duplicates
- I have searched the open bugs/issues and have found no duplicates for this bug report
Contributor guide
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 the encoder entry point that accepts a torch tensor and reproduce the indefinite hang using a minimal tensor input; the issue provides no usable example, environment, logs, file, or test. Determine whether the expected resolution is an exception or conversion to a CuPy array, then add coverage showing that passing a torch tensor terminates with the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- pytorch
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100