Closed edouardbruelhart closed 6 months ago
In fact, the problem is more a timing problem. The places left are correctly reached, but as the number of samples (and the new storage point that is hdd) slows down the process and has a latency. So I will change the behaviour by adding a local counter and ask the places left only when rack is scanned.
Problem should be resolved. The problem came from the new directus setup that used redis as cache. After removing redis instance, it seems that there is no more latency between API requests and database response.
In falcon mode, the count of free places in the rack is no more working. Possibility to add more than 24 samples in a single rack. Appened after directus instance update, so should be related to the directus API.