Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -37,12 +37,8 @@ internal class CleanupDeprecatedWorkersUseCase @Inject constructor(

private fun tagsForDeprecatedWorkers() = listOf(
"TAG_PEOPLE_SYNC_WORKER_TYPE_DOWN_COUNTER", // 2023.1.0
"TAG_PEOPLE_SYNC_WORKER_TYPE_DOWNLOADER", // 2023.1.0
"TAG_PEOPLE_SYNC_WORKER_TYPE_END_SYNC_REPORTER", // 2023.1.0
"TAG_PEOPLE_SYNC_WORKER_TYPE_START_SYNC_REPORTER", // 2023.1.0
"MASTER_SYNC_SCHEDULERS", // 2023.1.0
"TAG_PEOPLE_SYNC_WORKER_TYPE_UP_COUNTER", // 2023.1.0
"TAG_PEOPLE_SYNC_WORKER_TYPE_UPLOADER", // 2023.1.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did we add these tags for cleanup in the first place? Were they used for deprecated workers and then reused for the new ones? If that's the case, don't we still want to cancel deprecated workers? If so, we should rename the tags for the current workers instead of removing old ones from cleanup.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is intended to stop old workers scheduled in previous versions of
SID to prevent crashes during migration to newer app versions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, and with the removal of these tags aren't we regressing to the same situation?

)

}