You shouldn’t disable device assert errors, as they are pointing towards critical errors in your code.
E.g. you might run into an illegal memory access (the PyTorch device assert statements should trigger the assertion before hitting the memory violation), which might corrupt your data in all imaginable ways.
E.g. in case you are indeed finding a way to disable all asserts, your code might use an illegal indexing value and the (now faulty) indexing kernel might write (any) value to this invalid memory location.
If your data (e.g. a forward activation) would be stored there, it might be overwritten, which might even result in random NaN values during your training.
In short: don’t do it and fix your code