After configuring as show in the Readme fit in Hyperledger explore and making md5 to trust I have managed to come this far. I am currently using an Ubuntu 18.04 LTS server.
Test explorerpg.sql for DDL statements syntax verification
✓ should read the file explorerpg.sql for ddl statements
TAP version 13
# Test Results
ok 1 DROP USER IF EXISTS testuser;
not ok 2 WITH PASSWORD 'password';
---
operator: fail
at: <anonymous> (/home/hrm/hrm-explorer/app/test/postgrespgtest.js:2:5157)
stack: |-
Error: WITH PASSWORD 'password';
at Test.assert [as _assert] (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:228:54)
at Test.bound [as _assert] (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:80:32)
at Test.fail (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:322:10)
at Test.bound [as fail] (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:80:32)
at /home/hrm/hrm-explorer/app/test/postgrespgtest.js:2:5157
at processTicksAndRejections (internal/process/task_queues.js:97:5)
...
Test fails of: # tests 65, # pass 43, # fail 22
Moreover npm ERR! Failed at the hyperledger-explorer-test#0.3.9 test script
The error has been fixed in the recent Pull Request. You won't see it any more in the latest codebase (v1.1.0).
Related
When I try to execute Amplify GraphiQL Explorer via npm run start, it works initially via browser. But when I execute the GraphQL query after for a few seconds I get the following error:
Error:
[0] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set
AWS_SDK_LOAD_CONFIG=1
[0] at Timeout.connectTimeout [as _onTimeout]
(C:\Users\username\WebstormProjects\configurationservice\node_modules\serverless-plugin-
offline-dynamodb-stream\node_modules\aws-sdk\lib\http\node.js:69:15)
[0] at listOnTimeout (node:internal/timers:559:17)
[0] at processTimers (node:internal/timers:502:7)
[0]
[0] 1 deprecation found: run 'serverless doctor' for more details
[0] npm run local exited with code 1
I dont know the reason and I am concerned about whether I am supposed to use the parameter as well. Any help would be appreciated.
I found the problem. Credentials file in .aws folder should include [default] profile.
When trying to init Sanity I keep getting this error during the "resolving latest module versions" step.
Error: connect ETIMEDOUT xxx.xx.xx.xx:xxx
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
I saw here something about specifying the pool variable in options. Without access to the referred file, what can I do to complete the init?
Apparently, this specific error was caused by the use of a VPN or Proxy. Turning it off fixed it for me.
I have 230 tests and on my own machine its passed always, but on the github in github actions, tests is often falling with econnreset problem:
[0] 1) App [0] Get full search result [0] "before all" hook for "should search full list of collabraotions and users": [0] Error: connect ECONNRESET 127.0.0.1:36421 [0] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
And I don't know how fix this, and I will be happy if someone tell me reason and how fix it.
My througts was, that it caused by wrong ports, but after change ports to hardcode 3000, problem not left
UPDATE: node version is 16.14 on my own computer and in workflow
I have a Node.js app on a shared hosting plan. I found out that when I login using the Firebase Authentication layer, I get a 401 error. While digging deeper, I found the following error message on the server:
Error: error:02016002:system library:stat:No such file or directory
at Sign.sign (internal/crypto/sig.js:103:29)
at Object.sign (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/jsonwebtoken/node_modules/jwa/index.js:152:45)
at Object.jwsSign [as sign] (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/jsonwebtoken/node_modules/jws/lib/sign-stream.js:32:24)
at Object.module.exports [as sign] (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/jsonwebtoken/sign.js:204:16)
at ServiceAccountCredential.createAuthJwt_ (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/auth/credential.js:103:20)
at ServiceAccountCredential.getAccessToken (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/auth/credential.js:76:26)
at FirebaseAppInternals.getToken (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/firebase-app.js:65:73)
at AuthorizedHttpClient.send (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/utils/api-request.js:666:34)
at /home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/auth/auth-api-request.js:1472:37
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
opensslErrorStack: [
'error:0E07606D:configuration file routines:module_run:module initialization error',
'error:0E07B075:configuration file routines:ssl_module_init:ssl command section empty'
],
library: 'system library',
function: 'stat',
reason: 'No such file or directory',
code: 'ERR_OSSL_SYS_NO_SUCH_FILE_OR_DIRECTORY'
}
This error happens only when I restart the app and I sign in for the first time. Then, it happens at random occasion. How can I fix this?
NodeJS version 12.18.3
I contacted the hosting provider and found that the issues were tied to jsonwebtoken and firebase-admin packages.
after npm install , getting error like, i have checked every config file and also installed lodash manually after but still not working
error: A hook (`userconfig`) failed to load!
error: Error: In Sails v1.x, `sails.config.globals._` must be either `false` or an object (typically the value of `require('lodash')`)
at Sails.exposeGlobals (D:\Node_Project\POS\trunk\node_modules\sails\lib\app\private\exposeGlobals.js:47:44)
at Sails.wrapper [as exposeGlobals] (D:\Node_Project\POS\trunk\node_modules\#sailshq\lodash\lib\index.js:3250:19)
at emitNone (events.js:91:20)
at Sails.emit (events.js:185:7)
at Sails.emitter.emit (D:\Node_Project\POS\trunk\node_modules\sails\lib\app\private\after.js:50:11)
at D:\Node_Project\POS\trunk\node_modules\sails\lib\app\private\loadHooks.js:111:15
at Hook.initialize (D:\Node_Project\POS\trunk\node_modules\sails\lib\hooks\index.js:154:14)
at Hook.wrapper [as initialize] (D:\Node_Project\POS\trunk\node_modules\#sailshq\lodash\lib\index.js:3250:19)
at D:\Node_Project\POS\trunk\node_modules\sails\lib\hooks\index.js:88:16
at D:\Node_Project\POS\trunk\node_modules\sails\node_modules\async\dist\async.js:486:20
First : Make sure you've installed dependencies with npm install
Second : Check that this app was built for a compatible version of Sails.