-
Notifications
You must be signed in to change notification settings - Fork 0
Labels
ready for testingThis issue has been fixed and is ready for testingThis issue has been fixed and is ready for testing
Milestone
Description
If a simulation fails, I get this error:
RuntimeError: Cannot append item '{'message': 'Traceback (most recent call last):\n\n File "/home/openfoam/.cache/pypoetry/virtualenvs/simvue-integrations-HDbrc9RV-py3.10/lib/python3.10/site-packages/simvue/utilities.py", line 244, in wrapper\n return class_func(self, *args, **kwargs)\n\n File "/home/openfoam/.cache/pypoetry/virtualenvs/simvue-integrations-HDbrc9RV-py3.10/lib/python3.10/site-packages/pydantic/_internal/_validate_call.py", line 38, in wrapper_function\n return wrapper(*args, **kwargs)\n\n File "/home/openfoam/.cache/pypoetry/virtualenvs/simvue-integrations-HDbrc9RV-py3.10/lib/python3.10/site-packages/pydantic/_internal/_validate_call.py", line 111, in __call__\n res = self.__pydantic_validator__.validate_python(pydantic_core.ArgsKwargs(args, kwargs))\n\npydantic_core._pydantic_core.ValidationError: 1 validation error for Run.create_metric_threshold_alert\nsource\n Unexpected keyword argument [type=unexpected_keyword_argument, input_value=\'metrics\', input_type=str]\n For further information visit https://errors.pydantic.dev/2.10/v/unexpected_keyword_argument\n\n\nDuring handling of the above exception, another exception occurred:\n\n\nTraceback (most recent call last):\n\n File "/home/openfoam/integrations/examples/openfoam/openfoam_example.py", line 50, in openfoam_example\n run.create_metric_threshold_alert(\n\n File "/home/openfoam/.cache/pypoetry/virtualenvs/simvue-integrations-HDbrc9RV-py3.10/lib/python3.10/site-packages/simvue/utilities.py", line 251, in wrapper\n self._error(error_str)\n\n File "/home/openfoam/.cache/pypoetry/virtualenvs/simvue-integrations-HDbrc9RV-py3.10/lib/python3.10/site-packages/simvue/run.py", line 543, in _error\n raise SimvueRunError(message)\n\nsimvue.exception.SimvueRunError: `Run.create_metric_threshold_alert` Validation:\n╒═════════╤════════════╤═════════════════════════════╤═════════════════════════════╕\n│ Input │ Location │ Type │ Message │\n╞═════════╪════════════╪═════════════════════════════╪═════════════════════════════╡\n│ metrics │ [\'source\'] │ unexpected_keyword_argument │ Unexpected keyword argument │\n╘═════════╧════════════╧═════════════════════════════╧═════════════════════════════╛\n', 'timestamp': '2025-02-18T10:49:42.743996'}' to queue 'events', termination called.
This is because the termination trigger has been set due to the process erroring out, but that means the event cannot be logged. This should be fixed since it would be useful to have the stderr logged to the run
Metadata
Metadata
Assignees
Labels
ready for testingThis issue has been fixed and is ready for testingThis issue has been fixed and is ready for testing