Description
Currently, when you press the "Stop Run" button on the W&B web interface, a SIGINT is sent to the main process of the application that created the W&B run (via wandb.init()). Can this behavior be customized? For instance, changing SIGINT to SIGUSR2 or other custom signals. On compute clusters, SIGINT is already used by SLURM to signal processes. It would be nice if we can customize W&B to use some other signal so these events can be distinguished.
Suggested Solution
Perhaps make wandb.init accept an optional argument that can customize this behavior.
Description
Currently, when you press the "Stop Run" button on the W&B web interface, a
SIGINTis sent to the main process of the application that created the W&B run (viawandb.init()). Can this behavior be customized? For instance, changingSIGINTtoSIGUSR2or other custom signals. On compute clusters,SIGINTis already used by SLURM to signal processes. It would be nice if we can customize W&B to use some other signal so these events can be distinguished.Suggested Solution
Perhaps make
wandb.initaccept an optional argument that can customize this behavior.