We use the private temp storage to generate a gist (ingested, failed, warnings). This storage is specific to each user and is bound to the user sending the processing. But bc Hydroponics runs on the background and is detached from the actual user sending data, the private storage available to that "drush" session is not the same as the one used by the user sending the data, which leads to 0 ingested being shown, even if the logs are accurate (bc its a file + cache-time == o added recently)
I will try to figure out a way of either loading the user (which is in the queue item data) or using a different method for keeping track of this info, so we don't have this issue. That said, that info (bc it is temporary) expires after 6 days... so we should also make sure we don't show any at all, if the storage is empty (instead of making it 0 valued)
What?
We use the private temp storage to generate a gist (ingested, failed, warnings). This storage is specific to each user and is bound to the user sending the processing. But bc Hydroponics runs on the background and is detached from the actual user sending data, the private storage available to that "drush" session is not the same as the one used by the user sending the data, which leads to 0 ingested being shown, even if the logs are accurate (bc its a file + cache-time == o added recently)
I will try to figure out a way of either loading the user (which is in the queue item data) or using a different method for keeping track of this info, so we don't have this issue. That said, that info (bc it is temporary) expires after 6 days... so we should also make sure we don't show any at all, if the storage is empty (instead of making it
0valued)@alliomeria this is what we saw today.