v1.1.0 appears to be a breaking change

Open
#2 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go

Research direction

Start by inspecting the safe.Run API and compare its current callback signature with the call shown in packr.go at the linked location. Check how the v1.1.0 change affects callers that provide func() callbacks. Done means the reported transitive dependency call is compatible again, with coverage for the affected behavior if the repository provides tests.

Written by the indexing model from the issue text.

Description

We are seeing CI failures in some private repositories that pull in this repo as a transitive dependency (due to it being used in github.com/gobuffalo/packr). The issue appears to be that the safe.Run now requires a func() error instead of just func(). You can see how it's being called here - https://github.com/gobuffalo/packr/blob/master/packr.go#L14.

Dominant language
Go
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from markbates/safe

All issues in markbates/safe

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.