search

hugo-toha / toha

A Hugo theme for personal portfolio
https://hugo-toha.github.io
MIT License
1.03k stars 591 forks source link

Process completed with exit code 255 #738

Closed IhnwhiHeo closed 1 year ago

IhnwhiHeo commented 1 year ago

Hi Toha folks,

I have been facing the following error messages when I try to build and update my website using GitHub Actions: Process completed with exit code 255.

For example, please see my recent trials:

** I am using Mac to build my website.

hossainemruz commented 1 year ago

Hi @IhnwhiHeo, we have made some changes in how the theme is used. We have moved from git sub module to Hugo modules. Please check the Usage section on Readme file.

IhnwhiHeo commented 1 year ago

Hi @hossainemruz, thank you for letting me know! I will check the Usage section and let me ask you if I find anything unclear.

Cheers, Ihnwhi

hossainemruz commented 1 year ago

Be aware that configuration format has changed. You might have to change quite a few things. If you don't need any newer features and happy with your existing site, I will recommend to disable auto-updating using dependabot and stay to the latest stable release v3.8.0.

IhnwhiHeo commented 1 year ago

@hossainemruz I checked a bit. I have two quick questions, please:

hossainemruz commented 1 year ago

It seems you have already updated the theme to the latest commit. You have to roll-back to the latest release. I will let you know how you can you roll-back.

IhnwhiHeo commented 1 year ago

I see. Could you please let me know how to do that? Thanks :)

hossainemruz commented 1 year ago

Sure. Give me a day.

hossainemruz commented 1 year ago

Hi @IhnwhiHeo, created a PR to your repo upgrading the configuration to latest version. Once you merge it, your GitHub action should start working again.

IhnwhiHeo commented 1 year ago

Hi @hossainemruz, Thank you so much for this! I appreciate it. Then, from now onwards, I should not update the toha package, right?

hossainemruz commented 1 year ago

You can update the theme.

IhnwhiHeo commented 1 year ago

Hi @hossainemruz,

Thank you! I will keep updating the theme. BTW, an additional issue arises:

Could you please check this issue?

hossainemruz commented 1 year ago

I will take a look at night.

IhnwhiHeo commented 1 year ago

Great, thank you! FYI, the example TOHA website also stopped working for the resume part. So fixing this will be very useful.

IhnwhiHeo commented 1 year ago

Hi @hossainemruz, Just wondering whether there are any updates on Resume/CV error. Hope this does not bug you too much, tho :)

hossainemruz commented 1 year ago

Hi @IhnwhiHeo. Sorry, I couldn't manage time to look into this issue. This week was overwhelming for me. Hopefully, I will be able to look into this issue over the weekend or next week.

d-huck commented 1 year ago

I think what is happening here is that the fonts are overwriting whatever is in fonts from this line in the example config:

module:
  imports:
  - path: github.com/hugo-toha/toha/v4
  mounts:
  - source: ./node_modules/flag-icon-css/flags
    target: static/flags
  - source: ./node_modules/@fontsource/mulish/files
    target: static/files
  - source: ./node_modules/katex/dist/fonts
    target: static/fonts

This basically is just filling the files directory with the mullish font files and nothing else.

A temporary workaround is to just change that section in config.yaml to

module:
  imports:
  - path: github.com/hugo-toha/toha/v4
  mounts:
  - source: ./node_modules/flag-icon-css/flags
    target: static/flags
  - source: ./node_modules/@fontsource/mulish/files
    target: static/files
  - source: ./node_modules/katex/dist/fonts
    target: static/fonts
  - source: ./static/files
    target: static/files

I don't know enough about Hugo to suggest a more substantial change to the theme, but I hope this helps @IhnwhiHeo in the meantime. To make things less confusing, I actually end up making a pdf folder and change any pdf links to point to that directory. I still have to add

- source: ./static/pdf
  target: static/pdf
IhnwhiHeo commented 1 year ago

@hossainemruz No worries at all! I understand that sometimes works are overwhelming. I hope all went well :) And the good news is that the solution suggested by @d-huck works! After adding those two lines, the website now works perfectly fine. Thank you so much, @d-huck!! Your solution is just amazing!

hossainemruz commented 1 year ago

@d-huck solution is the right one. I would have suggested that too. If everything works properly, please consider closing this issue.

IhnwhiHeo commented 1 year ago

Perfect. Let me close this issue now. Thank you @hossainemruz and @d-huck for your time on this issue!