All Issues
24,993 verified issues
Publish 4.19.1?
Need to pick up the axios security update.
[iOS][Facebook] Not redirecting back to app after Facebook.logInWithReadPermissionsAsync through facebook app
🐛 Bug Report Environment [code block] iOS Standalone AND iOS Expo Client Steps to Reproduce Must be logged out of Facebook in the browser, but logged in in the Facebook app Facebook.logInWithReadPermissionsAsync, doesn’t come back to our app after flying to Facebook app. This may or may not occur. For now it only occurs on iOS standalone. It’s pretty strange because it’s quite strange behavior and it hurts user acquisition opportunities. This is fatal for our app. Expected Behavior After logging in with Facebook, you are redirected to our app and the login process is executed Actual Behavior Even after logging in on the Facebook app, it behaves like staying in the Facebook app. The only way to get back to our app is to cancel, and of course the login process will fail. Sample code [code block]
[Feature Proposal] Coloured Box Shadow
Heya, I think it'd be neat if box shadows worked with colour variations. I tried to reach for it for a hover state and really wished it was there.
Do not insert whitespaces between latin and cj letters
Environments: - Prettier Version: 1.18.2 Steps to reproduce: [code block] Expected behavior: [code block] Actual behavior: [code block] *** For now, Prettier inserts whitespace between latin and Japanese/Chinese on formatting Markdown. As mentioned in #5938, this is not good behavior for Japanese, but correct for Chinese. I tried to avoid this problem in the same way as handling Korean language, but it was impossible because Japanese and Chinese uses same Kanji letter, with same char code. From above reason, I think we should add new option like `add-whitespace-between-latin-and-cj` to determine whether whitespace is inserted between latin and cj. Of cource it's the best if there is the way to distinguish Japanese and Chinese.
why socket.disconnect() on client side doesn't fire disconnect event on the server?
here's my code: <p style="color:red;"> client-side</p> [code block] server-side: [code block] the socket.disconnect() method doesn't work why?
Add support for database views
Problem In a database, a view is the result set of a stored query on the data, which the database users can query just as they would in a persistent database collection object. Unlike ordinary base tables in a relational database, a view does not form part of the physical schema: as a result set, it is a virtual table computed or collated dynamically from data in the database when access to that view is requested. Changes applied to the data in a relevant underlying table are reflected in the data shown in subsequent invocations of the view. Prisma does not currently support database views. Suggested solution No suggestion. Alternatives The current workaround available is to manage views manually and query views by using the raw SQL API. ~Or use the documented workarounds https://www.prisma.io/docs/guides/database/advanced-database-tasks/sql-views-postgres or https://www.prisma.io/docs/guides/database/advanced-database-tasks/sql-views-mysql but make sure to read the "Limitations" section properly!~ Alternatively you can treat a "fake model" to your Prisma schema that has the same structure than the view results. Note that future Introspection might drop this "model" and future Migrations might try to create a table of that name - so make sure to handle that. Additional context Frameworks like Ruby on Rails don't support views out of the box, but there are 3rd party libraries available (scenic for Rails). Original issue >Prisma 2 init doesn't print MySQL views into
React Hook useEffect has a missing dependency: 'xxx' ?
Hi, I am researching React Hook recently, it's great. But I have a problem, I did not find a suitable answer in the React Hook documentation and google to solve my problem. When I used a function in useEffect and function component together, I encountered a warning that I did not specify a dependency in useEffect, as shown below: Is there any way to solve my problem? I have thought about it for a long time. What is the current behavior? [code block] Mini repro in codesandbox: https://codesandbox.io/s/trusting-kowalevski-oet4b Any solution, thanks. Code [code block]
Use MongoClient.connect() instead of authenticate() if user provides URI to avoid Db.prototype.authenticate deprecated
I'm using a connection method like : [code block] ... as indicated in the docs, but receiving the following warning on NodeJS console : [code block] (I get an authentication failure if I omit `?authSource=admin`) Is this normal at this stage (do we need to wait for a next mongoose release ?), or what should I change from now ? Versions : Node : 7.10.0 Mongoose : 4.10.3 MongoDB : 3.4 Thank you.
Next.js 14 build fails: useSearchParams() must be wrapped in Suspense boundary
Running next build fails with: "useSearchParams() should be wrapped in a suspense boundary at page /search". Any page that calls useSearchParams() at the component root without a Suspense wrapper causes the entire build to fail in Next.js 14 App Router.
auth.signIn() with magic link creates users in Auth.users table
Bug report Describe the bug Using magic link feature to login creates the user if the email provided doesn't exist on Auth.users table. To Reproduce 1. Use this snippet to login with magic lik `const { user, session, error } = await supabase.auth.signIn({ email: 'example@email.com' })` 2. Use an email that doesn't exist on Auth.users table 3. Check Auth.users table Expected behavior If the email provided is not in Auth.users table it shouldn't be created and an error should be thrown.
[Bug] (Create React App) Issues with resolving an .mjs file instead of an .js file leading to test failures
Running tests on a local project get's the following errors since the publish of 0.13.1 [code block]
cannot get cross-site POST to work
Hello, Thanks for the great work. Although that were some releases targeting cross-site requests, I still can't get it to work. I dug through the previous posts and tried adding: - crossDomain: true - xDomain: true *xDomainRequest: true to the config. And none of them worked. (If this feature is actually available, updating the readme would help.) Please advise ASAP. Thank you.
Buttons have cursor: pointer by default, but should not for accessibility reasons
What version of Tailwind CSS are you using? 3.1.6 What build tool (or framework if it abstracts the build tool) are you using? Vite 3.0.0 (rollup) 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://stackblitz.com/edit/react-tailwind-qds1vc?file=index.js Describe your issue While it's common to give `<button>`s `cursor: pointer;`, this is an anti-pattern. The CSS spec establishes that `cursor: pointer` indicates an element is a link. This article has some additional justification for this. I understand many users will want to override this behavior back to the common misuse of `cursor: pointer;`, but Tailwind should be correct by default.
Hydration performance issue on complex dataset
Issue type: [X] question [ ] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [X] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` TypeORM version: [ ] `latest` [ ] `@next` [X] `0.2.6` *Steps to reproduce or a small repository showing the problem: Hi, we have a performance issue in hydration for a (quite) complex query like this: [code block] This generates a SQL query like the following: [code block] The SQL query in our development database takes approximately 32ms and returns a raw resultset of approx 4400 rows, as you can see it's very fast. On the other hand the hydration process takes approx 4500ms running inside an hi-end Intel I7 CPU. Have you any clues why the hydration process takes so long ? Could be something related to the entities config ? Thanks in adavnce for your help, Leonardo
AxiosError: unexpected end of file
Describe the bug AxiosError: unexpected end of file Was not present before 1.2.1 To Reproduce _No response_ Code snippet _No response_ Expected behavior _No response_ Axios Version 1.2.1 Adapter Version _No response_ Browser _No response_ Browser Version _No response_ Node.js Version _No response_ OS _No response_ Additional Library Versions _No response_ Additional context/Screenshots _No response_
1.2.0 transformResponse
Describe the bug When upgrading from `1.2.0-alpha.1` to just `1.2.0` the config `transformResponse` sends data as binary instead of string. To Reproduce _No response_ Code snippet _No response_ Expected behavior _No response_ Axios Version _No response_ Adapter Version _No response_ Browser _No response_ Browser Version _No response_ Node.js Version _No response_ OS _No response_ Additional Library Versions _No response_ Additional context/Screenshots _No response_
Also Add Password Changing Guidelines
Improve documentation Link https://supabase.com/docs/guides/self-hosting/docker Describe the problem When password is changed like for postgres in .env , It causes an error when started again `docker compose up -d` , there is no mention of fixing that or any passwd changing guidelines. Describe the improvement After many hours i found out you need to `docker compose down -v` and also `rm -rf volumes/db/data/` sometimes. Then `docker compose up -d` to change it without error.
[BUG]: drizzle-orm@0.30.10 not working with react@18.3.1
What version of `drizzle-orm` are you using? 0.30.10 What version of `drizzle-kit` are you using? _No response_ Describe the Bug react@"18.2.0" is marked as the peer dependency Expected behavior the package should be installed with no problem :) Environment & setup _No response_
ioredis left open handles in Jest
Hello. I can't resolve the issue with my Jest tests because of ioredis. Recently I started recieving messages after Jest finished all tests: > A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --runInBand --detectOpenHandles to find leaks. After a few days of struggling I found the module called leaked-handles, installed it and started debugging. And it seems like both `redis.quit()` and `redis.disconnect()` not working and connection remains opened after those calls. The error is: [code block] I couldn't find any mentioning of `ioredis` at Jest repo and viceversa. Is there anything that can be done to close connection properly?
Express v4 -> v5 Migration
Copied from my comment in the Release 5.0 PR: Maybe I missed a v5 planning document somewhere - I'm looking for a few details to help determine how and when to migrate our projects: 1. When is it planned that `express@5.0.0` be published to the npm `latest` tag? 2. Is there a plan to publish an Express v4 -> v5 Migration Guide? (or a visible list of breaking changes with short suggestions about what to do about them) The closest thing that I can see is this small `breaking` note in `History.md`) 3. What's the current plan for the TypeScript types in DefinitelyTyped `@types/express` and `@types/express-serve-static-core`? Does anything need to be changed here? Specifically, things like https://github.com/DefinitelyTyped/DefinitelyTyped/pull/69660#issuecomment-2179358937 cc DT maintainers @borisyankov @samijaber @NatoBoram @bombillazo @AndrewLeedham @gabritto @sandersn