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

LeetPeet reports: Two death messages for jike at ... #3017

New Issue
Closed
opened 2022-11-13 13:01:33 +00:00 by yourland-report · 19 comments
yourland-report commented 2022-11-13 13:01:33 +00:00
Member
Copy Link

LeetPeet reports a bug:

Two death messages for jike at 8:00 AM EST? "jike was killed by mime near Arena." and "jike was killed near Arena."

Player position:

{
	x = 1578.1159667969,
	y = -30.5,
	z = 297.68099975586
}

Player look:

{
	x = 0.032820913940668,
	y = 0.29737484455109,
	z = -0.95419651269913
}

Player information:

{
	max_rtt = 1.3200000524521,
	lang_code = "",
	state = "Active",
	formspec_version = 6,
	ip_version = 6,
	min_rtt = 0.093000002205372,
	avg_rtt = 0.097999997437,
	min_jitter = 0,
	max_jitter = 1.2170000076294,
	avg_jitter = 0,
	connection_uptime = 3669,
	serialization_version = 29,
	patch = 0,
	minor = 6,
	version_string = "5.6.0",
	major = 5,
	protocol_version = 41
}

Player meta:

{
	fields = {
		bitten = "0",
		played_time = "7825638",
		digged_nodes = "3108462",
		placed_nodes = "616372",
		yl_commons_thankyou = "60",
		crafted = "21138",
		hud_state = "on",
		xp = "2928016",
		yl_church = "return {[\"last_heal\"] = 1630693112, [\"last_death_portal\"] = 1667960745, [\"last_death\"] = {[\"x\"] = 781, [\"y\"] = -5, [\"z\"] = 2179}}",
		["stamina:exhaustion"] = "27",
		punch_count = "23243",
		["stamina:level"] = "9",
		repellant = "0",
		partychat = "main",
		["ocean_build.forbidden"] = "true",
		died = "305",
		["stamina:poisoned"] = "no",
		["ocean_build.last_warning"] = "1.65343e+09",
		["signslib:pos"] = "(810,2,2198)",
		["ocean_build.ocean_built"] = "12",
		inflicted_damage = "373982",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}",
		yl_commons_player_created = "1609243939",
		yl_commons_player_joined = "1668340856",
		arenalib_infobox_arenaID = "0",
		["3d_armor_inventory"] = "return {\"3d_armor:leggings_crystal 1 37180\", \"3d_armor:chestplate_crystal 1 37180\", \"shields:shield_crystal 1 37180\", \"3d_armor:helmet_crystal 1 36880\", \"3d_armor:boots_crystal 1 37180\", \"\"}"
	}
}

Log identifier


[MOD] yl_report log identifier = T9tbrIEc0t4sgY9YuDGeBEb5nsW676FX

Profiler save:

profile-20221113T130133.json_prettyEE

Status:

# Server: version: 5.6.1-yl | game: Minetest Game | uptime: 1h 59min 42s | max lag: 2.27s | clients (17/42): alexandre2005, AliasAlreadyTaken, Bailiff, damiemk, daydream, Greater_Dog, JeCel, jike, Laylem, LeetPeet, lorenzofoz, Sense, Service, sherkhan30452, Stelio, Sundew, yo_hi

Teleport command:

/teleport xyz 1578 -31 298

Compass command:

