[jira] [Closed] (THRIFT-3200) JS and nodejs do not encode JSON protocol binary fields as base64

[ https://issues.apache.org/jira/browse/THRIFT-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Sukegawa closed THRIFT-3200. Resolution: Fixed > JS and nodejs do not encode JSON protocol binary fields as base64 >

[jira] [Commented] (THRIFT-3200) JS and nodejs do not encode JSON protocol binary fields as base64

[ https://issues.apache.org/jira/browse/THRIFT-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006821#comment-15006821 ] Aki Sukegawa commented on THRIFT-3200: -- Thanks :) Closing, then. > JS and nodejs do not encode JSON

Re: Flooded with issues

Great tips ! It was indeed hidden... On Sun, Nov 15, 2015 at 6:33 PM Jens Geyer wrote: > When I finally close a bunch of issues I now usually do this using the > bulk change option (hidden in the tools menu on top of a list of issues) > and uncheck "send email" in the

[jira] [Commented] (THRIFT-3388) hash doesn't work on set/list

[ https://issues.apache.org/jira/browse/THRIFT-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007397#comment-15007397 ] Tejal Desai commented on THRIFT-3388: - Thank you all for chiming in! I was about to propose a patch

[jira] [Created] (THRIFT-3428) Go test fails when running make check

Roger Meier created THRIFT-3428: --- Summary: Go test fails when running make check Key: THRIFT-3428 URL: https://issues.apache.org/jira/browse/THRIFT-3428 Project: Thrift Issue Type: Bug

[jira] [Commented] (THRIFT-3428) Go test fails when running make check

[ https://issues.apache.org/jira/browse/THRIFT-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007306#comment-15007306 ] Jake Farrell commented on THRIFT-3428: -- I am not aware of any issues with these tests, i've been

RE: Flooded with issues

I'm not entirely clear -- this sounds like people doing things that generate emails could limit the flood. What I was hoping for is some setting at my end that would avoid ever receiving most issue-related emails. Yes, I can write a local filter rule but that's less than ideal... Regards