Integrate sync_schema_config_fields fixes into main#8067
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Fixes #8065
Integrate sync_schema_config_fields fixes into main.
This ports the release branch schema config fix into
mainwhile preserving the newer main-branch schema config locking and de-duplication logic.Checklist
self-explanatory (or properly documented)
Testing instructions
ve/bin/python manage.py sync_schema_config_fields --discipline-id <discipline_id>.accessionId,localityId,collectionObjectId, or other{table}Idfields.ve/bin/python manage.py sync_schema_config_fields --discipline-id <discipline_id> --apply.