feat(): Convert zone not found errors to warnings in entity updates #1708
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So the subsequent process can still continue
Note
Shifts entity metadata update failures from hard errors to collected warnings, allowing processing to continue.
_get_boundary_full_namenow returns(full_name, warning)instead of raisingFlow360BoundaryMissingError; import removed_SurfaceEntityBase._update_entity_info_with_metadatareturnsOptional[str]warning and only setsprivate_attribute_full_namewhen found_update_entity_full_name(model, target_entity_type, volume_mesh_meta_data)now returnsList[str]of warnings, aggregating from nested entitiesSimulationParams._update_param_with_actual_volume_mesh_metareturnslist[str]of warnings (aggregates surface and volume warnings) while still updating zone boundaries via_update_zone_boundaries_with_metadataWritten by Cursor Bugbot for commit 5904d94. This will update automatically on new commits. Configure here.