Re: [PHP-DEV] [VOTE] Random Extension Improvement

[Guilliam Xavier]

On Thursday, July 14, 2022, Go Kudo  wrote:

> 2022年7月13日(水) 1:10 Tim Düsterhus :
>
>> Hi
>>
>> On 7/12/22 18:04, Tim Düsterhus wrote:
>> > I also think that both '$string' and '$binary' are appropriate parameter
>> > names in this case, so particular preference from my side.
>>
>> Sorry for the follow-up, there's two mistakes in that sentence. It
>> should read:
>>
>> I also think that both '$string' and **'$bytes'** are appropriate
>> parameter names in this case, so **no** particular preference from my
>> side.
>>
>> Best regards
>> Tim Düsterhus
>>
>
> Hi
>
> I agree with you. I will change the parameter name from `$string` to
> `$bytes` as I don't see any problem.
>
> I will try to explain the changes more rigorously in future proposals.
> Thank you.
>
> Regards,
> Go Kudo
>

Hi,

I was waiting for more opinions but... so here's mine:

I would prefer to keep "$string", as [that's how I read the RFCs, and] when
calling e.g. shuffleBytes('foobar') I don't feel like I'm passing "bytes"
(or "a binary") but a string (to be shuffled byte-wise rather than
character-wise or codepoint-wise, but that's from the function, not the
argument)...
Granted, not compelling, and probably won't matter in practice, but hey ;)

Regards

PS: sent from mobile


-- 
Guilliam Xavier

Re: [PHP-DEV] Re: [VOTE] Random Extension Improvement

[Go Kudo]

2022年7月13日(水) 1:10 Tim Düsterhus :

> Hi
>
> On 7/12/22 18:04, Tim Düsterhus wrote:
> > I also think that both '$string' and '$binary' are appropriate parameter
> > names in this case, so particular preference from my side.
>
> Sorry for the follow-up, there's two mistakes in that sentence. It
> should read:
>
> I also think that both '$string' and **'$bytes'** are appropriate
> parameter names in this case, so **no** particular preference from my side.
>
> Best regards
> Tim Düsterhus
>

Hi

I agree with you. I will change the parameter name from `$string` to
`$bytes` as I don't see any problem.

I will try to explain the changes more rigorously in future proposals.
Thank you.

Regards,
Go Kudo

Re: [PHP-DEV] Windows PECL build machine died

[Hans Henrik Bergan]

Fwiw Chris Haas / vendiadvertising.com has reached out, they're willing to
sponsor raid(1) if my proposal is accepted.
Haas is reading this mailing list, but does not wish to participate/post
directly at present.
(I have no prior relation, never heard of them before today)

On Tue, 12 Jul 2022 at 22:31, Hans Henrik Bergan 
wrote:

> i have a 40-core 128GB RAM server with 1 (and only 1) static ipv4 address
> that I intend to keep around until at least 27 november 2025 (but unsure
> after that),
> it has more RAM/CPU than i need, and i could set up a virtual machine on
> it and give VNC access to the VM in the form of
> > ssh -L :localhost:3389 user@ip
> then point a RDP/VNC client to localhost:
> i can dedicate individual TCP ports to it, but not any of 22, 80, 443,
> 5900,  5901, 8083, , 587, 2525
> (after which i can recommend Teamviewer for a more comfortable access)
>
> but the server has several caveats:
> - it's un-raided, rolling just a single 1TB SSD, if that SSD was to die,
> everything on it would be lost, and it would probably take days to replace
> the drive.
> - it's located in a somewhat unstable environment, occasional power
> outage, it was out on 30 june, 23 june, 27 january, and in 2021 was down on
> 30 august. (it boots up and recovers automatically, but it has a reboot
> time of roughly 300 seconds until ssh responds again)
> - I can not offer a dedicated IP (but can offer some dedicated ports)
> - May be decommissioned after 27-11-2025
>
> If that sounds like a good idea, I'll want a ssh public key.
>
>
> On Tue, 12 Jul 2022 at 15:38, Christoph M. Becker 
> wrote:
>
>> On 11.07.2022 at 21:04, Hans Henrik Bergan wrote:
>>
>> > Any of you windows.php.net guys familiar with SSH? Can one be created?
>>
>> That would be possible (needed to be set-up by Alex Schoenmaker), but
>> while that could solve the upload issue, it wouldn't solve the other
>> issue I've mentioned, namely that we need to avoid dynamically linking
>> against incompatible versions of dependencies.  And there is yet another
>> issue, namely security.  I think these issues can only be solved by some
>> central place where the packages are build.
>>
>> > On Mon, 11 Jul 2022 at 19:52, Christoph M. Becker 
>> wrote:
>> >
>> >> On 11.07.2022 at 18:53, Hans Henrik Bergan wrote:
>> >>
>> >>> Is there any SSH public key associated with the Windows php
>> developers?
>> >> Or
>> >>> with CMB?
>> >>
>> >> No.  At least not regarding windows.php.net.
>> >>
>> >>> On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker 
>> >> wrote:
>> >>>
>>  On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
>> 
>> > Do you mean it is unlikely that Github Actions will suffice? because
>> >> that
>> > would definitely be a great solution if it was possible/feasible .
>> 
>>  No.  It is only unlikely that automated uploads to window.php.net
>> will
>>  ever be possible using GH actions.
>> 
>> > Anyway, with regards to "I don't think there are special
>> requirements
>> > regarding the hardware", can you give a rough estimate on RAM/disk
>> >> space
>> > requirements?
>> 
>>  The old machine had something like 4 or 8 GB RAM, and a 128 GB hard
>> >> disk.
>> 
>> >>>
>> >>
>> >
>>
>>