* Add feature gate
* Add helper fn
* Require split destination to be rent-exempt if it is active
* Update cli to prefund split accounts
* cli: require rent param with sign-only
* Update tokens to prefund split accounts
* Update split tests with sysvar accounts
* Fix test_split_to_account_with_rent_exempt_reserve
* Fix test_staked_split_destination_minimum_balance
* Fix test_split_more_than_staked
* Fix test_split_minimum_stake_delegation and remove misleading StakeState::Initialized case
* Fix test_split_from_larger_sized_account
* Add test for pre-/post-activation behavior splitting some or all of stake account
* Assert active stake
* Fix runtime test
* Ignore stake-pool downstream
* Review comments
* Feature gate sysvar reads
* ci: init spl downstream project on Github Action
* ci: fix spl downstream project doesn't use cargo-test-sbf
* ci: move nightly build to another individual file
* ci: get more space for runners on Github Action
* ci: trun off fali-fast
* Update .github/workflows/downstream-project-spl.yml
Co-authored-by: Jon Cinque <me@jonc.dev>
* ci: separate all spl programs
* use reusable workflow
* add error reporting for nightly build
* update test method
* add build and test
* only build required program
* remove other branches
* Update .github/workflows/downstream-project-spl.yml
Co-authored-by: Jon Cinque <me@jonc.dev>
* Update .github/workflows/downstream-project-spl.yml
Co-authored-by: Jon Cinque <me@jonc.dev>
* add check
* update build and test
* add lacking programs
* remove unnecessary programs
---------
Co-authored-by: Jon Cinque <me@jonc.dev>
Current limit of 3 is too low, as the updates are happening faster than
they are processed via our review process.
As this limit applies to the total number of outstanding PRs, any PR
that requires additional investigation is further reducing the update
speed.
Bumping 2x to see if this would get us back on track to catching up with
the current state of the world.
If someone forks the `solana` repo, they should not have access to Slack
or AWS storage locations that hold build artifacts. Meaning, actions
that interact with that infrastructure will always fail. It makes sense
to disable these actions in forks.
This doesn't actually do what I thought it did. The `start-date` config doesn't make stalebot start from a certain date forward, it makes tasks older than that date immune to being closed.
This means I'm going to just have to find a way to raise the GitHub API operations limit to be able to handle more tasks, or wait until enough have been closed that it fits within our current limit.
* init
* print all errors in the end
* print success msg
* use skip patterns instead of specific file
* v2
* checkout full history
* install toml cli in Github Actions step
* git diff only list added and modified
* prevent empty owner list
* lint: ident with space 2
* update 404 hint
* lint
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* wording
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* indent with space
* add some friendly error message
* wording
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* Update .github/workflows/crate-check.yml
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* fix indent
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* create a reusable workflow for current error reporting logic
* make github.event.head_commit.message as a env, COMMIT_MESSAGE
* make github.event.head_commit.author.name as a env, COMMIT_AUTHOR_NAME
* remove redundant name
* replace error reporting step with the reusalble workflow
* Enable remote cache for Turborepo
* Rename `build` to `compile` and `package` to `build`
* Add a workflow that builds on PRs and pushes with Turborepo
* Explain how to connect to Turborepo remote caching
* Upgrade to pnpm 7