-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Crash while running Concrete ML #66725
Comments
@llvm/issue-subscribers-mlir
I tried this code:
from sklearn.datasets import make_classification Lets create a synthetic data-setx, y = make_classification(n_samples=100, class_sep=2, n_features=30, random_state=42) Split the data-set into a train and test setX_train, X_test, y_train, y_test = train_test_split( Now we train in the clear and quantize the weightsmodel = LogisticRegression(n_bits=8) We can simulate the predictions in the cleary_pred_clear = model.predict(X_test) We then compile on a representative setmodel.compile(X_train) Finally we run the inference on encrypted inputs !y_pred_fhe = model.predict(X_test, fhe="execute") print("In clear :", y_pred_clear) Output:
but I got this? #0 0x00007f0d6bae5b91 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/home/marcelo/Documentos/Projeto/teste3/lib/python3.10/site-packages/mlir/_mlir_libs/libConcretelangBindingsPythonCAPI.so+0x13b4b91) |
Related issues:
All three these issues are related to the Concrete ML (https://github.com/zama-ai/concrete-ml) Python package called I'll try to see if I can find the root cause and submit a patch within a few days. |
@marcelocirilo I have no problems to run your code on an M1 chip:
Could you provide more information such as
and your system? Especially the CPU. Basically anything we could need to reproduce your issue. It could be that your CPU is too old (zama-ai/concrete-ml#62 (comment)). |
Okay we cannot reproduce and it's probably fixed (either here at MLIR or at concrete-ml (related comment)) since no new reports have come in. I'll close this issue. |
I tried this code:
but I got this?
The text was updated successfully, but these errors were encountered: