Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
special test for eric
Here is a summary of the changes I made to add the
concurrencyKey
to the runctx
:Schema Update: I started by updating the
TaskRun
schema located inpackages/core/src/v3/schemas/common.ts
. I added an optionalconcurrencyKey
field to this schema, which ensures that our type definitions across the system are aware of this new property.Context Creation: I then located the code responsible for creating the
TaskRunContext
that gets passed to each task'srun
function. This was in theresolveTaskRunContext
method within theRunAttemptSystem
atinternal-packages/run-engine/src/engine/systems/runAttemptSystem.ts
.Data Fetching: Inside this method, I updated the database query to select the
concurrencyKey
field from theTaskRun
record.Context Population: Finally, I added the retrieved
concurrencyKey
to therun
object within theTaskRunContext
, making it available asctx.run.concurrencyKey
inside the task execution environment.In short, I ensured the
concurrencyKey
is fetched from the database and correctly placed into the task's context object, making it accessible during runtime as requested.