[00:00:46] is this big json blob on the pages always there? :p [00:04:41] hi SothoTalKer, instead of parsing html, you should try parsing json : eg : https://www.wikidata.org/wiki/Special:EntityData/Q42.json or you can try other formats : rdf, ttl, nt [00:06:35] considering the json is on every page already. I did not intend to make it a full rewrite, though :D [00:07:26] rewrite ? [00:09:59] well, the current code uses var exp = $('div.wb-claim-section-P'+p+' div.valueview-value') ; [00:11:03] oh ok [00:12:08] i assume, it's from some good old times, when it was differently stored/displayed. I might have to switch to json, though. [00:14:00] it all depends what you wanna do [00:14:32] writing a query and exporting the result may be easier [00:15:57] unless you're writing gadgets [00:16:41] where it makes sense to work on an item page [00:17:09] so many use cases :) [00:22:42] melderick: more like a gadjet, yes [00:22:50] ye, its late (: [00:24:28] what the code tries to do is compare the values from the page with external values and colorcode them. but since it cannot read the values from the page at all, the rest does not work either. [00:24:35] and i want colors :( [00:26:16] i see [00:33:51] i already saw that every page contains a json blob at the start. I'm now wondering how to access that. It might be better to use the json directly. It's only one query more for a page and i could save the json object and use it for later. [00:40:01] ah yeah never saw that there was a json blob on the html page [00:40:19] wonder what's the point is [00:40:30] maybe to update the page [00:40:46] it stores all kind of configuration data also. [00:41:03] that makes sense [01:00:39] ah well, i just use a simple getJSON and filter it for the claims. Then i can use that for comparison. but not today (: [05:02:43] PROBLEM - WDQS HTTP Port on wdqs1009 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 380 bytes in 0.001 second response time [05:03:15] PROBLEM - Blazegraph Port for wdqs-categories on wdqs1009 is CRITICAL: connect to address 127.0.0.1 and port 9990: Connection refused [05:03:19] PROBLEM - Blazegraph Port for wdqs-blazegraph on wdqs1009 is CRITICAL: connect to address 127.0.0.1 and port 9999: Connection refused [05:03:35] PROBLEM - Blazegraph process -wdqs-categories- on wdqs1009 is CRITICAL: PROCS CRITICAL: 0 processes with UID = 499 (blazegraph), regex args ^java .* --port 9990 .* blazegraph-service-.*war [05:03:55] PROBLEM - Check systemd state on wdqs1009 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [05:04:25] PROBLEM - Blazegraph process -wdqs-blazegraph- on wdqs1009 is CRITICAL: PROCS CRITICAL: 0 processes with UID = 499 (blazegraph), regex args ^java .* --port 9999 .* blazegraph-service-.*war [05:09:35] RECOVERY - Blazegraph process -wdqs-blazegraph- on wdqs1009 is OK: PROCS OK: 1 process with UID = 499 (blazegraph), regex args ^java .* --port 9999 .* blazegraph-service-.*war [05:13:27] PROBLEM - Blazegraph process -wdqs-blazegraph- on wdqs1009 is CRITICAL: PROCS CRITICAL: 0 processes with UID = 499 (blazegraph), regex args ^java .* --port 9999 .* blazegraph-service-.*war [05:19:59] RECOVERY - Blazegraph Port for wdqs-categories on wdqs1009 is OK: TCP OK - 0.000 second response time on 127.0.0.1 port 9990 [05:20:21] RECOVERY - Blazegraph process -wdqs-categories- on wdqs1009 is OK: PROCS OK: 1 process with UID = 499 (blazegraph), regex args ^java .* --port 9990 .* blazegraph-service-.*war [05:20:41] RECOVERY - Check systemd state on wdqs1009 is OK: OK - running: The system is fully operational [05:20:45] RECOVERY - WDQS HTTP Port on wdqs1009 is OK: HTTP OK: HTTP/1.1 200 OK - 448 bytes in 0.058 second response time [05:21:11] RECOVERY - Blazegraph process -wdqs-blazegraph- on wdqs1009 is OK: PROCS OK: 1 process with UID = 499 (blazegraph), regex args ^java .* --port 9999 .* blazegraph-service-.*war [05:21:21] RECOVERY - Blazegraph Port for wdqs-blazegraph on wdqs1009 is OK: TCP OK - 0.000 second response time on 127.0.0.1 port 9999 [11:53:34] SothoTalKer: you can get the json with mw.hook("wikibase.entityPage.entityLoaded").add(function (entity) { ... }); [11:54:40] (there's also mw.config.get("wbEntity"); but that's deprecated) [16:32:50] Is it allowed to create new items in automatic tests? (on test.wikidata ofc)