Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: b6fb7aad68ce9f58d7c1c3a9f345ea7cb9ea0015
      
https://github.com/WebKit/WebKit/commit/b6fb7aad68ce9f58d7c1c3a9f345ea7cb9ea0015
  Author: Issac Roy <[email protected]>
  Date:   2026-09-03 (Thu, 03 Sep 2026)

  Changed paths:
    M 
Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/templates/documentation.html

  Log Message:
  -----------
  [resultsdbpy] The EWS upload and query endpoints are missing from 
/documentation
https://bugs.webkit.org/show_bug.cgi?id=323344
<rdar://problem/186585819>

Reviewed by Sam Sneddon.

`/documentation` describes every results-database endpoint except the three EWS
ones. `/upload/ews`, `/results-ews` and `/results-ews/tests` have no entry, so
the only way to learn that its `results` is a flat map rather than a trie, that
`flaky_type` decides which table an upload lands in, or that a query with no
matches answers 404 rather than an empty list is to read `ews_controller.py`.

Document the three, including the behaviours a caller cannot guess from the
shape of a response: `limit` is applied per test rather than shared across the
batch, so a 50-test request can return 50 times the limit; `MAX_TESTS_PER_QUERY`
caps a request at 100 names, but the names travel in the query string, so long
test paths overflow the request line well before that cap; a `timestamp` may
backfill an older result but not one more than five minutes ahead; and
`/results-ews/tests` defaults to 100 names, which makes a default-length answer
a sample rather than the whole catalog.

* 
Tools/Scripts/libraries/resultsdbpy/resultsdbpy/view/templates/documentation.html:

Canonical link: https://commits.webkit.org/320469@main



To unsubscribe from these emails, change your notification settings at 
https://github.com/WebKit/WebKit/settings/notifications

Reply via email to