-
Notifications
You must be signed in to change notification settings - Fork 35
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
Small improvements #393
Small improvements #393
Conversation
Great - I thought I tried |
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.
LGTM and works locally on my side
FWIW, I have no easy way of testing this because when I try to install from the repo I get errors about missing rust, but when I edit |
It's very strange that you get errors about rust - it might be needed for the optional dependency metatensor, but not for just |
Rust should not even be needed for metatensor, since pip should use the pre-built wheels and not build from source. |
@bernstei you could also try to install the wheel built by CI for this PR by downloading https://github.com/lab-cosmo/chemiscope/actions/runs/11822592226/artifacts/2183374870, unziping and then running |
I thought I had a rust issue earlier, but now the error is just complaining about npm. I'll try the wheel. Is there also always a wheel built for the main branch whenever a PR is merged?
|
I can confirm that the prebuilt PR wheel works, and I get a much better resolution image. It'd be even better for that resolution to be settable, but that's not at all urgent. |
An error on npm makes sense, we need it to build the JS part of the code.
Even before it is merged, you can find the link by looking at the "build-wheels" CI job, and then "Summary" and "Artifacts" at the bottom. |
OK, I can install now that I added npm. Is there a faster way of doing debugging than just modifying the typescript source in the repo dir and doing |
So if you are debugging the juptyter extension, that's the main way. If you want to work with the website, |
Thanks. I guess since the problem shows up in both, I can try to debug it in the web server context. Now I just have to figure out how to get information out of the typescript code (without knowing much about it). |
Fix #392