Skip to content

Fix string representation of values in settings panel #2793

Fix string representation of values in settings panel

Fix string representation of values in settings panel #2793

Triggered via pull request November 25, 2025 23:02
Status Success
Total duration 7m 19s
Artifacts 24

test.yml

on: pull_request
Matrix: mysql
Matrix: postgres
Matrix: sqlite
Fit to window
Zoom out
Zoom in

Annotations

10 notices
Coverage
Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).
Coverage
HTTP Request: PATCH https://api.github.com/repos/django-commons/django-debug-toolbar/issues/comments/3562248585 "HTTP/1.1 403 Forbidden"
Coverage
Update previous comment
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar/issues/2263/comments "HTTP/1.1 200 OK"
Coverage
HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar/pulls/2263 "HTTP/1.1 200 OK"
Coverage
Generating comment for PR
Coverage
HTTP Request: GET https://api.github.com/repos/django-commons/django-debug-toolbar "HTTP/1.1 200 OK"
Coverage
Starting action

Artifacts

Produced during runtime
Name Size Digest
coverage-mysql-3.10
176 KB
sha256:df597e53d08bfd4f3e720559eacd00cda0a5ff4f75fc59c1834916ee21ea8ee8
coverage-mysql-3.11
181 KB
sha256:0063d2c12e9d5f3bdc37449ab0b74cff0cc6f63fef7696c79af49420938b49df
coverage-mysql-3.12
240 KB
sha256:3af99726b189b02cb993213125c3a6681051d1b5a2428373d660c6047e4b3597
coverage-mysql-3.13
241 KB
sha256:6da8d43b66eb6c956c2133ea31b424608077618ed9025707c338bb3bc3325646
coverage-mysql-3.14
177 KB
sha256:4d14371ea7ddd66c73534ee4f5be2a91170c7741a80337bf85514c4a34da4ae6
coverage-postgis-3.10
179 KB
sha256:0b755cb0f1f219d9f4c9a63cc64a6cf501d5fbd2eaf8f7717779e1e6f1a74d15
coverage-postgis-3.11
184 KB
sha256:bbd234de5957fa3264dda65e800bce0e304887db6ef9796df3baf4a87fc5fc87
coverage-postgis-3.12
246 KB
sha256:baa6fc2d24d91bcdf73d505591f9d2dca0c9e9bf71361a3c2d8c29e37c64c00c
coverage-postgis3-3.13
244 KB
sha256:6c3a2bf2a031897919fb408c76db41efa63f61eac22e99056226c168a649b905
coverage-postgis3-3.14
181 KB
sha256:2b2581ca0d2576e709bfda45c1da9f68a1cb00758eff17960786ae0348cfb95c
coverage-postgresql-3.10
179 KB
sha256:6f4af6caca1b0e3590f9d926d5f08072b9d824c7f4880f9c8751bbafa0a4f233
coverage-postgresql-3.11
184 KB
sha256:0cc51c786a059366405f4909a423e48f3c231de47babe3a3b366e15f65612d84
coverage-postgresql-3.12
246 KB
sha256:8d58618de40b9a49c9ef4f4d64fa0f15f522deaec050ea23c31cd853a0195351
coverage-psycopg3-3.10
179 KB
sha256:4a7c99265a50d3ac4bf71c32982941c99f212b1edfd8414327e4f5386c3b1cdf
coverage-psycopg3-3.11
185 KB
sha256:487ed74211885609805205df21fadb5b73ccb9bdd87cac50448066ae88649985
coverage-psycopg3-3.12
245 KB
sha256:be413dba6a64a484fa7d9bd86dbd8009d42d8bb45f73763fd19989e0abf1a054
coverage-psycopg3-3.13
244 KB
sha256:9ebb47ffd040dbf57276753a2462718ee01e56cd3b2393c94cf46621694fab4c
coverage-psycopg3-3.14
181 KB
sha256:dd43650995f29e3b32a03d68d49a0f1e77f48e61ee0e22547ea27f38f89a3bd4
coverage-sqlite-3.10
176 KB
sha256:5eba25667ac0bd0eea157e4976719194d0de44d955a834f55e33a486784a4689
coverage-sqlite-3.11
180 KB
sha256:724e8d1b1f377f6decdd7b06fa2a0d13e10601aabe961f204bafa01e47cfe98d
coverage-sqlite-3.12
240 KB
sha256:cbf224b26d33addb64c10f49f10ba76440db673316a2c3c09127923e6d0cc0db
coverage-sqlite-3.13
240 KB
sha256:635915fbea83c5cb39ea1c532cfc3d474a035a5505cb9de7d4994ff3df690146
coverage-sqlite-3.14
177 KB
sha256:61efbd8261984f2bc993ba51f238b4ad39a8ac4d1e48a93b56c0e0f9cff5ec67
python-coverage-comment-action
1.4 KB
sha256:8b27296b622be1d9837fa9b523db53171e0e36ba3c9641629f49976712e77fe6