Re: PAUSE 504 errors when trying to add a co-maintainer

[email protected] (Laura Chevalier via modules)
Newsgroups perl.modules
Message-ID <CA+EcEXkbR2gqs-CsE2FewEC7BKOagsCXfUA68Y6TLjPKKWBZiQ@mail.gmail.com>
Hey Neil,

Happy almost Friday! Thanks for the continued follow-ups.

I wasn't able to follow your suggested steps since I get the 504 before I
can reach the "Add comaintainers" page, *but* I think I reached the same
page by clicking "Change Permissions per module" in the left nav. So I
think that should work if I need to add another comaintainer in the future.

I'm a little surprised that the size is still a problem. It looks like the
distributions are only ~1.2MB each, and after the previous versions were
deleted we only have 7 distinct versions on PAUSE. Plus, we're no longer
indexing
<https://github.com/googleads/google-ads-perl/blob/05a263401e4119271cf0fcbc5427b5b051184bd2/Build.PL#L46>
the largest directories after you helped us identify that this was causing
indexing errors. Could there be another issue here or am I missing
something?

Many thanks,
Laura

On Tue, Mar 24, 2026 at 6:38 AM Neil Bowers <[email protected]> wrote:

> Hi Laura,
>
> I think the issue is the number of modules, and some action is timing out.
>
> I discovered a way around this:
>
>    - First click on "Add comaintainers" in the side bar on PAUSE
>    - In the blurb at the top, you'll see there's a link to "Add
>    Comaintainers per module"
>    - If you go there, you get a list of all your modules, and you can
>    tick them individually and then give someone, such as Dora, co-maint.
>    - This is a lot more tedious than just selecting a distribution name
>    and letting PAUSE work out the associated modules, but it doesn't seem to
>    have the timeout problem.
>
> Could you split the old modules off into a different distribution, and
> direct people to that if they want to use an older version of the interface?
>
> You've managed to push PAUSE further than anyone else ever has, so you
> should feel proud. Maybe. :-)
>
> Cheers,
> Neil
>
> On 11 Mar 2026 at 14:50 +0000, Laura Chevalier via modules <
> [email protected]>, wrote:
>
> Hey Neil,
>
> I've tried accessing the "Add Comaintainers" page again now that old
> releases have been deleted, but I'm still running into 504s. Since I may
> eventually need to add another comaintainer who isn't Dora, I'd like to
> proactively figure this out. Is it possible there are still too many
> modules? Or might there be another cause for the error?
>
> Many thanks,
> Laura
>
> On Mon, Mar 9, 2026 at 12:12 PM Laura Chevalier <[email protected]>
> wrote:
>
>> Thanks so much for jumping in to share your expertise and add the missing
>> permissions while I was away, Neil! We really appreciate it.
>>
>> On Thu, Feb 26, 2026 at 11:14 AM Dora Sun <[email protected]> wrote:
>>
>>> Thanks for all your help, Neil!
>>>
>>>
>>>
>>> Dora Sun
>>> Developer Relations Engineer
>>>
>>>
>>> On Thu, Feb 26, 2026 at 11:06 AM Neil Bowers <[email protected]> wrote:
>>>
>>>> Hi Dora,
>>>>
>>>>
>>>> Thanks for the follow up, Neil! I'm pretty new to CPAN; is there a good
>>>> way to identify and update modules that haven't been updated in the Index?
>>>>
>>>>
>>>> When you log into PAUSE, in the left sidebar you'll see "Force
>>>> Reindexing". Click on that, and you'll get a list of the files in your
>>>> author directory:
>>>>
>>>>    - Click on the checkbox next to the .tar.gz file for your most
>>>>    recent release
>>>>    - Scroll to the bottom and hit "Reindex"
>>>>    - That would put it in the queue for reindexing
>>>>    - It can take up to an hour for the reindexing to happen, after
>>>>    which you'll get the usual email from PAUSE.
>>>>
>>>>
>>>> Cheers,
>>>> Neil
>>>>
>>>>
>>>>
>>
>> --
>> Laura Chevalier
>> Developer Relations Engineer | Google Ads API
>>
>>
>
> --
> Laura Chevalier
> Developer Relations Engineer | Google Ads API
>
>

-- 
Laura Chevalier
Developer Relations Engineer | Google Ads API
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.