James Addison dixit:
>AssertionError [ERR_ASSERTION]: The input did not match the regular
> expression /RangeError: Maximum call stack size exceeded/. Input:
>
>'Segmentation fault\n'
You removed the subtraction of V8_STACK_RESERVE when mutilating
my patch; this may be related (if it
James Addison dixit:
>... to add something like this:
Ouch, by going via a string?! I wouldn’t have thought of that…
> if (!(flags & ProcessInitializationFlags::kNoAdjustResourceLimits)) {
>struct rlimit lim;
>if (getrlimit(RLIMIT_STACK, &lim) == 0) {
> char stackSize[32];
32 is m
James Addison dixit:
>I'm going to stay involved with this thread, but I think that it is
>upon you to develop or provide further guidance towards a patch if
>it's something you'd like to have implemented, Thorsten.
I actually have looked into that but I don’t understand the nodejs
and v8 source
James Addison dixit:
>So: a fix here won't achieve stack capacity equality across
No. The fix you proposed won’t achieve that but others would
improve the situation much more, so that equality across arches
won’t need to matter any more.
>Or, to put it another way: applying an increase (either s
James Addison dixit:
>On Thu, 11 May 2023 at 02:43, Andres Salomon wrote:
>> For ARM64, he says that raising the stack limit is not safe for v8
>> *embedded inside WebView*, and therefore not appropriate for upstream
>> v8. But then he says it could/should be safe for v8 *embedded inside
>> Node
James Addison dixit:
>Based on what I've learned about this bug, I believe that architecture-specific
>behaviour related to stack sizes is inherent in the V8 library vendored by
>upstream NodeJS.
Yes, but the v8 library’s defaults are targetting a browser, and one
whose uses are much wider, e.g.
Jérémy Lal dixit:
>I can build nodejs on amhdal.debian.org if you're not comfortable with that.
The problem with the DSA porterboxen is that you cannot install your own
built packages in the chroot to use them there… unless there’s a
solution not yet known to me?
bye,
//mirabilos
--
“ah that re
James Addison dixit:
>Hi - what do you both think of the attached patch, which brings the ARM stack
>size into line with almost all other architectures (= 984 KB)?
It might do the job unless arm64 for some reason uses more stack
elsewhere as well.
Can you test it? I don’t have the bandwidth for
James Addison dixit:
>Maybe it's rare to propose 'do nothing' as a technical suggestion but I think
>it is worth considering here, since we are not the arbiters of Node.
It’s still a release-critical bug in Debian which impacts arm64 builders
including reproducible-builds. I would see this fixed
Hi James,
(you might wish to Cc <${bugnumber}-submit...@bugs.debian.org> so they
actually get the reply…)
>Are you able to determine whether https://github.com/nodejs/node/issues/41163
>(and/or any of the guidance within that thread) seems relevant to this bug?
It appears so. I commented there,
Package: nodejs
Version: 18.13.0+dfsg1-1
Severity: serious
Tags: upstream
Justification: breaks on release architecture
X-Debbugs-Cc: t...@mirbsd.de
Control: affects -1 src:dygraphs
During reproducible-builds testing, I found that one of my packages,
the one with nodejs used during build, worked o
On Thu, 26 Jan 2023, Yadd wrote:
> could you try attached patch ? It keeps related paths where needed.
Tested now (only one build, but should suffice), and yes, it does
the job.
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
--
Pkg-javascript-devel mailing list
Pk
Yadd dixit:
> could you try attached patch ? It keeps related paths where needed.
Not easily/right now, but it looks as if it does the job as well.
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-list
Package: node-browser-pack
Version: 6.1.0+ds+~6.1.1-2
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath toolchain
X-Debbugs-Cc: t...@mirbsd.de
Control: affects -1 src:dygraphs
var preludePath = opts.preludePath ||
path.relative(basedir, defaultPre
Package: chai
Version: 4.2.0+ds+~4.2.14-2
Severity: serious
Justification: Policy 2.3
User: debian...@lists.debian.org
Usertags: adequate broken-symlink missing-copyright-file
X-Debbugs-Cc: t...@mirbsd.de
chai: broken-symlink /usr/share/doc/chai -> libjs-chai
chai: broken-symlink /usr/share/nodejs
Package: node-jquery
Version: 3.5.1+dfsg+~3.5.5-3
Followup-For: Bug #977960
X-Debbugs-Cc: t...@mirbsd.de
Even for the latest versions of these packages, adequate reports:
node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js ->
../../nodejs/jquery/dist/jquery.js
node-jquery: broken
Package: libjs-jquery
Version: 3.5.1+dfsg+~3.5.5-3
Followup-For: Bug #977960
X-Debbugs-Cc: t...@mirbsd.de
Even for the latest versions of these packages, adequate reports:
node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jquery.js ->
../../nodejs/jquery/dist/jquery.js
node-jquery: broke
Package: node-graceful-fs
Version: 4.2.3-1
Severity: normal
adequate reports:
node-graceful-fs: broken-symlink /usr/lib/nodejs/graceful-fs/index.js ->
graceful-fs.js
The cause is obvious:
$ dpkg -L node-graceful-fs | sort
/.
/usr
/usr/lib
/usr/lib/nodejs
/usr/lib/nodejs/graceful-fs
/usr/lib/no
Package: libjs-leaflet-markercluster
Version: 1.4.1~dfsg-5
Severity: important
When removing the libjs-leaflet-markercluster “transitional” package,
apt also clears the new one for removal:
$ sudo apt-get purge libjs-leaflet-markercluster
Reading package lists... Done
Building dependency tree
Re
Package: mocha
Version: 4.1.0+ds3-4
Severity: grave
Justification: renders package unusable
The /usr/bin/mocha command, present in mocha_4.1.0+ds3-3_all.deb, no
longer exists, making the package totally unusable.
-- System Information:
Debian Release: buster/sid
APT prefers buildd-unstable
AP
Package: mocha
Version: 4.1.0+ds1-1
Severity: serious
Justification: Policy 12.5
Adequate reports:
mocha: missing-copyright-file /usr/share/doc/mocha/copyright
And adequate is right, as /usr/share/doc/mocha/ is empty.
-- System Information:
Debian Release: buster/sid
APT prefers unreleased
reopen 826890
thanks
Hello Jérémy,
> + Multi-Arch: same on lib/dev packages (Closes: #826890)
this bugreport is about M-A:foreign on the nodejs binary package
(so I can use arch:all stuff like node-uglify which Depends on
nodejs, with a foreign-architecture nodejs).
M-A:same on lib/dev pack
22 matches
Mail list logo
