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

[Access] Add compatible range to Node Version Info endpoint #6294

Conversation

UlyanaAndrukhiv
Copy link
Contributor

@UlyanaAndrukhiv UlyanaAndrukhiv commented Aug 5, 2024

Closes: #6248

Related PRs:

Context

In this PR :

  • RPC and REST NodeVersionInfo endpoint was updated to return the first and last block that the node's version supports.
  • Updated functional tests.

@codecov-commenter
Copy link

codecov-commenter commented Aug 5, 2024

Codecov Report

Attention: Patch coverage is 40.47619% with 25 lines in your changes missing coverage. Please review.

Project coverage is 41.46%. Comparing base (b93c60f) to head (00eae08).

Files with missing lines Patch % Lines
engine/common/version/version_control.go 0.00% 10 Missing ⚠️
access/api.go 0.00% 6 Missing ⚠️
cmd/access/node_builder/access_node_builder.go 0.00% 4 Missing ⚠️
cmd/observer/node_builder/observer_builder.go 0.00% 4 Missing ⚠️
access/handler.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #6294      +/-   ##
==========================================
- Coverage   41.47%   41.46%   -0.01%     
==========================================
  Files        2017     2017              
  Lines      143768   143785      +17     
==========================================
- Hits        59622    59619       -3     
- Misses      77972    77990      +18     
- Partials     6174     6176       +2     
Flag Coverage Δ
unittests 41.46% <40.47%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@UlyanaAndrukhiv UlyanaAndrukhiv marked this pull request as ready for review August 6, 2024 08:39
Copy link
Collaborator

@Guitarheroua Guitarheroua left a comment

Choose a reason for hiding this comment

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

Looks good for me!

Have a minor comment about the naming of the fields on https://github.com/onflow/flow PR, so the same goes here.

Copy link
Contributor

@peterargue peterargue left a comment

Choose a reason for hiding this comment

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

looks like I forgot to submit my review a few days ago 😅 . sorry for the delay

model/flow/node_version_info.go Outdated Show resolved Hide resolved
engine/common/rpc/convert/compatible_range.go Outdated Show resolved Hide resolved
engine/common/version/version_control.go Outdated Show resolved Hide resolved
engine/common/version/version_control.go Outdated Show resolved Hide resolved
engine/access/rpc/backend/backend_network.go Show resolved Hide resolved
engine/access/rpc/backend/backend.go Outdated Show resolved Hide resolved
engine/access/rpc/backend/backend.go Outdated Show resolved Hide resolved
engine/access/rpc/backend/backend_test.go Show resolved Hide resolved
@peterargue peterargue self-requested a review August 28, 2024 15:50
peterargue
peterargue previously approved these changes Aug 28, 2024
@peterargue peterargue dismissed their stale review August 28, 2024 22:20

re-approve after fixing conflicts

@peterargue
Copy link
Contributor

@UlyanaAndrukhiv looks good. Please fix conflicts, then I'll approve and merge

@peterargue peterargue added this pull request to the merge queue Aug 29, 2024
Merged via the queue into onflow:master with commit 51a9497 Aug 29, 2024
55 checks passed
@peterargue peterargue deleted the UlyanaAndrukhiv/6248-compatible-range-to-node-version branch August 29, 2024 14:17
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.

[Access] Add compatible range to Node Version Info endpoint
4 participants