Yep, looks like it's broken. Probably something I did regarding the way reports 
are processed now.

Until I can get it fixed, or get a replacement, probably the best way to find 
this information is by using the api.cpantesters.org 
<http://api.cpantesters.org/>: Each report now has the reporter's information 
(name and e-mail address) stored inside. Install the "jq" program[1], and do: 
`curl http://api.cpantesters.org/v3/report/<guid> | jq '.reporter'`. This is, 
effectively, what the Find a Tester tool does. The `jq` program is optional, 
but then it means you have to look for the "reporter" section of the report, to 
find the "email" field.

There are a couple options for future development that would fix this problem:

1. Fix the current Find a Tester.
2. The API needs a way to look up testers, with the goal being for testers to 
be able to see lists of all the reports they've submitted. Testers are 
distinguished by e-mail address, but the API could allow for a search by name 
(but there needs to be protections against misuse and spam).
3. Create a new website. My goal here is still that the new site can be used to 
message testers directly without requiring them to expose their e-mail address 
to everyone.
4. Give access to a group of people to handle support requests like this by 
looking at the database. I wrote Yancy[2] basically for this purpose: Looking 
at the CPAN Testers database from a website and editing things inside. This is 
how I fix tester information now, and how I looked up the e-mails of these two 
testers. Yancy isn't perfect, the CPAN Testers database is huge and the APIs 
Yancy uses aren't fast enough, but it's a start.

[1]: https://stedolan.github.io/jq/ <https://stedolan.github.io/jq/> also 
available in most package managers
[2]: http://metacpan.org/pod/Yancy <http://metacpan.org/pod/Yancy>


Doug Bell
d...@preaction.me



> On Jun 9, 2018, at 5:13 PM, Alceu R. de Freitas Jr. via cpan-testers-discuss 
> <cpan-testers-discuss@perl.org> wrote:
> 
> Hello folks,
> 
> I'm trying to fetch the author for both reports below:
> 
> https://www.cpantesters.org/cpan/report/aa4f5cac-6e3a-1014-a899-817a51db77ab 
> <https://www.cpantesters.org/cpan/report/aa4f5cac-6e3a-1014-a899-817a51db77ab>
> https://www.cpantesters.org/cpan/report/1de885b4-687c-11e8-a021-da16591eefd3 
> <https://www.cpantesters.org/cpan/report/1de885b4-687c-11e8-a021-da16591eefd3>
> 
> At http://stats.cpantesters.org/cgi-bin/cpanmail.cgi 
> <http://stats.cpantesters.org/cgi-bin/cpanmail.cgi> and both are giving the 
> message "Sorry, we were unable to retrieve that ID/GUID."
> 
> I'm using as ID the string right after the last slash (e.g. 
> "1de885b4-687c-11e8-a021-da16591eefd3").
> 
> Thanks,
> 
> Alceu

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to