You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
handle_output_metadata deletes .extras values if they were returned on a FailedOperation object #397
Describe the bug
If the output_data passed to util.handle_output_metadata is a FailedOperation object (or corresponding dictionary) the reinstantiation of the FailedOperation object on lines 208-212 removes these values.
To Reproduce
Pass any FailedOperation object containing values in the .extras field to handle_output_metadata and note that the returned object has these values removed.
Expected behavior
All data on output_data fed to handle_output_metadata is included on the returned object, including .extras.
Additional context
The TeraChemPBSHarness and TeraChemFrontendHarness both return AtomicResult or FailedOperation objects upon success/failure of a calculation. When the FailedOperation object is passed to handle_ouput_metadata the values in the .extras field get.
I agree it shouldn't be dropping fields. I'm not able to reproduct the problem, though. The test below has extras on output_data passed into handle_output_metadata, and both tests pass, albeit it's on FailedOperation.input_data. Do you have an example of the problem?
Activity
loriab commentedon Aug 8, 2023
I agree it shouldn't be dropping fields. I'm not able to reproduct the problem, though. The test below has extras on
output_datapassed intohandle_output_metadata, and both tests pass, albeit it's onFailedOperation.input_data. Do you have an example of the problem?