Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The error encountered when the Chunker option is set to Code. #270

Open
redkit75 opened this issue Sep 4, 2024 · 2 comments
Open

The error encountered when the Chunker option is set to Code. #270

redkit75 opened this issue Sep 4, 2024 · 2 comments
Labels
investigating Bugs that are still being investigated whether they are valid

Comments

@redkit75
Copy link

redkit75 commented Sep 4, 2024

Hello,

On the Import Config page, when I select the Chunker option as Code, I choose either the Python or PHP option. Then, I select a file with the .py or .php extension according to my choice, and when I perform the import, I get the following error. I wonder if this error is related to LangChain? I feel like I might be missing something that needs to be done, but I also wanted to report it in case it might be a issue.

Import for framework.py failed: '>' not supported between instances of 'int' and 'str' | 0


✔ Collected all Batches of framework.py
ℹ Removing framework.py from BatchManager
ℹ Found existing Client
ℹ FileStatus.STARTING | framework.py | Starting Import | 0
ℹ Loading framework.py (py)
ℹ FileStatus.LOADING | framework.py | Loaded framework.py | 0.14
ℹ FileStatus.CHUNKING | framework.py | | 0
ℹ FileStatus.ERROR | framework.py | Import for framework.py failed: '>'
not supported between instances of 'int' and 'str' | 0.0
✘ No documents imported 0 of 1 succesful tasks
ℹ FileStatus.ERROR | framework.py | Import for framework.py failed:
Import for framework.py failed: '>' not supported between instances of 'int' and
'str' | 0

@thomashacker
Copy link
Collaborator

Thanks for the issue, I'll look into it!

@thomashacker thomashacker added the investigating Bugs that are still being investigated whether they are valid label Sep 13, 2024
@redkit75
Copy link
Author

It is clear that this is definitely a bug. Could you update the status as a bug? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating Bugs that are still being investigated whether they are valid
Projects
None yet
Development

No branches or pull requests

2 participants