Skip to content

setTime always be 0 #43

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

Merged
merged 3 commits into from
Aug 27, 2019
Merged

Conversation

waterandair
Copy link
Contributor

No description provided.

@codecov-io
Copy link

codecov-io commented Aug 18, 2019

Codecov Report

Merging #43 into master will increase coverage by 0.17%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
+ Coverage   78.57%   78.74%   +0.17%     
==========================================
  Files          11       11              
  Lines        1148     1148              
==========================================
+ Hits          902      904       +2     
+ Misses        180      178       -2     
  Partials       66       66
Impacted Files Coverage Δ
naming/client.go 73.19% <0%> (+0.51%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f112a9e...1c7e8fc. Read the comment docs.

@@ -309,7 +309,7 @@ func (a *App) Set(changes *ArgSet) (ok bool) {
defer a.lock.Unlock()
var (
dst *Instance
setTime int64
setTime = time.Now().UnixNano()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这里之前漏了个判断,直接改为下面这样吧

	if changes.SetTimestamp == 0 {
		setTime = time.Now().UnixNano()
	}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

改好啦,是这样吧?

@lintanghui lintanghui merged commit 1b54000 into bilibili:master Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants