Skip to content

Conversation

@ArtyomSavchenko
Copy link
Member

@ArtyomSavchenko ArtyomSavchenko commented Nov 21, 2025

Do nothing for now due to the following:

  • previous implementation was very slow and caused issues in production
  • old communication is used now on Huly and for self-hosters, so it is not required

Lets add a migration tool with fixed performance later

Signed-off-by: Artem Savchenko <armisav@gmail.com>
Signed-off-by: Artem Savchenko <armisav@gmail.com>
Signed-off-by: Artem Savchenko <armisav@gmail.com>
@huly-github-staging
Copy link

Connected to Huly®: UBERF-14186

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR disables a slow-performing notification migration that caused production issues. The migrateReactionNotifications function is converted to a no-op while maintaining its registration in the migration pipeline to preserve migration state tracking. Since the old communication system is still in use, the migration is deferred to a future tool with improved performance (tracked as UBERF-14185).

Key changes:

  • Gutted migrateReactionNotifications function body and replaced with explanatory comment
  • Removed unused type imports that were only needed by the deleted migration logic
  • Cleaned up activity-related imports no longer referenced in the file

@ArtyomSavchenko ArtyomSavchenko merged commit fd4854c into develop Nov 21, 2025
21 checks passed
@BykhovDenis BykhovDenis deleted the remove-migration branch November 23, 2025 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants