-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Unhandled Rejection (SecurityError): The operation is insecure. #3901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! Could this be the issue? https://stackoverflow.com/a/49547221/893113 Maybe try it in Chrome? |
It seems the problem exists on firefox only since I tried it on brave and it worked perfectly but I noticed two things:
|
Ah, the logs are unrelated to the security error. |
But the problem of it not running with firefox still exists. |
I can't reproduce it in my copy of Firefox (68.0.1). Are you installing dependencies with The stack trace you're seeing isn't from Shields, so this is either an underlying issue in Gatsby, or something in your Firefox setup. If you run the built site, does the problem go away? Try |
I tried the steps which you described, but after running
|
Ah, yea, that's another issue we're trying to solve at the moment; see #3904. |
So is there any workaround or I need to wait for an update. |
I think |
It works for now but still the same error on firefox still persists. |
Sure, sounds good. I don’t have the capacity to investigate the Firefox issue, especially since there’s a workaround. |
It looks like the workaround for the |
I was getting "Unhandled Rejection (SecurityError): The operation is insecure." in firefox. See badges/shields#3901
Are you experiencing an issue with...
🪲 Description
I just started running the development using the steps in TUTORIAL.md after running
npm start
. After that the browser tries to render the webpage but provides an error,Here is the screen shot file:
The logs produced were:
[server] (node:10068) UnhandledPromiseRejectionWarning: Error: Token pool is exhausted [server] at TokenPool._nextBatch (C:\Users\User\Documents\User\git\shields\core\token-pooling\token-pool.js:263:11) [server] at TokenPool.next (C:\Users\User\Documents\User\git\shields\core\token-pooling\token-pool.js:300:20) [server] at GithubApiProvider.tokenForUrl (C:\Users\User\Documents\User\git\shields\services\github\github-api-provider.js:155:33) [server] at GithubApiProvider.request (C:\Users\User\Documents\User\git\shields\services\github\github-api-provider.js:171:22) [server] at Promise (C:\Users\User\Documents\User\git\shields\services\github\github-api-provider.js:210:12) [server] at new Promise (<anonymous>) [server] at GithubApiProvider.requestAsPromise (C:\Users\User\Documents\User\git\shields\services\github\github-api-provider.js:209:12) [server] at GithubForks._requestFetcher (C:\Users\User\Documents\User\git\shields\services\github\github-auth-service.js:13:23) [server] at GithubForks._request (C:\Users\User\Documents\User\git\shields\core\base-service\base.js:223:40) [server] at GithubForks._requestGraphql (C:\Users\User\Documents\User\git\shields\core\base-service\base-graphql.js:72:35) [server] (node:10068) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) [server] (node:10068) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
🔗 Link to the badge
💡 Possible Solution
The text was updated successfully, but these errors were encountered: