-
Notifications
You must be signed in to change notification settings - Fork 5
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
test: MSP move bucket reject on max capacity exceeded #328
base: feat/msp-move-bucket-improvements
Are you sure you want to change the base?
test: MSP move bucket reject on max capacity exceeded #328
Conversation
`--max-storage-capacity=${options?.maxStorageCapacity}`, | ||
`--jump-capacity=${options?.jumpCapacity}`, | ||
"--msp-charging-period=12", | ||
"--database-url=postgresql://postgres:postgres@docker-sh-postgres-1:5432/storage_hub", |
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.
every MSP container we spawn relies on the same postgres database index?
}); | ||
|
||
// Create API for MSP | ||
const mspApi = await BspNetTestApi.create(`ws://127.0.0.1:${rpcPort}`); |
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.
we should rename this api object BspNetTestApi
to something like ProviderNetTestApi
@@ -337,6 +331,8 @@ export type TestOptions = { | |||
extrinsicRetryTimeout?: number; | |||
/** If true, runs launched userNode has attached indexer service enabled. */ | |||
indexer?: boolean; | |||
/** Set a custom max storage capacity for MSP2 */ | |||
msp2MaxStorageCapacity?: number; |
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.
I don't see this being used anywhere
pricePerGigaUnitOfDataPerBlock: 100 * 1024 * 1024, | ||
commitment: "Terms of Service...", | ||
maxDataLimit: 9999999, | ||
paymentAccount: who |
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.
we can omit these fields since they are defaults in the forceSignupMsp
In order to test proper rejection of move bucket request on low capacity, a refactor and addition of onboardMsp (similar to onboardBsp) was needed.
This PR builds on top of #318.