Go to file
GroovieGermanikus 2c8aa2adf1
fix into_inner from RwLockWrapped
2024-06-24 17:16:01 +02:00
.buildkite
.github
account-decoder
accounts-bench
accounts-cluster-bench
accounts-db fix into_inner from RwLockWrapped 2024-06-24 17:16:01 +02:00
banking-bench
banks-client
banks-interface
banks-server
bench-streamer
bench-tps
bloom
bucket_map
cd
ci
clap-utils
clap-v3-utils
cli
cli-config
cli-output
client
client-test
connection-cache
core
cost-model
docs
dos
download-utils
entry
faucet
frozen-abi
genesis
genesis-utils
geyser-plugin-interface
geyser-plugin-manager
gossip
install
keygen
ledger
ledger-tool
local-cluster
log-analyzer
logger
measure
memory-management
merkle-root-bench
merkle-tree
metrics
multinode-demo
net
net-shaper
net-utils
notifier
perf
poh
poh-bench
program-runtime
program-test
programs
pubsub-client
quic-client
rayon-threadlimit
rbpf-cli
remote-wallet
rpc Returning only program id, when there are no filters and dataslice lenghth is 0 2024-04-09 14:25:00 +02:00
rpc-client
rpc-client-api
rpc-client-nonce-utils
rpc-test
runtime loc map access 2024-06-11 22:13:01 +02:00
scripts
sdk log fastcpy 2024-06-24 15:12:28 +02:00
send-transaction-service
stake-accounts
storage-bigtable
storage-proto
streamer
system-test
test-validator
thin-client
tokens
tpu-client
transaction-dos
transaction-status
turbine
udp-client
upload-perf
validator
version
vote
watchtower
web3.js
zk-keygen
zk-token-sdk
.clippy.toml
.codecov.yml
.gitignore
.mergify.yml
CHANGELOG.md
CONTRIBUTING.md
Cargo.lock fix into_inner from RwLockWrapped 2024-06-24 17:16:01 +02:00
Cargo.toml
LICENSE
README.md
RELEASE.md
SECURITY.md
cargo
cargo-build-bpf
cargo-build-sbf
cargo-test-bpf
cargo-test-sbf
fetch-perf-libs.sh
fetch-spl.sh
nextest.toml
run.sh
rust-toolchain.toml
rustfmt.toml
test-abi.sh
vercel.json

README.md

Solana

Solana crate Solana documentation Build status codecov

Building

1. Install rustc, cargo and rustfmt.

$ curl https://sh.rustup.rs -sSf | sh
$ source $HOME/.cargo/env
$ rustup component add rustfmt

When building the master branch, please make sure you are using the latest stable rust version by running:

$ rustup update

When building a specific release branch, you should check the rust version in ci/rust-version.sh and if necessary, install that version by running:

$ rustup install VERSION

Note that if this is not the latest rust version on your machine, cargo commands may require an override in order to use the correct version.

On Linux systems you may need to install libssl-dev, pkg-config, zlib1g-dev, protobuf etc.

On Ubuntu:

$ sudo apt-get update
$ sudo apt-get install libssl-dev libudev-dev pkg-config zlib1g-dev llvm clang cmake make libprotobuf-dev protobuf-compiler

On Fedora:

$ sudo dnf install openssl-devel systemd-devel pkg-config zlib-devel llvm clang cmake make protobuf-devel protobuf-compiler perl-core

2. Download the source code.

$ git clone https://github.com/solana-labs/solana.git
$ cd solana

3. Build.

$ ./cargo build

Testing

Run the test suite:

$ ./cargo test

Starting a local testnet

Start your own testnet locally, instructions are in the online docs.

Accessing the remote development cluster

  • devnet - stable public cluster for development accessible via devnet.solana.com. Runs 24/7. Learn more about the public clusters

Benchmarking

First, install the nightly build of rustc. cargo bench requires the use of the unstable features only available in the nightly build.

$ rustup install nightly

Run the benchmarks:

$ cargo +nightly bench

Release Process

The release process for this project is described here.

Code coverage

To generate code coverage statistics:

$ scripts/coverage.sh
$ open target/cov/lcov-local/index.html

Why coverage? While most see coverage as a code quality metric, we see it primarily as a developer productivity metric. When a developer makes a change to the codebase, presumably it's a solution to some problem. Our unit-test suite is how we encode the set of problems the codebase solves. Running the test suite should indicate that your change didn't infringe on anyone else's solutions. Adding a test protects your solution from future changes. Say you don't understand why a line of code exists, try deleting it and running the unit-tests. The nearest test failure should tell you what problem was solved by that code. If no test fails, go ahead and submit a Pull Request that asks, "what problem is solved by this code?" On the other hand, if a test does fail and you can think of a better way to solve the same problem, a Pull Request with your solution would most certainly be welcome! Likewise, if rewriting a test can better communicate what code it's protecting, please send us that patch!