fix: issue with interruptible commands on interrupt.

[prmukherj]

Context

Calling session.settings.solution.run_calculation.interrupt() from within a SolverEvent.ITERATION_ENDED callback causes the concurrently-blocking run_calculation.iterate() gRPC call on the main thread to raise RuntimeError: () rather than returning normally — even though Fluent itself stops the solver cleanly and prints Done. Operation stopped.

The consequence is that any code following the iterate() call (writing case files, post-processing, etc.) is silently skipped. This makes event-driven convergence monitoring unreliable in practice.

Change Summary

1. Pass is_interruptible from the solver to the settings root.
2. Use that to check if any interruptible commands raise RuntimeError: (), and if so swallow the error.
3. Added test with the case in the particular bug to check the behavior for all Fluent versions.

Rationale

Ideally Fluent should not raise an error in this case, but currently it is interrupting cleanly and raising an error with blank message unlike in other cases where the message strings are populated appropriately. Hence using that to handle this particular bug.

Impact

Users will not face the situation as described, and will be able to develop similar workflows seamlessly.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[seanpearsonuk]

@prmukherj Isn't this all done and ready?

[prmukherj]

@prmukherj Isn't this all done and ready?

Ready now @seanpearsonuk