nreport() caches recent news reports in cache[], so it can collapse
multiple news reports into one. Writing back such a collapsed news
report triggered a generation oops when the processor had been yielded
since the cached report was last written back. But this is actually
perfectly safe, because the cache can't become stale: news file
updates either go through the cache (nreport()), or they clear the
entire cache (delete_old_news()).
Silence the oops by marking the news report fresh.
A case could be made for removing nws_generation alltogether. Maybe
later.
projects / empserver / commit