[Systers-dev] Testing Request for Bug 583379

[kanika vats]

Hi Robin,

Yes the steps you gave helped me track down the error.I have corrected the
error (had to use addr.lower() in place of addr in one of the code lines).I
have made the changes directly in DlistUtils.py at abiwt.org but I will make
a commit to the required branch too.You can test and let me know whether the
problem still exists or not.

Thanks

On Tue, Jun 8, 2010 at 10:08 AM, Robin Jeffries <robin at jeffries.org> wrote:

> Nope, I still get the error with the list Change_email_test.  Here is the
> traceback below.  I'm not sure what others are doing differently.  This is
> how I create the error.
>
> - go to www.abiwt.org/mailman/listinfo/change_email_test
> - fill out the subscription information.  The email address I used was
> JeffRies at google.com
> - Wait for the "please confirm your subscription" message to arrive
> - click on the confirmation link (BTW, I can go to the options page from
> there, but that one only asks me to enter my password, and tells me that I
> am on the page for jeffries at google.com -- all lower case)
> - go back to www.abiwt.org/mailman/listinfo/change_email_test
> - enter my mixed case email address in the last text box on the page
> - see the "you have hit a bug" error message on the resulting page.
>
> Also BTW, I entered my user name (mixed case or lower case -- I tried both)
> and password for the line that goes to the subscriber list, and that worked
> just fine, but then that doesn't need access to the postgres database.
>
> Kanika Vats, does this help you track it down?
>
> Robin
>
>
> Jun 07 21:30:02 2010 admin(1448):
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> admin(1448): [----- Mailman Version: 2.1.10 -----]
> admin(1448): [----- Traceback ------]
> admin(1448): Traceback (most recent call last):
> admin(1448):   File "/usr/local/mailman/scripts/driver", line 101, in
> run_main
> admin(1448):     main()
> admin(1448):   File "/usr/local/mailman/Mailman/Cgi/options.py", line 821,
> in main
> admin(1448):     options_page(mlist, doc, user, cpuser, userlang)
> admin(1448):   File "/usr/local/mailman/Mailman/Cgi/options.py", line 865,
> in options_page
> admin(1448):     subscriber_id =
> subscriber.getSubscriber_id_raw_or_die(user)
> admin(1448):   File "/usr/local/mailman/Mailman/DlistUtils.py", line 98, in
> getSubscriber_id_raw_or_die
> admin(1448):     raise ErrorsDlist.InternalError
> admin(1448): InternalError
> admin(1448):    HTTP_REFERER:
> http://abiwt.org/mailman/listinfo/change_email_test
> admin(1448):    SERVER_SOFTWARE: Apache/2.2.8 (Ubuntu)
> PHP/5.2.4-2ubuntu5.10 with Suhosin-Patch
> admin(1448):    SCRIPT_NAME: /mailman/options
> admin(1448):    SERVER_SIGNATURE: <address>Apache/2.2.8 (Ubuntu)
> PHP/5.2.4-2ubuntu5.10 with Suhosin-Patch Server at abiwt.org Port
> 80</address>
> admin(1448):
> admin(1448):    REQUEST_METHOD: POST
> admin(1448):    PATH_INFO: /change_email_test
>
>
> On Mon, Jun 7, 2010 at 1:08 PM, Jason Cox <jasonwilburcox at gmail.com>wrote:
>
>> Kathy,
>>
>> Ok, that is how I was thinking it works.
>>
>> Thanks!
>>
>> Jason
>>
>>
>> On Mon, Jun 7, 2010 at 3:48 PM, Kathy Richardson <kjr at casaveracruz.com>wrote:
>>
>>>
>>>
>>> Jason,
>>>
>>> I'm answering this because I want to test my understanding, and hope
>>> others will correct me if I am wrong.
>>>
>>> Robin said I was wrong about any old code running.   I now believe that
>>> this is the deal:
>>>  MM stopped
>>>  Apache stopped
>>>
>>>  The new code was installed ( python files over writing existing python
>>> files)
>>>
>>>  MM started
>>>  Apache started
>>>
>>> This means that all/any data or messages that existed before the upgrade
>>> are still there.
>>> The new code needs to run on the exact same data.  If not then a
>>> conversion step needs to take place after stopping the services and before
>>> restarting then.  Of course new code could be smart enough to handle a
>>> complicate upgrade in functionality seamlessly.
>>>
>>> Kathy
>>> On Jun 7, 2010, at 10:45 AM, Jason Cox <jasonwilburcox at gmail.com> wrote:
>>>
>>> Robin,
>>>
>>> On Fri, Jun 4, 2010 at 7:28 PM, Robin Jeffries <robin at jeffries.org>
>>> wrote:
>>>
>>> Jason and company need to create a list for this testing cycle (it needs
>>> to
>>> be created with the code that we are testing) and I need to figure out
>>> how
>>> to create a user with
>>>
>>>
>>> When a list is created, does it use the code from the time of creation
>>> forever? Or, does updating the code update how the list works as well?
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>>
>>> mixed case addresses.  The easiest way to deal with the latter is that I
>>> will take on testing the test for the bug this is supposed to fix (SBT1
>>> --
>>> Jason has already dibbed SBT2), as I can't get to creating this user till
>>> tomorrow.
>>>
>>> Jason, can you let us all know when you have the list created?  (Or
>>> whoever
>>> you delegate this to creates it)
>>>
>>> Robin
>>>
>>> On Fri, Jun 4, 2010 at 3:04 PM, Jennifer Redman <jenred at gmail.com>
>>> wrote:
>>>
>>> Ok I've merged Kanika Vats changes into systers-dev/systers/development
>>> and
>>> pulled the changes to abiwt.org.
>>>
>>> Restarted Mailman.  System should now be ready for testing.
>>>
>>> Let me know if you have any problems.
>>>
>>> Jen
>>>
>>>
>>> To unsubscribe from this conversation, send email to <
>>> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>
>>> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
>>> >>
>>> or visit <
>>> http://systers.org/mailman/options/systers-dev?override=121&preference=0
>>> >
>>> To contribute to this conversation, use your mailer's reply-all or
>>> reply-group command or send your message to
>>> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org> <
>>> systers-dev%2Btesting7 at systers.org<systers-dev%252Btesting7 at systers.org>
>>> >
>>> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>>> <systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>>
>>>
>>> To unsubscribe entirely from systers-dev, send email to <
>>> systers-dev-request at systers.org> with subject unsubscribe.
>>>
>>>
>>>
>>>
>>>
>>> To unsubscribe from this conversation, send email to <
>>> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>>
>>> or visit <
>>> http://systers.org/mailman/options/systers-dev?override=121&preference=0
>>> >
>>> To contribute to this conversation, use your mailer's reply-all or
>>> reply-group command or send your message to
>>> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org>
>>> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
>>> >
>>> To unsubscribe entirely from systers-dev, send email to <
>>> systers-dev-request at systers.org> with subject unsubscribe.
>>>
>>>
>>>
>>
>


-- 
Best Regards
Kanika Vats