All Issues
24,993 verified issues
docker compose up recreates running container that does not have their configs changed in docker-compose.yml
Description `docker compose up` stops and recreates running containers that do not have their config changed. Steps to reproduce the issue: 1. Run `docker compose up` 2. Change config for one service in `docker-compose.yml` 3. Run `docker compose up` again Describe the results you received: A lot of containers that are not related to the service that has its config changed are recreated and restarted. Describe the results you expected: Only the container of the service that has new config should be recreated and those that depend on it should be restarted. Additional information you deem important (e.g. issue happens only occasionally): After switching to v2 it happens almost all of the time. Previously on v1 there was no such problem. Output of `docker compose version`: [code block] Output of `docker info`: [code block] Additional environment details: -
Could you replace "q" to Promise es6?
Could you replace "q" to Promise es6?
[BUG]: ER_WRONG_AUTO_KEY - Drizzle Kit not detecting primary keys
What version of `drizzle-orm` are you using? 0.28.6 What version of `drizzle-kit` are you using? 0.19.13 Describe the Bug Drizzle-kit isn't introspecting the correct primary keys from planet scale. Every push to the database causes: [code block] It's not detecting any primaryKeys that are assigned. Here is my posts table schema: [code block] From Planetscale's console using query `describe myroutepayments_posts;` [code block] Planetscale's database creation [code block] Drizzle-kit's introspection of the table: [code block] and the snapshot meta [code block] Expected behavior Introspection should be able to extract the primary keys from the database. Environment & setup On MacOS (M1), pnpm with nextjs, planet scale
prisma db push overwrites production schema without migration history
`prisma db push` is intended for prototyping — it applies schema changes directly without creating a migration file. When used in production, it can silently drop columns, rename relations, or change types without a rollback path. Many developers use `db push` in CI/CD pipelines out of convenience, not realizing it bypasses the migration system entirely.
Disabling "smart formatting" of HTML class attribute
_"We get a lot of requests for adding options, but Prettier is built on the principle of being opinionated about code formatting."_ I totally understand this, and so I apologize beforehand for opening this issue. The reason I think this is a valid issue is because the opinion about this seems to have _changed_ from the perspective of Prettier, even though it was mentioned that there's no community interest for this change (and a lot of pushback) in the introducing pull request. The issue When using frameworks like Tailwind, readability has lowered drastically since this feature: <img width="320" src="https://user-images.githubusercontent.com/1065835/117627441-13b4c680-b170-11eb-824b-d22f07456e84.png" /> References - #836345253 - #836536543 - #836652940 - #839911172 - #841662012 I'd love to still be able to use Prettier, but this is a blocking issue for me and many others. The solution Respecting the `class` attribute to stay on a single line, and only applying formatting it when a user already has a multi-line approach for `class`. Alternatively, an option to disable this feature. Thanks in advance for considering this!
[BUG] ERR! Workspaces not supported for global packages (8.5.0+)
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior After updating to 8.5.0 (and 8.5.2), I'm seeing the following when running a script that uses concurrently: [code block] Log: [code block] What is that `"prefix" "-g"` thing? Expected Behavior No errors. Steps To Reproduce 1. In Windows. 2. Using workspaces. 3. Run a script using `concurrently`. 4. See error. Environment - npm: 8.5.2 - Node.js: 16.14.0 - OS Name: Windows - System Model Name: Really? - npm config: [code block]
request.auth is null in Firestore Rules when called from Firebase JS SDK in UWP
I've discovered a problem when querying Firestore from UWP Universal Javascript project with Firebase JS SDK. Problem description Problem occurs when querying Firestore with authenticated user and Firestore Security Rules set to: [code block]` I'm always receiving: [code block]` With try and fail method I was able to find out that 'request.auth' object is 'null' in Security Rules because with following rule I'm able to successfully query Firestore: [code block]` However this Security Rule enables reading of data for everyone and stored data will not be secured. In my opinion, the problem is related to the fact that access token is not processed (therefore request.auth is null). The only difference I've found is that HTTP header is NOT 'Origin: file://' (Origin header is completely missing) and CORS headers are not set correctly set in Response (CORS header are missing, but I'm not sure if this is the reason why access token is not processed). Expected behavior Auth token should be processed and Firestore Security Rules applied accordingly. Attachements UWP Project to reproduce the error (need some Firebase Test project and Firebase user): https://1drv.ms/u/s!AjL4mBIpdvWDnYZqNkla5hHjjguGVg HTTP Request from UWP: [code block]` Javascript Console output: [code block]`
`"module": "node16"` should support extension rewriting
Bug Report TypeScript 4.7 RC introduces the `"module": "node16"` setting. When used, this requires users to use the `.js` extension in import paths. I strongly believe this to be a mistake and TypeScript should instead allow users to use the `.ts`/`.tsx` extension of the source file. It would then be the TS compiler’s responsibility to rewrite this to the output file as necessary. I have several reasons for requesting this change: - The file with the `.js` extension most likely does not exist on disk. It may exist on disk if a build has been created and the output is placed right alongside the sources (not a common configuration), but otherwise the file is simply not there or in a different place than one might expect. This is confusing to users, because they need to manually consider how output files are created. - Using the `.js` extension makes the source code less portable for full-stack projects. If a user wants to use the same sources for a frontend project that uses a bundler, they will be out of luck. A bundler would be able to understand a reference to the `.ts` file (because that one actually exists on disk!), but would struggle with references to files that do not exist for its configuration. - Using the `.js` extension makes the source incompatible with Deno projects, as they use the `.ts`/`.tsx` extensions, because those are the ones that actually exist. - Using the `.js` extension is inconsistent with type import. Does `import type { MyType } from “./myFile.j
[BUG]: Postgres Numeric Type is Inferred as Typescript String
What version of `drizzle-orm` are you using? 0.27.2 What version of `drizzle-kit` are you using? 0.19.12 Describe the Bug Given the following schema [code block] Drizzle type inferences infer the numeric column as a `string` type, when it should be a `number`. [code block] Is there any way to have the numeric column inferred as a `string`? Expected behavior numeric columns to be inferred as numbers, not string Environment & setup _No response_
[Android] CameraX preview is rotated 90 degrees
What package does this bug report belong to? camera What target platforms are you seeing this bug on? Android Have you already upgraded your packages? Yes Dependency versions <details><summary>pubspec.yaml</summary> [code block] </details> <details><summary>pubspec.lock</summary> [code block] </details> Steps to reproduce 1. Open the application 2. Confirm camera permissions 3. See improperly rotated preview Expected results The camera preview should be properly rotated. Actual results The camera preview is rotated 90º. Code sample <details open><summary>Code sample</summary> [code block] </details> Screenshots or Videos _No response_ Logs _No response_ Flutter Doctor output <details open><summary>Doctor output</summary> [code block] </details> Additional: This issue reproduces on a Pixel 1 device. I wasn't able to test this on a more capable device. The issue first occurs with the `camera_android_camerax: 0.6.8+2` if I override the dependency to: `camera_android_camerax: 0.6.7+2` everything works as expected.
Jest has detected the following 1 open handle potentially keeping Jest from exiting: CustomGC
Bug description When I run `jest --detectOpenHandles` I get the following: (Which seems to stem from the Prisma Client) [code block] How to reproduce [code block] Expected behavior There should be no open handles left over from Jest tests to prisma. There should be no open DB handles anyways since the tests are not connecting a database. Prisma information Cannot share on the given project unfortunately. Environment & setup - OS: macOS - Database: PostgreSQL - Node.js version: v16.15.1 Prisma Version [code block]
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
Hi all, I am new to react and I am trying to create a react library of components and I came across this problem because one of the components I am creating uses REACT HOOKS. Disclaimer: this is my first time creating an issue, so please bear with me. So I am trying to create an accordion component which toggles between these classes [code block] and [code block] to open and close. package.json [code block] webpack.config.js [code block] This is the accordion container: [code block] This is the accordion item that will live inside the container: [code block] Now inside of a create-react-app I import these components My library and the create-react-app are relative to each other and I am using [code block] [code block] I have followed all of these instructions and I still get the same error. Current behavior? [code block] Steps to reproduce - clone https://github.com/sethandleah/react-lib - clone https://github.com/sethandleah/myapp - [code block] - [code block] - [code block] - [code block] - [code block] - [code block] - [code block] Expected behavior - It should show a button with a "plus" svg sign and the words "Hello" and "World" respectively - Open devtools and go to elements - When clicking on the button the class [code block] should toggle To see the above, do the following: - Uncomment these lines at [code block] [code block] - The comment out these line, alse at [code block]: [code block] Versions of React, Browser / OS are affected by this
Unable to call a platform channel method from another isolate
Status 9/9/22: Work- in-progress Description When I try to invoke a platform channel method from a custom spawned isolate, the app crashes badly (both on iOS and Android). I'm trying to figure out whether this is expected or not. If it's not, it's probably worth to mention that somewhere. Anyways I think that this can potentially be a strong limitation. Is there a way to be able to call platform plugins from a secondary isolate? PRs - [x] iOS Engine - https://github.com/flutter/engine/pull/35174 - [x] iOS Framework - https://github.com/flutter/flutter/pull/109005 - [x] Reland iOS Framework - https://github.com/flutter/flutter/pull/111320 - [x] Android Engine - https://github.com/flutter/engine/pull/35804 - [x] Android Framework - https://github.com/flutter/flutter/pull/111279 - [x] Add macOS platform channel integration tests - https://github.com/flutter/flutter/pull/110606 - [x] Desktop Engine - https://github.com/flutter/engine/pull/35893 - [x] Desktop Framework - https://github.com/flutter/flutter/pull/110882 - [ ] Add samplecode - https://github.com/flutter/flutter/issues/112235 - [ ] Update website documentation - https://github.com/flutter/website/pull/7592 - [x] Make it work with plugins that require a dart plugin registrant - https://github.com/flutter/flutter/issues/112240
[ERR_PACKAGE_PATH_NOT_EXPORTED] when trying to import anything from lib/helpers
Trying to import helper into my project: [code block] Getting: [code block] Expected behavior Was able to import the helper (used to work in 0.27) Environment - Axios Version [1.1.2] - Node.js Version [16]
No retries are made after "failed to connect on first connect"
By default, mongoose throws an Error if the first connect fails, which crashes node. So to reproduce this bug, you will need the following code in your app, to catch the error and prevent the crash: db.on('error', console.error.bind(console, 'connection error:')); Now we can reproduce this bug as follows: 1. Shut down your MongoDB 2. Start up your node app that uses mongoose 3. Your app will log: `[MongoError: failed to connect to server [localhost:27017] on first connect [MongoError: connect ECONNREFUSED 127.0.0.1:27017]]` 4. Start up your MongoDB again 5. Observe that mongoose does not now connect to the working MongoDB. The only way to get reconnected is to restart your app, or to use a manual workaround. Expected behaviour: Since `autoreconnect` defaults to true, I would expect mongoose to establish a connection soon after the MongoDB is accessible again. Note: If the first connect succeeds, but the connection to MongoDB is lost during runtime, then autoreconnect works fine, as expected. The problem is the inconsistency if MongoDB is not available when the app starts up. (If this is the desired behaviour, and developers are recommended to handle this situation by not catching the error, and letting node crash, then I can accept that, but it is worth making it clear.) node v4.4.1, mongoose@4.9.4, mongodb@2.2.19, mongodb-core@2.1.4
Allow WHERE clause on joined columns.
Issue type: [ ] question [ ] bug report [x ] feature request [ ] documentation issue Hi! As it said in the documentation of `FindManyOptions#where`: > Querying a column from an embedded entity should be done with respect to the hierarchy in which it was defined. It is possible to extend this capability to the joined columns ? For exemple with 2 entities: [code block] Make a request like this: [code block] SQL: [code block] I don't have seen any other options in TypeORM documentation to apply where clauses on joined columns. If there another way I am interested about it. Thank you in advance for your help.
[Next 13] Server Component + Layout.tsx - Can't access the URL / Pathname
Edit: Please see the response and solutions here: https://github.com/vercel/next.js/issues/43704#issuecomment-2090798307
Model Update method does not respect validators
I can use the model.Update method to update to any value regardless of schema constraints For example if I have a Schema with a enum property, using update I can change to any value outside of the enum constraint, thus invalidating the set. The expected behavior was to throw an error if the updated value did not validate. I suggest an extra option to the update method to exit on the first error or not.
443 Error not found on twilio.messages.create
Hi I have a problem and I cannot find a solution. I do not know why I'm getting this error bellow: [code block] Of course, twilioError is my custom name of this object. The piece of code which I was trying to run is here: [code block] Here is also my twilio.js which I've imported to this file above: [code block] I really want to know how to resolve this. I went through all Twilio's documentation and I didn't find an explanation. Even on the first page, at the very bottom, is mentioned about possible errors on sending messages and there is no information about 443 Error. My versions: [code block] As you can see I also used firebase to deploy my app. Are there some restrictions between firebase and twilio? If someone knows what I am doing wrong or where is the problem I will be grateful for helping me. Thanks!
Not valid sdk version after upgrading Android Expo app (
I have Android Expo app (v. 2.10.0) downloaded from the Play Store. I try to run a new Expo project: [code block] Then I open the app on my device and get a blue screen with: "Something went wrong. 31.0.0. is not a valid SDK version. Options are 32.0.0, UNVERSIONED." How can I use Expo app on my device with expo project which uses < 32.0.0 expo version?