Dmitry Dygalo

@g3rda Awesome! Indeed, as Schemathesis does not have full visibility to distinguish different server errors, it may merge them into a single failure report. There are a bit more details...

> I like the idea of checking Sentry/logs, it adds real system feedback into fuzzing. I feel such a hook could improve the accuracy of reported bugs a lot. The...

> By “the whole sequence of API calls” do you mean replaying the full pre-shrinking sequence of requests? Yes, as a way to see everything that happened. > If so,...

In any event I plan to finish a few things for the 4.1 release and will work on this issue more focused (somewhere next week)

@nedbat Thank you for your response! It is indeed niche, and I was thinking about the least invasive way - maybe a way to hook into the DB schema would...

Thank you for opening this issue! It would be an interesting addition to the coverage phase - I'll take a look at it in the following days

Sorry for the delay! The following has no ground from the JSON Schema point of view: ```json { "priority": "9" # value: Near-boundary number" } ``` Given the schema definition:...

@uncenter > I suspect this is an issue where when resolving the $ref, the description field is ignored. JSON Schema drafts 7 and earlier ignore all other keywords if `$ref`...

Thank you so much for such a detailed report! Will take a look at it soon :)

To confirm, does it work as expected if the "examples" & "coverage" phases are disabled? I.e. if only "fuzzing" is [enabled](https://schemathesis.readthedocs.io/en/stable/reference/configuration/#phasesenabled) My current assumption is that custom media types aren't...