Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Releases: maruel/panicparse

v2.4.0

29 Nov 00:33
@maruel maruel

Choose a tag to compare

I had forgotten to make a release. Creating one as this removes support for older pre go1.17 versions. The next release will likely require go1.22.

What's Changed

New Contributors

Full Changelog: v2.3.1...v2.4.0

Contributors

AlekSi and nikolaydubina
Assets 2
Loading

go1.19 test fixes

29 Aug 13:47
@maruel maruel

Choose a tag to compare

Full Changelog: v2.3.0...v2.3.1

Various changes to make it compatible with go1.19.

The only functional change is to add a timeout to panicweb to prevent a DoS.

Loading

Internal improvements; drop <go1.13

21 Jun 20:19
@maruel maruel

Choose a tag to compare

  • Rewrote the github actions. Enforce much more strict lints, including gosec.
  • Bumped minimal support to go1.13 and removed support code for older code.
  • Skip change detector test cases that were broken on 386, arm, arm64, mipsle, mips64le, ppc64le, riscv64 and s390x. Thanks @anthonyfok!

Full Changelog: v2.2.2...v2.3.0

Contributors

anthonyfok
Loading
svengreb and anthonyfok reacted with thumbs up emoji
2 people reacted

Fix import from bazel

13 May 13:22
@maruel maruel
95bad65
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

What's Changed

  • Avoid unicode filename by @tbg in #78

New Contributors

  • @tbg made their first contribution in #78

Full Changelog: v2.2.1...v2.2.2

Contributors

tbg
Loading

go1.17 / go1.18 full support

09 Apr 21:37
@maruel maruel

Choose a tag to compare

What's Changed

  • README.md: add hint for sh aliasing (pp naming conflict) by @jtagcat in #72
  • stack: add support for 1.17 stack traces by @MordFustang21 in #74

New Contributors

Full Changelog: v2.2.0...v2.2.1

Contributors

MordFustang21 and jtagcat
Loading
MordFustang21 and svengreb reacted with heart emoji
2 people reacted

go1.17 support

19 Oct 17:54
@maruel maruel

Choose a tag to compare

Stack traces from go1.17 runtime are now supported!

What's Changed

New Contributors

Full Changelog: v2.1.1...v2.2.0

Contributors

dallbee and nvb
Loading

Backported v2

19 Dec 20:49
@maruel maruel

Choose a tag to compare

Remove the nudge to upgrade to v2, copied the necessary code back to v1, and it leverages stack@v2.1.0.

Loading

Nudge to ugprade to v2

24 Aug 00:09
@maruel maruel

Choose a tag to compare

If you are reading this, you have three choices:

  • Upgrade to v2. Seriously, do this. It's so much better!
  • Disable the nudge with the environment variable PANICPARSE_V1_NO_WARN=1
  • Stick to v1.5.0.
Loading

Official v2.0.1 release

10 Aug 22:35
@maruel maruel

Choose a tag to compare

Loading

Initial v2 release

31 May 23:45
@maruel maruel

Choose a tag to compare

Initial v2 release Pre-release
Pre-release
  • Enabled race detector parsing!
  • Significantly accelerated performance for pass through.
  • Significant refactoring of the package stack.
  • Removed vendor/ since it's not used anymore by current Go versions. As such, the minimum required version is now 1.9.x.
  • Includes recent v1.5.0 go module support.
Loading
Previous 1 3
Previous

AltStyle によって変換されたページ (->オリジナル) /