 |
|
You are not logged in! F.A.Q Log in Register |
 |
|
 |
 (nobody)...and 57 guests Last 5 registered Oplandisks nothingstar N_loop yipe foxtrotromeo Browse members... |
 |
Members 8025Messages 2613722 Today 3 Topics 127517 |
|
|||||||||
| |||||||||
|
|
|
||||||||
|
|
|||||||||
| |||||||||
|
|
i was thinking, "when is my next shot to get a code update to the moon so i can pwn that" and all i had to do was poop on^H^H^H open the news |
||||||||
|
|
|||||||||
| |||||||||
|
|
2223 GMT give or take 56 |
||||||||
|
|
|||||||||
| |||||||||
|
|
I submit to you that, although NetHack responded to the full moon in its intended way, this quirky, very hard-to-fathom stop on a machine-learning journey was indeed a bug and a worthy one in the pantheon. It's not a Harvard moth, nor a 500-mile email, but what is? Because the team used Singularity to back up and restore their stack, they inadvertently carried forward the machine time and resulting bug each time they tried to solve it. The machine's resulting behavior was so bizarre, and seemingly based on unseen forces, that it drove a coder into fits. And the story has a beginning, a climactic middle, and a denouement that teaches us something, however obscure. The NetHack Lunar Learning Bug is, I submit, quite worth memorializing. Thank you for your time. |
||||||||
|
|
|||||||||
| |||||||||
|
|
Full Moon June 21 9:07 pm Strawberry Moon Third Quarter June 28 5:53 pm |
||||||||
|
|
|||||||||
|
Messageboard index
|
|||||||||
