[web2py] Re: 2.19.1 redis sessions problem
Is there any update on this or will we not be able to use redis again? ;) I see there is a redis pull request from last year too. On Saturday, 28 March 2020 11:30:11 UTC+1, Jose C wrote: > > Just started testing version 2.19.1 (prior to upgrading) with py3.6 and it > appears that when sessions are stored in redis, a new session is being > created each time the login is submitted which then prevents a session from > logging in. > > This issue was discussed in > https://groups.google.com/forum/#!msg/web2py/z1ee025ghRU/qByNuEjGAgAJ > and Jim S found a workaround with the .decode function which worked on py3 > but not on py2 (and which I've been using live). It looks like the redis > session code has been refactored in 2.19.1 to remove all the decodes but I > can't get it to work correctly. > > Can anyone confirm whether they have this issue when trying to login using > redis sessions in 2.19.1 (with py3)? If confirmed, I'll file a bug report. > > Thanks, > > Jose > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/70b9080b-f567-48c3-8a2c-466f65cd5165o%40googlegroups.com.
[web2py] Re: 2.19.1 redis sessions problem
Thanks for confirming... issue created: https://github.com/web2py/web2py/issues/2330 On Wednesday, 10 June 2020 17:03:39 UTC+1, Joe Barnhart wrote: > > Yep. I just confirmed the errant behavior with web2py 2.20.4 and python > 3.8.2. If reds sessions are enabled the logon never completes. > > -- Joe B. > > On Sunday, March 29, 2020 at 11:39:10 PM UTC-5, Massimo Di Pierro wrote: >> >> Sorry. We should fix this. Will look into it asap. >> >> On Sunday, 29 March 2020 15:38:27 UTC-7, Jim S wrote: >>> >>> FWIW - I've abandoned redis for sessions. I can't get it to work >>> reliably and no one seems interested in fixing it. I submitted some >>> patches but they were rejected. So, I've moved my sessions into my >>> database. Not what I wanted to do, but at least that works reliably. >>> Sorry to be negative about this, it just seems it isn't a priority for the >>> project. >>> >>> -Jim >>> >>> >>> On Saturday, March 28, 2020 at 5:30:11 AM UTC-5, Jose C wrote: Just started testing version 2.19.1 (prior to upgrading) with py3.6 and it appears that when sessions are stored in redis, a new session is being created each time the login is submitted which then prevents a session from logging in. This issue was discussed in https://groups.google.com/forum/#!msg/web2py/z1ee025ghRU/qByNuEjGAgAJ and Jim S found a workaround with the .decode function which worked on py3 but not on py2 (and which I've been using live). It looks like the redis session code has been refactored in 2.19.1 to remove all the decodes but I can't get it to work correctly. Can anyone confirm whether they have this issue when trying to login using redis sessions in 2.19.1 (with py3)? If confirmed, I'll file a bug report. Thanks, Jose >>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/1e28ed19-5eba-44a7-947e-ae3bc76aba1do%40googlegroups.com.
[web2py] Re: 2.19.1 redis sessions problem
Yep. I just confirmed the errant behavior with web2py 2.20.4 and python 3.8.2. If reds sessions are enabled the logon never completes. -- Joe B. On Sunday, March 29, 2020 at 11:39:10 PM UTC-5, Massimo Di Pierro wrote: > > Sorry. We should fix this. Will look into it asap. > > On Sunday, 29 March 2020 15:38:27 UTC-7, Jim S wrote: >> >> FWIW - I've abandoned redis for sessions. I can't get it to work >> reliably and no one seems interested in fixing it. I submitted some >> patches but they were rejected. So, I've moved my sessions into my >> database. Not what I wanted to do, but at least that works reliably. >> Sorry to be negative about this, it just seems it isn't a priority for the >> project. >> >> -Jim >> >> >> On Saturday, March 28, 2020 at 5:30:11 AM UTC-5, Jose C wrote: >>> >>> Just started testing version 2.19.1 (prior to upgrading) with py3.6 and >>> it appears that when sessions are stored in redis, a new session is being >>> created each time the login is submitted which then prevents a session from >>> logging in. >>> >>> This issue was discussed in >>> https://groups.google.com/forum/#!msg/web2py/z1ee025ghRU/qByNuEjGAgAJ >>> and Jim S found a workaround with the .decode function which worked on py3 >>> but not on py2 (and which I've been using live). It looks like the redis >>> session code has been refactored in 2.19.1 to remove all the decodes but I >>> can't get it to work correctly. >>> >>> Can anyone confirm whether they have this issue when trying to login >>> using redis sessions in 2.19.1 (with py3)? If confirmed, I'll file a bug >>> report. >>> >>> Thanks, >>> >>> Jose >>> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/fe268b34-a931-45d2-872c-a5e73d803b43o%40googlegroups.com.
[web2py] Re: 2.19.1 redis sessions problem
Sorry. We should fix this. Will look into it asap. On Sunday, 29 March 2020 15:38:27 UTC-7, Jim S wrote: > > FWIW - I've abandoned redis for sessions. I can't get it to work reliably > and no one seems interested in fixing it. I submitted some patches but > they were rejected. So, I've moved my sessions into my database. Not what > I wanted to do, but at least that works reliably. Sorry to be negative > about this, it just seems it isn't a priority for the project. > > -Jim > > > On Saturday, March 28, 2020 at 5:30:11 AM UTC-5, Jose C wrote: >> >> Just started testing version 2.19.1 (prior to upgrading) with py3.6 and >> it appears that when sessions are stored in redis, a new session is being >> created each time the login is submitted which then prevents a session from >> logging in. >> >> This issue was discussed in >> https://groups.google.com/forum/#!msg/web2py/z1ee025ghRU/qByNuEjGAgAJ >> and Jim S found a workaround with the .decode function which worked on py3 >> but not on py2 (and which I've been using live). It looks like the redis >> session code has been refactored in 2.19.1 to remove all the decodes but I >> can't get it to work correctly. >> >> Can anyone confirm whether they have this issue when trying to login >> using redis sessions in 2.19.1 (with py3)? If confirmed, I'll file a bug >> report. >> >> Thanks, >> >> Jose >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/d829a9cb-620a-440f-bd1d-baea78d88a12%40googlegroups.com.
[web2py] Re: 2.19.1 redis sessions problem
FWIW - I've abandoned redis for sessions. I can't get it to work reliably and no one seems interested in fixing it. I submitted some patches but they were rejected. So, I've moved my sessions into my database. Not what I wanted to do, but at least that works reliably. Sorry to be negative about this, it just seems it isn't a priority for the project. -Jim On Saturday, March 28, 2020 at 5:30:11 AM UTC-5, Jose C wrote: > > Just started testing version 2.19.1 (prior to upgrading) with py3.6 and it > appears that when sessions are stored in redis, a new session is being > created each time the login is submitted which then prevents a session from > logging in. > > This issue was discussed in > https://groups.google.com/forum/#!msg/web2py/z1ee025ghRU/qByNuEjGAgAJ > and Jim S found a workaround with the .decode function which worked on py3 > but not on py2 (and which I've been using live). It looks like the redis > session code has been refactored in 2.19.1 to remove all the decodes but I > can't get it to work correctly. > > Can anyone confirm whether they have this issue when trying to login using > redis sessions in 2.19.1 (with py3)? If confirmed, I'll file a bug report. > > Thanks, > > Jose > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/9ffc7481-f757-4bd9-8a51-dd0602220d8f%40googlegroups.com.
