date:20170511

[jira] [Commented] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

2017-05-11 Thread James E. King, III (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007638#comment-16007638
 ] 

James E. King, III commented on THRIFT-4188:


Yep, I see it; but I cannot participate right now.  If anyone else with Go 
experience could look at this in the meantime..

> Error while flushing write buffer of size 70 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe
> 
>
> Key: THRIFT-4188
> URL: https://issues.apache.org/jira/browse/THRIFT-4188
> Project: Thrift
>  Issue Type: Bug
>  Components: Go - Library
>Affects Versions: 0.10.0
>Reporter: brian.kang
> Attachments: client.go, handler.go, main.go, main.go, server.go, 
> shared.thrift, tutorial.thrift
>
>
> if *server {
>   if err := runServer(transportFactory, protocolFactory, *addr, 
> *secure); err != nil {
>   fmt.Println("error running server:", err)
>   }
>   } else {
>   done := make(chan int32)
>   for i := 0; i < 5000; i++ {
>   go func(i int) {
>   err, s := runClient(transportFactory, 
> protocolFactory, *addr, *secure, int32(i))
>   if err != nil {
>   fmt.Println("error running client:", 
> err)
>   }
>   done <- s
>   }(i)
>   }
>   for i := 0; i < 5000; i++ {
>   fmt.Println(<-done)
>   }
>   }
> too many errors,eg:
> Error while flushing write buffer of size 17 to transport, only wrote 
> 02017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
>  bytes: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58922: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58928: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken 
> pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> Error while flushing write buffer of size 172017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken 
> pipe
>  to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58918: 
> write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe



--
This message was sent by

[jira] [Comment Edited] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

2017-05-11 Thread brian.kang (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007560#comment-16007560
 ] 

brian.kang edited comment on THRIFT-4188 at 5/12/17 2:58 AM:
-

[~jking]


was (Author: brian.kang):
@James E. King, III

> Error while flushing write buffer of size 70 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe
> 
>
> Key: THRIFT-4188
> URL: https://issues.apache.org/jira/browse/THRIFT-4188
> Project: Thrift
>  Issue Type: Bug
>  Components: Go - Library
>Affects Versions: 0.10.0
>Reporter: brian.kang
> Attachments: client.go, handler.go, main.go, main.go, server.go, 
> shared.thrift, tutorial.thrift
>
>
> if *server {
>   if err := runServer(transportFactory, protocolFactory, *addr, 
> *secure); err != nil {
>   fmt.Println("error running server:", err)
>   }
>   } else {
>   done := make(chan int32)
>   for i := 0; i < 5000; i++ {
>   go func(i int) {
>   err, s := runClient(transportFactory, 
> protocolFactory, *addr, *secure, int32(i))
>   if err != nil {
>   fmt.Println("error running client:", 
> err)
>   }
>   done <- s
>   }(i)
>   }
>   for i := 0; i < 5000; i++ {
>   fmt.Println(<-done)
>   }
>   }
> too many errors,eg:
> Error while flushing write buffer of size 17 to transport, only wrote 
> 02017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
>  bytes: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58922: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58928: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken 
> pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> Error while flushing write buffer of size 172017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken 
> pipe
>  to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58918: 
> write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

2017-05-11 Thread brian.kang (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007560#comment-16007560
 ] 

brian.kang edited comment on THRIFT-4188 at 5/12/17 2:58 AM:
-

@ [~jking]


was (Author: brian.kang):
[~jking]

> Error while flushing write buffer of size 70 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe
> 
>
> Key: THRIFT-4188
> URL: https://issues.apache.org/jira/browse/THRIFT-4188
> Project: Thrift
>  Issue Type: Bug
>  Components: Go - Library
>Affects Versions: 0.10.0
>Reporter: brian.kang
> Attachments: client.go, handler.go, main.go, main.go, server.go, 
> shared.thrift, tutorial.thrift
>
>
> if *server {
>   if err := runServer(transportFactory, protocolFactory, *addr, 
> *secure); err != nil {
>   fmt.Println("error running server:", err)
>   }
>   } else {
>   done := make(chan int32)
>   for i := 0; i < 5000; i++ {
>   go func(i int) {
>   err, s := runClient(transportFactory, 
> protocolFactory, *addr, *secure, int32(i))
>   if err != nil {
>   fmt.Println("error running client:", 
> err)
>   }
>   done <- s
>   }(i)
>   }
>   for i := 0; i < 5000; i++ {
>   fmt.Println(<-done)
>   }
>   }
> too many errors,eg:
> Error while flushing write buffer of size 17 to transport, only wrote 
> 02017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
>  bytes: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58922: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58928: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken 
> pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> Error while flushing write buffer of size 172017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken 
> pipe
>  to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58918: 
> write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

2017-05-11 Thread brian.kang (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007560#comment-16007560
 ] 

brian.kang commented on THRIFT-4188:


@James E. King, III

> Error while flushing write buffer of size 70 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe
> 
>
> Key: THRIFT-4188
> URL: https://issues.apache.org/jira/browse/THRIFT-4188
> Project: Thrift
>  Issue Type: Bug
>  Components: Go - Library
>Affects Versions: 0.10.0
>Reporter: brian.kang
> Attachments: client.go, handler.go, main.go, main.go, server.go, 
> shared.thrift, tutorial.thrift
>
>
> if *server {
>   if err := runServer(transportFactory, protocolFactory, *addr, 
> *secure); err != nil {
>   fmt.Println("error running server:", err)
>   }
>   } else {
>   done := make(chan int32)
>   for i := 0; i < 5000; i++ {
>   go func(i int) {
>   err, s := runClient(transportFactory, 
> protocolFactory, *addr, *secure, int32(i))
>   if err != nil {
>   fmt.Println("error running client:", 
> err)
>   }
>   done <- s
>   }(i)
>   }
>   for i := 0; i < 5000; i++ {
>   fmt.Println(<-done)
>   }
>   }
> too many errors,eg:
> Error while flushing write buffer of size 17 to transport, only wrote 
> 02017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
>  bytes: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58922: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58928: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken 
> pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken 
> pipe
> 17 to transport, only wrote 0 bytes: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> Error while flushing write buffer of size 172017/05/04 13:29:00 error 
> processing request: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken 
> pipe
>  to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58918: 
> write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 
> 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (THRIFT-4196) Cannot generate recursive Rust types

2017-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007559#comment-16007559
 ] 

ASF GitHub Bot commented on THRIFT-4196:


GitHub user allengeorge opened a pull request:

https://github.com/apache/thrift/pull/1267

THRIFT-4196 Support recursive types in Rust

Client: rs

* Modify code generator to support recursive types
* Modify rust test (not cross-test) client to test recursive calls

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/allengeorge/thrift allen/thrift-4196-final

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/thrift/pull/1267.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1267


commit a3e38261108430585f0e5d72f59b093e1ceffbf6
Author: Allen George 
Date:   2017-05-11T11:56:15Z

THRIFT-4196 Support recursive types in Rust
Client: rs

* Modify code generator to support recursive types
* Modify rust test (not cross-test) client to test recursive calls




> Cannot generate recursive Rust types
> 
>
> Key: THRIFT-4196
> URL: https://issues.apache.org/jira/browse/THRIFT-4196
> Project: Thrift
>  Issue Type: Bug
>  Components: Rust - Compiler
>Reporter: Allen George
>Assignee: Allen George
>
> Pretty simple: I attempted to generate code for a recursive type described in 
> test/recursive.thrift and the rust code generator promptly failed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] thrift pull request #1267: THRIFT-4196 Support recursive types in Rust

2017-05-11 Thread allengeorge

GitHub user allengeorge opened a pull request:

https://github.com/apache/thrift/pull/1267

THRIFT-4196 Support recursive types in Rust

Client: rs

* Modify code generator to support recursive types
* Modify rust test (not cross-test) client to test recursive calls

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/allengeorge/thrift allen/thrift-4196-final

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/thrift/pull/1267.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1267


commit a3e38261108430585f0e5d72f59b093e1ceffbf6
Author: Allen George 
Date:   2017-05-11T11:56:15Z

THRIFT-4196 Support recursive types in Rust
Client: rs

* Modify code generator to support recursive types
* Modify rust test (not cross-test) client to test recursive calls




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (THRIFT-4197) Implement transparent gzip compression for HTTP transport

2017-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/THRIFT-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006548#comment-16006548
 ] 

ASF GitHub Bot commented on THRIFT-4197:


Github user dcelasun commented on the issue:

https://github.com/apache/thrift/pull/1266
  
Travis failure is unrelated, seems like a Haskell problem:

```
Build log ( /root/.cabal/logs/HUnit-1.6.0.0.log ):
cabal: /root/.cabal/logs/HUnit-1.6.0.0.log: does not exist
lib/hs/CMakeFiles/haskell_library.dir/build.make:88: recipe for target 
'lib/hs/thrift_cabal.stamp' failed
make[2]: *** [lib/hs/thrift_cabal.stamp] Error 1
CMakeFiles/Makefile2:3926: recipe for target 
'lib/hs/CMakeFiles/haskell_library.dir/all' failed
make[1]: *** [lib/hs/CMakeFiles/haskell_library.dir/all] Error 2
```


> Implement transparent gzip compression for HTTP transport
> -
>
> Key: THRIFT-4197
> URL: https://issues.apache.org/jira/browse/THRIFT-4197
> Project: Thrift
>  Issue Type: Improvement
>  Components: Go - Library
>Affects Versions: 0.10.0
>Reporter: Can Celasun
>Assignee: Can Celasun
>Priority: Minor
>
> HTTP transport should check if the client supports gzip compressed responses 
> and do transparent compression if it does.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] thrift issue #1266: THRIFT-4197 [Go] Transparent gzip support for HTTP trans...

2017-05-11 Thread dcelasun

Github user dcelasun commented on the issue:

https://github.com/apache/thrift/pull/1266
  
Travis failure is unrelated, seems like a Haskell problem:

```
Build log ( /root/.cabal/logs/HUnit-1.6.0.0.log ):
cabal: /root/.cabal/logs/HUnit-1.6.0.0.log: does not exist
lib/hs/CMakeFiles/haskell_library.dir/build.make:88: recipe for target 
'lib/hs/thrift_cabal.stamp' failed
make[2]: *** [lib/hs/thrift_cabal.stamp] Error 1
CMakeFiles/Makefile2:3926: recipe for target 
'lib/hs/CMakeFiles/haskell_library.dir/all' failed
make[1]: *** [lib/hs/CMakeFiles/haskell_library.dir/all] Error 2
```


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] thrift pull request #1266: THRIFT-4197 [Go] Transparent gzip support for HTT...

2017-05-11 Thread dcelasun

GitHub user dcelasun opened a pull request:

https://github.com/apache/thrift/pull/1266

THRIFT-4197 [Go] Transparent gzip support for HTTP transport

Check if the client supports gzip compressed responses and compress the 
response if it does.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dcelasun/thrift go-gzip-support

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/thrift/pull/1266.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1266


commit b148a865bc2c2ade26dcffc0a7b18c85dc332464
Author: D. Can Celasun 
Date:   2017-05-11T10:04:01Z

[Go] Transparent gzip support for HTTP transport

Check if the client supports gzip compressed responses and compress
the response if it does.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (THRIFT-4197) Implement transparent gzip compression for HTTP transport

2017-05-11 Thread Can Celasun (JIRA)

Can Celasun created THRIFT-4197:
---

 Summary: Implement transparent gzip compression for HTTP transport
 Key: THRIFT-4197
 URL: https://issues.apache.org/jira/browse/THRIFT-4197
 Project: Thrift
  Issue Type: Improvement
  Components: Go - Library
Affects Versions: 0.10.0
Reporter: Can Celasun
Assignee: Can Celasun
Priority: Minor


HTTP transport should check if the client supports gzip compressed responses 
and do transparent compression if it does.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

[jira] [Comment Edited] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

[jira] [Comment Edited] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

[jira] [Commented] (THRIFT-4188) Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe

[jira] [Commented] (THRIFT-4196) Cannot generate recursive Rust types

[GitHub] thrift pull request #1267: THRIFT-4196 Support recursive types in Rust

[jira] [Commented] (THRIFT-4197) Implement transparent gzip compression for HTTP transport

[GitHub] thrift issue #1266: THRIFT-4197 [Go] Transparent gzip support for HTTP trans...

[GitHub] thrift pull request #1266: THRIFT-4197 [Go] Transparent gzip support for HTT...

[jira] [Created] (THRIFT-4197) Implement transparent gzip compression for HTTP transport

10 matches

Site Navigation

Mail list logo

Footer information