/give_compass Construction T9tbrIEc0t4sgY9YuDGeBEb5nsW676FX D2691E 1578 -31 298
LeetPeet reports a bug: > Two death messages for jike at 8:00 AM EST? "jike was killed by mime near Arena." and "jike was killed near Arena." Player position: ``` { x = 1578.1159667969, y = -30.5, z = 297.68099975586 } ``` Player look: ``` { x = 0.032820913940668, y = 0.29737484455109, z = -0.95419651269913 } ``` Player information: ``` { max_rtt = 1.3200000524521, lang_code = "", state = "Active", formspec_version = 6, ip_version = 6, min_rtt = 0.093000002205372, avg_rtt = 0.097999997437, min_jitter = 0, max_jitter = 1.2170000076294, avg_jitter = 0, connection_uptime = 3669, serialization_version = 29, patch = 0, minor = 6, version_string = "5.6.0", major = 5, protocol_version = 41 } ``` Player meta: ``` { fields = { bitten = "0", played_time = "7825638", digged_nodes = "3108462", placed_nodes = "616372", yl_commons_thankyou = "60", crafted = "21138", hud_state = "on", xp = "2928016", yl_church = "return {[\"last_heal\"] = 1630693112, [\"last_death_portal\"] = 1667960745, [\"last_death\"] = {[\"x\"] = 781, [\"y\"] = -5, [\"z\"] = 2179}}", ["stamina:exhaustion"] = "27", punch_count = "23243", ["stamina:level"] = "9", repellant = "0", partychat = "main", ["ocean_build.forbidden"] = "true", died = "305", ["stamina:poisoned"] = "no", ["ocean_build.last_warning"] = "1.65343e+09", ["signslib:pos"] = "(810,2,2198)", ["ocean_build.ocean_built"] = "12", inflicted_damage = "373982", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}", yl_commons_player_created = "1609243939", yl_commons_player_joined = "1668340856", arenalib_infobox_arenaID = "0", ["3d_armor_inventory"] = "return {\"3d_armor:leggings_crystal 1 37180\", \"3d_armor:chestplate_crystal 1 37180\", \"shields:shield_crystal 1 37180\", \"3d_armor:helmet_crystal 1 36880\", \"3d_armor:boots_crystal 1 37180\", \"\"}" } } ``` Log identifier ``` [MOD] yl_report log identifier = T9tbrIEc0t4sgY9YuDGeBEb5nsW676FX ``` Profiler save: ``` profile-20221113T130133.json_prettyEE ``` Status: ``` # Server: version: 5.6.1-yl | game: Minetest Game | uptime: 1h 59min 42s | max lag: 2.27s | clients (17/42): alexandre2005, AliasAlreadyTaken, Bailiff, damiemk, daydream, Greater_Dog, JeCel, jike, Laylem, LeetPeet, lorenzofoz, Sense, Service, sherkhan30452, Stelio, Sundew, yo_hi ``` Teleport command: ``` /teleport xyz 1578 -31 298 ``` Compass command: ``` /give_compass Construction T9tbrIEc0t4sgY9YuDGeBEb5nsW676FX D2691E 1578 -31 298 ```
AliasAlreadyTaken was assigned by yourland-report 2022-11-13 13:01:33 +00:00
flux added the
1. kind/bug
 label 2022-11-13 15:04:53 +00:00
flux commented 2022-11-13 15:05:50 +00:00
Member
Copy Link

possibly a regression of #1015

possibly a regression of #1015
flux commented 2022-11-17 15:35:36 +00:00
Member
Copy Link
@respawn)phillip was killed by big near caves.
[STAFF] phillip dies at (2206,20,101) and their inventory goes to bones.
@respawn)phillip was killed near caves.
[STAFF] phillip dies at (2206,20,101) and doesn't have any inventory to be dropped.
@respawn)phillip was killed near caves.
[STAFF] phillip dies at (2206,20,101) and doesn't have any inventory to be dropped.
@respawn)phillip was killed near caves.
[STAFF] phillip dies at (2206,20,101) and doesn't have any inventory to be dropped.
<phillip> ups rein gefallen

so this is definitely happening, but it's not a regression of #1015, which was due to the game predicting the player would die, and the armor heal factor negating it.

this feels more like multiple mobs are attacking the player, and one kills the player, but the attacks from the others still land.

``` @respawn)phillip was killed by big near caves. [STAFF] phillip dies at (2206,20,101) and their inventory goes to bones. @respawn)phillip was killed near caves. [STAFF] phillip dies at (2206,20,101) and doesn't have any inventory to be dropped. @respawn)phillip was killed near caves. [STAFF] phillip dies at (2206,20,101) and doesn't have any inventory to be dropped. @respawn)phillip was killed near caves. [STAFF] phillip dies at (2206,20,101) and doesn't have any inventory to be dropped. <phillip> ups rein gefallen ``` so this is definitely happening, but it's not a regression of #1015, which was due to the game *predicting* the player would die, and the armor heal factor negating it. this feels more like multiple mobs are attacking the player, and one kills the player, but the attacks from the others still land.
flux commented 2022-11-17 19:09:49 +00:00
Member
Copy Link

after testing, this seems to be caused when the player is getting attacked by multiple mobs and they're wearing armor w/ "heal".

after testing, this seems to be caused when the player is getting attacked by multiple mobs *and* they're wearing armor w/ "heal".
flux commented 2022-11-17 19:21:11 +00:00
Member
Copy Link

verified that "on_dieplayer" is called again if the player is killed while dead. which sounds like a glitch, but consider the case that the player is "dead" but didn't get the "death formspec" e.g. https://github.com/minetest/minetest/issues/11523

question is, can we detect that and ignore it...

verified that "on_dieplayer" is called again if the player is killed while dead. which sounds like a glitch, but consider the case that the player is "dead" but didn't get the "death formspec" e.g. https://github.com/minetest/minetest/issues/11523 question is, can we detect that and ignore it...
flux commented 2022-11-17 21:40:45 +00:00
Member
Copy Link

i was able to reliably cause the issue for a while, then it stopped happening. possibly this fixes it, but the problem wasn't occurring when i was testing it:

fb0200b640

