Bug report form completely broken

Anaminus · April 11, 2022, 4:00pm

Reproduction Steps

Navigate to the bug report wizard while being me. ¯\_(ツ)_/¯ Maybe it has to do with whatever data is currently saved in the form.

Expected Behavior

I am able to fill out and submit bug reports without any problems.

Actual Behavior

After filling in a bug report and attempting to submit it, the attempt failed, and the following error was displayed at the top of the page:

<!DOCTYPE html>

After closing the page, attempting to go the bug report wizard now results in a blank page. That is, I am completely unable to submit any reports at all. The following error is present in the debug console:

Uncaught TypeError: can't access property "isReadOnly", t is undefined
    createCurrent _application-bffc0e1637f61eb27bb68baf723f0c1f265bcda294bec4659a386e31ae2248fb.js:52063
    current _application-bffc0e1637f61eb27bb68baf723f0c1f265bcda294bec4659a386e31ae2248fb.js:10254
    initialize _application-bffc0e1637f61eb27bb68baf723f0c1f265bcda294bec4659a386e31ae2248fb.js:81598
    initialize _application-bffc0e1637f61eb27bb68baf723f0c1f265bcda294bec4659a386e31ae2248fb.js:8256
    runInitializers _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:49335
    each _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:67724
    walk _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:67638
    each _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:67568
    topsort _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:67576
    _runInitializer _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:49361
    runInitializers _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:49333
    _bootSync _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:47768
    domReady _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:47668
    _run _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:67275
    _join _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:67251
    join _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:66968
    h _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:53760
    bind _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:53864
    l _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:3776
    c _vendor-bcdd7d658b70fae28b38aedf12b9a16ee2c5545475fc3e6f574d860f0679e65f.js:3844
_application-bffc0e1637f61eb27bb68baf723f0c1f265bcda294bec4659a386e31ae2248fb.js:52063:59

In general, my experience with the bug report wizard has been extremely poor. Until it is truly in a stable state, I would like an alternative way to submit reports. If there’s a standardized format I can follow, I am willing to do that, but I need to be able to submit reports without any hindrances. So far, the bug report wizard has been a constant hurdle, to the point that I am reluctant to submit reports entirely.

Browser: Firefox Developer Edition 100.0 Beta 4
Date First Experienced: 2022-04-06
Date Last Experienced: 2022-04-11

Hooksmith · April 11, 2022, 4:31pm

Thanks for pointing this out, team is investigating currently.

LuaCow · April 11, 2022, 4:38pm

@Anaminus Do you happen to know/have a screenshot of the bug report you were filling in?

Anaminus · April 11, 2022, 4:52pm

A screenshot of the error message:

I don’t have a screenshot of the rest, but I have a copy of the text that should mostly represent what was filled in at the time:

Title

Tag names containing null characters allow duplicate tags

Reproduction Steps

When a tag name contains a null character, the name is truncated:

```lua
CollectionService:AddTag(instance, "ABC\0DEF")
print(CollectionService:HasTag(instance, "ABC\0DEF")) --> false
print(CollectionService:HasTag(instance, "ABC")) --> true
```

To ensure correctness, an error should be thrown instead.

Furthermore, if a tag is truncated, it can be added to an instance multiple times:

```lua
CollectionService:AddTag(instance, "A\0")
CollectionService:AddTag(instance, "A\0")
CollectionService:AddTag(instance, "A\0")
print(CollectionService:GetTags(instance)
--> {
--     [1] = "A",
--     [2] = "A",
--     [3] = "A"
-- }
```

These duplicate tags are saved within serialized formats. When decoding tags, duplicates should be collapsed down to one.

The following script reproduces the issue:

```lua
local CollectionService = game:GetService("CollectionService")

-- Call GetTags, expect result to be equivalent to `want`.
local function passTags(inst, want)
	local got = CollectionService:GetTags(inst)
	if #got == #want then
		local ok = true
		for i, v in ipairs(want) do
			if got[i] ~= v then
				ok = false
				break
			end
		end
		if ok then
			return
		end
	end
	local line = debug.info(2, "l")
	print(string.format("line %d: tags: {%s} ~= {%s}", line, table.concat(got,", "), table.concat(want,", ")))
end

-- Call AddTag, expect no error.
local function passAdd(inst, tag)
	local ok, err = pcall(CollectionService.AddTag, CollectionService, inst, tag)
	if ok then
		return
	end
	local line = debug.info(2, "l")
	print(string.format("line %d: add %q: %s", line, tag, tostring(err)))
end

-- Call AddTag, expect error.
local function failAdd(inst, tag)
	local ok = pcall(CollectionService.AddTag, CollectionService, inst, tag)
	if not ok then
		return
	end
	local line = debug.info(2, "l")
	print(string.format("line %d: add %q: expected error", line, tag))
end

---- Tests

local inst = Instance.new("Folder")
passTags(inst, {})

passAdd(inst, "A")
passAdd(inst, "A")
passTags(inst, {"A"})

passAdd(inst, "B")
passTags(inst, {"A", "B"})

failAdd(inst, "Z\0")
passTags(inst, {"A", "B"})

failAdd(inst, "Z\0")
passTags(inst, {"A", "B"})

failAdd(inst, "Z\0")
passTags(inst, {"A", "B"})

passAdd(inst, "C")
passTags(inst, {"A", "B", "C"})
```

Expected Behavior

The script prints nothing, indicating no assertions have failed.

Actual Behavior

The following failed assertions are printed:

```text
line 51: add "Z\000": expected error
line 52: tags: {A, B, Z} ~= {A, B}
line 54: add "Z\000": expected error
line 55: tags: {A, B, Z, Z} ~= {A, B}
line 57: add "Z\000": expected error
line 58: tags: {A, B, Z, Z, Z} ~= {A, B}
line 61: tags: {A, B, Z, Z, Z, C} ~= {A, B, C}
```

Anaminus · April 19, 2022, 3:45pm

Just checking in on the progress of this. It has been over a week, and I am still unable to submit bug reports. If this is going to take a while, I’d like to explore temporary solutions, such as:

Have an administrator reset my stored state for the report wizard, which might fix the problem.
Allow me to report bugs manually in some category (such as here), and have a moderator move the topic to the correct category.
Have someone to submit reports on my behalf.

Qualadore · April 19, 2022, 5:23pm

Messaging Bug Support group might work as a temporary solution? You just send them a message as if you were posting a topic. Approval is manual but I had a report moved within a few hours last month.

LuaCow · April 22, 2022, 6:49pm

Hey @Anaminus,

Thanks for your patience.

We’ve been working to get a long-term fix in place, but in the meantime I’ve cleared your latest submission so you should be able to use the wizard again.

However, the markdown from the submission you mentioned below will still cause the issue until a fix is in place. I’ll update the thread when this is ready!