Anatole: Page after deployment to GitHub Pages didn't load custom css

[PiotrWachulec]

After updating to v0.2 I'm getting the message when I deploy my page to GitHub Pages, I'm getting an error related to custom css:

Failed to find a valid digest in the 'integrity' attribute for resource 'https://devdiary.wachulec.me/css/newsletter-form.41ab8feeeba31fe76d273b3cf27a31ff6acd2203b4c18108390653b995d72a80.css' with computed SHA-256 integrity 'GeWA05DEnpmOAEbv24B8taIzq+jKlpCHi6kvlUlFoqQ='. The resource has been blocked.

Used Hugo version: v0.74.3/extended. All necessary files are added in config file.

[lxndrblz]

@PiotrWachulec Thanks for reporting this issue. I had a look at your website and was able to see it in the dev console.

It looks like the Hash values for the integrity checks are not computed correctly. Can you check if you get the same error locally too? Do you see any error?

[PiotrWachulec]

@lxndrblz Yeah, I checked and locally all looks good. Styles are loaded. But when I push my page to GH Pages, there is an error.

[lxndrblz]

Do you see any error in the GitHub pages log? Unfortunately, I couldn't reproduce your error, so I assume it's not a general problem. Maybe a rebuild of your site could fix it?

[PiotrWachulec]

Where can I find such logs?

I deployed page before the theme upgrade to v0.2 and exactly with the update and then styles are broken.

See what was upgraded:

[lxndrblz]

That looks highly suspicious. It might have to do with the changes in head.html. However, I can't wrap my head around why this change should have such an effect.

With logs I meat the ones of GitHub pages. If everything has been successful during the page built. Would you mind trying a rebuild?

In case that doesn't help I'll have to investigate this issue using shotgun Pages myself.

[PiotrWachulec]

Yup, I built the page again many times, when I added new articles. I'm building it with Azure DevOps, but logs looks as always.

"C:\Users\VSSADM~1\AppData\Local\Temp\hugotask_v0.74.1\hugo.exe"  --source D:\a\1\s --baseURL https://devdiary.wachulec.me --destination D:\a\1\a  --enableGitInfo --i18n-warnings --verbose
INFO 2020/09/07 12:48:53 Using config file: 
Building sites … INFO 2020/09/07 12:48:53 syncing static files to D:\a\1\a\

                   | EN  
-------------------+-----
  Pages            | 54  
  Paginator pages  |  1  
  Non-page files   |  0  
  Static files     |  4  
  Processed images |  0  
  Aliases          |  1  
  Sitemaps         |  1  
  Cleaned          |  0  

Total in 369 ms
Finishing: Generate Hugo site

[lxndrblz]

Thanks. I'll try to reproduce issue myself on GitHub Pages then.

[PiotrWachulec]

Thank you @lxndrblz ! I really appreciate your involvement! :)

[lxndrblz]

@PiotrWachulec I tried it on GitHub pages with another account and didn't have any issues. I am slowly running out of ideas.

One last thing you could try, is to remove the submodule and clone the theme. It would be interesting to see if your issue persists.

[PiotrWachulec]

Ok @lxndrblz , I'll try it. I'll come back to you.

[lxndrblz]

Closing issue due to inactivity.

[PiotrWachulec]

Hi @lxndrblz ,
Sorry for being not responsive for a long time. I didn't have time to continue to fight with it. But today I tested your proposition of the solution and the problem still exists. I removed the submodule and cloned the theme manually. I tested upgrading the used Hugo version in my build pipeline too, but nothing changed... What can we do more with it? Thanks in advance!

[lxndrblz]

@PiotrWachulec Thanks for your feedback. I am sorry to hear that your issue still exists.

Is this this your latest working version: https://devdiary.wachulec.me/ ?

Because I earlier had a similar case: Would you mind sharing in which folder your custom css files is located (static or assets)?

[PiotrWachulec]

@lxndrblz in the assets folder.

In the meantime, I removed all files from the publishing folder and add them again, but this also did not work.

If you want I can give you access to my repo to make some debugging.

[lxndrblz]

@PiotrWachulec Access would certainly help.

[PiotrWachulec]

Hi @lxndrblz , I granted access to my repo for you. Thanks a lot for your engagement!

[lxndrblz]

@PiotrWachulec Got it. I'll have a look on the weekend.

[PiotrWachulec]

Hi @lxndrblz :) Any updates from your side?

[lxndrblz]

Hello @PiotrWachulec Thanks for your patience. I've checked the repository and everything looked correct. However, I've also changed the way custom css is handled in the meantime. Would you mind running a git submodule update --remote --merge?
I didn't want to trigger any builds myself.

[PiotrWachulec]

Hi @lxndrblz !

I updated the theme to the newest version with the command which you indicated and... It works now! Thanks a lot for your time and engagement, you are the best! :)

[lxndrblz]

@PiotrWachulec Don't forget to remove me from your repo! 👍

[PiotrWachulec]

Thanks @lxndrblz , of course I forgot 😂 But I already removed you :) Thanks again!