Project Euler Forum

Yes, 800 problems is quite a landmark.

Thanks for letting me know about the minimal output for problems. It should be fixed now.

More a minor curiosity or caching issue than a real bug, I suspect, but I noticed something strange in the Big Game Hunter award recipients. There are currently 41 people in newly-created level 31, who have solved at least 775 problems, which mean they have at most 25 unsolved problems. That means they should all have the Big Game Hunter award for solving at least half the 50 most difficult problems. But if you look at that award's recipients, it only shows 32 people at level 31. Why the missing people? At the current time, the Big Game Hunter list was updated more recently than the level 31 list.

Scanning the diffs, looks like the people missing from the Big Game Hunter list are Jerome R, Tepsi, aleksey, gmt, grechnik, hos-lyric, uwi, voltara, and x22, all of whom have been active in the past day.

Interesting and thank you for drawing this to my attention.

Awards are earned when a problem is solved or a member visits their own progress page (awards sub-section). It seems that the script which triggered when a problem is solved wasn't checking difficulty based awards properly. Visiting the progress page for a couple of test cases from those you listed gave them the award.

I've made some changes, which I hope will have solved the issue and hasn't caused some other undesired effect. :fingers-crossed:

After solving problem 360 I got again a message indicating (wrongly) that I got the big game hunter award. Unfortunately that's still too far away for me...

(It's a pity because I wanted a screenshot of the "problem solved" page, since I got a level up. But now this screenshot shows the "new award" line... which would be nice, if not for the detail that I know it's not true ).

Why my post in thread 799 is not permanent?
Is it just a bug or does my post violate the rules?

https://projecteuler.net/action=redirect;post_id=401131

@Decarabia: Thank you for reporting this. I have no idea how this happened, but it seems one of the scripts had reverted back to an old version that had this issue. It should be fixed for the next time you or anyone else solves a problem. I am sorry to say that it means you've lost it again, but it's always good to have a goal to work towards.

@hidesugar: Your post certainly does not violate any rules and I don't know what could have caused it. I did upload a lot of changes last night to implement some features for the admin team, but nothing I did should have caused temporary/permanent posts to be affected. I've set your post to permanent again, but we'll have to keep an eye on things. Can you remember if it was originally permanent or did you not notice at the time?

Thank you for fixing.
I think it was originally permanent, but not sure.

euler wrote: Fri Jun 17, 2022 5:45 pm I am sorry to say that it means you've lost it again, but it's always good to have a goal to work towards.

Of course . I never actually got the award; if I went to the awards page, it was (correctly) displayed as still not achieved; it's just that I got the message.

Thanks again for all your work.

For a lot of problems, the "solved by" count seems to have decreased substantially at some point. As far as I can tell not every problem has been affected, but e.g. Problem 1 is way lower than it used to be (726k now vs. something like a million; it had 949k back in May 2020, which is when I decided to save all of PE's solve data to a spreadsheet for some reason), and the numbers don't agree with the Statistics page. Is this a bug, or the result of something intentional?

(and congrats on 800+ excellent problems, onwards to 900!)

Thanks for the heads-up. I'd completely missed that. I'd made a small error in one of the scripts in the recent changes. It should be fixed now. I've manually synced problem 1 to check it is working properly, but it will take time for the counts to synchronise properly for the other problems. This happens when someone solves a problem.

On the Eulerians page, performance is misspelt (peformance) in one location.

Hopefully this is the right spot for this. Code snippets in the language Nim do not render properly. I'm not sure if this is because the syntax highlighter needs to be updated or something. Previous posts about syntax highlighting indicate that the site uses highlight.js, which should support Nim fully. For an example take a look at my post in the thread for 508 (link), where it thinks that // are supposed to be comments, and ignores the real comments which start with #.

Not sure if there's a great solution to this but I thought I'd make note of it.

By default, highlight.js supports 40 of the most popular languages. Upon request, it is necessary to add support modules for other languages that cannot be rendered by its generic handling algorithm. As you're saying it doesn't do a good job, I've added specific support for Nim.

Thanks for adding it!
However.. the highlighting works on light mode, but me and a friend have verified that using dark mode, no syntax highlighting is used for any code snippets in any language.

Thank you for letting me know. When I remember, I update the highlight.js CDN links to the latest versions (currently 11.5.1). It seems that the old dark mode style we used: tomorrow-night, has been removed for no obvious reason. It's a shame because it is a really nice version. For the sake of consistency I have replaced both light and dark versions with "Stack Overflow" themes.

It seems at least on my end that dark mode code highlighting is still broken.

It was working last night when I uploaded it, but it wasn't working for me when I just checked now. It looks like one of their CDN streams wasn't working, so I've changed them all to a different one. Could you check again?

Yup, works for me now! Thanks for the fix.

When trying to open main site, I'm getting a "certificate expired" warning from Firefox (it actually doesn't let me through to the site).

The certificate for projecteuler.net expired on 19/09/2022.
Error code: SEC_ERROR_EXPIRED_CERTIFICATE

Yep, cert is expired, and HSTS means you can't "bypass" the warning. This is a code red.