Change Details

This avoids re-fetching all origin visits / origin visit statuses when new visits happen. This is only a workaround. When voiding the cache, the error will still happen. We need to rework the overall visit/visit-status fetching, the code is hard to follow through. Discussing with @anlambert, there is yet another improvement we could lift (independently from this). Related to T3905

This clarifies the current code and optimize the re-fetching of all origin visits / origin visit statuses when new visits happen. It's an optimization providing previous visits are in the cache already. The second part serves also as a workaround of some problematic origins (the ones with a high number of visits). It's only a workaround though because when voiding the cache (e.g. restart the cache service), the initial error (e.g. crash 500 or 502, ...) will still happen. Another change is on its way to try and fix that specific problem. Related to T3905 Related to T3905

This avoids re-fetching all origin visits / origin visit statuses when newclarifies the current code and optimize the re-fetching of all origin visits / happen. This is only a workaround. When voiding the cache, the error will still happen. We need to rework the overall visit/visit-status fetching,origin visit statuses when new visits happen. the code is hard to followIt's an optimization providing previous throughvisits are in the cache already. Discussing with @anlambertThe second part serves also as a workaround of some problematic origins (the ones with a high number of visits). It's only a workaround though because when voiding the cache (e.g. restart the cache service), the initial error (e.g. crash 500 or 502, there is yet another improvement we could lift (independently...) from this)will still happen. Another change is on its way to try and fix that specific problem. Related to T3905 Related to T3905