Conversation
Remove `sei-db` as a nested go module and instead flatten it into `sei-chain` top level module. This simplifies the go module structure and removes one degree of complexity from workspace management.
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2587 +/- ##
==========================================
+ Coverage 42.00% 43.20% +1.20%
==========================================
Files 1510 1856 +346
Lines 118778 152688 +33910
==========================================
+ Hits 49891 65970 +16079
- Misses 64558 80834 +16276
- Partials 4329 5884 +1555
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
| github.com/gonum/lapack v0.0.0-20181123203213-e4cdc5a0bff9 h1:7qnwS9+oeSiOIsiUMajT+0R7HR6hw5NegnKPmn/94oI= | ||
| github.com/gonum/matrix v0.0.0-20181209220409-c518dec07be9 h1:V2IgdyerlBa/MxaEFRbV5juy/C3MGdj4ePi+g6ePIp4= | ||
| github.com/google/btree v1.1.3/go.mod h1:qOPhT0dTNdNzV6Z/lhRX0YXUafgPLFUh+gZMl761Gm4= | ||
| github.com/google/btree v1.0.1/go.mod h1:xXMiIv4Fb/0kKde4SpL7qlzvu5cMJDRkFDxJfI9uaxA= |
There was a problem hiding this comment.
fyi, btree gets reverted to an older version
There was a problem hiding this comment.
Yeah this also caught my eye thanks for pointing that out.
This is a transitive dependency. Taking a closer look to see why this happened.
There was a problem hiding this comment.
After a closer look, this is in go wor sum, and a result of running go work sync. The indirect dependency in sei-chain remains 1.1.3 which is the one ends up being used in the built binary.
Remove
sei-dbas a nested go module and instead flatten it intosei-chaintop level module.This simplifies the go module structure and removes one degree of complexity from workspace management.