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.

Sign up for GitHub

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

Jump to bottom

Duplicate target paths warning after upgrade to v0.115.0 #11187

Closed
xeptore opened this issue Jun 30, 2023 · 3 comments · Fixed by #11188
Closed

Duplicate target paths warning after upgrade to v0.115.0 #11187

xeptore opened this issue Jun 30, 2023 · 3 comments · Fixed by #11188
Assignees
@bep
Labels
Bug Outdated
Milestone
v0.115.1

Comments

@xeptore
Copy link

xeptore commented Jun 30, 2023

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.115.0+extended linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?

Yes

After upgrading from v0.114.1 to the latest version, I receive duplicate path warning for every content file every time I change, and save a file.

Steps to reproduce:

  1. Clone/download the repo xeptore/blog 
    curl -sSfL https://github.com/xeptore/blog/archive/main.tar.gz | tar -xzvf -
  2. Install dependencies using pnpm (pnpm install)
  3. Start server: make run
  4. Edit, and save a random content file, e.g., layouts/404.html

If you follow the above steps having hugo version 0.114.1, no path warnings will be printed in the terminal. But, if you upgrade the hugo version to v0.115.0, and try step 4, a duplicate target path warning will be printed similar to the following:

WARN  Duplicate target paths: /404.html (2), /about/index.html (2), /contact/index.html (2), /emoji-support-demo/index.html (2), /index.html (2), /index.xml (2), /markdown-syntax-guide/index.html (2), /math-typesetting-demo/index.html (2), /my-first-post-with-slug/index.html (2), /rich-content-demo/index.html (2), /sitemap.xml (2), /tags/demo/index.html (2), /tags/demo/index.xml (2), /tags/development/index.html (2), /tags/development/index.xml (2), /tags/emoji/index.html (2), /tags/emoji/index.xml (2), /tags/first/index.html (2), /tags/first/index.xml (2), /tags/hello/index.html (2), /tags/hello/index.xml (2), /tags/markdown/index.html (2), /tags/markdown/index.xml (2), /tags/privacy/index.html (2), /tags/privacy/index.xml (2), /tags/shortcodes/index.html (2), /tags/shortcodes/index.xml (2), pages/1/index.html (2), robots.txt (2), tags/demo/pages/1/index.html (2), tags/development/pages/1/index.html (2), tags/emoji/pages/1/index.html (2), tags/first/pages/1/index.html (2), tags/hello/pages/1/index.html (2), tags/markdown/pages/1/index.html (2), tags/privacy/pages/1/index.html (2), tags/shortcodes/pages/1/index.html (2)
@bep bep removed the NeedsTriage label Jun 30, 2023
@bep bep self-assigned this Jun 30, 2023
@bep
Copy link
Member

bep commented Jun 30, 2023

This is a side effect of the fix for fa0e16f

We will fix this, but to me it does not make sense to have this enabled when running the server, so I suggest you at least temporarily turn it off in your server setup (or config) and just do hugo --printPathWarnings when you need to do these checks.

@bep bep added this to the v0.115.0 milestone Jun 30, 2023
@bep bep mentioned this issue Jun 30, 2023
Merged
bep added a commit to bep/hugo that referenced this issue Jun 30, 2023
@bep
Only print the path warnings once
fcf9984 
We could reset and rerun it on server rebuilds, but that report needs a full build to make sense.

Also clean up the config vs flags in this area: Make all config settings match the flags e.g. `printPathWarnings`, but set up aliases for the
old.

Fixes gohugoio#11187
bep added a commit that referenced this issue Jun 30, 2023
@bep
Only print the path warnings once
ffd37d4 
We could reset and rerun it on server rebuilds, but that report needs a full build to make sense.

Also clean up the config vs flags in this area: Make all config settings match the flags e.g. `printPathWarnings`, but set up aliases for the
old.

Fixes #11187
@bep bep modified the milestones: v0.115.0, v0.115.1 Jun 30, 2023
@xeptore
Copy link
Author

xeptore commented Jul 1, 2023

@bep, #11188 fixed this issue as I installed master version, and it no warnings were printed even in server mode.

Thanks for the effort and being quick to respond!

@github-actions
Copy link

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 Jul 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bep bep

Labels
Bug Outdated
Projects
None yet
Milestone
v0.115.1
Development

Successfully merging a pull request may close this issue.

Only print the path warnings once bep/hugo
2 participants
@bep @xeptore