Yes that's right and it may also explain the problem that I met when changing the order status... that may also caused by the unreachable email address...
That's really great !! Thanks. Bin On Fri, Nov 18, 2011 at 4:12 AM, hynekcer <[email protected]> wrote: > Haha... to send a mail can sometimes take an hour and to send an email > without address can take a little more. That is really better to do it > on the background... :-) > I am pleased that the work fell off. > > On 17 lis, 13:55, Bin Chen <[email protected]> wrote: >> Problem resolved! >> The problem resides in the code to send the confirmation email! >> Because I use a faked email for the Oauth user(I don't know the >> email), so the satchmo just blocked there for 2 minutes, and this >> problem is random, maybe DNS resovlve timeout or somethign like that? >> >> Anyway thanks all! >> >> >> >> >> >> >> >> On Thu, Nov 17, 2011 at 5:04 PM, Bin Chen <[email protected]> wrote: >> > Hi hynekcer, >> >> > I diff the database for 2 cases: one for normal registered user, the >> > other one for registered by my program. The difference is the normal >> > registered user has a Contact entry but in my code I didn't new a >> > Contact and save to database. >> >> > Not sure it is the root cause, still testing. I am wondering is it >> > useful for you to resolve the bug that makes the submiting order >> > process timeout? >> >> > Anyway may I suggest in next version satchmo we report error for >> > database inconsistency instead of waiting for timeout? >> >> > And one further question, I don't know where the code resides, can you >> > tell me so maybe I can take a look to try to fix it? The timeout is >> > accurately 2 minutes. >> >> > THANKS. >> > Bin >> >> > On Thu, Nov 17, 2011 at 2:46 PM, Bin Chen <[email protected]> wrote: >> >> Hi hynekcer, >> >> >> I am using runfcgi, and the command says it doesn't support --noreload >> >> option. >> >> >> Is it possible to do it with runfcgi? My command: >> >> >> ./manage.py runfcgi method=threaded host=127.0.0.1 port=8801 >> >> >> On Tue, Nov 15, 2011 at 8:57 AM, Bin Chen <[email protected]> wrote: >> >>> Thanks, I will take a look first. >> >> >>> For the issue that the admin interface can't change the status, I >> >>> didn't notice the timeout, maybe I haven't waited long enough for the >> >>> timeout. >> >> >>> FYI, the timeout of the problem I described earlier is precisely 2 >> >>> minutes, I can't reproduce them but once I can I will send you the >> >>> trace. >> >> >>> On Tue, Nov 15, 2011 at 6:22 AM, hynekcer <[email protected]> wrote: >> >>>> Hi Bin Chen, >> >>>> I wrote a guide how to report timeouts and get a traceback of them. It >> >>>> is written also for you. >> >>>>http://groups.google.com/group/satchmo-users/browse_thread/thread/89b... >> >> >>>> You wrote >> >>>>> I found some cases several times that the admin interface just >> >>>>> can't change the order status... >> >> >>>> That are also timeouts? >> >> >>>> --Hynek >> >> >>>> On 14 lis, 03:01, Bin Chen <[email protected]> wrote: >> >>>>> Yes I found some cases several times that the admin interface just >> >>>>> can't change the order status(not related to this one), then I try to >> >>>>> manipulate the database(delete orders, new orders back and force), >> >>>>> finally it resolved... I don't know why. >> >> >>>>> Thanks for your help, next time I will be trying to "diff" the >> >>>>> database. >> >> >>>>> This problem is OK now, I didn't do any thing... Maybe it is still the >> >>>>> database's problem. >> >> >>>>> On Mon, Nov 14, 2011 at 9:33 AM, hynekcer <[email protected]> wrote: >> >>>>> > Timeout should really be fixed in Satchmo if possible, notably if it >> >>>>> > could be caused by unusual data in the database. >> >> >>>>> > Please, try to find the cause. >> >>>>> > What does automatically created user with manual login? Does it fail >> >>>>> > exactly on the last step of checkout - confirm? >> >> >>>>> > Try to restart python between loging and checkout. This eliminates >> >>>>> > all >> >>>>> > possible causes related to theadlocals. >> >> >>>>> > If I would you, I would first export the database to SQL before and >> >>>>> > after manual/automatic registration and to "diff" them. >> >> >>>>> > On 14 lis, 01:31, Bin Chen <[email protected]> wrote: >> >>>>> >> Thanks hynekcer, I will take a look. I found the submit process is >> >>>>> >> "waiting for something to timeout", if I click the confirm button >> >>>>> >> the >> >>>>> >> page just stuck and finally got Gateway timeout, but after 1 minute >> >>>>> >> the order status can be changed to New successfully. So I guess the >> >>>>> >> order processing logic is waiting for some signal or something? Any >> >>>>> >> idea for which file I should look into? I think the problem resides >> >>>>> >> in >> >>>>> >> confirm order -> change order to New. >> >> >>>>> >> With the account which is registered by human in Satchmo, it is OK >> >>>>> >> without any problems. >> >> >>>>> >> On Mon, Nov 14, 2011 at 8:18 AM, hynekcer <[email protected]> wrote: >> >>>>> >> > Satchmo uses >> >>>>> >> > "threaded_multihost.middleware.ThreadLocalMiddleware". >> >>>>> >> > Verify if there is any code related to it around login. >> >> >>>>> >> > On 13 lis, 04:12, Bin Chen <[email protected]> wrote: >> >>>>> >> >> I am using Satchmo 9.2, and I have developed some code to login >> >>>>> >> >> user >> >>>>> >> >> using a twitter like website's oauth system. My code to create >> >>>>> >> >> the >> >>>>> >> >> user: >> >> >>>>> >> >> if user == None: >> >>>>> >> >> user = User.objects.create_user(username=uu, >> >>>>> >> >> email=uu, >> >>>>> >> >> password=password) >> >>>>> >> >> user.first_name = username >> >>>>> >> >> user.save() >> >> >>>>> >> >> And I login user by: >> >> >>>>> >> >> user = authenticate(username=uu, password=password) >> >>>>> >> >> if user is not None: >> >>>>> >> >> if user.is_active: >> >>>>> >> >> login(request, user) >> >>>>> >> >> # Redirect to a success page. >> >>>>> >> >> else: >> >>>>> >> >> pass >> >> >>>>> >> >> Everything works fine but if I use this auto-generated user to >> >>>>> >> >> make >> >>>>> >> >> the order, the order submit page just stuck. I don't know if I am >> >>>>> >> >> missing something? Please suggest, thanks!! >> >> >>>>> >> > -- >> >>>>> >> > You received this message because you are subscribed to the >> >>>>> >> > Google Groups "Satchmo users" group. >> >>>>> >> > To post to this group, send email to >> >>>>> >> > [email protected]. >> >>>>> >> > To unsubscribe from this group, send email to >> >>>>> >> > [email protected]. >> >>>>> >> > For more options, visit this group >> >>>>> >> > athttp://groups.google.com/group/satchmo-users?hl=en. >> >> >>>>> > -- >> >>>>> > You received this message because you are subscribed to the Google >> >>>>> > Groups "Satchmo users" group. >> >>>>> > To post to this group, send email to [email protected]. >> >>>>> > To unsubscribe from this group, send email to >> >>>>> > [email protected]. >> >>>>> > For more options, visit this group >> >>>>> > athttp://groups.google.com/group/satchmo-users?hl=en. >> >> >>>> -- >> >>>> You received this message because you are subscribed to the Google >> >>>> Groups "Satchmo users" group. >> >>>> To post to this group, send email to [email protected]. >> >>>> To unsubscribe from this group, send email to >> >>>> [email protected]. >> >>>> For more options, visit this group >> >>>> athttp://groups.google.com/group/satchmo-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/satchmo-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
