your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.4k Projects 2 Wiki

Player died, other player looted the bones in less than 15 minutes #3082

New Issue
Closed
opened 2022-11-19 07:56:22 +00:00 by AliasAlreadyTaken · 8 comments
AliasAlreadyTaken commented 2022-11-19 07:56:22 +00:00
Owner
Copy Link

From first glance, Koolk7474mine died from fall damage near the Battle Royale Arena. Only seconds after the bones were created, player zanezand got hold of the items.

Parts of the death:

2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added mobs:lava_orb to bones @ (-29016,15,-30705)
2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added shields:shield_crystal 1 23640 to bones @ (-29016,15,-30705)
2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:helmet_crystal 1 23640 to bones @ (-29016,15,-30705)
2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:leggings_crystal 1 24790 to bones @ (-29016,15,-30705)
2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:chestplate_crystal 1 24790 to bones @ (-29016,15,-30705)
2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:boots_crystal 1 30082 to bones @ (-29016,15,-30705)
2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine dies at (-29016,15,-30705) and their inventory goes to bones.
2022-11-19 07:32:19: ACTION[Server]: [MOD] xp_redo: Koolk7474mine lost 66 XP!
2022-11-19 07:32:19: ACTION[Server]: [MOD] xp_redo: Reason of death of Koolk7474mine: return {["type"] = "fall", ["from"] = "engine"}

What's this?

2022-11-19 07:32:20: ACTION[Server]: [yl_commons] Koolk7474mine is not immune to fall damage
2022-11-19 07:32:20: ACTION[Server]: Moving Koolk7474mine to static spawnpoint at (2002,15,1154)
2022-11-19 07:32:20: ACTION[Server]: Koolk7474mine respawns at (2002,15,1154)

The log says Koolk7474mine went to the priest and took the items from the bones.

2022-11-19 07:32:35: ACTION[Server]: zanezand activates 
2022-11-19 07:32:42: ACTION[Server]: Koolk7474mine right-clicks object 1558: LuaEntitySAO "yl_speak_up:human" at (1981,15,1216)
2022-11-19 07:32:50: ACTION[Server]: player Koolk7474mine (id=5560, hp=20) punched player zanezand (id=60425, hp=12), damage=0 (handled by Lua)
2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes shields:shield_crystal 1 23640 from bones @ (-29016,15,-30705)
2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:helmet_crystal 1 23640 from bones @ (-29016,15,-30705)
2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:leggings_crystal 1 24790 from bones @ (-29016,15,-30705)
2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:chestplate_crystal 1 24790 from bones @ (-29016,15,-30705)
2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:boots_crystal 1 30082 from bones @ (-29016,15,-30705)

How did the items then end up with zanezand? zanezand is a new player, nothing in the log indicates where he would have gotten those items from. Still, he suddenly "had" them. He took them from the bones, which were generated two seconds earlier. But how? They should have been "fresh" ?

2022-11-19 07:32:52: ACTION[Server]: [yl_commons] zanezand moves "shields:shield_crystal 1 23640" to {"name":"zanezand","type":"player"} [main]
2022-11-19 07:32:52: ACTION[Server]: [bones] zanezand takes shields:shield_crystal 1 23640 from bones @ (-29016,15,-30705)
2022-11-19 07:32:54: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:helmet_crystal 1 23640" to {"name":"zanezand","type":"player"} [main]
2022-11-19 07:32:54: ACTION[Server]: [bones] zanezand takes 3d_armor:helmet_crystal 1 23640 from bones @ (-29016,15,-30705)
2022-11-19 07:32:54: ACTION[Server]: [yl_commons] "Koolk7474mine" dropped "default:coal_lump 4" at pos "(-29016,15.5,-30705)"
2022-11-19 07:32:54: ACTION[Server]: [yl_commons] Koolk7474mine takes "default:coal_lump 4" from {"name":"Koolk7474mine","type":"player"} [main]
2022-11-19 07:32:54: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:leggings_crystal 1 24790" to {"name":"zanezand","type":"player"} [main]
2022-11-19 07:32:54: ACTION[Server]: [bones] zanezand takes 3d_armor:leggings_crystal 1 24790 from bones @ (-29016,15,-30705)
2022-11-19 07:32:55: ACTION[Server]: Koolk7474mine uses default:book_written, pointing at [object 2584]
2022-11-19 07:32:56: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:chestplate_crystal 1 24790" to {"name":"zanezand","type":"player"} [main]
2022-11-19 07:32:56: ACTION[Server]: [bones] zanezand takes 3d_armor:chestplate_crystal 1 24790 from bones @ (-29016,15,-30705)
2022-11-19 07:32:57: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:boots_crystal 1 30082" to {"name":"zanezand","type":"player"} [main]
2022-11-19 07:32:57: ACTION[Server]: [bones] zanezand takes 3d_armor:boots_crystal 1 30082 from bones @ (-29016,15,-30705)

