Skip to content

feat: improve start id exclusion to avoid race condition fk error#730

Open
MatheusLeall wants to merge 2 commits intomainfrom
feature/improve-start-id-exclusion-process
Open

feat: improve start id exclusion to avoid race condition fk error#730
MatheusLeall wants to merge 2 commits intomainfrom
feature/improve-start-id-exclusion-process

Conversation

@MatheusLeall
Copy link
Copy Markdown
Collaborator

Solução para o problema de FK resultante de um race condition que está ocorrendo entre uma task do celery e o acionamento de uma trigger no banco de dados

Tarefa relacionada: https://vtex-dev.atlassian.net/jira/software/projects/ENGINE/boards/4798/backlog?selectedIssue=ENGINE-3008

@MatheusLeall MatheusLeall self-assigned this Jan 26, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Jan 26, 2026

Codecov Report

❌ Patch coverage is 87.50000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 98.62%. Comparing base (1d69ba4) to head (64b40f6).

Files with missing lines Patch % Lines
temba/flows/tasks.py 66.66% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #730      +/-   ##
==========================================
- Coverage   98.62%   98.62%   -0.01%     
==========================================
  Files         647      648       +1     
  Lines       34916    34924       +8     
==========================================
+ Hits        34436    34443       +7     
- Misses        480      481       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Makes sense update a migration file that is already on database?

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.

You're right, I'll create a new migration for that. I hadn't noticed that the SQL files were called as migration execution in the init file; I'll follow the existing pattern in the repository.

@sonarqubecloud
Copy link
Copy Markdown

@MatheusLeall MatheusLeall marked this pull request as ready for review January 27, 2026 21:16
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.

2 participants