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

Import w3c/screen-wake-lock #252

Closed
xfq opened this issue Sep 29, 2022 · 4 comments
Closed

Import w3c/screen-wake-lock #252

xfq opened this issue Sep 29, 2022 · 4 comments
Assignees

Comments

@xfq
Copy link
Member

xfq commented Sep 29, 2022

We'd like to use repo manager for the w3c/screen-wake-lock repo. I tried using https://labs.w3.org/repo-manager/repo/import , but it emitted Cannot read properties of undefined (reading 'message'):

screen-wake-lock

Here are the errors in the console:

Failed to load resource: the server responded with a status of 500 ()
app.js:1 undefined
error @ app.js:1
app.js:1 TypeError: Cannot read properties of undefined (reading 'message')
    at Object.ID_2 (app.js:12:17533)
    at e._invokeCallback (app.js:4:28094)
    at e.dispatch (app.js:4:27896)
    at Object.error (app.js:1:633)
    at app.js:2:29479
error @ app.js:1

I'm using Chrome 106. Can anyone point me in the right direction? Thanks!

@deniak deniak self-assigned this Sep 29, 2022
@deniak
Copy link
Member

deniak commented Sep 29, 2022

Looking at your screenshot, it seems you have not provided enough rights when login with GH. Can you logout and login again but using the second link (see screenshot below)
Screen Shot 2022-09-29 at 15 52 14

@xfq
Copy link
Member Author

xfq commented Oct 4, 2022

Thanks for the hint Denis - you are right as usual. Closing.

@xfq xfq closed this as completed Oct 4, 2022
@anssiko
Copy link
Member

anssiko commented Oct 12, 2022

@xfq @deniak thanks for debugging this. Does the IPR check now work as expected for the w3c/screen-wake-lock repo?

I see two instances of w3c/screen-wake-lock in https://labs.w3.org/repo-manager/repos -- is that intentional?

@deniak
Copy link
Member

deniak commented Oct 13, 2022

The IPR check should work as expected for w3c/screen-wake-lock.
Looking at the database, I think the duplicate comes from the rename and an additional import.
As the repository manager can now handle repository renaming, it recorded the new name already. But there was another import of the repository that created the second record. I'll clean that up.

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

3 participants