You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pkg/workflows/wasm/host/module.go
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -682,7 +682,7 @@ func runWasm[I, O proto.Message](
682
682
1, // memories
683
683
)
684
684
685
-
deadline:=*m.cfg.Timeout/m.cfg.TickInterval
685
+
deadline:=maxTimeout/m.cfg.TickInterval
686
686
store.SetEpochDeadline(uint64(deadline))
687
687
688
688
h:=fnv.New64a()
@@ -744,7 +744,7 @@ func runWasm[I, O proto.Message](
744
744
// Note - there is no other reliable signal on the error that can be used to infer it is due to epoch deadline
745
745
// being reached, so if an error is returned after the deadline it is assumed it is due to that and return
746
746
// context.DeadlineExceeded.
747
-
iferr!=nil&& ((executionDuration>=*m.cfg.Timeout-m.cfg.TickInterval) ||ctx.Err() !=nil) { // As start could be called just before epoch update 1 tick interval is deducted to account for this
747
+
iferr!=nil&& ((executionDuration>=maxTimeout-m.cfg.TickInterval) ||ctx.Err() !=nil) { // As start could be called just before epoch update 1 tick interval is deducted to account for this
748
748
m.cfg.Logger.Errorw("start function returned error after deadline reached, returning deadline exceeded error", "errFromStartFunction", err)
0 commit comments