[GitHub] thrift issue #1240: return full error message when exception happens

2017-04-11 Thread DanielYWoo
Github user DanielYWoo commented on the issue: https://github.com/apache/thrift/pull/1240 Yes, we probably keep a patch list for this. Thanks Jeking3. --- 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

[GitHub] thrift issue #1240: return full error message when exception happens

2017-04-10 Thread jeking3
Github user jeking3 commented on the issue: https://github.com/apache/thrift/pull/1240 In a project I work on that uses thrift, the company maintains a set of patches they pull (mostly from master, where defects have been fixed on top of 0.10.0) that they need to ship something that

[GitHub] thrift issue #1240: return full error message when exception happens

2017-04-09 Thread DanielYWoo
Github user DanielYWoo commented on the issue: https://github.com/apache/thrift/pull/1240 Thanks for explanation. In our case, we have a web server layer on top of many layers of backends which communicate in thrift, e,g. > web server -> backend A -> backend B -> backend C.

[GitHub] thrift issue #1240: return full error message when exception happens

2017-04-06 Thread jeking3
Github user jeking3 commented on the issue: https://github.com/apache/thrift/pull/1240 This is related to THRIFT-3607. --- 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