Updating the leaking-user test to reproduce a problem I'd found earlier.

[jmacdotorg]

Per Yanick's request, constructing a simulation of an issue I ran into when using the current release of this module in a live Catalyst-based application.

Changes made include using two different $mech objects (to simulate two separate but simultaneous sessions), and having the /leaking_users action display the Twitter ID of the currently authenticated user.

Please disregard the first two no-op change-chunks in basic-app.t; not sure how those got in there.

[yanick]

Sorry for the day. Got around checking out the branch tonight and, ah ah!, it does reproduce the problem here. Now that I can see it first-hand, I'll see what I can do. Thanks!

[jmacdotorg]

Hooray! Glad to know it's not just me. Let me know if I can be of further help.

For what it's worth: the simple workaround that I added to my Catalyst application is to call $c->get_auth_realm('twitter')->credential->twitter_user( undef ); at the end of every request. That clears out that bit of cached information whose presence, I think, is at the heart of the problem, and it doesn't prevent login from occurring as expected. Hope that's helpful info...

[yanick]

I'm fairly sure I've fixed the problem. New version v1.0.0 is on its way to CPAN.

Warning: the function twitter_user now takes $c as an argument, and is stored in the per_user session object rather than globally for the plugin (one of the reason why it could end up being shared).

[jmacdotorg]

Just an FYI that I've updated my in-production Catalyst::Authentication::Credential::Twitter installation and removed my app's workaround code, and everything is running smoothly so far.

Thanks again for attending to this so quickly!

On Mar 9, 2013, at 6:32 PM, Yanick Champoux notifications@github.com wrote:

I'm fairly sure I've fixed the problem. New version v1.0.0 is on its way to CPAN.

Warning: the function twitter_user now takes $c as an argument, and is stored in the per_user session object rather than globally for the plugin (one of the reason why it could end up being shared).

—
Reply to this email directly or view it on GitHub.

Jason McIntosh
Appleseed Software Consulting

jmac@appleseed-sc.com • www.appleseed-sc.com

[yanick]

On 13-03-26 05:25 PM, Jason McIntosh wrote:

Just an FYI that I've updated my in-production
Catalyst::Authentication::Credential::Twitter installation and removed
my app's workaround code, and everything is running smoothly so far.

*victory dance*

Awesome. :-)

Thanks again for attending to this so quickly!

My pleasure. And thanks for helping with the bug hunting.

Joy,
`/anick