Skip to content
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

"/artwork" API endpoints throwing the 500 error ("Internal server error") on production server #24

Open
trivialworks opened this issue Jul 19, 2021 · 2 comments

Comments

@trivialworks
Copy link
Collaborator

500 error is coming on the production server. I have attached the screenshots for it. Please have a look.

Error:

Error: 1014: Priority is too low: (1330904335908 vs 1330666336494): The transaction has too low priority to replace another transaction already in the pool.
    at RpcCoder._checkError (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/@polkadot/rpc-provider/coder/index.cjs:84:13)
    at RpcCoder.decodeResponse (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/@polkadot/rpc-provider/coder/index.cjs:47:10)
    at WsProvider.value (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/@polkadot/rpc-provider/ws/index.cjs:239:90)
    at W3CWebSocket.value [as onmessage] (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/@polkadot/rpc-provider/ws/index.cjs:219:153)
    at W3CWebSocket._dispatchEvent [as dispatchEvent] (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/yaeti/lib/EventTarget.js:107:17)
    at W3CWebSocket.onMessage (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/websocket/lib/W3CWebSocket.js:234:14)
    at WebSocketConnection.<anonymous> (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/websocket/lib/W3CWebSocket.js:205:19)
    at WebSocketConnection.emit (node:events:365:28)
    at WebSocketConnection.emit (node:domain:470:12)
    at WebSocketConnection.processFrame (/home/bas/app_c6b0c100-24f3-4e70-ad0e-ba8f755e5bf8/node_modules/websocket/lib/WebSocketConnection.js:554:26)

image (7)
image (6)

@danforbes
Copy link
Contributor

@trivialworks - please include exact steps to reproduce this problem and also point out the places in the code that are encountering the errors.

@trivialworks
Copy link
Collaborator Author

Just for your reference, I have created a video for it. Please have a look.
https://www.loom.com/share/bb96a9fc5e664ca2b53c68b4c3509ff4

Here is the curl request.

curl 'https://production.svc.blockchain.art/artwork'
-H 'Connection: keep-alive'
-H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"'
-H 'Accept: application/json, text/plain, /'
-H 'sec-ch-ua-mobile: ?0'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.164 Safari/537.36'
-H 'Content-Type: application/json;charset=UTF-8'
-H 'Origin: http://localhost:3000'
-H 'Sec-Fetch-Site: cross-site'
-H 'Sec-Fetch-Mode: cors'
-H 'Sec-Fetch-Dest: empty'
-H 'Referer: http://localhost:3000/'
-H 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8'
--data-raw $'{"galleryId":13,"artistId":14,"description":"There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, ","year":"2021","numAp":2,"url":"ipfs://ipfs/Qmf44Mac7vcNdCEgxGntJbhwaDnnB4MCetYyygNBUr4gn5","name":"Where does it come from","max":6,"symbol":"7e1d0adc-e71b-45d7-bd31-d5f7ca0f70dc","type":"image/jpeg"}'
--compressed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants