All Issues
24,993 verified issues
Messages from client to WebSocket are not working
I have a problem with proxying messages from the client to the websocket server. The messages do not reach the websocket server at all. When I connect to the server directly, it works. However, all other things work. I can conenct & send messages to the client. I´m using the following websocket server: https://github.com/miksago/node-websocket-server Has anyone the same problem?
Stuck in 'connect' state with Cluster and Node 10.x
I'm seeing ioredis 3.2.2 intermittently getting indefinitely stuck in the 'connect' state when run with Redis.Cluster under all versions of Node 10 up to the latest (10.3.0), and not under previous major versions (e.g. 9.11.1). I'm working on a minimal repro to illustrate this, but right now it looks as though the Node 10 stream is not emitting a 'close' event to trigger `eventHandler.closeHandler(_this)` under Node 10. I'm not yet sure why this happens, but I thought I'd give a heads-up as I look at it in case anyone else is seeing the same.
Terminal shows corrupt texture sometimes when resuming the OS from a sleep state
Workaround: Press ctrl++ and ctrl+- (mac: cmd++, cmd+-) to zoom VS Code in and out which will do a complete redraw of the terminal. --- Repro: 1. Open a terminal, run some commands 2. Sleep system 3. Resume the system (I think the delay between 2 and 3 has to be a while) What happens exactly differs across machines, I've seen full black, full transparent and things like this: <img width="228" alt="screen shot 2019-03-01 at 10 54 08 am" src="https://user-images.githubusercontent.com/2193314/53659411-5b467c00-3c10-11e9-9185-a63b426ce26f.png"> It seems like both the main terminal canvas texture as well as the texture atlas textures can become corrupted.
Issue with using 'stream' option in TypeScript with CreateChatCompletionResponse
Describe the bug I have been exploring how to use the 'stream' option in TypeScript for discussion #18. While trying to implement it, I found that the CreateChatCompletionResponse does not have a property 'on', which is required to stream the data. To overcome this issue, I converted the CreateChatCompletionResponse to Readable type, and it worked perfectly. However, I believe this is a problem that needs to be addressed as it is not intuitive for TypeScript users. To Reproduce 1. Use the createChatCompletion method to create a chat completion. 2. Add the 'stream' property and set it to 'true' to enable streaming. 3. Add the 'responseType' property to the axios config object and set it to 'stream' to specify the data format. 4. Try to access the 'on' property in the response data, which is not available in TypeScript. Code snippets [code block] OS Windows 11 22621.1413 Node version Node v18.8.0 Library version openai v3.2.1
Very slow with socket.io?
I currently have this set up: port 80: note-http-proxy port 3000: rails port 8888: nodejs server (connection made via socket.io) I have the following in my node-http-proxy: [code block] basically any socket.io connection will be forced to port 8888. When I run this on firefox, I am noticing the following error: When I run this on chrome, I am seeing about a 10 second delay before socket.io can make its first communication. Please look at the screen shot at http://i.imgur.com/Y0rHk.png
Importing Stripe via ES Modules does not respect monkey-patching 'http'
Describe the bug When trying to mock responses made with stripe-node in a Node.js enviroment, the requests hit the real server instead of getting caught by MSW. To Reproduce You can copy and paste the code below. (Either write actual handlers for your `stripeHandlers`, or you can leave them out, as we did below. If you want to try it out with handlers, simply spread them into `setupServer`.) Sine we configured `onUnhandledRequest: 'warn'` MSW should log out to the console when requests are uncaught. The manual method with `axios` works correctly and logs out this warning / reacts when you configure handlers. However, the second (in the code blocked `skip`ped) test does NOT log out this warning and simply hits the servers. [code block] [code block] Expected behavior MSW can intercept the Stripe requests. I assume this library does HTTP requests somehow esoterically, so it would be nice to learn how it does it, so that we can get MSW to work. Code snippets _No response_ OS macOS Node version 18.6.0 Library version stripe-node v12.12.0 API version 2022-11-15 Additional context _No response_
Suggestion: non-nullable type
Introduce two new syntax for type declaration based on JSDoc [code block] by default type are nullable. Two new compiler flag : - `inferNonNullableType` make the compiler infer non-nullable type : [code block] - `nonNullableTypeByDefault` (I guess there might be a better name) : [code block]
warming 'websocket connection invalid' in new version chrome 15.0.8 74.106
But today I found the things don't work properly. on the server side, there is a warming: websocket connection invalid debugs, and on the client I can't see anything. The only change I found is the Chrome version is updated to 15.0.8 74.106 now, the old version Chrome is working well
new Error("Please install chromadb as a dependency with, e.g. `npm install -S chromadb`") but chromadb existed in node_modules in newer langchain since version 147
My previous code used to be working in 0.0.145, [code block] now in newer version, 0.0.147, 0.0.148, 0.0.149(not tested yet but seems to be still wrong) are all getting an errors saying [code block] however the node_modules has the latest chromadb 1.5.8 , even downgraded to 1.5.3, still output the same error for no reason, any ideas why chromadb package not found ?
Support customParameters when calling js client using api calls
Hi, use case: We use twilio client(js) as part of our contact center platform. In response to certain type of callers in the queue, we ring certain agents using apis, and if they accept the call, only then the caller is whisked out of queue and conferenced with the agent. When calling a client using api, we want to piggyback extra details about the call like call id in the crm, so that extra details about the caller can be displayed to the agent. (This is not our exact flow, but simplified, to share the scenario)
AttributeError: module 'anthropic' has no attribute 'beta'
Hi , I am testing the Anthropic API / MCP integration in Python SDK. I received the error: "AttributeError: module 'anthropic' has no attribute 'beta' Have you run into this ? Any idea if the Python SDK is ready for beta messages API ? my code: [code block] Reference doc/example: https://docs.anthropic.com/en/docs/agents-and-tools/mcp-connector Anthropic SDK version: Version: 0.62.0 Anthropic SDK libraries / namespaces : `['AI_PROMPT', 'APIConnectionError', 'APIError', 'APIResponse', 'APIResponseValidationError', 'APIStatusError', 'APITimeoutError', 'Anthropic', 'AnthropicBedrock', 'AnthropicError', 'AnthropicVertex', 'AsyncAPIResponse', 'AsyncAnthropic', 'AsyncAnthropicBedrock', 'AsyncAnthropicVertex', 'AsyncClient', 'AsyncMessageStream', 'AsyncMessageStreamManager', 'AsyncStream', 'AuthenticationError', 'BadRequestError', 'BaseModel', 'BetaAsyncMessageStream', 'BetaAsyncMessageStreamManager', 'BetaContentBlockStopEvent', 'BetaInputJsonEvent', 'BetaMessageStopEvent', 'BetaMessageStream', 'BetaMessageStreamEvent', 'BetaMessageStreamManager', 'BetaTextEvent', 'Client', 'ConflictError', 'ContentBlockStopEvent', 'DEFAULT_CONNECTION_LIMITS', 'DEFAULT_MAX_RETRIES', 'DEFAULT_TIMEOUT', 'DefaultAioHttpClient', 'DefaultAsyncHttpxClient', 'DefaultHttpxClient', 'HUMAN_PROMPT', 'InputJsonEvent', 'InternalServerError', 'MessageStopEvent', 'MessageStream', 'MessageStreamEvent', 'MessageStreamManager', 'NOT_GIVEN', 'NoneType', 'NotFoundError', 'NotGiven', 'Omit', 'PermissionDeniedE
Twilio Verify - requested resource /Services/.../VerificationCheck was not found
Issue Summary Seeing this in our sentry: `The requested resource /Services/VA.../VerificationCheck was not found` Customers are complaining, seems to be happening occasionally as can not reproduce locally? Trying to get a better idea. Steps to Reproduce 1) Type in phone number 2) Send API call to Twilio Verify to send verification code Code Snippet [code block] Exception/Log [code block] Technical details: twilio-node version: v3.50.0 node version: v12
consider using SRV records for redis & sentinel hosts
In an ever changing world like docker & microservices , the IP-adresses + PORTS of hosts change. Traditionally only DNS takes care of the hostname->IP - Ideally on connection failure the client would lookup the DNS & Port again. - On redis-sentinel topology change it could lookup the master & slave DNS & Port again. We could leverage the SRV record to find the current redis host & port instead of a regular dns lookup. This ticket is to ask if you will find the useful, and would be willing to accept a pullrequest for implementing this.
Unix socket support
So I wanted to use node-http-proxy to serve content from multiple apps running locally on unix sockets. I found out quick that this was not going to work: [code block] I spent the next 5 hours or so trying to figure out why. It turns out the problem was in this method: [code block] That method is always looking for a host and a port, because it does a split on the string. It could easily be modified to use a unix socket path, which is the first argument for the net.Server.listen method, the same as a port. The core lib simply checks if this value is a number or a string. So anyway, rather than modifying the code because I didn't want to monkey around in there just yet. The simple solution after 5 hours of trying to make this reverse proxy unix sockets was this: [code block] That my friends, is one magical colon. Thanks again for this great and extremely useful module. Let me know what you think about all this, I can try to contribute. Jim
[BUG]: drizzle-kit push:sqlite fails to copy table data after adding a column
What version of `drizzle-orm` are you using? 0.28.6(better-sqlite3@8.6.0) What version of `drizzle-kit` are you using? 0.19.13 Describe the Bug After adding a column to a table in schema, and executing `drizzle-kit push:sqlite`, it fails with error: SqliteError: table posts has 4 columns but 3 values were supplied In the database there's now `__old_push_posts` table, that the original `posts` table was renamed into, with all the data. There's also now a new `posts` table with 4 columns, but no data. The error message suggests that drizzle-kit fails to copy the data over after the change, because of the different number of columns. Running `push` again, warns that it's going to delete the `__old_push_posts`, but I know that it contains the original data, not copied to the new `posts` table. Expected behavior drizzle-kit should be able to add a new column to a table in an sqlite db, with all the data intact, after adding a column to a table schema. Environment & setup Apple M1 Pro, Sonoma, Node v19.7.0
Model defaults to version 2.1 even when specified to claude-2
Hello and thank you for providing access to the SDK and Claude APIs. Two notes: 1. Pydantic Versioning: The Anthropics SDK currently has a hard dependency on Pydantic version 1.0, which causes other modules, of which are dependent on higher versions, to break. 2. Model Versioning in Completion API: When using the Python SDK's completion API, it appears that the specified model version is not being honored. Despite selecting "claude-2" as the model, the API defaults to version 2.1. Below are the relevant version details and execution code: Version Information: [code block] Execution Code: [code block] Response: [code block]
Huge performance issue
Hi all, I have a huge performance issue with node-http-proxy, maybe I'm missing something, hopefully someone can point out what's wrong. Here's the code I'm using for the proxy (listening on 9000): [code block] and here's the code of the server listening on 8000: [code block] I used wrk to benchmark the performance of the proxy. First, I test the http server to see how many requests it can handle: wrk -c 64 -d 15s http://127.0.0.1:8000 Requests/sec: 26255.78 Now when I test the proxy: wrk -c 64 -d 15s http://127.0.0.1:9000 Requests/sec: 543.84 Something is clearly wrong, so I inspected the cpu usage during the benchmark and I noticed that when I directly test the http server (port 8000), the cpu usage of the server's process stays very close to 100% for the duration of the test (which is expected), but when I test the proxy, the proxy's process gets to 100% but quickly (1-2 seconds after the beginning of the test) drops to 0% Note that wrk, the proxy and the hello world server run on different threads, this issue is not related to insufficient resources (I have 8 thread on my machine). I have also tested nginx and HAProxy, and both did fine. The main reason I want to use http-proxy is for load balancing, but so far it looks like it's gonna be a bottleneck more than anything else.
is express dying?
Since TJ left the project and it became "property" of StrongLoop the project is slowly dying. I guess you (StrongLoop) promised TJ and thus a community to continue to maintain the code. Sure you want to push part of express users to use yours solutions and to make money on support. But open-source gave a start to your company and if you don't want to share back your code and time, just give a control back to community
TypeScript typed statusCallbackEvent writes invalid attribute value
As can be seen from the example code and its output below, `statusCallbackEvent` attribute ends up having wrong delimiter, comma instead of space, in the resulting XML, and this causes error on Twilio side. Version: 3.37.0 Code Snippet (main.ts) [code block] Output [code block]
[cluster mode] inconsistent errors
Cluster is created and then destroyed before and after the tests. So test runs are idempotent. For some reason, sometimes redis cluster client instance doesn't have `sendCommand` on it and sometimes it does. I assume that context can be rewritten on retry or smth and become 'undefined' [code block] [code block]