Skip to content

Conversation

@benflexcompute
Copy link
Collaborator

@benflexcompute benflexcompute commented Jan 9, 2026

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_name now returns (full_name, warning) instead of raising Flow360BoundaryMissingError; import removed
  • _SurfaceEntityBase._update_entity_info_with_metadata returns Optional[str] warning and only sets private_attribute_full_name when found
  • _update_entity_full_name(model, target_entity_type, volume_mesh_meta_data) now returns List[str] of warnings, aggregating from nested entities
  • SimulationParams._update_param_with_actual_volume_mesh_meta returns list[str] of warnings (aggregates surface and volume warnings) while still updating zone boundaries via _update_zone_boundaries_with_metadata

Written by Cursor Bugbot for commit 5904d94. This will update automatically on new commits. Configure here.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8c7b03eb84

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

_update_entity_full_name(self, _VolumeEntityBase, volume_mesh_meta_data)
warnings = []
warnings.extend(_update_entity_full_name(self, _SurfaceEntityBase, volume_mesh_meta_data))
warnings.extend(_update_entity_full_name(self, _VolumeEntityBase, volume_mesh_meta_data))
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Volume entities silently fail without generating warnings

Medium Severity

The PR converts surface entity "zone not found" errors to warnings, but _VolumeEntityBase._update_entity_info_with_metadata still returns None and was not updated to return warnings. When _update_entity_full_name is called with _VolumeEntityBase, it attempts to collect warnings from _update_entity_info_with_metadata, but the method always returns None. This means volume zones that can't be found in metadata will silently fail to update without generating any warning, defeating the PR's purpose of surfacing these issues as warnings.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants