{"action":"created","issue":{"url":"https://api.github.com/repos/jimhigson/oboe.js/issues/53","labels_url":"https://api.github.com/repos/jimhigson/oboe.js/issues/53/labels{/name}","comments_url":"https://api.github.com/repos/jimhigson/oboe.js/issues/53/comments","events_url":"https://api.github.com/repos/jimhigson/oboe.js/issues/53/events","html_url":"https://github.com/jimhigson/oboe.js/issues/53","id":52887752,"number":53,"title":"using alert() in an Oboe callback seems to mess up parsing?","user":{"login":"balrog-kun","id":387877,"avatar_url":"https://avatars.githubusercontent.com/u/387877?v=3","gravatar_id":"","url":"https://api.github.com/users/balrog-kun","html_url":"https://github.com/balrog-kun","followers_url":"https://api.github.com/users/balrog-kun/followers","following_url":"https://api.github.com/users/balrog-kun/following{/other_user}","gists_url":"https://api.github.com/users/balrog-kun/gists{/gist_id}","starred_url":"https://api.github.com/users/balrog-kun/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/balrog-kun/subscriptions","organizations_url":"https://api.github.com/users/balrog-kun/orgs","repos_url":"https://api.github.com/users/balrog-kun/repos","events_url":"https://api.github.com/users/balrog-kun/events{/privacy}","received_events_url":"https://api.github.com/users/balrog-kun/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2014-12-26T07:31:41Z","updated_at":"2015-01-03T15:42:38Z","closed_at":null,"body":"I'm streaming more than one JSON file simultaneously with Oboe, in Firefox 28.0.  One of the streams contains information about a UI event, so for now I'm trying to pop up an alert() box when that event is seen in the stream.  But adding the alert() produces an exception in oboe:\r\n\"Bad array\\nLn: 1\\nCol: 132\\nChr: [\"\r\n\r\nNeither stream has a [ on column 132, confirmed with firefox's console.\r\n\r\nWhen I add a console.log(c) at the beginning of clarinet.write() in oboe-browser.js, it looks like it's mixing the various streams up, but I could be wrong...\r\n\r\nI'm not sure my interpretation of this problem is right, I'll dig in further is someone says that is impossible.\r\n\r\nFull stack is\r\nemitError@https://rawgithub.com/jimhigson/oboe.js/master/dist/oboe-browser.js:628\r\nwrite@https://rawgithub.com/jimhigson/oboe.js/master/dist/oboe-browser.js:802\r\napplyEach@https://rawgithub.com/jimhigson/oboe.js/master/dist/oboe-browser.js:497\r\nsingleEventPubSub/<.emit@https://rawgithub.com/jimhigson/oboe.js/master/dist/oboe-browser.js:2005\r\nhandleProgress@https://rawgithub.com/jimhigson/oboe.js/master/dist/oboe-browser.js:1219"},"comment":{"url":"https://api.github.com/repos/jimhigson/oboe.js/issues/comments/68598678","html_url":"https://github.com/jimhigson/oboe.js/issues/53#issuecomment-68598678","issue_url":"https://api.github.com/repos/jimhigson/oboe.js/issues/53","id":68598678,"user":{"login":"jimhigson","id":136306,"avatar_url":"https://avatars.githubusercontent.com/u/136306?v=3","gravatar_id":"","url":"https://api.github.com/users/jimhigson","html_url":"https://github.com/jimhigson","followers_url":"https://api.github.com/users/jimhigson/followers","following_url":"https://api.github.com/users/jimhigson/following{/other_user}","gists_url":"https://api.github.com/users/jimhigson/gists{/gist_id}","starred_url":"https://api.github.com/users/jimhigson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimhigson/subscriptions","organizations_url":"https://api.github.com/users/jimhigson/orgs","repos_url":"https://api.github.com/users/jimhigson/repos","events_url":"https://api.github.com/users/jimhigson/events{/privacy}","received_events_url":"https://api.github.com/users/jimhigson/received_events","type":"User","site_admin":false},"created_at":"2015-01-03T15:42:38Z","updated_at":"2015-01-03T15:42:38Z","body":"The alert thing is odd. Alerting is expected to hold up parsing (because it is blocking) but shouldn't actually cause anything to break (well I guess unless the alert is shown for so long that the http times out).\r\n\r\nIt sounds like a low priority bug since nobody should be using alert in production, but weird and possibly worth getting to the bottom of.\r\n\r\nThe multiple streams thing is interesting, and something I've not seen in my own usage with several http resources being fetched simulataneously. @balrog-kun - would it be possible to put together a small page demonstrating this issue? Then I'll be able to see what's going on."}}