I tried to kill Boris at the location and grab the bones contents with Violetta. No chance.

From first glance, Koolk7474mine died from fall damage near the Battle Royale Arena. Only seconds after the bones were created, player zanezand got hold of the items. Parts of the death: ``` 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added mobs:lava_orb to bones @ (-29016,15,-30705) 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added shields:shield_crystal 1 23640 to bones @ (-29016,15,-30705) 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:helmet_crystal 1 23640 to bones @ (-29016,15,-30705) 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:leggings_crystal 1 24790 to bones @ (-29016,15,-30705) 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:chestplate_crystal 1 24790 to bones @ (-29016,15,-30705) 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine added 3d_armor:boots_crystal 1 30082 to bones @ (-29016,15,-30705) 2022-11-19 07:32:19: ACTION[Server]: [bones] Koolk7474mine dies at (-29016,15,-30705) and their inventory goes to bones. 2022-11-19 07:32:19: ACTION[Server]: [MOD] xp_redo: Koolk7474mine lost 66 XP! 2022-11-19 07:32:19: ACTION[Server]: [MOD] xp_redo: Reason of death of Koolk7474mine: return {["type"] = "fall", ["from"] = "engine"} ``` What's this? ``` 2022-11-19 07:32:20: ACTION[Server]: [yl_commons] Koolk7474mine is not immune to fall damage 2022-11-19 07:32:20: ACTION[Server]: Moving Koolk7474mine to static spawnpoint at (2002,15,1154) 2022-11-19 07:32:20: ACTION[Server]: Koolk7474mine respawns at (2002,15,1154) ``` The log says Koolk7474mine went to the priest and took the items from the bones. ``` 2022-11-19 07:32:35: ACTION[Server]: zanezand activates 2022-11-19 07:32:42: ACTION[Server]: Koolk7474mine right-clicks object 1558: LuaEntitySAO "yl_speak_up:human" at (1981,15,1216) 2022-11-19 07:32:50: ACTION[Server]: player Koolk7474mine (id=5560, hp=20) punched player zanezand (id=60425, hp=12), damage=0 (handled by Lua) 2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes shields:shield_crystal 1 23640 from bones @ (-29016,15,-30705) 2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:helmet_crystal 1 23640 from bones @ (-29016,15,-30705) 2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:leggings_crystal 1 24790 from bones @ (-29016,15,-30705) 2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:chestplate_crystal 1 24790 from bones @ (-29016,15,-30705) 2022-11-19 07:32:50: ACTION[Server]: [bones] Koolk7474mine takes 3d_armor:boots_crystal 1 30082 from bones @ (-29016,15,-30705) ``` How did the items then end up with zanezand? zanezand is a new player, nothing in the log indicates where he would have gotten those items from. Still, he suddenly "had" them. He took them from the bones, which were generated two seconds earlier. But how? They should have been "fresh" ? ``` 2022-11-19 07:32:52: ACTION[Server]: [yl_commons] zanezand moves "shields:shield_crystal 1 23640" to {"name":"zanezand","type":"player"} [main] 2022-11-19 07:32:52: ACTION[Server]: [bones] zanezand takes shields:shield_crystal 1 23640 from bones @ (-29016,15,-30705) 2022-11-19 07:32:54: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:helmet_crystal 1 23640" to {"name":"zanezand","type":"player"} [main] 2022-11-19 07:32:54: ACTION[Server]: [bones] zanezand takes 3d_armor:helmet_crystal 1 23640 from bones @ (-29016,15,-30705) 2022-11-19 07:32:54: ACTION[Server]: [yl_commons] "Koolk7474mine" dropped "default:coal_lump 4" at pos "(-29016,15.5,-30705)" 2022-11-19 07:32:54: ACTION[Server]: [yl_commons] Koolk7474mine takes "default:coal_lump 4" from {"name":"Koolk7474mine","type":"player"} [main] 2022-11-19 07:32:54: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:leggings_crystal 1 24790" to {"name":"zanezand","type":"player"} [main] 2022-11-19 07:32:54: ACTION[Server]: [bones] zanezand takes 3d_armor:leggings_crystal 1 24790 from bones @ (-29016,15,-30705) 2022-11-19 07:32:55: ACTION[Server]: Koolk7474mine uses default:book_written, pointing at [object 2584] 2022-11-19 07:32:56: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:chestplate_crystal 1 24790" to {"name":"zanezand","type":"player"} [main] 2022-11-19 07:32:56: ACTION[Server]: [bones] zanezand takes 3d_armor:chestplate_crystal 1 24790 from bones @ (-29016,15,-30705) 2022-11-19 07:32:57: ACTION[Server]: [yl_commons] zanezand moves "3d_armor:boots_crystal 1 30082" to {"name":"zanezand","type":"player"} [main] 2022-11-19 07:32:57: ACTION[Server]: [bones] zanezand takes 3d_armor:boots_crystal 1 30082 from bones @ (-29016,15,-30705) ``` I tried to kill Boris at the location and grab the bones contents with Violetta. No chance.
AliasAlreadyTaken added the
1. kind/bug
 label 2022-11-19 07:56:26 +00:00
