You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
Dify version
0.15.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Create Knowledge-Upload file
Batch add Chunk Upload csv file
log of the api container:
/app/api/controllers/console/datasets/datasets_segments.py:371: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
data = {"content": row[0], "answer": row[1]}
✔️ Expected Behavior
No response
❌ Actual Behavior
Run batch failed
The text was updated successfully, but these errors were encountered:
@CN-P5 Hello there! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer.
The "Run batch failed" error you're encountering during the batch add process in Dify could be related to the deprecation warning in your logs. The warning indicates that the code is using Series.__getitem__ to access elements by position, which is deprecated. This could potentially lead to issues in future versions of pandas.
To address this, you should modify the code to use ser.iloc[pos] for accessing elements by position. This change will ensure compatibility with future versions of pandas and might resolve the batch process failure if it's related to this issue.
Here's a quick example of how you might adjust the code:
Make sure to review the rest of the code for similar issues and update them accordingly. This should help prevent any unexpected behavior due to deprecated methods.
Self Checks
Dify version
0.15.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
log of the api container:
✔️ Expected Behavior
No response
❌ Actual Behavior
Run batch failed
The text was updated successfully, but these errors were encountered: