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

reduce log frequency #772

Merged
merged 1 commit into from
Mar 21, 2020
Merged

reduce log frequency #772

merged 1 commit into from
Mar 21, 2020

Conversation

rberrelleza
Copy link
Member

When a sync goes wrong, this line gets logged once every 100 milliseconds, making the logs hard to parse. I think having one log every 10 seconds should be enough for diagnosis.

Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
@codecov
Copy link

codecov bot commented Mar 20, 2020

Codecov Report

Merging #772 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #772      +/-   ##
==========================================
- Coverage   31.99%   31.99%   -0.01%     
==========================================
  Files          62       62              
  Lines        4819     4820       +1     
==========================================
  Hits         1542     1542              
- Misses       3158     3159       +1     
  Partials      119      119              
Impacted Files Coverage Δ
pkg/syncthing/syncthing.go 0.57% <0.00%> (-0.01%) ⬇️

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 e3c2fb5...5fd68eb. Read the comment docs.

@rberrelleza rberrelleza merged commit 2344cb5 into master Mar 21, 2020
@rberrelleza rberrelleza deleted the reduce-log-frequency branch March 21, 2020 00:18
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.

None yet

2 participants