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
I encountered a critical issue when using onnxruntime==1.19.2 in the AWS Lambda Python 3.12 container (public.ecr.aws/lambda/python:3.12). The error is as follows:
terminate called after throwing an instance of 'onnxruntime::OnnxRuntimeException'
what(): /onnxruntime_src/include/onnxruntime/core/common/logging/logging.h:340 static const onnxruntime::logging::Logger& onnxruntime::logging::LoggingManager::DefaultLogger() Attempt to use DefaultLogger but none has been registered.
I attempted to resolve this by explicitly initializing the default logger in Python code:
import onnxruntime as ort
ort.set_default_logger()
What is the expected behaviour?
No response
A minimal reproducible example
Use the onnxruntime==1.19.2 library in a Docker image based on public.ecr.aws/lambda/python:3.12.
Run any script that initializes an ONNX Runtime session (e.g., ort.InferenceSession).
Observe the error indicating an unregistered DefaultLogger.
What Python version are you on? e.g. python --version
What happened?
I encountered a critical issue when using onnxruntime==1.19.2 in the AWS Lambda Python 3.12 container (public.ecr.aws/lambda/python:3.12). The error is as follows:
I attempted to resolve this by explicitly initializing the default logger in Python code:
What is the expected behaviour?
No response
A minimal reproducible example
Use the onnxruntime==1.19.2 library in a Docker image based on public.ecr.aws/lambda/python:3.12.
Run any script that initializes an ONNX Runtime session (e.g., ort.InferenceSession).
Observe the error indicating an unregistered DefaultLogger.
What Python version are you on? e.g. python --version
ONNX Runtime Version: 1.19.2
Python Version: 3.12
Docker Image: public.ecr.aws/lambda/python:3.12
Operating System: AWS Lambda Runtime
FastEmbed version
v0.5.0
What os are you seeing the problem on?
Linux
Relevant stack traces and/or logs
No response
The text was updated successfully, but these errors were encountered: