CAN NOT UPDATE USERINFO IN METACPAN

[snmpd]

is_pause_custodial_account: Reference bless( do{(my $o = 0)}, 'JSON::PP::Boolean' ) did not pass type constraint "Bool"

[oalders]

More context required.

[haarg]

This message appears at the top of the page when attempting to update your profile on MetaCPAN.

[zoffixznet]

Having same issues:

Possibly unrelated steps I took before I encountered the issue:

1. Login to account using GitHub
2. Confirm PAUSE account so that I could edit profile details (worth noting, confirmation link in the email just redirected to metacpan homepage and did nothing to confirm the account; clicking it the second time lead to a page showing an empty JSON object, but this time confirmation worked)
3. Go to https://metacpan.org/account/profile
4. Remove a bunch of sites from "Profiles" section
5. Try to save
6. Get error that ASCII name field is required (it was blank; also this lost all of the attempted changes to Profiles section, so they're back where they were)
7. Enter the ASCII name and save
8. Get confirmation that save has been successful(!)

Now steps directly reproducing the problem:

1. Go to https://metacpan.org/account/profile
2. Click "Save"
3. Error is_pause_custodial_account: Reference bless( do{\(my $o = 0)}, 'JSON::PP::Boolean' ) did not pass type constraint "Bool" is shown

I tried disconnecting and reconnecting PAUSE account but that didn't help the error (though this time, confirmation email link lead to a full JSON object the first try just fine))

[stigtsp]

I'm having the same problem trying to update my MetaCPAN profile.

    is_pause_custodial_account: Reference bless( do{\(my $o = 0)}, 'JSON::PP::Boolean' ) did not pass type constraint "Bool"

[oalders]

I think that error is being returned from the API. https://github.com/metacpan/metacpan-api/blob/master/lib/MetaCPAN/Script/Mapping/CPAN/Author.pm#L50-L52

It looks like that's the only place we use boolean in that mapping. @mickeyn thoughts on this? Do we need to fix the data that's being sent from metacpan-web?

[oalders]

This issue was opened 2 days after this merge: metacpan/metacpan-api#1058

Maybe it's related to an updated dep, like Type::Tiny?

[mickeyn]

I'm a bit lost on all the different Type::Tiny versions and it seems we're using an old one. is there a reason for that?

[oalders]

We can't auto-upgrade the deps on the API because some unknown module breaks the test suite if we just upgrade everything to the latest version. I can put in a PR to upgrade Type::Tiny and we could see if this error just goes away. That might be a good way to start.

Having said that, I see that the CircleCI build is no longer running on automated API pull requests to upgrade deps. I think it's because those are created by the bot user.

[karenetheridge]

We can't auto-upgrade the deps on the API...

What is the breakage? is there a ticket on this for folks to poke at?

[oalders]

What is the breakage? is there a ticket on this for folks to poke at?

I just ran a job since CircleCI hasn't been doing it automatically. It looks like some Pod parsing changed. That's my best guess. It could have been years ago, though, since the deps are very badly out of date.

https://app.circleci.com/pipelines/github/metacpan/metacpan-api/183/workflows/dd0c1872-d397-459d-bb41-5cf122023977/jobs/192

[oalders]

If this isn't fixed in about 90 minutes, we should re-open this ticket.

[oalders]

Re-opening. 😭