Strange behaviour of cache after no memory error


I’ve described an issue, which I found during checking borderline cases of cache, at a github: GitHub Reference

Could you explain described cache behaviour? Is it a bug? Hi,

We have responded to your question in the issue :slight_smile:

In the future, please avoid cross-posting between multiple channels of communication, it will make things easier for us. GitHub issues are reserved for bug reports (your concern could have been one), and this forum is reserved for more general questions, feature requests, and community discussions. Thanks!

@thibaultcha Thanks for your support. In the next time I’ll avoid cross-posting communication.