Skip Menu |
 
Update: The rt.cpan.org bug tracker service is no longer shutting down.

This queue is for tickets about the JSON-XS CPAN distribution.

Report information
The Basics
Id: 122378
Status: open
Priority: 0/
Queue: JSON-XS

People
Owner: MLEHMANN [...] cpan.org
Requestors: RSHADOW [...] cpan.org
Cc:
AdminCc:

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



Subject: Please add support for JSON5
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
Message-ID: <rt-4.0.18-23179-1499357424-1664.0-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 113
Download (untitled) / with headers
text/plain 113b
Please add support for JSON5 extension: http://json5.org/ Maybe you can simple add support in ->relaxed method?
MIME-Version: 1.0
X-Spam-Status: No, score=-5.857 tagged_above=-99.9 required=10 tests=[AWL=0.042, BAYES_00=-1.9, FROM_OUR_RT=-4, SPF_FAIL=0.001] autolearn=ham
In-Reply-To: <rt-4.0.18-23179-1499357424-379.122378-4-0 [...] rt.cpan.org>
Content-Disposition: inline
X-Cpan.org: This message routed through the cpan.org mail forwarding service. Please use PAUSE pause.perl.org to configure your delivery settings.
X-Spam-Flag: NO
X-RT-Interface: API
References: <RT-Ticket-122378 [...] rt.cpan.org> <rt-4.0.18-23179-1499357424-379.122378-4-0 [...] rt.cpan.org>
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
Message-ID: <20170706165555.7s6w4oggxxhgybgq [...] schmorp.de>
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
X-Spam-Score: -5.857
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id D66002403C3 for <cpan-bug+JSON-XS [...] hipster.bestpractical.com>; Thu, 6 Jul 2017 13:11:51 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAEGHsww3mpQ for <cpan-bug+JSON-XS [...] hipster.bestpractical.com>; Thu, 6 Jul 2017 13:11:49 -0400 (EDT)
Received: from xx1.develooper.com (xx1.develooper.com [207.171.7.115]) by hipster.bestpractical.com (Postfix) with ESMTPS id ACB87240228 for <bug-JSON-XS [...] rt.cpan.org>; Thu, 6 Jul 2017 13:11:49 -0400 (EDT)
Received: from localhost (xx1.develooper.com [127.0.0.1]) by localhost (Postfix) with ESMTP id 5F4F4120311 for <bug-JSON-XS [...] rt.cpan.org>; Thu, 6 Jul 2017 10:11:48 -0700 (PDT)
Received: from xx1.develooper.com (xx1.develooper.com [127.0.0.1]) by localhost (Postfix) with SMTP id 4CA9D1203B0 for <bug-JSON-XS [...] rt.cpan.org>; Thu, 6 Jul 2017 10:11:46 -0700 (PDT)
Received: from mail.nethype.de (mail.nethype.de [5.9.56.24]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by xx1.develooper.com (Postfix) with ESMTPS id 1613F120311 for <bug-JSON-XS [...] rt.cpan.org>; Thu, 6 Jul 2017 10:11:38 -0700 (PDT)
Received: from [10.0.0.5] (helo=doom.schmorp.de) by mail.nethype.de with esmtp (Exim 4.89) (envelope-from <schmorp [...] schmorp.de>) id 1dTA4K-0004sK-9b for bug-JSON-XS [...] rt.cpan.org; Thu, 06 Jul 2017 16:55:56 +0000
Received: from [10.0.0.1] (helo=cerebro.laendle) by doom.schmorp.de with esmtp (Exim 4.89) (envelope-from <schmorp [...] schmorp.de>) id 1dTA4K-0000Zx-5J for bug-JSON-XS [...] rt.cpan.org; Thu, 06 Jul 2017 16:55:56 +0000
Received: from root by cerebro.laendle with local (Exim 4.89) (envelope-from <root [...] schmorp.de>) id 1dTA4K-00016j-3z for bug-JSON-XS [...] rt.cpan.org; Thu, 06 Jul 2017 18:55:56 +0200
Delivered-To: cpan-bug+JSON-XS [...] hipster.bestpractical.com
Subject: Re: [rt.cpan.org #122378] Please add support for JSON5
Return-Path: <schmorp [...] schmorp.de>
X-Original-To: cpan-bug+JSON-XS [...] hipster.bestpractical.com
X-RT-Mail-Extension: json-xs
Openpgp: id=904ad2f81fb16978e7536f726dea2ba30bc39eb6; url=http://pgp.schmorp.de/schmorp-pgpkey.txt; preference=signencrypt
Date: Thu, 6 Jul 2017 18:55:56 +0200
X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_3000_3999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, IN_REP_TO 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, NO_URI_HTTPS 0, REFERENCES 0, SPF_PASS 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CANPHARM_UNSUB 0, __CD 0, __CT 0, __CT_TEXT_PLAIN 0, __FRAUD_BADTHINGS 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __NO_HTML_TAG_RAW 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0, __URI_NO_WWW 0, __URI_NS , __zen.spamhaus.org_ERROR '
X-Spam-Level:
X-Greylist: delayed 942 seconds by postgrey-1.34 at xx1.develooper.com; Thu, 06 Jul 2017 10:11:40 PDT
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2017.7.6.170616
To: Nikolaev Roman via RT <bug-JSON-XS [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
RT-Message-ID: <rt-4.0.18-13220-1499361112-1701.122378-0-0 [...] rt.cpan.org>
Content-Length: 3083
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.