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

Update related_website_sets.JSON #387

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

Jp-Aqfer
Copy link

Adding new set for public registration
Looking to begin testing on RWS as soon as possible.
Thank you in advance

Adding new set for public registreation
Copy link

google-cla bot commented May 13, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link

It appears you have failed some tests. Here are your results:
The set associated with https://sackrace.ai was removed from the list, but https://sackrace.ai/.well-known/related-website-set.json does not return error 404.
The set associated with https://tolteck.com was removed from the list, but https://tolteck.com/.well-known/related-website-set.json does not return error 404.
The set associated with https://sapo.pt was removed from the list, but https://sapo.pt/.well-known/related-website-set.json does not return error 404.
The set associated with https://nvidia.com was removed from the list, but https://nvidia.com/.well-known/related-website-set.json does not return error 404.
The provided associated site is not an eTLD+1: https://retail.aqfer.com
The provided associated site is not an eTLD+1: https://demo.pxcel.net
The provided associated site is not an eTLD+1: https://app.aqfer.net
The provided service site is not an eTLD+1: https://demoping-aut-prod.aqfer.com
The provided service site is not an eTLD+1: https://t.retail.aqfer.com
The provided service site is not an eTLD+1: https://t3.aqfer.com
Encountered an inequality between the PR submission and the /.well-known/related-website-set.json file:
associatedSites was ['https://aqferproducts.com', 'https://retail.aqfer.com', 'https://demo.pxcel.net', 'https://app.aqfer.net'] in the PR, and ['https://aqferproducts.com', 'https://pxcel.net'] in the well-known.
Diff was: ['https://app.aqfer.net', 'https://demo.pxcel.net', 'https://pxcel.net', 'https://retail.aqfer.com'].
The listed associated site did not have https://aqfer.com listed as its primary: https://retail.aqfer.com
Experienced an error when trying to access https://demo.pxcel.net/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://app.aqfer.net/.well-known/related-website-set.json; error was: Expecting value: line 1 column 1 (char 0)
Experienced an error when trying to access https://demoping-aut-prod.aqfer.com/.well-known/related-website-set.json; error was: <urlopen error [Errno -2] Name or service not known>
Experienced an error when trying to access https://t.retail.aqfer.com/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Experienced an error when trying to access https://t3.aqfer.com/.well-known/related-website-set.json; error was: HTTP Error 404: Not Found
Unexpected error for service site: https://demoping-aut-prod.aqfer.com; Received error: HTTPSConnectionPool(host='demoping-aut-prod.aqfer.com', port=443): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fab5a8bdbd0>: Failed to establish a new connection: [Errno -2] Name or service not known'))
The service site https://t3.aqfer.com does not have an X-Robots-Tag in its header

@shuranhuang
Copy link
Collaborator

The rationale for the sites look like you might be using them for testing. I wanted to make sure that you're aware of the local testing capabilities for RWS. Instructions for doing so can be found here. We typically recommend this approach so that you don't have to wait for a pull request to be merged to continue your testing.

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

Successfully merging this pull request may close these issues.

2 participants