Currently, we fix this issue by wiping the content folder, and regenerating it again. We do not know why the site does not run into this error after regenerating all the content. In theory, the offending shout card should cause the same error after being regenerated.
Currently, we fix this issue by wiping the content folder, and regenerating it again. We do not know why the site does not run into this error after regenerating all the content. In theory, the offending shout card should cause the same error after being regenerated.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
...and we don't know why! Here's some logs
@r
Currently, we fix this issue by wiping the content folder, and regenerating it again. We do not know why the site does not run into this error after regenerating all the content. In theory, the offending shout card should cause the same error after being regenerated.