-
Notifications
You must be signed in to change notification settings - Fork 37
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
Ozone instance not responding to label changes, moderation queue emptied after container restart #228
Comments
Hi, did you manage to solve the problem with the labels? I add labels in ozone but no changes happen in the application. I have no idea anymore, maybe you can guide me? |
I hit this initially because my labels were malformed (mixed case).
Once I got the config JSON set up right, it worked fine
…On Mon, Dec 30, 2024, 8:46 AM Michal-Tomasz ***@***.***> wrote:
Hi, did you manage to solve the problem with the labels? I add labels in
ozone but no changes happen in the application. I have no idea anymore,
maybe you can guide me?
—
Reply to this email directly, view it on GitHub
<#228 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRDNC3QWW6RUYOD2VJTF332IFFDBAVCNFSM6AAAAABRWFF2V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGUYDMMBYGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
and you can send me a fragment of your JSON or I can send you mine because it seems to be OK and yet it does not work properly |
Do you see your labels ok on the service account's profile page in the app?
If so, the JSON is fine imo and something else is your problem
…On Mon, Dec 30, 2024, 11:31 AM Michal-Tomasz ***@***.***> wrote:
and you can send me a fragment of your JSON or I can send you mine because
it seems to be OK and yet it does not work properly
—
Reply to this email directly, view it on GitHub
<#228 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRDNCYPTCEZDUGHY3QLXAT2IFYPTAVCNFSM6AAAAABRWFF2V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGY4TAMRVGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
yes the labels are visible in the account, the default values and everything is visible. So I have to look somewhere else. I found such a problem maybe it is here? |
That looks suspect for sure. I have not seen it myself.
…On Mon, Dec 30, 2024 at 11:38 AM Michal-Tomasz ***@***.***> wrote:
yes the labels are visible in the account, the default values and
everything is visible. So I have to look somewhere else. I found such a
problem maybe it is here?
@repo <https://github.com/repo> undefined
https://imgur.com/QPR3ADd
—
Reply to this email directly, view it on GitHub
<#228 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRDNCZ7K2OQM3IAGSPL2DL2IFZJLAVCNFSM6AAAAABRWFF2V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGY4TOMJYGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Since yesterday evening, my Ozone instance has stopped "working" correctly. Despite adding or removing labels, no changes appear to take effect.
In an attempt to resolve the issue, I restarted the container. However, after rebooting, I found that my moderation queue had been completely cleared. Is this expected behavior?
Aside from the empty moderation queue, could the initial issue with unresponsive labels be due to a sudden influx of new users?
Steps to reproduce:
Expected behavior:
Thank you in advance for your assistance.
The text was updated successfully, but these errors were encountered: