You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somehow the morpheus-visualizations submodule was reverted to point back to 23.03. This reintroduced bug which was fixed in 23.07.
Minimum reproducible example
Follow instructions to run DFP Visualization example. Error is seen when opening viz in web browser.
Relevant log output
error - Error: libnvrtc.so.11.2: cannot open shared object file: No such file or directory
at Object.Module._extensions..node (node:internal/modules/cjs/loader:1179:18)
at Module.load (node:internal/modules/cjs/loader:975:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:999:19)
at require (node:internal/modules/cjs/helpers:102:18)
at bindings (/workspace/external/morpheus-visualizations/DFP/node_modules/bindings/bindings.js:112:48)
at Object.<anonymous> (/workspace/external/morpheus-visualizations/DFP/node_modules/@rapidsai/cuda/build/js/addon.js:20:25)
at Module._compile (node:internal/modules/cjs/loader:1097:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
at Module.load (node:internal/modules/cjs/loader:975:32) {
code: 'ERR_DLOPEN_FAILED'
}
Full env printout
No response
Other/Misc.
No response
Code of Conduct
I agree to follow Morpheus' Code of Conduct
I have searched the open bugs and have found no duplicates for this bug report
The text was updated successfully, but these errors were encountered:
Version
23.07
Which installation method(s) does this occur on?
Docker
Describe the bug.
Somehow the
morpheus-visualizations
submodule was reverted to point back to 23.03. This reintroduced bug which was fixed in 23.07.Minimum reproducible example
Follow instructions to run DFP Visualization example. Error is seen when opening viz in web browser.
Relevant log output
Full env printout
No response
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: