Serve algjulia-interop as a service through the backend#1132
Open
Serve algjulia-interop as a service through the backend#1132
Conversation
jmoggr
added
enhancement
jmoggr
force-pushed
the
julia-service
branch
2 times, most recently
from
7d2f37f to
7b74906
Compare
epatters
changed the title
epatters
requested changes
Mar 17, 2026
Member
epatters
left a comment
epatters
left a comment
There was a problem hiding this comment.
Thanks Jason, this looks great. Just a few small comments below.
| # native libraries needed by AlgebraicJulia packages. | ||
| { pkgs }: | ||
| let | ||
| juliaVersion = "1.11.6"; |
Member
There was a problem hiding this comment.
We should bump the Julia version to v1.12, the latest stable release.
Member
There was a problem hiding this comment.
This diff shouldn't be here, but in view of #1136, it should disappear anyway after rebasing off main.
| qubit = { version = "1.0.0-beta.0", features = ["ts-serde-json", "ts-uuid", "ts-chrono"] } | ||
| rand = "0.8" | ||
| regex = "1.11.1" | ||
| reqwest = { version = "0.12", default-features = false, features = ["rustls-tls"] } |
Member
There was a problem hiding this comment.
Any reason not to use the latest v0.13, which apparently also uses rustls by default?
|
|
||
| async ({ model, diagram }) => { | ||
| const response = await fetch("http://127.0.0.1:8080/acsetcolim", { | ||
| const response = await api.fetch("/julia/acsetcolim", { |
Member
There was a problem hiding this comment.
I can imagine wanting to use a local Julia server when developing new analyses based on Julia. How should we handle that? One idea is add a Vite env variable defaulting to the above but settable to localhost if desired.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1109
I've tested this in the VM, but I expect there to be issues when it's first deployed. I don't think we should merge this until I/we have confirmed that it can be successfully deployed to staging manually, otherwise it will likely break CI.
Running other peoples code on servers I am responsible for makes me nervous. I have hardened the systemd service for julia to the best of my ability and am going to have an LLM spend the night iterating through all of the other options to find the minimal set of permissions that still works. This is probably better isolation than what docker offers by default and I don't think we can do much better without full virtualization. I might look into options for hardening the kernel as well, I've not done that on Nix and Nix might make that easy and worth doing.