Please Help ,I have been trying to execute this script (link below) to get NFT Mint Addresses . Unfortunately I always get this error no matter which candy machine v1 or v2 I use.
https://solanacookbook.com/references/nfts.html#how-to-get-nft-mint-addresses
bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)
(node:11240) UnhandledPromiseRejectionWarning: Error: 410 Gone: {"jsonrpc":"2.0","error":{"code": 410, "message":"The RPC call or parameters have been disabled."}, "id": "3bc319ad-c4e0-45a4-b4bf-c1009ce99851" }
at ClientBrowser.callServer (C:\Users\mlvie\Desktop\ranking projects\test4\node_modules\#solana\web3.js\lib\index.cjs.js:4819:18)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:11240) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:11240) [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.
Different RPCs will not allow the RPC call getProgramAccounts because it is very expensive to the RPC infrastructure
You are running into 410 gone because whatever RPC you're hitting has removed it
Related
I have a problem my mongo-express container can't connect to the MongoDB container. Although I didn't change my code, I changed the version of the image container by downloading the latest version. And this is the log file from the mongo-express container.
(node:7) [MONGODB DRIVER] Warning: Current Server Discovery and Monitoring
engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.
Could not connect to database using connectionString: mongodb://admin:password#mongodb:27017/"
(node:7) UnhandledPromiseRejectionWarning: MongoNetworkError: failed to connect to server [mongodb:27017] on first connect [MongoNetworkTimeoutError: connection timed out
at connectionFailureError (/node_modules/mongodb/lib/core/connection/connect.js:362:14)
at Socket.<anonymous> (/node_modules/mongodb/lib/core/connection/connect.js:330:16)
at Object.onceWrapper (events.js:420:28)
at Socket.emit (events.js:314:20)
at Socket._onTimeout (net.js:483:8)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)]
at Pool.<anonymous> (/node_modules/mongodb/lib/core/topologies/server.js:441:11)
at Pool.emit (events.js:314:20)
at /node_modules/mongodb/lib/core/connection/pool.js:564:14
at /node_modules/mongodb/lib/core/connection/pool.js:1000:11
at /node_modules/mongodb/lib/core/connection/connect.js:32:7
at callback (/node_modules/mongodb/lib/core/connection/connect.js:300:5)
at Socket.<anonymous> (/node_modules/mongodb/lib/core/connection/connect.js:330:7)
at Object.onceWrapper (events.js:420:28)
at Socket.emit (events.js:314:20)
at Socket._onTimeout (net.js:483:8)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
(node:7) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:7) [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.
I tried to connect mongo-express to MongoDB and every 10 seconds mongo-express restarted.
E:>create-react-app react-app
(node:12408) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, mkdir 'E:\react-app'
at Object.mkdirSync (fs.js:1013:3)
at Object.module.exports.makeDirSync (C:\Users\Admin\AppData\Roaming\npm\node_modules\create-react-app\node_modules\fs-extra\lib\mkdirs\make-dir.js:101:15)
at createApp (C:\Users\Admin\AppData\Roaming\npm\node_modules\create-react-app\createReactApp.js:255:6)
at C:\Users\Admin\AppData\Roaming\npm\node_modules\create-react-app\createReactApp.js:226:9
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:12408) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:12408) [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.
I'm trying to deploy my react app on firebase but i get this error:
Error: Failed to list Firebase projects. See firebase-debug.log for more info.
and in the firebase-debug.log file this shows:
[info] First, let's associate this project directory with a Firebase project.
[info] You can create multiple project aliases by running firebase use --add,
[info] but for now we'll just set up a default project.
[info]
[debug] [2021-03-20T19:18:31.200Z] > refreshing access token with scopes: []
[debug] [2021-03-20T19:18:31.202Z] >>> HTTP REQUEST POST https://www.googleapis.com/oauth2/v3/token
[debug] [2021-03-20T19:18:32.948Z] <<< HTTP RESPONSE 200 {"expires":"Mon, 01 Jan 1990 00:00:00
GMT","cache-control":"no-cache, no-store, max-age=0, must-revalidate","date":"Sat, 20 Mar 2021 19:18:28 GMT","pragma":"no-cache","content-type":"application/json; charset=utf-8","vary":"X-Origin, Referer, Origin,Accept-Encoding","server":"scaffolding on HTTPServer2","x-xss-protection":"0","x-frame-options":"SAMEORIGIN","x-content-type-options":"nosniff","alt-svc":"h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"","accept-ranges":"none","transfer-encoding":"chunked"}
[debug] [2021-03-20T19:18:33.023Z] >>> [apiv2][query] GET https://firebase.googleapis.com/v1beta1/projects pageSize=100
[debug] [2021-03-20T19:18:35.619Z] Failed to make request: invalid json response body at https://firebase.googleapis.com/v1beta1/projects?pageSize=100 reason: Unexpected token < in JSON at position 0
[debug] [2021-03-20T19:18:37.235Z] FirebaseError: Failed to make request: invalid json response body at https://firebase.googleapis.com/v1beta1/projects?pageSize=100 reason: Unexpected token < in JSON at position 0
at Client.request (C:\Users\john tucker\AppData\Roaming\npm\node_modules\firebase-tools\lib\apiv2.js:109:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
[error]
[error] Error: Failed to list Firebase projects. See firebase-debug.log for more info.
I have already tried to logout and login and made sure that my app exists in the firebase console .
I also get this error when I type firebase init in the terminal :
(node:12720) UnhandledPromiseRejectionWarning: FirebaseError: Failed to make request to https://firebase-public.firebaseio.com/cli.json
at Client.doRequest (C:\Users\john tucker\AppData\Roaming\npm\node_modules\firebase-tools\lib\apiv2.js:211:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:12720) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:12720) [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.
You have to follow this steps to deploy your react app online with fire-base hosting :
npm run build => Run the following command to create a build directory with a production build of your app
npm install -g firebase-tools => To host your site with Firebase Hosting, you need the Firebase command-line tool (CLI). Run the following npm command to install the CLI on your system globally
firebase login => If you're not logged in, you'll be asked to enter the credentials for your google account.
firebase init => to initialize firebase in your react app
firebase deploy => Firebase will now run the deploying process and will give you a unique URL where your app is deployed
I'm developing something using Microsoft Graph.
At first, just some permission is given.
But I found it's not enough. I added more permission.
But it seems it's not working. Because after I log in, the Authorization web doesn't come out
I'm following the steps here to use Microsoft Graph. and I'm using ADv1
I've added "User.ReadBasic.All".
I'm trying to get information by "/users?$select=displayName,userPrincipalName".
The error is as below
BotFrameworkAdapter.processActivity(): 500 ERROR - [object Object]
botFrameworkAdapter.ts:607
(node:1752) UnhandledPromiseRejectionWarning: Error: [object Object]
at BotFrameworkAdapter.processActivity (c:\Users\XXXXXX\src\botFrameworkAdapter.ts:608:19)
at process._tickCallback (internal/process/next_tick.js:68:7)
warning.js:18
(node:1752) 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: 1)
warning.js:18
(node:1752) [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.
After updating the permissions, users and/or admins will have to consent again.
Click 'Grant admin consent for XXX' to grant admin consent.
Force user consent through a url request
https://login.microsoftonline.com/{tenant}/oauth2/authorize?
client_id={your_client_id}
&response_type=code
&response_mode=query
&resource=https://graph.microsoft.com
&state=12345
&prompt=consent
Refer to this document for more details.
logging error like: Unhandled Promise Rejection with Error: Network Error
Possible Unhandled Promise Rejection (id: 0):
Error: Network Error
Error: Network Error
at createError (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:79490:17)
at XMLHttpRequest.handleError (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:79398:16)
at XMLHttpRequest.dispatchEvent (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:17902:39)
at XMLHttpRequest.setReadyState (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:17657:20)
at XMLHttpRequest.__didCompleteResponse (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:17484:16)
at blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:17594:47
at RCTDeviceEventEmitter.emit (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:3480:37)
at MessageQueue.__callFunction (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:2386:44)
at blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:2156:17
at MessageQueue.__guardSafe (blob:http://localhost:8081/3aab7ec1-40be-4c43-864c-6474a71b00c9:2348:11)
This error comes when your device or emulator is not connected to internet and trying to make XMLHttpRequest with axios or fetch via device or emulator.
Please make sure you are connected on the same network on both your machine and your device. Also reverify that your debugger is running on localhost.