* chore: cargo +nightly clippy --fix -Z unstable-options (cherry picked from commit6514096a67) # Conflicts: # core/src/banking_stage.rs # core/src/cost_model.rs # core/src/cost_tracker.rs # core/src/execute_cost_table.rs # core/src/replay_stage.rs # core/src/tvu.rs # ledger-tool/src/main.rs # programs/bpf_loader/build.rs # rbpf-cli/src/main.rs # sdk/cargo-build-bpf/src/main.rs # sdk/cargo-test-bpf/src/main.rs # sdk/src/secp256k1_instruction.rs * chore: cargo fmt (cherry picked from commit789f33e8db) * Updates BPF program assert_instruction_count tests. (cherry picked from commitc1e03f3410) # Conflicts: # programs/bpf/tests/programs.rs * Resolve conflicts Co-authored-by: Alexander Meißner <AlexanderMeissner@gmx.net> Co-authored-by: Michael Vines <mvines@gmail.com>
BigTable Setup
Development Environment
The Cloud BigTable emulator can be used during development/test. See https://cloud.google.com/bigtable/docs/emulator for general setup information.
Process:
- Run
gcloud beta emulators bigtable startin the background - Run
$(gcloud beta emulators bigtable env-init)to establish theBIGTABLE_EMULATOR_HOSTenvironment variable - Run
./init-bigtable.shto configure the emulator - Develop/test
Production Environment
Export a standard GOOGLE_APPLICATION_CREDENTIALS environment variable to your
service account credentials. The project should contain a BigTable instance
called solana-ledger that has been initialized by running the ./init-bigtable.sh script.
Depending on what operation mode is required, either the
https://www.googleapis.com/auth/bigtable.data or
https://www.googleapis.com/auth/bigtable.data.readonly OAuth scope will be
requested using the provided credentials.