We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
steps to reproduce
/some/non-existing/path
you will see like this in response
PANIC: runtime error: invalid memory address or nil pointer dereference goroutine 33 [running]: github.com/urfave/negroni/v3.(*Recovery).ServeHTTP.func1() /home/runner/go/pkg/mod/github.com/urfave/negroni/v3@v3.0.0/recovery.go:168 +0x140 panic({0x51c020, 0x9c3c10}) /opt/hostedtoolcache/go/1.20.8/x64/src/runtime/panic.go:884 +0x1f4 github.com/tidwall/buntdb.(*Tx).lock(0x400022a440?) /home/runner/go/pkg/mod/github.com/tidwall/buntdb@v1.3.0/buntdb.go:1140 +0x24
when you hit url second time, it will not crash but will create cache files in /app instead of creating cache path setted by user in prest.toml file
The text was updated successfully, but these errors were encountered:
@moinologics I've raised a PR for a potential solution, but could you also provide the full stack trace of the panic error?
Thanks
Sorry, something went wrong.
released in https://github.com/prest/prest/releases/tag/v1.4.2
Successfully merging a pull request may close this issue.
steps to reproduce
/some/non-existing/path
) in prest.tomlyou will see like this in response
when you hit url second time, it will not crash but will create cache files in /app instead of creating cache path setted by user in prest.toml file
The text was updated successfully, but these errors were encountered: