Bart Koelman
Bart Koelman
Well, I agree that printing a stack trace for functional errors that are supposed to happen sometimes (for example: OAS file not found or invalid) is annoying for users. But...
Got another crash today (v1.24.1), same message: > crit: Kiota.Builder.KiotaBuilder[0] > error generating the client: One or more errors occurred. (Object reference not set to an instance of an object.)...
Don't know yet, it only happens once in a while. That's why we need diagnostics, including the stack trace and command-line parameters used.
What's expected from me?
Yes, it happens randomly. But that's irrelevant. Kita needs to provide error details first, before the cause can be determined. There's no point in me reporting each time it happens...
See https://github.com/microsoft/kiota/issues/6035#issuecomment-2603189954, that's something different, right? For example, write to the console: > kiota failed with an unexpected internal error, please open an issue at (GitHub link). > Exception: {...