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

Failed to process seeded cover art parameters: seedParameters.entries() is not iterable #773

Closed
liftarn opened this issue Jul 9, 2024 · 3 comments · Fixed by #784
Closed
Labels

Comments

@liftarn
Copy link

liftarn commented Jul 9, 2024

When I clock on cover art I get the message
"Failed to process seeded cover art parameters: seedParameters.entries() is not iterable"
If I click on the source it gets imported correctly. Interestingly on my other computer it works correctly.

@kellnerd
Copy link
Collaborator

When I clock on cover art

Can you expand on this please, I don't know which workflow you are using here on which website and for which cover art source?

Interestingly on my other computer it works correctly.

Without knowing the difference between your computers it is hard to help you here.

@kellnerd kellnerd added question Further information is requested mb_enhanced_cover_art_uploads labels Jul 21, 2024
@ROpdebee
Copy link
Owner

What browser (Firefox/Chrome/…) and userscript engine (Tampermonkey/Violentmonkey/Greasemonkey/…) are you using? Can you upgrade them to the latest version and check whether the problem persists?

NB: If it's Firefox, it might be related to violentmonkey/violentmonkey#1213 which was diagnosed as a Firefox bug involving Xrays and iterators.

@ROpdebee ROpdebee changed the title "Failed to process seeded cover art parameters" Failed to process seeded cover art parameters: seedParameters.entries() is not iterable Jul 27, 2024
@ROpdebee ROpdebee added bug Something isn't working and removed question Further information is requested labels Jul 27, 2024
@ROpdebee
Copy link
Owner

I managed to reproduce this with Greasemonkey on Firefox. The 2024.7.27 version released in #784 should fix this issue.

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

Successfully merging a pull request may close this issue.

3 participants