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
`>>>>>>>>|- ERROR in [bdal-logconf:logger_config.cpp:430] - XML analysis error: The resulting configuration is unusable - Falling back to default configuration:
Dynamic exception type: std::bad_cast
std::exception::what: std::bad_cast
terminate called after throwing an instance of 'boost::interprocess::interprocess_exception'
what(): boost::interprocess::intermodule_singleton initialization failed
.command.sh: line 3: 79273 Aborted`
The following error occurs when running TIMSCONVERT in Linux using Nextflow or as a CLI application. The error is not present in when using TIMSCONVERT as a CLI application on Windows. We suspect the issue is caused by an error in timsdata.so which is absent in timsdata.dll, hence the lack of errors in Windows environments.
The text was updated successfully, but these errors were encountered:
Update: This issue is most likely caused by the use of certain versions of the Boost C++ library in C++ that do not appear to work well with Linux compilers. The issue needs to be fixed in the TDF-SDK library source code. A workaround for now is to use Python 3.7 when creating your conda venv.
`>>>>>>>>|- ERROR in [bdal-logconf:logger_config.cpp:430] - XML analysis error: The resulting configuration is unusable - Falling back to default configuration:
Dynamic exception type: std::bad_cast
std::exception::what: std::bad_cast
terminate called after throwing an instance of 'boost::interprocess::interprocess_exception'
what(): boost::interprocess::intermodule_singleton initialization failed
.command.sh: line 3: 79273 Aborted`
The following error occurs when running TIMSCONVERT in Linux using Nextflow or as a CLI application. The error is not present in when using TIMSCONVERT as a CLI application on Windows. We suspect the issue is caused by an error in timsdata.so which is absent in timsdata.dll, hence the lack of errors in Windows environments.
The text was updated successfully, but these errors were encountered: