gmantwo Posted March 27, 2010 Share Posted March 27, 2010 I've tried to email USPSA, but they keep bouncing back. I'm sure Mark would want his pin # if I can get it to him. Anyone know him, pass my cell and email to him. gmantwo@logonbasic.com 573-421-0395 Link to comment Share on other sites More sharing options...
ima45dv8 Posted March 27, 2010 Share Posted March 27, 2010 I've tried to email USPSA, but they keep bouncing back. I'm sure Mark would want his pin # if I can get it to him. Anyone know him, pass my cell and email to him. gmantwo@logonbasic.com 573-421-0395 So far at least 4 people received that same email....besides me! They sent me another pin last night. Link to comment Share on other sites More sharing options...
gmantwo Posted March 27, 2010 Author Share Posted March 27, 2010 LOL, well I already have mine. Maybe he has his as well. Oh, are you him, lol? Link to comment Share on other sites More sharing options...
ima45dv8 Posted March 27, 2010 Share Posted March 27, 2010 LOL, well I already have mine. Maybe he has his as well. Oh, are you him, lol? Link to comment Share on other sites More sharing options...
spanky Posted March 29, 2010 Share Posted March 29, 2010 Pin #? Link to comment Share on other sites More sharing options...
Rob Boudrie Posted March 29, 2010 Share Posted March 29, 2010 That was my goof. An uninitialized variable in the code that sends out the squadding pin for self-squadding caused the message destined for the previous shooter to be sent out when a shooter was not due a message (most typically because they were already in the system). I don't believe the system failed to send out the squadding/PIN notices, but some people got copies they should not. Now you know why USPSA has a policy that we NEVER process credit card numbers on the USPSA server. Anything with credit card numbers is off-loaded to reputable vendors that specialize in secure commerce. Link to comment Share on other sites More sharing options...
High Lord Gomer Posted March 29, 2010 Share Posted March 29, 2010 Cool! I was able to change it so that Mark was squadded with ME! Link to comment Share on other sites More sharing options...
Paul Santiago Posted March 29, 2010 Share Posted March 29, 2010 (edited) That was my goof. An uninitialized variable in the code that sends out the squadding pin for self-squadding caused the message destined for the previous shooter to be sent out when a shooter was not due a message (most typically because they were already in the system). I don't believe the system failed to send out the squadding/PIN notices, but some people got copies they should not. Now you know why USPSA has a policy that we NEVER process credit card numbers on the USPSA server. Anything with credit card numbers is off-loaded to reputable vendors that specialize in secure commerce. I tell people all the time.... INITIALIZE variables!!!! funny things can happen when you dont't and leave it to the system to play with... Edited March 29, 2010 by pas44 Link to comment Share on other sites More sharing options...
Rob Boudrie Posted March 29, 2010 Share Posted March 29, 2010 I tell people all the time.... INITIALIZE variables!!!! funny things can happen when you dont't and leave it to the system to play with... I did, but it was outside the loop that checked to see if each shooter was to receive a message rather than at the inside top of the loop. As a result, if nothing triggered the sending of a message, the string variable I used to contain the message remained set and was sent. It also meant that, as far as the code was concerned, the variable was not "uninitialized" and did not generate run time errors in the log. A more accuarate description would be "failed to re-initialize". Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now