Please paste the console output

Do you mean to spend an hour to open all the objects again, or the new one you've added?

In T245428#5890825, @IKhitron wrote:

Do you mean to spend an hour to open all the objects again, or the new one you've added?

The console outputs that the feed is legal, all the edits are there, they are just not shown. - I need to know what it says
But, you should be able to type console.log( GlobalWatchlist.debugLog );, which will have something easy to copy and will take care of the objects

For example,

GlobalWatchlist@www.wikidata:getWikidataLabels wdlabels: index.php:195:11
{…}
​
Q17523682: Object { type: "item", id: "Q17523682", labels: {…} }
​
<prototype>: Object { … }
index.php:196:11

About the debugLog, where do you want me to paste it?

In T245428#5890847, @IKhitron wrote:

About the debugLog, where do you want me to paste it?

On Phabricator likely. Use either form 14 (for public paste) or form 45 (for private paste). You should be able to see the forms since I have now added you to Trusted-Contributors group.

Thanks a lot.
P10428

One more observation. I did a lot of tests in the last couple of hours, and can focus the problem much better.

1. Open the GW.
2. Open in other tabs and read all the shown diffs for some wiki.
3. Click refresh.
4. See the list is gone to globalWatch-col.
5. Wait until there will be at least one new edit from that wiki.
6. Click refresh.
7. Expected: The list moves from globalWatch-col up and shows the new edits.
8. Got: The list remains in globalWatch-col without showing edits.

@IKhitron looking through the paste, it seems like this isn't a bug with the script: at line 344, eg, you can see a refresh start, and the api response it gets is empty for all of the sites. This is the response before any processing by the script

I do not understand. Do you mean that you're going to remove the refresh button entirely, because api does not support its functionality? And there us nothing you can do?

In T245428#5891480, @IKhitron wrote:

I do not understand. Do you mean that you're going to remove the refresh button entirely, because api does not support its functionality? And there us nothing you can do?

No, I'm saying that, in this case, the refresh button is working fine, and its the api that isn't returning properly; i.e., this is an Upstream issue with MediaWiki-Action-API

Exactly what I said, you can't use the refresh button, because api does not return the right answer.

In T245428#5891488, @IKhitron wrote:

Exactly what I said, you can't use the refresh button, because api does not return the right answer.

But I'm not removing the refresh button

So it will remain there, but will not work?

In T245428#5891542, @IKhitron wrote:

So it will remain there, but will not work?

it should work. When it doesn't work, its because of an issue with the api, not the script

Nevermind why. The result is that the button does not do what it supposed to do.

Yes, you can. You can remove the Refresh button, because it can't work as promised. In any case, I'll try to find some time to investigate this. Seems quite impossible that api returns different answers in different tabs at the same time, depends on the screen layout, which this api even does not need to see. Maybe the api just gets wrong parameters from the script in this case - timestamp or something else and as a result of this return wrong answer. Especially when we can see the right answer on the console, and it must come from somewhere, it is new, so couldn't remain from before. @Masumrezarock100, can you help in this investigation, please?

Well, working on this in meta:User:IKhitron/Global Watchlist.js. Now I'm certain that the problem is in script, in api usage, and not in api itself. This what I have now on a console, while there is no wikidata in the list:

Continuing working. Opened two windows on hewiki with GL on the same wiki, emptied all, waited to a new edit. Clicked Refresh on the first, get nothing. Clicked F5 on the second, get the result. After running a query on both consules, get the same output:

var api = new mw.ForeignApi( 'https://ru.wikipedia.org/w/api.php' );
api.get( {
    action: 'query',
    list: 'watchlist',
    wlshow: 'unread'
} ).done( function ( data ) {
    console.log( data );
} );
Object { abort: abort(), state: state(), always: always(), catch: catch(), pipe: pipe(), then: then(), promise: promise(), progress: add(), done: add(), fail: add()
 }

{…}
​
batchcomplete: ""
​
query: {…}
​​
watchlist: (1) […]
​​​
0: Object { type: "edit", ns: 0, title: "Бердымухамедов, Гурбангулы Мяликгулыевич", … }
​​​
length: 1
​​​
<prototype>: Array []
​​
<prototype>: Object { … }
​
<prototype>: Object { … }

Hi, @DannyS712. Congrats. I can understand why you've declined all the future requests. But I do not see why to decline this. The main software engineering rule that I teach my students every year is "Never make red refactoring". If something is broken, you can't convert the script to the extension, you should make the script green first. Only if you're going to forget about the script code and write the extension from scratch. It's possible, but it's a waste of time. Not saying that it will be broken for script users in the four years that will take to write and deploy the extension.

In T245428#6215067, @IKhitron wrote:

Hi, @DannyS712. Congrats. I can understand why you've declined all the future requests. But I do not see why to decline this. The main software engineering rule that I teach my students every year is "Never make red refactoring". If something is broken, you can't convert the script to the extension, you should make the script green first. Only if you're going to forget about the script code and write the extension from scratch. It's possible, but it's a waste of time. Not saying that it will be broken for script users in the four years that will take to write and deploy the extension.

I'm planning on rewriting most of it from scratch, and this doesn't seem like it affects many users. Sorry, but I just don't have time to work on this. If you would like to submit a patch to fix it (just tell me what to change, or have a fork on meta with the fixed code) I'll take a look though

Well, I think it affects all the users, it's just too difficult to pay attention that the displayed data is wrong. A pity.