Ben
Ben
Hey @lokisisland, do you think you can take a look at this? :)
Hi @jafitzwater you already noticed that this does not work right now out of the box. A NEARBY search is currently limited to either no boundary, or a search radius...
hmm 🤔 `NEARBY fleet POINT 33.462 -112.268 OBJECT {}` But that looks confusing, given the syntax of the other searches. It would also be hell for existing clients. edit: `NEARBY...
Hey, tile38 sends the events when the underlying spatial query resolves. meaning that if you have a hook whos query takes 50ms and the next event in line resolves in...
Please correct me if I am wrong, but I am pretty sure `Promise.all` does not guarantee that commands resolve in order. It only attempts to send both at the same...
I'm sorry I lost you. I cannot seem to properly understand what you do and what you expect to happen. If you send 10 `SET` in a `Promise.all` you cannot...
Glad you found a solution @eduardotang 🙏
this was a very generic description of an issue four years ago, and your comment does not add anything to it. Do you think you can create a new issue...
optionally i believe adding `tls: true` would also work.
i have a working first draft, where whenever a `REDIS_URL` is present in the configService I change connection parameters. ```javascript private getConnection() { const hasUrl = this.configService.config.REDIS_URL !== ''; return...