Danbooru 2 Issues Topic

This isn't a major issue, but it's been over 2 weeks since v2.101.0 was released, yet it still shows v2.100.0 at the bottom of the page. I've looked at the code, and indeed the version number was changed. I'm just wondering if there's a disconnect somewhere that prevents the true version number from being displayed on the web page...?

BrokenEagle98 said:

This isn't a major issue, but it's been over 2 weeks since v2.101.0 was released, yet it still shows v2.100.0 at the bottom of the page. I've looked at the code, and indeed the version number was changed. I'm just wondering if there's a disconnect somewhere that prevents the true version number from being displayed on the web page...?

The currently released version != the currently deployed version.

Right now the version of Danbooru that is deployed is 2.100.0. Albert didn't deploy 2.101.0 yet.

Ah, it's just that when commits have been made on GitHub in the recent past, the effects have seemed to be immediate. Of course, maybe albert can select which commits get deployed immediately and which ones don't.

BrokenEagle98 said:

Ah, it's just that when commits have been made on GitHub in the recent past, the effects have seemed to be immediate. Of course, maybe albert can select which commits get deployed immediately and which ones don't.

Mostly likely he has manual deployment set up, so he would only issue the deploy command whenever he feels. I do the same sort of thing at work with Laravel Forge sometimes, I would just keep auto deploy deactivated and only deploy when I'm comfortable enough with the current state of the project. Or I turn on auto deploy and every time I push to Bitbucket Forge will run the deployment script that pulls in from the repo, updates dependencies, and runs migrations.

Click tagme, and it will gets statement timeout issue.

The recent tagging work has made it so that the first page of results for the search tagme includes posts from eight years ago, which puts a strain on the servers. Either use the id metatag to narrow your results or actually tag your stuff.

Sorry for making this search such a trouble^^'. But on my end, there is luckily no timeout.
But yes, tapnek is right. An Id search with tagme id:2000000..2500000 (example) throws the post eight years and older out.

I want to mention again the DeviantArt bug with the bookmarklet.
Just uploaded an artwork from paul_kwon but since I didn't know he is a banned artist, I uploaded it without noticing.
The problem is, that I don't get the correct artist name but lapres. Doesn't happen always, but this time it did.

Huh, are name changes not recorded anymore?

Dafuq?
http://i.imgur.com/iL5Ndfs.png
:c

-3?

Provence said:

Dafuq?
http://i.imgur.com/iL5Ndfs.png
:c

-3?

It's not reading -3 anymore. The servers probably hadn't caught up yet.

BrokenEagle98 said:

It's not reading -3 anymore. The servers probably hadn't caught up yet.

Yes, probaly.
But now it should display the correct number :3.

Type-kun said:

Huh, are name changes not recorded anymore?

That is the case. Not in records or profile pages anymore. I think name changes should at least be visible to Janitors and up, to reduce the possibility of abuse by users changing their names (if it comes up).

It seems, when one becomes a so called "super-voter", one can again vote for pictures that are already voted by the same users. (I tried that out on my own uploads and then on my favs. When I try to upvote agains fav pics, then this doesn't work. So only for pics I haven't already favorised.)
For example post #2081522 (I had already upvoted that one before some time and then did it again just before this post).
I don't think that this is intended :3.

Voting info for individual voters is thrown away after about a month, regardless of voting power.

Gollgagh said:

Voting info for individual voters is thrown away after about a month, regardless of voting power.

Oh? Where is this written here? Seems I've missed that part :c.

Provence said:

Oh? Where is this written here? Seems I've missed that part :c.

Probably not in the wiki, but yes, votes are periodically pruned, probably because the table becomes way too large otherwise. Judging by the code, comment votes are pruned after 2 weeks, and post votes after 1 month. That also makes it impossible to properly recalculate things when voting model changes.

This isn't a problem as much as an odd stylistic choice, but why is the post description just unceremoniously dumped beneath the picture now?

I could get if it was a title above the picture or something, but as it is, it's just some tiny italicized text repeating character and copyright info that's already more visible in the tags section.

I'm more curious as to why we even a description format like that when we have the tags shown to us right next to the image.

The post description has actually existed for a while in the browser tab heading. The only difference is that the same information is now being displayed below the pictures as well.