๐Ÿ’พ Archived View for bbs.geminispace.org โ€บ u โ€บ gritty โ€บ 16883 captured on 2024-05-12 at 18:25:28. Gemini links have been rewritten to link to archived content

View Raw

More Information

โžก๏ธ Next capture (2024-05-26)

-=-=-=-=-=-=-

Comment by ๐Ÿ€ gritty

Re: "Another corner condition bug"

In: s/farkle

ah, maybe I'm misreading - having the app know when a response was already received for the dice and not allowing more?

๐Ÿ€ gritty [mod]

1 hour ago

3 Later Comments โ†“

๐Ÿ satch ยท 1 hour ago:

@gritty no I think the first one is better

๐Ÿš€ stack [OP] ยท 1 hour ago:

Well, if you implement my idea of accepting values, you can take multiple inputs in any order! If you keep renumbering dice, order matters, and to be safe you probably should not accept multiple inputs. Although it's unlikely to receive them out-of-order.

๐Ÿ€ gritty [mod] ยท 1 hour ago:

ah I get it now. Let me think it over, but you're right, multiple inputs should be disabled - I have flags for this but apparently I wasn't checking

Original Post

๐ŸŒ’ s/farkle

Another corner condition bug โ€” Somehow, in Lagrange, I managed to get two "select dice" dialogs. After the first one is accepted, the second one results in a crashed cgi. I was not able to easily replicate it, so I opened two windows with the same certificate into "?select", and yup, same deal - pythony CGI crash It seems that your logic is not protected from out-of-sequence responses. Oh, entering the selection directly into the URL line allows you to select from the remaining dice more than...

๐Ÿ’ฌ stack ยท 5 comments ยท 6 hours ago