You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Lari Hotari <lh...@apache.org> on 2024/03/05 12:31:28 UTC
Staging release artifacts fail when file size exceeds 429MB, ASF Infra ticket created to increase limit by about 100MB
Hi,
For the upcoming 3.1.3 release, we encountered a problem where the staging of release artifacts failed because the size of apache-pulsar-3.1.3-bin.tar.gz is now 455MB. The current limit for SVN file uploads is 429MB. The size of apache-pulsar-3.1.2-bin.tar.gz was 428MB.
The ASF infra ticket can be found at https://issues.apache.org/jira/browse/INFRA-25579 (visible to Apache committers). I have requested an increase in the limit by about 100MB, from 450000000 bytes (429MB) to 550000000 bytes (524MB).
Meanwhile, we will investigate why the size increased from 428MB to 455MB between apache-pulsar-3.1.2-bin.tar.gz and apache-pulsar-3.1.3-bin.tar.gz.
-Lari
Re: Staging release artifacts fail when file size exceeds 429MB, ASF Infra ticket created to increase limit by about 100MB
Posted by Enrico Olivelli <eo...@gmail.com>.
Il Mar 5 Mar 2024, 14:33 Lari Hotari <lh...@apache.org> ha scritto:
> The size had increased from 428MiB to 434MiB. I had mixed the units
> MiB/1048576B and MB/1000000B. We found an explanation to the increase.
> byte-buddy-1.14.12.jar adds 4MiB to the release and the remaining 2MiB
> comes from upgraded jars.
>
Thanks
Enrico
>
> -Lari
>
> On 2024/03/05 12:31:28 Lari Hotari wrote:
> > Hi,
> >
> > For the upcoming 3.1.3 release, we encountered a problem where the
> staging of release artifacts failed because the size of
> apache-pulsar-3.1.3-bin.tar.gz is now 455MB. The current limit for SVN file
> uploads is 429MB. The size of apache-pulsar-3.1.2-bin.tar.gz was 428MB.
> >
> > The ASF infra ticket can be found at
> https://issues.apache.org/jira/browse/INFRA-25579 (visible to Apache
> committers). I have requested an increase in the limit by about 100MB, from
> 450000000 bytes (429MB) to 550000000 bytes (524MB).
> >
> > Meanwhile, we will investigate why the size increased from 428MB to
> 455MB between apache-pulsar-3.1.2-bin.tar.gz and
> apache-pulsar-3.1.3-bin.tar.gz.
> >
> > -Lari
> >
>
Re: Staging release artifacts fail when file size exceeds 429MB, ASF Infra ticket created to increase limit by about 100MB
Posted by Lari Hotari <lh...@apache.org>.
The size had increased from 428MiB to 434MiB. I had mixed the units MiB/1048576B and MB/1000000B. We found an explanation to the increase. byte-buddy-1.14.12.jar adds 4MiB to the release and the remaining 2MiB comes from upgraded jars.
-Lari
On 2024/03/05 12:31:28 Lari Hotari wrote:
> Hi,
>
> For the upcoming 3.1.3 release, we encountered a problem where the staging of release artifacts failed because the size of apache-pulsar-3.1.3-bin.tar.gz is now 455MB. The current limit for SVN file uploads is 429MB. The size of apache-pulsar-3.1.2-bin.tar.gz was 428MB.
>
> The ASF infra ticket can be found at https://issues.apache.org/jira/browse/INFRA-25579 (visible to Apache committers). I have requested an increase in the limit by about 100MB, from 450000000 bytes (429MB) to 550000000 bytes (524MB).
>
> Meanwhile, we will investigate why the size increased from 428MB to 455MB between apache-pulsar-3.1.2-bin.tar.gz and apache-pulsar-3.1.3-bin.tar.gz.
>
> -Lari
>