dify icon indicating copy to clipboard operation
dify copied to clipboard

problem with log detail, long detail can't show on the right side

Open guowei-3399 opened this issue 11 months ago • 2 comments

Self Checks

  • [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
  • [x] I have searched for existing issues search for existing issues, including closed ones.
  • [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

can't scoll down anymore for more detial.

✔️ Expected Behavior

can scoll down all logs, that we can find more logs

❌ Actual Behavior

No response

guowei-3399 avatar Apr 02 '25 02:04 guowei-3399

Hello @guowei-3399! I'm here to help you with any bugs, questions, or contributions. Let's work on resolving the issue you've encountered.

The issue you're experiencing with the log detail interface not allowing you to scroll down to view more details might be related to the implementation of the scrolling functionality. In Dify, the scrolling is managed using the react-infinite-scroll-component library, which should dynamically load more data as you scroll down [1].

Here are a few things you can check or try to resolve the issue:

  1. Check the hasMore Property: Ensure that the hasMore property in the InfiniteScroll component is set correctly. This property determines whether more data should be loaded when you reach the bottom of the scrollable area.

  2. Verify the fetchData Function: Make sure that the fetchData function is correctly implemented and capable of fetching additional log details when called.

  3. CSS and Styling: Review the CSS rules applied to the log detail interface. Specifically, check for any styles that might restrict the height or overflow properties of the container, such as overflow-hidden or fixed heights that could prevent scrolling [2][3].

  4. Known Issues: There was a known issue in a previous version of Dify where not all parallel node executions were displayed in the workflow logs. Although this was fixed in a later version, ensure that your current version (1.1.0) includes this fix [4].

If these steps do not resolve the issue, consider checking for any updates or patches that might address this problem in newer versions of Dify.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

dosubot[bot] avatar Apr 02 '25 02:04 dosubot[bot]

hey @guowei-3399, can you please provide me more detailed breakdown of steps to reproduce this error?

ikunal-04 avatar Apr 02 '25 11:04 ikunal-04

Hi, @guowei-3399. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You reported an issue with long log entries not being fully visible in the self-hosted version 1.1.0 using Docker.
  • Suggestions were made to check the hasMore property, verify the fetchData function, and review CSS styles for scrolling issues.
  • A request was made for a more detailed breakdown of steps to reproduce the error.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting on the issue.
  • If there is no further activity, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

dosubot[bot] avatar May 03 '25 16:05 dosubot[bot]