Kartographer, is not a problem, we installed it separately ... the problems are:
Mon, Apr 6
yes the bundle for 1.34 exists. But the two features I was describing above are not in 1.34, they are only in latest as far as I know. So the question is how/if we should move to latest ....
Thu, Apr 2
Tue, Mar 24
thank you! It helped!
Mon, Mar 23
Thank you very much for the insights!
here is the size of the biggest tables in Mb
Sat, Mar 21
Thu, Mar 12
We solved the problem by recreating a new account and a new consumer. So this seams to be a bug on Wikimedia side. If someone runs into the problem he can try to make the same. Thank you for the support!
Mar 10 2020
@Tgr: we made a further experiment .... if we select "This consumer is for use only by DD063520." then we get directly access and verifier tokens. With these the code works ....
@Tgr, could you help us out with this?
Mar 6 2020
@Tgr could you find time to check?
Mar 5 2020
@Tgr Hi, I just made a request at 08:03 Paris time .... could you check .... the consumer is:
Mar 4 2020
I published the code here:
yes the user info is correct. The consumer is this one ....
Would it help if we share some minimal code for the functionality we want, so that someone can debug it with an own consumer? But without seeing what is happening on the server side I'm not sure how we will solve the problem .....
Mar 3 2020
mhmmm, so what to do?
I'm not able to fix this ..... the token is for example
this is the consumer:
Feb 19 2020
is this export (dump) available to download somewhere? Is this planned? Should I add an additional ticket for that?
Feb 14 2020
No, problem .... there is still time to do it ; ) ..... I see what @thiemowmde means. But I'm not sure if I can implement this. The problem is that there can be precision problems if it is done as I propose, right?
I think I found a patch. We can changes this https://github.com/wikimedia/pywikibot/blob/2dfe67426c22c3c11cf9be0eabcf538f8848bd48/pywikibot/__init__.py#L847:
I'm also encountering this. I also saw that it is related to this:
I'm encountering the same problem. I also have seen that this is related to this:
Feb 13 2020
Hi, when this is ready I'm eager to test it. I imported the properties I need from Wikidata with the corresponding constrain properties, e.g.
could you indicate the process to upgrade the current version wikibase/wikibase:1.33-bundle in the docker-compose setting to the master branch. This way I can try out the new feature. I read this:
Jan 28 2020
what you mean with server's health? that the cpu is not always 100%?
Thank you for these pointers:
My own wikibase .....
I think I use a bot account. I created it using Special Pages / Bot passwords. And I set high volume editing. In this scenario, is the rate limit not set? i.e. should I be able to edit more?
Jan 17 2020
Jan 6 2020
Tutorial is perfect! You can close this .....
Jan 4 2020
Ok, I got it. I just removed the alias from the wikibase instance. This way he is passing through the "real internet" where the certificate is exposed and not over the internal network. Thank you very much for the support!
I was able to fix the above and to reload the data in the query service as described in:
I understood a bit by chance when this error appears. In my case I was modifying some configuration in the LocationSettings files and I used wrong syntax. Then the Wikibase instance is broken and the APIs do not replay correctly anymore causing this error. You can close this. Hopefully it will help someone in a similar situation.
Jan 3 2020
Ok, this is related to this:
If I set the variable now I get the following log:
Sorry, the error above was quite clear .... the mistake was:
Here is the full log:
I understand that the updater is considering the wrong URL, but should that not work by only setting the environment variables in:
Dec 21 2019
Yes, I mean the image previews
Dec 20 2019
Sorry for pointing again on this .... in fact also another main feature is not working due to this. It is not possible to add manually new statements to items.
So currently we are in the following situation:
- either we have a running SPARQL endpoint, or
- the search and adding statements is running
Both are really important and not just some optional features or minor bugs.
Could you please prioritise this.
Cool thank you!
Dec 19 2019
Ok, this works out! Thank you!
I tried to debug a bit more and I can confirm. If I set:
Dec 17 2019
Dec 14 2019
Dec 10 2019
Perfect! Thank you!
Hi I guess the mistake was that the change has not to be done in the:
Mhmmmm ..... still not working somehow, I do:
thank you for you answer! Unfortunately I do not get it fully. In different places it seams that the configuration is slightly different. I now put:
Dec 8 2019
not sure if this is the right place, hopefully yes!
Nov 15 2019
Ahhh, my mistake, ok, fine for me. I saw that you opened this:
So for me we can close this one.
Thank you very much for the help!
Mhmmm .... on github I cannot find the "ban" language in the wikipedia_family:
yes, I did:
Mhmmmm, I use this version of Pywikibot: pywikibot-3.0.dev0
could that be the problem?
Nov 14 2019
@Xqt : hi, would you consider again this patch, currently I make this modification locally to have some code running
Nov 5 2019
ok, cool, I try to go through it until the end of the week and give you feedback! Merci
Oct 29 2019
When importing the sitelinks of Earth I get a similar problem:
I reduced it down, apparently the language code that makes problems is:
Oct 28 2019
Ok, thank you! I will try it out.
ok, I understand the problem. I'm currently changing the host by going inside the wikimedia docker instance and manually editing the LocalSettings.php file. Can you explain me how to change the host. Is it this line?
Oct 26 2019
Oct 23 2019
This are the labels I'm trying to import:
Oct 22 2019
Hello, could we push this change forward?
Oct 17 2019
The difference is the following .... if you try to put in the wiki twice the same property:
Oct 16 2019
I suggest to replace this line:
Ok, to give back the error message to the user I propose the following change:
Alternatively, is there an option to get the id of the existing Item/Property?
Ahhhh, I got it. The problem is that a property with this label is already existing. But the error message is really not clear. I only understood it after sending the same request over the API sandbox. Is there a way to ignore this check and create the property anyway?
Oct 15 2019
Oct 2 2019
Sep 29 2019
fine for me
Sep 27 2019
this one ....