Invalid memory address or nil pointer dereference on Windows #3
Comments
|
same here, moved to ubuntu on WSL it doesn't work either |
|
@AnimMouse Sorry for the delay responding. Somehow I was unsubscribed from issue notifications. Does the problem still occur on the latest version? The problem seems to be here: It looks like resources.GetMatch had a problem with the input of What was your config value for |
|
I am seeing the same problem. The problem is showing on a raw, clean base new site created with your template, with no modifications. |
|
Oh, and to answer your direct question, the only reference I could find to |
|
@Dekker500 Thanks for the info. Unfortunately, I don't have a Windows computer with WSL set up, so I can't repro the issue directly. If I can know what the input to resources.GetMatch is, I might be able to figure out the issue anyway. I asked for the value of Also, I can tell from |
|
@luisimasd @AnimMouse Can either of you report the site/page config you used? See my post above. I can't debug without knowing this. |
|
I won't be able to test until the 20th, however the site config was the one you provided. The course shown above is the exact sequence I followed in a brand new folder. Will report after the 20th... Sorry! |
We haven't edited any configuration, I basically run Hugo on your exampleSite folder on Windows.
Since I saw you use GitHub Actions for CI/CD, you can use GitHub Actions' Windows runners by using The logs below are created on GitHub Actions Windows runners for clean reproducible environment. Logs as of be57840: Hugo extended: |
|
I've experienced this same error but haven't had time to work out how to get a log file or more detailed debug information about it. As above, I've experienced it on a new/clean site, using the exampleSite config. I think it comes from this line, but that's as far as I've got; Happy to help in any way I can. |
|
@rogerssam Were you using Windows too? |
Yes I am. Win10 pro. Happy to run anything to help debug :) |
|
After some debugging, I might have a fix. The error still happens on a GitHub runner running Windows Server, but it doesn't happen on a PC running Windows 11. Would someone please test v0.39.0 and report back? |
I can confirm this works for me with a blank site using the default exampleSite config and content. Thanks! |
|
Thanks, @rogerssam! @AnimMouse @luisimasd @Dekker500 Does it work for you? |
|
Tried running on Windows 11 and Windows 10, still errors, but different message. Windows 11 logs as of 0f6f3ba: Hugo extended: |
|
@AnimMouse Thanks for your report.
In the latest version, the setup instructions have changed:
This is the current version:
The run instructions have also changed:
This is the current version: $ cd yourproject
$ hugo mod npm pack
$ npm install
$ hugo server -DNote that the current version is v0.41.2 as of this writing. Would you please try running |
|
This is the first time I have encountered a Hugo theme that requires P.S. I agree with this, instead of |
@AnimMouse Thank you for your report!
I thought it would be good to keep deps out of the repo to make it smaller. It's already too large, in my opinion. I'm going to try to slim it down in the future. Fortunately, Hugo supports this.
How are you deploying to Cloudflare Pages? Are you using https://github.com/cloudflare/pages-action in a GitHub workflow? If so, the doc there says you can put your own build actions in the middle: on: [push]
jobs:
publish:
runs-on: ubuntu-latest
permissions:
contents: read
deployments: write
name: Publish to Cloudflare Pages
steps:
- name: Checkout
uses: actions/checkout@v3
# Run a build step here if your project requires
- name: Publish to Cloudflare Pages
uses: cloudflare/pages-action@v1
with:
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
accountId: YOUR_ACCOUNT_ID
projectName: YOUR_PROJECT_NAME
directory: YOUR_ASSET_DIRECTORY
# Optional: Enable this if you want to have GitHub Deployments triggered
gitHubToken: ${{ secrets.GITHUB_TOKEN }}You can put - name: Build
run: |
npm build
hugo build # ...flagsAll the GitHub runners have npm installed. See the changes to
My pleasure. |
I wasn't thrilled with the name, either, but I couldn't think of a better one. Suggestions are welcome. |
I personally use |
|
@rogerssam Take a look at the current menu of the exampleSite. "Content" is the name of a section that shows how standard content is displayed in the theme. It's adjacent to other sections that show off the theme's shortcodes ("Shortcodes"), layouts ("Layouts"), and so on. There's no single "posts" or "blog" section that can correspond to the "content" section in this context. Some alternative section names that seemed worse than "Content" to me:
I couldn't think of anything better. 🤷♂️ |
|
Yeah fair comment, I see what you mean. You could call the section name "List-style content"? I realise it's long (not ideal), but perhaps clearer what it's demoing? Or maybe even just "Lists" or "Articles"? I would still suggest that "Posts" would give that information to new users because I figure most people are going to want to use that section for blog-style content, so making it clear that's where/how it will display is probably useful. You could also change this line to something like "Demonstrations of Paige list-style content (suitable for blogs, articles etc)". At the end of the day it probably doesn't matter too much :) Thanks for your work with this theme - it's very impressive! |
The other sections also have lists of links to pages in those sections, so it would be confusing for only one of them to be called that. That name also wouldn't describe what kind of pages are in that section. Hence, the current situation. :) Thanks for your suggestions. |
I'm currently using Cloudflare Pages' own builder, so that I don't unnecessarily use my GitHub Actions runner minutes, but since there is no way to do |
When trying to build exampleSite on Windows, it errors, but in Ubuntu, it is working.
The text was updated successfully, but these errors were encountered: