attempt to index field 'locks_sent_lock_command' in locks/init.lua:493 #202
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#202
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I inserted
right before that part, we will see if that helps.
Seems like it happened 3 times at least:
These are the clues extracted from the three different incidents:
1:
2:
Seems like a user went on his way to craft a shared locked door. I didn't see him place the door though.
3:
The peer was not found warning appeared several times in a row before the incident, but I do not know whether there is a connection. On the third occasion the door was most likely already in place.
These log messages appear, when someone places a shared locked door:
https://github.com/Sokomine/locks/issues/18
2021-11-21 12:46:48: ERROR[Server]: [#202] locks_sent_lock_command nil
2021-11-21 12:46:48: ERROR[Server]: [#202] {
key_up = "true"
}
2021-11-02 20:54:10: ERROR[Server]: [#202] locks_sent_lock_command nil
2021-11-02 20:54:10: ERROR[Server]: [#202] {
key_up = "true"
}
2021-11-02 20:54:11: ERROR[Server]: [#202] locks_sent_lock_command nil
2021-11-02 20:54:11: ERROR[Server]: [#202] {
key_up = "true"
}
2021-10-31 20:58:29: ERROR[Server]: [#202] locks_sent_lock_command nil
2021-10-31 20:58:29: ERROR[Server]: [#202] {
key_up = "true"
}
The exact same issue can't happen again since locks 1d83f5702b.
And
your-land/locks#1
will prevent further problems.