Lucien Zürcher

Dockerfile to test with the latest curl version support quic-draft-29 Dockerfile ```dockerfile FROM node:14.4.0-stretch # install dependencies RUN apt-get update && \ apt-get upgrade -y && \ apt-get install -y...

llnode dump; ``` Process 33180 stopped * thread #1, name = 'node', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x000000000166eb59 node`OPENSSL_cleanse + 41 node`OPENSSL_cleanse: ->...

Found some things, a `ng_flush_egress(conn, sockfd, qs)` fails with `CURLE_SEND_ERROR`. This happens at: https://github.com/curl/curl/blob/1313d7a35620e40c765bd8dc4138916264f20e61/lib/vquic/ngtcp2.c#L1692-L1718 because of: https://github.com/curl/curl/blob/1313d7a35620e40c765bd8dc4138916264f20e61/lib/vquic/ngtcp2.c#L1862-L1866 (ngtcp2_conn_write_pkt returned error: -502 / NGTCP2_ERR_CALLBACK_FAILURE) called by: https://github.com/JCMais/node-libcurl/blob/c563f5efadb1972aca95e3f936ce1ed4779e8c25/src/Multi.cc#L164-L165 I am not sure...

I am testing it locally again, but in the container i use `OpenSSL_1_1_1g-quic-draft-29` and ``` root@4808d4ebfb95:/app# node -e "console.log(process.versions)" { node: '14.4.0', v8: '8.1.307.31-node.33', uv: '1.37.0', zlib: '1.2.11', brotli: '1.0.7',...

Nope, getting the same error `CURLE_SEND_ERROR` followed by SIGFAULT

Seems like bare multi-uv and http3 example work with the version I compiled, I will try to run those examples now as part as nodejs callbacks, hopefully I will figure...

Providing a schema via argument / startup of the application provided by the user those erros will occure. I agree that those errors do not occure as often, but they...

That is great, but I ran into the issue when I referenced to an non existent ref. object. Aka, it throws in case of `#/bad/ref`. So it seems only maybe...

And the exception would be extended with a json pointer containing location of the bad reference and the bad reference? That would work.

Well, I am not the biggest expert, but as I would do it is extend `std::exception` or probably better extend `json::exception` and overwrite `const char* what()`. In `nlohmann::json` it seems...