All Issues
24,993 verified issues
How to add A custom reponse object type?
How can I makemy response object of a custom type?
kubernetes-soak-continuous-e2e-gke: broken test run
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-soak-continuous-e2e-gke/8059/ Multiple broken tests: Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} [code block] Issues about this test specifically: #26982 Failed: [k8s.io] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} [code block] Issues about this test specifically: #29816 #30018 Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} [code block] Issues about this test specifically: #26784 #28384 Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} [code block] Issues about this test specifically: #28220 Previous issues for this suite: #28514 #30157
How to share the connection pool across multiple databases
In node-mongodb-native, I can share the connection pool across multiple databases: <code> var mongodb = require("mongodb"), mongoserver = new mongodb.Server(host, port, server_options), db_connector = new mongodb.Db(name, mongoserver, db_options); db_connector.open(callback); </code> And then I use <code>db_connector.db(name)</code>, this returns a new db instance that shares the connections off the previous instance but will send all commands to the database name . This allows for better control of resource usage in a multiple database scenario. HOW CAN I DO THIS IN MONGOOSE?
Bug with @VirtualColumn not being returned correctly
Issue description @VirtualColumn not being returned correctly Expected Behavior [code block] It was expected that @VirtualColumn would return the correct values according to the logic defined in the decorator. [code block] Actual Behavior [code block] DNS column is not being returned [code block] Steps to reproduce 1. Add the @VirtualColumn decorator to an entity or class. 2. Define the expected logic for the virtual value. 3. Observe the obtained result. My Environment | Dependency | Version | | --- | --- | | Operating System | windows 10 | | Node.js version | 18.18.0 | | Typescript version | 5.3.3 | | TypeORM version | 0.3.19 | Additional Context _No response_ Relevant Database Driver(s) - [ ] aurora-mysql - [ ] aurora-postgres - [ ] better-sqlite3 - [ ] cockroachdb - [ ] cordova - [ ] expo - [ ] mongodb - [ ] mysql - [ ] nativescript - [ ] oracle - [X] postgres - [ ] react-native - [ ] sap - [ ] spanner - [ ] sqlite - [ ] sqlite-abstract - [ ] sqljs - [ ] sqlserver Are you willing to resolve this issue by submitting a Pull Request? Yes, I have the time, and I know how to start.
errors should inherit from the Error object
currently twilio errors are represented as a dictionary: [code block] it would be better if errors inherited from the Error js object. there are a few reasons for this: - Error objects have stack traces, which help you nail down where they originate - makes it possible for someone to throw a Twilio error (currently a dictionary). the JS behavior for throwing/catching non-Error objects is wonky at best and handling varies by library - mocha, raven-node behave oddly when you're using them without an Error object. It would be pretty straight forward to add considering there is already a `message` property on the object.
CI Status Thread
The bot will post _here_ when a rolling build (rather than a triggered PR associated build) fails; simply subscribe to this thread for updates.
No results when using index
I have a table of quotes with vector embeddings. There are two columns in the table, one is indexed one is not, they are otherwise identical. When I query against the unindexed column for the 5 nearest neighbors to a given embedding, I get 5 results. However, when I run the same query using the indexed column I get no results. [code block] Produces: [code block] But changing to use the indexed column, embedding2, in the order by clause, and setting the probes parameter [code block] Returns no results. How can using an index in an order by clause lead to no results being returned? This is entirely reproducible, so if there is any debugging I can do to help diagnose the issue, let me know.
Wildcard in route parameter regexp
Route `'/:username([a-z][a-z-])'` Route `'/:username([a-z][a-z-])/:project([a-z][a-z0-9-])'` URL `/someone/project` Expectation is that the second route should match. Actual result is the first route matches because the \ is considered as all the things rather than "zero or more" `[a-z-]`.
Xcode 16.3 and SDK 52 / React Native 0.76
Update April 3, 2025 from @brentvatne This issue is resolved. See: https://github.com/expo/expo/issues/35807#issuecomment-2776278963 <hr /> Summary After updating Xcode, running a React Native with expo app results in a build error. First, there’s a warning about a Hermes script that runs during every build because it doesn’t specify output dependencies. Then, while compiling some files, an error occurs in string_view:300:42, related to the instantiation of an undefined template (std::char_traits<unsigned char>). This seems to be caused by an incompatibility between the Xcode version, the iOS SDK, and React Native libraries. [code block] What platform(s) does this occur on? iOS SDK Version 52.0.18 Environment [code block] Minimal reproducible example npx expo install expo-dev-client npx expo prebuild npx expo run:ios
Error reporting in production
We've been using Sentry to log errors in our server-side rendering and client-side. Unfortunately, the error message that React throws in production mode is pretty useless, so we wind up with a lot of unactionable reporting. React has two levels of errors—warnings (those logged to the console) and errors (the ones that are thrown)—but both are enabled/disabled using the same env var/compile option. It would be really great if there were two different options so that I could reap the benefits of disabling warnings (e.g. from runtime type checking) without losing meaningful error messages (for example, from checksum violations). Thanks!
HTML TODOs
This issue tracks HTML issues that should be done before the public release. --- Please take a look at #5259, which should address this issue. --- Try out the current experimental HTML support: [code block] or preview playground in #5135. --- | icon | description | |-|-| | ✔️ | merged | | 👀 | in review | | 🔜 | #5259 | | 🏃 | WIP | --- Features - [x] support front matter - #5110 - [ ] support pragma - 🔜 - [x] unambiguous/XHTML-compatible output for void tags (e.g., `<br />`) (reason) - #5116 - [ ] html in js template literal (comment) - 🔜 - [x] whitespace-sensitive formatting (comment) - #5168 - [ ] recognize CDATA (comment) - 🔜 - template languages - [ ] format interpolation `{{ js expression }}` (comment) - 🔜 - ~~maybe support bracketSpacing?~~ (no, it's not supported in JSX) - Angular - [ ] format attribute binding syntax (`*ngIf`, `[target]`, `(target)`, `[(target)]`) - 🔜 - [ ] format inline template (``@Component({ template: `html` })``) - 🔜 - Vue - [ ] format attribute binding syntax (`:class`, `v-if`, `v-bind:id`, `@click`) - 🔜 Bug fixes - [x] ~~exclude comments from fragment detection~~ (outdated) - #5100 - [x] remove extra trailing newline for `<template>` (repro) - #5127 - [x] add missing trailing newline for `<style>` (repro) - #5111 - [x] preserve HTML entities - ~~#5119~~ #5127 - [x] preserve case-sensitive tags - #5101 - [x] preserve case-sensitive attributes - #51
[expo-screen-orientation] Screen orientation does not lock or trigger with EAS Build
Summary On a built app with EAS build, calling https://docs.expo.dev/versions/latest/sdk/screen-orientation/#screenorientationlockasyncorientationlock does not trigger the screen to rotate and lock on iOS. When the app isn't built with EAS build, and created with expo build, the screen orientation lock async function works. Could possibly be related to: https://github.com/expo/expo/issues/11558 Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? iOS SDK Version (managed workflow only) 43 Environment Expo CLI 4.12.10 environment info: System: OS: macOS 11.6 Shell: 5.8 - /bin/zsh Binaries: Node: 14.15.1 - ~/.nvm/versions/node/v14.15.1/bin/node Yarn: 3.0.2 - ~/.nvm/versions/node/v14.15.1/bin/yarn npm: 6.14.8 - ~/.nvm/versions/node/v14.15.1/bin/npm Watchman: 2021.06.07.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.2 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 30, 31 Build Tools: 29.0.2, 30.0.2, 31.0.0 System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-31 | Android TV Intel x86 Atom, android-31 | ARM 64 v8a, android-31 | Intel x86 Atom_64, android-31 | Google TV Intel x86 Atom, android-31 | Google APIs ARM 64 v8a, androi
Express more tests via public API
This is a great contribution opportunity. We need to rewrite more unit tests in terms of public API. This means that they can only import npm entry points like `react`, `react-dom`, `react-dom/test-utils`, `react-test-renderer`, etc, but not internal modules like `SyntheticEvent` or `ReactDOMComponentTree`. The “bad” requires are already marked with a TODO in tests so you won’t miss them. To help with this: 1. Find `// TODO: can we express this test with only public API?` in the unclaimed test files below. 2. Comment in this issue if you want to take a particular unit test file, with its name. 3. Submit a PR that rewrites the test to use public APIs instead. Step 3 requires some thinking. You can use previous examples where we rewrote tests with public API for inspiration. For example: https://github.com/facebook/react/pull/10429 https://github.com/facebook/react/pull/10281 https://github.com/facebook/react/pull/9080 https://github.com/facebook/react/pull/8148 Generally, you need to think about how the behavior you’re testing actually reproduces in a React app, and then test for that. In rare cases it may involve exposing some API as public which we’ll need to discuss separately, so don’t hesitate to start a discussion! If you can’t figure out how to rewrite some particular test with a public API, comment here and we can brainstorm. Here is the full list of tests that need to change. Some of them may be simple one-liner changes, some may involve a bit of a rewrite,
[Discussion] The future of the browser package
This discussion started in PR #837 @pleerock: "What do you think if we simply remove all drivers (except websql, sqljs) for browser package? And probably stub them somehow elegant? Same with advanced console logger, maybe remove that too? And do same for ionic/cordova?" It would be great to have a package that includes the SystemJS and TypeScript version so that it can be either used in a SystemJS project or retranspiled for a different module loader I like the idea from @pleerock to only include the needed drivers (websql, cordova, sqljs - at some point) but I'm not sure who replacing or stubbing them would work. The way it is done right now with the PlatformTools class is fine for that one file but is going to be a nightmare to maintain if it is done for multiple files/all drivers. Same would apply to creating a reperate repository. Is there a better way to maybe generate mocks automatically?
A Cookie `maxAge` of `undefined` causes incorrect behavior.
In `lib/response.js` in `res.cookie()` some assumptions are made that the incoming `maxAge` option will always be a number. However, if `maxAge` is set to `undefined` through some process, `opts.maxAge /= 1000` returns `NaN`. `maxAge` should be verified and/or coerced to be numeric.
Drop support for Node < 4
We've supported Node.js versions 0.10 and up for a while now. We didn't want to move off of it until the Node.js ecosystem solidified. This would mark the second time we've end-of-lifed support for an older version of Node.js, the previous being when we dropped 0.8 (#734). We'd like to start using Node.js 4 so we can start writing ES6 and enable as many ES6 rules as possible on our code base (dogfooding rules yields a lot of problems). The question is: should we do this sooner or later? It seems like a lot of people have been moving to Node.js 4 (or 5) and 0.10 and 0.12 installations are disappearing as a result. We don't want to leave people out in the cold, but we also don't want to wait forever. <bountysource-plugin> Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Importing & using AssistantStream breaks Angular SSR
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 Just by adding the following lines in my new Angular project, I get an error. Lines: [code block] On compiling the code I get the following error: [code block] Now I'm unsure whether or not this is something you guys can fix, or it should be somehow reported to Angular or the polyfill... but I thought I'd start here, because I really have no clue what's going on. The internals of the AssistantStream are somewhat beyond me and I have no experience with handling streams in Typescript. Feel free to close this issue and report it to the right place - or I can do it with the right info. To Reproduce 1. Install Angular normally with [code block] As part of the installation prompts, choose to use SSR 2. Add this lib [code block] 3. Change the app.component.ts to include the openai AssistantStream [code block] 4. Run angular and watch it crash [code block] Code snippets [code block] OS Linux Mint Node version 20.9.0 and 22.1.0 Library version 4.51.0
Websockets dont work with a router
I'm not sure if this is a bug or not but websockets wont work with a proxy table e.g [code block] It works fine proxying web requests. But websockets don't work. If I access the site directly it does work (with websockets) I also unsuccessfully tried adding in [code block] It also looks like `server.on('upgrade` doesn't fire. In addition, even without the above event. If there are attempts to use websockets (after a while). The below error will appear: [code block] After a while it will run out of memory and crash.
Error with Prisma v15: can't find prisma.schema
I updated to prisma version 15 and when I run prisma2 generate in a docker environment, I receive the error: [code block] I don't see that the filename has been changed from `schema.prisma` to `prisma.schema` so this seems like a bug.
socket.emit inside socket.on function
Note: for support questions, please use one of these channels: stackoverflow or slack You want to: [ ] report a bug [x] request a feature Current behaviour invoke a socket.emit inside a socket.on function does not work. (see code below) ` socket.on('notification', function (data) { socket.emit('news', { hello: 'world' }); });` Steps to reproduce (if the current behaviour is a bug) Server side, emit a message from inside a "socket.on" method. Expected behaviour Message sent to client Setup - OS: Archlinux - browser: Firefox - socket.io version: 1.7.2 Other information (e.g. stacktraces, related issues, suggestions how to fix)