primordic/IssueDupesLite huggingface dataset:
Repository: nodeSolidServer/node-solid-server

Issue #454: HEAD doesn't set right Content-Type  or right Content-Length headers
Created: 2016-10-26T23:17:46Z
for example GET request to foo.png includes correct header
Content-Type: image/png
but HEAD request to foo.png responds with incorrect header
Content-Type: text/plain; charset=utf-8

Duplicate issue #789: Content-type on HEAD is text/plain, text/turtle on GET
Created: 2018-09-23T20:44:40Z
Why is https://rubentest.solidtest.space/profile/card suddenly text/plain?

Closing comment (2018-09-24T19:00:39Z): Duplicate of #454 indeed; straightforward #662 wouldn't fix it indeed. Closing in favor of #454.
Repository: nodeSolidServer/node-solid-server

Issue #275: Persist Content-Type of resources without file extensions
Created: 2016-03-07T16:40:22Z
(Creating a tracking issue for PRs #159 and #229)
Problem: When writing a resource without a file extension, there is currently no way for the server to remember what its content-type was. So, when it's next requested, the server doesn't know what that resource's content type is, and returns text/turtle by default.
Potential Solutions:

Add the content type to the resource's .meta file. Have the server check the .meta (if the resource doesn't have a file extension), discover the content type, and return it with the response.
(Route taken by PR #229) Append a transparent file extension to the resource, only when the resource does not include a file extension. For example, if you PUT a resource named article with an HTML content type, the file will be named article.$.html on disk. When reading the resource, ldnode detects the special extension (and filters it out), and returns the resource with the correct content-type.

Duplicate issue #445: Possibly add file extension when adding a POST
Created: 2016-09-24T15:55:28Z
Raised by @timbl
From gitter chat here:
https://gitter.im/linkedresearch/chat?at=57e64fd8240a335f12e881d8

It should have been stored as 33560d70-81da-11e6-8400-5f305f4cc319$.jsonld then
or else of course you could make things easier in he meantime and send a name which ends in .jsonld
until the srever is fixed to add the extension
Oh hang on that was generated by a POST with no slug?
In that case maybe another issue with server - if generating a new id in a POST then add the right extension
I have to go to the airport - could someone add an issue to the server about adding a file extension when something created and the server makes up a random URI?

Closing comment (2016-12-13T16:49:51Z): Closing as duplicate of #275: Persist Content-Type of resources without file extensions
Repository: nodeSolidServer/node-solid-server

Issue #1751: Exclude swap files (.swp) from containment statements
Created: 2024-01-16T23:19:20Z
https://fileinfo.com/extension/swp
.swp file is created when a text editor like nano or vim opens a file in a directory. When the editor is closed, the swap file is removed.
While swap files exist in a directory, NSS includes them in containment statements.
My attempts to GET the .swp file resulted in a 404, but this could still be a potential risk. At the very least, it does expose information when it really shouldn't.
I suggest excluding .swp from containment statements.

Duplicate issue #1485: .lock files show up in directory listings
Created: 2020-10-05T19:27:25Z
This bug is hard to reproduce timing-wise, but I have received at least one directory listing containing a .lock file.
For reference, this is what it looked like:
@prefix : <#>.
@prefix inbox: <>.
@prefix ldp: <http://www.w3.org/ns/ldp#>.
@prefix terms: <http://purl.org/dc/terms/>.
@prefix XML: <http://www.w3.org/2001/XMLSchema#>.
@prefix dcd: <dcd04010-0722-11eb-aaa1-f5587892eb36.ttl.lock/>.
@prefix st: <http://www.w3.org/ns/posix/stat#>.
@prefix tur: <http://www.w3.org/ns/iana/media-types/text/turtle#>.

inbox:
    a ldp:BasicContainer, ldp:Container;
    terms:modified "2020-10-05T19:22:19Z"^^XML:dateTime;
    ldp:contains
        <378f8150-0728-11eb-aaa1-f5587892eb36.ttl>,
        <4870d3e0-073f-11eb-aaa1-f5587892eb36.ttl>,
        <92f0e640-073e-11eb-aaa1-f5587892eb36.ttl>,
        <abf84aa0-0731-11eb-aaa1-f5587892eb36.ttl>,
        <dcd04010-0722-11eb-aaa1-f5587892eb36.ttl>, dcd:;
    st:mtime 1601925739.707;
    st:size 4096.
<378f8150-0728-11eb-aaa1-f5587892eb36.ttl>
    a tur:Resource, ldp:Resource;
    terms:modified "2020-10-05T16:31:27Z"^^XML:dateTime;
    st:mtime 1601915487.715;
    st:size 531.
<4870d3e0-073f-11eb-aaa1-f5587892eb36.ttl>
    a tur:Resource, ldp:Resource;
    terms:modified "2020-10-05T19:16:34Z"^^XML:dateTime;
    st:mtime 1601925394.459;
    st:size 552.
<92f0e640-073e-11eb-aaa1-f5587892eb36.ttl>
    a tur:Resource, ldp:Resource;
    terms:modified "2020-10-05T19:11:29Z"^^XML:dateTime;
    st:mtime 1601925089.955;
    st:size 552.
<abf84aa0-0731-11eb-aaa1-f5587892eb36.ttl>
    a tur:Resource, ldp:Resource;
    terms:modified "2020-10-05T17:39:08Z"^^XML:dateTime;
    st:mtime 1601919548.486;
    st:size 531.
<dcd04010-0722-11eb-aaa1-f5587892eb36.ttl>
    a tur:Resource, ldp:Resource;
    terms:modified "2020-10-05T15:53:07Z"^^XML:dateTime;
    st:mtime 1601913187.983;
    st:size 531.
dcd:
    a ldp:BasicContainer, ldp:Container, ldp:Resource;
    terms:modified "2020-10-05T19:22:19Z"^^XML:dateTime;
    st:mtime 1601925739.711;
    st:size 4096.
Note how it ends with .lock/ as opposed to just .lock, which might be the reason why it is not caught.
Should be fixed when not using on-disk locking anymore (#1475), but wanted to mention this in case there would be issues with other magic extensions.

Closing comment (2024-10-12T17:12:46Z): Related to #1751
Repository: nodeSolidServer/node-solid-server

Issue #741: Only trust apps from a single origin
Created: 2018-08-07T21:09:45Z
There are CORS issues with current Solid apps: resources read from one origin cannot be read from another (despite Vary: Origin).
While we could fix these issues (for instance, by disabling caching), the question rises whether we should actually allow apps from random domains to access our pods.
Therefore, as a temporary solution for v5.0.0, @timbl proposes a single trusted domain on which apps run.
This domain should be configurable, and perhaps multiple can be allowed on a given server.
For v6.0.0, we should come up with a more flexible security model.

Duplicate issue #738: Add an Origin we control as trusted
Created: 2018-08-06T23:51:22Z
@timbl said:

Concluded to keep a long story short that 5.0.0 should run with every data browser running not in the  some origin as the data, but in a single trusted origin we control. Change the server so that it only gives the CORS origin-echo response for a specfic domain like apps.solid.org

Closing comment (2018-08-08T12:07:33Z): Duplicate of #741.
Repository: nodeSolidServer/node-solid-server

Issue #410: Accept-Patch HTTP header
Created: 2016-07-01T16:03:39Z
Accept-Patch is missing in action for HTTP OPTIONS

Duplicate issue #1561: accept-PATCH header
Created: 2021-01-29T20:45:51Z
linkeddata/rdflib.js#473

Closing comment (2021-11-09T21:38:14Z): I'm not sure I understand this issue. Isn't Accept-Patch currently supported? Is this issue a duplicate of #410 ?
Repository: nodeSolidServer/node-solid-server

Issue #1021: solid init does not store serverUri
Created: 2018-12-11T20:39:53Z
As reported in #1019 (comment)

Duplicate issue #1081: config.json issues [v5.0.0-beta.6]
Created: 2019-01-31T18:42:13Z
I have encountered some issues with config.json

solid init doesn't save serverUri to config.json
setting "multiuser": true & "webid": false results in

  solid:get / on idp.hackers4peace.net +3s
  solid:get GET -- Error: 404 Can't find file requested: [object Object] +2ms


setting "multiuser": false and  "webid": false results in

  solid:get / on idp.hackers4peace.net +7ms
  solid:get    sending data browser file: /usr/lib/node_modules/solid-server/static/databrowser.html +31ms


setting "multiuser": false and "webid": true and "auth": "oidc" finally leads to expected


I plan to use this deployment only as OIDC Issuer for external WebIDs, it will never act as Resource Server. Another deployment on different domain will act as Resource Server which will also include WebID Profile, but will not act as OIDC Issuer. Currently both don't require "multiuser": true, but later I might enable it.
I miss combination of configuration options to clearly define:

only act as OIDC Issuer, no Resource Server
only act as Resource Server, no OIDC Issuer

I would also like to disable WebID-TLS on those both servers, only using WebID-OIDC.
Related to #672

Closing comment (2019-02-01T09:03:48Z): #1 is also reported in #1021.
I think we should prioritize these bugs.
Repository: nodeSolidServer/node-solid-server

Issue #1243: delete account links to the wrong place
Created: 2019-06-27T13:18:37Z
cc @megoth
this is on the home page of a newly created pod. It links to the delete path on that subdomain, instead of to the delete path on the server root

Duplicate issue #1250: 'Delete Account' goes to wrong URL
Created: 2019-06-27T13:31:47Z
When attempting to delete an existing Pod by clicking the 'Delete Account' button on the 'Solid Home' page, I am redirected to a URL https://WebID.PodProvider/account/delete and am shown a page:
No permission to access this resource
You are currently logged in as https://WebID.PodProvider/profile/card#me, but do not have permission to access https://WebID.PodProvider/account/delete/.
The URL should be https://PodProvider/account/delete/. For example, https://inrupt.net/account/delete.
To Replicate

Log into a Solid Pod.
Display the 'Solid Home' page.
Click the 'Delete Account' button.

Expected Behaviour

Redirected to https://PodProvider/account/delete/ to allow Account name to be entered.

Actual Behaviour

Redirected to https://WebID.PodProvider/profile/card#me and No permission to access this resource error displayed.

Closing comment (2019-07-02T15:31:28Z): Duplicate of #1243
Repository: nodeSolidServer/node-solid-server

Issue #688: Existing dashboards are not regenerated after dashboard improvements
Created: 2018-05-29T15:34:49Z
After improvements to the dashboard existing users will still have the existing index.html.  And therefore, will not see the improvements leading to a possible inconsistent user experience.
One possible solution would be to have a link or script to regenerate templates from the original.  Im sure there are other possible strategies.
Related issues : #683 , #683

Duplicate issue #853: Implement simple system for updating user's index.html (and other resources that live inside a user's POD)
Created: 2018-10-10T10:36:17Z
Today the index.html-file and similar resources that live in users PODs do not have a way of being updated by the POD providers. I think we need a simple system to allow for this so that user's can opt-in by default whenever there are updates. (As for the update that brings this functionality itself I think we have to force an update; this needs to be communicated to the community.) A result of not having this system in place prevents us from exposing the link to /delete/account that has been implemented in #177.
I don't quite know how to solve this, but my idea is the following:

Upon the forced update, all index.html get a version id
Include a script that checks this version with an API that returns whether or not there is an update
2a) If no update, then do nothing (End of actions)
If there is an update available, notify the user of this and give them options:
3a) To do an update, see 4
3b) To skip that specific update; this will add the version id of the updated to somewhere (cookie, localStorage, maybe as data somewhere in the user's POD) that tells the checkForUpdate-script to ignore this version in the future (End of actions)
Calls an API that does the update of the index.html and other resources, and lastly refreshes the page (End of actions)

We could add to this more information on what the update entails (maybe have a link returned from the API) that allows people more insight. It could also list which files will be affected, but I think that's maybe version 2 of this script.

Closing comment (2018-11-06T19:04:14Z): This is related to #688.
Repository: nodejs/help

Issue #3026: Worker thread post message performance
Created: 2020-10-14T21:20:43Z
Node.js Version: v12.18.4
OS: Ubuntu 18.04 LTS
Scope (install, code, runtime, meta, other?): code/runtime
Module (and version) (if relevant): worker_threads

I am using perf_hooks to help track down some issues that I have with the event loop getting blocked. I am measuring the overhead of posting a message to a worker thread and noticed that sometimes it can take upwards of 100+ms to post a message to a thread. I am curious where this latency is coming from as it seems that posting a message should be more or less constant time and very lightweight:
            const message = 'marco'
            const start = performance.now();
            myWorker.postMessage(message);
            const end = performance.now();
            console.log(`worker_thread:postMessage ${end - start} ms`);
I also tried to find the underlying code for the postMessage but was unable to locate any specific code. If someone could point me to that code as well that would be great.

Duplicate issue #3025: MessageChannel constructor performance
Created: 2020-10-14T21:14:54Z
Node.js Version: v12.18.4
OS: Ubuntu 18.04 LTS
Scope (install, code, runtime, meta, other?): code/runtime
Module (and version) (if relevant): worker_threads

I am using perf_hooks to help track down some issues that I have with the event loop getting blocked. I am measuring the creation of MessageChannel objects and noticed that sometimes it can take upwards of 20ms to create a MessageChannel object. I am curious where this latency is coming from as it seems that the creation of a MessageChannel object should be more or less constant time and very lightweight:
            const start = performance.now();
            channel = new MessageChannel();
            const end = performance.now();
            console.log(`MessageChannel:constructor ${end - start} ms`);
I also tried to find the underlying code for the MessageChannel constructor but was unable to locate any specific code. If someone could point me to that code as well that would be great.

Closing comment (2021-01-07T09:18:37Z): duplicate of #3026
Repository: nodejs/help

Issue #796: Need a help for Button work real time 
Created: 2017-08-28T19:21:05Z
i want to do this website real time open web page and start local then see 6 buttons i want  this 6 button work real time but  when i use socket io and command server node localhost display nothing only so i need help please see my code and help me.. code is clean. my code here attach
csgo.zip

Duplicate issue #797: Real time full webpage 
Created: 2017-08-28T19:58:35Z
http://mapvote.16mb.com/
How to do this site real time.. but why?

Closing comment (2017-09-05T16:34:01Z): I assume this is a duplicate of #796, closing.
Repository: nodejs/help

Issue #2853: nodemon is not getting installed.
Created: 2020-07-17T08:37:21Z
Node.js Version: v12.8.2
OS: Windows 8.1 pro
Scope (install, code, runtime, meta, other?):
Module (and version) (if relevant):

Duplicate issue #2857: nodemon is not getting installed
Created: 2020-07-17T16:48:59Z

Closing comment (2020-07-20T08:10:08Z): Closing as a duplicate of #2853.
Repository: nodejs/help

Issue #2266: prefix -g is not recognized as internal or external command
Created: 2019-11-01T10:40:35Z
'CALL "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" prefix -g' is not recognized as an internal or external command,
operable program or batch file.

Duplicate issue #2642: NPM not recognized as an internal or external command
Created: 2020-04-20T18:14:58Z
I’ve installed latest version of NodeJS and I'm trying to install Angular CLI , but...
When i try to use NPM commands i always get this message:
'CALL “C:\Program Files\nodejs\node_modules \npm\bin\npm-cli.js” prefix -g' is not recognized as an internal or external command
and then command is executed.Here's an image

and when I try to instal Angular cli with "npm install -g @angular/cli" this happens:

and Angular's not working

PS: here's my Environment Variables
USER:

SYSTEM:

I don't know what could be a problem. Please help me...
Thank you.

Closing comment (2020-04-24T00:29:35Z): OP's 1st image:

1st command: no problem.
2nd command: duplicate of #2266.


OP's 2nd image:

1st command: no problem.
2nd command: duplicate of #2266.
3rd command: duplicate of #2266.



/cc @addaleax as we now have a command associated w/ error message seen in  #2266
Repository: nodejs/help

Issue #3502: doc: NODE_EXTRA_CA_CERTS Override
Created: 2021-08-13T22:45:50Z
Hello
I need a little help to set a self signed certificate in Nodejs. I have been doing research on this for many days and found a working solution in one of the GitHub issues of nodejs 
This is how I am setting global options
    const CA_STORE = await getCertificate()
    https.globalAgent.options.ca = [];

    https.globalAgent.options.ca.push(CA_STORE)

The solution really set the self signed certificate into node.js process but the problem is it overrides the default trusted certificates of Nodejs and my other Axios call that are using public certificates stop working.
I cannot use NODE_EXTRA_CA_CERTS because I cannot set its value runtime (I am reading the certificate from s3)

Duplicate issue #3501: How to set self signed certificate in Nodejs process
Created: 2021-08-13T22:40:09Z
Hello
I need a little help to set a self signed certificate in Nodejs. I have been doing research on this for many days and found a working solution in one of the GitHub issues of nodejs 
This is how I am setting global options
    const CA_STORE = await getCertificate()
    https.globalAgent.options.ca = [];

    https.globalAgent.options.ca.push(CA_STORE)

The solution really set the self signed certificate into node.js process but the problem is it overrides the default trusted certificates of Nodejs and my other Axios call that are using public certificates stop working.
I cannot use NODE_EXTRA_CA_CERTS because I cannot set its value runtime (I am reading the certificate from s3)

Closing comment (2021-08-30T13:11:18Z): Closing as duplicate of #3502.
Repository: nodejs/help

Issue #2243: “node-v12.12.0 (1).pkg” can’t be opened because Apple cannot check it for malicious software.
Created: 2019-10-21T14:34:24Z
Node.js Version: 12.12.0
OS: iOS 10.15
Scope (install, code, runtime, meta, other?):
Module (and version) (if relevant):

“node-v12.12.0 (1).pkg” can’t be opened because Apple cannot check it for malicious software.
Apple won't let me install the latest version of Node on my iMac and has told me:
"This software needs to be updated. Contact the developer for more information."
Any chance of a later version or any workaround advice? - cheers!

Duplicate issue #2469: Can't install Node for MacOS
Created: 2020-02-14T00:20:03Z
12.16.0
macOS Catalina 10.15.3:
Install:

I am not able to install node from the node package downloaded from the website

Closing comment (2020-09-30T10:53:55Z): @evan-k-wright - is this still outstanding ?
for me with your issue ,looks similar to #2243 hopefully this may help you to resolve the issue.
Repository: nodejs/help

Issue #430: nodejs, expressjs, mongodb and angularjs
Created: 2017-01-04T17:10:18Z
I want to use these tools in my company and i would like to know if they are free licensed and which limits of warrants to use in my company and if i can use with free or how much it costs.
i refer to use these tools in software to be sold.
thanks, joana

Duplicate issue #433: licenses of expressjs, mongodb, angularjs and nodejs
Created: 2017-01-05T10:45:40Z
I continue with the same problem... if i can use these tools in my company????
Thanks a lot.... joana

Closing comment (2017-01-06T10:02:33Z): Closing, duplicate of #430.
Repository: nodejs/help

Issue #1618: Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\node_modules\npm\bin\npm-cli.js'
Created: 2018-11-11T09:43:23Z
I just reinstalled node and I have been having issues with npm...
C:\Users\Mubarak>node -v
v10.13.0
C:\Users\Mubarak>npm -v
internal/modules/cjs/loader.js:582
throw err;
^
Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\node_modules\npm\bin\npm-cli.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
at Function.Module._load (internal/modules/cjs/loader.js:506:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
at startup (internal/bootstrap/node.js:285:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
internal/modules/cjs/loader.js:582
throw err;
^
Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\node_modules\npm\bin\npm-cli.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
at Function.Module._load (internal/modules/cjs/loader.js:506:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
at startup (internal/bootstrap/node.js:285:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)

Duplicate issue #3153: Administrator mode error
Created: 2020-12-31T07:13:02Z
12.13.1:
Windows:

What steps will reproduce the bug?
Whenever I run a node program with administrator privileges, it throws this error
internal/modules/cjs/loader.js:800
    throw err;
    ^

Error: Cannot find module 'C:\Windows\system32'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
    at Function.Module._load (internal/modules/cjs/loader.js:690:27)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
    at internal/main/run_main_module.js:17:11 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

How often does it reproduce? Is there a required condition?
Every time I run a program in administrator mode, it throws that error.
What is the expected behavior?
I don't even know why that error, its most probably because the working directory should be set to C:/Windows/System32 instead of C:/Windows/system32 (probably case sensitive).

What do you see instead?

Additional information

Closing comment (2020-12-31T07:35:48Z): @m-Phoenix852 - well looks like your install path may be corrupted. what does where node and where npm gives? its a duplicate of #1618 . I hope you can refer this.

where node gives me
C:\Program Files\nodejs\node.exe

and where npm gives me
C:\Program Files\nodejs\npm
C:\Program Files\nodejs\npm.cmd
Repository: nodejs/help

Issue #2942: Getting problem in installing Node.js
Created: 2020-08-27T10:22:00Z
Iam unable to install Node.js on my machine getting issue as could not access network location *:. Even though iam deleting all the old node files from system. Please help me to resolve this problem.

Duplicate issue #2956: Node.js Installation Issue
Created: 2020-09-04T05:32:57Z
Hi team,
Iam unable to install node.js on system. While installing iam facing an issue which i attached below

Thank You!

Closing comment (2020-10-13T15:25:00Z): no response , closing this issue as it is same as #2942
Repository: nodejs/node-addon-api

Issue #509: Update node_api modules at src/ with threadsafe functionality
Created: 2019-07-11T11:11:03Z
Hi to everyone!
I have tried to compile with the last update with the ThreadSafeFunction class but it seems that the node_api modules at the src/ folder are not updated with the threadsafe functionality.
I think that is needed to update these files for using the new functionality.

Duplicate issue #641: /src/node_api.h lack function declaration of napi threadsafe_function
Created: 2019-12-26T01:46:02Z
node_api.h not has napi threadsafe_function
(https://nodejs.org/dist/latest-v12.x/docs/api/n-api.html#n_api_napi_create_threadsafe_function)
napi_create_threadsafe_function
napi_get_threadsafe_function_context
napi_call_threadsafe_function
napi_acquire_threadsafe_function
napi_release_threadsafe_function
napi_ref_threadsafe_function
napi_unref_threadsafe_function

It cause my IDE always  show error when I use those function.

Closing comment (2020-01-01T05:18:28Z): Actually, a duplicate of #509.
Repository: nodejs/node-addon-api

Issue #99: Not building on node 8.2.1
Created: 2017-08-02T07:36:23Z
In file included from /Users/matteo/Repositories/native-hdr-histogram/node_modules/node-addon-api/napi.h:1447:
/Users/matteo/Repositories/native-hdr-histogram/node_modules/node-addon-api/napi-inl.h:1461:20: error: no matching function for call to 'napi_create_type_error'
          status = napi_create_type_error(env, nullptr, message, &error);
                   ^~~~~~~~~~~~~~~~~~~~~~

I think this is due to a semver-major change happening in core for the new error codes. In case such events happen again, this module should be released to NPM after the change lands in a release.

Duplicate issue #100: napi_throw_type_error  arguments is different with Node 8 N-API
Created: 2017-08-04T04:04:48Z
node 8 api doc
napi_throw_type_error
Added in: v8.0.0
NODE_EXTERN napi_status napi_throw_type_error(napi_env env, const char* msg);
[in] env: The environment that the API is invoked under.
[in] msg: C string representing the text to be associated with the error.
Returns napi_ok if the API succeeded.

This API throws a JavaScript TypeError with the text provided.

Closing comment (2017-08-04T04:11:53Z): Currently this package works against the latest node nightly builds, and will work with the node 8.3.0 release that is expected soon.
N-API is still experimental, so there are occasional breaking changes. It should stabilize very soon though.
Duplicate of #99
Repository: nodejs/node-addon-api

Issue #312: Support for Asynchronous Thread-safe Function Calls
Created: 2018-07-30T21:17:13Z
Hello, Thank you for the effort to create and maintain the C++ wrappers for N-API. The wrappers make it very much easier to create native addons.
N-API added capability for additional threads to invoke JavaScript functions based on the processing completed by those threads. Is there any timeline/plan to add wrappers for the same?
https://nodejs.org/docs/latest-v10.x/api/n-api.html#n_api_asynchronous_thread_safe_function_calls
Thank you

Duplicate issue #364: napi_threadsafe_function
Created: 2018-10-04T18:38:34Z
Now that we've added support for NAPI_EXPERIMENTAL we should add wrappers for napi_threadsafe_function.

Closing comment (2018-10-08T15:12:11Z): This is a duplicate of #312.
Repository: nodejs/node-addon-api

Issue #16: Symbol class missing
Created: 2017-04-06T22:34:26Z
Are we using String class for both string and symbol use cases?

Duplicate issue #23: Symbol class
Created: 2017-04-14T18:44:25Z
There should be a Napi::Symbol class, implemented with napi_create_symbol(). And probably also a Napi::Name class that is a common base class for Symbol and String, because there are several APIs that can accept either a string or symbol.

Closing comment (2017-04-14T18:46:20Z): Oops closing as duplicate of #16
Repository: nodejs/node-v0.x-archive

Issue #685: BUG: fs.rename gives incorrect error message on error
Created: 2011-02-17T17:03:00Z
Try this:
mkdir -p ./path/that/exists/
touch ./path/that/exists/file

test.js
(function () {
  "use strict";

  var fs = require("fs");

  fs.rename("path/that/exists/file", "path/that/doesntexist/file", function (err) {
    console.log(err);
  });
}());

node test.js
{ message: 'ENOENT, No such file or directory \'path/that/exists/file\''
, stack: [Getter/Setter]
, errno: 2
, path: 'path/that/exists/file'
}

expected:
{ message: 'ENOENT, No such file or directory \'path/that/doesntexists/file\''
, stack: [Getter/Setter]
, errno: 2
, path: 'path/that/exists/file'
}

AJ ONeal

Duplicate issue #7657: fs.rename returns deceptive error when target path is problematic
Created: 2014-05-20T16:43:37Z
when i try to rename a file and its source path is accurate, but target directory doesn't exist, I get simply ENOENT, rename and it quotes the source path. This made me think for a long time that my source path was problematic when the problem all along was that the target dir doesn't exist and there is no indication in the error of that.

Closing comment (2014-05-31T03:16:35Z): This is a dupe of #685 , right?
Repository: nodejs/node-v0.x-archive

Issue #5618: ENOTCONN error after installing node-v0.10.9-x64.msi
Created: 2013-06-02T07:05:25Z
My issue is documented here: http://stackoverflow.com/questions/16879027/why-am-i-getting-errors-running-the-coffee-command-in-cygwin
After installing node-v0.10.9-x64.msi, when I run node it says:
$ node

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: read ENOTCONN
    at errnoException (net.js:884:11)
    at Socket._read (net.js:389:21)
    at Socket.Readable.read (_stream_readable.js:320:10)
    at Socket.read (net.js:291:43)
    at new Socket (net.js:185:10)
    at process.stdin (node.js:660:19)
    at startup (node.js:145:16)
    at node.js:901:3

I don't know anything about node.js so I apologize if I'm not giving enough information.

Duplicate issue #5779: debugger doesn't work in Cygwin
Created: 2013-07-02T16:19:28Z
From Cygwin prompt:
/cygdrive/d/workspace/vts.server/node/lnk2req
$ node debug lnk2req.js -t
debug> There was an internal error in Node's debugger. Please report this bug.
From Windows prompt:
D:\workspace\vts.server\node\lnk2req>node debug lnk2req.js -t
< debugger listening on port 5858
connecting... ok
break in D:\workspace\vts.server\node\lnk2req\lnk2req.js:20
18  */
19
20 var fs = require('fs');
21 var vm = require('vm');
22
debug>

Closing comment (2013-07-03T02:31:33Z): I'm closing this as it's almost certainly a duplicate of #5618. Cygwin does something to the console that breaks node.js.
Repository: nodejs/node-v0.x-archive

Issue #2124: No install target
Created: 2011-11-15T23:46:17Z
I could be doing something really stupid... but there appears to be no install target in the Makefile.

Duplicate issue #2283: `make install` is not implemented yet. Bug bnoordhuis about it in #node.js
Created: 2011-12-07T07:37:27Z
I tried to install nowjs on my ubuntu 11.04... For the first 5 instructions there 's no problem, but till the 6th I failed to execute "sudo make install"
$ sudo apt-get update
$ sudo apt-get install git-core curl build-essential openssl libssl-dev
$ git clone https://github.com/joyent/node.git && cd node
$ ./configure
$ make
ilmagnificia23@ubuntu:~/node$ sudo make install
make install is not implemented yet. Bug bnoordhuis about it in #node.js
Did I miss something on the instalation? Need help really... and Desperately... --a

Closing comment (2011-12-07T13:28:53Z): @ilmagnificia23: @whitman just explained that to you, you can check out specific versions with e.g. git checkout v0.6.5. Closing, dup of #2124.
Repository: nodejs/node-v0.x-archive

Issue #1202: http.get() raises uncatchable EBADNAME exception
Created: 2011-06-18T22:54:23Z
Test case:
var http = require('http');
var host = '********';

host += host;
host += host;
host += host;
host += host;
host += host;

try {
  // raises uncatchable EBADNAME
  http.get({host:host, port:80}, console.error);
}
catch (e) {
  console.error('Caught exception', e);
}

As a gist: https://gist.github.com/1033563

Duplicate issue #1271: http client request emit 'error' event before 'error' listener attached
Created: 2011-07-05T02:23:02Z
start the http server when network is on
turn off the network, visit http://127.0.0.1:8000/
cannot find event listeners, throw error

var http = require('http');
http.createServer(function(req, res){
  var options = {
    host: 'www.google.com',
    method: 'GET',
    path: '/',
    port: 80
  };
  var client_req = http.request(options, function(client_res){
    res.writeHead(client_res.statusCode, client_res.headers);
    client_res.pipe(res);
  }).on('error', function(e){
    res.writeHead(500);
    res.end(e.message);
  });
  req.pipe(client_req);
}).listen(8000);

Closing comment (2011-07-05T03:39:56Z): I think this is the same as #1202 and #1164.
Repository: nodejs/node-v0.x-archive

Issue #615: port v8 to cygwin for v0.4
Created: 2011-02-01T19:06:44Z

Duplicate issue #616: port v8 to cygwin for v0.4
Created: 2011-02-01T19:06:45Z

Closing comment (2011-03-16T22:21:53Z): Isn't this a dup? #615
Repository: nodejs/node-v0.x-archive

Issue #540: RunInThisContext is not aware of getters and setters
Created: 2010-12-31T02:01:01Z
in node 0.3.1 source at
node::Script::EvalMachine template
./src/node_script.cc:217
./src/node_script.cc:270
example of getter setters aware code:
var mixin = function(target) {
var i = 1, length = arguments.length, source;
for ( ; i < length; i++ ) {
// Only deal with defined values
if ( (source = arguments[i]) !== undefined ) {
Object.getOwnPropertyNames(source).forEach(function(k){
var d = Object.getOwnPropertyDescriptor(source, k) || {value:source[k]};
if (d.get) {
target.defineGetter(k, d.get);
if (d.set) target.defineSetter(k, d.set);
}
else if (target !== d.value) {
target[k] = d.value;
}
});
}
}
return target;
};

Duplicate issue #724: vm.runInNewContext incompatible with getters/setters
Created: 2011-02-24T07:28:30Z
There are some weird issues with getters/setters in context objects. Basically, node will try to set all properties in the context, including getters/setter to undefined. The issue is it treats the getters/setters like regular properties.
var ctx = { get poo() {} };
vm.runInNewContext("", ctx);

TypeError: Cannot set property poo of [object Object] which has only a getter
at Object.<anonymous> (/home/cloudhead/src/golem/test.js:29:13)
at Module._compile (module.js:374:26)
at Object..js (module.js:380:10)
at Module.load (module.js:306:31)
at Function._load (module.js:272:10)
at Array.<anonymous> (module.js:393:10)
at EventEmitter._tickCallback (node.js:108:26)

Closing comment (2011-10-19T01:08:04Z): Dupe of #540, closed by 200df86
Repository: nodejs/node-v0.x-archive

Issue #5666: net module memory leak
Created: 2013-06-11T17:19:50Z
very simple socket server
var net = require('net');
var server = net.createServer(function(c) { //'connection' listener
    while(1) 
        c.write('hi\n');
});
server.listen(8124);
only one client ...
memory leak why that happens?
(v0.4.12 is not happen;;;)
while(1) console.log('hi');
too...

Duplicate issue #5708: Memory leak, running a counting loop.
Created: 2013-06-17T07:28:34Z
While testing some stuff with a node framework, i noticed my memory usage sky-rocketed out of control.  I wanted to see what was causing it, so i wrote a simple test.  The files for these test can be found at the link below.  Both the javascript file (run by node) and the .c file (compiled down to a.out) run loops that add to an integer, and print the process id.  While running the tests, i noticed that node memory usage worked its way up to 1GB of memory usage.  The C version of the loop remained steady at 2044 bytes.  I'm assuming that this is a memory leak caused by node or v8.  I'm not sure on this, but wanted to bring this evidence afront for inspection.  The results.txt file shows my output from htop.  For convenience of anyone that would like to test this themselves, i have packed all files into a tar.gz
https://drive.google.com/folderview?id=0B2linT1ymg8aQzcwMk9XX0FucVk&usp=sharing
System Specs:
Intel Atom Dual Core D250
2048 DDR2 memory
OS: Ubuntu 13.04
Linux 3.8.0-25-generic i686 GNU/LINUX
node:  v0.10.11
gcc: v4.7.3
If you need more information, just tag me in a comment on here and i will respond.

Closing comment (2013-06-17T10:57:21Z): Duplicate of #5666 and others. Infinite loops don't give node.js the chance to reclaim data that's associated with each write.
Repository: nodejs/node-v0.x-archive

Issue #2387: fs.readdir/open broken for non-UTF8 filenames
Created: 2011-12-20T14:58:36Z
I have problems with fs.readdir(Sync) and directories/filenames that include ISO-8859-1 characters. The following is an example for this using the special character ß (ISO-8859: 223 / 0xDF / 0337 (dec/hex/oct) in UTF-8: U+00DF (0xC3 0x9F)):
$ locale
LANG=en_US.ISO-8859-1
$ mkdir isotest; cd isotest
$ touch Gro$'\xDF'
$ ls
Groß
$ node
> var fs = require('fs');
> var file = fs.readdirSync('.')[0];
> file
'Groï¿½' # already broken encoding
> new Buffer(file, 'binary')
<Buffer 47 72 6f fd> 
> fs.openSync(file, 'r');
Error: ENOENT, no such file or directory 'Groï¿½'
    at Object.openSync (fs.js:230:18)
    at repl:1:4
    at REPLServer.eval (repl.js:80:21)
    at repl.js:190:20
    at REPLServer.eval (repl.js:87:5)
    at Interface.<anonymous> (repl.js:182:12)
    at Interface.emit (events.js:67:17)
    at Interface._onLine (readline.js:162:10)
    at Interface._line (readline.js:426:8)
    at Interface._ttyWrite (readline.js:603:14)
> # other tests try to open the file manually:
> fs.openSync('Gro\xDF', 'r')
Error: ENOENT, no such file or directory 'GroÃ�'
> fs.openSync('Gro\u00DF', 'r')
Error: ENOENT, no such file or directory 'GroÃ�'

I'm using node v0.6.4 with linux. Related issues #1971 #1842 and #1785

Duplicate issue #8619: unable to deal with file names that have invalid encoding
Created: 2014-10-25T15:18:36Z
There is a file in my user's file system and Node.js cannot use any of the fs API on it, because the file name has an invalid encoding. File names are byte arrays; not strings. This is the root of the problem.
How should I solve this problem? Is this a limitation of Node.js, that it cannot deal with file names with invalid encodings?
andrewrk/groovebasin#383

Closing comment (2014-11-15T01:04:13Z): I have a sneaking suspicion that this is related to #2387 -- the age old problem of JS strings being in UCS2, but the filesystem being in ISO-8859-1, or some other encoding.
Repository: nodejs/undici

Issue #1270: ProxyAgent can not work with Pool request
Created: 2022-03-10T03:04:52Z
Bug Description
  const pool = new Pool(url);
  const proxyAgent = new ProxyAgent("http://one-proxy:8080");
  const { statusCode, body } = await pool.request({
    ...
    dispatcher: proxyAgent,
    ...
  ...});

when Pool is used, it's not picking up { ..., dispatcher: new ProxyAgent("...")}, nor setGlobalDispatcher(proxyAgent).
However, request is used, ProxyAgent works.
my code is behind the proxy. also Pool is the one I will need to use.
Reproducible By

Expected Behavior

Logs & Screenshots
{
  error: Error: getaddrinfo ENOTFOUND eth-testnet-communities-152b99c6597fb22e.elb.us-west-2.amazonaws.com
      at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)
      at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
    errno: -3008,
    code: 'ENOTFOUND',
    syscall: 'getaddrinfo',
    hostname: 'eth-testnet-communities-152b99c6597fb22e.elb.us-west-2.amazonaws.com'
  }
}

Environment
Node v16.14.0
Additional context

Duplicate issue #1153: HTTP Proxy with undici and HTTPDataSource
Created: 2021-12-23T17:16:07Z
Hi,
I'm using HTTPDataSource that uses undici.
I'm trying to make it work through a proxy.
I've tried to use:
const proxyAgent = new ProxyAgent({  uri: '0.0.0.0:3128', protocol: 'http', } ); setGlobalDispatcher(proxyAgent);
The problem is, it does not seem to work. Could You provide any suggestions?
I'm using HTTPDataSource the recommended way based on the manual provided here:
https://github.com/StarpTech/apollo-datasource-http

Closing comment (2022-09-13T14:04:03Z): This is a duplicate of #1270.
Repository: nodejs/undici

Issue #2954: Unexpected token on class private field check with in operator
Created: 2024-03-13T09:29:19Z
Bug Description

The issue arises from undici@6.7.0,  which is believed to be caused by the PR https://github.com/nodejs/undici/pull/2743/files#diff-7d87ea2cf8b3c20e25ac9a785c4ae7603f4a8c3d7bf3a80f5fb46265f0dba078R776
 ⨯ ./node_modules/undici/lib/web/fetch/util.js
Module parse failed: Unexpected token (608:63)
|             // 5. If object is not a default iterator object for interface,
|             //    then throw a TypeError.
>             if (typeof this !== "object" || this === null || !(#target in this)) {
|                 throw new TypeError(`'next' called on an object that does not implement interface ${name} Iterator.`);
|             }

Import trace for requested module:
./node_modules/undici/lib/web/fetch/util.js
./node_modules/undici/lib/web/fetch/index.js
./node_modules/undici/index.js
Reproducible By
The issue can be replicated in any Next.js project by simply upgrading undici to version 6.7.0

Expected Behavior
Run without error

Logs & Screenshots

Environment

Additional context

Duplicate issue #3134: NextJS: Module parse failed: Unexpected token
Created: 2024-04-17T10:22:44Z
Bug Description
When importing an elastic search package in a NextJS 14 project I get this error:
 ⨯ ../../node_modules/.pnpm/undici@6.13.0/node_modules/undici/lib/web/fetch/util.js
Module parse failed: Unexpected token (874:57)
|       // 5. If object is not a default iterator object for interface,
|       //    then throw a TypeError.
>       if (typeof this !== 'object' || this === null || !(#target in this)) {
|         throw new TypeError(
|           `'next' called on an object that does not implement interface ${name} Iterator.`

Import trace for requested module:
../../node_modules/.pnpm/undici@6.13.0/node_modules/undici/lib/web/fetch/util.js
../../node_modules/.pnpm/undici@6.13.0/node_modules/undici/lib/web/fetch/headers.js
../../node_modules/.pnpm/undici@6.13.0/node_modules/undici/index.js
../../node_modules/.pnpm/@elastic+transport@8.5.1/node_modules/@elastic/transport/lib/connection/UndiciConnection.js
../../node_modules/.pnpm/@elastic+transport@8.5.1/node_modules/@elastic/transport/lib/connection/index.js
../../node_modules/.pnpm/@elastic+transport@8.5.1/node_modules/@elastic/transport/index.js
../../node_modules/.pnpm/@elastic+enterprise-search@8.6.1/node_modules/@elastic/enterprise-search/index.js
../api/src/drivers/search/getEnterpriseSearchClient.ts
../api/src/drivers/search/AppSearchDriver.ts
../api/src/app/App.ts
../api/src/app/index.ts
./src/app/api/graphql/route.ts

Environment
OS: MacOS Sonoma v14.4.1
NextJS version: v14.2.1
$ node --version
v18.19.0

Closing comment (2024-04-17T10:32:33Z): Upstream issue in nextjs. Duplicate of #2954
Repository: nodejs/undici

Issue #2954: Unexpected token on class private field check with in operator
Created: 2024-03-13T09:29:19Z
Bug Description

The issue arises from undici@6.7.0,  which is believed to be caused by the PR https://github.com/nodejs/undici/pull/2743/files#diff-7d87ea2cf8b3c20e25ac9a785c4ae7603f4a8c3d7bf3a80f5fb46265f0dba078R776
 ⨯ ./node_modules/undici/lib/web/fetch/util.js
Module parse failed: Unexpected token (608:63)
|             // 5. If object is not a default iterator object for interface,
|             //    then throw a TypeError.
>             if (typeof this !== "object" || this === null || !(#target in this)) {
|                 throw new TypeError(`'next' called on an object that does not implement interface ${name} Iterator.`);
|             }

Import trace for requested module:
./node_modules/undici/lib/web/fetch/util.js
./node_modules/undici/lib/web/fetch/index.js
./node_modules/undici/index.js
Reproducible By
The issue can be replicated in any Next.js project by simply upgrading undici to version 6.7.0

Expected Behavior
Run without error

Logs & Screenshots

Environment

Additional context

Duplicate issue #3009: Unable to compile when using in typescript
Created: 2024-03-28T11:24:09Z
This code
import { request } from 'undici';

export async function getDevices() {

  const catResult = await request('https://aws.random.cat/meow');
  return {};
}


gives me an unable to compile error

Closing comment (2024-04-06T22:39:29Z): Duplicate of #2954
Repository: nodejs/undici

Issue #386: Client will connect even if all requests are aborted
Created: 2020-08-30T17:33:19Z
Client will not notice requests might be aborted until request.onConnect which will only happen after the socket has connected. Thus the client might unnecessarily create a connection if all pending requests have been aborted.
A bit of an edge case.

Duplicate issue #871: Aborting the request before `onConnect`
Created: 2021-07-11T17:12:37Z
When using dispatcher.dispatch there is no other way than to abort the request when the socket gets connected.

Closing comment (2021-07-11T21:40:14Z): Ah it seems this was a duplicate of #386
Repository: nodejs/undici

Issue #1992: bundling issues with webpack
Created: 2023-03-06T17:55:09Z
Currently package.json specifies >=12.18 in engines.node, but the code uses ??= and util/types which are Node.js 15+ features.
The implementation should look like...
Updating package.json to reflect the correct minimum Node.js version.
I have also considered...
Alternatively, the code could stop using those features to retain compatibility with 12.18+

Duplicate issue #2015: unidici doesn't play nice with webpack
Created: 2023-03-18T18:00:37Z
I am writing a package in deno, and compiling it into npm.
Somehow unidici gets in the compiled target.
I then use webpack because I want to use this package in react setup.
webpack refuses to process unidici because of two dependencies: util/types and stream/web
I haven't found a polyfill for them.
Any idea what can be done?
this is my webpack config
const NodePolyfillPlugin = require("node-polyfill-webpack-plugin");

const path = require("path");

module.exports = {
  mode: "production",
  entry: "./src/index.js",
  output: {
    filename: "main.js",
    path: path.resolve(__dirname, "dist"),
  },
  plugins: [new NodePolyfillPlugin()],
  resolve: {
    fallback: {
      perf_hooks: false,
      async_hooks: false,
      dns: false,
      tls: false,
      child_process: false,
      fs: false,
      net: require.resolve("net-websocket-polyfill"),
      diagnostics_channel: require.resolve("diagnostics_channel"),
      worker_threads: require.resolve("bthreads"),
    },
  },
};

Closing comment (2023-03-18T18:23:52Z): this is a duplicate of #1992
Repository: nodejs/undici

Issue #734: Make options argument optional in undici.pipeline and undici.stream
Created: 2021-04-12T23:00:18Z
Make options argument optional in undici.pipeline and undici.stream.
Maybe also undici.connect and undici.upgrade.

Duplicate issue #624: pipeline and stream API should have optional opts parameter
Created: 2021-03-26T10:33:11Z

Closing comment (2021-04-12T23:04:52Z): duplicate #734
Repository: nodesource/distributions

Issue #1359: Ubuntu Budgie 22.04 LTS (Jammy Jellyfish)
Created: 2022-03-27T06:24:18Z
Your distribution, identified as "Ubuntu Jammy Jellyfish (development branch)", is a pre-release version of Ubuntu. NodeSource does not maintain official support for Ubuntu versions until they are formally released. You can try using the manual installation instructions available at https://github.com/nodesource/distributions and use the latest supported Ubuntu version name as the distribution identifier, although this is not guaranteed to work.

Duplicate issue #1376: NodeJs for Ubuntu 22.04 LTS (Jammy)
Created: 2022-04-21T19:35:56Z
Hello,
I was using the official release of Ubuntu 22.04 (ubuntu-jammy-oci-amd64-root.tar.gz), from:
https://partner-images.canonical.com/oci/jammy/current/
And I did run the command below:
curl -fsSL https://deb.nodesource.com/setup_16.x | bash -
And then I got this message:
Your distribution, identified as "jammy", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Could you please review this and update it?
Sorry for reporting this so early.

Closing comment (2022-04-21T20:50:54Z): Duplicate of #1359
Repository: nodesource/distributions

Issue #128: Node.js 4.0.0 on el6?
Created: 2015-09-10T13:47:12Z
https://rpm.nodesource.com/pub_4.x
There only seems to be a folder for 7 here.
I can roll my own but would like to know if there are plans to support EL6 in the future for node.js 4.x.

Duplicate issue #221: redhat-release-server-6Server-6.5.0.1.el6.x86_64 not supported
Created: 2016-01-26T11:05:01Z
Your distribution, identified as "redhat-release-server-6Server-6.5.0.1.el6.x86_64", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

Closing comment (2016-01-27T17:27:50Z): This issue is being tracked in #128. Thanks.