All Issues
24,993 verified issues
New version of pkg is published but not getting shown
See https://www.npmjs.com/package/chokidar I've published 3.3.1, but the page, curl `json api`, and npm all say only 3.3.0 is available. If you enter `chokida` into the search box, you'll see `version: 3.3.1`. Also happens to other people: https://twitter.com/itsmequinn/status/1206246890427297802
Merging schemas
I work on a huge project. To ensue project's long-term maintainability we decided to split the application into 3 standalone pieces thus we now have 3 specialized teams. Each app exposes its own GraphQL schema. At the end we plan to create the 4th app which will merge all 3 pieces together into a `gateway` application using the `express-graphql` package. What is the best way to merge schemas? What we would need is a mechanism similar to Express Router. Our current plan is to make all 3 apps available as private packages from which we can build a new schema for the main (4th) app. Well, we could make each app act as a standalone private graphql server and then the main application would just send requests to sub-apps but I believe it could potentially represent a huge overhead. Am I wrong? Are there any plans for supporting this? What do you suggest? How do you handle this at Facebook?
[resolved] [HTML] allow corresponding option to jsxBracketSameLine
Note: Read this comment to make sure you’re up-to-speed on what this issue is and is not about: https://github.com/prettier/prettier/issues/5377#issuecomment-628213559 --- For React/JSX - Prettier has an option to allow tags to close on the same line as the declaration, rather then on a new line: `jsxBracketSameLine: true`: [code block] `jsxBracketSameLine: false`: [code block] With Prettier 1.15.1, at least for the Angular parser, there is no corresponding option, so all HTML is formatted like this: Input: [code block] Output: [code block] Playground link It would be nice to have a flag to set it such that the output of the above would be: [code block]
aws s3 cp hangs on download more than 500MB on content
Hello, I am just doing daily backups from s3 files. Bassically I copy from a s3 bucket files to local disk to zip them and copy after to another s3 bucket the zipped contain. The issue is the aws s3 get stuck in any moment and doesn't download, I mean, the download starts but is interrupted in an specific moment in an specific file. This file can be accessed via web or any s3 explorer. the files are not big. My aws cli is: aws-cli/1.9.18 Python/2.7.10 Linux/4.1.13-19.31.amzn1.x86_64 botocore/1.3.18 OK I will change the issue, aws s3 cp is hanging when is downloading a lot of files. I checked with 2 s3 buckets with no long content and it downloads well but not the same when the bucket has a lot of files: S3 bucket content between 200 and 500MB on storage are downloaded without problems but not the same when content is beyond 500MB. Regards
403 when trying to download prisma engine
Bug description calling https://binaries.prisma.sh/all_commits/06fc58a368dc7be9fbbbe894adf8d445d208c284/debian-openssl-3.0.x/schema-engine.gz.sha256 and getting 403 error Severity 🚨 Critical: Unable to run new builds Reproduction [code block] Expected vs. Actual Behavior expected 200 but getting 403 Frequency Consistently reproducible Does this occur in development or production? All envs Workaround No workaround ```
Support `.mjs` output
Experimental support for ES modules just landed in Node 8.5 (changelog, PR). Since ES modules have some parsing and semantic differences, Node decided to use the `mjs` extension for ES modules (while `js` is for the "script" target and commonjs modules). The current Typescript version (`2.5.2`) supports ES modules emission but uses the `js` extension by default. It means that to use it with Node, a post-compilation step is required to change the extension from `js` to `mjs`. This adds undesirable complexity to use native ES modules support with Node. A solution would be to add a compiler option to output `.mjs` files when emitting ES modules. Edit (2018-03-22): The propositions below are a bit outdated. I recommend reading the issue to see the progression. See this comment for my current proposition. Notes: - It is possible that new parse goals will be added in the next versions of the ES spec. Letting the user provide the extension explicitly (as opposed to a boolean switch) would allow to be forward compatible with other new extension. - It should still be possible to emit ES modules with the `.js` extension, many tools rely on the `js` extension. - Another solution would be to have a different extension for the source files: `.mts` files would compile to `.mjs`, this would be similar to `.tsx` and `.jsx`.
When using multiple docker-compose.yml files from different directories, local paths are not followed correctly.
Consider the following command, working from `~/myproj/`: `docker-compose -f docker-compose.yml -f somesubmodule/docker-compose.yml up` Suppose `somesubmodule/docker-compose.yml` contains the following [code block] `docker-compose up` fails because it will try to build `myservice` from `~/myproj/myservice/docker-compose.yml` instead of `~/myproj/myservice/somesubmodule/docker-compose.yml`. The error message is something like: `ERROR: build path ~/myproj/myservice/ either does not exist, is not accessible, or is not a valid URL.` This happened with docker-compose version 1.8.0-rc1, build 9bf6bc6, installed from Homebrew on my Mac OS X Yosemite version 10.10.5 Note that simply running `docker-compose -f somesubmodule/docker-compose.yml up` works fine, it's probably a glitch due to merging yml files and losing locality. Relative paths should be expanded before merging instead.
[BUG]: drizzle-kit push TypeError Cannot use 'in' operator to search for 'default' in undefined
What version of `drizzle-orm` are you using? 0.30.10 What version of `drizzle-kit` are you using? 0.21.4 Describe the Bug run drizzle-kit push get error [code block] I had to drop all my tables and only then it worked [code block] however running it again with NO changes to schema or anything it shows the error again [code block] The error is also present when using npm [code block] Error is not present on older versions of drizzle-kit [code block] Expected behavior I should be able to run drizzle-kit push with no errors without having to reset my tables * and errors should be present when nothing has even changed? Please let me know if there is anything else that you need! Environment & setup Drizzle Config [code block] Drizzle Schema [code block] Package.json [code block]
Code Insider complains "Could not install typings files for JS/TS language features. Please ensure that NPM is installed"
- VSCode Version: Insider (daily latest, 1.12.0) - OS Version: Mac OS X 10.12.4 Steps to Reproduce: 1. I've nvm, node, and npm installed the current version in the system. 2. Open Code Insider 2. Open any existing JavaScript (ES) node project, warning appears: "Could not install typings files for JS/TS language features. Please ensure that NPM is installed"
Not refreshing access token automatically
Environment details - OS: Windows 10 64x - Node.js version: 12.16.3 - npm version: 6.14.4 - `googleapis` version: 59.0.0 Steps to reproduce I expect the API to automatically refresh the access token on the next API call after it expires, but I only get an "Invalid Client" error. I can successfully access the API and upload/download google drive files until the access token expires, so I know the tokens I received from the API on first signin are valid. I have that same refresh token assigned to the oauth2client immediately before any request. I can verify that they are set via console.log. Is there some missing step to get the API to "automatically refresh the access token" as it says in the documentation? [code block]
Touchable components stop responding randomly
Description We've been experiencing this issue in a couple of our apps, it's kinda driving us mad. Basically, sometimes, completely unpredictably the touchable areas just stop responding. We tried reproducing this consistently in several different ways but just couldn't pin point what causes it to happen and in which devices. It happens on both iOS and Android, and also in debug or release mode. Generally, it looks like it only happens after the user has been using the app for a little while (10+ minutes). It seems to happen in any button in the app randomly, and some times it also seemingly randomly starts working again. Closing and opening the app again always fixes the problem. We had clients complain about it in quite a few occasion, but some of our public testers rarely ever experience this either which makes it even harder to understand. I spent a very long time investigating it over literally the past entire year, but it's really really hard to debug, because when the issue happens in debug mode, anything you do in the code that causes hot reloading actually "fixes it", making it almost impossible to investigate. I have added lots of debugging tools to try and understand what happens though, I got a few bits of information that might be able to help. 1. This is not a performance or execution queue issue, as we have other interactive components in the screen that update automatically based on time and these never freeze. 2. Other touch based components seem to co
Issue with Typescript
I have been following this documentation(https://github.com/TwilioDevEd/api-snippets/blob/master/rest/access-tokens/video-example/video-example.3.x.js) to generate a auth token. Using `"twilio": "^3.19.1"` with `"@types/twilio": "0.0.9",` seems like the `VideoGrant` is unavailable and the Typescript and `AccessToken.toJwt()` requires a String parameter which is not necessary. I ended up doing the following, but it would be nice to fix these. Version: ^3.19.1 Code Snippet [code block] Thanks
Auth session sometimes ends with "Something went wrong trying to finish signing in."
Maintainer edit The auth session proxy service is deprecated and not recommended for production. For production apps, your app should navigate to the third-party authentication provider directly instead of using this service. This is the official workaround to this issue, which is likely unresolvable due to how browser cookie policies have changed. Follow this migration guide if you are currently using the proxy service. The migration guide shows how to configure the authentication provider to redirect directly to your app, typically with a deep link with your app's own URL scheme. In your app, set the useProxy option to false (the default) when calling the promptAsync method, which configures your app not to use this service. Due to web browser changes like WebKit's Tracking Prevention, the AuthSession proxy service may not work reliably in edge cases such as when a user's device is configured to block cookies or prevent cross-site tracking. The AuthSession proxy service does not track nor collect any user data but it requires cookies to correctly redirect back to your app after the user has authenticated with the third-party authentication provider. This service will not work if the browser's settings or heuristics block cookies. --- 🐛 Bug Report Summary of Issue (just a few sentences) Sometimes when I try logging in using AuthSession it doesn't redirect me back to app, but shows "Something went wrong trying to finish signing in." instead. After that when I try agai
Deprecate componentWillMount Maybe?
Let's use this thread to discuss use cases for componentWillMount and alternative solutions to those problems. Generally the solution is simply to use componentDidMount and two pass rendering if necessary. There are several problems with doing global side-effects in the "componentWill" phase. That includes starting network requests or subscribing to Flux stores etc. 1) It is confusing when used with error boundaries because currently `componentWillUnmount` can be called without `componentDidMount` ever being called. `componentWill*` is a false promise until all the children have successfully completed. Currently, this only applies when error boundaries are used but we'll probably want to revert this decision and simply not call `componentWillUnmount` here. 2) The Fiber experiment doesn't really have a good way to call `componentWillUnmount` when a new render gets aborted because a higher priority update interrupted it. Similarly, our sister project ComponentKit does reconciliation in threads where it is not safe to perform side-effects yet. 3) Callbacks from `componentWillMount` that update parent components with a `setState` is completely unsupported and lead to strange and order dependent race conditions. We already know that we want to deprecate that pattern. 4) The reconciliation order of children can easily be dependent upon if you perform global side-effects in `componentWillMount`. They're already not fully guaranteed because updates can cause unexpected reconcili
Passing in secrets to reusable workflow does not work without secrets in env
We are trying out Github Actions and have run into a curious issue which we think is a bug. We have configured secrets at the organization level, and are trying to pass those secrets in to a reusable workflow as shown below: [code block] This does not work. `password` shows up blank in the reusable workflow instead of having the value of the secret. If we instead add `env: ${{ secrets }}` to the top-level of the manifest, all of a sudden the secret gets passed in to the workflow. This seems quite counterintuitive since passing in secrets should not be related to the env, and this behavior does not appear to be documented anywhere. In fact, this example of secrets in reusable workflows does not need an `env` key set at the top-level.
DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
After update to version `5.2.9` I'm getting this message in console all the time, when I start my web app: `DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.` And I don't use neither of them.
Support for AWS access via IAM - AssumeRole
I get it's probably a lot of complexity to add, but it'd be great if Terraform supported using IAM roles in its AWS provider authentication. This adds a few steps to how API credentials are used – you use your normal AWS access key and secret key to call `sts assume-role` in the API, and this responds with a temporary access key, secret key and session token which you use for the rest of the session. An example with AWS's own CLI is here. The big use case for this is cross-account access. We have lots of AWS accounts to isolate billing to individual projects, and we link these to one parent account with AWS's consolidated billing. The cross-account roles let us have one set of IAM users in the parent account (eg one IAM user for each actual developer using AWS), and then just a single IAM role in each sub-account, which the developers can assume when needed. This saves having to create a new set of IAM users in each sub-account. I imagine this would involve adding extra AWS provider config fields to describe the role to assume (using an AWS ARN like `arn:aws:iam::account-of-role-to-assume:role/name-of-role`), and would also involve changing the AWS API access layer to use the temporary role access/secret keys _and_ a session token. This should be linked to the AWS meta-issue. I felt the explanation was long enough to warrant a full issue.
How to debug locally?
Hi, this isn't really a bug but more a general question about using Lambda and JAWS. With a typical Node server I'm used to pointing my mobile app to the locally running server so I can debug in my IDE during development. How can this be accomplished when using Lambda and JAWS? As I understand it, there are two ways to call Lambda functions, either directly through the AWS SDK or via REST API calls. It seems neither of these would be available on my local machine, as the SDK would be calling to Amazon, API Gateway also points to Amazon, and calling the REST API some other way wouldn't be possible without something like Express running as part of the app. I'm very interested in trying JAWS but I just want to understand how I can run and debug locally like I do today before deploying my functions. Thanks.
Fetch not working on Android 9 API 28
🐛 Bug Report Hello, I'm having an Issue about a HTTP service (the error only in simulator with API 28 (Pie) environment). I already add the domain on react_native_config.xml and add the networkSecurityConfig on both Manifests.xml (debug and release) but still get the TypeError: Network request failed error: I already try all this Issues: #23986, #23984 My info: info React Native Environment Info: System: OS: macOS 10.14.2 CPU: (8) x64 Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz Memory: 318.58 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 11.8.0 - /usr/local/bin/node Yarn: 1.13.0 - /usr/local/bin/yarn npm: 6.9.0 - /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: 25, 26, 27, 28 Build Tools: 25.0.0, 25.0.1, 26.0.2, 27.0.3, 28.0.3 System Images: android-25 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom IDEs: Android Studio: 3.3 AI-182.5107.16.33.5199772 Xcode: 10.2/10P91b - /usr/bin/xcodebuild npmPackages: react: 16.8.3 => 16.8.3 react-native: 0.59.0 => 0.59.0 npmGlobalPackages: react-native-cli: 2.0.1 react-native-git-upgrade: 0.2.7 My react_native_config.xml: <network-security-config> <domain-config cleartextTrafficPermitted="true"> <domain includeSubdomains="false">acolhebrasil.com.br</domain> </domain-config> <domain-config cleartextTrafficPermitted="true"> <domain inclu
Support to open a project folder in multiple VS Code windows
Currently VS Code prevents opening a folder more than once which makes it impossible to work on a project in multiple windows (e.g. on multiple displays). @bpasero @dbaeumer @egamma @alexandrudima please raise any obstacles and issues you might foresee with this request. Issues found so far: - [ ] we use the workspace path as identifier to communicate back from debug target to debug host - [ ] we need to verify cross platform that there is no code causing issues when running over the same root folder (e.g. file watchers) --- Please note: Initially I've created this feature request for a specific use case: enable debugging of multiple processes. In the meantime, debugging of multiple processes has become possible without the need for opening a folder more than once (see https://github.com/Microsoft/vscode/issues/13426). But instead of closing this item (as no longer necessary), I've repurposed it by removing the specific debug use case. For transparency you can find the original comment below: > Currently it is not possible to debug more than one process from a single VS Code project (= window) > because VS Code prevents opening a folder more than once. > > The workaround is to open VS code on a subfolder within the original folder, which means to restructure the project (which is not desirable). > > This feature request asks for lifting the constraint and allowing to open a project folder multiple times. >