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).
(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.
(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.
<rdar://problem/84252131>
(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.