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

Fixed compatibility checks with pre-release versions #1730

Merged
merged 2 commits into from
Apr 10, 2024

Conversation

Raalsky
Copy link
Contributor

@Raalsky Raalsky commented Apr 10, 2024

Before submitting checklist

  • Did you update the CHANGELOG? (not for test updates, internal changes/refactors or CI/CD setup)
  • Did you ask the docs owner to review all the user-facing changes?

@Raalsky Raalsky changed the title Fixed compatibility checks with pre release versions Fixed compatibility checks with pre-release versions Apr 10, 2024
Copy link

codecov bot commented Apr 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.55%. Comparing base (dea2299) to head (ba3768c).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1730      +/-   ##
==========================================
- Coverage   77.93%   73.55%   -4.38%     
==========================================
  Files         244      244              
  Lines       12960    12775     -185     
==========================================
- Hits        10100     9397     -703     
- Misses       2860     3378     +518     
Flag Coverage Δ
e2e ?
e2e-management ?
e2e-s3 ?
e2e-s3-gcs ?
e2e-standard ?
macos 73.40% <100.00%> (-4.46%) ⬇️
py3.10 ?
py3.11 ?
py3.12 ?
py3.7 73.53% <100.00%> (-3.75%) ⬇️
py3.7.16 ?
py3.8 ?
py3.9 ?
ubuntu 73.48% <100.00%> (-4.40%) ⬇️
unit 73.53% <100.00%> (-0.69%) ⬇️
windows 72.41% <100.00%> (-5.10%) ⬇️

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.

raise NeptuneClientUpgradeRequiredError(version, min_version=client_config.version_info.min_compatible)
if client_config.version_info.max_compatible and client_config.version_info.max_compatible < version_with_patch_0:

if max_compatible and max_compatible < version_with_patch_0:
Copy link
Contributor

Choose a reason for hiding this comment

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

Why when checking whether client version is too big we extend possible micro versions?

Ex. if version = 1.5.10 and max_compatible = 1.5.0 we are not raising exception

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know :<. Maybe someone set 0.10.0 instead of 0.10.9999 for some already delivered self hosted environment and that was easier to do it in client.

@Raalsky Raalsky merged commit e946c70 into master Apr 10, 2024
4 checks passed
@Raalsky Raalsky deleted the rj/pre-version-fix branch April 10, 2024 11:28
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.

2 participants