Stephen R. van den Berg wrote: >Stephen R. van den Berg wrote: >>I upgraded all my systems to the bleeding edge last wednesday, sadly >>it does not fix the TB message-status-cache-issue.
>One of my customers just checked and found the following (all tests >against last week's aox): >- On TB 31.6.0 it works fine, no status issues whatsoever. >- On TB 38.5.1 it forgets the changes after switching maps back and forth. >- Upgrading the machine that has TB 31.6.0 to the latest TB (on MacOSX) > results in a TB which has exactly the same problem as TB 38.5.1 on the > machine where it already didn't work. >- Shortly after every full hour, all statuses are synced and show their > correct intended values. Any hints where I should look? The problem is still present, and I'd like to avoid having to bisect the codebase. -- Stephen.
