-
Notifications
You must be signed in to change notification settings - Fork 479
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
MarketPlace "supposed UTF-8 string is not valid UTF-8" #6705
Comments
what OS are you on? Cannot reproduce on my end |
Debian 11 Is there any way to look a bit deeper at what's throwing this error? I'm coming empty handed across all debug / verbosity / logging options here. |
One thing, in case it rings a bell to you -
(I only have the default MarketPlace and Docker's, which is empty) |
Hello @gbonfiglio, Identify corrupted app ID
Note the app ID, which fails to display, later I'll refer to this app as Get more info to help us solve the issue
You can find your MySQL username and password in Workaround to solve the issue
Run |
Hey Pavel, thanks for the update here - what would I be looking for exactly in the |
First two outputs in the meantime:
|
I expected the same error as Are you sure the command I know we had some charset issues when the MySQL changed default charset from You can try
If this doesn't help, please post here as a file attachment full output of |
I am not as I never tried it before, but the MarketPlace UI in Sunstone was definitely working as I pulled the Debian 12 image 10 days ago or so, now it's erroring out in the same way. This issue presented after the upgrade to 6.8, but disappeared afterwards (see #6390) with no action on my side. I have now disabled both marketplaces:
The error persists:
There are still some entries in the database, dump here: https://gist.github.com/gbonfiglio/395b785219f1be249a20e78410666b9f (none of those entries is familiar to me, must be auto-downloaded stuff) |
I've recovered it based on your suggestions above like this: 1 - Now list works. Waiting for the apps to be pulled again. I'm curious as to how/why those entries got stuck in my DB though? They seemed to be orphaned - I still have output of |
Glad to here it works. Thanks for the list of remaining apps - they are all from the DockerHub market. All of them registered in last month. Some of them contains UTF8 characters. I'm afraid that if you enable DockerHub market again, the error returns. I'll make a note for me for later, as I can't work on this now. Possible steps to reproduce:
|
Thankyou! Two more things for you:
Should I see something in the DockerHub marketplace? |
I forgot that the DockerHub marketplace was removed in release 6.10, you may safely delete it by
The corrupted marketapps were orphaned, because the |
Gone! In this case, shouldn't the 6.10 migration have killed it? |
Closing this, created more general issue, for possible charset bugs #6709 |
Description
After upgrading to 6.10, I'm back with the error described here #6390. When it previously occurred, it self-resolved after a few days and we dropped it there.
Adding
--verbose
doesn't actually get any relevant output, and nothing is written to log files in/var/log/one/
when this happens.I'm happy to collect more debug info if anyone can give me an hint here. Thanks!
To Reproduce
Expected behavior
The command completes with no errors.
Details
Additional context
Progress Status
The text was updated successfully, but these errors were encountered: