User talk:Beetstra

From Meta, a Wikimedia project coordination wiki
(Redirected from User talk:COIBot)
Jump to navigation Jump to search

LinkWatchers missing[edit]

Hi. COIBot is hanging around, though its mates the LiWas are missing. When you are next around and available, it would be great if you could kick whatever needs kicking. Thx.  — billinghurst sDrewth 11:49, 18 May 2018 (UTC)

All functioning. If you did something, thx.  — billinghurst sDrewth 00:06, 19 May 2018 (UTC)
I did, all bots were misbehaving at the moment. XLinkBot was basically dead, COIBot half blind, LiWa3 mute and UnBlockBot crashed. —Dirk Beetstra T C (en: U, T) 08:28, 19 May 2018 (UTC)

Link analyser issue?[edit]

COIBot is whining that linkanalyser is haning and restarting. It is also building up a backlog of reports, with none from the backlog processing.

Report of status

  • 2018/06/09 08:49 UTC

<COIBot> Syslogs: case: 226243 secs. coibot: 178 secs. commander: 0 secs. diffreader: 1179 secs. linksaver: 1 secs. output: 1 secs. parser: 2496 secs. script: -1 secs. special: 1937131 secs.

<LiWa3_1> Syslogs: diffreader: 83018 secs. linkanalyser: 15 secs. linkparser: 1262 secs. linkreporter: 232630 secs. linkwatcher: 25 secs. output: -1 secs. script: -1 secs.

<LiWa3_3> LW: 2 days, 16:37:15 hours active; RC: last 4 sec. ago; Reading ~ 825 wikis; Queues: P1=0; P2=7; P3=35 (537 / 613); A1=50; A2=0 (24 / 1509); M=0 - In LinkWatcher edit-backlog: 0 files (0 lines) and in analyser backlog: 854 files (213605 lines).

  • 2018/06/10 05:37 UTC

<COIBot> Syslogs: case: 301111 secs. coibot: 6 secs. commander: 1 secs. diffreader: 3438 secs. linksaver: 1 secs. output: 50 secs. parser: 5619 secs. script: -1 secs. special: 2011999 secs.

<LiWa3_2> Syslogs: diffreader: 41520 secs. linkanalyser: 216 secs. linkparser: 23149 secs. linkreporter: 307497 secs. linkwatcher: 1676 secs. output: -1 secs. script: -1 secs.

<LiWa3_3> LW: 3 days, 13:25:02 hours active; RC: last 4 sec. ago; Reading ~ 825 wikis; Queues: P1=0; P2=0; P3=0 (763 / 613); A1=235; A2=1301 (1084 / 1046); M=0 - In LinkWatcher edit-backlog: 0 files (0 lines) and in analyser backlog: 1238 files (309653 lines).

 — billinghurst sDrewth 05:46, 10 June 2018 (UTC)

I’ll try and have a look. —Dirk Beetstra T C (en: U, T) 08:49, 10 June 2018 (UTC)

User:COIBot/Local/êµ¬ë¯¸ì†¡ì •ì„œí¬ìŠ¤íƒ€ížìŠ¤.net[edit]

Can you have a look at this? Bot seems to be unhappy with punycodes... — regards, Revi 08:34, 12 July 2018 (UTC)

It is. I have to check this. There are more problems like this. —Dirk Beetstra T C (en: U, T) 13:32, 12 July 2018 (UTC)

Next steps for the wish “confirmation prompt for the rollback link”[edit]

Logo Feedback round in the Technical Wishes project.png

Hello, a while ago you participated in a feedback round about a proposal how accidental clicks on the rollback link could be avoided. Thanks again for sharing your thoughts and ideas!
Looking at the feedback and the rollback situation in different wikis, the development team decided how to approach this wish: As a default, most wikis won’t have a confirmation. But users who wish to have one, can enable it in their preferences, which will add a confirmation prompt to the rollback link on the diff page and on the list pages. The prompt won’t be a pop-up, but an inline prompt like for the thanks confirmation. You can read more about the planned solution and what influenced this decision on the project page. -- Best, Johanna Strodt (WMDE) (talk) 09:45, 16 July 2018 (UTC)

Encoding issues[edit]

Hello & hope that you're okay. I think the bot has some encoding issues at User:COIBot/Local/ I'm afraid I cannot be more specific :-( Regards, —MarcoAurelio (talk) 16:07, 16 July 2018 (UTC)

Yep, also see two threads up. I'll have another look at this, but debugging this on a terminal is near impossible. XLinkBot has the same problem, and I hope that my db does not have the same problem too... --Dirk Beetstra T C (en: U, T) 16:35, 16 July 2018 (UTC)
Thank you. Maybe some InnoDB or encoding? On our tools we did to fix some encoding issues. Maybe that helps? Best regards, —MarcoAurelio (talk) 09:51, 17 July 2018 (UTC)

webdetail link issues[edit]

I just clicked on the webdetail link for a link report, and it looks like that domain is being used by spammers. Link in the report is this. Something's not right - would you mind double-checking? Thanks! Ravensfire (talk) 02:38, 15 August 2018 (UTC)

@Ravensfire: I replaced it with the template from en.wikipedia, but notice now that reverseinternet also does not work anymore (but that is just a 404). We'll have to find some other places to get information on adsenses, webbugs and similar (@MER-C:. --Dirk Beetstra T C (en: U, T) 03:26, 15 August 2018 (UTC)
Thank ya, sir! Ravensfire (talk) 03:29, 15 August 2018 (UTC)
Found three sites, though only one overtly shows it as part of a url post
 — billinghurst sDrewth 04:21, 15 August 2018 (UTC)