your-land/bugtracker
your-land/bugtracker
41
22
Issues 3.6k Projects 4 Wiki

testmineweirdo reports: ImageError while going through ... #7410

New Issue
Open
opened 2024-09-12 09:10:23 +02:00 by yourland-report · 15 comments
yourland-report commented 2024-09-12 09:10:23 +02:00
Member
Copy Link

testmineweirdo reports a bug:

ImageError while going through netherlands church nether portal

Player position:

{
	x = 3112.6721191406,
	y = 29294.5,
	z = 4019.5639648438
}

Player look:

{
	x = 0.25258040428162,
	y = -0.03612045198679,
	z = 0.96690142154694
}

Player information:

{
	version_string = "5.9.0",
	avg_rtt = 0.17399999499321,
	max_rtt = 4.2950000762939,
	state = "Active",
	protocol_version = 43,
	minor = 9,
	connection_uptime = 7825,
	ip_version = 6,
	min_rtt = 0.16799999773502,
	min_jitter = 0,
	max_jitter = 4.1160001754761,
	avg_jitter = 0.0020000040531158,
	formspec_version = 7,
	serialization_version = 29,
	patch = 0,
	lang_code = "",
	major = 5
}

Player meta:

{
	fields = {
		["3d_armor_inventory"] = "return {\"\", \"\", \"\", \"\", \"\", \"\"}",
		repellant = "0",
		hud_state = "on",
		partychat = "party",
		yl_commons_player_created = "1708500045",
		["petz:werewolf"] = "0",
		["signslib:pos"] = "(-1108,30,-2977)",
		["stamina:level"] = "15",
		xp = "106750",
		["stamina:exhaustion"] = "10.5",
		jointime = "1708500045",
		bitten = "0",
		yl_commons_thankyou = "94",
		played_time = "4221575",
		digged_nodes = "412607",
		yl_church = "return {[\"last_death_portal\"] = 1726124357, [\"last_heal\"] = 1724396781, [\"last_death\"] = {[\"x\"] = -873, [\"y\"] = -327, [\"z\"] = 20002}}",
		died = "978",
		crafted = "117151",
		inflicted_damage = "124866",
		placed_nodes = "53613",
		["petz:lycanthropy"] = "0",
		yl_commons_player_joined = "1726117211",
		["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}",
		punch_count = "6844",
		["petz:werewolf_clan_idx"] = "3"
	}
}

Log identifier


[MOD] yl_report log identifier = MotgwxWs2k8bLnHo7hV5LrDNN1Fzb3ht

Profiler save:

profile-20240912T071023.json_prettyEE

Status:

# Server: version: 5.8.0-yl-debug | game: Minetest Game | uptime: 7d 2h 44min 44s | max lag: 0.584s | clients (10/52): AliasAlreadyTaken, Bailiff, daydream, Deathwing, flux, LadyPixels, Murmel, RPiManiac, Service, testmineweirdo

Teleport command:

/teleport xyz 3113 29295 4020

Compass command:

/give_compass Construction MotgwxWs2k8bLnHo7hV5LrDNN1Fzb3ht D2691E 3113 29295 4020
testmineweirdo reports a bug: > ImageError while going through netherlands church nether portal Player position: ``` { x = 3112.6721191406, y = 29294.5, z = 4019.5639648438 } ``` Player look: ``` { x = 0.25258040428162, y = -0.03612045198679, z = 0.96690142154694 } ``` Player information: ``` { version_string = "5.9.0", avg_rtt = 0.17399999499321, max_rtt = 4.2950000762939, state = "Active", protocol_version = 43, minor = 9, connection_uptime = 7825, ip_version = 6, min_rtt = 0.16799999773502, min_jitter = 0, max_jitter = 4.1160001754761, avg_jitter = 0.0020000040531158, formspec_version = 7, serialization_version = 29, patch = 0, lang_code = "", major = 5 } ``` Player meta: ``` { fields = { ["3d_armor_inventory"] = "return {\"\", \"\", \"\", \"\", \"\", \"\"}", repellant = "0", hud_state = "on", partychat = "party", yl_commons_player_created = "1708500045", ["petz:werewolf"] = "0", ["signslib:pos"] = "(-1108,30,-2977)", ["stamina:level"] = "15", xp = "106750", ["stamina:exhaustion"] = "10.5", jointime = "1708500045", bitten = "0", yl_commons_thankyou = "94", played_time = "4221575", digged_nodes = "412607", yl_church = "return {[\"last_death_portal\"] = 1726124357, [\"last_heal\"] = 1724396781, [\"last_death\"] = {[\"x\"] = -873, [\"y\"] = -327, [\"z\"] = 20002}}", died = "978", crafted = "117151", inflicted_damage = "124866", placed_nodes = "53613", ["petz:lycanthropy"] = "0", yl_commons_player_joined = "1726117211", ["unified_inventory:bags"] = "return {\"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\", \"unified_inventory:bag_large\"}", punch_count = "6844", ["petz:werewolf_clan_idx"] = "3" } } ``` Log identifier ``` [MOD] yl_report log identifier = MotgwxWs2k8bLnHo7hV5LrDNN1Fzb3ht ``` Profiler save: ``` profile-20240912T071023.json_prettyEE ``` Status: ``` # Server: version: 5.8.0-yl-debug | game: Minetest Game | uptime: 7d 2h 44min 44s | max lag: 0.584s | clients (10/52): AliasAlreadyTaken, Bailiff, daydream, Deathwing, flux, LadyPixels, Murmel, RPiManiac, Service, testmineweirdo ``` Teleport command: ``` /teleport xyz 3113 29295 4020 ``` Compass command: ``` /give_compass Construction MotgwxWs2k8bLnHo7hV5LrDNN1Fzb3ht D2691E 3113 29295 4020 ```
AliasAlreadyTaken was assigned by yourland-report 2024-09-12 09:10:23 +02:00
AliasAlreadyTaken added the
4. step/needs confirmation
 label 2024-09-19 16:26:31 +02:00
whosit commented 2024-10-16 22:49:17 +02:00
Member
Copy Link

I got this in the transitional nether portal:

2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "")
2024-10-16 23:45:12: ERROR[Main]: generateImagePart(): baseimg == NULL for part_of_name="[colorize:#A00:255", cancelling.
2024-10-16 23:45:12: ERROR[Main]: generateImage(): Failed to generate "[colorize:#A00:255"
2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "^[colorize:#A00:255")
2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "")
2024-10-16 23:45:12: ERROR[Main]: generateImagePart(): baseimg == NULL for part_of_name="[colorize:#A50:255", cancelling.
2024-10-16 23:45:12: ERROR[Main]: generateImage(): Failed to generate "[colorize:#A50:255"
2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "^[colorize:#A50:255")

