-
Notifications
You must be signed in to change notification settings - Fork 13
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
Serialiser_Engine: Fix serialiser crash on failed #3086
Serialiser_Engine: Fix serialiser crash on failed #3086
Conversation
@BHoMBot check versioning |
@adecler to confirm, the following actions are now queued:
There are 14 requests in the queue ahead of you. |
@FraserGreenroyd to confirm, the following actions are now queued:
|
@FraserGreenroyd to confirm, the following actions are now queued:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed the code and it's only deleted lines which is always nice to tidy up 😄
I have then performed the following actions on this branch:
- Deserialised Test Sets for Versioning from version 3.3 to 6.1 for objects and methods
- Some failures are noted during this deserialisation, however, they are either known issues as a result of the new serialisation framework, or not related to this particular work
- Despite failures, every single test set JSON file deserialised without crashing Rhino/Grasshopper
- Objects were returned where possible
- Deserialised every dataset housed within BHoM_Datasets
- All datasets deserialised without crashing Rhino/Grasshopper
- Some errors in deserialisation as a result of failing to convert types for objects I do not currently have compiled on my machine, with all other datasets deserialising correctly
In addition, the dataset issue described in the #3066 has also stopped crashing Rhino entirely and deserialises to a dataset but with errors reported as expected.
Thus, I am happy to merge this for wider testing during our 6.2 beta close out sprint this sprint, but this improves the behaviour discussed 😄
FAO: @FraserGreenroyd The check they wish to have dispensation on is unit-tests. If you are providing dispensation on this occasion, please reply with:
|
@BHoMBot this is a DevOps instruction. I am authorising dispensation to be granted on check ref. 14265547610 |
@FraserGreenroyd I have now provided a passing check on reference |
@BHoMBot check ready-to-merge |
@FraserGreenroyd to confirm, the following actions are now queued:
|
Issues addressed by this PR
Closes #3066
As detailed in the issue, the BHoM UI was crashing on the deserialisation of a specific dataset. It appears that the 'failed' boolean that is passes up from properties to parents was used to force a different deserialisation behaviour inside the
SetProperties
method.As the only place where the 'failed' boolean is used for a conditional check is inside the
SetProperty
method (where it is incorrectly used), I would recommend to get rid of that boolean altogether. We agreed with @FraserGreenroyd to do this in two phases:SetProperty
method (this PR)Test files