Skip to content

chore: bump duty to v1.0.327 #732

chore: bump duty to v1.0.327

chore: bump duty to v1.0.327 #732

Triggered via pull request January 2, 2024 10:23
Status Failure
Total duration 3m 54s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
lint: jobs/cleanup.go#L1
: # github.com/flanksource/config-db/jobs
lint: jobs/sync_upstream.go#L36
assignment mismatch: 1 variable but reconciler.SyncAfter returns 2 values
lint: jobs/sync_upstream.go#L102
cannot use scrapeConfigs[len(scrapeConfigs) - 1].UpdatedAt (variable of type *"time".Time) as "time".Time value in assignment
lint: jobs/sync_upstream.go#L113
undefined: upstream.NewPushQueueConsumer
lint: jobs/sync_upstream.go#L119
cannot use ctx (variable of type "github.com/flanksource/config-db/api".ScrapeContext) as postq.Context value in argument to pg.Listen: "github.com/flanksource/config-db/api".ScrapeContext does not implement postq.Context (missing method Debugf) (typecheck)
lint: cmd/root.go#L11
could not import github.com/flanksource/config-db/jobs (-: # github.com/flanksource/config-db/jobs
lint: jobs/sync_upstream.go#L36
assignment mismatch: 1 variable but reconciler.SyncAfter returns 2 values
lint: jobs/sync_upstream.go#L102
cannot use scrapeConfigs[len(scrapeConfigs) - 1].UpdatedAt (variable of type *"time".Time) as "time".Time value in assignment
lint: jobs/sync_upstream.go#L113
undefined: upstream.NewPushQueueConsumer
lint: jobs/sync_upstream.go#L119
cannot use ctx (variable of type "github.com/flanksource/config-db/api".ScrapeContext) as postq.Context value in argument to pg.Listen: "github.com/flanksource/config-db/api".ScrapeContext does not implement postq.Context (missing method Debugf)) (typecheck)
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@ee0669bd1cc54295c223e0bb666b733df41de1c5, actions/setup-go@bfdd3570ce990073878bf10f6b2d79082de49492. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/