-
Notifications
You must be signed in to change notification settings - Fork 59
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
Version/service #961
Version/service #961
Conversation
4d0cf6f
to
c829ff4
Compare
db72969
to
8de9732
Compare
35d318b
to
ad5fa7e
Compare
3b1693f
to
98dea9f
Compare
core/version/src/github.rs
Outdated
Err(e) => log::error!("Storing new Yagna release {} to DB. {}", rel, e), | ||
Ok(r) => { | ||
counter!("version.new", 1); | ||
log::warn!("{}", ReleaseMessage::Available(&r)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like the idea of claiming pinger
responsibility here. It can result in ugly spamming of log more frequently than defined by interval in pinger
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will be invoked:
- every 24h by
worker
- on every start
- manually via
yagna version check
It will immediately inform the user (via logs) that there is new version. This immediate notification was my goal here.
The same message will be logged by pinger
every 30mins.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So every 24h we will get double logs from pinger and worker?
No description provided.