Discussion utilisateur:Mwjames

From Semantic MediaWiki - Sandbox

Semantic Notifications

Interesting because there was no code change for 17 days: I have just been notified about this diff done by 127.0.0.1 about 21 h ago. Cheers --Karsten Hoffmeyer (discussion) 26 octobre 2016 à 18:52 (CEST)

Ah, ok, I am logged in with another account. Still it should probably not be 127.0.0.1 and just 21 hours ago. --Karsten Hoffmeyer (discussion) 26 octobre 2016 à 18:53 (CEST)
`rebuildData.php` logs changes with 127.0.0.1
Ok, thanks! --[[kgh]] (discussion) 26 octobre 2016 à 19:02 (CEST)

Property grouping

I guess I have understood the feature in the meantime. What wonders me is that special properties "Page length" and "Number of page views" are not shown in the Page Group section though both belong to category. --[[kgh]] (discussion) 9 février 2018 à 10:11 (CET)

This was a caching issue. After purging the pages everything worked fine. Thanks and cheers --[[kgh]] (discussion) 9 février 2018 à 10:43 (CET)

Semantic MediaWiki Usage

Heiya James, it appears that the ElasticSearch backend does not handle comparators? Cheers --[[kgh]] (discussion) 4 août 2018 à 11:40 (CEST)

We test for it and [0, 1] seems to work.
[0] https://sandbox.semantic-mediawiki.org/w/index.php?title=Sp%C3%A9cial:Ask&cl=YzpNjkEKwkAMRU_UZlS6KcxGRLxG2macoZkOJFN6Bg_ixTyJ0SIIf_HgfX4SimSsfpCCU8WBCTjlVP3ROaNl9sgMkXAiUa-xbKCEMkbGgdi3bdscXVilRhIjIV25KoyMavUi30kTW5rTjzVv-6WP91DEtj3qCCUEpeodNN3ZckO19qp4p75_PZ4H55ruYoHmdP2TkDEt-z9v
[1] https://sandbox.semantic-mediawiki.org/w/index.php?title=Sp%C3%A9cial:Ask&cl=YzpNjlEKwjAQRE_Ubqz0p5AfEdFjbNuNDd00sJtSr-BBvJgnMTUIwnwMzGNmXJSAyfYScUzYMwH74JNtjMlumS0yw0Q4kqjVKW6ghDJMjD2xreu6aoxbJU0k2QnpyklhYNSMR_lW5mDzs_95DVtZ2nMLUXK3RR0gOqeUrIGqPWVdUTO9Kt6p697P18GYqj3vakwhbjsQ_BLLNhNqRh2ujwJCdbz8tUBAv5TjHw
Ah, indeed. This would have surprised me. As it turns out the result format used is broken. Cheers --[[kgh]] (discussion) 4 août 2018 à 11:54 (CEST)

Smwdoc

Hmm, I wonder why the query does not return any results? Cheers --[[kgh]] (discussion) 18 août 2018 à 12:40 (CEST)

> Could be related to last weeks ID moves where some of the assignments in ES went missing. I finished the first merge window, so maybe pull the and run `rebuildElasticIndex.php`.
Affirmative. Doing so fixed the issue. Thanks and cheers --[[kgh]] (discussion) 18 août 2018 à 13:42 (CEST)

Within scope?

Hi, is the usage of property "Has Audible link" within the scope of the "External identifier" special property? The result is not as probably expected. Cheers --[[kgh]] (discussion) 1 septembre 2018 à 19:11 (CEST)

What do you mean by "within the scope of the "External identifier"?
Can you clarify "The result is not as probably expected" because Der-Kaempfer-im-Vatikan-Hoerbuch/B0176O7AIM appears for me as "https://www.audible.de/pd/Der-Kaempfer-im-Vatikan-Hoerbuch/B0176O7AIM ". Where did you see "https://www.audible.de/pd/Der-Kaempfer-im-Vatikan-Hoerbuch%2FB0176O7AIM "?
The identifier renders correctly on wiki, however once you click on the link the slash gets transformed into "%2F". To me it looks like SMW is doing this, i.e. there is a difference between display and storage. This is a "more complicated" value to this property so it may not be within the scope of it. Cheers --[[kgh]] (discussion) 1 septembre 2018 à 19:31 (CEST)
Okay, so when you use Firfox you get / and in Chrome you get %2F, [0]. Let me see whether we can do something here [1] or not.
[0] https://user-images.githubusercontent.com/1245473/44948590-f3a1a680-ae0f-11e8-9546-47a04e8f552c.png
[1] https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/src/DataValues/ExternalFormatterUriValue.php#L61-L73
It must not be now. I can create an issue report for this. The behaviour at my end is the same in Fx and Ch. Cheers --[[kgh]] (discussion) 1 septembre 2018 à 20:00 (CEST)
"I can create an issue report for this", yes please so I can add a PR and get it off my list.
Ok, will do. Now I also know what you mean. Indeed, but in the end the result, i.e. broken link at audible is the same for both browsers. --[[kgh]] (discussion) 1 septembre 2018 à 20:03 (CEST)
Done with https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/3386 --[[kgh]] (discussion) 1 septembre 2018 à 20:43 (CEST)

From the "elasticsearch.log" file:

See this page. I am not sure if I should open an issue for this on GitHub. Cheers --[[kgh]] (discussion) 11 février 2019 à 18:59 (CET)

There are two distinct issues in the log, one that relates to "Caused by: org.elasticsearch.index.query.QueryShardException: Failed to parse query [+~plato]" and the other "Caused by: org.elasticsearch.index.query.QueryShardException: No mapping found for [P:13077.wpgField.sort] in order to sort on" both are no real hard issues as the query returns 0 results as it cannot match the condition but we should follow-up and see if we can't improve the situation before they reach ES. Not sure I'll find the time this weekend but ping me if I'm on the verge on forgetting about it.
Shingles struck me so I am not really active this weekend. I guess I should create two issue reports on GitHub. No problem at all. --[[kgh]] (discussion) 17 février 2019 à 11:10 (CET)

Replication issue in "User" namespace?

Basically every time I visit my user page I see the replication issue warning which can easily be resolved by purging. Anyways I wonder if there is a general issue in the "User" namespace or if there is something on my user page which is causing this. Apparently general replication is working. Admittedly I have experienced this for months now but never got around asking you. :| --[[kgh]] (discussion) 4 août 2019 à 11:58 (CEST)

Ah, this does not happen on subpages. So it is either Babel causing this or Semantic Notifications. --[[kgh]] (discussion) 4 août 2019 à 12:01 (CEST)
My guess is that this is caused by Semantic Notifications and it needs some investigation at some point.

Issue/1258

Somehow this went south. If you have time ... Thanks and cheers --[[kgh]] (discussion) 23 novembre 2019 à 18:34 (CET)

Cookies help us deliver our services. By using our services, you agree to our use of cookies.