google-stackdriver-profiler: floating latest URL broke CI, and the dependency bot cannot update the entry

オープン
#1,521 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
go, java
領域
build-system

調査の方向性

Start with the three named entry points: libbuildpack.FindMatchingVersion and Manifest.DefaultVersion for resolving date versions, then tasks/update-buildpack-dependency/dependencies.rb in buildpacks-ci for version comparison. The issue identifies failures in each area but leaves the cross-repository design undecided. Done means agreeing on an approach that handles date versions through resolution and bot updates without breaking the Stackdriver binding.

索引モデルが issue の本文から書いたものです。

説明

Symptom

Concourse specs-switchblade-docker-cflinuxfs4 build 202 failed on one test,
Frameworks/APM_Agents/with_Google_Stackdriver_Profiler_service_binding/detects_and_installs_Google_Stackdriver_Profiler:

dependency sha256 mismatch: expected 509b87c4...7bde0c, actual bd443833...f835

The manifest entry points at the floating URL
https://storage.googleapis.com/cloud-profiler/java/latest/profiler_java_agent.tar.gz.
Google moved latest to a new release on 2026-10-27 without changing the URL.

  • Old pinned hash 509b87c4... is cloud-profiler-java-agent_20241028_RC00.tar.gz.
  • Current hash bd443833... is cloud-profiler-java-agent_20261026_RC00.tar.gz.

#1520 updates the hash. It fixes today's failure, but the same failure will come back on the next upload.

Root causes
  1. Floating URL. The entry uses .../java/latest/... with a pinned sha256, so it breaks whenever Google re-uploads.
  2. Bot skips the entry. The depwatcher already sees the dated releases (build-google-stackdriver-profiler-latest
    succeeded 2026-10-27). update-google-stackdriver-profiler-latest-java build 10 then logged
    SKIP: Built version is not required by buildpack.
    • The manifest entry was added by hand with version: 0.4.0.
    • latest? in buildpacks-ci tasks/update-buildpack-dependency/dependencies.rb compares a date version only against
      other date versions. 0.4.0 is not one, so a new YYYYMMDD_RCNN never counts as newer.
  3. Resolver cannot handle date versions. A probe against libbuildpack.FindMatchingVersion with manifest versions
    20241028_RC00 and 20261026_RC00 fails for every constraint (0.x, x, *, +, 20.x, the exact version),
    with Invalid Semantic Version or improper constraint.
    GoogleStackdriverProfilerFramework.Supply() calls Manifest.DefaultVersion(...), so if the bot ever wrote a date version,
    staging with a Stackdriver binding would fail.
Options
  1. Merge #1520 only. This is the minimum, and updates stay manual.
  2. Interim: use the versioned URI .../java/cloud-profiler-java-agent_20261026_RC00.tar.gz with the matching sha256.
    This stops the silent swap. 0.4.0 is only a made-up label (Google's agent uses date versions), so bump it to 0.5.0
    for this artifact and add a comment next to the entry with the real date version and URI. The 0.x default pin still
    resolves. Bump the minor on each manual update. Updates stay manual.
  3. Make the bot work: libbuildpack must resolve date versions, or the framework must bypass DefaultVersion.
    buildpacks-ci latest? must also treat a date version as newer than a semver-like one.
    This touches three repos, so it needs a design decision.
Proposal

Merge #1520 now, do option 2 as a follow-up PR, and use this issue to decide on option 3.

主要言語
Go
スター
455
フォーク
2.5k
平均マージ
22時間 9分
マージ済み PR(30日)
69

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

cloudfoundry/java-buildpack のほかの issue

cloudfoundry/java-buildpack の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。