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]: Attu up_time is negative #32993

Open
1 task done
ccinv opened this issue May 11, 2024 · 1 comment
Open
1 task done

[Bug]: Attu up_time is negative #32993

ccinv opened this issue May 11, 2024 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ccinv
Copy link

ccinv commented May 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.4.1-79-g36f1ea93a
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): Ubuntu
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

image

Expected Behavior

In this case, up_time is less than 5 minutes.

Steps To Reproduce

Just clone the latest version of milvus and attu and connect.

Milvus Log

No response

Anything else?

Attu can't parse monotonic clock(m+=) in output of Time.string().
"created_time": "2024-05-11 20:05:21.922713137 +0800 CST m=+6.750931297", "updated_time": "2024-05-11 20:05:21.922713375 +0800 CST m=+6.750931533",
Another build from release works fine
"created_time": "2024-05-11 12:14:32.023107697 +0000 UTC", "updated_time": "2024-05-11 12:14:32.023109206 +0000 UTC",
Maybe it's the go version, idk, but add .Round(0) to

CreatedTime: paramtable.GetCreateTime().String(),
UpdatedTime: paramtable.GetUpdateTime().String(),

can eliminate this problem.

@ccinv ccinv added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 11, 2024
@yanliang567
Copy link
Contributor

/assign @shanghaikid
/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants