NEW 231707
Committers/contributors autocomplete failing
https://bugs.webkit.org/show_bug.cgi?id=231707
Summary Committers/contributors autocomplete failing
Sam Sneddon [:gsnedders]
Reported 2021-10-13 16:38:01 PDT
Many people are having Bugzilla autocompletion fail to work since https://commits.webkit.org/242672@main landed six days ago. While https://commits.webkit.org/241245@main landed over a month ago, committers-autocomplete.js is served as cacheable for a year, hence we actually need to wait a year for caches to expire or load the file from a different URL (e.g. by adding a query string to it).
Attachments
Jonathan Bedard
Comment 1 2021-10-13 16:41:37 PDT
(In reply to Sam Sneddon [:gsnedders] from comment #0) > committers-autocomplete.js is served as cacheable for a year, hence we That's the bit that seems like the bug. contributors.json is updated once or twice a month.
Sam Sneddon [:gsnedders]
Comment 2 2021-10-14 05:44:17 PDT
(In reply to Jonathan Bedard from comment #1) > (In reply to Sam Sneddon [:gsnedders] from comment #0) > > > committers-autocomplete.js is served as cacheable for a year, hence we > > That's the bit that seems like the bug. contributors.json is updated once or > twice a month. contributors.json is uncacheable (which arguably is bad too!), it's only the committers-autocomplete.js script which is cached for too long.
Radar WebKit Bug Importer
Comment 3 2021-10-14 05:44:36 PDT
Jonathan Bedard
Comment 4 2021-10-14 08:02:03 PDT
(In reply to Sam Sneddon [:gsnedders] from comment #2) > (In reply to Jonathan Bedard from comment #1) > > (In reply to Sam Sneddon [:gsnedders] from comment #0) > > > > > committers-autocomplete.js is served as cacheable for a year, hence we > > > > That's the bit that seems like the bug. contributors.json is updated once or > > twice a month. > > contributors.json is uncacheable (which arguably is bad too!), it's only the > committers-autocomplete.js script which is cached for too long. Oh, missed that it was the JS file. That makes more sense.
Note You need to log in before you can comment on or make changes to this bug.