syz - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	dashboard: extend bug's JSON representation	Aleksandr Nogikh	2025-12-29	1	-9/+33
\| \| \| \|	Add status, crash, fix, close and commit dates.
*	dashboard: factor out uiBugDetails and loadBugDetails	Aleksandr Nogikh	2025-12-29	1	-10/+10
\| \| \| \| \| \| \|	Separate the code that loads all details about a particular bug from the code that is only necessary for rendering a bug page on Web UI. These can be used in mass bug exports.
*	all: use any instead of interface{}	Dmitry Vyukov	2025-12-22	1	-2/+2
\| \| \| \|	Any is the preferred over interface{} now in Go.
*	dashboard/app: ns/cover?jsonl=1 supports manager and subsystem selection	Taras Madan	2025-06-06	1	-4/+16
\| \| \| \| \|	1. Refactor handleHeatmap. 2. Introduce function options. Build them from http.Request.
*	dashboard/app: allow to set spanner context only from tests	Taras Madan	2025-05-05	1	-1/+1
\| \| \| \|	getSpannerClient returns prod client as a default.
*	dashboard/app: export info about uncovered blocks as well	Dmitry Vyukov	2025-04-10	1	-26/+13
\| \| \| \| \| \| \| \|	Currently it's only possible to understand total number of uncovered blocks in a function (implicitly defined by Instrumented field). This does not allow to render coverage data, nor do detailed analysis on line level. Export detailed info about both covered and uncovered blocks. This allows to e.g. calculate coverage percent for kernel interfaces.
*	pkg/manager: export programs + coverage jsonl	Taras Madan	2025-02-28	1	-27/+8
\| \| \| \| \|	The export is quite big but is generated fast. Every line is a valid json object representing the single program coverage.
*	dashboard/app: fix coverage jsonl formatting	Taras Madan	2025-02-06	1	-1/+1
\|
*	dashboard/app: export coverage json	Taras Madan	2025-02-06	1	-0/+120
\|
*	dashboard/api: add Client type	Dmitry Vyukov	2024-10-15	1	-3/+3
\|
*	dashboard/api: add "Link" to link fields	Dmitry Vyukov	2024-10-15	1	-4/+4
\|
*	dashboard/api: add package	Dmitry Vyukov	2024-10-15	1	-72/+25
\| \| \| \| \|	Move JSON API structs to a separate package. These definitions are also needed by tools that consume the API.
*	dashboard: add syzkaller commit to the backports json	Aleksandr Nogikh	2024-09-12	1	-12/+14
\| \| \| \|	Also, slightly refine the field names.
*	dashboard: export missing backports as json	Aleksandr Nogikh	2024-09-12	1	-0/+68
\| \| \| \| \|	Also include more information into the output: kernel config and reproducer links.
*	dashboard: include fix commits into terminal page JSONs	Aleksandr Nogikh	2024-04-15	1	-21/+22
\| \| \| \| \|	There's little sense to make users query that information in separate queries when we already have it available.
*	dashboard/app: export ReportLink as a json	Taras Madan	2023-10-26	1	-0/+2
\|
*	dashboard/app: export bug id	Taras Madan	2023-07-04	1	-0/+2
\| \| \| \| \|	Let's assume we don't know fixing commit. Exporting bug id we allow external systems to group our reports.
*	dashboard/app: export fix commits repo + branch as json	Taras Madan	2023-07-04	1	-18/+14
\|
*	dashboard/app: export crash title as json	Taras Madan	2023-07-03	1	-0/+2
\|
*	dashboard/app/public_json_api.go: export all crashes, not one	Taras Madan	2023-06-29	1	-12/+17
\|
*	dashboard: export causeBug repo + branch	Taras Madan	2023-06-29	1	-15/+26
\|
*	dashboard/app: export cause-commit as a json	Taras Madan	2023-06-29	1	-3/+15
\|
*	dashboard/app/getjson_test.go: rename fixCommit to vcsCommit	Taras Madan	2023-06-29	1	-5/+5
\|
*	dashboard/app: export fix-commits as a json	Taras Madan	2023-06-20	1	-2/+23
\|
*	dashboard/app: add bugGroup json reporting	Taras Madan	2023-06-19	1	-0/+33
\|
*	dashboard/app: prepare json generation code for extension	Taras Madan	2023-06-19	1	-6/+19
\|
*	dashboard/app: export discussion link, jsonAPI	Taras Madan	2023-06-19	1	-3/+11
\|
*	dashboard/app: return JSON data for the /bug requests with "&json=1" (#2823)	tarasmadan	2021-10-25	1	-0/+43