Topic: MyriadCoins.com - Make the bet you want - page 2. (Read 7992 times)

She's thinking now that the reason it wasn't updating was because it was saying "double check your amounts" because the numbers were too high...

She's made her first bet, 0.01 to win the max, with a 0.24% chance of winning.  Not surprisingly she lost.

She guessed 6942, and would like her free dime please, and is a newbie so can't post here.  Should she post in the newbie forum, or is my word good enough?

I think she plans to make the same bet 9 more times now... 

It turns out the percentage chance isn't updating even if she does tab between boxes.  I don't know why that would be - she'll not have javascript disabled.

And another problem:  she tried betting 0.01 to win the maximum, and got an error:

> it says win amt must be between 0.05 and 3.9179
Chris: and was it?
> I put 3.92 cuz thats what it said on the side

So it's reporting the max bet as 3.92 when it's really 3.9179, and rejecting 3.92 when you submit the bet.

I tried showing the site to a friend.  Got this comment:

"so it doesnt change anything when i play with the numbers, that i can see"

She was editing the bet amount, but not tabbing or clicking out of the box.  The percentage only updates when you leave the box.  How about having it update on each keystroke (onkeyup) rather than waiting for me to leave the box?

I have Windows 7 on this laptop still I think - I could try it there.  I also have a machine with the previous Ubuntu (11.10) on it.

I can't think what it might be though - I tried 3 completely different browsers and got the same result from all 3.

Can you think of anything I can run here that would help diagnose why it's sending duplicate requests?

Awesome... now I can sleep.  I still wish I knew why your system wanted to send two requests, but at least we stopped it.

Looks fine from the one trial I did.  Good job! 

You know I'll let you know if I see the error again...

Make sure you refresh to get the latest javascript, but it should prevent duplicate submissions now.

Cleared you IP records again.  Since the first request creates the game, the second request sees that game as well.  Anyway, I'm off to javascript land, be back soon.

It's odd that the "Too many outstanding games from your IP address. Please pay for a game or wait for one to time out" message also goes away when I refresh.  Is it the 2nd POST that's getting that message, because it's trying to make a 2nd game?

I just got the "tampered" and "too many" messages, hit refresh and got a payment address, sent BTC to that address, and won.  So it seems like both messages can be ignored.

Thanks... I only bring up the double clicking because I've seen it too many times.  Facepalm.

Heck, I'm going to go ahead and patch up the javascript to prevent the extra submission.  I'll let you now when it is uploaded.

I just tried tabbing to the button and hitting the space bar instead of clicking it.  I got the error again, but also the 'too many' message, even though I just paid & lost:

Yes, the null.php is fine.  The actual form is hooked up to load that in a hidden iframe, whereas the actual submission is handled by javascript (it needs to clean up a few things).  I had to make it actually submit the form the old fashion way to get it to remember the autocomplete values.  It seems browsers only save them on a regular form submission, not an ajax submission, so null.php just ignores it's parameters and prints "Okay".  Not the most efficient way to do things, but sometimes the standards box you in.

I'm clicking.  Once.

Right, I fixed a bug earlier that was causing what you saw.  I have no clue what could be causing the issue for dooglus unless his keyboard is stuttering and sending two enters.  I can reproduce if I hit enter twice quickly.  Double clicking could also trigger it.  If that's the case, shame on you dooglus, never double click on the internet .  I'll leave it alone for now in case you guys want to play with it more, but i have a patch for the javascript that will ignore the second response that I'll upload in the morning.  It needs put in place anyway since double clicking and double enters will cause the behavior.  In fact, I should be able to rework it a little to prevent the second request from being made, and still ignoring extra responses in case a duplicate request somehow gets made.

As for a workaround if you guys or anyone else sees this tonight and wants to play, if you hit refresh the game will be perfectly fine to play.

I use the same address every time, and currently see the error almost every time.  I'd guess 6 out of the last 7 times I tried, I saw it.

For the record, I saw the error in chromium without squid, and in firefox without squid.

I'm not sure what other browsers I have.  I don't want to install all the Qt stuff I'll need to get Konqueror working.  Maybe 'epiphany' (the basic GNOME browser) will work - I'll try it.

[time passes]

The 'tampered' error showed up in epiphany too.  I notice that in addition to the two 'create game' POSTS, there's also a 'null' one:


Is that something you know about and expect to see?

I got it like 3 times in a row earlier (emailed you about it) while reusing an address and then didn't get it when I tried a new address. Now I can't make it happen.

The bug still happens without squid.

The packets now contain gzipped responses, but I'll email you them anyway.

I'll also try in firefox.

Mine is a little newer, but shouldn't be majorly different:
18.0.1025.168 (Developer Build 134367 Linux) Built on Ubuntu 11.10, running on LinuxMint 12

Thanks again for all the effort, I'll probably hang around long enough to see how your new experiment turns out before calling it a night.

I renamed the files manually and may have messed them up.  I thought I got it right, but maybe not.

I'll try connecting directly to the internet, rather than going via squid and see if that fixes the problem...

(it seems chromium doesn't have any way of changing proxy settings except from the command line, so I'll post this, restart chromium, test, and report back).  It's "18.0.1025.151 (Developer Build 130497 Linux) Ubuntu 12.04" by the way.

Looking at your captured packets, I see no problems with 1-3, but it appears 4 and 5 are mixed up and missing some data.

4a should be a match for 5b, although 5b has two responses and 4a is only one request.
4b is the appropriate response for 5a.

That said, the request in 4a should never have happened, it is identical to 3a.  A double request would indeed cause the "tampered" error, but I'm stumped as to why it would have occurred.  It also explains why refreshing it fixes it, since as you can see in 3b, the game was successfully submitted and refreshing it just reloads it from the database.  I'm unable to reproduce the extra request here.  I'm also using Chromium, as you seem to be.  Do you also get the same behavior in other browsers?  I don't know much about squid, but is it possible it is duplicating the request?

Can you reproduce the "tampered" error freemoney?

I'll leave the site be for now, but I'm going to bed soon.  If either of you find more info let me know, otherwise I will put a fix in place in the morning that will not replace the text after the second request.  That way only the first submission's response will be displayed, and you'll see the regular text instead of the error.  Not ideal, but if I can't reproduce the extra request, it it's hard to eliminate it.

Thank you very much dooglus for providing all this debugging info.  It was very helpful.