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
// MessageReceived provides runtime orchestration to pass the envelope / context to configured pipeline(s) along with a response callback to execute on each completion.
lc.Errorf("failed to process output for message '%s' on pipeline %s: %s", ctx.CorrelationID(), p.Id, outputErr.Error())
errCollector(outputErr)
return
}
}
lc.Debugf("trigger successfully processed message '%s' in pipeline %s", p.Id, envelope.CorrelationID)
}
}(pipeline, &pipelinesWaitGroup, func(eerror) {
errorCollectionLock.Lock()
defererrorCollectionLock.Unlock()
finalErr=multierror.Append(finalErr, e)
})
}
pipelinesWaitGroup.Wait()
returnfinalErr
}
In the method MssageReceived within the triggerMessageProcessor implementation, if no pipelines are found for the received topic, it would be more efficient to return early to avoid unnecessary allocations, message decoding, and WaitGroup usage.
The text was updated successfully, but these errors were encountered:
app-functions-sdk-go/internal/app/triggermessageprocessor.go
Lines 102 to 176 in 0835601
In the method
MssageReceived
within thetriggerMessageProcessor
implementation, if no pipelines are found for the received topic, it would be more efficient to return early to avoid unnecessary allocations, message decoding, and WaitGroup usage.The text was updated successfully, but these errors were encountered: