Semanticmediawiki: How to fix a locked property that keeps waiting for its change propagation process ?

Created on 4 Feb 2021  Â·  5Comments  Â·  Source: SemanticMediaWiki/SemanticMediaWiki

One of my properties shows:

Property "Workpackage description" was altered and requires assigned entities to be reevaluated using a change propagation process. The property page has been locked until the primary specification update is completed to prevent intermediary interruptions or contradictory specifications. The process may take moment before the page can be unlocked as it depends on the size and frequency of the job queue scheduler.

although my jobs run every minute.

I tried to understand what is going on by reading https://www.semantic-mediawiki.org/wiki/Change_propagation.
There are quite a few parameters to fiddle with but i have no clue what and why i should do now given that the property is locked.

Where is the "unlock" button for the property or a function that will specifically care for the problem of this one property and give debug info for it? Since my job queue runs every minute via crontab and the property has been sitting there already for more than i day i'd assume that there is a more serious reason for the situation being as it is.

duplicate question

Most helpful comment

The data rebuild successfully worked around the issue.

All 5 comments

I am now scheduling a data rebuild since I wouldn't know any other remedy at this point.

The data rebuild successfully worked around the issue.

Good

On Sat, Feb 6, 2021 at 8:44 AM Wolfgang Fahl notifications@github.com
wrote:

The data rebuild successfully worked around the issue.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/4923#issuecomment-774479678,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHE5IJQJ6FFMTJSIDEDBLDS5VBT5ANCNFSM4XDHM5FQ
.

>

Kimberly Ann Collins

Indeed good to know that we have a second "workaround" to the issue.

Was this page helpful?
0 / 5 - 0 ratings