Skip to content

MetaCall Core seems to fail in order to close the application gracefully #1

Open
@viferga

Description

@viferga

I have found this bug while implementing this project, here's the logs:

There are 9 handle(s) keeping the process running

# FSREQWRAP
~/Downloads/metacall-polyglot-repl/index.js:15 - fs.readdir(scriptsPath, (err, files) => {
~/Downloads/metacall-polyglot-repl/index.js:12 - const load = () => new Promise((resolve, reject) => {
~/Downloads/metacall-polyglot-repl/index.js:43 - const functions = await load();
~/Downloads/metacall-polyglot-repl/index.js:52 - })();

# INSPECTORJSBINDING
~/Downloads/metacall-polyglot-repl/scripts/repl.js:8 - const r = repl.start({

# TickObject
(unknown stack trace)

# Immediate
~/Downloads/metacall-polyglot-repl/scripts/repl.js:22 - setImmediate(callback);

# Immediate
~/Downloads/metacall-polyglot-repl/scripts/repl.js:17 - setImmediate(() => this.push(null));

# TickObject
(unknown stack trace)

# TickObject
(unknown stack trace)

# TickObject
(unknown stack trace)

# TickObject
~/Downloads/metacall-polyglot-repl/scripts/repl.js:37 - return r.close();
~/Downloads/metacall-polyglot-repl/index.js:47        - await functions['node_repl_close']();

Once this is completely solved, remove this line:

process.exit(0); // TODO: This is temporal, due to a bug in metacall related to async handles

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions