{"action":"created","issue":{"url":"https://api.github.com/repos/libusb/libusb/issues/241","repository_url":"https://api.github.com/repos/libusb/libusb","labels_url":"https://api.github.com/repos/libusb/libusb/issues/241/labels{/name}","comments_url":"https://api.github.com/repos/libusb/libusb/issues/241/comments","events_url":"https://api.github.com/repos/libusb/libusb/issues/241/events","html_url":"https://github.com/libusb/libusb/issues/241","id":195087256,"number":241,"title":"Ideas on Intermittent Pipe error [Errno 32]","user":{"login":"c1728p9","id":2916772,"avatar_url":"https://avatars.githubusercontent.com/u/2916772?v=3","gravatar_id":"","url":"https://api.github.com/users/c1728p9","html_url":"https://github.com/c1728p9","followers_url":"https://api.github.com/users/c1728p9/followers","following_url":"https://api.github.com/users/c1728p9/following{/other_user}","gists_url":"https://api.github.com/users/c1728p9/gists{/gist_id}","starred_url":"https://api.github.com/users/c1728p9/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/c1728p9/subscriptions","organizations_url":"https://api.github.com/users/c1728p9/orgs","repos_url":"https://api.github.com/users/c1728p9/repos","events_url":"https://api.github.com/users/c1728p9/events{/privacy}","received_events_url":"https://api.github.com/users/c1728p9/received_events","type":"User","site_admin":false},"labels":[{"id":336719814,"url":"https://api.github.com/repos/libusb/libusb/labels/linux","name":"linux","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-12-12T21:13:37Z","updated_at":"2016-12-31T02:28:58Z","closed_at":null,"body":"I'm getting an intermittent pipe error when using libusb 1.0.20 on Ubuntu 16.04. I also tried the latest code from master - b14d0a49e8014c0043673160ace2910e5742a1d2 and had this same problem. The code I'm using communicates over interrupt endpoints and as a stress test does this repeatedly to multiple devices. The test I'm using accesses libusb through the python library pyusb.\r\n\r\nI also capture this event on a USB analyzer, and the interrupt endpoints in use are not stalled (the API indicates that libusb_interrupt_transfer returns LIBUSB_ERROR_PIPE if the endpoint is halted). It appears that the transaction is getting canceled, since in the USB logs show an IN transaction is started (log has SSPLIT IN) but is never finished (no CSPLIT OUT).\r\n\r\nAny ideas on how I could narrow this problem down? I set LIBUSB_DEBUG=2 but I don't see anything when the error occurs. To see if pyusb was the problem I ran the same script on Windows 10 using libusb 0.1 (I couldn't get libusb 1.0 to work) and didn't have any problems.  I know python masks off some signals, is it possible this would have an effect on libusb? Also any recommendations on how I could debug this?"},"comment":{"url":"https://api.github.com/repos/libusb/libusb/issues/comments/269844457","html_url":"https://github.com/libusb/libusb/issues/241#issuecomment-269844457","issue_url":"https://api.github.com/repos/libusb/libusb/issues/241","id":269844457,"user":{"login":"mcuee","id":1294740,"avatar_url":"https://avatars.githubusercontent.com/u/1294740?v=3","gravatar_id":"","url":"https://api.github.com/users/mcuee","html_url":"https://github.com/mcuee","followers_url":"https://api.github.com/users/mcuee/followers","following_url":"https://api.github.com/users/mcuee/following{/other_user}","gists_url":"https://api.github.com/users/mcuee/gists{/gist_id}","starred_url":"https://api.github.com/users/mcuee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcuee/subscriptions","organizations_url":"https://api.github.com/users/mcuee/orgs","repos_url":"https://api.github.com/users/mcuee/repos","events_url":"https://api.github.com/users/mcuee/events{/privacy}","received_events_url":"https://api.github.com/users/mcuee/received_events","type":"User","site_admin":false},"created_at":"2016-12-31T02:28:58Z","updated_at":"2016-12-31T02:28:58Z","body":"This is also being discussed in the mailing list -- Alan Stern is suggesting the OP to capture the usbmon trace to further debug the issue. This may not be a libusb issue, could be a kernel issue as well."}}
{"actor":{"display_login":"mcuee"}}