You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We assume there is some system dependency related to RocksDB that is not present in our CI build environment that causes the problems.
Also, the upgrade of RocksDB on nearcore side has been reverted, and perhaps we need to try the release after that in case there is any connection with wrong/missing dependency and our binary not working.
The text was updated successfully, but these errors were encountered:
Also, the upgrade of RocksDB on nearcore side has been reverted, and perhaps we need to try the release after that in case there is any connection with wrong/missing dependency and our binary not working.
While that could have been an issue, given that the same near-lake code being compiled in another environment works fine, I feel that these might be unrelated.
Without any changes in this regard from the side of NEAR Lake, the release workflow produces the working binary. I've just testnet it on ci/release-check branch with TEST-0.0.0 release.
We assume there is some system dependency related to RocksDB that is not present in our CI build environment that causes the problems.
Also, the upgrade of RocksDB on
nearcore
side has been reverted, and perhaps we need to try the release after that in case there is any connection with wrong/missing dependency and our binary not working.The text was updated successfully, but these errors were encountered: