[ 
https://issues.apache.org/jira/browse/TINKERPOP-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118548#comment-16118548
 ] 

ASF GitHub Bot commented on TINKERPOP-1743:
-------------------------------------------

GitHub user okram opened a pull request:

    https://github.com/apache/tinkerpop/pull/689

    TINKERPOP-1743: LambdaRestrictionStrategy does not catch lambdas passed to 
sack()

    https://issues.apache.org/jira/browse/TINKERPOP-1743
    
    Fixed a lambda-leak in `SackValueStep` where `BiFunction` must be tested 
for true lambda status.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/tinkerpop TINKERPOP-1743

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tinkerpop/pull/689.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #689
    
----
commit 1e04d928a0b87f6aa82e77756f5458d62b14a6d9
Author: Marko A. Rodriguez <okramma...@gmail.com>
Date:   2017-08-08T16:12:11Z

    Fixed a lambda-leak in SackValueStep where BiFunction could be a real 
lambda.

----


> LambdaRestrictionStrategy does not catch lambdas passed to sack()
> -----------------------------------------------------------------
>
>                 Key: TINKERPOP-1743
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1743
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.1.7
>            Reporter: stephen mallette
>            Assignee: Marko A. Rodriguez
>
> {code}
> gremlin> g.V().limit(1).map{ System.exit(1) }
> The provided traversal contains a lambda step: LambdaMapStep(lambda)
> Type ':help' or ':h' for help.
> Display stack trace? [yN]n
> gremlin> g.withSack(0).V().limit(1).sack{ v,s -> System.exit(1) }
> /// nothing
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to