Posted under General
This topic has been locked.
I appear to a have a phantom unread message. It says I have 1 Unread message but I check my inbox and the last message I received was in April and I had cleared all the others. So is this a bug or is my Inbox screwed up?
Edit: Nevermind I didn't even realize we had folder tagged as spam.
Mysterious_Uploader said:
This probably has already been answered before, but i've been trying multiple times to upload a picture, but i get greeted by
"413 Request Entity Too Large"
what's the problem?
There's a size limit of 35 MB, and a video length limit of 2 minutes. The second one can be bypassed by request with Admins (topic #14647), whereas the first one applies to all.
Is the bookmarklet broken for Twitter? It looks like Twitter recently did a redesign. Below is the error I got when I attempted to upload.
Did their URL size parameters ever have something like "4096x4096"? I tried "orig" and it still worked.
1. go to https://twitter.com/runawate56/status/1152165848691269632/photo/1
2. right-click on image and select View Image.
3. run bookmarklet.
4. Run bookmarklet.
5. fill in rating/tags and then upload.Get following error:
Upload #2475428
Source: https://pbs.twimg.com/media/D_1QufpVUAA95El?format=jpg&name=4096x4096
An error occurred: error: Downloads::File::Error - HTTP error code: 404 Not Found
app/logical/downloads/file.rb:56:in `http_get_streaming'
app/logical/downloads/file.rb:31:in `block in download!'
app/logical/downloads/file.rb:30:in `download!'
app/logical/upload_service/utils.rb:217:in `get_file_for_upload'
app/logical/upload_service.rb:51:in `start!'
app/controllers/uploads_controller.rb:55:in `create'
john1980 said:
Is the bookmarklet broken for Twitter? .
try instead
1. go to https://twitter.com/runawate56/status/1152165848691269632/photo/1
2. run bookmarklet.
3. fill in rating/tags and then upload.
fredgido said:
try instead
1. go to https://twitter.com/runawate56/status/1152165848691269632/photo/1
2. run bookmarklet.
3. fill in rating/tags and then upload.
In mobile, it forces mobile site usage in Chrome 75.
Well, post preprocessing appears to have broke again.
Full changelog: https://github.com/r888888888/danbooru/compare/production-2019.07.12-175439-utc...production-2019.08.05-190217-utc
https://twitter.com/asteroid_ill/status/1155420330128625664
I'm trying to upload the 3rd picture of the batch (Image #2 in Batch Upload), but when i click on it's preview in Batch Upload it gives me the first picture (Image #0). I Thought it was an image preview mistake, so i tried to upload it, but it says that it's actually the same image as Image #0?
https://twitter.com/amamotan2/status/1155684841024700416
When I put the first image through iqdb or SauceNao, I get two results: post #3565375 (correct one) and post #3580756 (which is the second image). Also the thumbnail for the second post is the same as the first one.
When I do the same for the second image, I get no links.
When I try to upload either of those images, "similar posts" list acts same as above, although the thumbnails are correct.
Why does this happen, and is it something on Danbooru's side?
Minor update:
worldendDominator said:
https://twitter.com/amamotan2/status/1155684841024700416
When I put the first image through iqdb or SauceNao, I get two results: post #3565375 (correct one) and post #3580756 (which is the second image). Also the thumbnail for the second post is the same as the first one.
When I do the same for the second image, I get no links.When I try to upload either of those images, "similar posts" list acts same as above, although the thumbnails are correct.
Why does this happen, and is it something on Danbooru's side?
It looks like post #3580756 was originally the first image in the batch but @RaisingK replaced it with the second image. SauceNao and iqdb.org don't track replacements so they won't notice if a post totally changes like that. Our own "find similar" should have picked up the change but for some reason it didn't.
Post preprocessing died again.
:3
inkuJerr said:
Post preprocessing died again.
:3
aka delayed jobs got stuck again at about 2019-08-09 06:18:29 UTC and need to be kicked. :<
