They opened the API for it and I'm sending requests but the response always comes back 300ms before I send the request, is there a way of handling that with try{} predestined{} blocks? Or do I need to use the Bootstrap Paradox library?
What happens when you don't send the request after receiving the response? Please try and report back.
Finally, INTERCAL’s COME FROM statement has a practical use.
>They opened the API for it and I'm sending requests but the response always comes back 300ms before I send the request
For a brief moment I thought this was some quantum-magical side effect you were describing and not some API error.
Try using inverse promises. You get back the result you wanted, but if you don't then send the request the response is useless.
It's a bit like Jeopardy, really.
Did you try staring on your IP packets while sending the requests?
You are getting that response 300ms beforehand because your request is denied.
If you auth with the bearer token "And There Are No Friends At Dusk." then the API will call you and tell you which request you wanted to send.
Pretty sure you just need to use await-async (as opposed to async-await)
The answer is yes and no, simultaneously
Help! Every time I receive the response, an equal number of bits elsewhere in memory are reported as corrupt by my ECC RAM.
Update: I tried installing the current Boostrap Paradox library but it says I have to uninstall next years version first.
> I'm sending requests but the response always comes back 300ms before I send the request
Ah. Newbie mistake. You need to turn OFF your computer and disconnect from the network BEFORE sending the request. Without this step you will always receive a response before the request is issued.
I'm trying to write a new version of Snake game in Microsoft Q# but it keeps eating its own tail.
It think you are supposed to use a "past" object to get your results before calling the API.
Try setting up a beam-splitter router and report back with the interference pattern. If you don't see a wave pattern it might be because someone is spying on you.
Have you tried using the Schrödinger Exception Handler? It catches errors both before and after they occur simultaneously, until you observe the stack trace.