All Issues
24,993 verified issues
When new Xcode build system is used, Xcode build fails to download third-party dependencies
Workaround (edit by @hramos) You may work around this by manually installing third party dependencies into your project. The following steps are based on the workaround provided by @lyon007 in #14382. 1. ` rm -rf node_modules/ && yarn cache clean && yarn install` and ` rm -rf ~/.rncache` 2. ` cd node_modules/react-native/scripts` 3. `./ios-install-third-party.sh` If your network is slow, you can download the packages separately and move them to the `rncache ` folder _1_. folly-2016.10.31.00 _2_. double-conversion-1.1.5 _3_. glog-0.3.5 _4_. boost_1_63_0 4. `cd <Your-Project-Folder>/node_modules/react-native/third-party/glog-0.3.5` 5. ` ../../scripts/ios-configure-glog.sh` 6. Xcode Clean & Build Original issue - [x] Review the documentation: https://facebook.github.io/react-native - [x] Search for existing issues: https://github.com/facebook/react-native/issues - [x] Use the latest React Native release: https://github.com/facebook/react-native/releases Environment React Native Environment Info: System: OS: macOS High Sierra 10.13.6 CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz Memory: 103.23 MB / 4.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 10.9.0 - ~/.nvm/versions/node/v10.9.0/bin/node npm: 6.4.0 - ~/.nvm/versions/node/v10.9.0/bin/npm SDKs: iOS SDK: Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0 IDEs: Xcode: 10.0/10L221o - /usr/bin
Prisma Migrate: Error creating shadow database
Problem Users run into this issue if their database user has no privileges to create databases (MySQL / Postgres). This happens because Migrate tries to create a shadow database under the hood. [code block] Some of the situations where this might be the case: Running DBMS locally but user has insufficient privileges -> Possible resolution: grant privileges. We should improve the user-facing error and document this properly Using a cloud-hosted DB for development, where creating additional databases is probably not supported -> Possible resolution: make the shadow DB URL configurable Additional context * Slack conversation with user on Heroku
UnableToResolveError: Unable to resolve module `AccessibilityInfo`
Description I basically just cloned an existing project with a minimal setup, did `yarn install` and `node node_modules/react-native/local-cli/cli.js run-ios`. It started but the packer failed with: [code block] I found `get AccessibilityInfo() { return require('AccessibilityInfo'); },` in the `/Users/phillipp/Work///node_modules/react-native/Libraries/react-native/react-native-implementation.js` file but I have no clue where it wants to require that from. It seems to be a RN core thing. Here is the `package.json` for those who are curious: [code block] I already tried everything I found on the internet (reinstalling node modules, cleaning npm, yarn and watchman caches, deleting react files from temp dir, etc.) Additional Information React Native version: `^0.44.0` Platform: `ios` Development Operating System: OSX Dev tools: XCode Version 8.0 (8A218a)
PostgreSQL: add `generated always as identity` as modern alternative to `serial`
It's basically the newer (and recommended) way to make auto incrementing columns. Example: [code block] You can read about the benefits of using the new implementation on this StackOverflow post
Support for nested maps in variables
I'd love to be able to do this: [code block] Currently, you'd get an error like `Variable 'amis': must be string or mapping`
Placing operators at the beginning of lines
Prettier 1.10.2 Playground link [code block] Input: [code block] Output: [code block] Expected behavior: [code block]
Error: RepositoryNotFoundError: No repository for [Enitity] was found. Looks like this entity is not registered in current "default" connection?
Issue type: [x] question [x] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [x] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [ ] `latest` [ ] `@next` [x] `0.2.8` (or put your version here) Steps to reproduce or a small repository showing the problem: 1. Create my entity: import {Entity, PrimaryColumn, Column, BaseEntity} from "typeorm"; [code block] 2. Create my method: [code block] 3. Test with: `mocha --require ts-node/register './*/.test.ts' --recursive` Then, it throws that error. But also, it occurs not every time. Sometimes, the code can run well three or four times and then throw that bug next time. I don't really know what the cause is as I took that code from another of my projects in which it was and is working just fine.
service account with owner rights has insufficient permissions
Hello, I finally managed to make a successful api call with this npm package; `publisher.inappproducts.list({ ...` returns the expected result and everything is great. But when I go for: [code block] It always returns the same error: The current user has insufficient permissions to perform the requested operation. Assuming that: - The current user is a service account with the highest possible permissions granted in both the developer console and the google play console. (including "view financial data") - The project in the google developer console is linked to the app in the google play console. - The `packageName`, `subscriptionId` and `token` parameters sent are valid. What could possibly be missing? Is a refresh_token needed with service accounts? Could there be discrepancy between the permissions shown in the UI and the actual permissions granted to the service account? Does the service account need to "accept" the invitation to be a "owner"? Is there a way to list the service account's permissions through the API? Here is the code I use for authentication: [code block] Environment details - OS: OSX 10.14 (Mojave) - Node.js version: 8.11.4 - npm version: 5.6.0 - `googleapis` version: 34.0.0 Thanks for making it down here.
[0.60.2] Build failing when enabling Hermes (enableHermes: true)
Build is failing when I enable Hermes in android/app/build.gradle Error: React Native version: System: OS: macOS 10.14.5 CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Memory: 71.63 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 10.15.1 - /usr/local/bin/node Yarn: 1.13.0 - /usr/local/bin/yarn npm: 6.4.1 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2 Android SDK: API Levels: 23, 24, 25, 26, 27, 28 Build Tools: 21.1.2, 23.0.1, 25.0.0, 25.0.1, 25.0.2, 26.0.2, 26.0.3, 27.0.3, 28.0.0, 28.0.2, 28.0.3, 29.0.0 System Images: android-23 | Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-27 | Android TV Intel x86 Atom, android-27 | Intel x86 Atom, android-27 | Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64 Android NDK: 20.0.5594570 IDEs: Android Studio: 3.4 AI-183.6156.11.34.5522156 Xcode: 10.2/10E125 - /usr/bin/xcodebuild npmPackages: react: 16.8.6 => 16.8.6 react-native: 0.60.2 => 0.60.2 npmGlobalPackages: react-native-cli: 2.0.1 react
Watch code and automatically rebuild when something changes
Compose could watch your code and automatically kick off builds when something changes. This would mean: - Code can be reloaded automatically regardless of language. This would also make code reloading work on compiled languages if that was part of the build process! - Volumes are no longer needed in development - Production server can be used in development (e.g. gunicorn can be used to serve Django apps in development) It could either be an option to `up` (`docker-compose up --watch`), an option in the config file specifying directories to watch/ignore, or perhaps a separate command (`docker-compose watch`). Thanks to @samalba for the suggestion!
Increase max vectors dimension limit for index
Hello ! I'm wondering what are the reasons for the maximal dimension limit for indexes HNSW and IVFFlat. Checking _really quickly_ the code, I see those `HNSW_MAX_DIM` and `IVFFLAT_MAX_DIM` constants set to 2000 which seem arbitrary to me, as a non-educated user. - Why do we have these limits ? - How would performance scale if the limited were, say, doubled ? - Is there a plan to increase the limits, considering other vector database products offer up to 32768 dimensions (or even more) for indexed vector ? Thank you !
Performance Issues with React Native Bridgeless Architecture
Description The Bridgeless Architecture in React Native 0.74 and later introduces significant performance issues, particularly for apps with complex logic and high demands for UI responsiveness. Here are the main concerns: Key Issues 1. Screen Load Times - Problem: Synchronous communication with the native runtime slows down screen loading, particularly when multiple API calls are made. - Impact: Initial loads are bottlenecked, reducing overall app responsiveness. 2. UI Responsiveness and Touch Lag - Problem: The switch to synchronous communication impacts touch response, causing a laggy and less fluid user experience. - Result: Reduced interaction quality and increased user frustration. 3. Lazy Module Loading - Default Behavior: Bridgeless architecture loads modules lazily by default, contributing to delayed responses in complex pages. - Partial Fix: Disabling lazy loading improves response slightly but doesn’t fully solve the underlying delay issues. Comparative Performance with Older Versions - Testing Results: - React Native 0.71.8 (asynchronous bridge): Modal with 32 API calls loads in approximately 3 seconds. - React Native 0.74.x / 0.76.1 (bridgeless): Modal with only 14 API calls takes over 10 seconds. Attempts to Improve Performance - Native Threads & Configuration Adjustments: Shifting API calls to native threads, and enabling/disabling options like Hermes and New Architecture, failed to yield significant performance improvements. Call for Optimization
Poor performance as part of a webpack PostCSS build system
Using the latest Tailwind CSS (1.8.13 as of this writing), I'm seeing slowness very similar to https://github.com/tailwindlabs/tailwindcss/issues/1620 & also https://github.com/tailwindlabs/tailwindcss/issues/443, the performance of using HMR with `webpack-dev-server` and webpack 4 or 5 is quite slow. It takes about 10 seconds on my MacBook Pro 2019 just changing a single color in a `.pcss` file, and it appears externally that it's rebuilding everything each time. The building of Tailwind CSS seems to have gotten slower and slower as the amount of utilities it includes have gone up. I'm not sure what the caching implemented in 1.7.2 does, but in a long running process (and maybe it's already doing this but) what if all of the Tailwind-specific imports like: [code block] ...were cached in a long running process, so it just returns the pre-generated blob? I'd imagine you're probably already doing this, but have any instrumentation or profiling been hooked up to the build to determine where the bottlenecks are? My postcss.config.js looks like this: [code block] ...and the whole setup is essentially what's here: https://nystudio107.com/blog/an-annotated-webpack-4-config-for-frontend-web-development#tailwind-css-post-css-config It's not doing anything fancy re: the PostCSS part of the build, but its extremely slow compared to the HRM of JavaScript modules, etc. I tried removing `postcss-preset-env` to see if it made a difference, but it doesn't seem to. Related: https://
A way to hide certain expected changes from the "refresh" report ("Objects have changed outside of Terraform")
After upgrading to 0.15.4 terraform reports changes that are ignored. It is exactly like commented here: https://github.com/hashicorp/terraform/issues/28776#issuecomment-846547594 Terraform Version [code block] Terraform Configuration Files <!-- Paste the relevant parts of your Terraform configuration between the [code block]terraform resource "aws_batch_compute_environment" "batch_compute" { lifecycle { ignore_changes = [compute_resources[0].desired_vcpus] } ... compute_resources { ... } } resource "aws_db_instance" "postgres_db" { ... lifecycle { prevent_destroy = true ignore_changes = [latest_restorable_time] } } [code block] Note: Objects have changed outside of Terraform Terraform detected the following changes made outside of Terraform since the last "terraform apply": module.db.aws_db_instance.postgres_db has been changed ~ resource "aws_db_instance" "postgres_db" { id = "db" ~ latest_restorable_time = "2021-05-25T10:24:14Z" -> "2021-05-25T10:29:14Z" name = "db" tags = { "Name" = "DatabaseServer" } (47 unchanged attributes hidden) (1 unchanged block hidden) } module.batch_processor_dot_backend.aws_batch_compute_environment.batch_compute has been changed ~ resource "aws_batch_compute_environment" "batch_compute" { id
Support having plugins as dependencies in shareable config
My shareable config uses rules from an external plugin and I would like to make it a `dependency` so the user doesn't have to manually install the plugin manually. I couldn't find any docs on this, but it doesn't seem to work, so I'll assume it's not currently supported. [code block] I assume it's because you only try to load the plugin when the config is finished merging. Other shareable configs that depend on a plugin instructs the users to manually install the plugin too and they have it in `peerDependencies`. I find this sub-optimal though and I don't want the users to have to care what plugins my config uses internally. The whole point of shareable configs is to minimize boilerplate and overhead, so this would be a welcome improvement. <bountysource-plugin> Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Missing documentation for downloading binary files
I had to do a lot of trial and error, until I found out that adding "responseType" as "arraybuffer" would do the trick.
Workflow level `env` does not work properly in all fields.
Describe the bug When using workflow level environment variables they do not work when I use them to substitute for `jobs.build.name` or `jobs.build.runs-on`. See workflow file below for example: [code block] To Reproduce Steps to reproduce the behavior: 1.- Run the workflow file above to receive the following error: `The workflow is not valid. .github/workflows/dev.yml (Line: 15, Col: 11): Unrecognized named-value: 'env'. Located at position 1 within expression: env.aws_account,.github/workflows/dev.yml (Line: 16, Col: 14): Unrecognized named-value: 'env'. Located at position 1 within expression: env.aws_account` Expected behavior The expected behavior is that using the workflow file above the `build.name` would be `Deploy|cfaittoolsnp` and the `build.runs-on` would be `cfaittoolsnp`. Runner Version and Platform Running latest version of linux self-hosted runner. OS of the machine running the runner? linux (ubuntu 18.04)
Data sources should allow empty results without failing
This is an enhancement request. Data sources should allow empty results without failing the plan or apply. This would allow for fallback or fallthrough scenarios that are needed in certain situations. An optional `allow_empty_result` attribute on the data source would support many use cases where a datasource value is not explicitly required. The specific attribute name isn't important to me. As an example, the configuration below currently fails because the `aws_ami` datasource will not find any results. However I still want the apply to continue using a fallback AMI. [code block] (This is just an example so please don't get hung up on this specific use case.)
[Example needed] i18n with Next.js 13 and `app` directory
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: win32 Arch: x64 Version: Windows 10 Home Binaries: Node: 16.15.0 npm: N/A Yarn: N/A pnpm: N/A Relevant packages: next: 13.0.1-canary.0 eslint-config-next: 13.0.0 react: 18.2.0 react-dom: 18.2.0 What browser are you using? (if relevant) Chrome How are you deploying your application? (if relevant) Local Describe the Bug Setting up i18n test in next.config as follows: [code block] I've deleted pages and added a few files into the new /app folder to test Creating a simple component like so: [code block] I'm not seeing any locale information provided via the props. I was thinking this would be provided on the server side for rendering locale specific data on the server. Expected Behavior I would expect to be passed the current locale for use within sever components layouts/pages. Link to reproduction https://github.com/jimmyjamieson/nextjs-13-ts To Reproduce npm dev, check output of props, locale in layout
Failed to refresh slots cache
Hi, We are running ioredis 4.0.0 against an AWS ElastiCache replication group with cluster mode on (2 nodes, 1 shard) and using the cluster configuration address to connect to the cluster. [code block] and the config part: [code block] Every time we start the application the logs shows us: [code block] What more information do you need so we can get this fixed? <img width="1105" alt="screenshot 2018-09-28 at 16 08 57" src="https://user-images.githubusercontent.com/1263414/46213556-1fde1380-c339-11e8-9b9c-4fc8c627fd58.png">