Danbooru 2 Issues Topic

RaisingK said:

@Moonspeaker, if you switched to Tampermonkey, your settings aren't going to get carried over, and all tweaks are disabled by default. They work for me.

What a mess. Figured out how to modify scripts to work with Greasemonkey 4, realized that not all scripts had carried over, realized there's no way to manually install local scripts yet, gave up and switched to Tampermonkey.

@RaisingK

Sorry you had to waste so much time wrestling with that problem.

Anyway, it isn't a matter of tweaks being disabled, it's a matter of the script itself being inactive. I have no interface right now to open a list of tweaks to modify. I opened up a Tampermonkey tab and checked for installed scripts, and it doesn't recognize any. I guess I need to reinstall the tweaks script?

Bookmarklet / Batch Uploader:

Tumblr posts are getting their source set to DATA[...]raw.[filename] instead of automatically redirecting to the Tumblr post page.

Kikimaru said:

Bookmarklet / Batch Uploader:

Tumblr posts are getting their source set to DATA[...]raw.[filename] instead of automatically redirecting to the Tumblr post page.

Already opened issue #3385 about it.

kittey said:

I’m pretty sure that your paginators not showing page numbers is due to the timeouts I explained. Basic users always had a lower timeout than Gold users and it didn’t get reduced. During the past few days, the database has been under a lot of stress from the recent update(s), so it’s been slower for everyone, but basic users run into timeouts more easily, even with inclusive searches. It’ll hopefully be back to normal soon.

BrokenEagle98 said:

To add onto what kittey said, I can't replicate any of your issues with an anonymous login on Internet Explorer. I tried every search you mentioned that had an issue, and all of them work just fine. Just for reference, Anonymous has the same timeout and tag restrictions as Member-level users (Help:Users).

Therefore, I'm guessing that there's something else going on.

Have you tried those searches on a different browser...? Additionally, you could try resetting the cache and cookies for this site, or resetting the browser itself.

It seems to be working in Chrome but not FireFox 47. Did a cache clear but I guess a cookie nuke might fix? Testing.

Nuked cookies and it worked. Logged in and it Doesn't work.

I don't get it. I'm even running noscript to reduce overhead.

Would having blacklists matter at all? Since I have a lot of them (107) but the search term I used has nothing that'd trip a Blacklist and it never caused problems before. Seems to be tied to logging in for me as Chrome breaks as soon as I logged in.

Zelinkokitsune said:

It seems to be working in Chrome but not FireFox 47. Did a cache clear but I guess a cookie nuke might fix? Testing.

Nuked cookies and it worked. Logged in and it Doesn't work.

I don't get it. I'm even running noscript to reduce overhead.

Would having blacklists matter at all? Since I have a lot of them (107) but the search term I used has nothing that'd trip a Blacklist and it never caused problems before. Seems to be tied to logging in for me as Chrome breaks as soon as I logged in.

The blacklist shouldn’t matter because it runs in your browser after the database query finished. NoScript shouldn’t have any influence for the same reason.

The browser or cookies shouldn’t have any influence on whether or not the searches time out, unless it’s something in your Danbooru user settings. The only relevant setting I see is the “Deleted post filter”, which adds an extra slowdown, but from what I see, it should be on for anonymous default users too. You could try switching it off, but then you’ll have to endure all the deleted posts. :-/

kittey said:

The blacklist shouldn’t matter because it runs in your browser after the database query finished. NoScript shouldn’t have any influence for the same reason.

The browser or cookies shouldn’t have any influence on whether or not the searches time out, unless it’s something in your Danbooru user settings. The only relevant setting I see is the “Deleted post filter”, which adds an extra slowdown, but from what I see, it should be on for anonymous default users too. You could try switching it off, but then you’ll have to endure all the deleted posts. :-/

Filter off fixed it... but I don't know why though. Guest users don't see deleted images either. I don't get it.

It really makes no sense at all.

Are you using Safebooru in one browser and Danbooru in another? I'm able to reproduce this on Safebooru with https://safebooru.donmai.us/posts?tags=1girl+solo. It effects every two tag query that I've tested.

Looks like a timeout issue, as kittey explained. 1girl solo rating:s times out for me on Danbooru even as a Builder. There was a recent code refactor in issue #3376 that probably broke something here.

evazion said:

Are you using Safebooru in one browser and Danbooru in another? I'm able to reproduce this on Safebooru with https://safebooru.donmai.us/posts?tags=1girl+solo. It effects every two tag query that I've tested.

Looks like a timeout issue, as kittey explained. 1girl solo rating:s times out for me on Danbooru even as a Builder. There was a recent code refactor in issue #3376 that probably broke something here.

Nope just using danbooru in both cases

Wanted to say that the Tumblr sources are still not fixed when you use the bookmarklet from there and you have to change the source manually.
It sometimes (always?) only links the image URL instead of the page URL you got it from. That means you just get the image when cliking the source.

Chiera said:

Wanted to say that the Tumblr sources are still not fixed when you use the bookmarklet from there and you have to change the source manually.
It sometimes (always?) only links the image URL instead of the page URL you got it from. That means you just get the image when cliking the source.

Was already brought up in issue #3385. Has been fixed, but not deployed yet.

Something's been wrong when I use the Similar search to look up identical images uploaded by other users. If I search a Pixiv image source for an image I uploaded before, the function works. But when I tested doing similar image searches for others' uploads, the function doesn't work for me - it just says, "No matches found" even though I know there's a match. I wound up trying to upload some images that didn't return a similar image, yet was uploaded by someone else. This is rather frustrating because I use the button all the time, and I use as many tags as possible before processing the upload.

