| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | pkg/validator: fix regexp mistake | Taras Madan | 2024-11-07 | 2 | -7/+13 |
| | | | | | | | | | The main problem - kernel file path may contain "-". Let's allow it. Side problems: 1. Two -- are better to be blocked. It may be used as an SQL comment. 2. Some regexp engines consider "-" as a range. Let's move it to the end. | ||||
| * | pkg/validator: target value is not empty by default | Taras Madan | 2024-09-30 | 2 | -0/+5 |
| | | | | | | | The consistency make the code more predictable. We want all the values to be non-empty. If "empty" is an option - use validator.AnyOk(validator.EmptyStr(target), otherCheck(target)). | ||||
| * | dashboard/app: add file coverage page | Taras Madan | 2024-09-16 | 1 | -1/+5 |
| | | | | | | | | | | | | | | | It directly uses the coverage signals from BigQuery. There is no need to wait for the coverage_batch cron jobs. Looks good for debugging. Limitations: 1. It is slow. I know how to speed up but want to stabilize the UI first. 2. It is expensive because of the direct BQ requests. Limited to admin only because of it. 3. It merges only the commits reachable on github because of the gitweb throttling. After the UI stabilization I'll save all the required artifacts to spanner and make this page publicly available. To merge all the commits, not the github reachable only, http git caching instance is needed. | ||||
| * | pkg/validator: initial code | Taras Madan | 2024-08-22 | 2 | -0/+182 |
