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
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
In the event that execution of a TPL program fails (e.g. during interpretation, after a call to Module::GetFunction()) the tpl command-line program hangs after reporting the error. This is likely because of some state that gets corrupted which prevents the LLVM engine from shutting down or the TBB scheduler (the only two resources we attempt to clean up after a failure).
This error manifests when running TPL programs via the tpl command-line tool, but is also likely present in the DBMS itself.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the event that execution of a TPL program fails (e.g. during interpretation, after a call to
Module::GetFunction()
) thetpl
command-line program hangs after reporting the error. This is likely because of some state that gets corrupted which prevents the LLVM engine from shutting down or the TBB scheduler (the only two resources we attempt to clean up after a failure).This error manifests when running TPL programs via the
tpl
command-line tool, but is also likely present in the DBMS itself.The text was updated successfully, but these errors were encountered: