We ran into the following evaluation failure: “SRPC
failure in ToolDirServer (invalid_parameter): No
runtool for this directory handle”. It happens if
there is no RunToolCalls table entry with dirHandle
as a key. Trying to reproduce that failure did not
succeed, so maybe some processes interaction had
caused that. An assertion was added before sending a
handle to the repository which ensures that it will
not result in that error if received back. This
change is in
version /vesta/vestasys.org/vesta/eval/74.
Logged In: YES
user_id=1144459
Originator: YES
Derived files that created from text values during evaluation are placed in special volatile directory that is created for each evaluation process. That directory handle is sent to repository, but the directory info for ToolDirServer is not created and not recorded in the list of current volatile directories the evaluator is using. Repository on its own should not need to contact ToolDirServer for listing or looking up that directory, but if some outside process asks repository to do that, it causes the following failures:
SRPC failure in ToolDirServer (invalid_parameter): No runtool for this directory handle (continuing...)
SRPC failure in ToolDirServer (protocol_violation): await_call isn't legal now (in state 'data_in') (continuing...)
12/Error: Failed to convert text to file: SRPC::failure (9), problem creating derived..
Error: Failed to convert text to file: SRPC::failure (9), problem creating derived.
(the fix is in the following branch /vesta/vestasys.org/vesta/eval/94.deriveds_root_handle)