I have Greasemonkey active, but I only use it for mass tag updates. I was also forced to upgrade to Firefox Quantum earlier this week, so I don't know if that affects it in some way.

Benit149 said:

Something's been wrong when I use the Similar search to look up identical images uploaded by other users. If I search a Pixiv image source for an image I uploaded before, the function works. But when I tested doing similar image searches for others' uploads, the function doesn't work for me - it just says, "No matches found" even though I know there's a match. I wound up trying to upload some images that didn't return a similar image, yet was uploaded by someone else. This is rather frustrating because I use the button all the time, and I use as many tags as possible before processing the upload.

I have Greasemonkey active, but I only use it for mass tag updates. I was also forced to upgrade to Firefox Quantum earlier this week, so I don't know if that affects it in some way.

Yeah lately the embedded Similar search has been pretty unreliable for all of us. The best you can do is use saucenao or IQDB yourself to search for a picture before you upload it, or give a glance at the artist's tag on danbooru if it has few pictures.

nonamethanks said:

Yeah lately the embedded Similar search has been pretty unreliable for all of us. The best you can do is use saucenao or IQDB yourself to search for a picture before you upload it, or give a glance at the artist's tag on danbooru if it has few pictures.

I looked at the artist's tag to find similar images yesterday. Hopefully this gets addressed soon since it's cumbersome to do it this way all the time.

Benit149 said:

Something's been wrong when I use the Similar search to look up identical images uploaded by other users. If I search a Pixiv image source for an image I uploaded before, the function works. But when I tested doing similar image searches for others' uploads, the function doesn't work for me - it just says, "No matches found" even though I know there's a match. I wound up trying to upload some images that didn't return a similar image, yet was uploaded by someone else. This is rather frustrating because I use the button all the time, and I use as many tags as possible before processing the upload.

I have Greasemonkey active, but I only use it for mass tag updates. I was also forced to upgrade to Firefox Quantum earlier this week, so I don't know if that affects it in some way.

nonamethanks said:

Yeah lately the embedded Similar search has been pretty unreliable for all of us. The best you can do is use saucenao or IQDB yourself to search for a picture before you upload it, or give a glance at the artist's tag on danbooru if it has few pictures.

Benit149 said:

I looked at the artist's tag to find similar images yesterday. Hopefully this gets addressed soon since it's cumbersome to do it this way all the time.

Created issue #3386 for the above IQDB problem.

I recently noticed that post changes are taking a minute or two to show up in the versions page. That's new, right?

RaisingK said:

I recently noticed that post changes are taking a minute or two to show up in the versions page. That's new, right?

See issue #3378.

RaisingK said:

I recently noticed that post changes are taking a minute or two to show up in the versions page. That's new, right?

Yeah, it's been like that since the recent downtime. The most annoying thing with this is if someone adds a tag and you add another before the post version table updates it will act like you edited the version before they added that tag so you will "remove" their tag.

Zelinkokitsune said:

Searched "northern_ocean_hime seaport_hime" get no page mobility and I know it's got a LOT of art. So I kludge together a view page 10 of search results and it resolves to showing page 10 of results with the ability to go back to page 9 then back to page 8 all the way back to the front but not able to go forwards

It seems to be on all two tag searches now.

Worked out fine yesterday so not sure what broke today

Edit: Screenshot

Edit: Searching for "northern_ocean_hime" or any single tag gives proper behavior

Actually, I think Zelinkokitsune might be on to something here. I managed to replicate the same behavior on my builder account with this search and the deleted post filter on:
original -tag2 -tag3 -tag4 -tag5 -tag6 -tag7 -tag8 -tag9 -tag10 -tag11 -tag12

The paginator shows no page numbers, arrows to go forward aren’t linkified. Adding &page=2 to the URL shows the next page, which has working arrows to go backward but not forward.

Replacing original with any other existing tag shows exactly the same behavior, be it a big tag like touhou or a small tag like magic_school_uniform.

Note that all eleven excluded tags don’t even exist, so the extra load on the database should be pretty much zero.
The search for original shows the paginator as expected and so does a search for original -tag2 -tag3 -tag4 -tag5 -tag6 -tag7 -tag8 -tag9 -tag10 -tag11 (just one nonexistent tag less).

As a builder, my database timeout should be 9 seconds, but the page only takes about two seconds to load, so I’m suspecting that this is a different problem, especially because the “forward” arrows don’t work, even though they should be even if the paginator query times out.

Switching the deleted post filter off fixes the searches with eleven excluded tags.

Any ideas? As a wild guess, I’d say it might be counting the deleted post filter as a 13th tag for some reason and then not running the query at all because it’s above the limit, but only for the paginator for some reason?

Could someone with a Gold account run this search with the deleted post filter on and off and report whether it works?
original -tag2 -tag3 -tag4 -tag5 -tag6

See issue #3387. Your guess is exactly right, the deleted post filter option is adding -status:deleted to the search, which may put it over the tag limit. When this happens we swallow the error and return zero for the page count, which results in an empty paginator.

The empty paginator bug has been fixed. Well, partly. Two tags searches on Safebooru work again, and so do two tag searches when the "Deleted post filter" option is turned on. The bug with certain pools having empty paginators (pool:1537, among others) is not fixed, however. It should be in the next update.

The upside is that the rating:s and the -status:deleted tags are now free. They don't count against your tag limit. Note that status:deleted is also free, and has been for quite a while, but I don't think it's ever been documented.