Project

General

Profile

Actions

Bug #661

closed

city_freeze_workers_queue() not setting needs_arrange for cities already in queue

Added by Marko Lindqvist 7 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Category:
Server
Target version:
Start date:
05/22/2024
Due date:
% Done:

0%

Estimated time:

Description

I've been debugging a problem where city has not been refreshed when it should. Turns out the sequence is:

1) City gets added to the refresh queue by city_freeze_workers_queue(). needs_arrange gets set
2) Somewhere the city gets arranged. needs_arrange gets cleared
3) city_freeze_workers_queue() gets called for the same city again. It detects that the city is already in the queue, and does not nothing, DOESN'T EVEN SET needs_arrange
4) City get unqueued. city_thaw_workers() sees that needs_arrange is already cleared, and does no arrange


Files

Actions #1

Updated by Marko Lindqvist 7 months ago

Actions #2

Updated by Marko Lindqvist 7 months ago

Applies also to S2_6.

Actions #3

Updated by Marko Lindqvist 7 months ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF