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
/Users/kyle/anaconda3/lib/python3.11/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 32 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '
Sometimes occurs while in idle event loop or using Ctrl-c to terminate.
Steps to reproduce the behavior:
local profile modified to use: deepseek-coder-v2
poetry run 01 --profile local
Ctrl-c
Expected behavior
program exit, no output.
OS: mac m3 max
The currently activated Python version 3.12.4 is not supported by the project (>=3.9,<3.12).
Trying to find and use a compatible version.
Using python3.11 (3.11.7)
Additional context
On server start:
[2024-08-06 14:41:31.349] [ctranslate2] [thread 4558739] [warning] The compute type inferred from the saved model is float16, but the target device or backend do not support efficient float16 computation. The model weights have been automatically converted to use the float32 compute type instead.
I have also seen this pop up while idle in the event loop.
The text was updated successfully, but these errors were encountered:
Running current 01:
Sometimes occurs while in idle event loop or using Ctrl-c to terminate.
Steps to reproduce the behavior:
local profile modified to use: deepseek-coder-v2
poetry run 01 --profile local
Ctrl-c
Expected behavior
program exit, no output.
Trying to find and use a compatible version.
Using python3.11 (3.11.7)
Additional context
On server start:
[2024-08-06 14:41:31.349] [ctranslate2] [thread 4558739] [warning] The compute type inferred from the saved model is float16, but the target device or backend do not support efficient float16 computation. The model weights have been automatically converted to use the float32 compute type instead.
I have also seen this pop up while idle in the event loop.
The text was updated successfully, but these errors were encountered: