[
https://issues.apache.org/jira/browse/THRIFT-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370488#comment-14370488
]
Mike Riley commented on THRIFT-3041:
[~jfarrell] Depending on which you apply first,
Our company policy is to follow Microsoft with regard to supported Windows
versions, and we made good experiences with that approach.
That means to deprecate and mentally prepare to drop WinXP in near future. It
does not imply taking any action immediately, but as soon as WinXP
compatibility
[
https://issues.apache.org/jira/browse/THRIFT-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Demaine updated THRIFT-3048:
-
Description:
The NodeJS libraries decode i64 differently between protocols. The
Will Demaine created THRIFT-3048:
Summary: NodeJS decoding of I64 is inconsistent across protocols
Key: THRIFT-3048
URL: https://issues.apache.org/jira/browse/THRIFT-3048
Project: Thrift
Github user helgridly commented on the pull request:
https://github.com/apache/thrift/pull/213#issuecomment-83691723
I'm happy to pick this up if @eevee isn't around or doesn't have the time.
---
If your project is set up for it, you can reply to this email and have your
reply appear
[
https://issues.apache.org/jira/browse/THRIFT-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14369780#comment-14369780
]
Anna Dymek commented on THRIFT-2954:
Hi,
I'm Anna Dymek, last year Undergraduate in
Github user eevee commented on the pull request:
https://github.com/apache/thrift/pull/213#issuecomment-83729220
Feel free, @helgridly, and thanks :) â¥
---
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
Github user helgridly commented on the pull request:
https://github.com/apache/thrift/pull/213#issuecomment-83771333
I did the rebase, ran tests on python3, and fixed up a few issues over (in
my own fork)[https://github.com/broadinstitute/thrift/tree/eevee/python3]
However,
[
https://issues.apache.org/jira/browse/THRIFT-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14370185#comment-14370185
]
ASF GitHub Bot commented on THRIFT-1857:
Github user helgridly commented on the
The Vagrantfile was created initially to be a copy of what jenkins had and
mirrored our system test env. My goal with the Dockerfiles has been to
create just that, a set env that is guaranteed to build and test from. The
Ubuntu Dockerfile is what will be used on jenkins soon for the main system
+1 for Ubuntu 14.04 docker as reference platform
On Mar 19, 2015 9:15 AM, Jake Farrell jfarr...@apache.org wrote:
The Vagrantfile was created initially to be a copy of what jenkins had and
mirrored our system test env. My goal with the Dockerfiles has been to
create just that, a set env that
I think Jens makes a good point +1. We need to clearly communicate this
stuff, this should be front page news on the web site with a plan and
milestones when a consensus develops.
I also think we should deal with Cpp for users (lib/cpp and generator
output) separate from the compiler source
I didn't mention this in my last post, but one of the other troubles with
C++11 is figuring out which subset of C++11, and effectively communicating
that information. Suppose we support gcc 4.7+ and Visual Studio 2012+.
Visual Studio 2012 doesn't support braced initialization. It doesn't
13 matches
Mail list logo
