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

[Merged by Bors] - don't track latency for messages that are not gossipped futher #5064

Closed
wants to merge 6 commits into from

Conversation

dshulyak
Copy link
Contributor

@dshulyak dshulyak commented Sep 22, 2023

this is mainly to prevent duplicates from skewing results.
hare1 is not fixed in this change
latency metering is dropped for atx protocol, as we don't have good reference for it

closes: #4623

this is mainly to prevennt duplicates from skewing results
activation/handler.go Outdated Show resolved Hide resolved
@dshulyak
Copy link
Contributor Author

bors merge

bors bot pushed a commit that referenced this pull request Sep 28, 2023
this is mainly to prevent duplicates from skewing results. 
hare1 is not fixed in this change
latency metering is dropped for atx protocol, as we don't have good reference for it

closes: #4623
@bors
Copy link

bors bot commented Sep 28, 2023

Build failed:

@dshulyak
Copy link
Contributor Author

bors merge

bors bot pushed a commit that referenced this pull request Sep 28, 2023
this is mainly to prevent duplicates from skewing results. 
hare1 is not fixed in this change
latency metering is dropped for atx protocol, as we don't have good reference for it

closes: #4623
@bors
Copy link

bors bot commented Sep 28, 2023

Build failed:

@dshulyak
Copy link
Contributor Author

bors cancel

@dshulyak
Copy link
Contributor Author

bors merge

bors bot pushed a commit that referenced this pull request Sep 28, 2023
this is mainly to prevent duplicates from skewing results. 
hare1 is not fixed in this change
latency metering is dropped for atx protocol, as we don't have good reference for it

closes: #4623
@codecov
Copy link

codecov bot commented Sep 28, 2023

Codecov Report

Merging #5064 (609f26c) into develop (fe23c05) will decrease coverage by 0.1%.
The diff coverage is 100.0%.

@@            Coverage Diff            @@
##           develop   #5064     +/-   ##
=========================================
- Coverage     77.1%   77.1%   -0.1%     
=========================================
  Files          257     257             
  Lines        30307   30287     -20     
=========================================
- Hits         23371   23354     -17     
+ Misses        5411    5408      -3     
  Partials      1525    1525             
Files Coverage Δ
activation/handler.go 78.2% <ø> (-0.3%) ⬇️
beacon/handlers.go 86.3% <100.0%> (-0.4%) ⬇️
beacon/weakcoin/handler.go 87.2% <100.0%> (-0.8%) ⬇️
proposals/handler.go 87.5% <100.0%> (-0.1%) ⬇️

... and 4 files with indirect coverage changes

@bors
Copy link

bors bot commented Sep 28, 2023

Pull request successfully merged into develop.

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot changed the title don't track latency for messages that are not gossipped futher [Merged by Bors] - don't track latency for messages that are not gossipped futher Sep 28, 2023
@bors bors bot closed this Sep 28, 2023
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.

metrics: record latency only if object waasn't processed before
3 participants