Skip to content
New issue

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

Nilpointer in server mode, regression in 0.42 #4845

Closed
bep opened this issue Jun 12, 2018 · 1 comment · Fixed by #4848
Closed

Nilpointer in server mode, regression in 0.42 #4845

bep opened this issue Jun 12, 2018 · 1 comment · Fixed by #4848

Comments

@bep
Copy link
Member

bep commented Jun 12, 2018

See https://discourse.gohugo.io/t/regression-in-hugo-server-hugo-0-42/12386/6

@bep bep added this to the 0.42.1 milestone Jun 12, 2018
@bep bep changed the title Nilpointer regression in 0.42 Nilpointer in server mode, regression in 0.42 Jun 12, 2018
bep added a commit to bep/hugo that referenced this issue Jun 13, 2018
In Hugo 0.42, this could lead to errors of type `runtime error: invalid memory address or nil pointer dereference` in some rare situations.

Note that this was also an issue before 0.42, but the symptom was then potentially stale list content on rebuilds on content changes.

This commit also improves the above error message.

Fixes gohugoio#4845
@bep bep closed this as completed in #4848 Jun 13, 2018
bep added a commit that referenced this issue Jun 13, 2018
In Hugo 0.42, this could lead to errors of type `runtime error: invalid memory address or nil pointer dereference` in some rare situations.

Note that this was also an issue before 0.42, but the symptom was then potentially stale list content on rebuilds on content changes.

This commit also improves the above error message.

Fixes #4845
@github-actions
Copy link

github-actions bot commented Mar 2, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant