💾 Archived View for bbs.geminispace.org › u › gritty › 16880 captured on 2024-05-12 at 18:25:27. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Another corner condition bug"
I just pushed the out of range fix, so that should hopefully not be an issue now.
I'm not against picking more dice up, I just hadn't considered folks would want to do that. I I'll have to test it locally to make sure there's no bugs in just keeping the "select" option enabled
2 hours ago
ah, maybe I'm misreading - having the app know when a response was already received for the dice and not allowing more?
@gritty no I think the first one is better
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.
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
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...