Skip to content
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

Open
wants to merge 1 commit into
base: feat/msp-move-bucket-improvements
Choose a base branch
from

Conversation

links234
Copy link
Contributor

@links234 links234 commented Jan 16, 2025

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.

`--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",
Copy link
Contributor

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}`);
Copy link
Contributor

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;
Copy link
Contributor

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

Comment on lines +411 to +414
pricePerGigaUnitOfDataPerBlock: 100 * 1024 * 1024,
commitment: "Terms of Service...",
maxDataLimit: 9999999,
paymentAccount: who
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants