-
Notifications
You must be signed in to change notification settings - Fork 923
Update to Agave test validator 2.0.x #3640
Update to Agave test validator 2.0.x #3640
Conversation
🦋 Changeset detectedLatest commit: ee7988e The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
BundleMonFiles updated (6)
Unchanged files (119)
Total files change -319B -0.09% Final result: ✅ View report in BundleMon website ➡️ |
A preview of the GitHub Pages site based on this PR is now available here: |
43f1938
to
6c59ac1
Compare
43caded
to
88a885f
Compare
88a885f
to
ee7988e
Compare
@@ -2074,7 +2074,7 @@ describe('getProgramAccounts', () => { | |||
rentEpoch: expect.any(BigInt), | |||
space: 8n, | |||
}, | |||
pubkey: 'SysvarFees111111111111111111111111111111111', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sysvar is gone.
replacementBlockhash: { | ||
blockhash: expect.any(String), | ||
lastValidBlockHeight: expect.any(BigInt), | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See also #2869.
export const SYSVAR_FEES_ADDRESS = | ||
'SysvarFees111111111111111111111111111111111' as Address<'SysvarFees111111111111111111111111111111111'>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sysvar is fetchable using the test validator in Agave 1.18.
% curl http://localhost:8899 -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":"LOL","method":"getAccountInfo","params":["SysvarFees111111111111111111111111111111111"]}'
{"jsonrpc":"2.0","result":{"context":{"apiVersion":"1.18.26","slot":64},"value":{"data":"11111111","executable":false,"lamports":946560,"owner":"Sysvar1111111111111111111111111111111111111","rentEpoch":0,"space":8}},"id":"LOL"}
…but appears to have been removed from the test validator in Agave 2.0.
% curl http://localhost:8899 -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":"LOL","method":"getAccountInfo","params":["SysvarFees111111111111111111111111111111111"]}'
{"jsonrpc":"2.0","result":{"context":{"apiVersion":"2.0.17","slot":0},"value":null},"id":"LOL"}
Note that you can still fetch this account on mainnet-beta, even against a 2.0 RPC.
What's the right thing to do here? Should we leave it in the @solana/sysvars
package, mark it as deprecated, set the tests as ‘supposed to fail’, and leave it, or should we do what I did here and delete it completely before anyone much starts to rely on it in [email protected]?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly anza-xyz/agave#2003?
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
No description provided.