All Issues
24,993 verified issues
httpx.PoolTimeout, fixed by disabling HTTP keepalive
This is a deeply odd error, insofar as it's something that happens 100% of the time only when my code is invoking Anthropic (via client libraries 0.28.0) from our CI environment (hosted in AWS us-east-2). We get a `anthropic.APITimeoutError: Request timed out`, thrown from a `httpx.PoolTimeout`, thrown from a `httpcore.PoolTimeout` during a generally unremarkable test case. The following change in usage/invocation prevents it entirely: [code block]
[k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-prod-parallel/2086/ Failed: [k8s.io] Network should set TCP CLOSE_WAIT timeout {Kubernetes e2e suite} [code block]
Cannot read property 'protocol' of undefined
README has this example for custom application logic (for caronte tree): [code block] I'm getting these errors: [code block] I am running node v0.10.20.
Support looking for modules under node_modules when importing
Update 5 November 2015 The functionality requested below is currently implemented in typescript since at least 1.8 with one main difference: Instead of having `typescript.main` and `typescript.definition` properties, there is only one `typings` property which you can point to either a `d.ts` file or a normal `.ts` file. If you're developing a module to just use locally, you can have the `typings` point to a `.ts` file, but if you plan to publish the module, it is recommended to have it point to a `d.ts` file. This is because you don't want your module consumers to recompile your module files, just consume its typings. I have setup an example of using this here: https://github.com/chanon/typescript_module_example There is a documentation page here that has more information: http://www.typescriptlang.org/docs/handbook/typings-for-npm-packages.html Thank you TypeScript devs and all contributors. Original issue / feature request follows --- Motivation In TypeScript it is a lot harder to re-use typescript modules compared to re-using npm modules in JavaScript. It would be beneficial if the typescript compiler is smart enough to look in node_modules folders and package.json files. The reason is so that npm module developers that use TypeScript might be able to start writing and distributing modules through npm itself. TypeScript would be able to piggyback on npm's infrastructure and wide support. Example for node_modules If we had: [code block] And in index.ts
Adding extra_headers for the anthropic web-fetch tool causes the structured_output example to fail
Adding the `extra_headers` and `tools` options in the`messages.create` call causes the call with `output_format` to fail. I am using version 0.75 of the sdk. I took the example from here: https://platform.claude.com/docs/en/build-with-claude/structured-outputs#quick-start and added these two options in the create call [code block] This causes the example to fail with this error [code block] Are these options incompatible with structured output. I'm not sure this is an sdk error or an error in the api itself, please close if not appropriate.
nodejs.RangeError: Maximum call stack size exceeded when use hmset
when hmset get too much args(i passed 163368 args),it will report `nodejs.RangeError: Maximum call stack size exceeded`
Implement Sideways Data Loading
This is a first-class API for sideways data loading of stateless (although potentially memoized) data from a global store/network/resource, potentially using props/state as input. [code block] observe() executes after componentWillMount/componentWillUpdate but before render. For each key/value in the record. Subscribe to the Observable in the value. [code block] We allow onNext to be synchronously invoked from subscribe. If it is, we set: [code block] Otherwise we leave it as undefined for the initial render. (Maybe we set it to null?) Then render proceeds as usual. Every time onNext gets invoked, we schedule a new "this.data[key]" which effectively triggers a forcedUpdate on this component. If this is the only change, then observe is not reexecuted (componentWillUpdate -> render -> componentDidUpdate). If props / state changed (i.e. an update from recieveProps or setState), then observe() is reexecuted (during reconciliation). At this point we loop over the new record, and subscribe to all the new Observables. After that, unsubscribe to the previous Observables. [code block] This ordering is important since it allows the provider of data to do reference counting of their cache. I.e. I can cache data for as long as nobody listens to it. If I unsubscribed immediately, then the reference count would go down to zero before I subscribe to the same data again. When a component is unmounted, we automatically unsubscribe from all the active subscriptions. If the new
anthropic[vertex] has missing `requests` dependency
I install anthropic[vertex] [code block] Then write this code: [code block] It is running into the following exception: [code block] Looks like google-auth needs requests library: https://github.com/googleapis/google-auth-library-python/blob/3fae8f8368d4651cd11d4af3d80f687eab033175/google/auth/transport/requests.py#L28 google-auth defined "requests" extra: https://github.com/googleapis/google-auth-library-python/blob/3fae8f8368d4651cd11d4af3d80f687eab033175/setup.py#L33 But anthropic[vertex] uses plain google-auth dependency: https://github.com/anthropics/anthropic-sdk-python/blob/a3c59fc77610122a302aec1e7a2a59bbce94dbb2/pyproject.toml#L39
openai-node v3.2.1 createImageEdit() endpoint stopped working
Describe the bug I've been using openai-node v3.1.0 and openai.createImageEdit() worked well. I updated to the v3.2.1 to support the createChatCompletion() method, however my createImageEdit() is not working anymore. I get Error: Request failed with status code 400. If i downgrade to 3.1.0 is starts working back. Has createImageEdit() been changed in the latest update, so my call does not satisfy the new api? will add a code snippet wtih my method which works in v3.1.0 but doesn't in v3.2.1 <img width="567" alt="Screenshot 2023-03-03 at 12 40 49" src="https://user-images.githubusercontent.com/55192345/222686888-ee00c984-2d88-46df-8f8b-ba8bbddd6e65.png"> To Reproduce 1. update from v3.1.0 to v.3.2.1 2. call createImageEdit (implementation provided in snippets section) Code snippets [code block] OS macOS Node version v18.7.0 Library version 3.2.1
Mac support
I get an error when I ran `make`: [code block] Also I saw this line does this mean that mac is not supported?
expo-notifications FCM V1 Migration Tracking Issue
This is a tracking issue for user-reported issues related to the Spring 2024 migration of Expo Push Notifications from FCM Legacy to FCM V1 for Android devices. There have been reported instances of brokenness in production when moving from FCM Legacy to FCM V1, and this issue will serve as a central place to track our investigation and resolution of these issues. Recommend that users should now be on `expo@51.0.24` and `expo-notifications@0.28.15` or later. The remaining issues (as of 2024-08-06) are as follows: - Issues with channel ID and vibration pattern not being set correctly in notifications - Status: In progress - ENG-12759 and ENG-12770 - Vibration pattern issue being fixed in https://github.com/expo/expo/pull/30495 - Channel issue is being worked in #30762 - Issue with custom sound not working when app in background - Status: Investigating - https://github.com/expo/expo/issues/27978 and ENG-12780 - Issue with complex remapping of notification payload on Android FCMv1 - Status: Investigating - https://github.com/expo/expo/issues/30533 Fixed issues: - null `data` payload in client when receiving push notifications - See https://github.com/expo/expo/pull/28938 - handlers are not being called when app is backgrounded - See these comments from @douglowder - handlers are being called when app is foregrounded, but app resets itself (seen in development build, unconfirmed in production) - Notification icon not working - See https://github.com/expo
vector_eq raises ERROR instead of returning FALSE. Is that intended behavior?
Hi all, vector_eq() calls CheckDims() first, raising an ERROR if the compared vectors have different sizes. Since pg_vector supports vectors of variable size, this causes problems. In this case, vector_eq() should return FALSE, not throw an ERROR. This also throws ERRORs when doing a VACUUM ANALYZE. Is that intended behavior? best regards Ernst-Georg
TypeScript types are invalid when expanding responses
Describe the bug When expanding responses as per the documentation here, the return types for various Stripe methods are not updated to accurately reflect the modified responses. To Reproduce [code block] Expected behavior The returned data does indeed contain a nested `subscriptions` object: [code block] However, the TypeScript types do not declare this at all. Code snippets _No response_ OS macOS Node version Node v16.4.2 Library version stripe-node v10.8.0 API version 2022-08-01 Additional context _No response_
TypeScript - Property 'plan' does not exist on type 'Subscription'
Describe the bug The property `plan` is not accessible on `Subscription` objects when used in TypeScript. The `plan` property is, however, present in the `Subscription` object To Reproduce 1. Create an instance of `Stripe` 2. Request a `Subscription` object 3. Try to access the `plan` property Expected behavior For the `plan` property to be accessible Code snippets _No response_ OS Ubuntu 22.04 Node version Node v18.12.1 Library version stripe-node v12.5.0 API version 2022-11-15 Additional context The documentation for the `Subscription` object also does not list the `plan` property, and several others <https://stripe.com/docs/api/subscriptions/object>
router.use middleware is called twice
Node Version 12.22.3 Express Version 4.17.1 Platform Darwin 3655368-6357e 18.7.0 Darwin Kernel Version 18.7.0: Tue Jan 12 22:04:47 PST 2021; root:xnu-4903.278.56~1/RELEASE_X86_64 x86_64 Subsystem _No response_ What steps will reproduce the bug? app.js [code block] router.js [code block] Dependencies axios 0.23v express 4.17.1v Please install the above dependencies. Run node app.js Open browser http://localhost:3001/v1/food How often does it reproduce? Is there a required condition? For every long running request I see the request triggered multiple times. In the browser i see single request, i saw logs twice as below. Set timeout 0 URL request for ---> / Set timeout 0 URL request for ---> / What is the expected behavior? I expect single log and the middleware should run once. For a single request matching middleware should execute once not twice. Expected log Set timeout 0 URL request for ---> / What do you see instead? _No response_ Additional information _No response_
Canot call method 'split' of null
After recent upgrade my tests break: [code block]
`Cannot GET //socket.io/socket.io.js` when using Express, Socket.io and node-http-proxy
The following gist produces a `socket.io/socket.io.js 404 (Not Found)` error on the browser's side: https://gist.github.com/4324446 This gist does not reproduce that error: https://gist.github.com/4324576
Support Import Assertions
https://github.com/tc39/proposal-import-assertions [code block] Vite should support import-assertions because it has entered stage 3.
constructEvent is not working in the example
im using the provided example https://github.com/stripe/stripe-node/tree/master/examples/webhook-signing to check the sign (without changing any code, but just put the correct secret here is my test body that grep from the webhook request `{ "id": "evt_1HI8Y3G18iuNs10OgnHen3OH", "object": "event", "api_version": "2020-03-02", "created": 1597909859, "data": { "object": { "id": "pi_1HI8Y3G18iuNs10OOPlF55v4", "object": "payment_intent", "amount": 21000, "amount_capturable": 0, "amount_received": 0, "application": null, "application_fee_amount": null, "canceled_at": null, "cancellation_reason": null, "capture_method": "automatic", "charges": { "object": "list", "data": [], "has_more": false, "total_count": 0, "url": "/v1/charges?payment_intent=pi_1HI8Y3G18iuNs10OOPlF55v4" }, "client_secret": "pi_1HI8Y3G18iuNs10OOPlF55v4_secret_fBJ4VKg0NttX3X5wbN1BHmfoL", "confirmation_method": "automatic", "created": 1597909859, "currency": "hkd", "customer": null, "description": "Order #: SMY1597909859", "invoice": null, "last_payment_error": null, "livemode": false, "metadata": {}, "next_action": null, "o
4.40.0 -> 4.40.1: Breaking change - OpenAI is not a constructor
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 Based on numbers, 4.40.1 is supposed to be a bug fix release over 4.40.0, so I didn't expect something to break. I have not tested the application after 4.40.1 to see if anything else is broken. const openai = new OpenAI({ ^ TypeError: OpenAI is not a constructor To Reproduce Code saved as test.js: [code block] [code block] Code snippets _No response_ OS WSL Ubuntu 24.04 LTS Node version v20.12.2 Library version 4.40.1