
Security News
RubyGems Adds Cooldown Feature to Bundler for Newly Published Gems
RubyGems and Bundler 4.0.13 introduced an opt-in cooldown feature that delays newly published gems during dependency resolution.
go.xsfx.dev/workgroups
Advanced tools
Package workgroups is a little helper for creating workers with the help of sync.Errgroup.

ErrInWorker is an error that gets returned if there is a error in the work function.
var ErrInWorker = errors.New("received error in worker")
type Dispatcher struct { ... }
Dispatcher carries the job queue, the errgroup and the number of workers to start.
func (d *Dispatcher) Append(job Job)
Append adds a job to the work queue.
func (d *Dispatcher) Close()
Close closes the queue channel.
func (d *Dispatcher) Start()
Start starts the configured number of workers and waits for jobs.
func (d *Dispatcher) Wait() error
Wait for all jobs to finnish.
type Job struct { ... }
Job carries a job with everything it needs. I know know that contexts shouldnt be stored in a struct. Here is an exception, because its a short living object. The context is only used as argument for the Work function. Please use the NewJob function to get around this context in struct shenanigans.
type Work func(ctx context.Context) error
Work is a type that defines worker work.
package main
import (
"context"
"fmt"
"github.com/go-logr/stdr"
"go.xsfx.dev/workgroups"
"log"
"os"
"runtime"
)
func main() {
d, ctx := workgroups.NewDispatcher(
context.Background(),
stdr.New(log.New(os.Stderr, "", log.Lshortfile)),
runtime.GOMAXPROCS(0), // This starts as much worker as maximal processes are allowed for go.
10, // Capacity of the queue.
)
work := func(ctx context.Context) error {
// Check if context already expired.
// Return if its the case, else just go forward.
select {
case <-ctx.Done():
return fmt.Errorf("got error from context: %w", ctx.Err())
default:
}
// Some wannebe work... printing something.
fmt.Print("hello world from work")
return nil
}
// Starting up the workers.
d.Start()
// Feeding the workers some work.
d.Append(workgroups.NewJob(ctx, work))
// Closing the channel for work.
d.Close()
// Waiting to finnish everything.
if err := d.Wait(); err != nil {
log.Fatal(err)
}
}
Output:
hello world from work
Retry is a middleware for doing a retry in executing job work.
package main
import (
"context"
"errors"
"fmt"
"github.com/go-logr/stdr"
"go.xsfx.dev/workgroups"
"log"
"os"
"runtime"
"time"
)
func main() {
d, ctx := workgroups.NewDispatcher(
context.Background(),
stdr.New(log.New(os.Stderr, "", log.Lshortfile)),
runtime.GOMAXPROCS(0), // This starts as much worker as maximal processes are allowed for go.
10, // Capacity of the queue.
)
// Just returning some error. So it can retry.
failFunc := func() error {
fmt.Print("fail ")
return errors.New("fail") //nolint:goerr113
}
work := func(ctx context.Context) error {
// Check if context already expired.
// Return if its the case, else just go forward.
select {
case <-ctx.Done():
return fmt.Errorf("got error from context: %w", ctx.Err())
default:
}
if err := failFunc(); err != nil {
return err
}
return nil
}
// Starting up the workers.
d.Start()
ctx, cancel := context.WithTimeout(ctx, time.Second)
defer cancel()
// Feeding the workers some work.
d.Append(
workgroups.NewJob(
ctx,
workgroups.Retry(ctx, time.Second/2)(work), // This will retry after a half second.
),
)
// Closing the channel for work.
d.Close()
// Waiting to finnish everything.
if err := d.Wait(); err != nil {
fmt.Print(err)
}
}
Output:
fail fail error on waiting: got error from context: context deadline exceeded
FAQs
Unknown package
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
RubyGems and Bundler 4.0.13 introduced an opt-in cooldown feature that delays newly published gems during dependency resolution.

Security News
pnpm 11.5 now recognizes npm staged publish approvals in release metadata, preventing those releases from being mistaken for lower-trust package publishes.

Security News
Federal audit finds NIST lacked a plan to clear the NVD backlog, wasted funds on duplicate work, and delayed use of CISA data.