[
https://issues.apache.org/jira/browse/TINKERPOP-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325728#comment-16325728
]
ASF GitHub Bot commented on TINKERPOP-1862:
---
Github user PBGraff commented o
Github user PBGraff commented on the issue:
https://github.com/apache/tinkerpop/pull/777
Tests pass now, good to go from me.
---
[
https://issues.apache.org/jira/browse/TINKERPOP-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325701#comment-16325701
]
ASF GitHub Bot commented on TINKERPOP-1861:
---
Github user PBGraff commented o
Github user PBGraff commented on the issue:
https://github.com/apache/tinkerpop/pull/772
I think all test problems have now been fixed. My concern is that people
may still override/implement the old method and not the new one, thus yielding
programs that don't execute properly. It wil
Github user FlorianHockmann commented on a diff in the pull request:
https://github.com/apache/tinkerpop/pull/774#discussion_r161403447
--- Diff:
gremlin-dotnet/test/Gremlin.Net.IntegrationTest/Gherkin/CommonSteps.cs ---
@@ -236,6 +237,11 @@ private static object ToLambda(string st
[
https://issues.apache.org/jira/browse/TINKERPOP-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325671#comment-16325671
]
ASF GitHub Bot commented on TINKERPOP-1860:
---
Github user FlorianHockmann com
[
https://issues.apache.org/jira/browse/TINKERPOP-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325567#comment-16325567
]
ASF GitHub Bot commented on TINKERPOP-1868:
---
Github user FlorianHockmann com
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/776
```
$ docker/build.sh -t -i
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache TinkerPop .
First of all: if you're not manually enabling the memory-efficient mode,
you get the exact same behaviour as now.
With the memory-efficient mode enabled, a few semantics change (by design):
* setting a property that is not schema-conform may (IMO *should*, but
that depends on the implementation) t
