Documentation ¶
Overview ¶
Package services contain the key components of the Chainlink node. This includes the Application, JobRunner, LogListener, and Scheduler.
Application ¶
The Application is the main component used for starting and stopping the Chainlink node.
JobRunner ¶
The JobRunner keeps track of Runs within a Job and ensures that they're executed in order. Within each Run, the tasks are also executed from the JobRunner.
JobSubscriber ¶
The JobSubscriber coordinates running job events with the EventLog in the Store, and also subscribes to the given address on the Ethereum blockchain.
Scheduler ¶
The Scheduler ensures that recurring events are executed according to their schedule, and one-time events occur only when the specified time has passed.
Index ¶
Examples ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Checkable ¶ added in v1.2.0
type Checkable interface { // Ready should return nil if ready, or an error message otherwise. Ready() error // Healthy should return nil if healthy, or an error message otherwise. Healthy() error }
Checkable should be implemented by any type requiring health checks. From the k8s docs: > ready means it’s initialized and healthy means that it can accept traffic in kubernetes See: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
type Checker ¶ added in v1.2.0
type Checker interface { // Register a service for health checks. Register(name string, service Checkable) error // Unregister a service. Unregister(name string) error // IsReady returns the current readiness of the system. // A system is considered ready if all checks are passing (no errors) IsReady() (ready bool, errors map[string]error) // IsHealthy returns the current health of the system. // A system is considered healthy if all checks are passing (no errors) IsHealthy() (healthy bool, errors map[string]error) Start() error Close() error }
Checker provides a service which can be probed for system health.
func NewChecker ¶ added in v1.2.0
func NewChecker() Checker
type Config ¶ added in v1.2.0
type Config interface { AutoPprofProfileRoot() string AutoPprofPollInterval() models.Duration AutoPprofGatherDuration() models.Duration AutoPprofGatherTraceDuration() models.Duration AutoPprofMaxProfileSize() utils.FileSize AutoPprofCPUProfileRate() int AutoPprofMemProfileRate() int AutoPprofBlockProfileRate() int AutoPprofMutexProfileFraction() int AutoPprofMemThreshold() utils.FileSize AutoPprofGoroutineThreshold() int }
type MultiClose ¶ added in v1.10.0
MultiClose is a utility for closing multiple services concurrently.
Example ¶
ctx := context.Background() f1 := CloseFailure("f") f2 := CloseFailure("f") var ms MultiStart if err := ms.Start(ctx, f1, f2); err != nil { fmt.Println(err) return } mc := MultiClose{f1, f2} if err := mc.Close(); err != nil { fmt.Println(err) }
Output: f started f started f close failure f close failure failed to close: f; failed to close: f
func (MultiClose) Close ¶ added in v1.10.0
func (m MultiClose) Close() (err error)
Close closes alls service concurrently and collects any returned errors as a multierr.
type MultiStart ¶ added in v1.9.0
type MultiStart struct {
// contains filtered or unexported fields
}
MultiStart is a utility for starting multiple services together. The set of started services is tracked internally, so that they can be closed if any single service fails to start.
Example ¶
ctx := context.Background() a := Healthy("a") b := CloseFailure("b") c := WontStart("c") var ms MultiStart if err := ms.Start(ctx, a, b, c); err != nil { fmt.Println(err) }
Output: a started b started c start failure b close failure a closed failed to start: c; failed to close: b
func (*MultiStart) Close ¶ added in v1.9.0
func (m *MultiStart) Close() (err error)
Close closes all started services, in reverse order.
func (*MultiStart) CloseBecause ¶ added in v1.11.0
func (m *MultiStart) CloseBecause(reason error) (err error)
CloseBecause calls Close and returns reason along with any additional errors.
func (*MultiStart) Start ¶ added in v1.9.0
func (m *MultiStart) Start(ctx context.Context, srvcs ...StartClose) (err error)
Start attempts to Start all services. If any service fails to start, the previously started services will be Closed, and an error returned.
type Nurse ¶ added in v1.2.0
type Nurse struct { utils.StartStopOnce // contains filtered or unexported fields }
func (*Nurse) GatherVitals ¶ added in v1.2.0
type ServiceCtx ¶ added in v1.3.0
type ServiceCtx interface { // Start the service. Must quit immediately if the context is cancelled. // The given context applies to Start function only and must not be retained. Start(context.Context) error // Close stops the Service. // Invariants: Usually after this call the Service cannot be started // again, you need to build a new Service to do so. Close() error Checkable }
ServiceCtx represents a long-running service inside the Application.
Typically, a ServiceCtx will leverage utils.StartStopOnce to implement these calls in a safe manner.
Template ¶
Mockable Foo service with a run loop
//go:generate mockery --quiet --name Foo --output ../internal/mocks/ --case=underscore type ( // Expose a public interface so we can mock the service. Foo interface { service.ServiceCtx // ... } foo struct { // ... stop chan struct{} done chan struct{} utils.StartStopOnce } ) var _ Foo = (*foo)(nil) func NewFoo() Foo { f := &foo{ // ... } return f } func (f *foo) Start(ctx context.Context) error { return f.StartOnce("Foo", func() error { go f.run() return nil }) } func (f *foo) Close() error { return f.StopOnce("Foo", func() error { // trigger goroutine cleanup close(f.stop) // wait for cleanup to complete <-f.done return nil }) } func (f *foo) run() { // signal cleanup completion defer close(f.done) for { select { // ... case <-f.stop: // stop the routine return } } }
type StartClose ¶ added in v1.9.0
StartClose is a subset of the ServiceCtx interface.
Directories ¶
Path | Synopsis |
---|---|
signatures
|
|
cryptotest
Package cryptotest provides convenience functions for kyber-based APIs.
|
Package cryptotest provides convenience functions for kyber-based APIs. |
ethdss
Package ethdss implements the Distributed Schnorr Signature protocol from the //////////////////////////////////////////////////////////////////////////////
|
Package ethdss implements the Distributed Schnorr Signature protocol from the ////////////////////////////////////////////////////////////////////////////// |
ethschnorr
Package ethschnorr implements a version of the Schnorr signature which is //////////////////////////////////////////////////////////////////////////////
|
Package ethschnorr implements a version of the Schnorr signature which is ////////////////////////////////////////////////////////////////////////////// |
secp256k1
Package secp256k1 is an implementation of the kyber.{Group,Point,Scalar} //////////////////////////////////////////////////////////////////////////////
|
Package secp256k1 is an implementation of the kyber.{Group,Point,Scalar} ////////////////////////////////////////////////////////////////////////////// |