Josh Stevens
Josh Stevens
Taking this one - so you be able to map to call a contract call to get data back on index - a bit of improvements to be done on...
The main reason char(42) works quite nice as the db protects against bad mistakes from the code say the address got messed up somehow, it would throw on the DB...
you are probably right tbh char(42) it just pad it if its to short or shorten it its to long which has the same kind of issue (does not protect...
Is there no example of how to use an HTTPS clienthouse URL it seems not and hard to find examples of this
any more info on this @jaggad ive never seen this so without more info the ticket is hard to keep alive
Known thing it should really use the network to know how often it polls or even use WS to solve over fetching - I think it should share the same...
sounds good @jaggad 🔥
it's a good feature to add right now it doesn't try to map back to objects it just puts them in tuple order, so [0] = [0] of output but...
yeah this is happening as you got slack enabled and it has failed to send due to rate limiting with slack - atm it will fail fully if the slack...
Yes it will forever keep retrying it assumes in these cases the node or whatever is temp down so it is as strict as possible and just keeps going back...