w3c/network-error-logging Issues

Last updated Feb 22, 2025, 5:54:59 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

11 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time left	Time past SLO
#27	error codes should ideally link to definitions	❌	10 years		10 years
#32	Investigate report-uri management workflows	❌	10 years		10 years
#84	Make `report_to` field optional	❌	6.7 years		6.6 years
#107	Disallow "hop-by-hop" headers in `request_headers` and `response_headers`	❌	6 years		6 years
#119	Define HTTP/3 Error Type	❌	5.3 years		5.3 years
#120	server_ip is likely not defined correctly.	❌	5.2 years		5.2 years
#156	JSON validation schema	❌	1.4 years		1.4 years
#181	Redefine network request in terms of Fetch	❌	2.3 weeks		1.3 weeks
#183	Redefine report delivery in terms of Fetch	❌	2 weeks		1 week
#184	Map NEL phases to fetch	❌	2 weeks		1 week
#185	Should some Predefined network error types map directly to fetch error states?	❌	2 weeks		1 week
#188	Deal with fetchParams	✔	4 days	3 days