-
Notifications
You must be signed in to change notification settings - Fork 53
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
Conflict between plum-dispatch and cola-plum-dispatch #441
Comments
This issue has been marked as stale because it has been open for 7 days with no activity. |
Spoke to @daniel-dodd - this issue is caused by the downstream dependency |
CC: @vabor112 |
Thanks for updating @aterenin. I'd prefer to see this fixed upstream in Cola, otherwise we may need to fork the project and implement a workaround. Needless to say, this would be messy. |
I filed an issue with |
Bug Report
GPJax version: 0.8.0
Current behavior:
I am trying to update the existing integration of GeometricKernels with GPJax so that it works with newer versions of GPJax. It works okay for GPJax 0.6.9. However, for the current GPJax 0.8.0, I hit two problems.
The first one is exactly #397, which, although quite annoying, can be fixed by downgrading
tensorflow
to version 2.13.The second one is illustrated in the Related code section below. I believe it is concenred with plum-dispatch, which we use extensively in GeometricKernels to support multiple backends. GPJax uses cola which in its turn relies on a fork of
cola
, cola-plum-dispatch. This unmaintained fork uses the same namespaceplum
(which seems like a terrible sin) and gets overriden by the actualplum
that GeometricKernels uses, causing the error below. I believe this is similar to this issue.Expected behavior:
I am not sure how to fix this, but it seems to be an important problem to fix as otherwise GPJax becomes incompatible with any other libraries that rely on
plum-dispatch
, which is quite popular.Steps to reproduce:
See below.
Related code:
It is enough to run this snippet:
which leads to
The text was updated successfully, but these errors were encountered: