-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: refresh timeout #495
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tenant := ctx.Value("tenant").(*dbsqlc.Tenant) | ||
tenantId := sqlchelpers.UUIDToStr(tenant.ID) | ||
|
||
stepRun, err := d.repo.StepRun().RefreshTimeoutAt(ctx, tenantId, request.StepRunId, request.IncrementTimeoutBy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abelanger5 is there a convenient way to validate the IncrementTimeoutBy string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use the duration
validator within RefreshTimeoutAt
in an opts
struct.
tenant := ctx.Value("tenant").(*dbsqlc.Tenant) | ||
tenantId := sqlchelpers.UUIDToStr(tenant.ID) | ||
|
||
stepRun, err := d.repo.StepRun().RefreshTimeoutAt(ctx, tenantId, request.StepRunId, request.IncrementTimeoutBy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use the duration
validator within RefreshTimeoutAt
in an opts
struct.
Description
Timeouts have been fixed intervals which does not afford flexibility during execution. Adds support to increase the timeout during step runtime.
Fixes HAT-121
Type of change
What's Changed