Skip to content

Conversation

@anutosh491
Copy link
Member

Fixes the problem of exposing generated binaries as per pointed out here : https://discourse.llvm.org/t/mlir-python-bindings-entirely-in-the-browser/87013/4?u=anutosh491

We recently fixes it for clang-repl : llvm/llvm-project#175508 (comment)

@makslevental makslevental self-requested a review February 11, 2026 16:50
@makslevental
Copy link
Contributor

Hmm I'm not sure why actions aren't running - lemme figure it out then we can merge (even though there aren't really "tests" for this path...)

@anutosh491
Copy link
Member Author

anutosh491 commented Feb 12, 2026

lemme figure it out then we can merge

Thank you.

Can just build it all and can query into Jupyterlite's filesystem and the generated binaries shouldn't be exposed no more and be present in a unique path.

@makslevental
Copy link
Contributor

lemme figure it out then we can merge

Thank you.

Can just build it all and can query into Jupyterlite's filesystem and the generated binaries shouldn't be exposed no more and be present in a unique path.

Sure but I'm still not gonna merge without tests passing

@anutosh491
Copy link
Member Author

Yess offcourse no rush ;~)

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.

2 participants