-
Notifications
You must be signed in to change notification settings - Fork 25
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
Fix Issues Related to Asset Library #919
Conversation
- limit the width of the asset item in the asset library - ellipsis the asset name if it is too long
Added a check logic before adding an asset to the database to avoid adding the same asset multiple times and causing duplication errors. If the asset already exists in the database, the add operation is not performed.
Hi @Gerrnperl. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Co-authored-by: qiniu-x[bot] <154984095+qiniu-x[bot]@users.noreply.github.com>
[Git-flow] Hi @Gerrnperl, There are some suggestions for your information: Rebase suggestions
Which seems insignificant, recommend to use For other If you have any questions about this comment, feel free to raise an issue here: |
Shows a loading animation after the animation is generated and before it is uploaded and displayed. Shows a tip to let users start motion recording to generate animation.
This PR addresses several issues related to asset library
Fixes:
Excessively long asset name causes the asset item to be the wrong size
Repeatedly adding assets to a project results in an error on the backend
Missing search suggestions for old assets
Duplicate asset item in Milvus database
Wrong temporarily calculated asset rate