When errors appeared, I saw a smoke (from nether:fumarole I think).

[minetest 5.9.1]

/teleport xyz 3112 29296 4020
I got this in the transitional nether portal: ```bash 2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "") 2024-10-16 23:45:12: ERROR[Main]: generateImagePart(): baseimg == NULL for part_of_name="[colorize:#A00:255", cancelling. 2024-10-16 23:45:12: ERROR[Main]: generateImage(): Failed to generate "[colorize:#A00:255" 2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "^[colorize:#A00:255") 2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "") 2024-10-16 23:45:12: ERROR[Main]: generateImagePart(): baseimg == NULL for part_of_name="[colorize:#A50:255", cancelling. 2024-10-16 23:45:12: ERROR[Main]: generateImage(): Failed to generate "[colorize:#A50:255" 2024-10-16 23:45:12: ERROR[Main]: generateImage(): baseimg is NULL (attempted to create texture "^[colorize:#A50:255") ``` When errors appeared, I saw a smoke (from nether:fumarole I think). [minetest 5.9.1] ```bash /teleport xyz 3112 29296 4020 ```
whosit added
1. kind/bug
 and removed
4. step/needs confirmation
 labels 2024-10-16 22:49:31 +02:00
DragonWrangler commented 2024-10-16 22:54:08 +02:00
Copy Link

This is due to a change in 5.9.0. You'll need to do:

"blank.png^[noalpha^[colorize:..."

or make a fully black image and do:

"black.png^[colorize:..."

This is due to a change in 5.9.0. You'll need to do: "blank.png^[noalpha^[colorize:..." or make a fully black image and do: "black.png^[colorize:..."
DragonWrangler commented 2024-10-16 22:54:41 +02:00
Copy Link

Every occurance of colorization that has no base texture will cause this sadly.