i was able to reliably cause the issue for a while, then it stopped happening. possibly this fixes it, but the problem wasn't occurring when i was testing it: https://gitea.your-land.de/your-land/mt-respawn/commit/fb0200b64003d029286257fd08f29f7028cfac1b
flux added the
4. step/ready to QA test
 label 2022-11-17 21:40:53 +00:00
AliasAlreadyTaken commented 2022-11-23 07:40:21 +00:00
Owner
Copy Link

Why did it happen just now? We (more likely: 3d_armor?) must have changed something in some on_death (or on_hp_change) callback?

Why did it happen just now? We (more likely: 3d_armor?) must have changed something in some on_death (or on_hp_change) callback?
flux commented 2022-11-24 03:29:43 +00:00
Member
Copy Link

Why did it happen just now? We (more likely: 3d_armor?) must have changed something in some on_death (or on_hp_change) callback?

very good questions that i don't have good theories about. let's wait and see if it happens more, it doesn't seem to happen often?

> Why did it happen just now? We (more likely: 3d_armor?) must have changed something in some on_death (or on_hp_change) callback? very good questions that i don't have good theories about. let's wait and see if it happens more, it doesn't seem to happen often?
AliasAlreadyTaken commented 2022-11-24 16:26:07 +00:00
Owner
Copy Link

Current rotation of the log started on 2022-11-13 10:46:17
Today is 2022-11-24 16:23:58

In this period 2376 death were recorded, of which 455 seem "duplicate death", measured by "death in the same second"

Current rotation of the log started on 2022-11-13 10:46:17 Today is 2022-11-24 16:23:58 In this period 2376 death were recorded, of which 455 seem "duplicate death", measured by "death in the same second"
AliasAlreadyTaken commented 2022-11-24 19:25:26 +00:00
Owner
Copy Link

One example:

2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage
2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro added default:pick_stone 1 38071 to bones @ (2211,-913,582)
2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro added default:iron_lump 4 to bones @ (2211,-913,582)
2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro added default:tree to bones @ (2211,-913,582)
..
2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro dies at (2211,-913,582) and their inventory goes to bones.
2022-11-24 19:21:48: ACTION[Server]: [MOD] xp_redo: Spectro lost 37 XP!
2022-11-24 19:21:48: ACTION[Server]: [MOD] xp_redo: Reason of death of Spectro: return {["from"] = "engine", ["type"] = "punch", ["object"] = nil}
2022-11-24 19:21:48: ACTION[Server]: LuaEntitySAO "mobs_monster:oerkki" at (2211,-912,584) (id=42074, hp=38) punched player Spectro (id=29162, hp=0), damage=4
2022-11-24 19:21:48: ACTION[Server]: Server: Spectro tried to interact while dead; ignoring.
2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro tried to interacted_while_dead while dead; killing again
2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage
2022-11-24 19:21:48: ACTION[Server]: Sandra places node ethereal:glostone at (1642,-881,623)
2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage
2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro dies at (2211,-913,582) and doesn't have any inventory to be dropped.
2022-11-24 19:21:48: ACTION[Server]: Server: Spectro tried to interact while dead; ignoring.
2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro tried to interacted_while_dead while dead; killing again
2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage
2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage
2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro dies at (2211,-913,582) and doesn't have any inventory to be dropped.

One example: 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage 2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro added default:pick_stone 1 38071 to bones @ (2211,-913,582) 2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro added default:iron_lump 4 to bones @ (2211,-913,582) 2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro added default:tree to bones @ (2211,-913,582) .. 2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro dies at (2211,-913,582) and their inventory goes to bones. 2022-11-24 19:21:48: ACTION[Server]: [MOD] xp_redo: Spectro lost 37 XP! 2022-11-24 19:21:48: ACTION[Server]: [MOD] xp_redo: Reason of death of Spectro: return {["from"] = "engine", ["type"] = "punch", ["object"] = nil} 2022-11-24 19:21:48: ACTION[Server]: LuaEntitySAO "mobs_monster:oerkki" at (2211,-912,584) (id=42074, hp=38) punched player Spectro (id=29162, hp=0), damage=4 2022-11-24 19:21:48: ACTION[Server]: Server: Spectro tried to interact while dead; ignoring. 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro tried to interacted_while_dead while dead; killing again 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage 2022-11-24 19:21:48: ACTION[Server]: Sandra places node ethereal:glostone at (1642,-881,623) 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage 2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro dies at (2211,-913,582) and doesn't have any inventory to be dropped. 2022-11-24 19:21:48: ACTION[Server]: Server: Spectro tried to interact while dead; ignoring. 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro tried to interacted_while_dead while dead; killing again 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage 2022-11-24 19:21:48: ACTION[Server]: [yl_commons] Spectro is not immune to fall damage 2022-11-24 19:21:48: ACTION[Server]: [bones] Spectro dies at (2211,-913,582) and doesn't have any inventory to be dropped.
JeCel commented 2022-11-24 20:41:50 +00:00
Copy Link

