Talk:Automated Edits/b-jazz-bot
one changeset
Why cant changesets be grouped in an area or group a number of items in one group or by a day. spitting each change (just changing a letter) as different change in this case makes it hard to review changes harder. Also creates lot of unnecessary overhead for same repeated change. (edit: contributed by user:Muzirian)
--
I actually agree with you on this, but I've gotten complaints from others before about making too many changes at once in a changeset and how that makes it more difficult to revert changes. Unfortunately, there are no hard-and-fast guidelines that say you should limit a change to this many square kilometers, or this number of changes in a changeset, so I have nothing to point to in defense so I've given up and just do one change per changeset. --B-jazz (talk) 15:53, 19 October 2023 (UTC)
Check error messages and HTTP status for the redirect target
For example, v2 of node 2869095796 used to link to http://www.zechecarl.de/gastronomie.html , which redirects to https://www.zechecarl.de/gastronomie.html , which in turn just displays an error message. Your bot created v3 with https://www.zechecarl.de/gastronomie.html , even though this URL returns 404 to a HEAD request. Is there a way to avoid problems like this? Maybe your bot could check the HTTP status code? --BiBaBoChum (talk) 22:43, 1 December 2023 (UTC)
- Thanks for the report BiBaBoChum. There is an issue filed in my gitlab repo for this type of problem. It is rather old, but I'm starting to put more time into improvements, and this is one of the more interesting issues to get fixed for me. --B-jazz (talk) 23:30, 1 December 2023 (UTC)
- Thanks for the quick response! I'm glad to hear that you're already aware of the issue. I'd be happy to help, but your gitlab profile is set to private, so the link doesn't work, and instead I only see the message "This user has a private profile". --BiBaBoChum (talk) 23:39, 1 December 2023 (UTC)
- I used a "private" browsing window and was able to open issue #8 (the earlier link) and read the issue just fine. I then tried clicking on the "b-jazz" Assignee link though and was given the error you mentioned. Is there some reason you would need to view the profile as well? --B-jazz (talk) 17:46, 2 December 2023 (UTC)
- Huh, something really weird must be going on. I just tried again to open the link, it still says 404. When I try to do it in a "private browsing" tab, it asks me log in while refusing to show the project, and when I log in I see the 404 screen again.
curl -I https://gitlab.com/b-jazz/https%20all%20the%20things/-/issues/8
also gives a 302 redirect to the login page, instead of 200. The profile is only related because I thought that might be the reason for it all. Anyway, I hope you can make sure that your bot doesn't make any further bad updates to OSM. --BiBaBoChum (talk) 18:26, 2 December 2023 (UTC)
- Huh, something really weird must be going on. I just tried again to open the link, it still says 404. When I try to do it in a "private browsing" tab, it asks me log in while refusing to show the project, and when I log in I see the 404 screen again.
- I used a "private" browsing window and was able to open issue #8 (the earlier link) and read the issue just fine. I then tried clicking on the "b-jazz" Assignee link though and was given the error you mentioned. Is there some reason you would need to view the profile as well? --B-jazz (talk) 17:46, 2 December 2023 (UTC)
- Thanks for the quick response! I'm glad to hear that you're already aware of the issue. I'd be happy to help, but your gitlab profile is set to private, so the link doesn't work, and instead I only see the message "This user has a private profile". --BiBaBoChum (talk) 23:39, 1 December 2023 (UTC)