Skip Menu |
 

This queue is for tickets about the AnyEvent CPAN distribution.

Report information
The Basics
Id: 106395
Status: rejected
Priority: 0/
Queue: AnyEvent

People
Owner: Nobody in particular
Requestors: jellofan [...] hotmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



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>
Download (untitled) / with headers
text/plain 3.2k
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?
Subject: Re: [rt.cpan.org #106395] incr_text can not be called when the incremental parser already started parsing at AnyEvent/Handle.pm line 1765
Date: Thu, 13 Aug 2015 08:25:10 +0200
To: Jeffrey Johnson via RT <bug-AnyEvent [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
Hi! Please send your bug report to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de> Last updated: 2012-04-22


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.