Sometimes they are not just sent twice but four or five times. Generally I have seen this happen quite often now.

Sometimes they are not just sent twice but four or five times. Generally I have seen this happen quite often now.
flux commented 2022-11-24 23:20:35 +00:00
Member
Copy Link

Spectro tried to interacted_while_dead while dead; killing again

i bet that's the issue - i'm not sure why it's getting triggered, but it seems due to the solution to #478.

when a player is dead, further death messages should be ignored until they respawn.

> Spectro tried to interacted_while_dead while dead; killing again i bet that's the issue - i'm not sure why it's getting triggered, but it seems due to the solution to #478. when a player is dead, further death messages should be ignored until they respawn.
flux commented 2022-11-24 23:33:27 +00:00
Member
Copy Link

fixed in 502b5a7706

fixed in https://gitea.your-land.de/your-land/mt-respawn/commit/502b5a77063ffd0ef7f67572208121e3b1284e07
AliasAlreadyTaken added this to the 1.1.117 milestone 2022-11-25 17:24:16 +00:00
AliasAlreadyTaken commented 2023-01-02 10:35:22 +00:00
Owner
Copy Link

I still get more than one staff message when aplayer dies and the death portal points to a wrong location?

I still get more than one staff message when aplayer dies and the death portal points to a wrong location?
flux commented 2023-01-02 22:27:55 +00:00
Member
Copy Link

I still get more than one staff message when aplayer dies and the death portal points to a wrong location?

ah, that's handled by entirely different code, isn't it.

> I still get more than one staff message when aplayer dies and the death portal points to a wrong location? ah, that's handled by entirely different code, isn't it.
flux commented 2023-01-02 22:38:03 +00:00
Member
Copy Link

I still get more than one staff message when aplayer dies
ah, that's handled by entirely different code, isn't it.

fixed in ba092b8075

the death portal points to a wrong location?

wait really? i didn't think players could meaningfully move while dead, at least as far as the server was concerned.

> I still get more than one staff message when aplayer dies > ah, that's handled by entirely different code, isn't it. fixed in https://gitea.your-land.de/your-land/yl_commons/commit/ba092b8075ca5833ae1f873d4f79d4b9b87669b1 > the death portal points to a wrong location? wait really? i didn't think players could meaningfully move while dead, at least as far as the server was concerned.
AliasAlreadyTaken commented 2023-01-03 06:36:02 +00:00
Owner
Copy Link

There must be something that kills the player over and over and even affects dead players. We should go through all register_on_dieplayer and see if there's some death loop there? Could also happen in some register_on_respawnplayer or register_on_player_hpchange or any other that affects the hp0-death-respawn order.

the death portal points to a wrong location?

wait really? i didn't think players could meaningfully move while dead, at least as far as the server was concerned.

Lag may cause a player to "keep on dieing" at the spawnpoint, effectively setting the death portal to the spawnpoint.

There must be something that kills the player over and over and even affects dead players. We should go through all register_on_dieplayer and see if there's some death loop there? Could also happen in some register_on_respawnplayer or register_on_player_hpchange or any other that affects the hp0-death-respawn order. > > the death portal points to a wrong location? > > wait really? i didn't think players could meaningfully move while dead, at least as far as the server was concerned. Lag may cause a player to "keep on dieing" at the spawnpoint, effectively setting the death portal to the spawnpoint.
flux commented 2023-01-04 00:00:33 +00:00
Member
Copy Link

Lag may cause a player to "keep on dieing" at the spawnpoint, effectively setting the death portal to the spawnpoint.

lag. i see a race condition in my "kill on dead" code, that's almost certainly the cause.

> Lag may cause a player to "keep on dieing" at the spawnpoint, effectively setting the death portal to the spawnpoint. lag. i see a race condition in my "kill on dead" code, that's almost certainly the cause.
flux commented 2023-01-04 00:09:58 +00:00
Member
Copy Link

fixed in 8b3a832f86

still testing it, but i think this works ....

fixed in https://gitea.your-land.de/your-land/yl_commons/commit/8b3a832f86ad59917fe96c7d1688613a48ba5d78 still testing it, but i think this works ....
AliasAlreadyTaken added the
ugh/QA main
 label 2023-01-18 10:53:04 +00:00
flux added
5. result/fixed
 and removed
4. step/ready to QA test
 labels 2023-01-25 22:23:10 +00:00
AliasAlreadyTaken was unassigned by flux 2023-01-25 22:23:13 +00:00
flux commented 2023-01-25 22:23:36 +00:00
Member
Copy Link

this is live and appears to solve the problem - i don't see any more repeated death messages.

this is live and appears to solve the problem - i don't see any more repeated death messages.
🎉 1
flux closed this issue 2023-01-25 22:23:37 +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.117
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 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#3017
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?