All Issues
24,993 verified issues
Kaspersky antivirus breaks Firestore ("Could not reach Cloud Firestore backend.")
UPDATE [by @mikelehen 2018/10/21]: This issue has morphed into specifically being about the Kaspersky antivirus software blocking Firestore. Please open a separate bug if you're encountering issues without Kaspersky. Environment Operating System version: Windows 10 Browser version: Chrome 68.0.3440.106 Firebase SDK version: 5.4.2 Firebase Product: store Problem Im using Firestore with Ionic (Angularfire2 package). Any collection or doc gives error but after ~10 seconds it gives data. Auth works without any problems. Error: [code block] Created new Firebase Project and new Ionic project, installed packages, tried to make collection, shows same error. [code block] The code im trying to run: [code block] And the console output: [code block]
[BUG]: Drizzle keep removing and re-adding a unique index with multiple fields
Report hasn't been filed before. - [X] I have verified that the bug I'm about to report hasn't been filed before. What version of `drizzle-orm` are you using? 0.38.2 What version of `drizzle-kit` are you using? 0.30.1 Other packages _No response_ Describe the Bug I notice that the command `drizzle-kit push` can remove and recreate the unique index over and over again if I used multiple fields and not in the right order. In the repo below, the following will recreate each run: [code block] But the following won't: [code block] Seems like something in the ordering of the columns confuse the script. Use the following code to test it: https://github.com/moshest/drizzle-unique-bug/tree/main Best way to verify is to add a single row to the table and then get the warning about truncating the table each time.
Node v4.0.0 - Build failing
When installing socket.io latest with node V4.0.0 (stable), the following build failure occurs. [code block] This is obviously a compilation problem with upstream packages on `utf-8-validate` and `bufferutil`, never-the-less a release will need to be made with their subsequent releases. I will be adding tickets in these two projects as a result and reference this ticket.
Weekly community hangout
In the interest of collaboration and transparency I'd like to propose a short open online meet-up perhaps once a week for anyone who is working on Express issues/pull requests to share their plans, progress and thoughts on what they are working on. I would suggest a Google Hangout and a scrum format (what have you been working on? what are you going to work on? are you blocked?) plus questions/any other business. Suggestions for alternatives welcome. To start the ball rolling on a time/date, how about: a 10-30 minute hangout on Tuesdays at 5:30pm EST / 10:30pm GMT. Feedback and expressions of interest welcome in this thread.
Project package.json contains vulnerable version of jsonwebtoken
Issue Summary jsonwebtoken v9 has been released to address vulnerability found in 8.51 and lower. Steps to Reproduce Look at the package.json Suggest updating twilio dependency to 9 so users of twilio can keep the package and avoid security warning messages. Resource: https://unit42.paloaltonetworks.com/jsonwebtoken-vulnerability-cve-2022-23529/
`@trpc/next` with `ssr: true` breaks `getServerSideProps`
> Notes by @KATT: > > - Solving this is blocked by https://github.com/vercel/next.js/discussions/28183. > - Keeping this open for visibility, but it likely won't be fixed. > - See warning-block at https://trpc.io/docs/ssr --- `@trpc/next`: 8.0.0-alpha.6 Using: [code block] Any page with `getServerSideProps`, for example: [code block] Will receive undefined props, then get refreshed with props (the latter usually never executes due to errors using undefined) Removing `withTRPC` hof stops this behavior.
Engine Exited on GCR (Google Cloud Run)
Getting this error on Google Cloud Run, after redeploy it works again. Is there still some issue with serverless?
Not getting the conference logs with twilio client when conference is created by dial() fn
Issue Summary I am not able to see the conference I just created using the dial() function. I need this so I can grab the conference sid off of it to make another outbound call with twilio client. But the ironic thing is that the conference I create using dial() appears in the conference logs on twilio's website. Another weird thing... The only time I am able to see conference logs using twilio client is when I create the conference through twilio client. Steps to Reproduce 1. Create Conference using twiml 2. Try to get the status of that conference using twilio client Code Snippet [code block] Technical details: twilio-node version: node version:
Specific font family setting breaks Expo go [SDK 51]
Minimal reproducible example https://github.com/SenadAlagic/expo-bug-repro What platform(s) does this occur on? iOS Did you reproduce this issue in a development build? Yes Summary As many people who transitioned to SDK 51 it didn't go smooth on my project but issues are to be expected. I ran into the issue of the app crashing and looked around and found this issue: https://github.com/expo/expo/issues/28618 which I thought was everything I needed, it described my issue perfectly and I thought that would be the end. I followed everything that was said here and still when I boot up my app on an iOS simulator it crashed immediately, BUT when I run it on my physical Android phone it works fine. I decided to strip it down and see what exactly is the cause of the issue. For some reason the issue seems to be in specifying the font-family of a Text component (default react-native's). Now, in the interest of shortening the repro I didn't assign the values "properly", the IDE does complain but the app does build and it crashes.(just pointing out that I don't have these issues and errors in my app, this is not how I change font family of text) I attributed those crashes to the new SDK version and the issue from the before mentioned GitHub issue link but this doesn't appear to be the issue with Reanimated (?). Anyways, I hope this repro is of use to you guys and I hope we can figure what exactly is the issue here. Thank you so much for your time! Steps to reproduce 1. clone
aws: Allow rolling updates for ASGs
Once #1109 is fixed, I'd like to be able to use Terraform to actually roll out the updated launch configuration and do it carefully. Whoever decides to not roll out the update and change the LC association only should still be allowed to do so. Here's an example from CloudFormation: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html How about something like this? [code block] then if there's such policy defined, TF can use autoscaling API and shut down each EC2 instance separately and let ASG spin up a new one with an updated LC.
Latest dayjs version causes exception in client.messages.create()
Issue Summary Calling client.messages.create() using version 1.11.7 of dayjs throws an exception as shown below. Downgrading to version 1.11.5 resolves the issue. Steps to Reproduce 1. send a message using client.messages.create() as shown in the code snippet Code Snippet [code block] Exception/Log [code block] Technical details: twilio-node version: 4.11.0 dayjs version: 1.11.7 * node version: 18.15.0
Prisma CLI installation hangs indefinitely inside of docker (Kernel 5.10)
Bug description @prisma/cli installation hangs indefinitely inside of docker How to reproduce REPRO: https://github.com/svelters/prisma-poc Expected behavior It should install without container discrimination Prisma information `@prisma/cli` version: "2.15.0" Environment & setup - OS: Linux - Docker (alpine, debian etc...) - Database: doesn't matter - Node.js version: 15.6.0 but it seems to fail on any version we tried - Prisma version: doesn't matter as it fails because of the cli
Wrong `PromptAttributes` interface implementation
Issue Summary Right now I'm following the docs to use `Pay.Prompt` noun but there is a problem while using TypeScript. The interface includes the following: [code block] And as we can see the attribute is `for_` (with the `_`) and inside the docs: https://www.twilio.com/es-mx/docs/voice/twiml/pay/prompt#for It's `for` only (without the `_`), if we try to use `Pay.Prompt` like the following: [code block] It throws an error: `Argument of type '{ for: string; }' is not assignable to parameter of type 'PromptAttributes'.` So, we need to use `for_` but the Twilio parser does not detect `for_`. Another thing is that it looks like the docs are also out of date: The errorTypes are: [code block] And there is no `invalid-postal-code` for example when the current docs state that it is actually there. Maybe it could be another good idea to add the usage of the errorTypes inside the docs? so we know it's an array and how to use it with `cardType` could be really useful. Steps to Reproduce 1. Create a Twilio Serverless function 2. Add TS support 3. Use the `Pay` verb 4. Add the `Prompt` noun support Code Snippet [code block] Exception/Log [code block] Technical details: twilio-node version: ^3.80.0 twilio/runtime-handler: ^1.25.0 node version: 16.16.0 typescript: 4.0.0 ts-node: 10.7.0 @types/node 17.0.21 Workaround: There is a workaround by adding `// @ts-ignore` above the line like: [code block]
GraphQL Error Swallowed Natively but works in Express-graphql
Using Graphql 0.13.2 Executing graphql natively as follows through AWS Lambda: index.js - calls [code block] If the executing code throws an error, it usually returns message as string with [object, Object]. I suspect it wraps to GraphQLError. If I wrap the above error object using GraphQLError then I do not get anything back and my response.errors is an empty object {}. The only way I am able to get back data properly is to return an Error as a string or a GraphQLError as a string, I am unable to push back an object. Oddly enough if I run GraphQL with express and add the formatError with an error handler then that works, however using it natively it does not. It seems that I am missing something simple to get GraphQL to return the object instead of only working with strings. Any ideas?
Umbrella issue for v1.0.0
Summary This issue is an umbrella for the next release of axios. We might add more issues to the `issues to fix` list. Pull Requests [x] Babel & Webpack 3 [x] ESLint shared config (standard) [x] Migrate nodeunit to jasmine [x] Karma with Webpack config [x] Adjust specs to work with new lib interface [x] Substitute custom utils with lodash [ ] Move core / adapters to ESM [ ] Move helpers to ESM [ ] Remove lodash helpers from utils [ ] Move cancel module to ESM [ ] Change external surface Issues to fix Build system - [x] https://github.com/axios/axios/issues/1209 - [x] https://github.com/axios/axios/issues/1259 Utils: - [x] https://github.com/axios/axios/issues/1298 Default instances / Config merge: - [x] https://github.com/axios/axios/pull/533 - [x] https://github.com/axios/axios/issues/1239 - closed in favor of #385 - [ ] https://github.com/axios/axios/issues/1237 - [ ] https://github.com/axios/axios/issues/812 - [ ] https://github.com/axios/axios/issues/369 - [ ] https://github.com/axios/axios/issues/723 - [ ] maybe https://github.com/axios/axios/issues/498 - [ ] https://github.com/axios/axios/issues/385 - [ ] https://github.com/axios/axios/issues/382 - [ ] maybe https://github.com/axios/axios/issues/370 - [ ] https://github.com/axios/axios/issues/369 - [ ] https://github.com/axios/axios/issues/809 - [ ] https://github.com/axios/axios/issues/688 - [ ] https://github.com/axios/axios/issues/587 - [ ] https://github.com/axios/axios/issues/1042 Proxy: - [
Is there a Rust SDK?
I couldn't find one, so I'm making one, based on this. Let me know if one already exists, and/or you're interested. Thanks!
ClusterAllFailedError on version 4.24.1
Hey! We're using ioredis with our AWS ElastiCache cluster running 3 shards on version 5.0.5. We're making the redis calls through a lambda with quite high traffic, meaning multiple concurrent lambdas running. I've done some version bumping and I'm seeing the error `ClusterAllFailedError: Failed to refresh slots cache` intermittently. Through some debugging I've narrowed version 4.24.1 to be the culprit - any version before that works fine. When setting `DEBUG=ioredis:*` in the lambda env the `ClusterAllFailedError: Failed to refresh slots cache` is in most cases followed by these logs: [code block] When looking at the 4.24.1 commit https://github.com/luin/ioredis/commit/8524eeaedaa2542f119f2b65ab8e2f15644b474e I can tell that code related to this error has been touched - could this fix have introduced unintended issues? Any pointers would be appreciated :+1:
Add wildcard support for events
It would be great if you could use a wildcard to capture all events. For example: [code block]
[NEXT-1186] revalidatePath not working for dynamic routes while res.revalidate works fine
Verify canary release [X] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] Which area(s) of Next.js are affected? (leave empty if unsure) App directory (appDir: true) Link to the code that reproduces this issue https://github.com/roxizhauk/revalidate-path CodeSandBox To Reproduce Visit `/blog/[anything]` (e.g. `/blog/test` ) to generate a dynamic page and check the time shown To try "unsuccessful" app directory's `revalidatePath`: 1. hit `/api/revalidate-path?path=/blog/[anything]` and you'll see "revalidated" 2. refresh `/blog/[anything]` and you'll see the time not changed To try "successful" pages directory's `res.revalidate`: 1. hit `/api/revalidate?path=/blog/[anything]` and you'll see "revalidated" 2. refresh `/blog/[anything]` and you'll see the time changed Describe the Bug The app directory's `revalidatePath` works fine for "/" or "/blog" but dynamic routes like "/blog/1" or "/blog/test" while pages directory's `res.revalidate` works fine for all Expected Behavior `revalidatePath` works the same as `res.revalidate` for dynamic routes Which browser are you using? (if relevant) No response How are you deploying your application? (if relevant) No response* <sub>From SyncLinear.com | NEXT-1186</sub>
[Question] Prettier Philosophy and Rationale printWidth
I am opening an issue just to get an information about one decision, not related to a specific code formatting rule, but about a core concept in prettier : the `printWidth` option. First of all, I really love prettier and the philosophy ! I configured it in all projects in my company and I am using it every day ! But....why, in 2018, are we talking about `printWidth` when we talk about formatting ? Are you still printing your code ? Are you all using the same screen resolution/scale ? If it's about removing horizontal scroll, the best option is to use a “soft wrap” setting/plugin in your editor...it will break your line visually and it will adapt this automatically if you reduce the width of your editor. The philosophy of prettier is to define a common way to format your code and stop debating... Why this common way is impacted by a printWidth ? For example, sometimes, my JS array is formatted in one line and sometimes in multiple lines just because of the printWidth….this is not a common way to format arrays…It should be even more strict than that: put my array in one line all the times and I'll soft wrapping if it's too long or...split my array in multiple lines all the times * or...format my array in one line if it contains one element and split my array in multiple lines if it contain more than one element all the times Maybe I completly misunderstanding the philosophy of prettier but I feel that the `printWidth` is not matching it. What do you think ?