|
Balise : Éditeur de wikicode 2017 |
| (25 versions intermédiaires par 3 utilisateurs non affichées) |
| Ligne 1 : |
Ligne 1 : |
| − | == SFS xml ==
| + | <big>'''[[/referencedata/|→ page for storing reference data]]'''</big> |
| | + | __TOC__ |
| | + | : Archives of this page: [[/2019/]] - [[/2018/]] - [[/2017/]] - [[/2015/]] |
| | + | ---- |
| | + | ---- |
| | | | |
| − | The old XML contained `#set_internal` calls, I cleaned-up the demo examples on the sandbox to use subobjects instead. -- [[User:Mwjames|Mwjames]] 15:37, 7. Dez. 2015
| + | == Constraint == |
| | | | |
| − | : Ah, ok, thanks! I'll create and upload an new xml file. Cheers --[[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 19:30, 8 December 2015 (CET)
| + | Could you please create a constraint called ''[[smw/schema:Constraint:MandatoryProperties]]'' with the content: |
| − | | + | <pre>{ |
| − | == Leading Pound ==
| + | "type": "CLASS_CONSTRAINT_SCHEMA", |
| − | | + | "constraints": { |
| − | Thanks for that. Template to force the issue will work great in this case. Though I found it a curious behavior when it seems to be handled in the default table formats just fine. Cheers! - [[Utilisateur:Lbillett|Lbillett]] ([[Discussion utilisateur:Lbillett|discussion]]) 21 mars 2017 à 19:00 (CET)
| + | "mandatory_properties": [ "Mandatory 1", "Mandatory 2" ] |
| − | | |
| − | : With tables you have extra "layer" in between whereas without it is directly passed to MediaWiki which does what it sees, i.e. transforms the # to the ordered list. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 21 mars 2017 à 19:07 (CET)
| |
| − | | |
| − | ==What about External Data?==
| |
| − | Hi Karsten, could you perhaps install Yaron's External Data extension? I don't think there's any serious security risk involved in this and there's stuff I'd like to demonstrate/try out. Best, [[Utilisateur:D. G.|D. G.]] ([[Discussion utilisateur:D. G.|discussion]]) 1 septembre 2017 à 16:43 (CEST)
| |
| − | : Hi D. G., indeed I could. :) The reason why I did not install it yet was that extra configuration is needed depending on what one would like to do. Just tell me which domain you would like to access so I can whitelist that one during the installation process. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 1 septembre 2017 à 17:05 (CEST)
| |
| − | :: Thanks, that would be great - I was thinking of the following domains:
| |
| − | ::* logainm.ie (including subdomains)
| |
| − | ::* archives.library.wales
| |
| − | ::* subdomains of ucc.ie
| |
| − | ::* subdomains of www.asnc.cam.ac.uk
| |
| − | :: [[Utilisateur:D. G.|D. G.]] ([[Discussion utilisateur:D. G.|discussion]]) 2 septembre 2017 à 17:19 (CEST)
| |
| − | ::: Done now. Don't you think that something like "subdomains of ucc.ie" is a bit to unspecific? Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 3 septembre 2017 à 11:21 (CEST)
| |
| − | :::: Thanks! And yes, I think so. I'll get back to you with more specifc details. [[Utilisateur:D. G.|D. G.]] ([[Discussion utilisateur:D. G.|discussion]]) 4 septembre 2017 à 22:32 (CEST)
| |
| − | | |
| − | == Disable jsbc-breadcrumbs ==
| |
| − | | |
| − | Can we disable `jsbc-breadcrumbs` because the JS loads late causing FOUC or unrelated content movements and somtimes it is not loaded at all?
| |
| − | | |
| − | : Done for now. This must have started on February 12, 2018. In the end I would love to have this extension back on again. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 17 février 2018 à 11:31 (CET)
| |
| − | | |
| − | :: > I would love to have this extension back on again.
| |
| − | | |
| − | :: If it can be disabled per user (like mine) I'm fine with that. It is really annoying to have those content jumps and due to the design of how the JS is loaded (as async) it will always cause HTML being moved from top to bottom. The extension maintainer should make sure that styles are loaded upfront and have a dedicated div element injected before the HTML is displayed otherwise I cannot see this becoming better at any point.
| |
| − | | |
| − | ::: It indeed adds an UPO allowing each user to choose. This extension provides a functionality which I miss a lot on wikis. It is the best one on the market for this. I will get in touch with Cindy about your suggestions. What I meant with 2018-02-12 was that the bread crumbs were frozen completely. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 17 février 2018 à 11:51 (CET)
| |
| − | | |
| − | :::: "I meant with 2018-02-12 was that the bread crumbs were frozen completely" I wouldn't be surprised if https://github.com/oetterer/BootstrapComponents/issues/9 has something to do with that since it will stop any other JS from executing due to the failure.
| |
| − | | |
| − | ::::: This may very well be the case. Thanks for the pointer. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 17 février 2018 à 11:57 (CET)
| |
| − | | |
| − | == You got mail! ==
| |
| − | | |
| − | Tell me if you didn't get it. [[Utilisateur:Benfletcher|Benfletcher]] ([[Discussion utilisateur:Benfletcher|discussion]]) 30 août 2018 à 13:47 (CEST)
| |
| − | | |
| − | : Looked for it and got it. :) --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussio==n utilisateur:Kghbln|discussion]]) 30 août 2018 à 14:29 (CEST)
| |
| − | | |
| − | == smwgQDefaultLimit ? ==
| |
| − | | |
| − | Can we change <code>$smwgQDefaultLimit</code> to 250? It would allow the Special:Ask pagination to higlight the limit directly.
| |
| − | | |
| − | : [[Special:Diff/12107/12450|done]] --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 15 septembre 2018 à 22:01 (CEST)
| |
| − | | |
| − | == Sandbox Semantic Mediawiki & Allowing on Semantic ==
| |
| − | | |
| − | Hi!
| |
| − | I'm Requested an account on Semantic. Please, Allow me there. And I want to know about Sandbox Semantic. Why is this? [[Utilisateur:Ahmsaqib|Ahmsaqib]] ([[Discussion utilisateur:Ahmsaqib|discussion]]) 30 septembre 2018 à 09:05 (CEST)
| |
| − | | |
| − | : Hi, I was not available the past three days. Anyways I would not have accepted your account request since you did not yet confirm your e-mail address. Once this is done ... Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 30 septembre 2018 à 22:13 (CEST)
| |
| − | ::But, i didn't found any confirmation email. I checked spam folder also. [[Utilisateur:Ahmsaqib|Ahmsaqib]] ([[Discussion utilisateur:Ahmsaqib|discussion]]) 30 septembre 2018 à 22:17 (CEST)
| |
| − | | |
| − | ::: I cannot help you if your e-mail service does not accept e-mails from the wiki. Indeed Gmail is a disaster howerver it does work for others. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 30 septembre 2018 à 22:19 (CEST)
| |
| − | | |
| − | ::::Can you disapprove it? or Edit? only replace with "hotmail.com" [[Utilisateur:Ahmsaqib|Ahmsaqib]] ([[Discussion utilisateur:Ahmsaqib|discussion]]) 30 septembre 2018 à 22:26 (CEST)
| |
| − | | |
| − | :::::I have just created your account and changed the e-mail to use hotmail. You should now be able to access and confirm your e-mail. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 1 octobre 2018 à 21:46 (CEST)
| |
| − | :: But I didn't get a confirmation email. Just get the email:
| |
| − | <pre> | |
| − | Dear Ahmsaqib,
| |
| − | | |
| − | The semantic-mediawiki.org page User:Ahmsaqib has been changed on
| |
| − | 1 October 2018 by Kghbln, see
| |
| − | https://www.semantic-mediawiki.org/wiki/User:Ahmsaqib for the current
| |
| − | revision.
| |
| − | | |
| − | Editor's summary: -
| |
| − | | |
| − | Contact the editor:
| |
| − | mail: https://www.semantic-mediawiki.org/wiki/Special:EmailUser/Kghbln
| |
| − | wiki: https://www.semantic-mediawiki.org/wiki/User:Kghbln
| |
| − | | |
| − | There will be no other notifications in case of further activity unless
| |
| − | you visit this page while logged in. You could also reset the
| |
| − | notification flags for all your watched pages on your watchlist.
| |
| − | | |
| − | Your friendly semantic-mediawiki.org notification system
| |
| − | | |
| − | --
| |
| − | To change your email notification settings, visit
| |
| − | https://www.semantic-mediawiki.org/wiki/Special:Preferences
| |
| − | | |
| − | To change your watchlist settings, visit
| |
| − | https://www.semantic-mediawiki.org/wiki/Special:EditWatchlist
| |
| − | | |
| − | To delete the page from your watchlist, visit
| |
| − | https://www.semantic-mediawiki.org/w/index.php?title=User:Ahmsaqib&action=unwatch
| |
| − | | |
| − | Feedback and further assistance:
| |
| − | https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents
| |
| − | </pre>
| |
| − | [[Utilisateur:Ahmsaqib|Ahmsaqib]] ([[Discussion utilisateur:Ahmsaqib|discussion]]) 1 octobre 2018 à 22:12 (CEST)
| |
| − | | |
| − | : Admittedly I am starting to loose my patience here. I wrote that you should try to access your account and confirm your e-mail. Did this work? This e-mail informed you that I created the account. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 1 octobre 2018 à 22:15 (CEST)
| |
| − | | |
| − | I understand, but I can't do login. Showing password error. can you send me a temporary password? [[Utilisateur:Ahmsaqib|Ahmsaqib]] ([[Discussion utilisateur:Ahmsaqib|discussion]]) 2 octobre 2018 à 04:34 (CEST)
| |
| − | | |
| − | : So requesting a new temporary password does not work for you? --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 2 octobre 2018 à 08:15 (CEST)
| |
| − | | |
| − | == Elastic replication? ==
| |
| − | | |
| − | Just checked [[Exclude_page_example]] to see the query and I can see a couple of recent changes aren't in Elastic because [[Special:SemanticMediaWiki/elastic]] shows "Last active replication: 2019-02-02 03:14:38".
| |
| − | | |
| − | Any errors?
| |
| − | | |
| − | : I will have a look. However yesterday I upgraded Elasticseach which was a minor rather than a patch update so there may be a connection. Sit tight. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 2 février 2019 à 10:38 (CET)
| |
| − | | |
| − | : I again ran into and issue due to exeeding the disk watermark:<pre>Elasticsearch\Common\Exceptions\Forbidden403Exception from line 605 of /../w/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php: {"error":{"root_cause":[{"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"}],"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"},"status":403}</pre>
| |
| − | : 30GB of free discspace is just not enough for Elasticsearch. At the same time the server was under attac so it took longer to fix by running<ref>https://stackoverflow.com/questions/54027888/forbidden-12-index-read-only-allow-delete-api-problem/54493042#54493042 and https://www.elastic.co/guide/en/elasticsearch/reference/6.4/disk-allocator.html</ref> <syntaxhighlight lang="bash">curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'</syntaxhighlight>
| |
| − | : Should be resolved now. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 2 février 2019 à 13:37 (CET)
| |
| − | | |
| − | | |
| − | So again everything got out of control. Setting the following is nonsense:
| |
| − | <pre>
| |
| − | cluster.routing.allocation.disk.watermark.flood_stage: 99%
| |
| − | cluster.routing.allocation.disk.watermark.low: 95%
| |
| − | cluster.routing.allocation.disk.watermark.high: 97%
| |
| − | </pre>
| |
| − | I have a disk usage of 91% and Elasticsearch spams the error log with high and low disk warnings. Now I have set absolute gb:
| |
| − | <pre>
| |
| − | cluster.routing.allocation.disk.watermark.flood_stage: 5gb
| |
| − | cluster.routing.allocation.disk.watermark.low: 20gb
| |
| − | cluster.routing.allocation.disk.watermark.high: 10gb
| |
| − | </pre>
| |
| − | Let's see what happens. If this fails I am afraind not to be able to serve SMW with Elasticsearch on this server. :( --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 3 février 2019 à 21:48 (CET)
| |
| − | | |
| − | : It is still failing however for another reason
| |
| − | | |
| − | <syntaxhighlight lang="text">
| |
| − | [2019-02-04T05:46:37,800][DEBUG][o.e.a.s.TransportSearchAction] [Ql8wRCh] All shards failed for phase: [query]
| |
| − | org.elasticsearch.index.query.QueryShardException: failed to create query: {
| |
| − | "constant_score" : {
| |
| − | "filter" : { | |
| − | "bool" : {
| |
| − | "must" : [ | |
| − | {
| |
| − | "range" : {
| |
| − | "P:10.wpgField" : {
| |
| − | "from" : "O:35:\"SMW\\DataModel\\ContainerSemanticData\":10:{s:11:\"\u0000*\u0000mSubject\";O:14:\"SMW\\DIWikiPage\":9:{s:10:\"\u0000*\u0000m_dbkey\";s:17:\"SMWInternalObject\";s:14:\"\u0000*\u0000m_namespace\";i:-1;s:14:\"\u0000*\u0000m_interwiki\";s:0:\"\";s:18:\"\u0000*\u0000m_subobjectname\";s:3:\"int\";s:23:\"\u0000SMW\\DIWikiPage\u0000sortkey\";N;s:32:\"\u0000SMW\\DIWikiPage\u0000contextReference\";N;s:28:\"\u0000SMW\\DIWikiPage\u0000pageLanguage\";N;s:18:\"\u0000SMW\\DIWikiPage\u0000id\";i:0;s:20:\"\u0000SMWDataItem\u0000options\";N;}s:14:\"\u0000*\u0000mProperties\";a:2:{s:6:\"_LCODE\";O:14:\"SMW\\DIProperty\":5:{s:21:\"\u0000SMW\\DIProperty\u0000m_key\";s:6:\"_LCODE\";s:25:\"\u0000SMW\\DIProperty\u0000m_inverse\";b:0;s:33:\"\u0000SMW\\DIProperty\u0000propertyValueType\";s:7:\"__lcode\";s:25:\"\u0000SMW\\DIProperty\u0000interwiki\";s:0:\"\";s:20:\"\u0000SMWDataItem\u0000options\";N;}s:5:\"_TEXT\";O:14:\"SMW\\DIProperty\":5:{s:21:\"\u0000SMW\\DIProperty\u0000m_key\";s:5:\"_TEXT\";s:25:\"\u0000SMW\\DIProperty\u0000m_inverse\";b:0;s:33:\"\u0000SMW\\DIProperty\u0000propertyValueType\";s:4:\"_txt\";s:25:\"\u0000SMW\\DIProperty\u0000interwiki\";s:0:\"\";s:20:\"\u0000SMWDataItem\u0000options\";N;}}s:12:\"\u0000*\u0000mPropVals\";a:2:{s:5:\"_TEXT\";a:1:{s:120:\"Used in cases where a URL property needs to be exported as an \"owl:AnnotationProperty\". It is a variant of datatype URL.\";O:9:\"SMWDIBlob\":2:{s:11:\"\u0000*\u0000m_string\";s:120:\"Used in cases where a URL property needs to be exported as an \"owl:AnnotationProperty\". It is a variant of datatype URL.\";s:20:\"\u0000SMWDataItem\u0000options\";N;}}s:6:\"_LCODE\";a:1:{s:2:\"en\";O:9:\"SMWDIBlob\":2:{s:11:\"\u0000*\u0000m_string\";s:2:\"en\";s:20:\"\u0000SMWDataItem\u0000options\";N;}}}s:19:\"\u0000*\u0000mHasVisibleProps\";b:1;s:19:\"\u0000*\u0000mHasVisibleSpecs\";b:1;s:16:\"\u0000*\u0000mNoDuplicates\";b:1;s:55:\"\u0000SMW\\DataModel\\ContainerSemanticData\u0000skipAnonymousCheck\";b:1;s:18:\"\u0000*\u0000subSemanticData\";O:29:\"SMW\\DataModel\\SubSemanticData\":2:{s:38:\"\u0000SMW\\DataModel\\SubSemanticData\u0000subject\";r:2;s:46:\"\u0000SMW\\DataModel\\SubSemanticData\u0000subSemanticData\";a:0:{}}s:10:\"\u0000*\u0000options\";N;s:16:\"\u0000*\u0000extensionData\";a:1:{s:9:\"sort.data\";s:123:\"Used in cases where a URL property needs to be exported as an \"owl:AnnotationProperty\". It is a variant of datatype URL.;en\";}}",
| |
| − | "to" : null,
| |
| − | "include_lower" : false,
| |
| − | "include_upper" : true,
| |
| − | "boost" : 1.0
| |
| − | }
| |
| − | }
| |
| − | }
| |
| − | ],
| |
| − | "adjust_pure_negative" : true,
| |
| − | "boost" : 1.0
| |
| − | }
| |
| | }, | | }, |
| − | "boost" : 1.0 | + | "tags": [ |
| − | }
| + | "class constraint", |
| − | }
| + | "mandatory properties" |
| − | at org.elasticsearch.index.query.QueryShardContext.toQuery(QueryShardContext.java:324) ~[elasticsearch-6.6.0.jar:6.6.0]
| + | ] |
| − | at org.elasticsearch.index.query.QueryShardContext.toQuery(QueryShardContext.java:307) ~[elasticsearch-6.6.0.jar:6.6.0]
| + | }</pre>? I have no permissions do that. I am trying to reproduce an integration test case "#4 (violation of `mandatory_properties`, missing two properties, subobject)" from p-1110.json.<br />[[Utilisateur:Alex Mashin|Alex Mashin]] ([[Discussion utilisateur:Alex Mashin|discussion]]) 20 novembre 2021 à 10:35 (CET) |
| − | at org.elasticsearch.search.SearchService.parseSource(SearchService.java:806) ~[elasticsearch-6.6.0.jar:6.6.0]
| + | : Done. Showing an error though. Cheers --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 20 novembre 2021 à 10:36 (CET) |
| − | at org.elasticsearch.search.SearchService.createContext(SearchService.java:656) ~[elasticsearch-6.6.0.jar:6.6.0]
| + | :: Ah not saved. Omg. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 20 novembre 2021 à 10:40 (CET) |
| − | at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:631) ~[elasticsearch-6.6.0.jar:6.6.0]
| + | ::: Done now after disabling Lingo and Semantic Glossary. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 20 novembre 2021 à 10:40 (CET) |
| − | at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:388) ~[elasticsearch-6.6.0.jar:6.6.0]
| + | * Thank you.<br />[[Utilisateur:Alex Mashin|Alex Mashin]] ([[Discussion utilisateur:Alex Mashin|discussion]]) 20 novembre 2021 à 10:59 (CET) |
| − | at org.elasticsearch.search.SearchService.access$100(SearchService.java:126) ~[elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.search.SearchService$2.onResponse(SearchService.java:360) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.search.SearchService$2.onResponse(SearchService.java:356) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.search.SearchService$4.doRun(SearchService.java:1117) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:759) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:41) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.6.0.jar:6.6.0]
| |
| − | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_181]
| |
| − | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_181]
| |
| − | at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
| |
| − | Caused by: java.lang.IllegalArgumentException: input automaton is too large: 1001
| |
| − | at org.apache.lucene.util.automaton.Operations.isFinite(Operations.java:1037) ~[lucene-core-7.6.0.jar:7.6.0 719cde97f84640faa1e3525690d262946571245f - nknize - 2018-12-07 14:44:20]
| |
| − | ...
| |
| − | </syntaxhighlight>
| |
| − | | |
| − | So the reason is "Caused by: java.lang.IllegalArgumentException: input automaton is too large: 1001" meaning that Elasticsearch tries to do more than 1000 write operations a second which is in turn a limit that the ISP imposed on Saturday due to the wiki causing 50% of the total load at their end. I will now have to find out how to restrict write operatins per second. I am wondering why software tries to do this in the first place. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]]) 4 février 2019 à 10:03 (CET)
| |
| − | | |
| − | This is going to be fun, e.g.
| |
| − | : https://github.com/projectblacklight/blacklight/issues/1972 | |
| − | : http://lucene.472066.n3.nabble.com/solr-5-2-gt-7-2-suggester-failure-td4383551.html | |
| − | | |
| − | From quickly reading though the issues I think that the field "wpgField" is too long thus causing loops. --[[Utilisateur:Kghbln|[[kgh]]]] ([[Discussion utilisateur:Kghbln|discussion]])
| |
