dice/impress
1
0
Fork 0
forked from OpenNeo/impress
Code Pull requests Activity
impress/Gemfile.lock

325 lines
7.5 KiB
Text
Raw Normal View History

support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/eventmachine/eventmachine.git
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
revision: d7c8a14dc494193a775add4b16c1e303cab5b285
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
eventmachine (1.0.0)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
infer locale from params, then cookies, then Accept-Language header
2013-01-11 09:07:11 -08:00
GIT
remote: git://github.com/iain/http_accept_language.git
revision: 7738e45ba154015597fca749b7d0257861c14a02
specs:
http_accept_language (2.0.0.pre)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/igrigorik/em-http-request.git
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
revision: 322f2273fa7ea07c1eeb92755bf67f1f05058e54
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
em-http-request (1.0.3)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
addressable (>= 2.2.3)
cookiejar
em-socksify
eventmachine (>= 1.0.0.beta.4)
http_parser.rb (>= 0.5.3)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/igrigorik/em-mysqlplus.git
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
revision: 11d6e1123654b948c1d0a8c9d9077e82420b2846
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
em-mysqlplus (0.1.5)
eventmachine (>= 0.12.9)
GIT
remote: git://github.com/igrigorik/em-synchrony.git
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
revision: fe592a4b9b5345bca329477cb8f2f8d186b6fc7f
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
em-synchrony (1.0.2)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
eventmachine (>= 1.0.0.beta.1)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
oops: use public git uri for flex gem
2013-01-26 21:48:59 -08:00
GIT
remote: git://github.com/matchu/flex.git
revision: d62f508f795ecdbb383f406865daa72368b43ba5
specs:
flex (0.4.1)
multi_json (~> 1.3.4)
progressbar (~> 0.11.0)
prompter (~> 0.1.5)
cut down on pets#load queries
2013-01-28 00:10:25 -08:00
GIT
remote: git://github.com/matchu/globalize3.git
waaay speed up Pet#translate_items A few key changes: * Don't reload the whole pet 8 times!! Sooo many bad things happen, including redundant lookups of everything else and too many item saves and reindexes. Instead, fetch the item data, apply it to the items, and then save the items (once each!) * Updated my branch of globalize3 to be even better at avoiding redundant queries when saving. Woo. * Last realization: wrapping all the item saves in a single transaction works wonders. COMMIT seems to have high overhead, so doing only one took it from 50ms * 10 or whatever to 60ms. Good stuff.
2013-01-28 13:18:11 -08:00
revision: e23277864270131bbee29033f8a3abfb74ffe1f8
cut down on pets#load queries
2013-01-28 00:10:25 -08:00
specs:
globalize3 (0.3.0)
activemodel (>= 3.0.0)
activerecord (>= 3.0.0)
paper_trail (~> 2)
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
GIT
remote: git://github.com/matchu/neopets.git
pet states know their localized description
2013-01-31 17:11:15 -08:00
revision: 5d13a720b616ba57fbbd54541f3e5daf02b3fedc
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
specs:
pet states know their localized description
2013-01-31 17:11:15 -08:00
neopets (0.2.0)
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
nokogiri (~> 1.5.2)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/oldmoe/mysqlplus.git
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
revision: f07936d2eb9b0893994ed99fe82267b5e7770d06
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
mysqlplus (0.1.1)
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
GIT
update rocketamf repo
2011-07-31 20:20:04 -07:00
remote: git://github.com/rubyamf/rocketamf.git
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
revision: ed82db7659f624d6c3ca244e4127dad270a484c7
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
specs:
update rocketamf repo
2011-07-31 20:20:04 -07:00
RocketAMF (1.0.0)
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
GEM
remote: http://rubygems.org/
specs:
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
POpen4 (0.1.4)
Platform (>= 0.4.0)
open4
Platform (0.4.0)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
abstract (1.0.0)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
actionmailer (3.0.20)
actionpack (= 3.0.20)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
mail (~> 2.2.19)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
actionpack (3.0.20)
activemodel (= 3.0.20)
activesupport (= 3.0.20)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
builder (~> 2.1.2)
erubis (~> 2.6.6)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
i18n (~> 0.5.0)
rack (~> 1.2.5)
rack-mount (~> 0.6.14)
security update: rails -> 3.0.4
2011-02-08 17:15:06 -08:00
rack-test (~> 0.5.7)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
tzinfo (~> 0.3.23)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
activemodel (3.0.20)
activesupport (= 3.0.20)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
builder (~> 2.1.2)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
i18n (~> 0.5.0)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
activerecord (3.0.20)
activemodel (= 3.0.20)
activesupport (= 3.0.20)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
arel (~> 2.0.10)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
tzinfo (~> 0.3.23)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
activeresource (3.0.20)
activemodel (= 3.0.20)
activesupport (= 3.0.20)
activesupport (3.0.20)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
addressable (2.3.2)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
arel (2.0.10)
bundle update
2011-02-05 19:51:19 -08:00
bcrypt-ruby (2.1.4)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
builder (2.1.2)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
bullet (4.1.6)
remove N+1 queries on current user outfits page
2012-08-09 15:32:33 -07:00
uniform_notifier (~> 1.0.0)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
carrierwave (0.5.8)
activesupport (~> 3.0)
utf-8 support in both ruby 1.9 and 1.8
2011-06-04 15:40:15 -07:00
character-encodings (0.4.1)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
chronic (0.6.7)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
closure-compiler (1.1.8)
bundle update
2011-02-05 19:51:19 -08:00
compass (0.10.6)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
haml (>= 3.0.4)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
cookiejar (0.3.0)
devise (1.1.9)
devise implemented, but not remembering
2011-01-26 10:40:15 -08:00
bcrypt-ruby (~> 2.1.2)
warden (~> 1.0.2)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
diff-lcs (1.1.3)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
dye (0.1.4)
em-socksify (0.2.1)
eventmachine (>= 1.0.0.beta.4)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
erubis (2.6.6)
abstract (>= 1.0.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
excon (0.16.10)
factory_girl (2.6.4)
activesupport (>= 2.3.9)
factory_girl_rails (1.7.0)
factory_girl (~> 2.6.0)
bundle update
2011-02-05 19:51:19 -08:00
railties (>= 3.0.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
fog (1.8.0)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
builder
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
excon (~> 0.14)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
formatador (~> 0.2.0)
mime-types
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
multi_json (~> 1.0)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
net-scp (~> 1.0.4)
net-ssh (>= 2.1.3)
nokogiri (~> 1.5.0)
ruby-hmac
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
formatador (0.2.4)
bundle update
2011-02-05 19:51:19 -08:00
haml (3.0.25)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
hoptoad_notifier (2.4.11)
include hoptoad
2010-11-14 13:06:31 -08:00
activesupport
builder
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
http_parser.rb (0.5.3)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
i18n (0.5.0)
bundle update
2011-02-05 19:51:19 -08:00
jammit (0.5.4)
a functioning wardrobe
2010-10-10 19:18:42 -07:00
closure-compiler (>= 0.1.0)
yui-compressor (>= 0.9.1)
json 1.7.7 security update
2013-02-11 11:03:59 -08:00
json (1.7.7)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
mail (2.2.19)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
activesupport (>= 2.3.6)
bundle update
2011-02-05 19:51:19 -08:00
i18n (>= 0.4.0)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
mime-types (~> 1.16)
treetop (~> 1.4.8)
cache item show pages as a first try :)
2010-12-08 17:15:46 -08:00
memcache-client (1.8.5)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
mime-types (1.19)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
mini_magick (3.4)
subexec (~> 0.2.1)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
msgpack (0.4.7)
multi_json (1.3.7)
mysql2 (0.2.18)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
net-scp (1.0.4)
net-ssh (>= 1.99.1)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
net-ssh (2.6.3)
newrelic_rpm (3.5.5.38)
nokogiri (1.5.6)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
open4 (1.3.0)
bump version on openneo auth signatory to ensure we load the correct version
2010-11-28 17:49:34 -08:00
openneo-auth-signatory (0.1.0)
auth works - yaaay
2010-10-18 14:58:45 -07:00
ruby-hmac
apply globalize3 to items
2013-01-11 14:20:06 -08:00
paper_trail (2.7.0)
activerecord (~> 3.0)
railties (~> 3.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
parallel (0.5.21)
patron (0.4.18)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
polyglot (0.3.3)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
progressbar (0.11.0)
prompter (0.1.5)
dye (>= 0.1.1)
yard (>= 0.6.3)
rack (1.2.7)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
rack-fiber_pool (0.9.2)
rack-mount (0.6.14)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rack (>= 1.0.0)
bundle update
2011-02-05 19:51:19 -08:00
rack-test (0.5.7)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rack (>= 1.0)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
rails (3.0.20)
actionmailer (= 3.0.20)
actionpack (= 3.0.20)
activerecord (= 3.0.20)
activeresource (= 3.0.20)
activesupport (= 3.0.20)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
bundler (~> 1.0)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
railties (= 3.0.20)
add rails-i18n for standard rails api translations
2013-01-30 18:57:32 -08:00
rails-i18n (0.7.2)
i18n (~> 0.5)
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
railties (3.0.20)
actionpack (= 3.0.20)
activesupport (= 3.0.20)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
rake (>= 0.8.7)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
rdoc (~> 3.4)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
thor (~> 0.14.4)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
rake (10.0.3)
bundle update
2011-02-05 19:51:19 -08:00
rdiscount (1.6.8)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
rdoc (3.12)
json (~> 1.4)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
redis (3.0.2)
redis-namespace (1.2.1)
redis (~> 3.0.0)
update resque to see if maybe it fixes the stupid problems
2013-01-28 01:48:53 -08:00
resque (1.23.0)
multi_json (~> 1.0)
redis-namespace (~> 1.0)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
resque-retry (0.1.0)
resque (>= 1.8.0)
resque-scheduler (>= 1.8.0)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
resque-scheduler (2.0.0.e)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
redis (>= 2.0.1)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
resque (>= 1.15.0)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
rufus-scheduler
translate species/color
2013-01-26 08:34:48 -08:00
rest-client (1.6.7)
mime-types (>= 1.16)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
right_aws (2.1.0)
right_http_connection (>= 1.2.5)
right_http_connection (1.3.0)
bundle update
2011-02-05 19:51:19 -08:00
rspec (2.0.1)
rspec-core (~> 2.0.1)
rspec-expectations (~> 2.0.1)
rspec-mocks (~> 2.0.1)
rspec-core (2.0.1)
rspec-expectations (2.0.1)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
diff-lcs (>= 1.1.2)
bundle update
2011-02-05 19:51:19 -08:00
rspec-mocks (2.0.1)
rspec-core (~> 2.0.1)
rspec-expectations (~> 2.0.1)
rspec-rails (2.0.1)
rspec (~> 2.0.0)
auth works - yaaay
2010-10-18 14:58:45 -07:00
ruby-hmac (0.4.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
rufus-scheduler (2.0.17)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
tzinfo (>= 0.3.23)
closet lists, round one
2011-07-29 07:52:04 -07:00
sanitize (2.0.3)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
nokogiri (>= 1.4.4, < 1.6)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
sinatra (1.2.8)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
rack (~> 1.1)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
tilt (>= 1.2.2, < 2.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
subexec (0.2.2)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
swf_converter (0.0.3)
bundle update
2011-02-05 19:51:19 -08:00
thor (0.14.6)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
tilt (1.3.3)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
treetop (1.4.12)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
polyglot
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
polyglot (>= 0.3.1)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
tzinfo (0.3.35)
remove N+1 queries on current user outfits page
2012-08-09 15:32:33 -07:00
uniform_notifier (1.0.2)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
vegas (0.1.11)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
rack (>= 1.0.0)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
warden (1.0.6)
rack (>= 1.0)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
whenever (0.7.3)
cron via whenever for mall spider
2010-11-27 15:59:35 -08:00
activesupport (>= 2.3.4)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
chronic (~> 0.6.3)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
will_paginate (3.0.4)
yard (0.8.3)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
yui-compressor (0.9.6)
POpen4 (>= 0.1.4)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
PLATFORMS
ruby
DEPENDENCIES
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
RocketAMF!
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
addressable
remove N+1 queries on current user outfits page
2012-08-09 15:32:33 -07:00
bullet (~> 4.1.5)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
carrierwave (~> 0.5.8)
utf-8 support in both ruby 1.9 and 1.8
2011-06-04 15:40:15 -07:00
character-encodings (~> 0.4.1)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
compass (~> 0.10.1)
devise implemented, but not remembering
2011-01-26 10:40:15 -08:00
devise (~> 1.1.5)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
em-http-request!
em-mysqlplus!
em-synchrony!
eventmachine!
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
factory_girl_rails (~> 1.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
flex!
fog (~> 1.8.0)
cut down on pets#load queries
2013-01-28 00:10:25 -08:00
globalize3!
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
haml (~> 3.0.18)
include hoptoad
2010-11-14 13:06:31 -08:00
hoptoad_notifier
infer locale from params, then cookies, then Accept-Language header
2013-01-11 09:07:11 -08:00
http_accept_language!
a functioning wardrobe
2010-10-10 19:18:42 -07:00
jammit (~> 0.5.3)
json 1.7.7 security update
2013-02-11 11:03:59 -08:00
json (~> 1.7.7)
cache item show pages as a first try :)
2010-12-08 17:15:46 -08:00
memcache-client (~> 1.8.5)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
mini_magick (~> 3.4)
auth works - yaaay
2010-10-18 14:58:45 -07:00
msgpack (~> 0.4.3)
downgrade mysql2, oops
2012-01-12 18:31:50 -08:00
mysql2 (< 0.3)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
mysqlplus!
pet states know their localized description
2013-01-31 17:11:15 -08:00
neopets (~> 0.2.0)!
new relic
2012-04-08 14:37:32 -07:00
newrelic_rpm
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
nokogiri (~> 1.5.2)
bump version on openneo auth signatory to ensure we load the correct version
2010-11-28 17:49:34 -08:00
openneo-auth-signatory (~> 0.1.0)
optimize outfit image generation - 4x speed boost on my box Use the ImageMagick flatten command to generate the output all at once instead of compositing each layer individually, and download the layers in parallel. On my box, saving roopal27 five times took a total of 30 seconds before, whereas now it takes 7 seconds. I expect it to be even better on the production box, where latency is even lower.
2012-07-27 20:07:20 -07:00
parallel (~> 0.5.17)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
patron (~> 0.4.18)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
rack-fiber_pool
security update: rails 3.0.20
2013-01-28 13:34:44 -08:00
rails (= 3.0.20)
add rails-i18n for standard rails api translations
2013-01-30 18:57:32 -08:00
rails-i18n
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rdiscount (~> 1.6.5)
update resque to see if maybe it fixes the stupid problems
2013-01-28 01:48:53 -08:00
resque (~> 1.23.0)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
resque-retry (~> 0.1.0)
use dev version of resque-scheduler so we can use its pidfile option
2011-06-21 08:54:32 -07:00
resque-scheduler (~> 2.0.0.d)
translate species/color
2013-01-26 08:34:48 -08:00
rest-client (~> 1.6.7)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
right_aws (~> 2.1.0)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rspec-rails (~> 2.0.0.beta.22)
closet lists, round one
2011-07-29 07:52:04 -07:00
sanitize (~> 2.0.3)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
swf_converter (~> 0.0.3)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
whenever (~> 0.7.3)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
will_paginate (~> 3.0.pre2)
Copy permalink