All Issues
24,993 verified issues
Dependency Broken (2-thenable) - 404
❗️ NOTE FROM MAINTAINERS ❗️ It's an issue on npm registry side, where for requests which include the `accept: application/vnd.npm.install-v1+json` header a `404` response is returned Following returns 200 [code block] Following 404 [code block] I was informed that __issue is already fixed on npm side__. Still it may might take a couple of hours to propagate across all nodes and CDN layer. --- Hello there! I'm getting 404 err when installing serverless with: `npm install serverless`, check this out: Is someone facing the same problem?
Google as an Auth provider doesn't work on iOS saved to homescreen
[REQUIRED] Describe your environment Operating System version: iOS 10 Firebase SDK version: 4.1.3 Firebase Product: auth [REQUIRED] Describe the problem Steps to reproduce: 0. Save the app on the homescreen on iOS 1. make a redirect or popup login with google Auth provider 2. if redirect: - webview is not a "valid user agent" 3. if popup: - gets stuck in Safari about:blank, doesn't open the app again to pass on the token Relevant Code: [code block]
upsert with return functionality
proposing the following functionality (essentially `insert... on conflict.. returning..`): [code block] at least in postgres, this is possible in a single operation, but it's not currently possible in a single operation with TypeORM (example not tested, just for showing a current rough solution..): [code block]
Received status code 502 from server: Bad Gateway
* What went wrong: Could not resolve all files for configuration ':app:debugCompileClasspath'. > Could not resolve com.facebook.react:react-native:+. Required by: project :app project :app > project :react-native-snackbar project :app > project :react-native-settings project :app > project :react-native-location-switch project :app > project :react-native-i18n > Failed to list versions for com.facebook.react:react-native. > Unable to load Maven meta-data from https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml. > Could not HEAD 'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway This is due to bintray is down https://status.bintray.com/ let's have a cup of coffee
[Feature Request/Discussion] @apply with media queries and pseudo selectors
@apply currently does not work with pseudo selectors and media queries. I can see why that is difficult, but I wonder if it is on the roadmap to support something like that in the future? I'd love it if @apply could make media queries or hover selectors automatically. Maybe it would have to be a Saas/Less only feature because I'm not sure how it would work with raw CSS, but I'm not sure. Thanks for considering, and thanks for making such an awesome lib
Skip and take doesn't work with join
Issue type: [ ] question [x] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [x] `postgres` [ ] `cockroachdb` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [ ] `latest` [ ] `@next` [x] `0.2.18` (or put your version here) Hi I have 7 row in my table and it's my first query. First Query [code block] First test for First query It's my query log for just one request (my resolver dosn't have any additional middleware) with skip: 1 and take: 2 [code block] but i got my whole 7 rows and it seem two query executed!!! In above query log, in first log LIMIT and OFFSET clause exist but in the second query they don't exist. Second test for First query It's my second log for skip: 7 and take: 2 [code block] As i expected, result was empty and just one query executed (i have just 7 row in my table) LIMIT and OFFSET clause exist in query log. Second Query I changed my query to just retrieve rows without any join (relations). [code block] First test for Second query It's my log with skip: 1 and take: 2 [code block] Everything works properly and i got expected rows. Conclusion I can only say it's strange behavior.
[BUG] CVE-2024-21538 - cross-spawn to 7.0.5+
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 @wraithgar Since we cannot create updates of bundled node_modules, could you please bump the `cross-spawn` to 7.0.5 or higher? https://security.snyk.io/vuln/SNYK-JS-CROSSSPAWN-8303230 Expected Behavior _No response_ Steps To Reproduce 1. In this environment... 2. With this config... 3. Run '...' 4. See error... Environment - npm: - Node.js: - OS Name: - System Model Name: - npm config: [code block]
Destroy 'provisioner' for instance resources
I would be great to have sort of a 'provisioner' for destroying an instance resource. Example: When creating a instance, I bootstrap it with chef and the node is registered with the chef server. Now I need a way of automatically deleting the node from the chef server after terraform destroys the instance.
GraphQL should allow mutating optional fields to 'null'.
Unless I'm overlooking something, I'm not seeing any way to pass `null` into a mutation for an 'optional' arg. It seems that the keys with `null` values get stripped out inside GraphQL-JS itself before making it to my `resolve` in the `obj` parameter.
VS Code not working on Ubuntu when connected using XRDP.
Hi, it seems like the bug with either Atom or XRDP discussed in Atom issue here: https://github.com/atom/atom/issues/4360 is keeping VSCode from working in Ubuntu when you connect to it with RDP. Trying to launch the app gives the following output: Xlib: extension "XInputExtension" missing on display ":10.0". Xlib: extension "XInputExtension" missing on display ":10.0". libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so libGL: Can't open configuration file /home/hannesne/.drirc: No such file or directory. libGL: Can't open configuration file /home/hannesne/.drirc: No such file or directory. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell Xlib: extension "XInputExtension" missing on display ":10.0". Xlib: extension "XInputExtension" missing on display ":10.0". [ , [Error: channel closed] ] This happens regardless of using the MATE or LFCE desktop. An output of GLXInfo gives the following: libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast name of display: :10.0 display: :10 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_import_context, G
[BUG] `npm.cmd` uses deprecated switch `-g`
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 When invoking `npm --version` on Windows there is a warning about a deprecated commandline switch: [code block] Expected Behavior No warning when no deprecated switch is used. Steps To Reproduce After upgrading npm to version 8.12.0 with npm-windows-upgrade `npm` always shows a warning on every execution about the deprecated switch `-g`. Environment - npm: 8.12.0 - Node.js: 16.15.0 - OS Name: Windows 11
ENOENT: no such file or directory, rename ... deps_temp
Describe the bug Sometimes when Vite is starting up with Storybook, it throws an error as shown below. Normally it's difficult to reproduce, but I've got a set of steps that seems to reliably reproduce the issue (at least, it happened to a storybook maintainer, and I was able to follow the steps as well. 1. checked out https://github.com/yannbf/storybook-coverage-recipes/tree/main/angular_vite 2. ran `npx storybook@future upgrade --prerelease --yes && yarn storybook` 3. Storybook opened fine but after compiling, then it broke completely because of a Typescript issue 4. I fixed the types by renaming Story to StoryFn (3 files: `button.stories.ts`, `page.stories.ts`, `header.stories.ts`) 5. I ran `yarn storybook` again 6. Got the issue Reproduction https://github.com/yannbf/storybook-coverage-recipes/tree/main/angular_vite System Info [code block] Used Package Manager yarn Logs <details> <summary>Click to expand!</summary> [code block] </details> Validations - [X] Follow our Code of Conduct - [X] Read the Contributing Guidelines. - [X] Read the docs. - [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. - [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. - [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. - [X] The provided reproduction is a mini
[BUG] Exit handler never called during clean-install, with Node.js v22.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 (While there are similar issues already open, the wiki page for "exit handler never called" errors recommends opening a new issue, so I am doing so) I am running into errors when using Node.js v22.5.0 and npm v10.8.2 to install dependencies. In GitHub Actions, I'm seeing an "Exit handler never called!" error. I tried installing the same versions locally, and instead npm never exits -- the packages get installed, but I just see a spinner in the terminal forever. I did not have any issues in CI prior to the release of Node.js v22.5.0. When I use Node.js v20.12.2 and npm v10.8.2 locally, installation completes successfully. Thus, I think some change in Node.js v22.5.0 must be related. Here's a log file from the error happening in GitHub Actions: 2024-07-17T17_07_43_972Z-debug-0.log. This came from the following run: https://github.com/divviup/divviup-api/actions/runs/9978466717/job/27575428716?pr=1178 Expected Behavior `npm ci` should succeed and exit cleanly. Steps To Reproduce 1. Install Node.js v22.5.0. 1. Install npm v10.8.2. 1. `git clone https://github.com/divviup/divviup-api.git` 1. `cd divviup-api/app` 1. `git checkout 3edafaefe90795387db3e35a161f3110c3ac3dea` 1. `npm ci` Environment - npm: v10.8.2 - Node.js: v22.5.0 - OS Name: Ubuntu - System Model Name: Unknown, Azure instance - npm conf
[SDK 52] Splash screen image scaled very small on development builds
Minimal reproducible example https://github.com/expo/expo/tree/main/templates/expo-template-default What platform(s) does this occur on? Android, iOS Where did you reproduce the issue? in a development build Summary Splash screen image is scaled very small on iOS development builds, but not Expo Go. Using default template via `npx create-expo-app@latest --template default@beta` and run dev build via: `npx expo prebuild --clean --platform ios && npx expo run:ios` Screenshots to compare: Development build: Expo Go: Environment [code block] Expo Doctor Diagnostics [code block]
Vite >6.0.9 has CORS issue with laravel-vite
Describe the bug After updating VITE to version 6.0.9 I get the following error when vite build FULL ERROR: [code block] Reproduction https://o.kg Steps to reproduce set 6.0.9 vite version npm install npm run build System Info [code block] Used Package Manager npm Logs _No response_ Validations - [ ] Follow our Code of Conduct - [ ] Read the Contributing Guidelines. - [ ] Read the docs. - [ ] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. - [ ] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. - [ ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. - [ ] The provided reproduction is a minimal reproducible example of the bug.
Update icon
I use this customized icon by Santiago Ramos Panalés, and would like to petition for to be made the official Visual Studio Code icon on Mac OS X. I have not asked the artists permission before submitting this feature request. It looks fantastic and follows [Apples OS X Human Interface Guidelines], while the current icon looks out of place in both the dock and the application launcher. Images for comparison:
Proposed Rule: Enforce lines between class methods
I would like to propose a rule that enforces empty lines between class functions. When enabled and set to "always" it should make sure that there is at least one empty line between every method in a class declaration. If set to "never" the opposite would be true, that is, there should not be any empty lines at all between class methods. A line with a comment on should not count as an empty line. This rule should not concern itself with the class padding (empty lines before the first method and after the last method) since that is already taken care of by `padded-blocks`. It also shouldn't concern itself with how many empty lines that are present, since that is a job for `no-multiple-empty-lines`. This is a stylistic rule. The following patterns would be considered problems: [code block] The following pattern would be considered valid: [code block]
Store arrays in variables
I have lists of security groups and or lists of ec2 instances that i would like to to keep in arrays ( separated by files which are auto loaded by *.tf ) so i know when i change things in one place, it gets changed in another. Right now vars can only hold strings or key value maps, but not arrays (if i am reading the docs and error messages correctly)
consider not deprecating typeInfo and getFieldDef options to validate function and TypeInfo constructor
https://github.com/graphql/graphql-js/blob/e1726dfea66979bfe7ad1c0b0834613e4b6ce4b4/src/validation/validate.ts#L44-L45 https://github.com/graphql/graphql-js/blob/e1726dfea66979bfe7ad1c0b0834613e4b6ce4b4/src/utilities/TypeInfo.ts#L66-L67 From what I understand, by preserving these options, we add the ability for a server to add custom meta fields such as `__fulfilled` or `__directive` and still validate properly.
[Community contributions] Model cards
Hey friends! 👋 We are currently in the process of improving the Transformers model cards by making them more directly useful for everyone. The main goal is to: 1. Standardize all model cards with a consistent format so users know what to expect when moving between different model cards or trying to learn how to use a new model. 2. Include a brief description of the model (what makes it unique/different) written in a way that's accessible to everyone. 3. Provide ready to use code examples featuring the `Pipeline`, `AutoModel`, and `transformers-cli` with available optimizations included. For large models, provide a quantization example so its easier for everyone to run the model. 4. Include an attention mask visualizer for currently supported models to help users visualize what a model is seeing (refer to #36630) for more details. Compare the before and after model cards below: With so many models in Transformers, we could really use some a hand with standardizing the existing model cards. If you're interested in making a contribution, pick a model from the list below and then you can get started! Steps Each model card should follow the format below. You can copy the text exactly as it is! [code block]py from transformers.utils.attention_visualizer import AttentionMaskVisualizer visualizer = AttentionMaskVisualizer("google/gemma-3-4b-it") visualizer("<img>What is shown in this image?") \[code block]py <insert relevant code snippet here related to the note if its