Every occurance of colorization that has no base texture will cause this sadly.
whosit commented 2024-10-17 17:22:42 +02:00
Member
Copy Link

Should this bug be converted into a general bug for all mods that do this?
Or create a new one and link all these there? idk.

Should this bug be converted into a general bug for all mods that do this? Or create a new one and link all these there? idk.
flux commented 2024-10-19 06:55:23 +02:00
Member
Copy Link

"blank.png^[noalpha^[colorize:..."

i haven't tested this, but i don't think it's necessary to use blank.png. instead, use something like

[combine:16x16^[noalpha^[colorize:#000:255

> "blank.png^[noalpha^[colorize:..." i haven't tested this, but i don't think it's necessary to use blank.png. instead, use something like ```[combine:16x16^[noalpha^[colorize:#000:255```
DragonWrangler commented 2024-10-19 06:58:18 +02:00
Copy Link

that would work, however that would also take up a good bit more room if used in lots of occurences.

And it would take slightly more code.

that would work, however that would also take up a good bit more room if used in lots of occurences. And it would take slightly more code.
AliasAlreadyTaken commented 2024-10-29 05:19:07 +01:00
Owner
Copy Link

Is there a way to find all occurrences of that?

Is there a way to find all occurrences of that?
AliasAlreadyTaken added the
2. prio/interesting
 label 2024-10-29 05:19:16 +01:00
DragonWrangler commented 2024-10-29 05:23:21 +01:00
Copy Link

python script could easily work

python script could easily work
AliasAlreadyTaken added this to the Alias@work project 2024-10-29 05:43:44 +01:00
AliasAlreadyTaken removed this from the Alias@work project 2024-10-29 05:43:53 +01:00
DragonWrangler commented 2024-10-29 05:48:02 +01:00
Copy Link

A little python script I quickly made. No docs but here's a rundown of how it works.

  1. run python3 search.py (or whatever you name it) in your terminal (make sure that it's in the directory where all the mods you're testing are in.)
  2. input the keyword (or really whatever you're trying to find)
  3. input what to ignore.
  4. type yes or no depending on if you need to ignore more (in this case you'll want yes to allow you to add more options to avoid an fp (or multiple))
  5. Then input the number of extra keywords to ignore.
  6. Fill in all the extras then the script should run.

In the end it should tell you all the occurences of the keyword, and what file has it. Hope this helps.

@AliasAlreadyTaken pinging you since this is somewhat of a more important matter since 5.9.0 users and above can't see particles, but might get their chat spammed with warnings.

import re
from collections import defaultdict

def is_text_file(filepath):
    blacklisted_extensions = ('.png', '.jpg', '.jpeg')
    if filepath.lower().endswith(blacklisted_extensions):
        return False
    return True

def search_files(directory, include_term, exclude_terms):
    results = defaultdict(int)
    include_pattern = re.compile(re.escape(include_term), re.IGNORECASE)
    exclude_patterns = [re.compile(re.escape(term), re.IGNORECASE) for term in exclude_terms]
    for root, _, files in os.walk(directory):
        for file in files:
            file_path = os.path.join(root, file)
            if is_text_file(file_path):
                try:
                    with open(file_path, 'r', encoding='utf-8') as f:
                        text = f.read()
                        if include_pattern.search(text) and not any(pattern.search(text) for pattern in exclude_patterns):
                        results[file_path] = len(re.findall(include_pattern, text))
                except (UnicodeDecodeError, PermissionError):
                    pass
                for file, count in results.items():
                    print(f"\nFile: {file}")
                    print(f"  '{include_term}' found {count} times")
                    include_term = input("Enter the word or phrase to search for: ")
                    exclude_terms = []
                    exclude_term = input("Enter the word or phrase to exclude: ")
                    exclude_terms.append(exclude_term)
                    add_more = input("Would you like to add more words or phrases to ignore? (yes/no): ").strip().lower()
            if add_more == 'yes':
                try:
                    num_exclusions = int(input("How many more words or phrases would you like to exclude? "))
                for _ in range(num_exclusions):
                    additional_term = input("Enter a word or phrase to exclude: ")
                    exclude_terms.append(additional_term)
                except ValueError:
                    print("Invalid input. Please enter a number.")
                    
directory = os.getcwd()

search_files(directory, include_term, exclude_terms)```
A little python script I quickly made. No docs but here's a rundown of how it works. 1. run python3 search.py (or whatever you name it) in your terminal (make sure that it's in the directory where all the mods you're testing are in.) 2. input the keyword (or really whatever you're trying to find) 3. input what to ignore. 4. type yes or no depending on if you need to ignore more (in this case you'll want yes to allow you to add more options to avoid an fp (or multiple)) 5. Then input the number of extra keywords to ignore. 6. Fill in all the extras then the script should run. In the end it should tell you all the occurences of the keyword, and what file has it. Hope this helps. @AliasAlreadyTaken pinging you since this is somewhat of a more important matter since 5.9.0 users and above can't see particles, but might get their chat spammed with warnings. ```import os import re from collections import defaultdict def is_text_file(filepath): blacklisted_extensions = ('.png', '.jpg', '.jpeg') if filepath.lower().endswith(blacklisted_extensions): return False return True def search_files(directory, include_term, exclude_terms): results = defaultdict(int) include_pattern = re.compile(re.escape(include_term), re.IGNORECASE) exclude_patterns = [re.compile(re.escape(term), re.IGNORECASE) for term in exclude_terms] for root, _, files in os.walk(directory): for file in files: file_path = os.path.join(root, file) if is_text_file(file_path): try: with open(file_path, 'r', encoding='utf-8') as f: text = f.read() if include_pattern.search(text) and not any(pattern.search(text) for pattern in exclude_patterns): results[file_path] = len(re.findall(include_pattern, text)) except (UnicodeDecodeError, PermissionError): pass for file, count in results.items(): print(f"\nFile: {file}") print(f" '{include_term}' found {count} times") include_term = input("Enter the word or phrase to search for: ") exclude_terms = [] exclude_term = input("Enter the word or phrase to exclude: ") exclude_terms.append(exclude_term) add_more = input("Would you like to add more words or phrases to ignore? (yes/no): ").strip().lower() if add_more == 'yes': try: num_exclusions = int(input("How many more words or phrases would you like to exclude? ")) for _ in range(num_exclusions): additional_term = input("Enter a word or phrase to exclude: ") exclude_terms.append(additional_term) except ValueError: print("Invalid input. Please enter a number.") directory = os.getcwd() search_files(directory, include_term, exclude_terms)```
AliasAlreadyTaken added this to the Alias@work project 2024-10-29 05:52:51 +01:00
whosit commented 2024-10-29 08:38:47 +01:00
Member
Copy Link

re: DragonWrangler's code:
As far as I can see, this is a grep reimplementation...

Do we know exact change that caused these messages to appear?
Any specific issue or commit from MT's repo?

Blame'ing the error message leads nowhere. I don't really want to bisect the error appearance...

re: DragonWrangler's code: As far as I can see, this is a `grep` reimplementation... Do we know exact change that caused these messages to appear? Any specific issue or commit from MT's repo? Blame'ing the error message leads nowhere. I don't really want to bisect the error appearance...
DragonWrangler commented 2024-10-29 17:16:23 +01:00
Copy Link

@whosit

re: DragonWrangler's code:
As far as I can see, this is a grep reimplementation...

I always forget about the existance of grep, however the python script is probably simpler to use in this case.

Do we know exact change that caused these messages to appear?
Any specific issue or commit from MT's repo?

https://github.com/minetest/minetest/pull/14308

@whosit > re: DragonWrangler's code: > As far as I can see, this is a `grep` reimplementation... I always forget about the existance of `grep`, however the python script is probably simpler to use in this case. > Do we know exact change that caused these messages to appear? > Any specific issue or commit from MT's repo? https://github.com/minetest/minetest/pull/14308
whosit commented 2024-10-31 01:11:45 +01:00
Member
Copy Link

I've tried this:
grep . -rn -e '[^.][^.][ ]*"\^\[color' --exclude '*.py' --exclude '*.png'

Only nether stuff seems to have this pattern:

./mobs_redo/api.lua:3676:		damage_texture_modifier = def.damage_texture_modifier or "^[colorize:#c9900070",
./mobs_redo/api.txt:73:                   or default when enabled is "^[colorize:#c9900070".
./nether/nodes.lua:614:		texture = "^[colorize:#A00:255",
./nether/nodes.lua:618:	lava_particlespawn_def.texture = "^[colorize:#FB0:255"
./nether/nodes.lua:820:				texture = "^[colorize:#A00:255",
./nether/nodes.lua:824:			embers_particlespawn_def.texture = "^[colorize:#A50:255"
./unifieddyes/airbrush.lua:172:	local colorize = minetest.formspec_escape("^[colorize:#"..hexcolor..":255")

NPCs trigger similar error, but there's no similar patterns in code. Maybe it's some old NPCs with incorrectly defined textures? I'm not sure.

I've tried this: ```grep . -rn -e '[^.][^.][ ]*"\^\[color' --exclude '*.py' --exclude '*.png'``` Only nether stuff seems to have this pattern: ```bash ./mobs_redo/api.lua:3676: damage_texture_modifier = def.damage_texture_modifier or "^[colorize:#c9900070", ./mobs_redo/api.txt:73: or default when enabled is "^[colorize:#c9900070". ./nether/nodes.lua:614: texture = "^[colorize:#A00:255", ./nether/nodes.lua:618: lava_particlespawn_def.texture = "^[colorize:#FB0:255" ./nether/nodes.lua:820: texture = "^[colorize:#A00:255", ./nether/nodes.lua:824: embers_particlespawn_def.texture = "^[colorize:#A50:255" ./unifieddyes/airbrush.lua:172: local colorize = minetest.formspec_escape("^[colorize:#"..hexcolor..":255") ``` NPCs trigger similar error, but there's no similar patterns in code. Maybe it's some old NPCs with incorrectly defined textures? I'm not sure.
tour commented 2025-07-10 15:07:33 +02:00
Member
Copy Link

upstream's master has already implemented a fix for this.

but our yl_stable branch is several commits behind. There is just one commit where I'm not exactly sure whether we want it on yl bc. it registers 4? new nodes (I believe each xpane needs 2 nodes...) (nodes.lua @ 957fdc887b)

IMO these 4 nodes should not be a problem (and the pane looks quite cool :-)

upstream's master has already implemented a fix for this. but our yl_stable branch is several commits behind. There is just one commit where I'm not exactly sure whether we want it on yl bc. it registers 4? new nodes (I believe each xpane needs 2 nodes...) (nodes.lua @ https://gitea.your-land.de/your-land/nether/commit/957fdc887b81bc802ed6a3000e75c07c355e5618) IMO these 4 nodes should not be a problem (and the pane looks quite cool :-)
tour added the
4. step/want approval
 label 2025-07-10 21:48:47 +02:00
AliasAlreadyTaken commented 2025-07-25 22:04:54 +02:00
Owner
Copy Link

The problem with the nether is that I'd like to upgrade to the new nether, but that requires us to drop the old nether.

Until this problem is solved we can't upgrade OR we'd have to cut out the mapgen for the new nether.

The problem with the nether is that I'd like to upgrade to the new nether, but that requires us to drop the old nether. Until this problem is solved we can't upgrade OR we'd have to cut out the mapgen for the new nether.
tour commented 2025-07-25 23:05:04 +02:00
Member
Copy Link

OK, so no automatic updates.
yl_stable looks like a big mess already (many manual merges). So I simply cherry-picked some bugfix-commits.

OK, so no automatic updates. yl_stable looks like a big mess already (many manual merges). So I simply cherry-picked some bugfix-commits.
👍 1
tour added
4. step/ready to QA test
 and removed
4. step/want approval
 labels 2025-07-25 23:05:19 +02:00
AliasAlreadyTaken added this to the Next milestone 2025-07-25 23:13:37 +02:00
AliasAlreadyTaken removed this from the Alias@work project 2025-07-25 23:13:40 +02: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/petz

yet another petz bugz.

  
3. source/testserver

Originates on the testserver, no effect on main yet

  
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/possible close

Should be closed, but a second opinion is asked

  
4. step/QA main

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

  
4. step/QA NOK

Fix didn't yield the expected results

  
4. step/QA OK

tested

  
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.

  
kind/standalone

issues that don't depend on internal access and can be implemented as a stand-alone project

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/petz
3. source/testserver
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/possible close
4. step/QA main
4. step/QA NOK
4. step/QA OK
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
kind/standalone
Milestone
Clear milestone
No items
No Milestone
Next
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
AliasAlreadyTaken
6 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#7410
No description provided.
Delete Branch "%!s()"

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?