[image: image.png]
I just download and the fild can not open
何品

kerr <hepin1...@gmail.com> 于2024年1月26日周五 20:17写道:

> I was updated and replaced the dll on Windows, IIRC.
> 何品
>
>
> PJ Fanning <fannin...@apache.org> 于2024年1月26日周五 20:01写道:
>
>> I'm going to have to cancel this and look at doing an RC2.
>>
>> We had issues in the last pekko-http release with the linked dir used in
>> testing. Seemed to only affect Windows users then but now, it's affecting
>> Mac users.
>>
>> x
>> apache-pekko-http-1.0.1-RC1-incubating-src-20240126/http-tests/src/test/resources/dirWithLink/linked-dir:
>> Truncated tar archive
>> tar: Error exit delayed from previous errors.
>>
>> So, we'll have to look into seeing if we can fix this.
>>
>>
>> On 2024/01/26 04:00:50 kerr wrote:
>> > +1 for me
>> > This release is for the HTTP/2 reset protection and @PJ Fanning
>> > <fannin...@yahoo.com> implemented it in a performanted way.
>> >
>> > 何品
>> >
>> >
>> > PJ Fanning <fannin...@apache.org> 于2024年1月26日周五 04:50写道:
>> >
>> > > Hello Pekko Community,
>> > >
>> > > This is a call for a vote to release Apache Pekko(incubating)
>> > > HTTP version 1.0.1-RC1.
>> > >
>> > > The discussion thread:
>> > >
>> > > https://lists.apache.org/thread/c8vrl4cfgjzrfckxxbc1rt60cxocfy66
>> > >
>> > > The release candidate:
>> > >
>> > >
>> https://dist.apache.org/repos/dist/dev/incubator/pekko/HTTP-1.0.1-RC1/
>> > >
>> > > This release has been signed with a PGP key, available here:
>> > >
>> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
>> > >
>> > > Release Notes:
>> > >
>> > > https://github.com/apache/incubator-pekko-http/pull/442/files
>> > >
>> > > Git branch for the release:
>> > >
>> > > https://github.com/apache/incubator-pekko-http/tree/v1.0.1-RC1
>> > > Git commit ID: 00ebae1e13b6af65e732062d48ba7313dd317df9
>> > >
>> > > Please download, verify, and test.
>> > >
>> > > We have also staged jars in the Apache Nexus Repository. These were
>> > > built with the same code
>> > > as appears in this Source Release Candidate. We would appreciate if
>> > > users could test with these too.
>> > > If anyone finds any serious problems with these jars, please also
>> > > notify us on this thread.
>> > >
>> > >
>> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>> > >
>> > > In sbt, you can add this resolver.
>> > >
>> > > resolvers += "Apache Pekko Staging" at
>> > > "https://repository.apache.org/content/groups/staging";
>> > >
>> > >
>> > > The VOTE will pass if we have more positive votes than negative votes
>> > > and there must be a minimum of 3 approvals from Pekko PPMC members.
>> > > Anyone voting in favour of the release, could you please provide a
>> > > list of the checks you have done?
>> > > The vote will be left open for at least 72 hours.
>> > >
>> > > [ ] +1 approve
>> > > [ ] +0 no opinion
>> > > [ ] -1 disapprove with the reason
>> > >
>> > > To learn more about Apache Pekko, please see
>> https://pekko.apache.org/
>> > >
>> > > Checklist for reference:
>> > >
>> > > [ ] Download links are valid.
>> > > [ ] Checksums and signatures.
>> > > [ ] LICENSE/NOTICE files exist
>> > > [ ] No unexpected binary files
>> > > [ ] Source files have ASF headers
>> > > [ ] Can compile from source
>> > >
>> > > To compile from the source, please refer to:
>> > >
>> > >
>> > >
>> https://github.com/apache/incubator-pekko-http/blob/main/README.md#building-from-source
>> > >
>> > > Some notes about verifying downloads can be found at:
>> > >
>> > > https://pekko.apache.org/download.html#verifying-downloads
>> > >
>> > >
>> > > Here is my +1.
>> > >
>> > > Thanks,
>> > > PJ Fanning (Apache Pekko PPMC member)
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
>> > > For additional commands, e-mail: dev-h...@pekko.apache.org
>> > >
>> > >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
>> For additional commands, e-mail: dev-h...@pekko.apache.org
>>
>>

Reply via email to