From e486e6c0c73dc434a62aa85d12da378e9953fe13 Mon Sep 17 00:00:00 2001
From: Vasilii Polikarpov
 <126792224+vpolikarpov-akvelon@users.noreply.github.com>
Date: Fri, 21 Jul 2023 13:54:40 +0200
Subject: [PATCH] Temporarily hardcode chromium revision (#7948)

---
 images/linux/scripts/installers/google-chrome.sh | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/images/linux/scripts/installers/google-chrome.sh b/images/linux/scripts/installers/google-chrome.sh
index cc011ba6c..ee1c6dfd8 100644
--- a/images/linux/scripts/installers/google-chrome.sh
+++ b/images/linux/scripts/installers/google-chrome.sh
@@ -14,6 +14,12 @@ function GetChromiumRevision {
     URL="https://omahaproxy.appspot.com/deps.json?version=${CHROME_VERSION}"
     REVISION=$(curl -s $URL | jq -r '.chromium_base_position')
 
+    # Temporarily hardcode revision as both requests
+    # for 115.0.5790.102 and 115.0.5790.98 return old incorrect revision
+    if [ $REVISION -eq "1583" ]; then
+       REVISION="1134878"
+    fi
+
     # Some Google Chrome versions are based on Chromium revisions for which a (usually very old) Chromium release with the same number exist. So far this has heppened with 4 digits long Chromium revisions (1060, 1086).
     # Use the previous Chromium release when this happens to avoid downloading and installing very old Chromium releases that would break image build because of incompatibilities.
     # First reported with: https://github.com/actions/runner-images/issues/5256