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

fix: wasmer1_default feature actually selects wasmer1 #4279

Closed
wants to merge 1 commit into from

Conversation

matklad
Copy link
Contributor

@matklad matklad commented May 6, 2021

We use this feature in ./runtime/near-vm-runner/src/vm_kind.rs.

So, it should be declared in vm_runner Cargo.toml rather than in
vm_logic.

We use this feature in ./runtime/near-vm-runner/src/vm_kind.rs.

So, it should be declared in `vm_runner` Cargo.toml rather than in
`vm_logic`.
@matklad
Copy link
Contributor Author

matklad commented May 6, 2021

I think I orginialy broke that in #4225

@matklad
Copy link
Contributor Author

matklad commented May 6, 2021

My understanding is that we don't actually need this for 1.19.0 release, as #4278 fixed the problem. I am going to close this PR and open a new one against the master branch.

@matklad matklad closed this May 6, 2021
near-bulldozer bot pushed a commit that referenced this pull request May 7, 2021
We use this feature in ./runtime/near-vm-runner/src/vm_kind.rs.

So, it should be declared in `vm_runner` Cargo.toml rather than in
`vm_logic`.

This is #4279 submitted against master. 

Not sure how to make sure that similar errors don't happen in the future. The culprit here is that you can have `cfg(feature = "some-typo")`, and you won't see any warnings about this anywhere...
chefsale pushed a commit that referenced this pull request May 12, 2021
We use this feature in ./runtime/near-vm-runner/src/vm_kind.rs.

So, it should be declared in `vm_runner` Cargo.toml rather than in
`vm_logic`.

This is #4279 submitted against master. 

Not sure how to make sure that similar errors don't happen in the future. The culprit here is that you can have `cfg(feature = "some-typo")`, and you won't see any warnings about this anywhere...
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.

4 participants