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 clarabel to v0.9.0 #58

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Update clarabel to v0.9.0 #58

merged 1 commit into from
Aug 29, 2024

Conversation

calintat
Copy link
Contributor

This updates clarabel to v0.9.0 which crucially includes a fix that makes it work on WASM.

@lovasoa
Copy link
Collaborator

lovasoa commented Jul 23, 2024

If we decide to add support for wasm, then we need at least one test for the wasm build in our CI. Otherwise someone will break wasm compatibility later.

for the clarabel version update: no problem

@calintat
Copy link
Contributor Author

I removed the WASM flag for now as I've discovered a bug when running Clarabel on WASM.

It now only contains the version bump so hopefully we can merge this as is.

@calintat
Copy link
Contributor Author

@lovasoa could we get this merged?

@lovasoa lovasoa merged commit d4a4942 into rust-or:main Aug 29, 2024
1 check passed
@lovasoa
Copy link
Collaborator

lovasoa commented Aug 29, 2024

Thanks!

@Specy
Copy link
Contributor

Specy commented Nov 1, 2024

@calintat do you remember what error you were experiencing when running wasm?

@calintat
Copy link
Contributor Author

calintat commented Nov 1, 2024

Yes, I raised it on the Clarabel repo: oxfordcontrol/Clarabel.rs#125

It's not a WASM issue actually, it just means I can't switch to clarabel yet for my specific use case.

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.

3 participants