-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
[Bug Report] Bugs of JinaAPI and HTTP error #9623
Comments
@pprp 你好! 我是Dosu,一个可以帮助你解决 bug、回答问题并成为贡献者的机器人。我会帮你等待人类维护者的过程中。 For the issues you're experiencing with Dify, here are some relevant insights and potential solutions:
These steps should help address the issues you're facing with Dify. If the problems persist, further investigation into the specific configurations and logs might be necessary. |
If the key is changed, you need to remove the credentials in jina reader tool and add it again.
Please provide the DSL. |
@crazywoola how to remove the credential? I have updated the key in these two places. |
Hi, I'm Jina AI's engineer. After some checking with @pprp We found the place that made the confusion: the credentials of DataSource, Model(Provider), Tools are managed separately. And Jina have all of them, unfortunately. Wondering if you have some advice or plan to solve this kind of problem.🤔 |
@crazywoola for the 3rd bug, here is the dsl file:
Taking this input as example: https://mp.weixin.qq.com/s/XO7Qb6LlYPr7frxuJw2BuA here is the final output: Here are urls in the output of LLM. Unfortunatelly, there is no image shown as below: |
@crazywoola For the 2nd bug, here is the code for testing locally:
This is the test result: here is how to use it in dify: We got output:
It is so odd. Why can't I open this url? Additionally, there is other person who has the same issue as Bug3: |
@crazywoola is there any progress? Now, the second bug is fixed using python. But the 3rd bug still exists. |
For bug 3, I think you could use some nodes to extract the url and display it. But if you want to get the url from the uploaded file, please take a look at this. #9567 |
Self Checks
Dify version
0.10.0
Cloud or Self Hosted
Cloud
Steps to reproduce
Bug1: Jina error. I found that Dify can not update the Jina api properly. When my Jina API is out of tokens, I bought some tokens and update the API key. However, I find Dify still remembers the old API key so that Jina can not run and just give bugs:
Bug2: HTTP request. I am using imgrender api which is implemented using HTTP Request node in Dify. This API is properly tested on local device using python to get http results. Today, I just find that the returned img urls can not be open. (Also, it worked fine yesterday on dify.) I am sure that this bug has no relation with imgrender.
Bug3: I have both image and text in the output file. However, there is only text being shown. The images are now properly shown. For example, the figure below is have image link but it can not properly shown in the output.
✔️ Expected Behavior
Bug 1: After the Jina API is set, it can operate properly.
Bug 2: Please resolve the HTTPS error. As it can run locally, it should also function well on dify.
Bug 3: I wish to ensure that the image is displayed properly.
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: