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

Update osmosis tests #512

Closed
wants to merge 6 commits into from
Closed

Update osmosis tests #512

wants to merge 6 commits into from

Conversation

Buckram123
Copy link
Collaborator

@Buckram123 Buckram123 commented Oct 24, 2024

Now that osmosis and test-tube updated to cosmwasm v2 we can enable integration and tests back

This PR introduces mock binaries and mock-deploy feature with open mnemonic to the abstract, it allows publishing abstract in a mocked chains: local, test tubes or starship

Copy link

cloudflare-workers-and-pages bot commented Oct 24, 2024

Deploying abstract-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: f237470
Status: ✅  Deploy successful!
Preview URL: https://b6f398ed.abstract-docs.pages.dev
Branch Preview URL: https://buckram-update-osmosis-tests.abstract-docs.pages.dev

View logs

@Buckram123
Copy link
Collaborator Author

Depends on AbstractSDK/cw-orchestrator#511

Comment on lines 219 to 236
for $interface_name<Chain>
{
fn wasm(_chain: &::cw_orch::prelude::ChainInfoOwned) -> ::cw_orch::prelude::WasmPath {
let build_postfix = {
#[cfg(feature = "mock-deployment")]
{
cw_orch::build::BuildPostfix::Custom("mock".to_string())
}
#[cfg(not(feature = "mock-deployment"))]
{
cw_orch::build::BuildPostfix::None
}
};
let wasm_name = env!("CARGO_CRATE_NAME").replace('-', "_");
::cw_orch::prelude::ArtifactsDir::auto(Some(env!("CARGO_MANIFEST_DIR").to_string()))
.find_wasm_path(&wasm_name)
.find_wasm_path_with_build_postfix(&wasm_name, build_postfix)
.unwrap()
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about this one, but I don't know how to solve it better in current implementation.
Issue that it will require the module to have exactly module-deployment feature. This issue comes out because we generate this code with macro and feature checks is happening after macro gets evaluated inside user crate, and not on abstract-app level

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Buckram123 so this will be removed with the new solution right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Buckram123 so this will be removed with the new solution right?

Drafting this PR for now. But yes, hopefully all magic would be limited in a build script

@Buckram123
Copy link
Collaborator Author

Closed in favor #528

@Buckram123 Buckram123 closed this Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants