Re: [Proposal] security/vault without devel/yarn

On 10/1/23 18:43, Pavel Korovin wrote:
> On 10/01, Volker Schlecht wrote:
>> Hi Pavel,
>>
>> On 10/1/23 17:11, Pavel Korovin wrote:
>>> I always use Linux VM to pre-build Vault UI since Node stuff can be quirky on
>>> OpenBSD.
>>
>> Yeah... let's fix that, though :-)
>>
>>> The proposed solution didn't work for me with vault-1.15.0:
>>> ~/vault-vendored-1.15.0/ui$ corepack yarn run build
>>> Environment: production
>>> ⠋ BuildingWARNING: Option "nodeWorker" is deprecated since workerpool@5.0.0. Please use "workerType" instead.
>>> WARNING: Option "nodeWorker" is deprecated since workerpool@5.0.0. Please use "workerType" instead.
>>> ⠋ building... [Babel: @ember/test-helpers > applyPatches]libc++abi: libc++abi: terminating with uncaught exception of type std::bad_alloc: std::bad_allocterminating with uncaught exception of type std::bad_alloc: std::bad_alloc
>>
>> To avoid misunderstandings: Was that on the Linux VM (if yes, which
>> flavour of Linux?) or on OpenBSD?
>
> Fails on OpenBSD-current/amd64.
> For UI building/distfile creation I use AlmaLinux 9.2/x86_64,
> node-v16.20.2, yarn-1.22.19
>

I just tried again with a fresh checkout of vault, and I don't get that
error. Any chance you're hitting datasize-max there? It's quite memory
hungry when building on multiple cores... which your VM probably
doesn't.