Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blogs sorted by a certain year are having issues #2665

Closed
2 tasks done
fanyangCS opened this issue Aug 28, 2024 · 6 comments
Closed
2 tasks done

Blogs sorted by a certain year are having issues #2665

fanyangCS opened this issue Aug 28, 2024 · 6 comments
Labels

Comments

@fanyangCS
Copy link

fanyangCS commented Aug 28, 2024

Have you checked that your issue isn't already filed?

  • I read through FAQ and searched through the past issues, none of which addressed my issue.
  • Yes, I have checked that this issue isn't already filed.

Bug description

when blogs sorted by years, i.e., 2020, 2022, 2023, and 2024, the year of 2023 shows a blank page, but all other years look fine

How to reproduce the bug

The problematic blog year is here: blogs in 2023. Other year looks fine: blogs in 2024

Error messages and logs

see full logs here: https://github.com/fanyangCS/fanyangcs.github.io/actions/runs/10590121696/job/29345374852
the config yml file here: https://github.com/fanyangCS/fanyangcs.github.io/blob/master/_config.yml

Below are suspected logs:

AutoPages: Disabled/Not configured in site.config.
Pagination: Complete, processed 1 pagination page(s)
W, [2024-08-28 04:21:18 #1903] WARN -- : Lexer: unexpected token \' at 21708; brace level 1; mode :bibtex. W, [2024-08-28 04:21:22 #1903] WARN -- : Lexer: unexpected token ' at 21708; brace level 1; mode :bibtex.
[NbConvertApp] Converting notebook /tmp/jekyll-jupyter-notebook20240828-1903-ssrj0u.ipynb to html
Warning: Empty slug generated for '--'.
Conflict: The following destination is shared by multiple files.
The written file may end up with unexpected contents.
/home/runner/work/fanyangcs.github.io/fanyangcs.github.io/_site/blog/2023/index.html
- blog/2023/index.html
- /home/runner/work/fanyangcs.github.io/fanyangcs.github.io/_posts/--.md

      Conflict: The following destination is shared by multiple files.
                The written file may end up with unexpected contents.
                /home/runner/work/fanyangcs.github.io/fanyangcs.github.io/_site/blog/2024/.md/index.html
                 - /home/runner/work/fanyangcs.github.io/fanyangcs.github.io/_posts/.md
                 - /home/runner/work/fanyangcs.github.io/fanyangcs.github.io/_posts/.md
                 - /home/runner/work/fanyangcs.github.io/fanyangcs.github.io/_posts/.md
                
                done in 190.413 seconds.

Auto-regeneration: disabled. Use --watch to enable.

What operating system are you using?

Not applicable.
I am using GitHub Pages to compile, build, and deploy directly.

Where are you seeing the problem on?

Deployed site

More info

No response

@fanyangCS fanyangCS added the bug label Aug 28, 2024
@github-staff github-staff deleted a comment Aug 28, 2024
@george-gca
Copy link
Collaborator

Does this also happens when running locally?

I took a look at your posts and everything seems fine. The only "unusual" thing I saw was that none of your posts have either description, tags, or categories. Just to take these out of the equation, can you fill these fields and test again?

@fanyangCS
Copy link
Author

fanyangCS commented Aug 28, 2024

I removed all the local posts and it is the same. Maybe it is due to external posts in the _config.yml?

I don’t have a local environment to test.

@george-gca
Copy link
Collaborator

The mode :bibtex in your error means that your bib file is wrong. I recommend using something like bibtex-tidy to clean and format it a bit. For example, in here you have a \ after a comma that is invalidating your bib file.

Now, about the 2023 blog posts is probably something related to external blog posts, but I am not sure what. This requires further investigation.

@george-gca
Copy link
Collaborator

Just found out what is your issue, and yes: it is because of external posts. More specifically, your posts have foreign characters, and as the regex to replace chars in the external posts plugin replace those, the title ends up empty and it gives this error. I will upload a patch for it soon.

@george-gca
Copy link
Collaborator

I just commited a fix for this issue. Check if cd3f4d6 solves this issue for you. You can either get the latest updates from our repo, or just apply these changes in your own code and test if it works.

@fanyangCS
Copy link
Author

Yes, it is fixed. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants