When starting a flow from RPC with wrong parameters types there is no stacktrace on the exception

Description

This is very annoying when debugging a test because there is no clue to where the problem occurred.

After a bit of investigation, it seems to be caused by "RPCClientProxyHandler.addRpcCallSiteToThrowable" not populating the callsite of the exception thrown to the RPC client because

is probably not working as expected.

Assignee

Unassigned

Reporter

Tudor Malene

Labels

None

Sprint

None

Epic Link

None

Priority

Medium

Engineering Teams

None

Fix versions

None

Affects versions

None

Ported to...

None

Story Points / Dev Days

None

Build cut

None

Squad

None