[询问] 方舟豆包依赖pydantic和fschat冲突

[china-gcg]

在更改使用方舟的调用方式，为了调用豆包，他更新调用了方式，导致使用pydantic，他要在2.x。但是由于项目的冲突依赖，会卡住

有没有大佬有建议

[dosubot]

To address the dependency conflict between Pydantic required by your project and the syntax error you're encountering, follow these steps:

1. Resolve Dependency Conflict:

   • Update requirements_lite.txt to use Pydantic version 2.x by changing pydantic==1.10.13 to pydantic>=2.0.0. This change assumes backward compatibility with your current usage. Be cautious as this upgrade may impact other dependencies like fastapi and starlette, which rely on Pydantic for data validation and serialization.

2. Fix "Unexpected EOF while parsing" Error:

   • This error usually indicates a missing parenthesis, bracket, quote, or incorrect indentation. Review your code for incomplete statements and ensure all structures are properly closed. Tools like flake8 or pylint can help identify syntax errors.

For the dependency conflict, consider the impact of upgrading Pydantic on your project, especially regarding fastapi and starlette. For the syntax error, without specific code, the advice is to check for common syntax issues or use a linter for more precise error identification.

Details

Sources

• requirements_lite.txt
• requirements.txt
• server/agent/tools/search_knowledgebase_complex.py

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[china-gcg]

不用了，我自己解决了

[flyuuo9]

@china-gcg 请问下如何解决的，方便分享一下吗？我想加openparse进来，也是依赖了pydantic 2

[china-gcg]

额，他是方舟3升级了，我用原本的方式搭建搭建进去的，也是没有解决这个问题

…

---- 回复的原邮件 ---- | 发件人 | ***@***.***> | | 日期 | 2024年05月30日 11:20 | | 收件人 | ***@***.***> | | 抄送至 | ***@***.***>***@***.***> | | 主题 | Re: [chatchat-space/Langchain-Chatchat] [询问] 方舟豆包依赖pydantic和fschat冲突 (Issue #4033) | @china-gcg 请问下如何解决的，方便分享一下吗？我想加openparse进来，也是依赖了pydantic 2 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>