search

ikanago / omekasy

π˜Ύπ™€π™’π™’π™–π™£π™™ π™‘π™žπ™£π™š 𝙖π™₯π™₯π™‘π™žπ™˜π™–π™©π™žπ™€π™£ π•₯𝕙𝕒π•₯ π•”π• π•Ÿπ•§π•–π•£π•₯𝕀 π•’π•π•‘π•™π•’π•Ÿπ•¦π•žπ•–π•£π•šπ•” 𝕔𝕙𝕒𝕣𝕒𝕔π•₯𝕖𝕣𝕀 𝒕𝒐 π’—π’‚π’“π’Šπ’π’–π’” π’”π’•π’šπ’π’†π’” πšπšŽπšπš’πš—πšŽπš πš’πš— πš„πš—πš’πšŒπš˜πšπšŽ.
MIT License
131 stars 4 forks source link

Fix naming of sans family #23

Closed famasoon closed 2 years ago

famasoon commented 2 years ago

Fix #21

ikanago commented 2 years ago

Thank you for your work! But some of the test fails due to the existing build error, so I'm going to investigate it ahead of review. I'm going to create another PR fixing the problem, merge it toward main branch and re-run CI on this PR.

ikanago commented 2 years ago

Build error in CI on main branch must be solved on #24 , but the same error occurs... πŸ€” The error was solved by refreshing the build cache on GitHub Actions ~~and currently failing job on this PR uses the same cached artifacts. So I have thought everything should go well, but...~~ Currently failing job and the job succeeded on main branch uses different cache artifact. So I have to invalidate the current cache in some way.

ikanago commented 2 years ago

As a workaround, stopped using cache temporarily.