aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/html
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/app: move to GOMOD from GOPATHTaras Madan2024-02-141-2/+24
| | | | The deployment takes 1.1G now. Let's check what can be removed after deployment.
* dashboard: introduce an emergency stop modeAleksandr Nogikh2024-01-091-0/+12
| | | | | | | | Add an emergency stop button that can be used by any admin. After it's clicked two times, syzbot stops all reporting and recoding of new bugs. It's assumed that the stop mode is revoked by manually deleting an entry from the database.
* dashboard: display fix candidate info on the bug pageAleksandr Nogikh2023-07-261-0/+5
|
* dashboard: allow admins to retry individual bisectionsSpace Meyer2023-06-121-1/+1
| | | | | | | | | | Changes to our rootfs, compilers or bisection logic regularly cause regressions in our bisection accuracy. Retrying them currently entails fiddling with the GCP datastore directly or mass deleting all failed bisections. This change will allow us to retry specific bisections with a single click.
* pkg/html: add hover styles for tree origin table rowsAleksandr Nogikh2023-05-151-3/+15
|
* dashboard: display bug origin tree testing resultsAleksandr Nogikh2023-05-121-0/+12
| | | | | Display them as a collapsible block on the bug info page. Use colors to distinguish results.
* dashboard: support filtering over multiple labelsAleksandr Nogikh2023-05-102-2/+76
| | | | | | For each label, allow only one value to be specified. At the same time, allow multiple different labels (subsystem, origin, prio, etc) be specified together.
* dashboard: support bug labelsAleksandr Nogikh2023-04-271-2/+2
| | | | | | | | | | | | | | | | Let bug labels come in three flavours: 1) Bug labels with multiple values (e.g. `subsystems`). 2) Bug labels with only one value (e.g. `prio`). 3) Flags. Let users configure bug labels via email by issuing the following commands: #syz set subsystems: abc, def #syz set no-reminders #syz unset no-reminders Also let users set tags for invididual bugs in reported bug lists: #syz set <1> some-tag
* dashboard: display discussions info on the main pageAleksandr Nogikh2023-04-111-0/+9
|
* pkg/html/pages: sort table also by non-displayed valuesAleksandr Nogikh2023-04-111-2/+7
| | | | | | | | Now we're limited to sorting table columns exactly by the displayed content, but this is not always convenient. If the `sort-value` attribute is present, prefer it to the element's text content.
* dashboard: display collapsible info sections on the bug pageAleksandr Nogikh2023-04-072-0/+43
| | | | | Instead of showing tons of extra information to the user, only show the collapsed titles with counts and let user toggle the sections they need.
* dashboard: put cause and fix bisection info blocks closerAleksandr Nogikh2023-04-071-0/+12
| | | | | Align them horizontally instead of vertically. This will save space on the bug info page.
* dashboard/app: don't wrap assets column in crashes tableDmitry Vyukov2023-04-031-2/+1
| | | | | | Make each crash table row take 1 line. Otherwise it looks unesthetic and vertical space is wasted no other column has data on the second/third/fourth lines.
* dashboard/app: remove repetition on subsystems pageDmitry Vyukov2023-04-031-1/+1
| | | | | | | | | Currently it repeats that this is a list of subsystems 3 times: 1. "Subsystems" tab 2. "The list of subsystems" caption 3. "Subsystems list" table caption Leave only one of them.
* pkg/html/html.go: remove unnecessary conversionTaras Madan2023-02-241-1/+1
|
* dashboard: add a feedback buttonAleksandr Nogikh2023-02-211-0/+5
|
* dashboard: display the subsystem listAleksandr Nogikh2023-02-171-2/+2
| | | | Take the counts from the cache, include links to the filtered bug views.
* dashboard: display the list of applied filtersAleksandr Nogikh2023-02-141-1/+5
| | | | | | | Currently it's non obvious whether and what filters are applied to a bug list. Display the list to the user and enable them to drop individual filters.
* dashboard: display subsystems on the bug pageAleksandr Nogikh2023-02-141-2/+2
| | | | | Currently the information is only displayed on the main page, which is not very convenient.
* dashboard: display subsystems in bug listsAleksandr Nogikh2023-01-272-0/+30
| | | | | To generate filtering URLs, use the ability of context.Context to carry on variable values.
* dashboard: display assets in the crash tableAleksandr Nogikh2023-01-031-0/+9
|
* pkg/html: add a commitLink template functionAleksandr Nogikh2022-12-141-0/+6
|
* dashboard: visualize stale reprosAleksandr Nogikh2022-08-261-0/+4
| | | | | When rendering a crash list, strike stale repros with a line (like the <s></s> tag does).
* pkg/html/pages: switch to go:embedDmitry Vyukov2022-05-234-124/+108
| | | | | | | | | | We use clumsy generate scripts that embed some static files. Switch to the new go:embed thing (added in Go 1.16): https://pkg.go.dev/embed It's much nicer, does not require separate generate step and does not lead to additional diffs in code reviews. go:embed can only embed "files read from the package directory or subdirectories", so we need to move these assets to the package dir.
* pkg/html: move some functions to sub-packageDmitry Vyukov2022-05-234-22/+34
| | | | | Move functions that need embed assets to a separate package. In preparation for the next change.
* dashboard/app: linkify source files in sample reportsDmitry Vyukov2022-05-201-0/+4
| | | | Fixes #652
* dashboard/app: add #crash_div to style.cssAlexander Potapenko2022-05-201-0/+10
| | | | | | | | Currently we're using a TEXTAREA on the /bug page to display logs, which won't let us do fancy things like links. Replacing it with a `<div id="crash_div"><p><pre>` will allow HTML formatting.
* tools/syz-testbed: store html templates in filesAleksandr Nogikh2022-02-251-2/+12
|
* dasboard: add crash stats pageAleksandr Nogikh2022-02-251-1/+59
| | | | | Show top crashers for X last days. Show graph with daily shares of crashes that satisfy user-entered regexps.
* dashboard/app: add page with manager stats graphsDmitry Vyukov2021-12-061-0/+57
|
* tools/syz-testbed: show diffs and p-valuesAleksandr Nogikh2021-12-061-0/+13
| | | | | | | | | | Enable the user to specify the pivot column for the stats table. If such a column is set, calculate and print the relative difference between checkouts and p-values for the estimation of statistical significance of the experimental data. For the p-value calculation use the existing implementation from the go-benchstat tool.
* all: adjust Kernel Build Commit column widthAleksandr Nogikh2021-07-131-1/+0
| | | | | | | | After 12 digit kernel commit hashes were introduced, it turned out that there remains one table that cannot accommodate such values. Fix this by removing the max-width property from .list_table .stat. This class is not used for data that needs to be truncated anyway.
* dashboard/app/static/style.css: make tag cell widerAleksandr Nogikh2021-07-131-2/+1
| | | | | | | 40pt is not enough for 12 byte hashes. At the same time, 60pt is more than needed for 8 byte hashes. Remove fixed width for the tag column, let only the upper limit remain.
* all: make all kernel commit hashes 12 byte longAleksandr Nogikh2021-07-131-1/+1
| | | | | | | | | Currently email and web templates use 8 byte representation of commit hashes. While this is enough for syzkaller, it becomes less and less suitable for Linux kernel tags. Switch to 12 byte representation for all Linux kernel commit hash mentions.
* pkg/build, pkg/html: make bash path OS compatibletigergao992020-10-301-1/+1
|
* tools/syz-reporter: add summary and reproducer informationJouni Hogander2020-10-241-0/+1
|
* dashboard/app: show more detailed info about bisectionsDmitry Vyukov2020-10-221-1/+8
| | | | | | | | 1. Split cause/fix bisections in the bug table. 2. Show if bisection is inconclusive/unreliable in the bug table. 3. Show if bisection is unreliable on the bug page. Update #2098
* pkg/build, pkg/html: move generation logic into separate scriptsDmitry Vyukov2020-09-152-8/+15
| | | | | | | | Mentions of "// Code generated ... DO NOT EDIT." in these Go files somehow prevents golangci-lint from checking them. And github treats them as auto-generated as well. I guess some code somewhere has some imprecise heuristics. Move generation into separate shell scripts. Also cleaner.
* all: mark auto-generated filesDmitry Vyukov2020-07-292-2/+3
| | | | | | | | | | Use the standard Go convention for Go files: https://golang.org/pkg/cmd/go/internal/generate Use github linguish for other files: https://github.com/github/linguist#generated-code Both are understood by github and should result in these files being collapsed in PRs by default.
* dashboard/app: add navigation buttonsDmitry Vyukov2020-07-091-0/+24
| | | | | | Currently we have only "fixed" link at the top of the page. "invalid" is missing and this is not scalable. Add natigation buttons (tabs) for main pages.
* pkg/html: add function to format JS timeDmitry Vyukov2020-07-091-0/+5
|
* pkg/html: regenerateDmitry Vyukov2020-04-291-0/+5
|
* dashboard/app: allow reporting of BisectFix resultsZubin Mithra2019-08-301-0/+8
| | | | | | | | | | | | | * Modify mail_bisect_result.txt to allow for sending fix bisection results. * Modify BisectResult to have a Fix field; introduce selectBisect for use within the template for choosing between BisectCause/BisectFix fields. * Modify bisectFromJob() to return BisectResult with Fix field set if relevant. * Modify the tests inside bisect_test.go to account for bisect fix related reporting emails. * Modify incomingMail() to ignore any emails from syzbot itself.
* dashboard/app: allow main UI to show bisect resultsZubin Mithra2019-08-081-3/+2
| | | | | | | | | | | * Modify uiBug type. Rename BisectCause to BisectCauseDone. Introduce BisectFixDone. * Modify createUIBug() and MergeUIBug() to set the above fields appropriately. * Modify bug_list to display the bisection status; remove yesSort() as it is not used anymore. Adjust ".list_table .stat" to appropriate width. * Add TestBugBisectionStatus() to check bisection status on main page. * Add file from running "make generate": pkg/html/generated.go
* pkg/html: regenerateDmitry Vyukov2019-04-081-3/+3
|
* dashboard/app: split dashboard per-namespaceDmitry Vyukov2019-04-081-0/+6
| | | | | | | We now have too many namespaces and bugs. Main page takes infinity to load. Also almost nobody is interested in more than 1 namespace. So split main page per-namespaces.
* pkg/html: update generated fileDmitry Vyukov2019-03-251-0/+7
|
* dashboard/app: properly handle build failuresDmitry Vyukov2019-03-251-0/+8
| | | | | | | | | Separate kernel and syzkaller build failures. Fix logic to understand when a build is fixed: look if kernel/syzkaller commit changes to understand if it's a new good build or re-upload of an old build. Fixes #1014
* pkg/html: add reference for 12-char hashes in tagsDmitry Vyukov2019-03-211-1/+2
|
* dashboard/app: use 12-char hash in Fixes tagsDmitry Vyukov2019-03-211-0/+10
| | | | | | | @ebiggers pointed out that Fixes tags should use 12-char hash: https://groups.google.com/d/msg/syzkaller-bugs/yUhRrLD6T6A/3TMwOWvWAgAJ I can't find any documentation on this, but it looks like most existing tags follow this convention so use 12-char hashes.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-04-01 08:54:36 +0000