All Issues
24,993 verified issues
Allow hiding schema fields when calling toJSON
This is a feature request to allow hiding of a schema field when converting the document into json. I'm not sure if it would be better if this was set from inside the schema declaration or from the toJSON call, e.g. [code block] or something like [code block]
[Bug] Invalid types in last update
Some of the changes in the following commit define types don't match the actual structure of the data causing type errors when attempting to access values as documented. For example, `lineTypeIntelligence: Record<string, object>` suggests that the shape would be: [code block] It should probably instead be `Record<string, any>`. Or, even better, it should contain the actual available keys and value types as documented. https://github.com/twilio/twilio-node/commit/49f3f2b147818bf03d0067ad7cc13fbcbaf72c7d#diff-55a60b51b684465835a0448f6efceb0ef9b0cb5ada598728e1594ebf2507deddR292
Convert populate to use $lookup
Before: [code block] After: [code block] Can we normalize this functionality for population using `aggregate` and `$lookup` into a rewrite of the `populate` function (so it would still function the same, but it'd use `$lookup` instead?
createTranscription() doesn't work as expected in NodeJS
Describe the bug Hi! I tried to follow the documentation when I was writing a transcription script using NodeJS. And I wanted to get a response in .srt format. But it returns an error. I tried to use the argument `response_format` as well as `responseFormat()`. But that didn't work. Also, there is only one way to communicate with OpenAI API: [code block] But anyway, it doesn't work if I would like to specify the output file format. To Reproduce 1. Run the function (one of them) 2. Get `Required parameter model was null or undefined` error Code snippets [code block] [code block] ``` OS macOS Node version Node v.16.13.0 Library version openai v.3.2.1
[Vulnerability] patch axios vulnerability CVE 2023 45857
Issue Summary Current version of axios used by the library has a vulnerability. https://security.snyk.io/vuln/SNYK-JS-AXIOS-6032459 I see a few PRs open for this already, but it is not being addressed. https://github.com/twilio/twilio-node/pull/971 https://github.com/twilio/twilio-node/pull/970 Steps to Reproduce 1. Install latest twilio-node dependency 2. Run snyk/github security scan Code Snippet [code block] Exception/Log [code block] Technical details: twilio-node version: 4.8.1 node version: v18.16.0
The global variable `--tw-transform` is not defined in base
What version of Tailwind CSS are you using? v3.0.7 What build tool (or framework if it abstracts the build tool) are you using? tailwindcss-cli 3.0.7 What version of Node.js are you using? v16.13.0 What browser are you using? Chrome What operating system are you using? macOS Reproduction URL https://play.tailwindcss.com/iVIJhwfSBR – Funny thing here: `--tw-transform` gets directly added to `div:after` and there is no global definition of that variable. Maybe v3.0.1 is the reason for that 😕 Describe your issue Edit: It seems like this relates to https://github.com/tailwindlabs/tailwindcss/pull/6500 I am using web components which import a shared CSS file that only contains `@tailwind base`. When trying to use transform utilities I can also see `transform: var(--tw-transform);`. The problem is that the variable is not defined since that does not live in Tailwind base: [code block] Is it possible that we get this moved like the other globals like shadows or content? [code block] [code block] Thank you!
TS7030: Not all code paths return a value
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 building using `tsc` with `openai` as a dependency, I get the following error: node_modules/openai/src/lib/AbstractChatCompletionRunner.ts(224,28): error TS7030: Not all code paths return a value. I also had to disable the `noImplicitAny` rule since `openai` is not built, and then my app build inherits your source code basically. To Reproduce `const OpenAI = require('openai');` and build with `tsc` (Ideally, I would like this to be an automated test for this library, so build errors do not repeat.) Code snippets _No response_ OS macOS, ubuntu Node version Node 18 Library version 4.15.1
iOS fails to run on version 0.72.1, 'react/debug/react_native_assert.h' file not found on RunLoopObserver.cpp (React-utils)
Description I get the error: 'react/debug/react_native_assert.h' file not found, React-utils/RunLoopObserver. This is my Podfile: [code block] { "name": "POK", "version": "0.0.1", "private": true, "scripts": { "postinstall": "patch-package", "android": "react-native run-android", "ios": "react-native run-ios", "lint": "eslint .", "start": "react-native start", "test": "jest" }, "dependencies": { "@react-native-async-storage/async-storage": "^1.19.0", "@react-native-clipboard/clipboard": "^1.11.2", "@react-native-community/blur": "^4.3.2", "@react-native-community/netinfo": "^9.4.1", "@react-native-firebase/analytics": "^18.1.0", "@react-native-firebase/app": "^18.1.0", "@react-native-firebase/crashlytics": "^18.1.0", "@react-native-firebase/messaging": "^18.1.0", "@react-navigation/bottom-tabs": "^6.5.8", "@react-navigation/native": "^6.1.7", "@react-navigation/native-stack": "^6.9.13", "@react-navigation/stack": "^6.3.17", "axios": "^1.4.0", "buffer": "^6.0.3", "card-validator": "^8.1.1", "expo-modules-core": "^1.5.4", "fbjs": "^3.0.5", "isomorphic-webcrypto": "^2.3.8", "js-base64": "^3.7.5", "lodash": "^4.17.21", "lodash.compact": "^3.0.1", "lodash.every": "^4.6.0", "lodash.pick": "^4.4.0", "lodash.values": "^4.3.0", "lottie-ios": "3.4.1", "lottie-react-native": "^5.1.6", "moment-timezone": "^0.5.43", "patch-package": "^7.0.0",
Incremental Streaming vs Culimative Streaming
I noticed that Anthropics APIs use cumulative streaming in the completion endpoint, resulting in repetitive data being sent over the wire. Is there a reason for this design choice? I imagine Incremental streaming is typically preferred for efficiency. I see this is on the endpoint and not a python or ts issue. so this could impact existing customers.
[BUG]: Splitting database schemas into a separate package in monorepo causes TS2345 Property `[IsDrizzleTable]` is missing in type
What version of `drizzle-orm` are you using? 0.29.0 What version of `drizzle-kit` are you using? 0.20.4 (but not relevant) Describe the Bug 1. Copy/paste the example drizzle adapter code from https://github.com/nextauthjs/next-auth/blob/693a0723a7bad2b0950e4c6006a99c98852c4beb/packages/adapter-drizzle/src/lib/pg.ts into my own project 2. Note that the example code works (leave aside the deprecated `primaryKey(col1, col2)`, which I fixed). 3. My project is a monorepo, so the database schemas (which were in Prisma) are in a separate package. Move the table definitions for `users`, `accounts`, `sessions`, and `verificationTokens` into a separate package, where `tsc --build` is producing a `dist/` folder and `package.json`'s `exports` references `dist/index.d.ts` etc., then import the table definitions in the original `app` package which is making the `insert` calls. 4. Receive the following error: `TS2345` and `Property [isDrizzleTable] is missing in type`: the compiled `.d.ts` looks like this: Expected behavior Not to have the `tsc` error. I expect the types to be portable. Environment & setup I use a monorepo with `pnpm` and `syncpack` and have confirmed that both the main `app` package and the database schema package are using the same `0.29.0` version of `drizzle-orm`.
fetch is not exported from 'openai/_shims/fetch'
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 I am getting the following error when trying to instantiate my OpenAI client. [code block] To Reproduce Instantiate openAI with the following: [code block] Code snippets The OpenAI definition in my package.json is `"openai": "^4.2.0"` My `tsconfig.json` file: [code block] ``` OS macOS Node version v20.2.0 Library version 4.2.0
LINQ-style query builder
First I'd like to say this is an Impressive framework! Back on topic, I assume you have considered a more functional (rather than string-based) querying mechanism (like LINQ to SQL). What are the limitations and/or difficulty of implementing something like that?
[BUG] NPM v7 private registry authentication 401 (v6 works)
Current Behavior: While trying to install packages from GitHub package repository, I get 401 error when using npm v7 (tried with 7.3 and 7.4.2) while it's working with v6 (6.14.11) Full error: [code block] My `.npmrc` is as follows: [code block] Seems very similar to #2183 Expected Behavior: Packages are successfully installed Steps To Reproduce: Do `npm install` with npm v7, packages hosted in GitHub packages registry and `.npmrc` as mentioned above Environment: Happens to me both on macOS and in several Linux versions inside - OS macOS 10.15.7/ Debian stretch - Node: 15.5.1 - npm: 7.4.2
UnhandledPromiseRejectionWarning: Error: Connection is closed. event_handler.js:115:25
Some users of my project which is using ioredis current version (npm latest) got: [code block] On my host the line number lead me to [code block] Is there abug on your side? I'm not that fit in Promises and stuff. Thank you having a look.
Changing query parameter issue
I am hoping I can get some direction on this. Initializing the io with io(url,opts) works with the query parameter. If that query parameter needs to change you can dot into the sio.io.opts object. However, after it is changed that way, it is not able to be changed again. Iteration 0 - Works On Initialization <code> socket = io(options.socket,{query: {_accessToken: 'cow'} }); </code> Server's socket.request._query._accessToken returns 'cow' Iteration 1 -Works When changed the first time <code> socket.io.opts.query._accessToken = 'moo'; </code> Server's socket.request._query._accessToken returns 'moo' Iteration 2 - Doesn't work anymore <code> socket.io.opts.query._accessToken = 'twomoos'; </code> Server's socket.request._query._accessToken returns 'moo'' Although it seems to change on the client side, the server still returns the value of the access token in Iteration 1. Doing some digging, I found that the <code> socket.io.engine.transport.ws </code> contains the URL for the request, but keeps the _accessToken as the iteration 1 variable. <code> ws://192.168.1.8/socket.io/?_accessToken=moo&transport=websocket&sid=mY9rC4km7ASypgDTAAAI </code> I can't change the variable using javascript because it still stays the same. That also seems rather hacky and I'd like to not do that. I haven't put in an issue request for anything, so I hope this counts as a legitimate one.
☂️ Improving Codegen
Description > Note: The items in this list are eligible for Hacktoberfest (https://hacktoberfest.com/). All the accepted PRs under this umbrella task will be tagged with the hacktoberfest-accepted label, to count toward your score.:tada: Hi everyone! This is an umbrella issue to collect a set of tasks aimed to improve the code in the react-native-codegen package. Codegen is a pillar for the New Architecture and is part of the core developer experience. We believe that everyone would benefit from a clear and maintainable codebase, hence this umbrella issue to help us cleanup and restructure some of its components. The codegen internals Codegen work with a 2-steps process: 1. It parses a set of JS-based specifications and it creates a JSON Schema. 2. Starting from the Schema, it generates a set of Native files in various languages: Java, Objective-C++ and C++. Codegen package is divided in three high-level folders: 1. cli => it contains a set of scripts to use the Codegen from a Command Line Interface. 2. generators => it contains a set of file which generate the final code. 3. parsers => it contains a set of files to parse Flow and TypeScript specifications. The first step of this imrpovement effort will focus on the Parsers. Parsers The parsers folders contains subfolders to parse Flow and TypeScript specs. The two folders have a very similar structure: a components folder, where there is the logic to parse Native Components specs a modules folder, where there i
unusual behavior when proxying websocket to socket.io
I'm not really sure how to explain so I whipped up some code to demonstrate. https://gist.github.com/967964 please run that, then open 3 (console-supporting) browsers at http://localhost:8000 (i hope to find something to simulate in the future) hit send in each (you may need to modify node-http-proxy to not change headers) console will log msgs rcvd from server. then open 3 more browsers at http://localhost:9000 (no proxy) hit send in each notice the output is different. also, the server output is different. when proxied, messages are duplicated for client X depending on the number of clients connected after X. also, connections disconnect after some time when proxied while they remain open indefinitely when not proxied. [code block]
npm ERR! Failed to parse json
Hello there, I'm trying to install npm express on window(window 10) system. It give me error. [code block] I'm also use 'npm cache clean' but not able to install npm express on window 10. Please revert me as soon as possible.
Add a way to avoid printing the finalContent when using runFunctions
Confirm this is a feature request for the Node library and not the underlying OpenAI API. - [X] This is a feature request for the Node library Describe the feature or improvement you're requesting I have a routine that prints alphabet A-Z. One function prints one letter at a time. The problem is that OpenAI SDK also outputs the entire alphabet _again_, at the end. Is there a way that would force it to return early without bothering with producing the final output? [code block] Here the last `console.log` will print something along the lines of: [code block] I tried tapping into `.on('finalFunctionCall', ...` event, but that happens after `finalContent()` already has a result. I really just need some sort of event that fires before it starts generating the final output, so I could abort early. The example uses alphabet listing, which is quick. But in real-world scenario, that final content function can a long time/many tokens to generate.
AWS Elasticache + TLS + Hostname Verification
Tested Using Node.js v10.13.0 ioredis v4.2.3 AWS Clustered Redis Elasticache (3 nodes, in-transit and at-rest encryption enabled) Problem When connecting to a Redis cluster, a list of nodes (`host` and `port` combinations) are given. In the cluster connection logic, the list of node hostnames are then resolved to IP addresses. For the nodes that have successfully had hostnames resolved to IP addresses, the logic then overwrites the given `host` for that node with the resolved IP address. Normally this would not be an issue, but when connecting to a Redis cluster via TLS (such as AWS encrypted Elasticache) this can cause issues with Node.js' built-in TLS hostname verification. Basically, if the IP address of the node does not appear in the certificate received from the server, then the hostname verification step will fail causing the connection to fail. Example Running the following code: [code block] ran with `DEBUG=ioredis: node index.js` produces the following logs: [code block] where `clustercfg.xxx.use1.cache.amazonaws.com` is the cluster hostname and `aaa.bbb.ccc.ddd` is the IP address the hostname resolves to. Note the following debug log message: [code block] Workaround My current workaround is to bypass the TLS hostname verification step with a custom `checkServerIdentity` function: [code block] Additional Notes I also experimented with changing part of the cluster connection logic (`resolveStartupNodeHostnames`) so that it does not overwrite the