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
Starred member completions (e.g. stars in the completion list after typing myObject.) don't work on MacOS. (observed on arm64, but I believe this extends to x64 as well)
(note: Starred argument completions (e.g. stars in the completion list after typing myObject.myMethod( are unimpacted because they work totally differently and don't depend on any native libraries.)
On the currently released version 2.0, the process that hosts onnxruntime and blingfire fails silently. In the upcoming 2.1 this is improved with output window logging.
Neither of these can be loaded:
'.../libonnxruntime.dylib' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)
'.../libblingfiretokdll.dylib' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?
The first one is resolved after an update to 1.17.3, suggesting that microsoft/onnxruntime#16168 can be resolved. The latter we'll need to fix since we build it ourselves.
The text was updated successfully, but these errors were encountered:
Starred member completions (e.g. stars in the completion list after typing
myObject.
) don't work on MacOS. (observed on arm64, but I believe this extends to x64 as well)(note: Starred argument completions (e.g. stars in the completion list after typing
myObject.myMethod(
are unimpacted because they work totally differently and don't depend on any native libraries.)On the currently released version 2.0, the process that hosts onnxruntime and blingfire fails silently. In the upcoming 2.1 this is improved with output window logging.
Neither of these can be loaded:
The first one is resolved after an update to 1.17.3, suggesting that microsoft/onnxruntime#16168 can be resolved. The latter we'll need to fix since we build it ourselves.
The text was updated successfully, but these errors were encountered: