[CLI]: no good exit when terminated script by CTRL+C about wandb HOT 2 CLOSED

Yes, it seems the new backend has solved that issue (under Ubuntu). We don't have annoying messages from the zombie process in the shell after termination. I didn't checked how it was programmed, but I believe subprocess is now better managed.

from wandb.

Hi @christopher5106 - I am sorry to hear you are experiencing this issue. Would you mind sharing some additional information to help us troubleshoot this:

• What platform are you running your W&B experiments on?
• What version of the SDK do you currently have installed?
• Does this happen with all your W&B experiments? It would be useful to know what objects are you logging (metrics, Images, Artifacts, Tables)
• Do you have the URL for one of the interrupted Runs as well as the debug.log and debug-internal.log files you can find in the ./wandb/run-<date_time>-<runid>/logs folder?

Finally, with version 0.17.0+ we have been releasing a new backend for the SDK [wandb-core](https://github.com/wandb/wandb/tree/main/core#readme) as part of the wandb package. Among other features, this should improve the robustness of the client so it would be worth testing if you are still experiencing the same issue after enabling it.

The new backend can be enabled setting wandb.require("core") at the beginning of your script.

from wandb.