I am getting this error seemingly randomly in the logging, and it doesn't appear to be affecting anything. In addition there are protocolscript warnings that indicate an invalid number. Does anyone know where these come from/how to go debug them?
Alex Johnson [SLC] [DevOps Advocate] Selected answer as best 1st December 2020
More information about the CS1692 warning can be found here: https://docs.microsoft.com/en-us/dotnet/csharp/misc/cs1692.
Apparently the code in that QAction uses "#pragma warning disable <number>" to ignore some C# warnings, but with a number that is not correct.
Alex Johnson [SLC] [DevOps Advocate] Selected answer as best 1st December 2020