I'm having the following problem when I enter the page, I don't know what part of Elastic Search is causing it
NestedError: Error while validating Authorization header at
boService.getSignKey.then.then.catch (/var/youmarket/fo-search/src/middleWares/validation.js:32:28)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:182:7)
Caused By: JsonWebTokenError: jwt malformed
at Object.module.exports [as verify] (/var/youmarket/fo-search/node_modules/jsonwebtoken/verify.js:49:17)
at Promise (/var/youmarket/fo-search/src/middleWares/validation.js:16:9)
at new Promise (<anonymous>)
at jwtPromise (/var/youmarket/fo-search/src/middleWares/validation.js:6:10)
at boService.getSignKey.then (/var/youmarket/fo-search/src/middleWares/validation.js:26:23)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:182:7)
Related
This is what I get in the stack trace from launching chrome: Cypress version is 7.3.:
Title: Error launching browser
Message: Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
This usually indicates there was a problem opening the Chrome browser.
The CDP port requested was 29079.
Error details:
Error: connect ECONNREFUSED 127.0.0.1:29079
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
Stack trace:
Error: Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
This usually indicates there was a problem opening the Chrome browser.
The CDP port requested was [33m29079[39m.
Error details:
Error: connect ECONNREFUSED 127.0.0.1:29079
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
at get (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\lib\errors.js:988:15)
at Object.throwErr [as throw] (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\lib\errors.js:1006:9)
at C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\lib\browsers\protocol.js:106:21
at tryCatcher (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:547:31)
at Promise._settlePromise (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:604:18)
at Promise._settlePromise0 (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:649:10)
at Promise._settlePromises (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:725:18)
at _drainQueueStep (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:93:12)
at _drainQueue (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:86:9)
at Async._drainQueues (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:15:14)
at processImmediate (internal/timers.js:461:21)
I have spoken to the support team and they currently do not have any protocols in place that would block cypress from launching chrome. I have also looked at an earlier solution in stack overflow where you go into ext/files to comment out the localhost address but still to ano avail. Can anyone please help??
I am creating a website with Nuxt, graphql and strapi.
Locally with works well. I then deploy the backend in heuroku with mlab addon and also all good.
Went to netlify with the heuroku link and deploy it there( follow a tutorial). It said deployed successful but when I open the page it says page not found. I went to see the deploy log and there is an error:
Error: Network error: request to http://localhost:1337/graphql failed, reason: connect ECONNREFUSED 127.0.0.1:1337
10:16:00 AM: at new ApolloError (/opt/build/repo/node_modules/apollo-client/bundle.umd.js:92:26)
10:16:00 AM: at /opt/build/repo/node_modules/apollo-client/bundle.umd.js:1588:34
10:16:00 AM: at /opt/build/repo/node_modules/apollo-client/bundle.umd.js:2008:15
10:16:00 AM: at Set.forEach (<anonymous>)
10:16:00 AM: at /opt/build/repo/node_modules/apollo-client/bundle.umd.js:2006:26
10:16:00 AM: at Map.forEach (<anonymous>)
10:16:00 AM: at QueryManager.broadcastQueries (/opt/build/repo/node_modules/apollo-client/bundle.umd.js:2004:20)
10:16:00 AM: at /opt/build/repo/node_modules/apollo-client/bundle.umd.js:1483:29
10:16:00 AM: at processTicksAndRejections (internal/process/task_queues.js:97:5)
Any idea how to fix this? I search but couldn't find any answer that helped me.
Thank you
It should be referencing the Heroku url. You need to change your database.js for Heroku. https://strapi.io/documentation/3.0.0-beta.x/deployment/heroku.html
Everytime I'm trying to publish an app with sidekick I'm getting the same error:
--> starting at object with constructor 'Error'
--- property 'errors' closes the circle
at JSON.stringify (<anonymous>)
at process.target._send (internal/child_process.js:778:25)
at process.target.send (internal/child_process.js:676:19)
at MessageService.sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/message-service.js:34:21)
at sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:13:24)
at sendErrorMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:19:9)
at /opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:36:17
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at emitUnhandledRejectionWarning (internal/process/promises.js:141:15)
at processPromiseRejections (internal/process/promises.js:203:11)
at processTicksAndRejections (internal/process/task_queues.js:94:32)
(CLI) (node:17346) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'Error'
--- property 'errors' closes the circle
at JSON.stringify (<anonymous>)
at process.target._send (internal/child_process.js:778:25)
at process.target.send (internal/child_process.js:676:19)
at MessageService.sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/message-service.js:34:21)
at sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:13:24)
at sendErrorMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:19:9)
at /opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:36:17
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:17346) [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.
at emitDeprecationWarning (internal/process/promises.js:153:11)
at processPromiseRejections (internal/process/promises.js:205:13)
at processTicksAndRejections (internal/process/task_queues.js:94:32)
Version: 1.19.2-v.2019.11.18.2 (latest)
NativeScript CLI version: 6.2.2
CLI extension nativescript-cloud version: 1.19.3
CLI extension nativescript-starter-kits version: 0.3.5
node: v12.13.1
I've tried downgrade the node verson, to 10.12.0, still getting the same error
mouseMove is not working in firefox with the latest versions of Firefox, geckodriver, and protractor. Same code works fine for chrome 77.
I have the following environment:
Node: v10.16.3
Protractor: 5.4.2
Geckodriver: v0.25.0
firefox: 69.0.1 (64-bit)
browser.actions().mouseMove(element(by.xpath('//app-admin-panel/div/div/div/div[2]/table/tbody/tr/td[1]'))).perform();
This code snippet should hover over the specified element, but it throws the following error:
Message:
Failed: HTTP method not allowed
Stack:
WebDriverError: HTTP method not allowed
at parseHttpResponse (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:536:11)
at doSend.then.response (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: mouseMove
at Driver.schedule (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:807:17)
at actions.map.action (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\actions.js:124:23)
at Array.map (<anonymous>)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\actions.js:123:29
at TaskQueue.execute_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3084:14)
at TaskQueue.executeNext_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3067:27)
at asyncRun (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2927:27)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:668:7
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: ActionSequence.perform
at ActionSequence.perform (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\actions.js:122:33)
at UserContext.<anonymous> (E:\Office\Protractor\Wallboard\Smoketest.js:39:207)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:112:25
at new ManagedPromise (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1077:7)
at ControlFlow.promise (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2505:12)
at schedulerExecute (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:95:18)
at TaskQueue.execute_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3084:14)
at TaskQueue.executeNext_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3067:27)
at asyncRun (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2974:25)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:668:7
From: Task: Run it("Make a Copy of Dashboard") in control flow
at UserContext.<anonymous> (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:94:19)
From asynchronous test:
Error
at Suite.<anonymous> (E:\Office\Protractor\Wallboard\Smoketest.js:38:5)
at Object.<anonymous> (E:\Office\Protractor\Wallboard\Smoketest.js:2:1)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
4 specs, 1 failure
Finished in 21.836 seconds
[11:41:20] I/launcher - 0 instance(s) of WebDriver still running
[11:41:20] I/launcher - firefox #01 failed 1 test(s)
[11:41:20] I/launcher - overall: 1 failed spec(s)
[11:41:20] E/launcher - Process exited with error code 1
It's a known issue (not sure if they fixed it yet) for FF.
I suggest you to use this https://www.npmjs.com/package/protractor-firefox-support
solved by updating direct connect value to false in protractor config
in case of chrome set it to true for local testing
directConnect: false
Timeout when uploading HeroCard to the bot framework on messenger channel.
Error: connect ETIMEDOUT 40.121.91.199:443
at Object.exports._errnoException (util.js:1007:11)
at exports._exceptionWithHostPort (util.js:1030:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
When uploading seeing this error as well
Error: Request to 'https://facebook.botframework.com/v3/conversations/1184220421
633853-1103485719738974/activities/mid.1470863624883%3Ae1dcd9f8a2c3d74b52' failed: [500] Internal Server Error`