-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync issue #1524
Comments
Issue root-cause is migration "V1_342_1__SetDefaultsForStandardReportCardInput.sql", which does report_card new fields edit conditionally. To resolve the issue, changed the prod_vars value to
Only entities that were modified today and included under endOfLifeEndpoints was report-cards. select count(*) from dashboard where last_modified_date_time > '2024-09-26'::timestamp; --0
select count(*) from report_card where last_modified_date_time > '2024-09-26'::timestamp; --88
select count(*) from dashboard_section where last_modified_date_time > '2024-09-26'::timestamp; --0
select count(*) from dashboard_filter where last_modified_date_time > '2024-09-26'::timestamp; --0
select count(*) from dashboard_section_card_mapping where last_modified_date_time > '2024-09-26'::timestamp; --0
select count(*) from group_dashboard where last_modified_date_time > '2024-09-26'::timestamp; --0 |
sync for cini working now |
Further testing suggestions, After fresh sync on 9.4 for cini user
|
|
@AchalaBelokar Does the issue get resolved on fresh sync.? Need this info to provide proper fix.
|
@himeshr no after doing the fresh sync I am facing the same issue. |
And I am download 10.0 version it is stuck on loading page that is on avni. |
…during dbMigration
Discussion notes
Code changes done |
|
|
… removed get recent input duration default value from getter. realm initialises list to empty array by default. initialise with default values for duration input standard report card types.
RealmDB file of version 9.4 to test the fix using 10.0.1 apk. Do put db and login as anjalifc user of cini org. |
|
AAh, this is because of my mistake while specifying test case.. Instead of this test case:1> Login using 9.4
Follow this one:1> Login using 9.4
The reason is that, since DBMigration for both 10.0 and 10.0.1 is the same, it'll not resolve the issue on install of 10.0.1 on top of 10.0. |
User: anjalifc@cini, anjalib@cini, anjalibps@apfodisha
apk: 9.4
env: prod
fresh sync
Stacktrace:
The text was updated successfully, but these errors were encountered: