[
https://issues.apache.org/jira/browse/TINKERPOP-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119574#comment-16119574
]
Florian Hockmann commented on TINKERPOP-1744:
---------------------------------------------
We should just make sure that we throw all {{InnerExceptions}} of the
{{AggregateException}} as there could be (theoretically) more than one.
> Gremlin .NET: Exception from sync execution gets wrapped in AggregateException
> ------------------------------------------------------------------------------
>
> Key: TINKERPOP-1744
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1744
> Project: TinkerPop
> Issue Type: Bug
> Components: language-variant
> Reporter: Jorge Bay
>
> When getting a server side exception and executing a traversal synchronously
> (ie: {{Next()}}, {{ToList()}}, ...), Gremlin.Net throws the original
> exception wrapped in a {{AggregateException}}, which is not desired.
> This is caused by the {{Task.Wait()}} call on {{RemoteStrategy.Apply()}}
> method.
> We should catch the wrapped exception and throw the original.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
