Issue running node

[dusano]

This issue has been converted to a project Issue running node

---

When running hello-world-react example I get the following output:

═════════════════════════ Conformance Tests Script Output ═════════════════════════ Input parameters: build_folder_name: /Users/dusano/Dev/plainlang-examples/hello-world/react/plain_modules/typescript-react-app-boilerplate/code conformance_tests_folder: /Users/dusano/Dev/plainlang-examples/hello-world/react/plain_modules/typescript-react-app-boilerplate/tests/app_entry_point verbose_flag:

Step 1: Starting the React application in folder /tmp/node_code...

node[9668]: void node::PlatformInit(ProcessInitializationFlags::Flags) at ../src/node.cc:661

Assertion failed: (err) == (0)

----- Native stack trace -----

1: 0x100261538 node::Assert(node::AssertionInfo const&) [/usr/local/bin/node] 2: 0x10201b69c node::InitializeOncePerProcessInternal(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>>> const&, node::ProcessInitializationFlags::Flags) (.cold.2) [/usr/local/bin/node] 3: 0x10021bc84 node::InitializeOncePerProcessInternal(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>>> const&, node::ProcessInitializationFlags::Flags) [/usr/local/bin/node] 4: 0x10021c880 node::Start(int, char**) [/usr/local/bin/node] 5: 0x1883944e4 start [/usr/lib/dyld] Error: Installing Node modules.

══════════════════════════════════════════════════════════════════════
Conformance Tests script /Users/dusano/Dev/plainlang-examples/scripts/run_conformance_tests_cypress.sh failed with exit code 2.
Conformance Tests script execution time: 0.42 seconds.

The issue happens because we execute scripts with start_new_session parameter of subprocess.Popen set to true. You can replicate this using the following script:

runs.py

Please note that I couldn't reproduce the issue if I run python plain2code.py hello-world-react.plain. Only if I run this with codeplain client the issue pops up.

[dusano]

@pedjaradenkovic one solution to this issue is to replace

start_new_session parameter

with

process_group=0

This would still allow us to kill the whole subprocess group but wouldn't isolate the environment where the script is executed so cleanly.

[pedjaradenkovic]

Investigate why session was slightly different than the in original terminal environment where the renderer was run.