All Issues
24,993 verified issues
Missing SVG tags and attributes
Note from maintainers: Starting with React 15, we should have a complete support of the subset of SVG specifications that is actually implemented by browsers. If you find a missing attribute, or if a tag does not work correctly, please write a comment below. Note that `React.DOM.*` factory functions might not provide all tags, but you should be able to use `React.createFactory` or `React.createElement()` directly for the missing ones. Or you can just use JSX which translates to `React.createElement()` and supports all tags inherently.
Socket.IO and Windows Chrome Stuck
It stucks at "client Authorized for"
Add support for --build-args
As this docker/docker#15182 functionality has been merged, it would be great to manage with Compose I.e.: Dockerfile with default variables [code block] Overriding through docker-composer.yml [code block] Or an hierarchy of extended environments [code block]
Ability to specify which ES6 promises library mongoose uses
See discussion on #1699
NextJS navigator is not defined - azure v4 stream true
Describe the bug using last v4 server side, there is an error when calling for example chat.create here https://github.com/openai/openai-node/blob/3ec43ee790a2eb6a0ccdd5f25faa23251b0f9b8e/src/core.ts#L806 you can see code: if (!navigator || typeof navigator === 'undefined') { it is checking if it is undefined "after" trying to use it with !navigator To Reproduce calling chat.completions.create with stream true. but using it on Azure from this sample https://github.com/openai/openai-node/blob/3ec43ee790a2eb6a0ccdd5f25faa23251b0f9b8e/examples/azure.ts#L5 Code snippets _No response_ OS macOS Node version node 18 Library version v4.0.0
express 4.10.2 issue with sinon fake timers
When calling Sinon.JS's `useFakeTimers` with the most recent version of Express, requests sent to the app aren't answered. This is caused by the commit titled "Correctly invoke async router callback asynchronously", which changed line 186 of `lib/router/index.js` from `return done(layerError)` to `setImmediate(done, layerError)`. When using fake timers, functions run using `setImmediate` don't execute until one explicitly ticks forward the clock. It could be argued this isn't really a problem with Express, and rather the solution is to be sure to tick whenever one issues a request to the app. However, it's not entirely clear to me how this could be done, since one would have to know when Express got to that `setImmediate` call and only then tick. Further, even if it is possible, it's doubtful many existing tests do this, meaning this breaks a lot of existing code. Presumably this is also a problem with any other framework that manipulates `setImmediate`, not just Sinon.
Timestamps are not being created
I'm trying to add timestamps to my nested objects, but it's not working. Timestamps are being set only on the root documents (Church). Am I doing something wrong? Here's my schemas: [code block] [code block] [code block] Here's the function I'm using to insert nested documents: [code block] MongoDB: 4.4.6 Mongoose: 5.13.2 Node.js: v14.17.0
codebase
Just for my own sake: how is this different: [code block] from this? [code block] exports is already defined as module.exports, there is no need to redefine it. this call is just bad [code block] don't do that your code is so confusing. make it easier for people to understand. I won't trust the library with stuff like this.
Schema visualizer
You can use https://supabase-schema.vercel.app/ to visualize your table schemas. It would be amazing to have this in the dashboard, probably at the https://supabase.com/dashboard/project/_/database/schemas route. Looks like this original version was built with Vue. We could leverage https://reactflow.dev/ for this. If anyone is interested in working on this, reach out. We'd love to help make it happen. <img width="539" alt="CleanShot 2023-07-05 at 16 47 30@2x" src="https://github.com/supabase/supabase/assets/105593/80320545-5565-40c6-aaeb-2754b9def13a">
Unable to install Mongoose on Windows Server 2008 R2 SP1
When tried `npm install` on Windows Server 2008 R2 SP1, it gives the following messages C:\Users\someFolder>npm install mongoose- > kerberos@0.0.3 install C:\Users\SomeFolder\node_modules\mongoose\node_modules\mongodb\node_modules\kerberos > (node-gyp rebuild 2> builderror.log) || (exit 0) npm WARN optional dep failed, continuing kerberos@0.0.3 npm WARN optional dep failed, continuing kerberos@0.0.3 mongoose@3.8.8 node_modules\mongoose ├── regexp-clone@0.0.1 ├── sliced@0.0.5 ├── muri@0.3.1 ├── hooks@0.2.1 ├── mpath@0.1.1 ├── mpromise@0.4.3 ├── ms@0.1.0 ├── mquery@0.5.3 (debug@0.7.4) └── mongodb@1.3.23 > bson@0.2.5 install C:\Users\SomeFolder\node_modules\mongoose\node_modules\mongodb\node_modules\bson > (node-gyp rebuild 2> builderror.log) || (exit 0) When I run the app, I receive the following error C:\Users\Somefolder>node app.js module.js:340 throw err; ^ Error: Cannot find module 'bson' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (C:\Users\Somefolder\node_mod ules\agenda\node_modules\mongoskin\node_modules\mongodb\lib\mongodb\collection.j s:10:16) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17)
Don't reconnect after disconnection
After upgrading from 4.4.11 to >=4.6.1 we get random disconnections and mongoose never reconnects. mongoose version: 4.6.5 mongodb version: 3.2.9 This is the way I create the connections: [code block] This is the sequence of events I get: [code block] Then none of the disconnected databases reconnect. Due to the random nature of the problem, I won't be able to provide a code to reproduce it. I suspect about something saturated at node.js level or so. Independently of the cause of the disconnection, is there anything I can do to try to reconnect myself?
Switch to using hyphens as a separator in hostnames
The hostname format used by fig creates names that are not strictly valid. Current pseudo-code: [code block] This generates names like `cluster_hadoop_1`. Underscores are not valid (though in practice _most_ components are tolerant of this). Valid names should match `[a-zA-Z0-9\-]+`. I came across this error when trying to test out some hadoop/hdfs containers and hadoop bailed with an exception saying that `hdfs://flume_hadoop_1/` was not valid URI (even though it was in `/etc/hosts` and `ping flume_hadoop_1` worked just fine). See: http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names Changing this to dashes is easy, but it would break existing configurations that depend on hard coded container names.
performance issue of 4.0.0&4.0.1
After upgrading from 3.9.\* to 4.0.0&4.0.1, my node process's CPU usage increased by more than 200%. Each http request which uses mongoose costs cpu % 3 times than before. And when I downgrade back to 3.8.25, everything is OK.
TypeScript compilation errors in backend environment
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 Hello, I recently encountered several TypeScript compilation errors when using this library in a backend project. The issue primarily seems related to missing DOM types. Here are the errors I encountered when I run `tsc` command: [code block] For reference, my tsconfig.json is as follows: [code block] While adding the `dom` library to `lib` of my tsconfig.json does seem to resolve these errors, it causes references in other parts of the code to inadvertently change, leading to build failures. Furthermore, I believe that adding the dom library to a backend codebase isn't appropriate. I've verified that the problem is not related to React's StrictMode. Upon checking the openai library's tsconfig.json, I noticed it uses the skipLibCheck option, but adding that to my project's configuration did not resolve the issue. I wanted to raise this issue here to check if it's a known issue, or if there are any recommended workarounds. Any assistance or guidance would be appreciated. Thank you. To Reproduce 1. yarn add openai 2. run `tsc` on my repository 3. See error Code snippets _No response_ OS macOS Node version Node v18.4.0 Library version openai v4.8.0
Failed to export a file using drive API
I am using: - googleapis@12.3.0 - node@4.3.2 I was trying to download a spreadsheet using Drive API v3 like this: [code block] Resulting file was corrupted. Same situation with 'application/pdf' - I could not open them. After some investigation, I noticed that node-request module downloads data as string (decoded as utf8) by default unless you specify encoding option set to `null`. (what I am downloading here are binary files!) [code block] By adding a line in drive.files.export() function like below, I was able to download the file successfully: [code block] I am aware this file is generated with swig, and probably other methods (like drive.files.get with "alt" set to "media" for binary data) are suffering from the same problem, I do not have sufficient knowledge to propose most effective solution to this. I hope some one could come up with a good idea to this problem.
Rate exceeded
Description I have 8 times ${cf:..} in my serverless.yaml and I get 3 out of 5 times "Rate exceeded" while running serverless. I suppose I've reached a limit for cloudformation's API calls (DescribeStack for instance). Is there any chance to avoid this error except of increase my limits? Why doesn't serverless calls the api only once for all stacks? Or at least only once per stack? Last but not least: Which limit do I reach? I don't know which one mentiond on aws limits For bug reports: What went wrong? I run "serverless deploy -v" and I get an error "Rate exceeded" What did you expect should have happened? deploying without that error What was the config you used? [code block] What stacktrace or error message from your provider did you see? [code block] For feature proposals: What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us. If there is additional config how would it look Similar or dependent issues: #3339 Additional Data Serverless Framework Version you're using: 1.14.0 Operating System: Fedora / Linux Stack Trace: Rate exceeded Provider Error messages*:
Can not use OpenAI SDK with Sentry Node agent: TypeError: getDefaultAgent is not a function
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 Referenced previously here, closed without resolution: https://github.com/openai/openai-node/issues/903 This is a pretty big issue as it prevents usage of the SDK while using the latest Sentry monitoring package. To Reproduce 1. Install Sentry Node sdk via `npm i @sentry/node --save` 2. Enter the following code; [code block] 3. Try to create a completion somewhere in the process after Sentry has been initialized: [code block] Results in error: [code block] Code snippets (Included) OS All operating systems (macOS, Linux) Node version v20.10.0 Library version v4.56.0
Safari 5.1 Type Error Undefined Function Line 2
My socket.io application works on the latest versions of Chrome and Firefox. On Safari 5.1, though, during application load I get this error: TypeError: 'undefined' is not a function (evaluating 'j.open("GET",g)'), from line 2 of socket.io.min.js for socket.io-client. The version is 1.0.17 for socket.io and socket.io.client Note: I posted this earlier, and accidentally closed the issue. So I'm reposting it.
Module not found error on v4.5.0
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 was following the tutorial to integrate nextjs with openai and noticed that the latest release (v4.5.0) is throwing a module not found error. [code block] Maybe this is something related to this change: Important: I did a downgrade to version v4.4.0 and everything worked as expected. To Reproduce 1. Install release v4.5.0 2. `import OpenAI from "openai";` Code snippets _No response_ OS Debian Node version Node v18.17.1 Library version openai v4.5.0
Version 0.5.0 returns "Invalid argument to getAgent" on examples
I'm new to http-proxy but after running the example here: https://github.com/nodejitsu/node-http-proxy/blob/v0.5.0/examples/basic-proxy.js With some modifications (changed path of http-proxy to work in my environment) it starts but immediately throws an exception when the first client tries to connect. Is there additional setup I need to do to get it running? I am running node v0.5.0-pre according to "node --version" and just pulled http-agent from npm today (2011, April 26th). Here is the full exception: <pre>http.js:1446 throw new TypeError('Invalid argument to getAgent'); ^ TypeError: Invalid argument to getAgent at Object.getAgent (http.js:1446:11) at _getAgent (/home/tim/local/node/lib/node/.npm/http-proxy/0.5.0/package/lib/node-http-proxy.js:48:30) at [object Object].proxyRequest (/home/tim/local/node/lib/node/.npm/http-proxy/0.5.0/package/lib/node-http-proxy.js:377:12) at Server.<anonymous> (/home/tim/local/node/lib/node/.npm/http-proxy/0.5.0/package/lib/node-http-proxy.js:146:13) at Server.emit (events.js:67:17) at HTTPParser.onIncoming (http.js:1109:12) at HTTPParser.onHeadersComplete (http.js:108:31) at Socket.ondata (http.js:1008:22) at Socket._onReadable (net.js:682:27) at IOWatcher.onReadable [as callback] (net.js:177:10)</pre>