@krx3d/tizentube2 1.30.940 → 1.30.950
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -996,9 +996,25 @@ jobs:
|
|
|
996
996
|
# A wrong version inside the file is still an immediate failure: an
|
|
997
997
|
# immutable path cannot go stale, so that one cannot be transient.
|
|
998
998
|
# Only "not there yet" is retried.
|
|
999
|
+
# Ten attempts over three and a half minutes was not enough. The
|
|
1000
|
+
# release of 1.30.930 answered 404 or 502 on every one of them and
|
|
1001
|
+
# then caught up on its own shortly after, so the run failed over
|
|
1002
|
+
# jsDelivr's ingestion lag while the publish itself was fine.
|
|
1003
|
+
#
|
|
1004
|
+
# Twenty attempts over roughly ten minutes now, and then a warning
|
|
1005
|
+
# rather than a failure. The reasoning for not failing: npm has
|
|
1006
|
+
# already been confirmed earlier in this run by its own step, so a
|
|
1007
|
+
# pinned path that will not serve says something about jsDelivr's
|
|
1008
|
+
# queue and nothing about this repository. Failing here also takes
|
|
1009
|
+
# the .wgt release down with it, and injector.js now falls back to
|
|
1010
|
+
# the unversioned URL for exactly this window instead of injecting
|
|
1011
|
+
# the error page it used to.
|
|
1012
|
+
#
|
|
1013
|
+
# A wrong version inside a 200 is still a hard failure. An immutable
|
|
1014
|
+
# path cannot go stale, so that one is never a lag.
|
|
999
1015
|
echo "== the path every TV loads: ${PINNED}"
|
|
1000
1016
|
PINNED_OK=
|
|
1001
|
-
for i in $(seq 1
|
|
1017
|
+
for i in $(seq 1 20); do
|
|
1002
1018
|
CODE=$(curl -s -o /tmp/cdn_pinned.js -w '%{http_code}' -H 'Cache-Control: no-cache' "$PINNED" || echo 000)
|
|
1003
1019
|
if [ "$CODE" = "200" ]; then
|
|
1004
1020
|
if grep -aq "$VER" /tmp/cdn_pinned.js; then
|
|
@@ -1010,11 +1026,10 @@ jobs:
|
|
|
1010
1026
|
exit 1
|
|
1011
1027
|
fi
|
|
1012
1028
|
echo "attempt ${i}: HTTP ${CODE} — jsDelivr has not pulled this version from npm yet"
|
|
1013
|
-
sleep
|
|
1029
|
+
sleep 30
|
|
1014
1030
|
done
|
|
1015
1031
|
if [ -z "$PINNED_OK" ]; then
|
|
1016
|
-
echo "::
|
|
1017
|
-
exit 1
|
|
1032
|
+
echo "::warning::${PINNED} was still not readable after twenty attempts over ten minutes, last HTTP ${CODE}. npm has the version — the step before this confirmed it — so this is jsDelivr's ingestion queue rather than a bad publish, and it usually clears on its own within minutes. Until it does, injector.js falls back to the unversioned URL, which may be a release behind. Worth a look at https://www.jsdelivrstatus.com if it persists."
|
|
1018
1033
|
fi
|
|
1019
1034
|
|
|
1020
1035
|
# Then the alias, which is allowed to lag.
|