flux added the
2. prio/critical
 label 2022-11-19 15:47:22 +00:00
flux commented 2022-11-19 16:24:54 +00:00
Member
Copy Link

did the items get duped?

now, for things to get even weirder: here's what the rollback logs say (times are in UTC)

Checking (-29016,14,-30705) ...
2022-10-24 17:34:50Z: (-29016,15,-30704) player:Koolk7474 bones:bones -> air 2240597 seconds ago.
2022-11-11 00:23:34Z: (-29016,15,-30704) player:Minetest13 bones:bones -> air 747273 seconds ago.
2022-11-11 21:45:50Z: (-29017,15,-30704) player:etherflows bones:bones -> air 670337 seconds ago.
2022-11-19 07:32:52Z: (0,0,0) player:zanezand  ->  30315 seconds ago.
2022-11-19 07:32:54Z: (0,0,0) player:zanezand  ->  30313 seconds ago.
2022-11-19 07:32:54Z: (0,0,0) player:zanezand  ->  30313 seconds ago.
2022-11-19 07:32:56Z: (0,0,0) player:zanezand  ->  30311 seconds ago.
2022-11-19 07:32:57Z: (0,0,0) player:zanezand  ->  30310 seconds ago.
2022-11-19 07:32:57Z: (-29016,15,-30705) player:zanezand bones:bones -> air 30310 seconds ago.
2022-11-19 07:54:52Z: (-29015,15,-30705) player:Boris bones:bones -> air 28995 seconds ago.
2022-11-19 07:55:37Z: (-29016,15,-30706) player:Boris air -> bones:bones 28950 seconds ago.

according to this, Koolk7474 removed bones from that spot almost 26 days ago, and not sooner. and 2 other players removed bones from that spot as well, before zanezand came along.

what???

2022-11-19 07:32:20: ACTION[Server]: [yl_commons] Koolk7474mine is not immune to fall damage

that's an artifact of the fix for #720. here it means they got their hp reset to 20. it probably doesn't need to be logged.

did the items get duped? now, for things to get even weirder: here's what the rollback logs say (times are in UTC) ``` Checking (-29016,14,-30705) ... 2022-10-24 17:34:50Z: (-29016,15,-30704) player:Koolk7474 bones:bones -> air 2240597 seconds ago. 2022-11-11 00:23:34Z: (-29016,15,-30704) player:Minetest13 bones:bones -> air 747273 seconds ago. 2022-11-11 21:45:50Z: (-29017,15,-30704) player:etherflows bones:bones -> air 670337 seconds ago. 2022-11-19 07:32:52Z: (0,0,0) player:zanezand -> 30315 seconds ago. 2022-11-19 07:32:54Z: (0,0,0) player:zanezand -> 30313 seconds ago. 2022-11-19 07:32:54Z: (0,0,0) player:zanezand -> 30313 seconds ago. 2022-11-19 07:32:56Z: (0,0,0) player:zanezand -> 30311 seconds ago. 2022-11-19 07:32:57Z: (0,0,0) player:zanezand -> 30310 seconds ago. 2022-11-19 07:32:57Z: (-29016,15,-30705) player:zanezand bones:bones -> air 30310 seconds ago. 2022-11-19 07:54:52Z: (-29015,15,-30705) player:Boris bones:bones -> air 28995 seconds ago. 2022-11-19 07:55:37Z: (-29016,15,-30706) player:Boris air -> bones:bones 28950 seconds ago. ``` according to this, Koolk7474 removed bones from that spot almost 26 days ago, and not sooner. and 2 other players removed bones from that spot as well, before zanezand came along. what??? > 2022-11-19 07:32:20: ACTION[Server]: [yl_commons] Koolk7474mine is not immune to fall damage that's an artifact of the fix for #720. here it means they got their hp reset to 20. it probably doesn't need to be logged.
flux added the
3. source/unknown
 label 2022-11-20 21:16:24 +00:00
flux commented 2023-06-15 16:44:05 +00:00
Member
Copy Link

i reviewed the bones logic, and there was an error which would result in the bones becoming "old" whenever the timer triggers, no matter how much time has elapsed. i'm not sure why a timer would trigger early though.

i've reworked the logic so that the bones only become old when wall-time says they should: 9cd73daa90

also, bones now log when they become old, in case there's some other issue going on here which allowed a player to loot another's fresh bones.

