Allow for warn_only selection in enable_full_determinism
Enable full determinism crashes if the model has layer that do not support it (like layoutlmv2). This fixes it.
Or don't use the option with a model that does not support it? This is not something that is enabled by default.<|||||>_The documentation is not available anymore as the PR was closed or merged._<|||||>> Or don't use the option with a model that does not support it? This is not something that is enabled by default.

Well, not everyone can afford it, and it's not good practice to keep something that it's crash prone. e.g. In my company we are using a model to prod and would like to use full determinism to run full end-to-end evaluations to carry out fine tuning experiments. It doesn't really cost anything to add an option there (I pushed another commit), and would save people the burden of "hacking" a Docker image just to avoid crashes when deploying an image<|||||>Thank you for educating me on good practices.<|||||>To be honest, I started with a very simple request and you answered assuming to know what was our current situation: "don't use the option with a model that does not support it?" is not really a solution in many real world scenarios. I tried to explain to you our situation and you answered sarcastically.
My point was simply that you currently have an implementation of a function which is not very useable in the case I described to you above, but from your answer I assume that you probably don't care, even if is a two liner change.

Finally, even if it didn't make any sense you could have just thanked for the contribution instead of being standoffish<|||||>Hi there.

PyTorch has a built-in mechanism in this function to fail when it can't do its job properly, so that the user is not surprised to have non-reproducible result. You are, of course, free to change it in your experiments (and not get full reproducibility). You are wrong to assume that every person using Transformers would like to ignore the error. I apologize if my first answer was maybe too short and did not convey this point. There was nothing aggressive in it so you did not have to answer with a patronizing tone.

The function can be duplicated (it's five lines of code) and called with the arguments you require at the beginning of the script instead of calling via Transformers, which should solve your issue without changing the experience for other users.<|||||>You're right and you make a fair point. Indeed my first commit was a bit naive in assuming that everyone would like to have warn_only=True. That's why I changed it in the second commit (maybe you missed it). Do you think the current status is worth be applied?