-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Trying to sync sena 3 twice via fw headless results in an error #1251
Comments
Integration test will:
|
This comment has been minimized.
This comment has been minimized.
Now I'm getting the same exception. At a first guess, this might be a problem of operation ordering: complex forms needs to be added after their component parts. But I'll start by writing the test so that we can prove that that's the issue. |
Discussed with @hahn-kev, we're going to solve this with a transaction system where updates can be batched and added in a single commit. That way the compoent and its parts would have all been added together and there wouldn't be a "missing component part" error. I'll just focus on writing the test, and then @hahn-kev will implement the transaction system to make the test pass. |
I realized last night while thinking about this that transactions aren't really going to help, though they might make it easier to fix, ultimately a create entry call is going to try to make all the changes at once (complex forms etc), and that design is always going to be difficult. So I'm starting to wonder if we need to split the create entry calls out so that they don't try to create complex form references, and then once we've created all new entries, then we can apply the rest of the entry data. For example a change log might look like this:
|
fixed in #1256 |
Describe the bug
I was testing out calling fw headless sync and if I call it twice for sena 3, the second time I get the following error:
This is assuming you've never synced this project before.
To Reproduce
Expected behavior
no error and a result saying there's no changes (considering we just synced)
The text was updated successfully, but these errors were encountered: