Open ndegwamartin opened 1 month ago
@ndegwamartin Can you add some data for the valid cycle.
@ndegwamartin Did you share the data with @aditya-07 for the valid cycle? @ndegwamartin Do you mean the resources are already in sync, and it only throws exceptions when uploading updates during a valid cycle?
@aditya @santosh-pingle for context the above screenshot was captured after migrating to the latest codebase.
Attached is the SQL to recreate the state of the LocalChangeEntity
and LocalChangeResourceReferenceEntity
resources_db-LocalChanges.sql.zip . Let me know if you need data from any of the other tables.
I'm also happy to jump on a call to clarify further
@aditya-07 related to the above these are the resources(count by resource type) that could not be synced via Upload
@aditya @santosh-pingle for context the above screenshot was captured after migrating to the latest codebase.
Attached is the SQL to recreate the state of the
LocalChangeEntity
andLocalChangeResourceReferenceEntity
resources_db-LocalChanges.sql.zip . Let me know if you need data from any of the other tables.I'm also happy to jump on a call to clarify further
@ndegwamartin The .zip doesn't have sql to recreate LocalChangeResourceReferenceEntity
.
@aditya-07 you are correct, appears the LocalChangeResourceReferenceEntity
was not part of the archive. I've recreated the scripts with a new data set attached here - LocalChangesSQL.zip
hi @aditya-07 any update on progress here? Thank you!
Describe the bug After the latest updates to Sync, an exception is thrown on the code block/line here :
The check throws an exception if it detects a cycle, however there could be valid cycles .
See screenshot (Shows breakpoint debugging of code block/line above )
Component Core library - Engine
To Reproduce Steps to reproduce the behavior:
Expected behavior Sync upload should be successful
Screenshots
Screenshot shows breakpoint debugging of line here
Smartphone (please complete the following information): N/A
Additional context N/A
Would you like to work on the issue? @aditya-07 worked on the original issue