@pedropombeiro Yes, indeed. We don't need any sampling on this level 👍

Update to heroku/builder:24

Issue:

• #79
• https://gitlab.com/gitlab-com/Product/-/work_items/14424+

Mikhail Mazurskiy (d70adf6c) at 18 Mar 07:06

... and 1 more commit

I've left only one (very minor) comment. I don't know much about LangGraph, I mostly looked at the Temporal and Custom columns.

For completeness and transparency, there are other systems that we are considering: DBOS and River.

My thinking at the moment is that we'll likely need a custom implementation tailored to our requirements, with all the best parts of these systems.

Edit: we are doing research and discovery as part of AutoFlow (Durable Workflow Engine) - MVC (gitlab-org#21235) together with @timofurrer.

Mikhail Mazurskiy (b690862f) at 18 Mar 05:42

Mikhail Mazurskiy (77e27190) at 18 Mar 05:41

... and 1 more commit

The following discussion from !6508 should be addressed:

• @ajwalker started a discussion:

  @ash2k @avonbertoldi This has broken at least the Windows instance runners.

  instance.NewProvider(runnerCommand)

  Previously, I suspect the runner command here would have just been gitlab-runner, because it's up to the user to provide it in the remote environment's $PATH. The instance runner can target Windows and Linux environments from Windows or Linux, so hard-coding the path for the remote environment here, based on the runner manager, is an accidental breaking change (as confirmed by our pilot runners that deployed this today).

  Similarly, docker-windows and docker used to be separate, but a design several years ago made them entirely equal, and we made any OS differences (other than those in the abstract shell) be driven by inspecting the Docker daemon to determine the OS. The change here suggests that steps isn't enabled when docker-windows is used, which might break anybody running steps for Linux, but from a Windows-based runner manager.

  Commenting here because it means I can directly address the responsible code and in case this has been independently discovered and you're already working on it. If not, we should resolve this to an issue and fix 👍

What does this MR do?

It restores the behavior to what it was before the refactoring in !6508.

Why was this MR needed?

To fix the bug.

What's the best way to test this MR?

What are the relevant issue numbers?

Fixes #39329.

Cassandra was supported indeed, but it's no longer supported: https://docs.temporal.io/self-hosted-guide/visibility

At gitlab.com scale, PostgreSQL backend may not suffice — Cassandra recommended for full throughput.

Hm, I thought Temporal can scale horizontally across a huge number of PostgreSQL servers. I'm not sure this is accurate info in the table.

Mikhail Mazurskiy (57f1a368) at 18 Mar 02:48

Mikhail Mazurskiy (864b48d7) at 18 Mar 02:48

... and 1 more commit

This MR contains the following updates:

Package	Type	Update	Change
gitlab.com/gitlab-org/cluster-integration/tunnel	require	digest	84a8142 -> 1d54c34

---

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.

This MR contains the following updates:

Package	Type	Update	Change
gitlab.com/gitlab-org/cluster-integration/tunnel	require	digest	84a8142 -> 1d54c34

---

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.

What does this MR do?

It restores the behavior to what it was before the refactoring in !6508.

Why was this MR needed?

To fix the bug.

What's the best way to test this MR?

What are the relevant issue numbers?

Fixes #39329.

Mikhail Mazurskiy (b690862f) at 18 Mar 02:05

Mikhail Mazurskiy (9ac86527) at 18 Mar 01:20

Mikhail Mazurskiy (1d54c34a) at 18 Mar 01:20

... and 1 more commit

This MR contains the following updates:

Package	Type	Update	Change
google.golang.org/grpc	require	patch	v1.79.2 -> v1.79.3

---

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

---

Release Notes

grpc/grpc-go (google.golang.org/grpc)

v1.79.3: Release 1.79.3

Compare Source

Security

• server: fix an authorization bypass where malformed :path headers (missing the leading slash) could bypass path-based restricted "deny" rules in interceptors like grpc/authz. Any request with a non-canonical path is now immediately rejected with an Unimplemented error. (#​8981)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.