You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2017/08/16 15:12:00 UTC

[jira] [Closed] (TINKERPOP-1744) Gremlin .NET: Exception from sync execution gets wrapped in AggregateException

     [ https://issues.apache.org/jira/browse/TINKERPOP-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-1744.
---------------------------------------

You can fully close tickets when they are done (rather than just resolve). If you didn't have rights to do that or something I'll go check that now. Next time you should be good to go for sure.

> 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
>    Affects Versions: 3.2.5
>            Reporter: Jorge Bay
>            Assignee: Jorge Bay
>             Fix For: 3.2.6
>
>
> 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)