Resource not found in cache

[jirenius]

Issue

ResClient may, in case of high activity, give the error:

Resource not found in cache.

Even when the resource should have been available in the cache.

How to reproduce

Not yet known.

[CristianWesleyFront]

+1

[jirenius]

I failed to replicate the bug.

The bug that might have been the cause is that, when a cached resource is retrieved from the cache, using ResClient.get(rid), any current running eviction timeout will continue to tick.

If the resource was retrieved just moments before the timeout was reached, the resource might get evicted before the app has time to call on.

If that is the cause, then this issue is resolved in #40

If the bug is encountered again, this issue will be reopened.

[jirenius]

Reopening this issue because the bug still exists.

Probable cause

It seems to be caused by ResClient not sending an equal amount of unsubscribe requests to match the number of direct subscriptions held when unsubscribing/evicting a resource. As stated by the RES Client Specification:

It is possible to make multiple direct subscriptions on a resource. It will be considered directly subscribed until an equal number of unsubscribe requests has been made.

Even if a resource holds multiple direct subscriptions, ResClient only sends a single unsubscribe request before removing it from the cache. However, Resgate is true to the specification, and will assume the client still has the item cached.

[jirenius]

Resolved in #41

[jirenius]

Reopening this issue once again, as the bug still exists.
I am trying to produce full communication logs when this appears.