Fails to parse cluster domains.
See original GitHub issueI’m running sitespeedio in a cluster, when running it against internal domains (which look like this: http://www-my-domain-master
) I get an error from third-party-web.
ERROR: Error: Unable to find domain in "www-my-domain-master"
at getDomainFromOriginOrURL (/usr/src/app/node_modules/third-party-web/lib/create-entity-finder-api.js:8:9)
at getEntityInDataset (/usr/src/app/node_modules/third-party-web/lib/create-entity-finder-api.js:18:18)
...
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Failed to parse repository - Common causes and quick fixes
A detailed guide on how to resolve errors related to "failed to parse ... An Elasticsearch cluster consists of a number of servers...
Read more >The VCF stretch cluster operation fails in the "Configure Fault ...
The VCF stretch cluster operation fails in the "Configure Fault Domains" task with the below exception (88710) | VMware KB.
Read more >Troubleshooting Amazon OpenSearch Service
If your OpenSearch Service domain enters a red cluster status, AWS Support might contact you to ask whether you want to address the...
Read more >Common Error Messages - Troubleshoot | Consul
consul agent -server -config-file server.json ==> Error parsing server.json: ... The client should be configured to join a cluster inside its local network....
Read more >Error messages - Resource Manager - Google Cloud
Many APIs also define their own domains, which identify API-specific errors that are not in ... parseError, The API server cannot parse the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We decided against validation altogether and now just return
undefined
when a URL is invalidthat’s an interesting idea! basically giving control over whether an error is thrown we’ll do something along those lines