#5627 Typo in Stale Session Check - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#5627 ✓stale

Typo in Stale Session Check

Reported by W. Andrew Loe III | September 13th, 2010 @ 07:58 PM | in 2.3.10

This has been fixed before, but it has crept back in to 2-3-stable.

You flagged this item as spam.
W. Andrew Loe III September 13th, 2010 @ 07:59 PM
Previous Ticket: https://rails.lighthouseapp.com/projects/8994/tickets/2404-fix-typo...
Rohit Arondekar September 14th, 2010 @ 04:39 AM
- Milestone set to “2.3.10”
- State changed from “new” to “open”
- Assigned user set to “Santiago Pastorino”
- Importance changed from “” to “Low”
Santiago Pastorino February 2nd, 2011 @ 04:31 PM
This issue has been automatically marked as stale because it has not been commented on for at least three months.

The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
Santiago Pastorino February 2nd, 2011 @ 04:31 PM
- State changed from “open” to “stale”
You flagged this item as spam.
W. Andrew Loe III February 2nd, 2011 @ 06:05 PM
It would be nice to fix this for any forthcoming 2.3 release, but I believe it is already taken care of in the near rewrite of this code that Rails 3 introduced.