We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At some point I've made a mistake.
Submitted an item in the format:
ipfs/QmUq97VrrNX2MuoWeygCLVDo4bt5TPPg2DyfvS2yyz4xSM/item.json
Rather than:
/ipfs/QmUq97VrrNX2MuoWeygCLVDo4bt5TPPg2DyfvS2yyz4xSM/item.json
(note the / at the beginning)
/
It causes error in Chrome Dev Tools:
GET https://ipfs.kleros.ioipfs/QmWhSVtvmWdoBPCqsL6SDtPiqvtWVjaqqNAwaZYNQ9BFL6 net::ERR_NAME_NOT_RESOLVED
⛔️ Kleros hosted: https://curate.kleros.io/tcr/5/0x12B024E0F19Fc27CED2e50A888898304863500E0?registered=true
✅ Localhost: http://localhost:3000/tcr/5/0x12B024E0F19Fc27CED2e50A888898304863500E0?registered=true
Suprisingly, it works allright on localhost.
Probably, localhost has different settings than production deployment.
Production deployment should have some "graceful degradation" so that one wrong item does not make entire list unusable.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
At some point I've made a mistake.
Submitted an item in the format:
ipfs/QmUq97VrrNX2MuoWeygCLVDo4bt5TPPg2DyfvS2yyz4xSM/item.json
Rather than:
/ipfs/QmUq97VrrNX2MuoWeygCLVDo4bt5TPPg2DyfvS2yyz4xSM/item.json
(note the
/
at the beginning)It causes error in Chrome Dev Tools:
GET https://ipfs.kleros.ioipfs/QmWhSVtvmWdoBPCqsL6SDtPiqvtWVjaqqNAwaZYNQ9BFL6 net::ERR_NAME_NOT_RESOLVED
⛔️ Kleros hosted: https://curate.kleros.io/tcr/5/0x12B024E0F19Fc27CED2e50A888898304863500E0?registered=true
✅ Localhost: http://localhost:3000/tcr/5/0x12B024E0F19Fc27CED2e50A888898304863500E0?registered=true
Suprisingly, it works allright on localhost.
Probably, localhost has different settings than production deployment.
Production deployment should have some "graceful degradation" so that one wrong item does not make entire list unusable.
The text was updated successfully, but these errors were encountered: