Nov 6 2019
Oct 19 2019
Oct 16 2019
this is likely to be due to the custom-config.json file not being properly fetched from the client: it works when building the image from the current master, instead of relying on wikibase/wdqs-frontend:latest image (it could be that it now also works on latest if it was updated lately)
Oct 12 2019
could you tell more on that merge plugin?
what is it (found it), where is it referenced and used?
Sep 22 2019
I don't know if I am or not using the composer merge plugin, I'm using the wikibase/wikibase:1.33-bundle docker image without any additional extension
Sep 21 2019
the composer.lock I found in /var/www/html/extensions/Wikibase
Sep 16 2019
@Addshore it could apply to any image, not just wdqs-frontend:: when pulling wikibase/wikibase:1.33-bundle the name tells me it was built from the wikibase/1.33 folder, but that folder has been modified several times:
* 531fbda - (10 weeks ago) More cleanups for performance, use better names and passwords - Amir Sarabadani * a294b27 - (10 weeks ago) Use a commit that works for 1.33 - Amir Sarabadani * 7e8697d - (2 months ago) Explicitly download 1.34-wmf.8 of EntitySchema for 1.33 bundle - Amir Sarabadani * 562e69b - (2 months ago) Add 1.33 + EntitySchema extension - Amir Sarabadani
How can I know at which commit it was built?
Sep 14 2019
Aug 27 2019
Aug 24 2019
Jun 21 2019
May 31 2019
Apr 5 2019
Nov 29 2018
Nov 20 2018
I wasn't aware of the Grid, looks like it was what I was looking for indeed :)
This task can thus be closed as far as I'm concerned.
Nov 19 2018
Jul 14 2018
Jun 26 2018
Jun 11 2018
May 26 2018
May 23 2018
May 4 2018
May 3 2018
May 2 2018
Feb 22 2018
Jan 27 2018
Dec 4 2017
Dec 3 2017
ooh I didn't see the preview button, but yes, just adding a href to query.wikidata.org#SELECT... URLs and not preventing default on click events when opened outside shouldn't be too hard(?) and of great value for tabs extensive users :)
yes, the examples dialog, but mostly the links to the example queries themselves: every layout that has the possibility to be built from the URL (so for example queries that would be https://query.wikidata.org/#[the serialized SPARQL]), should ideally offer the possibility to be open outside)
Dec 2 2017
Jun 19 2017
May 21 2017
@MrSteff hey, feel free to reach me on IRC (user: maxlath) if/when you want to come, so that we don't miss each others
May 20 2017
@MrSteff sure! simply come to the Blunzn room anytime, I'm there most of the time (usually first desk at your right when you enter)
May 19 2017
@Framawiki I'm in the Blunzn room (1st level), come anytime!
May 18 2017
Aug 29 2016
Copying here the suggestion I made in the mailing list A plea for incremental dumps thread:
Aug 12 2016
May 11 2016
@JanZerebecki oh sorry, that should be published now
Following today's issue with the query GUI, I had a look at the code and thought of some optimizations, without being aware of this discussion, leading to the writing of a simple building script.
Given I did it without this conversation in mind, feel free to ignore it or just take is as inspiration. If you want to use a more elaborate build process, particularly fast in development mode, I would recommend having a look at brunch which is specialized in building this kind of front app. See here how it relates to Grunt, Gulp and others
Feb 11 2016
So it's time to eliminate the pretense that clients can manually construct the cookies instead of handing the standard HTTP cookie headers.
Jan 16 2016
Jan 15 2016
Aug 17 2015
ok, so I came to solve all my problems, including the very nasty
so that's the (coffeescript) code I'm using, with everything in the body, that created the noentity error
breq = require 'bluereq' Promise = require 'bluebird' _ = require './utils'
now, passing the parameters in the body, I get