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.
I had a few head-scratching moments about this one this weekend. After some thinking, I decided to close/remove #7437 from the mix and introduce a new (marked as internal for now)
Resource.NameOriginal
method that's used as a fall back in.Resources.Get
. We still normalize the resource name by removing any language code (so you can use the same name across languages), but:.Destination
All of this is reflected in my new test:
Also, thanks for the other bug reports, I will look at them shortly.