[jira] [Commented] (TINKERPOP-1600) Consistent use of base 64 encoded bytes for SASL negotiation

[ https://issues.apache.org/jira/browse/TINKERPOP-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827552#comment-15827552 ] ASF GitHub Bot commented on TINKERPOP-1600: --- Github user vtslab commented on the issue:

[GitHub] tinkerpop issue #533: TINKERPOP-1600 Added base64 encoded string to sasl cha...

Github user vtslab commented on the issue: https://github.com/apache/tinkerpop/pull/533 I agree with your explanation that a byte array returned from gremlin server as the result of a query does not crash gremlin driver (and I also checked it manually). Sorry for the confusion

[jira] [Commented] (TINKERPOP-1600) Consistent use of base 64 encoded bytes for SASL negotiation

[ https://issues.apache.org/jira/browse/TINKERPOP-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827516#comment-15827516 ] ASF GitHub Bot commented on TINKERPOP-1600: --- Github user vtslab commented on the issue:

[GitHub] tinkerpop issue #533: TINKERPOP-1600 Added base64 encoded string to sasl cha...

Github user vtslab commented on the issue: https://github.com/apache/tinkerpop/pull/533 Just undoing [this commit](https://github.com/apache/tinkerpop/pull/534/commits/62648242c6576b020d2dd2933b89b9d69e87fed0) in TINKERPOP-1566 and merging in TINKERPOP-1600 does not work for me, see

[jira] [Created] (TINKERPOP-1605) gremlin-console 3.2.3 -e can no longer take paths relative to current working directory

Xian Yi Teng created TINKERPOP-1605: --- Summary: gremlin-console 3.2.3 -e can no longer take paths relative to current working directory Key: TINKERPOP-1605 URL:

[jira] [Commented] (TINKERPOP-1600) Consistent use of base 64 encoded bytes for SASL negotiation

[ https://issues.apache.org/jira/browse/TINKERPOP-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826969#comment-15826969 ] ASF GitHub Bot commented on TINKERPOP-1600: --- Github user okram commented on the issue:

[jira] [Created] (TINKERPOP-1604) Let evaluate() handle : commands e.g. :remote connect

Xian Yi Teng created TINKERPOP-1604: --- Summary: Let evaluate() handle : commands e.g. :remote connect Key: TINKERPOP-1604 URL: https://issues.apache.org/jira/browse/TINKERPOP-1604 Project: TinkerPop

[GitHub] tinkerpop issue #536: TINKERPOP-1602 Support SSL client certificate authenti...

Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/536 And it does. Yay. :+1: --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[jira] [Commented] (TINKERPOP-1602) Support SSL client certificate authentication

[ https://issues.apache.org/jira/browse/TINKERPOP-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826857#comment-15826857 ] ASF GitHub Bot commented on TINKERPOP-1602: --- Github user robertdale commented on the issue:

[GitHub] tinkerpop issue #536: TINKERPOP-1602 Support SSL client certificate authenti...

Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/536 Just wondering if posting a comment after updating the title will trigger JIRA to connect (or however that works). --- If your project is set up for it, you can reply to this email and have

[jira] [Updated] (TINKERPOP-1602) Support SSL client certificate authentication

[ https://issues.apache.org/jira/browse/TINKERPOP-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-1602: --- Fix Version/s: 3.2.4 > Support SSL client certificate authentication >

[GitHub] tinkerpop issue #536: Support SSL client certificate authentication

Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/536 @spmallette before you say it, I know I have to update changelog and update docs. :boom: --- If your project is set up for it, you can reply to this email and have your reply appear on

Re: [DISCUSS] Bump to Groovy 2.4.8

The bump to 2.4.8 is done now - I've published fresh SNAPSHOTs from 3.1.x on up the line. On Sat, Jan 14, 2017 at 11:16 AM, Stephen Mallette wrote: > Groovy 2.4.8 just released. It has a lot of bug fixes, a couple of which > are important to TinkerPop: > >

[GitHub] tinkerpop pull request #531: Added more recipes

Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/531 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (TINKERPOP-1565) GraphSON 3.0 updates -- supporting attachment, maintaining consistency, and reducing verbosity

[ https://issues.apache.org/jira/browse/TINKERPOP-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1565: Labels: (was: breaking) Fix Version/s: 3.3.0 Summary:

[GitHub] tinkerpop issue #531: Added more recipes

Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/531 VOTE +1. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Commented] (TINKERPOP-1601) LazyBarrierStrategy should not check is.testing

[ https://issues.apache.org/jira/browse/TINKERPOP-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826395#comment-15826395 ] ASF GitHub Bot commented on TINKERPOP-1601: --- Github user okram commented on the issue:

[GitHub] tinkerpop issue #535: TINKERPOP-1601 LazyBarrierStrategy should not check is...

Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/535 I was thinking more about this specific problem. The real problem is `ProfileTest`, not `LazyBarrierStrategy`. We need to generalize all the `ProfileTest` test cases such that they not be concerned

[GitHub] tinkerpop issue #531: Added more recipes

Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/531 I went through all the code snippets again, optimized a few math examples and I think it's all looking good now. VOTE: +1 --- If your project is set up for it, you can reply to this

[jira] [Commented] (TINKERPOP-1599) implement real gremlin-python driver

[ https://issues.apache.org/jira/browse/TINKERPOP-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826328#comment-15826328 ] stephen mallette commented on TINKERPOP-1599: - All of those are good ideas. From my

[jira] [Commented] (TINKERPOP-1599) implement real gremlin-python driver

[ https://issues.apache.org/jira/browse/TINKERPOP-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826322#comment-15826322 ] David M. Brown commented on TINKERPOP-1599: --- Good point. I moved the

[jira] [Commented] (TINKERPOP-1600) Consistent use of base 64 encoded bytes for SASL negotiation

[ https://issues.apache.org/jira/browse/TINKERPOP-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826304#comment-15826304 ] ASF GitHub Bot commented on TINKERPOP-1600: --- Github user davebshow commented on the issue:

[GitHub] tinkerpop issue #533: TINKERPOP-1600 Added base64 encoded string to sasl cha...

Github user davebshow commented on the issue: https://github.com/apache/tinkerpop/pull/533 All of my driver tests succeed against this branch. They use `'saslMechanism': 'PLAIN'`, so they don't expect any `sasl` value to be returned. VOTE +1 --- If your project is set up

[jira] [Commented] (TINKERPOP-1601) LazyBarrierStrategy should not check is.testing

[ https://issues.apache.org/jira/browse/TINKERPOP-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826099#comment-15826099 ] ASF GitHub Bot commented on TINKERPOP-1601: --- Github user dkuppitz commented on the issue:

[GitHub] tinkerpop issue #535: TINKERPOP-1601 LazyBarrierStrategy should not check is...

Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/535 That was my plan. kinda. I was going to open a new ticket to get rid of `is.testing` altogether. --- If your project is set up for it, you can reply to this email and have your reply appear on

[jira] [Commented] (TINKERPOP-1601) LazyBarrierStrategy should not check is.testing

[ https://issues.apache.org/jira/browse/TINKERPOP-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826062#comment-15826062 ] ASF GitHub Bot commented on TINKERPOP-1601: --- Github user okram commented on the issue:

[GitHub] tinkerpop issue #535: TINKERPOP-1601 LazyBarrierStrategy should not check is...

Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/535 There are numerous areas where `is.testing` is used for strategies. We shouldn't just do this for one of them and push a PR. We should overhaul the entire system so we don't have some parts of the

[jira] [Created] (TINKERPOP-1603) Remove support for SASL byte array in protocol

stephen mallette created TINKERPOP-1603: --- Summary: Remove support for SASL byte array in protocol Key: TINKERPOP-1603 URL: https://issues.apache.org/jira/browse/TINKERPOP-1603 Project: TinkerPop

[GitHub] tinkerpop issue #534: Tinkerpop 1566 Kerberos

Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/534 I see that you renamed the title, but it's not exactly what I had. If you don't prefix the title with the actual JIRA identifier (which is all caps and has the dash) the automation won't work.

[GitHub] tinkerpop pull request #534: Tinkerpop 1566 Kerberos

Github user spmallette commented on a diff in the pull request: https://github.com/apache/tinkerpop/pull/534#discussion_r96403984 --- Diff: gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/ser/AbstractGryoMessageSerializerV1d0.java --- @@ -301,9 +301,12 @@ private

[jira] [Created] (TINKERPOP-1602) Support SSL client certificate authentication

Robert Dale created TINKERPOP-1602: -- Summary: Support SSL client certificate authentication Key: TINKERPOP-1602 URL: https://issues.apache.org/jira/browse/TINKERPOP-1602 Project: TinkerPop

[jira] [Commented] (TINKERPOP-1549) Implement skip()

[ https://issues.apache.org/jira/browse/TINKERPOP-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825943#comment-15825943 ] ASF GitHub Bot commented on TINKERPOP-1549: --- Github user asfgit closed the pull request at:

[jira] [Closed] (TINKERPOP-1549) Implement skip()

[ https://issues.apache.org/jira/browse/TINKERPOP-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kuppitz closed TINKERPOP-1549. - Resolution: Fixed Fix Version/s: 3.3.0 > Implement skip() > >

[GitHub] tinkerpop pull request #529: TINKERPOP-1549 Implement skip()

Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/529 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] tinkerpop issue #533: TINKERPOP-1600 Added base64 encoded string to sasl cha...

Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/533 The driver shouldn't crash by sending a byte array in the results, because it is only the SASL authentication process that was expecting `byte[]`. When it would find a `String` that's when