All Issues
24,993 verified issues
EventEmitter memory leak on node v0.3.5, with possible fix
I created a very simple http-proxy instance for some testing: https://gist.github.com/790342 Running on node v0.3.5, this immediately returns the warning: [code block] when an http request is made. Under load, it appears this is indeed leaking memory. After about 5 minutes with Siege hitting the proxy with 400 concurrent requests, it dies with: FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory However, removing the (empty?) pool error handler on line 184 of node-http-proxy.js appears to fix this. Should this be set once upon pool creation, rather than when the pool is retrieved for each request?
Refresh token automatically on HTTP 401 or 403 response?
I'm using the API (v1.0.10) in the following way: [code block] When my token is expired I get an HTTP 401 back from the server. However, I'd expect the library to automatically refresh my token and make the request again. It doesn't. I figured out that a workaround is to add the `expiry_date` when calling setCredentials, e.g. [code block] But this isn't mentioned in the docs. I'd expect `expiry_date` to be optional and the API to auto refresh the token.
Server-Sent Events transport
I recently wrote a transport for using XHR for sending and Server-Sent Events for receiving. In my opinion SSE provides a great alternative to the overhead of websockets (especially if you're mostly receiving data and not sending very often). Also, there were some recent changes to the SSE editor's draft that show possible upcoming support for cross-origin usage: http://dev.w3.org/html5/eventsource/. Mozilla has already committed changes to utilize this usage based on this draft: https://hg.mozilla.org/mozilla-central/rev/ed783dfd8179. This will make SSE even more handy/useful. I have already taken the initiative to add support for this in the transport as well. Is there any interest in adding a transport like this?
Fail to install aws-cli via sudo pip install awscli
I'm on El Capitan OSX. Got following error: Installing collected packages: six, python-dateutil, docutils, botocore, pyasn1, rsa, awscli Found existing installation: six 1.4.1 DEPRECATION: Uninstalling a distutils installed project (six) has been deprecated and will be removed in a future version. This is due to the fact that uninstalling a distutils project will only partially uninstall the project. Uninstalling six-1.4.1: Exception: Traceback (most recent call last): File "/Library/Python/2.7/site-packages/pip/basecommand.py", line 211, in main status = self.run(options, args) File "/Library/Python/2.7/site-packages/pip/commands/install.py", line 311, in run root=options.root_path, File "/Library/Python/2.7/site-packages/pip/req/req_set.py", line 640, in install requirement.uninstall(auto_confirm=True) File "/Library/Python/2.7/site-packages/pip/req/req_install.py", line 716, in uninstall paths_to_remove.remove(auto_confirm) File "/Library/Python/2.7/site-packages/pip/req/req_uninstall.py", line 125, in remove renames(path, new_path) File "/Library/Python/2.7/site-packages/pip/utils/init.py", line 315, in renames shutil.move(old, new) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 302, in move copy2(src, real_dst) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/System/Library/Framewo
Maximum call stack size exceeded
Discussed in https://github.com/tailwindlabs/tailwindcss/discussions/8578 <div type='discussions-op-text'> <sup>Originally posted by jithureddy June 10, 2022</sup> Hi, Please help Just updated my project to latest `"tailwindcss": "^3.1.1"` and using create react app setup from here. It was working great with `"tailwindcss": "^3.0.4"`. [code block] <img width="816" alt="image" src="https://user-images.githubusercontent.com/5911189/173025695-b85732f2-9a53-4aa1-a8e4-a87042bff58f.png"> </div>
Client.disconnect() to force a client to disconnect
It would be great to have a disconnect() method on Client instances. This is useful to implement mechanisms such as IRC's kick/ban. Basically there needs to be a way to get rid of abusers.
Binary on darwin fails with "illegal instruction" on some machines
The current `fig` release doesn’t work for me: [code block] I’m running OS X 10.9.3 on a 1.6 GHz Intel Core 2 Duo (Late 2010 MacBook Air).
[expo-image-picker] launchCameraAsync doesn’t open the camera on Android after the 2025-09-05 security update
Minimal reproducible example https://github.com/deka0106/expo-image-picker-test Steps to reproduce After applying the Android security patch 2025-09-05, calling `launchCameraAsync()` from `expo-image-picker` does not show the camera UI immediately. The camera only appears after the app is backgrounded and then resumed. It can be reproduced with the following steps: - Clone reproducible example - Run `pnpm install` - Run `pnpm run android` - Tap "Open Camera" When tapping "Open Camera", logcat outputs the following: [code block] I’ve confirmed the issue reproduces in the following environments: - Device: Pixel 9a, Pixel 8, Pixel 7a, Pixel 6 - Android OS: 16 - Security Update: 2025-09-05 Environment [code block] Expo Doctor Diagnostics [code block]
Unexpected token U in JSON
Issue Summary It throws an unhandled exception. Code Snippet [code block] Exception/Log [code block] Technical details: twilio-node version: 3.43.0 node version: 12.10.0
`npm install` fails when installing repo dependencies for development
Bug report - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug On running `npm install` after cloning the repository, it fails with the following log (some parts trimmed) : [code block] To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Follow the steps mentioned here. Clone the repo and install dependencies 2. It should fail. System information - OS: Tried on Arch Linux (EndeavourOS) and Ubuntu 23.10 - Version of npm: 10.2.3 and 9.9.2 - Version of Node.js: v21.5.0 v18.19.0 Additional context Seems to me that @gregnr/libpg-query package isn't building properly. I also notice that this URL: https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v13.4.0-dev.12-node-v108-linux-x64.tar.gz is returning a 404. Do let me know if I can give more information about my systems. I've tried and tested this both on my local machine and Ubuntu box. Thanks!
Cluster mode connections growing over time
We've recently been seeing huge slowdowns on our servers. We can't totally blame on redis yet, but we've noticed a huge amount of connections on our redis instance It seems to go down only when we restart the servers. For context, we have roughly 16 servers running all creating 4 connections each to the cluster. The connections are long-lived (aka we never create new ones during the process). So I can only assume something in the reconnection behavior maybe isn't cleaning up the previous connections. We are currently using ioredis version 4.19.2. I'll look at updating to latest see if it helps, but I haven't seen anything in the changelog that would suggest a fix. I also stumbled on #1295 which was closed for lack of more info. I can provide as much info as I can. Not sure I can run `DEBUG=ioredis:*` on our production servers, but here's what we have from cloudwatch for the past 3 months where we sometimes peak over 700 connections I also ran `client list` on our redis instance a few hours after restarting many of our servers if it can help. We can see that a single addr can have multiple connections to the same topic(name) <details> [code block] </details>
batch error when upload file vector in file_search type tool assistant ia
Confirm this is a Node library issue and not an underlying OpenAI API issue - [X] This is an issue with the Node library Describe the bug when i upload file vector to file_seach type tool assistant, then I follow instruction from doc, i had that error when i process to finish data :`js file-batches.js:99 if (files === null || files.length == 0) { ^ TypeError: Cannot read properties of undefined (reading 'length') ` To Reproduce 1 install 2 create assistant ia tool type file_search 3 upload file for this tools Code snippets _No response_ OS win 10 Node version >=20 Library version >=5.4.4
docker-compose build and docker build lead to different IDs
When building containers for my project I noticed that, even if I build from the same Dockerfile, `fig` and `docker` build different image IDs in the end. I also tried to use the same tag, but the images still were different. Built with fig: [code block] Built with docker: [code block] `ec26eedffc59` and `8fecc44750ee` is the same file, but added with different IDs. Is there anything I've overlooked or is this a bug? Using fig 1.0.1 docker 1.3.2.
New site
features I'd like: - new docs - better doc organization (guide, reference, use-cases) - "branding" aka express logo etc, and lighter design - easier addition of apps instead of the browser screenshots right now - multiple languages
高负载的时候会出现数据错误！！
开始是 ioredis + redis，因为准备加更多的缓存，所以换成了 codis。开始是正常的，直到某次代码更新，增加了大量的缓存数据。然后一直都会出现奇怪的错误，比如 get 一个数字，却返回了一串字符，总之返回的不是想要取的数据。在最简单的 redis.get("key") 代码里也会出现…… 同时伴随着 node 内存使用会增加很多（大部分会这样），我们以为是 codis 的问题，于是又把 codis 换回到原生的 redis 了。 这时候已经正常了（或者还有低概率发生这种情况但是没有发现，因为从 redis 取一段数据存到另一个地方可能并不会报错，类型被自动转换了之类的）。 直到昨天服务上整体的访问量翻了 N 倍，突然又爆发出来这个问题。我们用的 sentry，会一直出现各种奇怪的 cast 错误……比如把一串 json string cast 到 _id ，总之是和上面一样的问题。而且会集中爆发在一个或几个特定的 node 实例上，重启即可正常。 现在只能怀疑 ioredis 的 异步处理方式是不是在高负载下并不能保证正确的工作？因为 redis 协议的实现方式正确性基本依赖于一一对应的命令和应答，然而在 ioredis 里接收到应答是放到一个队列里（并没有仔细看源码，但好像大体是这么写的），然后通过 command send 的队列回调取去对应的数据，所以如果中间丢失了一段的话，那么这个 connection 之后的所有数据都会串掉…… 这个问题非常可怕。。。。
File watcher resulting in high CPU use on Mac/Linux for large folders
We are using chokidar for file watching. Chokidar is known for performing bad over large folders (see https://github.com/paulmillr/chokidar/issues/410). To investigate: - can we consume a newer version of chokidar with the scalability issue fixed - can we change our watching strategy to only watch what we need instead of always watching root - can we switch to another watching library that is more efficient Workaround: Find the large folders in your workspace and add them under the `files.watcherExclude` setting
Proposal: docker-compose events
There have been a few requests for supporting some form of "hooks" system within compose (#74, #1341). A feature which runs commands on the host would add a lot of complexity to compose and the compose configuration. Another option is to support these features by providing a way for external tools to run the command triggered by an event. docker events provides an event stream of all docker events, but would still require filtering. `docker-compose events` could provide a similar interface by filtering the events returned by `/events` and return a stream of only the events related to the active compose project. The event stream could also include a new field `"service": <service_name>` in addition to the fields already provided by `/events`
[BUG] Integrity check fails for azure artifacts (and apparently other private registries) NPM packages
Current Behavior: We are trying to upgrate to NPM 7, but we run into problems with getting packages from azure artifacts. The following log is shown, when running `npm i --verbose`: [code block] Expected Behavior: I expect the packages to be downloaded correctly, just as they did using npm 6 Steps To Reproduce: Reference packages to azure artifacts in your package.json. Try to run `npm install` expected: packages install actual: error as shown above Environment: - OS: windows 10 - Node: v12.16.1 - npm: 7@beta10
Error result: Streaming is strongly recommended for operations that may take longer than 10 minutes.
What's problem? Error result: Streaming is strongly recommended for operations that may take longer than 10 minutes. See https://github.com/anthropics/anthropic-sdk-python#long-requests for more details
Axios vs jQuery post CORS issue
When doing a CORS post request, jQuery succeeds but Axios gets a CORS error in the console. This gets a CORS error [code block] But this works [code block] Am I missing something with Axios? My server is already configured for CORS requests.