Github user ozymaxx commented on the issue:
https://github.com/apache/thrift/pull/1496
The AppVeyor builder with the `MSVC2013` configuration generates large
double constants differently as the old `MSVC2010` configuration used to do. So
I will add a condition to not do the

Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1479
Any other php folks out there want to comment or review on the breaking
change here? It looks like the strategy was to change the generator and
provide a flag to allow folks to generate older

Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1261
If you are able to finish this up and do the tutorial code, or if you are
not able to complete this, please let me know.
---

Github user ozymaxx commented on the issue:
https://github.com/apache/thrift/pull/1496
I have just disabled my new tests on `MSVC2013` builders and kicked a
build. Let's see what happens.
If the tests also fail on the `CYGWIN` machine, I will also write out new
tests for the x86

Github user bananer commented on the issue:
https://github.com/apache/thrift/pull/1141
@jeking3 it looks like a simple change now that support for node 4 can be
dropped. However, I'm not sure what the expected behaviour in case of a timeout
should be. Just from looking at the code it

Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1380
THRIFT-3458 is also related, and the approach in THRIFT-3458 would allow us
to add the apache git repo to dub directly so we should move in that direction,
but still try to use dub to build in

Github user bananer commented on the issue:
https://github.com/apache/thrift/pull/1075
@jeking3 This is a well-intended change but I think it is not implemented
correctly and will break error handling for users.
In some places in the compiler the input to `render_recv_throw`

[
https://issues.apache.org/jira/browse/THRIFT-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397019#comment-16397019
]
James E. King, III commented on THRIFT-4504:
I think the approach in

Github user bananer commented on the issue:
https://github.com/apache/thrift/pull/1058
@jeking3 To be honest, I don't know why this is useful/necessary. I think
there is no need for a seqid because the connection between request and
response is handled through callbacks

Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1496
I put the MSVC2013 job back in to make sure we had some backwards
compatibility... glad I did. I wonder if we have 32-bit issues with double in
general in thrift?
---

Github user bananer commented on the issue:
https://github.com/apache/thrift/pull/1506
@jeking3 I think all the problems mentioned in THRIFT-4509 are resolved
now. With the package-lock being included now, there should also be less random
build failures. The node and js parts of

Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1058
In general I want to make sure all clients send a seqid and all servers put
that seqid in the result. Without this we won't be able to have clients that
can have multiple outstanding requests in

Github user allengeorge commented on the issue:
https://github.com/apache/thrift/pull/1269
Yup. Will do. I'm a gonna set myself a target to get it done by end of next
week. I've been lax on this :/
---

Github user romanoid commented on the issue:
https://github.com/apache/thrift/pull/1505
Fix is in, the only failure left is this one, I'm not sure if it is
instability of tests or real problem:
https://travis-ci.org/apache/thrift/jobs/353050154
---

[
https://issues.apache.org/jira/browse/THRIFT-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Shchyrov updated THRIFT-4468:
---
Description:
In Delphi all methods that refer to VCL should do it only from main thread. But