All Issues
24,993 verified issues
1.0.0-pre "Session ID unknown"
HTTP Response {"code":1,"message":"Session ID unknown"} DEBUG=socket.io:* socket.io:socket joined room 2d1DHsPAtc1Sspm6AAAE +0ms socket.io:server incoming connection with id rwLW7JMBp6E4TyexAAAG +3s socket.io:client connecting to namespace / +3s socket.io:namespace adding socket to nsp / +3s socket.io:socket socket connected - writing packet +3s socket.io:socket joining room rwLW7JMBp6E4TyexAAAG +0ms socket.io:client writing packet {"type":0,"nsp":"/"} +1ms socket.io:client writing packet {"type":2,"data":["news",{"hello":"world"}],"nsp":"/"} +0ms socket.io:socket joined room rwLW7JMBp6E4TyexAAAG +1ms socket.io:server incoming connection with id 03Izy4YOxaYm5-d-AAAH +1s socket.io:client connecting to namespace / +1s socket.io:namespace adding socket to nsp / +1s socket.io:socket socket connected - writing packet +1s socket.io:socket joining room 03Izy4YOxaYm5-d-AAAH +0ms socket.io:client writing packet {"type":0,"nsp":"/"} +1ms socket.io:client writing packet {"type":2,"data":["news",{"hello":"world"}],"nsp":"/"} +0ms And socket is disconnected immediately
Service can't be reached by defined hostname
Given the following docker-compose.yml file: [code block] The following ping fails: [code block]
Jest tests failed after upgrading axios to v1.1.2
Describe the bug I updated the Axios from `"axios": "^0.27.2"` to `"axios": "^1.1.2"`, and Jest tests are not working anymore with the following error: [code block] To Reproduce 1. Use React and Axios latest version 2. Create Jest test 3. Run the test to generate the error Environment - Axios Version `^v1.1.2` - Browser `Chrome` - Browser Version `Version 105.0.5195.125 (Official Build) (x86_64)` - Node.js Version `v18.4.0` - OS: `MAC OS 12.4` - React: `^18.2.0` Temporary Fix The following fix works for now but I expect a standard fix for this issue. [code block] or [code block]
Cannot find name 'ProgressEvent' when compiling TypeScript
Describe the bug When trying to compile a Firebase function (Node.js / TypeScript) I get an error: [code block] To Reproduce Example of a `package.json` that fails to compile using `npm run build`. [code block] Expected behavior The Node.js code should compile. Environment - Axios Version: 0.20.0 - Node.js Version: 10.21.0 - OS: Ubuntu 20.04 Additional context/Screenshots None.
[BUG] v 7.3.0 when publishing to private rep You need to authorize this machine using 'npm adduser'
Current Behavior: Can not publish(This command requires you to be logged in) but I adduser successfully Expected Behavior: - it work with npm v 6 Steps To Reproduce: - npm adduser --registry=https://zelenjak.arnes.si/nexus/repository/ArnesNpm/ - ok login and in my .npmrc I get [code block] - in my package I have: [code block] - when running npm publish I got error: [code block] Environments: - Node: 12.6.0 - npm: 7.3.0 - OS: win32 x64
Axios catch error returns javascript error not server response
Im trying to catch validation errors from the server. Code: axios.post('/formulas/create', { name: "", parts: "" }) .then( (response) => { console.log(response) }, (error) => { console.log(error) } ); Console log output Error: Request failed with status code 422 at createError (app.js:6765) at settle (app.js:29489) at XMLHttpRequest.handleLoad (app.js:6600) Network tab output {"name":["The name field is required."],"parts":["The parts field is required."]} I should be seeing an object that contains JSON form validation as that is the response in my network tab, i seem to get the JS catch output? Also tried the following: axios.post('/formulas/create', { name: "", parts: "" }) .then(response => { console.log(response) }) .catch(error => { console.log(error) }); Same result More people seem to have the same problem using the same enviroment as me here. https://laracasts.com/discuss/channels/vue/issues-with-axios-catch-method - Axios version: ^0.16.2 - VueJS 2.3.4 - Vue-template-compiler 2.3.4 - Laravel-mix - Environment: node v6.4.0, chrome 58, Mac OSX 10.12.4
CORS problem (No 'Access-Control-Allow-Origin') on client
Hi all, Typically if you do have server with sockets on another domain and you do simple first line `io('YOUR_HOST')`, you will receive this message: `XMLHttpRequest cannot load YOUR_HOSTsocket.io/?EIO=3&transport=polling&t=1446467052356-0. No 'Access-Control-Allow-Origin'...` First appeared in head, that I need to look at documentation and find out how to set it from there, but eventually I did not find anything because of pure documentation. Then I entered source code and the only 2 usages of `setRequestHeader` method, which is actually allow you to do that, is only for setting content-type if POST method is chosen. Could you help me to fix this issue?
TypeError: url.URL is not a constructor
Issue Summary I am using latest version of this library 3.44.0. (I see from the npm version log. it's just a day ago!) and having the following error. TypeError: url.URL is not a constructor when I try to send message. the code is copied from doc. https://www.twilio.com/docs/sms/quickstart/node Steps to Reproduce 1. set up simple react project with create-react-app 2. npm install twilio 3. execute following code App.js Code Snippet [code block] Exception/Log [code block] Technical details: twilio-node version: 3.44.0 node version: 12.13.0
'SomeComponent' cannot be used as a JSX component.
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] What browser are you using? (if relevant) _No response_ How are you deploying your application? (if relevant) _No response_ Describe the Bug Any components are producing IDE error but builds successfully. [code block] Expected Behavior probably not give an error when using async components Link to reproduction no link To Reproduce [code block]
Decrease the amount of generated TS types (performance issues)
Based on Discord conversation https://discord.com/channels/1043890932593987624/1095436601426972822/1095436601426972822
Windows: Scrolling is not smooth but lags
Edit: Added the workaround: Workaround Configure: `"window.smoothScrollingWorkaround": true` `"window.titleBarStyle": "native"`
Verify access token on node.js
Add functionality to verify the access token and get a user on the server-side. Firebase Admin-like API to verify id token and get the current user on the server-side. I'm now working on a Nest.js-based Graphql API server and trying out Supabase Auth. When use sends a request to the server, I need to verify the access token and pass down the user info in the middleware. I checked the API but it seems there's no functionality for that right now. I also checked gotrue-js but seems they don't have anything like that. Do you plan to add firebase-admin-like toolsets? Describe the solution you'd like With FirebaseAdmin: admin.auth()verifyIdToken() will verify the user based on the access token and return the currentFirebaseUser. It seems gotrue server is doing this but I like to do the same on my own server. Is there any workaround for now to verify the user on the node.js side?
Allow hiding the buttons in the tab bar line and in the panel title bar
A small change related to the buttons in the tab bar line: Open Changes Split Editor Close and to the buttons in the panel title bar: New Terminal Split Terminal Kill Terminal Maximize Panel Size Move to Bottom * Close Panel For users who have already memorized the keyboard shortcuts for these commands (and considering the existence of Ctrl-p and Ctrl-Shift-p), the buttons are kind of redundant. It would be nice to have an option to hide them as almost everything in the UI already can be hidden. I know about Zen mode, but Zen mode also centers the text in the editor, hides the panel/terminals, makes Visual Studio Code full screen and all sort of other things which might not be desirable. As a note related to this, Vim and Emacs users generally tend to hide the UI. Funnily enough, even the beast that is IntelliJ IDEA allows it 😆
Receiving ERR_NETWORK suddenly on axios.get request
Describe the issue Roughly a month ago I started receiving an `ERR_NETWORK` response from my `axios.get` (and `axios.post`) requests. I have no idea what is causing this because nothing on the server it's requesting (I have access to the API server as well) has changed and nothing in my request has changed either. I'm using Vue 3 in Electron. I can make the request with the same URL and headers in PostMan and receive the correct response. When I build my app for production, the request works completely fine, but when it's in development mode, I receive these errors on any of the API calls and I have no idea what's going on. I receive the following errors in my console after the request fails - `Access to XMLHttpRequest at 'DOMAIN' from origin 'http://localhost:8080' has been blocked by CORS policy: Request header field accesstoken is not allowed by Access-Control-Allow-Headers in preflight response.` `GET DOMAIN net::ERR_FAILED` `{ "message": "Network Error", "name": "AxiosError", "stack": "AxiosError: Network Error\n at XMLHttpRequest.handleError (http://localhost:8080/js/chunk-vendors.js:24846:14)", "config": { "transitional": { "silentJSONParsing": true, "forcedJSONParsing": true, "clarifyTimeoutError": false }, "adapter": [ "xhr", "http" ], "transformRequest": [ null ], "transformResponse": [ null ],
JIT mode is not picking up changes unless I change tailwind.config.js file
What version of Tailwind CSS are you using? v2.2.4 What build tool (or framework if it abstracts the build tool) are you using? postcss-cli v8.3.1 What version of Node.js are you using? v14.15.5 What browser are you using? Firefox What operating system are you using? Windows Reproduction repository https://github.com/MohammadxAli/tailwind-test-repo Describe your issue Sometimes tailwind in `jit` mode is not adding classes to final CSS when I'm adding them to my HTML files unless I edit the `tailwind.config.js` file, I usually comment and uncomment some line in that file and all of sudden I see the class has been added to the CSS file, I had this very same issue on my Next.js project as well. I made a new reproduction repository and tested things there, it was all good and working. Not really sure why it's not working on my own projects at some point. This may sound stupid but maybe tailwind is not picking up changes as the project get's more complicated? I made this issue to know if anyone had some similar experience or not, so maybe someone can guide me on how to resolve this.
Using element with splat reference should scope dependency to selected resource
I'm trying to setup a multi-node cluster with attached ebs volumes. An example below: [code block] If a change happens to a single node (for instance if a single ec2 instance is terminated) ALL of the aws_volume_attachments are recreated. Clearly we would not want volume attachments to be removed in a production environment. Worse than that, in conjunction with #2957 you first must unmount these attachments before they can be recreated. This has the effect of making volume attachments only viable on brand new clusters.
Support for --profile argument when deploying to AWS
Feature Request: it should be possible to run `serverless deploy --profile production` to use the production AWS profile. At the moment this has to be set through environment variables Benefits: - being able to easily switch profiles to deploy with
auth/network-request-failed when debugging on react native
[REQUIRED] Describe your environment Operating System version: Mac 10.14.6 Browser version: Chrome Version 79.0.3945.130 Firebase SDK version: 6.6.2 Firebase Product: auth (auth, database, storage, etc) React Native version: 0.61.5 [REQUIRED] Describe the problem Getting an error when running on debug mode on the simulator (both for ios and android) [code block] Works fine on the simulator when I'm not debugging. Happens also for other teammates that work on the same project * Rebooting Chrome didn't help Steps to reproduce: Relevant Code: I created a small react native app to reproduce the bug: https://github.com/shirlev-wix/firebase-bug [code block] Thanks!
Can't subscribe to events of existing S3 bucket
This is a Bug Report Description When specifying an already existing S3 bucket (xxx) in a function event, I get this error on deploy: [code block] I could not find documentation on how to subscribe to events of an existing S3 bucket in 1.0 rc1. This worked in 0.5.
Boolean inputs are not actually booleans
>[!NOTE] > Although this has been fixed, see also: > - #2238 Describe the bug Boolean type inputs do not work as expected; they are strings instead of booleans, even when surrounded by `${{ }}` (e.g. in a step's `if` condition). To Reproduce Steps to reproduce the behavior: Run this workflow using the workflow dispatch, with the foo input checkbox not ticked: [code block] Expected behavior When the input is `false`, the `Run if foo` step should be skipped , and the `Don't run if foo` step should run. Runner Version and Platform Version of your runner? `2.284.0` OS of the machine running the runner? `ubuntu-latest (20.04.3)` What's not working? The value of `github.event.inputs.foo` is `false`, yet the `Run if foo` step runs and the `Don't run if foo` step is skipped. Additional context It is the same for a string input type or boolean input type (https://github.blog/changelog/2021-11-10-github-actions-input-types-for-manual-workflows/). Only `if: ${{ github.event.inputs.foo == 'true' }}` works. So the input must be being treated as a string. This goes against what the documentation says at https://docs.github.com/en/actions/learn-github-actions/expressions#about-expressions: >...evaluate an expression rather than treat it as a string. > >`${{ <expression> }}`