| commit | f11f6544fffd516bc118b05359d1f69b94cdb97c | [log] [tgz] |
|---|---|---|
| author | Sen Jiang <senj@fuchsia.infra.roller.google.com> | Thu Aug 05 00:01:06 2021 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 04 17:02:09 2021 -0700 |
| tree | 441bdab2ba238037221a731b1ef79134aa01775f | |
| parent | d0a02f8e0b29a589b29b4c41a09e6d2282150a06 [diff] |
[roll] Roll fuchsia [omaha-client] Policy return minimum wait for standard logic. When using standard logic, even though we have accurate monotonic time, it is possible that updates has been throttled, if a scheduled update gets throttled, it will come back to ask `compute_next_update_time` again without updating `last_update_time`, so in this case it could return a time in the past or future, depends on the fuzzing, but eventually it will always return a time in the past and results in an infinite loop until the rate limit period is passed. This CL fixes this case by adding minimum wait to the returned `CheckTiming` even in standard logic. Original-Fixed: 82023 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/563926 Original-Revision: a00bb5965fbbf9f9f454eafb98ec412c5933e4bc GitOrigin-RevId: 311cd6210afa35f6207f5f7031ff60bcac87bd04 Change-Id: If77dafef1f843c0792eb5b79124ee9c9512ee0ba
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.