go-stack/stack
### [`v1.8.0`](https://togithub.com/go-stack/stack/releases/v1.8.0)
[Compare Source](https://togithub.com/go-stack/stack/compare/v1.7.0...v1.8.0)
In addition to adding a go.mod file, this release also updates the implementation of the `%+s` and `%+v` formats to provide semantically equivalent behavior when compiled in either a GOPATH or module based project. All existing tests still pass in both modes. Several cases of using this package in a module aware main program and with stacks that include modules >= v2.0.0 have been manually tested to ensure the results are useful in those cases.
There is one subtle difference in the behavior when using modules. That is, stack frames originating in vendored packages built with the `-mod=vendor` flag will report their import path as seen in the source code rather than a path in the vendor folder of the main project. Some may consider this an improvement—having paths that match the import path used in the source seems more natural—but opinions may differ here. Also note that the `%#s` and `%#v` formats still produce unmodified full paths to the compile time source locations as always.
### [`v1.7.0`](https://togithub.com/go-stack/stack/releases/v1.7.0)
[Compare Source](https://togithub.com/go-stack/stack/compare/v1.6.0...v1.7.0)
This release updates the implementation to use [`runtime.CallersFrames`](https://golang.org/pkg/runtime/#CallersFrames) to examine stack frame data. CallersFrames was added in Go 1.7, so this package no longer supports versions of Go prior to 1.7. If you need to use Go 1.6 or earlier, you should pin this package to v1.6.0.
Go 1.9 [changed the way stack data is returned from `runtime.Callers`](https://golang.org/doc/go1.9#callersframes). The good news is that we can now see stack information for inlined functions. The bad news is that inspecting stack data is generally [slower and requires more memory](https://togithub.com/go-stack/stack/pull/19#issue-257935796) than before.
### [`v1.6.0`](https://togithub.com/go-stack/stack/releases/v1.6.0)
[Compare Source](https://togithub.com/go-stack/stack/compare/v1.5.4...v1.6.0)
This release adds the `%k` formatting verb to output the package name for the function or method of `stack.Call`. The unadorned verb outputs only the last segment of the package import path, while the `%+k` variety produces the full import path of the package.
Note that `%k` was chosen in part because one of this package's forks () had chosen it for the same purpose. `%p` was considered, but the `fmt` package already uses that for formatting pointer values, and we wanted to avoid potential confusion with that use case.
### [`v1.5.4`](https://togithub.com/go-stack/stack/releases/v1.5.4)
[Compare Source](https://togithub.com/go-stack/stack/compare/v1.5.3...v1.5.4)
This release should fix several recent reports that some environments don't handle the intentional `nil` pointer dereference used by this package to cache the address of `runtime.sigpanic`. Caching the address of `runtime.sigpanic` was a performance optimization, so `stack.Trace` is slower in this release as shown by the benchmarks posted here: [#12 (comment)](https://togithub.com/go-stack/stack/pull/12#issuecomment-307648686).
But correctness takes priority over speed, so this release addresses correctness in the simplest way possible. A future release may be able to regain some of the lost performance.
An incomplete list of Issues in other projects that this release is intended to resolve:
- [derekparker/delve#852](https://togithub.com/derekparker/delve/issues/852)
- [go-kit/kit#555](https://togithub.com/go-kit/kit/issues/555)
- [ethereum/go-ethereum#14777](https://togithub.com/ethereum/go-ethereum/issues/14777)
- [inconshreveable/ngrok#364](https://togithub.com/inconshreveable/ngrok/issues/364)
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot. View repository job log here.
This PR contains the following updates:
v1.5.3->v1.8.0Release Notes
go-stack/stack
### [`v1.8.0`](https://togithub.com/go-stack/stack/releases/v1.8.0) [Compare Source](https://togithub.com/go-stack/stack/compare/v1.7.0...v1.8.0) In addition to adding a go.mod file, this release also updates the implementation of the `%+s` and `%+v` formats to provide semantically equivalent behavior when compiled in either a GOPATH or module based project. All existing tests still pass in both modes. Several cases of using this package in a module aware main program and with stacks that include modules >= v2.0.0 have been manually tested to ensure the results are useful in those cases. There is one subtle difference in the behavior when using modules. That is, stack frames originating in vendored packages built with the `-mod=vendor` flag will report their import path as seen in the source code rather than a path in the vendor folder of the main project. Some may consider this an improvement—having paths that match the import path used in the source seems more natural—but opinions may differ here. Also note that the `%#s` and `%#v` formats still produce unmodified full paths to the compile time source locations as always. ### [`v1.7.0`](https://togithub.com/go-stack/stack/releases/v1.7.0) [Compare Source](https://togithub.com/go-stack/stack/compare/v1.6.0...v1.7.0) This release updates the implementation to use [`runtime.CallersFrames`](https://golang.org/pkg/runtime/#CallersFrames) to examine stack frame data. CallersFrames was added in Go 1.7, so this package no longer supports versions of Go prior to 1.7. If you need to use Go 1.6 or earlier, you should pin this package to v1.6.0. Go 1.9 [changed the way stack data is returned from `runtime.Callers`](https://golang.org/doc/go1.9#callersframes). The good news is that we can now see stack information for inlined functions. The bad news is that inspecting stack data is generally [slower and requires more memory](https://togithub.com/go-stack/stack/pull/19#issue-257935796) than before. ### [`v1.6.0`](https://togithub.com/go-stack/stack/releases/v1.6.0) [Compare Source](https://togithub.com/go-stack/stack/compare/v1.5.4...v1.6.0) This release adds the `%k` formatting verb to output the package name for the function or method of `stack.Call`. The unadorned verb outputs only the last segment of the package import path, while the `%+k` variety produces the full import path of the package. Note that `%k` was chosen in part because one of this package's forks (Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.