Subject: | incr_text can not be called when the incremental parser already started parsing at AnyEvent/Handle.pm line 1765 |
Date: | Wed, 12 Aug 2015 14:23:17 -0700 |
To: | "bug-AnyEvent [...] rt.cpan.org" <bug-anyevent [...] rt.cpan.org>, "bug-Gerrit-Client [...] rt.cpan.org" <bug-gerrit-client [...] rt.cpan.org> |
From: | Jeffrey Johnson <jellofan [...] hotmail.com> |
Using perl 5, version 14, subversion 2 (v5.14.2) built
for x86_64-linux-gnu-thread-multi
With AnyEvent VERSION: 7.11 and Gerrit::Client VERSION:
20140611
I am using AnyEvent with Gerrit::Client as follows:
+++
use AnyEvent;
use Gerrit::Client 'stream_events';
my $gerrit_server = '<omitted>';
my $stream = stream_events(
url =>
$gerrit_server,
on_event =>
sub {
my ($event) =
@_;
print
"$event->{type}\n";
print Dumper
\$event;
}
);
AE::cv()->recv(); # must run an event loop for
callbacks to be activated
---
This runs ok until a JSON record is received which
contains encoded unicode. Then the
script croaks with the subject line:
incr_text can not be called when the incremental parser
already started parsing at AnyEvent/Handle.pm line 1765
A redacted version of one such record is:
{"type":"comment-added","change":{"project":"project","branch":"master","topic":"","id":"I7419be663e3ec0bb858a39649c014e543b206ed1","number":"1360922","subject":"subject","owner":{"name":"Owner
Name","email":"owner@example.com","username":"owner"},"url":"https://review.example.com/1360922","createdOn":1438730037,"lastUpdated":1439345877},"patchSet":{"number":"3","revision":"b6406aa9426e8bfc35c1dda87ffeac12e97b5e5b","parents":["525af07f78bd0780b577088820a6127788307ac2"],"ref":"refs/changes/22/1360922/3","uploader":{"name":"Owner
Name","email":"owner@example.com","username":"owner"},"createdOn":1439236752,"author":{"name":"Owner
Name","email":"owner@example.com","username":"owner"},"sizeInsertions":9,"sizeDeletions":-1},"author":{"name":"Daemon","email":"daemon@localhost","username":"daemon"},"comment":"Patch
Set 3:\n\nThis change is being verified by daemon for the following manifests
along with other changes as detailed below:\n\n\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n\n\n--------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n
note that verification of all changes in this batch need to be successful before
this change can be merged.\n\nPLEASE DO NOT UPLOAD A NEW PATCH SET, OR REMOVE
APPROVALS UNTIL THE VERIFICATION IS COMPLETE."}
Any thoughts on how to address this issue?