i reviewed the bones logic, and there was an error which would result in the bones becoming "old" whenever the timer triggers, no matter how much time has elapsed. i'm not sure why a timer would trigger early though. i've reworked the logic so that the bones only become old when wall-time says they should: https://github.com/fluxionary/minetest-bones_redo/commit/9cd73daa907e679d380613ede1e01780eb3d689c also, bones now log when they become old, in case there's some other issue going on here which allowed a player to loot another's fresh bones.
flux added the
3. source/mod upstream
4. step/ready to QA test
 labels 2023-06-15 16:44:17 +00:00
flux commented 2023-06-15 17:23:17 +00:00
Member
Copy Link

hm. to QA test this, the following snippet will help:

local bones_pos = ...  -- location of the fresh bones node
minetest.get_node_timer(bones_pos):set(1, 1)

before this fix, this will cause a fresh bones node to become old immediately. now, it will reset the timer and continue waiting.

hm. to QA test this, the following snippet will help: ```lua local bones_pos = ... -- location of the fresh bones node minetest.get_node_timer(bones_pos):set(1, 1) ``` before this fix, this will cause a fresh bones node to become old immediately. now, it will reset the timer and continue waiting.
AliasAlreadyTaken added this to the 1.1.120 milestone 2023-06-15 19:47:33 +00:00
AliasAlreadyTaken commented 2023-08-28 14:43:45 +00:00
Author
Owner
Copy Link

Apparently we're on some outdated bones branch. We should switch to flux' bones mod: https://github.com/fluxionary/minetest-bones_redo

Unfortunately there is already a yl_stable branch, so we can't add our own.

Apparently we're on some outdated bones branch. We should switch to flux' bones mod: https://github.com/fluxionary/minetest-bones_redo Unfortunately there is already a yl_stable branch, so we can't add our own.
AliasAlreadyTaken commented 2023-09-03 23:03:12 +00:00
Author
Owner
Copy Link

hm. to QA test this, the following snippet will help:

local bones_pos = ...  -- location of the fresh bones node
minetest.get_node_timer(bones_pos):set(1, 1)

before this fix, this will cause a fresh bones node to become old immediately. now, it will reset the timer and continue waiting.

This makes the bones near-instantly old on the testserver. We're on https://gitea.your-land.de/your-land/minetest-bones_redo.git commit 05f96940000ad5fe994f93bb8e8ba2b6a5cfbc3d of origin/yl_stable

If you're right and this is a surefire way to prove the issue is still there, then the Issue is NOK. Otherwise I'd say we need to wait for the issue happening again on main.

> hm. to QA test this, the following snippet will help: > > ```lua > local bones_pos = ... -- location of the fresh bones node > minetest.get_node_timer(bones_pos):set(1, 1) > ``` > > before this fix, this will cause a fresh bones node to become old immediately. now, it will reset the timer and continue waiting. This makes the bones near-instantly old on the testserver. We're on https://gitea.your-land.de/your-land/minetest-bones_redo.git commit 05f96940000ad5fe994f93bb8e8ba2b6a5cfbc3d of origin/yl_stable If you're right and this is a surefire way to prove the issue is still there, then the Issue is NOK. Otherwise I'd say we need to wait for the issue happening again on main.
AliasAlreadyTaken added the
ugh/QA NOK
ugh/QA main
 labels 2023-09-03 23:04:07 +00:00
flux commented 2023-10-30 17:07:40 +00:00
Member
Copy Link

Unfortunately there is already a yl_stable branch, so we can't add our own.

whoops, removed that

> Unfortunately there is already a yl_stable branch, so we can't add our own. whoops, removed that
flux commented 2023-10-30 17:12:19 +00:00
Member
Copy Link

If you're right and this is a surefire way to prove the issue is still there, then the Issue is NOK. Otherwise I'd say we need to wait for the issue happening again on main.

yeah, we probably need to switch to use my repo as the new upstream. i think the current situation is a result of me trying to push changes from my repo directly into yl_stable on gitea at some point in the past.

> If you're right and this is a surefire way to prove the issue is still there, then the Issue is NOK. Otherwise I'd say we need to wait for the issue happening again on main. yeah, we probably need to switch to use my repo as the new upstream. i think the current situation is a result of me trying to push changes from my repo directly into yl_stable on gitea at some point in the past.
AliasAlreadyTaken commented 2023-11-27 01:27:37 +00:00
Author
Owner
Copy Link

We switched to https://github.com/fluxionary/minetest-bones_redo as upstream :)

We switched to https://github.com/fluxionary/minetest-bones_redo as upstream :)
AliasAlreadyTaken added
5. result/fixed
 and removed
4. step/ready to QA test
ugh/QA NOK
 labels 2023-11-27 01:27:49 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

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
Milestone
Clear milestone
No items
No Milestone
1.1.120
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#3082
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?