dotnet-httprepl swagger stackoverflowexception about httprepl HOT 6 CLOSED

Sorry for the delay, looking in to this now. It looks like this had to do with cyclic references in the swagger document. I'm currently testing out a fix, thanks for reporting this 👍

from httprepl.

Would you be able to provide the swagger.json file that you ran in to this with or the callstack at the time of the crash?

from httprepl.

Unfortunately I am not able to provide the swagger.json, but I can provide a sample which includes, info, path and definitiions of the swagger file.
swagger.txt

from httprepl.

Using the document you've provided (thanks!) I'm not seeing a StackOverflowException being thrown, but I did notice that the definitions object is being defined within the paths section, causing a pointer resolution to fail (in responses for About) and definitions to show up as a path, but not causing a crash. I think the best thing to do here might be to attach to the dotnet process running the tool, set the debugger to break on all exceptions and point it at the document that you're running in to problems with. The debugger should break when the stack overflow occurs (or if it breaks earlier, continue until you hit the right exception) - from there, we should be able to figure out where it's getting stuck.

from httprepl.

Thank's for the answer and your time.
I will use dotTrace for that purpose or try to debug the tool in order to identify what causes the StackOverflowException.

from httprepl.

I also seem to have the same issue myself with the httprepl attaching it to my own Swashbuckle.aspnetcore generated swagger.json

I haven't looked at attaching a debugger, thought I would just provide this to try and help investigation.

from httprepl.