[06:51:56] o/ [07:18:24] o/ welcome back! :-) [07:28:09] thanks! :) [07:28:53] reading emails and backscrolls but if there's anything important you think I should look at quickly please let me know :) [07:34:22] dcausse: welcome back! [07:35:37] thx! [10:03:35] lunch [14:42:37] dcausse: I'm looking at T337296 (last comment). I suspect the query in question is failing due to data or data size, but not because of federation. Is there a simple / generic way to test SPARQL federation? Like a query doing a remote count of triple, similar to the `ASK { ?x ?y ?z }` we use for readiness probe? [14:42:38] T337296: Allow federated queries with the NLG endpoint (data.nlg.gr) - https://phabricator.wikimedia.org/T337296 [14:43:06] gehel: looking [14:46:51] gehel: no this service seems dead, wrong cert and failing with 500 even for simple queries: curl -k -XPOST --data-urlencode "query=select * { } LIMIT 1" https://data.nlg.gr/sparql [14:48:47] weird, it seems to work with the default example query on https://data.nlg.gr/query [14:51:26] ok, this needs some digging into! [14:52:50] it needs a "Accept:application/sparql-results+json,*/*;q=0.9" header to work [14:53:06] not sure we can force blazegraph to do this [14:53:49] this one works: curl -k -XPOST -H"Accept:application/sparql-results+json" --data-urlencode "query=select * { } LIMIT 1" https://data.nlg.gr/sparql [14:56:54] looks like there is something weird with the cert chain. But my browser (Chrome) seems happy about it. [14:58:40] yes me too, just curl apparently... remember having weird issues locally a couple weeks ago where curl would complain for https://en.wikipedia.org [15:05:49] dcausse, ebernhardson, ryankemper, inflatador: meeting? https://meet.google.com/eki-rafx-cxi [15:06:00] oops [15:07:08] Oh, I forgot, US holiday [17:03:09] dinner