Change Details

Instead of iterating over all origin visits to find the one we are insterested in, use a simpler storage api call. In case of a huge number of visits for an origins, this makes the resolution spin out of control until it crashes (when the cache is initially empty). Related to T3905

Instead of iterating over all origin visits to find the one we are insterested in, use a simpler storage api call. In case of a huge number of visits for an origin, this currently makes the page queried crash (when the cache is initially empty). This fixes this by calling a new endpoint which only retrieves the most recent visit (and the most visit status associated to that visit). This bypasses the cache which is not needed here. Related to T3905

Instead of iterating over all origin visits to find the one we are insterested in, use a simpler storage api call. In case of a huge number of visits for an origins, this makes the resolution spin out of control until it crashes (when the cache is initially empty)currently makes the page queried crash (when the cache is initially empty). This fixes this by calling a new endpoint which only retrieves the most recent visit (and the most visit status associated to that visit). This bypasses the cache which is not needed here. Related to T3905