With v0.121.2:
| EN
-------------------+-----
Pages | 8
Paginator pages | 0
Non-page files | 0
Static files | 1
Processed images | 0
Aliases | 0
Sitemaps | 1
Cleaned | 0
With PR #11830:
| EN
-------------------+-----
Pages | 10
Paginator pages | 0
Non-page files | 0
Static files | 0
Processed images | 0
Aliases | 0
Cleaned | 0
On a few occassions I was not able to kill the server with Ctrl+C on the first try, and after several times it stopped with this message:
Error: context deadline exceeded
I've a resources.GetRemote call that's currently returning a bad request (400) error, and at the moment that is expected (the provider site is having issues). I expected the hugo server to terminate after throwing the error, but I have to Ctrl+C to stop the server. With v0.121.2 the server terminates immediately. This is an intermittent problem, and I have not been able to create a mimimal failing example yet.
OK, this one I don't understand and I have read your comment twice. I have pushed a test that matches my world view on this, and I have included both below. The first is from your first issue reported on this (which was an obvious bug), the second is my added test for your latest case:
My take on this is that:
s1/p1/index.md
ands1/p2.md
both are logicallly on the same level.p1
should be the relative path to p1 from both of them.../p2
you go one level up and arrive in thes1
section.../p2
from p1 should give p2 on the same level, then the first test needs to be adjusted accordingly.EDIT: But you're right, this behaves differently in the master branch, which puzzles me a little. I don't think we had existing tests for this. To me this is a bug fix, but I need to think a little.
Also, I have pushed a fix for the tags panic: c73cb3db7932b44eacb069124b4868b29b73f2ef