All Issues
24,993 verified issues
NullPointerException:tempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)'
Is this a bug report? yes Have you read the Contributing Guidelines? yes, I am sorry that I cant offer more information about this exception except for this stack trace because the crash report was collected from google analytics, I have no idea to reappear this exception. Environment Environment: OS: macOS Sierra 10.12.6 Node: 8.4.0 Yarn: 0.27.5 npm: 5.4.0 Android Studio: 3.0 Packages: (wanted => installed) react-native: 0.51.0 => 0.51.0 react: 16.0.0-alpha.12 => 16.0.0-alpha.12 Target Platform: Android (7.1.1) mobile:MIX 2 android:7.1.1 java.lang.NullPointerException: tempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)' on a null object reference at android.graphics.drawable.DrawableContainer$DrawableContainerState.getChild(DrawableContainer.java:888) at android.graphics.drawable.DrawableContainer.selectDrawable(DrawableContainer.java:466) at android.graphics.drawable.StateListDrawable.onStateChange(StateListDrawable.java:104) at android.graphics.drawable.Drawable.setState(Drawable.java:735) at android.graphics.drawable.DrawableWrapper.onStateChange(DrawableWrapper.java:331) at android.graphics.drawable.Drawable.setState(Drawable.java:735) at android.graphics.drawable.LayerDrawable.onStateChange(LayerDrawable.java:1488) at android.graphics.drawable.Drawable.setState(Drawable.java:735) at android.view.View.drawableS
Next 9.5.1 out of memory after some hot reloads
Bug report Describe the bug Since updating to 9.5.x (from 9.4.x), i get an out of memory error after 10 something hot reloads: `FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory` it did rarely happen in 9.4.1, but it happens very consistantly in 9.5.x To Reproduce thats probably tricky. it happens on big projects and might be related to some bug in the hot reload / rebuild. Maybe it happens when there are some import circles? Expected behavior nextjs should not go out-of-memory System information - OS:macOS - Browser: chrome - Version of Next.js: 9.5.1 - Version of Node.js: 12.13.1 Additional information we are using a custom server with typescript
Next.js API routes (and pages) should support reading files
Feature request Is your feature request related to a problem? Please describe. It's currently not possible to read files from API routes or pages. Describe the solution you'd like I want to be able to call `fs.readFile` with a `__dirname` path and have it "just work". This should work in Development and Production mode. Describe alternatives you've considered This may need to integrate with `@zeit/webpack-asset-relocator-loader` in some capacity. This plugin handles these types of requires. However, it's not a necessity. I'd be OK with something that _only_ works with `__dirname` and `__filename` (no relative or cwd-based paths). Additional context Example: [code block] > Note: I know you can cheat the above example ☝️ with `require`, but that's not the point. 😄
add conditional execution of action steps
Describe the enhancement Add possibility to use `if:` option for action steps of composite actions. Code Snippet [code block]`
Alternative locations for the outline view
The outline view lives inside the file explorer and while it can be re-arranges in there it cannot be dragged into its own view. Alternative locations could be: 1. a standalone viewlet, 2. inside another viewlets, 3. the bottom panel, or 4. as a re-arrangable view that can be docked anywhere in the UI (like most others have it).
Make the MongoDB Replica Set Requirement Optional in Development
Problem MongoDB only allows you to start a transaction on a replica set. Prisma uses transactions internally to avoid partial writes on nested queries. This means we inherit the requirement of needing a replica set configured. This makes our getting started experience more cumbersome because a locally installed MongoDB doesn't have the replica set configured by default. If you try running Prisma against a MongoDB without a replica set, you get the following error: [code block] Suggested solution We should find a way to make this requirement optional, at least during development. In production, most people will host their MongoDB instance with the replica set configured. Alternatives Right now we recommend that you use MongoDB Atlas to launch a free instance that has replica set support out of the box. There's also an option to run the replica set locally with this guide: https://docs.mongodb.com/manual/tutorial/convert-standalone-to-replica-set/
Invalid hook call in 9.0.6
Bug report Describe the bug When you use react a component residing outside the main Next.js project folder which uses hooks. You end up getting `Invalid hook call` error and the application breaks. Components without hooks work as expected. The bug appears in all versions `>9.0.5` when you change the webpack config so that files outside the main folder are transpiled. It’s working fine in `<=9.0.5` To Reproduce Check out the repro at https://github.com/baldurh/next-9.0.6-bug-repro Expected behavior The code should not break when using files outside the project folder. System information - OS: N/A - Browser: N/A - Version of Next.js: `>=9.0.6` Additional context I know this is probably not a common use of Next.js but in our project we’re using a monorepo and have a shared folder with components used by multiple applications. It would be nice to get this working again. If someone finds an alternative config we could use I’d also be happy to do that 🙂
Support for NodeJS 12.7+ package exports
NodeJS 12.7 added support for a (currently experimental) feature for custom package imports and exports in `package.json`: https://github.com/jkrems/proposal-pkg-exports/ In short, this feature allows a package author to redirect exports in their package to alternate locations: [code block] This is currently only available when `--experiemental-exports` is passed to NodeJS, however we should continue to track the development of this feature as it progresses.
Provide RPM and DEB packages for compose
Not everyone likes to install binaries (#1288). It might be good to provide a system package for compose. We should use https://github.com/spotify/dh-virtualenv for the debian package and look into a similar approach for the rpm.
Allow multiple views to show at the same time
Would be nice to be able to have both a left and right sidebar i,e file tree in left and VSC in right. Kinda vibing off the multi panel layout of atom with github / git integration Something like this
Partial/Progressive Configuration Changes
For a while now I've been wringing my hands over the issue of using computed resource properties in parts of the Terraform config that are needed during the refresh and apply phases, where the values are likely to not be known yet. The two primary situations that I and others have run into are: - Interpolating into provider configuration blocks, as I described in #2976. This is allowed by Terraform but fails in unintuitive ways when a chicken-and-egg problem arises. - Interpolating into the `count` modifier on resource blocks, as described in #1497. Currently this permits only variables, but having it configurable from resource attributes would be desirable. After a number of false-starts trying to find a way to make this work better in Terraform, I believe I've found a design that builds on concepts already present in Terraform, and that makes only small changes to the Terraform workflow. I arrived at this solution by "paving the cowpaths" after watching my coworkers and I work around the issue in various ways. --- The crux of the proposal is to alter Terraform's workflow to support the idea of _partial application_, allowing Terraform to apply a complicated configuration over several passes and converging on the desired configuration. So from the user's perspective, it would look something like this: [code block] For a particularly-complicated configuration there may be three or more apply/plan cycles, but eventually the configuration should converge. `terraform appl
[BUG] npm update does not save new versions in package.json
Current Behavior: When running `npm update`, packages are updated normally, package-lock.json is updated, but package.json is not. (`npm install [package]@[version]` does update package.json as expected.) Expected Behavior: The package.json file should be updated with the newly installed versions, as specified in the npm-update docs. Steps To Reproduce: - `npm update` - Check package.json Environment: OS: Mac OS Big Sur Node: 14.15.5 NPM: 7.5.4
How can I sort relations loaded with find's "relations" option?
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` [ ] `expo` TypeORM version: [X] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: I'm loading an entity with a one-to-many relationship. So, that relationship is an array of entities associated with the entity I'm querying. I'd like to specify an order for that array of entities. Example (Users and their Photos): I'd like to query a user, load their photos as a relation, and the photos should be loaded by their createdAt date: [code block] Is there a way to do this?
Git: Use VS Code as merge editor
1.0.0 introduced the ability to use VS Code as a git difftool. The relevant global `.gitconfig` lines are as follows: [code block] How can I use VS Code as a git mergetool? The relevant arguments it needs to accept, I believe, are `$LOCAL`, `$REMOTE`, `$BASE`, and `$MERGED`.
[BUG] ^7.20.3 no longer resolves local package first on install (workspaces)
Is there an existing issue for this? - [X] I have searched the existing issues Current Behavior In a workspaces based environment, for example: [code block] Running `npm install b --workspace a` will no longer install the locally linked package correctly. Instead, it'll use the version hosted on `npm`, or throw a 404 if you use a custom (unique) package name. Expected Behavior In <7.20.x, NPM would resolve the local package, and correctly alter package.json and package-lock.json. Steps To Reproduce With `node v16.6.1` and `npm 7.20.3` installed: 1) Make a new directory [code block] 2) Add a package.json [code block] 3) Setup 2 workspace packages [code block] (I used `@rijk/a` and `@rijk/b` as names, to avoid confusion with the existing packages `a` and `b`.) 5) Run `npm install` in the root, to give it a chance to npm link all the packages (not sure if needed) [code block] 6) Try installing `@rijk/b` as a dependency of `@rijk/a` [code block] 5) See error... [code block] --- If you install `7.20.2` or below (`npm i -g npm@7.20.2`), the above flow still works as expected. Environment - OS: macOS 11.4, also seen in GitHub Actions - Node: v16.6.1 - npm: 7.20.3 and up
Add ability to re-run single jobs
Please add the ability to re-run single jobs of a workflow. This is such a basic feature. Please keep the environment in mind while prioritizing features. 🙏
Docker compose pull doesn't respect local images
During my searches I've seen this issue raised and closed a few times, but even using the latest build of docker-compose, this still doesn't behave the way I understand that it is expected to. Scenario: We're building a composed environment for our CI tests to run. We grab a database image, an api image, and a _local_ copy of the image containing application we are trying to test (it has been built in a previous CI step, and tagged with the build hash provided by our CI environment (CIRCLE_SHA1) docker-compose.yml [code block] The commands we run then are as follows: [code block] Actual Result: No matter what I do, docker compose always tries to pull my CIRCLE_SHA1 tagged version from docker hub. it doesn't exist there, I never want to push it (until it passes tests and is re-tagged as :latest and/or :release I have a unique tag CIRCLE_SHA1 which only exists inside the build environment, meaning no confusion for docker-compose when it tries to pull, and yet, it seems to try to fetch it anyway, and fail even though that exact tag exists locally. Expected Result: I'd expect the fact that there is no remote build tagged with CIRCLE_SHA1 to cause docker-compose to use the local copy it finds. I need to do pull, because I want everything else to be the latest. I'd suggest that if there is confusion where `image:` refers to a remote repository, then perhaps we could use `local:` instead, to reference a local image?
MongoDB support for Prisma 2+
Our team is considering working with Prisma, but as Prisma 1 seems to go out of scope and prisma 2 not mongo ready yet would love to know when is support expected to be released? a week? a month ? 2021 ?
aws eks update-kubeconfig invalid apiVersion
Describe the bug Update kubectl from v1.23.6 to 1.24.0 and run commands [code block] I get the following error and exit status 1 [code block] Kubectl must need an updated apiVersion in kubeconfig file. Not sure if this is on aws side or kubectl side. https://github.com/kubernetes/kubectl/issues/1210 Expected Behavior No error message when using `kubectl` and `aws eks update-kubeconfig` Current Behavior error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1" Reproduction Steps Update kubectl from v1.23.6 to 1.24.0 and run commands [code block] Possible Solution _No response_ Additional Information/Context _No response_ CLI version used whatever is running in aws/codebuild/standard:5.0 Environment details (OS name and version, etc.) aws/codebuild/standard:5.0
Problem with dependant module resolution if the path is relative
Terraform Version 0.12.13 Terraform Configuration Files Here you can see two examples: https://github.com/xocasdashdash/terraform-test-case One works perfectly with 0.11, same one fails on 0.12.13 (and on dev too). Debug Output [code block] Expected Behavior It should resolve to the correct module path for the "d-module". Actual Behavior It does not. But if I change the route to use a local symlink and add a double "//" on the last folder before the module folder "//a-module" and set up a symlink from the module to the parent folder it does work correctly. Steps to Reproduce Run terraform init in each of the three folders with the last working version (0.11.14 and 0.12.13). Additional Context I've tried to fix it myself and I think the fix should go to this function: https://github.com/hashicorp/terraform/blob/6f66aad03262441521829ca3a678da2bb6bf51d9/internal/initwd/module_install.go#L226 I'm gonna try some more to make it work but I believe a bigger change will be needed to get this to work in all cases