Mar 25 2020
ScienceSource moved to a single 16G instance when these became available. This change is no longer applicable.
Hi @Aklapper -- this can be closed -- thanks.
Nov 29 2019
Nov 28 2019
The patch fails for codes the live system accepts. The live deployment is based on an earlier codebase which we have patched to fix this issue. This code will be reconciled with the current master and deployed after testing.
The test suite is close to being ready. Task: https://phabricator.wikimedia.org/T62525
There really needs to be an accepted set of use cases for the valid/invalid decodes (as well as trying to handle 'legacy' codes which were created by the previous system).
The patch failed some of our manual tests on the punctuation-encoding edge cases. To go forward we are developing a test suite and adding some basic READMEs etc. so functionality can be agreed and fixes tested.
Reviewing and triaging these tasks.
An A record has now been added to AWS for the name qrwp.org Whois shows what we expect in terms of DNS, resellers etc.
Jul 18 2019
Hi @Addshore I've been able to get our forked version working based on the latest version -- thanks.
Jul 17 2019
Our project site is also affected by this. Thanks for the details @AbdBarho.
Jun 10 2019
Because I am told that I wrote at a wrong place, I try once more and paste it here:
The issues still persist:
a) Double slashes in de.Wikipedia: https://de.qrwp.org/Berlin
The solution should be known at WMUK, because the bug has been fixed for other language versions.
b) Incorrect URL resolution for articles with non-letter character:
The issue already existed once in 2014, but was quickly fixed by a simple method at qrwp.org: With the incoming URL, do a regex_replace or string_replace, find '%25' replace with '%'.
I would like to know why the fix was undone.
Mar 13 2019
Mar 12 2019
@Samwilson yes the qrpedia repo on Wikimedia source forge is the good one.
Oct 22 2018
@Tarrow True, although in our fork we persist the Wikibase and wdqs data using host volumes, so have removed that final volumes section. Troubleshooting required examining how Blazegraph was working under the hood too!
Oct 19 2018
We have been having the same issues on ScienceSource this week. We now have a working Query Service.
(We have definitely found we need a large VM instance to run the current stack if we want any memory left to start a process for docker ps.)
Oct 16 2018
Thanks very much for the pointer @Krenair we were able to handle this.
Thanks for the reply @Krenair I will check whether we can handle this ourselves and close if so.
Oct 12 2018
Oct 5 2018
Yes, it does exist and we are using it, so this task should be closed.
Oct 4 2018
OK, sorry for the confusion! We have a project and don't need a new project to be created.
@Jkbr: Why was this assigned to me? What does "expose" mean actually? Subdomain of which domain? See also https://www.mediawiki.org/wiki/How_to_report_a_bug
This is a pre-requisite for an official conference event we are running as part of our project in mid October.
Please could we get this set up? Thanks.
Oct 1 2018
Sep 6 2018
@Aklapper We will be moving our tasks planning here but don't yet have a project set up.
Jun 27 2018
Please can you grant my user (Jkbr) projectadmin rights on sciencesource?