William Storey
William Storey
This is to address #50. I realize it is a bit strict. But I think it makes sense when releasing to be strict about information being available.
This is as discussed in #56. Note it changes the default behaviour to fail if we get a 404 when making API requests. Personally I don't know why you'd want...
This is related to discussion in #56.
I use these plugins as part of a bundle, and I found at least `GitHub::Update` checks for some information it needs only after the release, and then errors if it...
This was with version 0.46 as well. The same release as in #55. In the build step I see this: ``` [@MAXMIND/GitHub::Meta] Getting GitHub repository info [@MAXMIND/GitHub::Meta] Err: Not Found...
Hi! I have a use case where I need a stable JSON representation of a struct that contains a `map[string]string` as one of its fields. I found that when I...
Hi agai!. Sorry to be opening so many issues :-P. I came across another interesting behaviour difference compared to `golang.org/x/sync/errgroup`: It's possible for functions given to `Go()` to never be...
Hi! I'm using 0.1.5 with Go 1.16.3. First, thank you for making the package! It's a great idea! As to the issue: I've encountered what I believe is a deadlock...
Hi again! Another use of this package brought to mind a possible improvement: Checking whether the context is cancelled in `Go()`. This isn't something `golang.org/x/sync` does, but given this package's...
Previously if we encountered a file we could not read for permission reasons, we'd exit immediately. This meant that you either had to stop and fix the permissions or tell...