Christian Steinmeyer comments

Results 40 comments of


                                            Christian Steinmeyer

Support of webhooks

For our use case, it would be nice to somehow trigger a webhook when the status of a task changes (e.g. created, validation, completed)

add python 3.10 compatibility

Thanks for the response @thequilo. Quick question: which tests are you talking about? The last two azure pipelines seem to only have failed because they were cancelled, if I didn't...

If mypy fails and only prints to stdout, not stderr, this leads to a cryptic event log message without details or stacktrace

Thanks for the quick response! I understand, that some messages were silent before but are no longer, but in my case, the mypy plugin doesn't seem to work anymore at...

If mypy fails and only prints to stdout, not stderr, this leads to a cryptic event log message without details or stacktrace

If I run `mypy --show-column-numbers --follow-imports silent ` from the same virtual env and directory, mypy runs, and doesn't crash, but finds an error (`Match statement not supported`). Aaaaand there...

If mypy fails and only prints to stdout, not stderr, this leads to a cryptic event log message without details or stacktrace

FYI: Looks like mypy's support for match statements [might be released on Friday](https://github.com/python/mypy/issues/12021#issuecomment-1062767446).

If mypy fails and only prints to stdout, not stderr, this leads to a cryptic event log message without details or stacktrace

Updated the issue to reflect our findings. I think there are two issues, actually: 1. What you mentioned already: missing information about the error cause 2. Even if this was...

If mypy fails and only prints to stdout, not stderr, this leads to a cryptic event log message without details or stacktrace

That does make sense, thanks! If you point me to the correct file(s), I'd be happy to prepare a PR. Given, mypy's fix is just around the corner, this should...

If mypy fails and only prints to stdout, not stderr, this leads to a cryptic event log message without details or stacktrace

As I see it, the output of the process is already consumed and stored in `issues` at that point. So we could either handle them at that point as if...