All Issues
24,993 verified issues
Accessing headers from proxy target response
I'm trying to access the headers that are passed back from the proxied server and I can't find a way to access them. I tried accessing the response object on the 'end' event emitted from the RoutingProxies internal HttpProxy: [code block] Is there no way to accomplish this currently or am I overlooking something?
Iterable vs List in the request datatypes
Consider the definition of `MessageParam`: [code block] The `Iterable` here doesn't allow me to write any kind of useful transformations over the datatype without changing its state in the process: [code block] which is quite inconvenient and could easily lead to all kind of errors. Is there any reason to use `Iterable` here and in other request/response datatypes? Could it be replaced with `List`?
I got : TypeError: url.URL is not a constructor running examples with my account parameters
Hello, I tried to run several examples from https://www.twilio.com/docs/libraries/node and running code (with my account sid/token) [code block] I got error : `TypeError: url.URL is not a constructor ` I tried to debug this issue in Twilio.js:258 and found : https://prnt.sc/w79oys and ref to undefined element https://prnt.sc/w79pqi and I see ref 10 years old https://prnt.sc/w79q4s can it be reason of my error and why so ? I tried version of twilio 3.54.1 (latest) and 3.54.0 but I have the same error and the same data I see debugging... In my OS : [code block] Why so and how it can be fixed ? Thanks!
Cannot find name 'this'
getting the following error when compiling in node 18 environment on my express server with ts: node_modules/@langchain/core/dist/language_models/chat_models.d.ts(64,129): error TS2304: Cannot find name 'this'. node_modules/@langchain/core/dist/language_models/llms.d.ts(66,122): error TS2304: Cannot find name 'this'. updated from "langchain": "^0.0.72" due to davinci deprecation here is my package.json: [code block] and tsconfig [code block]
500 Error: Both `options` and `options.target` are required.
when use http-proxy in this manner - i do not have a problem - the target is reached. httpProxy.createServer(function (req, res, proxy) { var target = locations[1]; proxy.proxyRequest(req, res, target); but i want to create server with express so i do the following var proxy = new httpProxy.HttpProxy(); proxy.proxyRequest(req, res, target); i get the following 500 Error: Both `options` and `options.target` are required. is there something else that is required.
Could not reach Cloud Firestore backend after upgrading to v9, but only in some projects
[REQUIRED] Describe your environment Operating System version: Windows 10 Browser version: Chrome 97 Firebase SDK version: 9.6.5 * Firebase Product: Firestore [REQUIRED] Describe the problem After upgrading to Firebase v9 from v8, I'm encountering the following error in 2 of 4 environments: [code block] Here are the environments and results: GCP Project ID | GCP Firestore Region | After upgrading to v9 -- | -- | -- Firebase Emulator | None (local) | Works fine {project}-dev | us-central | Works fine {project}-prod | us-central | Could not reach Cloud Firestore backend {project}-prod-ca | northamerica-northeast1 | Could not reach Cloud Firestore backend The code in all 4 environments are identical and the CI/CD pipeline for the 3 GCP projects are identical. It's particularly noteworthy that `{project}-dev` works fine while `{project}-prod` and `{project}-prod-ca` don't. Steps to reproduce: To see the results, I created these 2 test pages. They both use SDK v9: {project}-dev: https://student-dev.examind.io/firestore {project}-prod-ca: https://student-ca.examind.io/firestore You will notice that `{project}-dev` loads firestore data just fine, while `{project}-prod-ca` doesn't and outputs this to the console after 10 seconds: There are a couple of related issues (https://github.com/firebase/firebase-js-sdk/issues/5667, https://github.com/firebase/firebase-js-sdk/issues/5932), but seeing different results in different projects with the same codebase may be a
this.req.headers.upgrade is undefined when trying to call toLowerCase()
Hi guys, First of all apologies I can't be more helpful with this bug report - it occurred on a production server thus logging was down to its minimum level. I'm also not very familiar with all the magic which socket.io provides, but here it is anyway. All of a sudden, my server app crashed, and the following was all I had in the log: [code block] It looks like something unexpected happened when a new client tried to connect to the server - with my poor HTTP knowledge it looks like socket.io is always expecting an upgrade header which it didn't receive? I suspect the fact that I am _only_ supporting the websocket transport (e.g. io.set('transports', ['websocket']) may be relevant - perhaps an old client tried to connect which refused to send the upgrade header. Not sure. Using latest release, 0.8.6 for both client and server: [code block] Anything else I can provide you with to help, just shout.
slow performance using basic-proxy.js vs. no proxy
Hey all, I have been running some ab tests against the basicproxy.js service and have noticed it's about 3 times slower using the proxy than not. I'm on node 0.8.8 and ubuntu 11.10. Using proxy > ab -c 10 -n 1000 http://127.0.0.1:8000/ > Total response time was approx. 4 seconds No proxy > ab -c 10 -n 1000 http://127.0.0.1:9000/ > Total response time was approx. 1.7 seconds I ran the proxy with node http debugging enabled for a single request and this was the output. NODE_DEBUG=http node basic-proxy.js 1 request through proxy HTTP: SERVER new http connection HTTP: server response shouldKeepAlive: false I'm proxyrequest get base result HTTP: outgoing message end. HTTP: SERVER new http connection HTTP: server response shouldKeepAlive: true HTTP: write ret = true HTTP: outgoing message end. HTTP: AGENT incoming response! HTTP: AGENT isHeadResponse false HTTP: write ret = true HTTP: AGENT socket keep-alive HTTP: outgoing message end. HTTP: server socket close HTTP: server socket close 1 request without proxy HTTP: SERVER new http connection HTTP: server response shouldKeepAlive: false HTTP: write ret = true HTTP: outgoing message end. HTTP: server socket close Is the performance difference simply because we're asking the proxy to do that much more, that 3x increase seems like something is askew here. I tested this with different ab parameters, played around with the maxSockets settting and tried a different http agent, but nothing seemed to speed up going through th
Include lastResponse in error object
Hi If a stripe error occurs (e.g. StripeCardError), it would be useful to be able to access the headers within the error object - particularly the date header. Would it be possible for the error object to include either lastResponse or lastReponse.headers please? Thanks very much. Robin
Up {e2e.go}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-federation/4526/ Failed: Up {e2e.go} [code block] Previous issues for this test: #33357 #33377
Upgrading 5.10.4 to 5.10.5 cause test run to hang
*Do you want to request a feature or report a bug? Might be a bug What is the current behavior? Update: I think I managed to drill down a little but still not quite sure. I isolated to a few more specific test case suite. Will update here once I have more findings. Update: Sorry, wasn't able to find anything conclusive yet.. --- When using `5.10.4`, when I ran my test (ts-mocha), it run smoothly as usual without any issue but once I upgrade to `5.10.5`, there seem to have some weird issue like "hanging" on the test case. I don't have any error, or anything. Based on the changelog, the only thing it seem to possibly affect is the upgrade of `mongodb driver` to 3.6.2 but I am not sure where to begin checking. I'm not sure if it has anything to do with #9203 ? Just a wild guess. I am still able to run my application without issue, it seem to be affecting the test run now All test case seem to hit the `timeout` limit of 10s I understand this is little to go with, but do let me know what I can do to provide more information What is the expected behavior? Test to run as per usual to what it does in 5.10.4 or before What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version. Working node: v12.18.4 mongoose: 5.10.4 mongodb: 4.2.0 Not working* node: v12.18.4 mongoose: 5.10.5 mongodb: 4.2.0
kubernetes-e2e-gce-federation: broken test run
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-federation/1554/ Run so broken it didn't make JUnit output!
vSphere Provider: Mapping out the Next Steps
Wanted to kick off a higher level discussion of what needs to be done on the vSphere provider and in what order. - What are the important missing resources? - Are there any enhancements that need to be made to the existing functionality? - What do we need to do to ensure the provider works with all common versions of vSphere in the wild? Pinging @tkak and @mkuzmin to chime in as well as anybody else with interest/knowledge in the community.
bug: inference errors in middleware and context
Provide environment information System: OS: macOS 13.6.2 CPU: (10) arm64 Apple M1 Pro Memory: 117.69 MB / 32.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node Yarn: 1.22.19 - ~/.nvm/versions/node/v18.15.0/bin/yarn npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm pnpm: 8.2.0 - ~/Library/pnpm/pnpm Browsers: Brave Browser: 115.1.56.20 Chrome: 119.0.6045.123 Chrome Canary: 121.0.6127.0 Safari: 17.1 npmPackages: @trpc/client: 10.43.2 => 10.43.2 @trpc/react-query: 10.43.2 => 10.43.2 @trpc/server: 10.43.2 => 10.43.2 typescript: ^5.2.2 => 5.2.2 Describe the bug Hard to explain but I have this code: (create-context.ts) [code block] And this wrapper for creating trpc (make-trpc.ts): [code block] This works fine in @trpc/server version 10.43.2, however, when upgrading to 10.43.3 I am getting the following error: [code block] <img width="1254" alt="CleanShot 2023-11-14 at 17 05 09@2x" src="https://github.com/trpc/trpc/assets/9701896/8c9ffba8-47cb-4c7b-a592-f93bcdd1228f"> Link to reproduction https://stackblitz.com/github/trpc/examples-next-minimal-starter To reproduce Sorry wasn't able to easily reproduce it in a new repo. Additional information _No response_ 👨👧👦 Contributing - [ ] 🙋♂️ Yes, I'd be down to file a PR fixing this bug!
cli hangs on version 4.0.16
What version of Tailwind CSS are you using? v4.0.16 What build tool (or framework if it abstracts the build tool) are you using? tailwind-cli What version of Node.js are you using? 21.7.3 What browser are you using? N/A What operating system are you using? macOS Describe your issue Just noticed this on a deploy to Heroku, our normal build step for Tailwind is hanging. No issues locally until I force it to install 4.0.16 and then it just hangs. No errors. I don't see a debug or verbose output option for the cli so I'm not sure what to do to further troubleshoot. Adding `"@tailwindcss/cli": "4.0.15"` to package.json, to force a downgrade to 15, and all is well again. [code block]
hybi10 incompatibility
Please note that the latest dev Chrome has a newer version of the websocket protocol, which is incompatible with the current one. For more info: http://googlechromereleases.blogspot.com/2011/07/chrome-dev-channel-release.html
Unicode characters in s3 command: 'ascii' codec can't encode characters in position 32-33: ordinal not in range(128)
I've seen similar questions asked for different aws-cli products, and the answer always has to do with the locale, though the asker, like myself, generally has their locale in order. [code block] How can I force using a different codec instead of ascii?
Stream handling does not recognize stream errors
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 For example, when a chat completion is created like: [code block] And the underlying stream generates an error, this library will not surface the error to the application. Instead, it generates an uncaught exception error. To Reproduce See https://github.com/jsumners-nr/openai-stream-issue/tree/91e2b46b08baec3cd061a02b9492b501a353aab3 Code snippets [code block] OS macOS Node version 18.18.2 Library version 4.20.0
Official Support for ARM/Raspberry Pi Linux (armhf, arm64)
- VSCode Version: > 1.1 - OS Version: Ubuntu Mate / Linux It would be good if VS Code Supports Raspberry Pi 2/3 or provide arm binaries alongside the x86 and x86-64 binaries for linux
Allow extensions to modify terminal environment variables
Users sometimes want to set SDK paths local to their project to pin the versions of them (or to progressively move projects to the next version). There are two places where they'd want these paths to apply: 1. The extension uses it to load the correct SDK (eg. for language services, debugger, etc.) 2. In the integrated terminal Currently it doesn't seem like there's a way to provide a path once to be used for both of these purposes so the user has to set the path in two places (one in extensions settings and the other in terminal path) and keep them in sync. I thought maybe I could read the terminals path and use that when locating my SDK, but I tried this: [code block] However if I read that value from `"terminal.integrated.env.windows"` I get the literal string above without the `${env:PATH}` being resolved. Although I could resolve that myself as a special case, maybe there's a better way to handle this (like allowing the user to specify paths that will be prepended to the terminal paths that extensions could use too).