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

bug: Run History UI Error #8037

Closed
5 tasks done
AAEE86 opened this issue Sep 6, 2024 · 1 comment · Fixed by #8062
Closed
5 tasks done

bug: Run History UI Error #8037

AAEE86 opened this issue Sep 6, 2024 · 1 comment · Fixed by #8062
Assignees
Labels
🐞 bug Something isn't working

Comments

@AAEE86
Copy link
Contributor

AAEE86 commented Sep 6, 2024

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • 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.8.0-beta1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This bug occurs when the file name in the knowledge base is too long.
QQ截图20240906095858

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Copy link

dosubot bot commented Sep 6, 2024

The Run History UI in the Dify codebase is implemented in the web/app/components/workflow/header/run-and-history.tsx file. Specifically, it is handled by the ViewHistory component within the RunAndHistory component [1].

Regarding the issue with long file names in the knowledge base, there is no specific information available in the repository about error handling mechanisms for long file names [1][2]. You might need to investigate further or implement a custom solution to handle this scenario.

To continue talking to Dosu, mention @dosu.

@dosubot dosubot bot added the 🐞 bug Something isn't working label Sep 6, 2024
@crazywoola crazywoola assigned crazywoola and YIXIAO0 and unassigned crazywoola Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants