nodegui / qodejs Goto Github PK

I just noticed that setTimeout() doesn't fire unless there is activity on the Qt event loop.

This sounds very similar to the problem reported here: nodegui/nodegui#864

Tried to run nodegui-starter and got this error:

error D:\mlp-mpv\nodegui-starter\node_modules\@nodegui\qode: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: D:\mlp-mpv\nodegui-starter\node_modules\@nodegui\qode
Output:
Error while setting up Qode:  Error: Error while downloading Qode v16.4.0:https://github.com/nodegui/qodejs/releases/download/v16.4.0-qode/v16.4.0-qode-win32-ia32.tar.gz. Not Found
    at download (D:\mlp-mpv\nodegui-starter\node_modules\@nodegui\qode\src\downloader.js:33:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async setupQode (D:\mlp-mpv\nodegui-starter\node_modules\@nodegui\qode\src\setup.js:19:3)

npm install fails on debian 11 (bullseye) with

�[K�[?25hnpm ERR! code 1
npm ERR! path /home/darko/GitHub/nodegui-starter/node_modules/@nodegui/qode
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! Error while setting up Qode:  Error: Error while downloading Qode v16.4.0:https://github.com/nodegui/qodejs/releases/download/v16.4.0-qode/v16.4.0-qode-linux-arm64.tar.gz. Not Found
npm ERR!     at download (/home/darko/GitHub/nodegui-starter/node_modules/@nodegui/qode/src/downloader.js:33:11)
npm ERR!     at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR!     at async setupQode (/home/darko/GitHub/nodegui-starter/node_modules/@nodegui/qode/src/setup.js:19:3)
npm ERR!     at async main (/home/darko/GitHub/nodegui-starter/node_modules/@nodegui/qode/install.js:7:5)

Right now, projects packaged using nodegui/packer still run the REPL by default when executed with no target script. This is undesirable behaviour, obviously, and the lack of clarity around that behaviour has spawned many issues on the packer project, so there clearly needs to be some way to override that behaviour in the qode executable for packaged applications. Particularly on Windows, the change to the windowing system causes the executable to run the REPL while having no stdio, causing a non-interactive and essentially dead process that must be manually killed.

One method would be to allow for simply catenating a script onto the executable, which could be the entire application script, or simply a loader for some external resources (loose scripts, ASAR archives, whatever the user wants) and having qode automatically execute this script if present, rather than invoking the REPL.

Another approach would be to try creating qode executables integrating the patches from pkg, potentially allowing leveraging pkg to build executables with packaged scripts and resources on top of the Qodejs binary instead of Nodejs. This would have a huge number of other benefits, such as bytecode execution, asset packing, default flags, and so on. Executables built with these patches cannot be easily used for development, however, so separate builds of qode for development and use in packaging would be needed.

Version

No response

Platform

macOS

Subsystem

No response

What steps will reproduce the bug?

Run this with Qode environment:
require('http').createServer(function (req, res) { res.end('OK'); }).listen(3000);

The http server can accept local connections but not connections from other computer inside the same LAN. If we run with node instead of qode, this http server can accept all connections.

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

HTTP connections from external IPs are not accepted

Additional information

No response

when I use upx , to compress qode.exe, it can't run, the autor of upx say that, if a pe file pack with Cotrol Flow Guard, it can't run. so , please fix it,thanks please!