@red-balloon-89377: i had seen

chttp

Thanks! That looks great, except it has no option for async requests that I can see. The actual reading and storing of the file can be async, because it returns a stream, but nobody can save us from the network latency. That said, even if we were to make the request async, we do wait for it to complete before returning from the node execution, so we’d probably not be gaining much?

Yea, I think the API in the ticket was currently blocking anyway. This would be a stopgap

Okay, cool 🙂 thanks.

yea, saw that. thanks

Would you like me to keep trying to figure out the SSL error with

reqwest

? If we eventually need to switch it would be useful, but I don’t have a good intuition of how much of a stopgap

chttp

is.

i'm going to look into the segfault i think.

Sounds good 🙂

the "Consume logger/console" one would interact fairly heavily with python code, but is otherwise fairly small

I thought that was going to be a bigger one

yea, it would be. i take that back. "medium to large"

Assuming I will be ooo for most of next week, I think the improve engine UI is better

ok, yes please!