TobyJaguar

@tobyjaguar

84 Following

15 Followers

TobyJaguar pfp

It’s all about the water!

0 reply

0 recast

0 reaction

TobyJaguar pfp

Gonna be awkward applying for those defense contractor jobs

0 reply

0 recast

0 reaction

TobyJaguar pfp

How do you limit an infinite gossip loop? Where is the check done if the hub has already seen a message and then to not send it back out?

0 reply

0 recast

0 reaction

TobyJaguar pfp

been listening to synthwave lately for this

0 reply

0 recast

0 reaction

TobyJaguar pfp

Does any one play pixels?

0 reply

0 recast

0 reaction

TobyJaguar pfp

Better spin up some brain flayer servers

0 reply

0 recast

0 reaction

TobyJaguar pfp

0 reply

0 recast

0 reaction

TobyJaguar pfp

I see this client connect in every route: const client = await pool.connect(); Does this not make a new connection for every api request? That is a lot of connections. Can you move the connect to the top level, and reuse the same connection until it auto disconnects, and then reest the connx?

0 reply

0 recast

0 reaction

TobyJaguar pfp

aight, I am a little confused by the repo, did you mock the code snippet that you posted? You can follow me so I can DM you, but I don't see the release in the catch, which may make @data-nerd 's point accurate, also...

1 reply

0 recast

0 reaction

TobyJaguar pfp

arg...I am working on ethergrams this weekend, but if I get a chance I'll take a look

0 reply

0 recast

0 reaction

TobyJaguar pfp

okay, last time I buy testnet ETH. Can anyone send me some Base Sepolia? -> 0xa3d6171E8A0DCB9F28F56bCbA45882e44fd61dca 😘

0 reply

0 recast

0 reaction

TobyJaguar pfp

did you get this sorted?

1 reply

0 recast

0 reaction

TobyJaguar pfp

the errors should be caught though as well, so you could use the finally block or move the release to the catch block. Of course all async/await calls should be wrapped in a try/catch ;)

1 reply

0 recast

1 reaction

TobyJaguar pfp

will take a look but no promises 😜

0 reply

0 recast

0 reaction

TobyJaguar pfp

good talk here by Martenson: https://youtu.be/3hOdQNDFY5E?si=DcNThHJYXbqH5a3r

0 reply

0 recast

0 reaction

TobyJaguar pfp

kind of tough not to know the infra, I am mostly on aws infra these days. Clearly the above is not working 🤣 , or it may be correct but isn't working with your infra. Can you verify that the connections are in fact being released? I will just be asking annoying questions at this point

1 reply

0 recast

0 reaction

TobyJaguar pfp

what the hell is that $3B of debt?

0 reply

0 recast

0 reaction

TobyJaguar pfp

are insiders not dumping their shares?

1 reply

0 recast

0 reaction

TobyJaguar pfp

but it ain't 😅

1 reply

0 recast

0 reaction

TobyJaguar pfp

so the issue is the connections, not the query timeouts? As already stated, how are connections being released? Does each query open a new connection, and does that connection get released after the query? Kind of need to know the setup

1 reply

0 recast

0 reaction