search

bluesky-social / ozone

web interface for labeling content in atproto / Bluesky
https://atproto.com
Other
218 stars 15 forks source link

[BUG] Blank Repositories and Blank Reports #122

Open HenrickTheBull opened 1 month ago

HenrickTheBull commented 1 month ago

I'm having a new issue that causes blank reports and repositories. When I try to get a report or repository's contents I just get 400 errors in the console.

image image image

Not sure if this is because of the fixes that fixed #88

bnewbold commented 1 month ago

are you running a tagged Docker version, or from git? was this working before and now not, or is this a new install? can you check in the network tab of browser dev tools to see what the HTTP response error message actually is?

HenrickTheBull commented 1 month ago

are you running a tagged Docker version, or from git? was this working before and now not, or is this a new install? can you check in the network tab of browser dev tools to see what the HTTP response error message actually is?

Running the docker version, this is new behavior in the last couple weeks, I will get this data when I run across another blank report or repo.

HenrickTheBull commented 1 month ago

@bnewbold here is the data from the network tab, I just ran across an account that shows blank reports and a blank repo. image

bnewbold commented 1 month ago

@HenrickTheBull it is the "Response" tab in that screenshot which would have the helpful context; the "Headers" tab is selected instead.

(it might help with future debugging if we could configure the error message/payload to the dev console!)

HenrickTheBull commented 1 month ago

@HenrickTheBull it is the "Response" tab in that screenshot which would have the helpful context; the "Headers" tab is selected instead.

(it might help with future debugging if we could configure the error message/payload to the dev console!)

Here we go. I got it. This kinda makes labelers... useless.

image