api_eggs.lua:20: in function 'lay_egg' #3084
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3084
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?
if not self.type then core.log("action","#3084 self="..dump(self)) return end
i rebased petz locally, and it seems to have fixed the crash. pulling from https://gitea.your-land.de/your-land/petz/src/branch/yl_stable should fix the issue.
And again ...
@AliasAlreadyTaken was the update live when it crashed again? locally i was able to replicate the crash before the update, and it didn't happen after the update, but petz has gotten so buggy lately i want to throw it out a window.
It's still on 74864e092b25e93a8c2cf878620939e336264dea , I don't dare update in between.
had this happen on my local server. no idea how.
created an upstream issue:
https://github.com/runsy/petz/issues/129
i think we can patch this temporarily by creating an alias of
petz:moth_egg
topetz:silkworm_eggs
.temporary fix:
c5b83377f3
upstream issue is supposedly fixed.
this should be live