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

near-runtime-standalone should be published to crates.io and not use rocksdb #2433

Closed
maxzaver opened this issue Apr 10, 2020 · 2 comments
Closed
Assignees
Labels
A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) P-low Priority: low

Comments

@maxzaver
Copy link
Contributor

maxzaver commented Apr 10, 2020

We should examine dependencies of the runtime crate and near-runtime-standalone and refactor them in such way that we can publish them to crates.io.

We also should be using TestDB instead of the rocksdb.

This is not critical for the Mainnet or for using near-runtime-standalone in the AssemblyScript tests.

@maxzaver maxzaver added P-low Priority: low A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) labels Apr 10, 2020
nearprotocol-bulldozer bot pushed a commit that referenced this issue Apr 29, 2020
The PR follows the very specific goal - to remove `actix` dependency from near-primitives.

The general approach here is  to move in small iterations to bring us closer to #2433
@stale
Copy link

stale bot commented Jul 1, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Jul 1, 2021
@bowenwang1996
Copy link
Collaborator

I believe this is already done. Please reopen if it is not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) P-low Priority: low
Projects
None yet
Development

No branches or pull requests

3 participants