chore: update poetry lock file so python-rocksdb is v0.9.3#1251
Merged
chore: update poetry lock file so python-rocksdb is v0.9.3#1251
Conversation
|
Bencher Report| Branch | chore/update-poetry-lock |
| Testbed | ubuntu-22.04 |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result minutes (m) (Result Δ%) | Lower Boundary minutes (m) (Limit %) | Upper Boundary minutes (m) (Limit %) |
|---|---|---|---|---|
| sync-v2 (up to 20000 blocks) | 📈 view plot 🚷 view threshold | 1.61 m(-1.50%)Baseline: 1.63 m | 1.47 m (91.37%) | 1.80 m (89.54%) |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1251 +/- ##
==========================================
- Coverage 84.11% 84.10% -0.02%
==========================================
Files 311 311
Lines 23869 23869
Branches 3651 3651
==========================================
- Hits 20078 20075 -3
- Misses 3073 3077 +4
+ Partials 718 717 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
glevco
previously approved these changes
Mar 27, 2025
jansegre
force-pushed
the
chore/update-poetry-lock
branch
2 times, most recently
from
396376e to
c55b701
Compare
Even if #1244 has updated the resolved_reference, it seems it didn't do a complete update (python-rocksdb version was still marked as 0.9.2 instead of 0.9.3). The lock file was generated with poetry-2.1.1, and thus includes some new fields. The only downside of not doing this change seems to be that in development setups where python-rocksdb v0.9.2 exists in the cache, it will be used instead of correctly installing the one from github with version v0.9.3.
jansegre
force-pushed
the
chore/update-poetry-lock
branch
from
c55b701 to
e1e23a1
Compare
msbrogli
approved these changes
Apr 4, 2025
glevco
approved these changes
Apr 8, 2025
github-project-automation
bot
moved this from In Review (WIP)
to Waiting to be deployed
in Hathor Network
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Even if #1244 has updated the resolved_reference, it seems it didn't do a complete update (python-rocksdb version was still marked as 0.9.2 instead of 0.9.3). The new lock file was generated with poetry-2.1.2, and thus includes some new fields.
The only downside of not doing this change seems to be that in development setups where python-rocksdb v0.9.2 exists in the cache, it will be used instead of correctly installing the one from github with version v0.9.3.
Acceptance Criteria
poetry.lockwith Poetry 2.1.2name = "rocksdb"should haveversion = "0.9.3"instead ofversion = "0.9.2"Checklist
master, confirm this code is production-ready and can be included in future releases as soon as it gets merged