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

Can not display parameters for models in v1.0.0 #14556

Open
5 tasks done
lyc280705 opened this issue Feb 28, 2025 · 3 comments
Open
5 tasks done

Can not display parameters for models in v1.0.0 #14556

lyc280705 opened this issue Feb 28, 2025 · 3 comments
Labels
🐞 bug Something isn't working

Comments

@lyc280705
Copy link

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Feb 28, 2025
@lyc280705
Copy link
Author

It just keeps loading.

Copy link

dosubot bot commented Feb 28, 2025

In Dify version 1.0.0, there is a known issue related to the display of model parameters where the frontend uses base 1000 instead of base 1024 for calculating the 'k' display format. This results in displaying 131072 as 131k instead of the expected 128k. However, this is purely a display issue and does not affect the actual functionality of the system [1].

For the issue of UI elements that keep loading, there isn't specific information available about common causes or troubleshooting steps for this problem in a self-hosted Docker setup. It might be helpful to check the network requests in the browser's developer tools to see if there are any failed requests or errors in the console that could provide more insight into the issue. Additionally, ensuring that all services are running correctly in the Docker setup and checking the logs for any errors might help identify the problem.

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

@lyc280705
Copy link
Author

Can not use LLM either: Run failed: PluginDaemonInternalServerError: killed by timeout

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

No branches or pull requests

2 participants