Unexpected response from RPC API getSignaturesForAddress when until sig not found

[jstarry]

Problem

When an RPC node receives a getSignaturesForAddress request and cannot find the signature used in the until parameter, it will just return a list of the most recent signatures (up to the limit). This is unexpected in cases where a signature has been confirmed by the cluster but the contacted RPC node has not yet confirmed the signature yet because it is slightly behind. See issue here: #24417

Proposed Solution

If until cannot be found, return an error response

[jstarry]

@CriesofCarrots what do you think about the proposed solution here?

[CriesofCarrots]

I think we may want different handling depending on whether a provided before signature is found or not -- I want to think through that a little more. But in the case of no before and not-found until, yes, I think an error response makes a lot of sense.

[ghost]

This is still an issue, any updates on this? thanks

[CriesofCarrots]

The proposed fix isn't completely trivial to implement, since we support before/until signatures that don't involve the specified address, and since we check both Blockstore and Bigtable for results. I'd be happy to look a PR for this, though, @jstarry