tony311 said:
Sure :)
Updated by anonymous
Topic: (OLD) The Bug Report Thread
Posted under Site Bug Reports & Feature Requests
This topic has been locked.
Not sure if this is a bug, or a "feature". But it's a recent issue that's causing problems, so I'm posting it here:
Until recently, if you had an image open in more than one tab/window, and then made tag edits for some reason via both windows, the site would be able to accept all the changes without undoing any of it.
For example, if you're using the "edit Mode" via the thumbnails screen, but you've also opened the image up in a separate tag. You might add the "male" tag via one method, then save it. Then you might click over to the other window where you'd previously opened the image up in full-size to check if that really is a person or an object in the background. Then you'd add the right tag (group/duo/solo whatever) via that screen and save it.
It used to be the site would keep both tags that you added without any problems.
But now it will remove any tag that wasn't already there when you loaded the page. It assumes that if a tag isn't in the tag box that you're editing right now, then you must have intended to remove it from the image. Even if your version of the page is just slightly out-of-date, and you have no way of knowing those tags had ever been added to that image in the meantime. You'll still be credited with removing them in the tag history, and it will remove them from the image when it adds your own tags. It would look for all the world like you were tag vandalising and you probably wouldn't even know the site had done that on your behalf while you were just doing a routine edit. Not good.
Basically if it doesn't recognise the tag as being already there as of the last time the page was refreshed then it assumes you are removing it. Even if it was placed there in the meantime, by yourself in another window or even potentially by another user who was editing tags at the same time as you. That's a mess and not very functional.
It used to be that if the page you'd loaded had fallen out of date, then it assumed you couldn't possibly be trying to remove tags that were added after the page was loaded, so it didn't change any tags or edit tags that were added in the meantime. It would only change or edit tags that were on the version of the page you were editing from. So tags could be edited and added in the meantime, but the site wouldn't try to remove them when you finally finished your tag edit. That worked.
I'm thinking it's a bug, and not an intentional feature. But it's a major problem in the making. Both because it creates false cases of "tag vandalism" with people who are credited with removing tags that they never knew were there when they were editing like normal (because this bug caused some tags to be removed automatically in the background and then credited them with doing it intentionally). And it's also a problem because of all the needless extra work it creates by undoing edits that happened to overlap with each other.
How to replicate it:
1, go to any page of thumbnails.
2, Right click and open any image into a new tab/window. Wait to make sure it's loaded.
3, On the thumbnails page, use the 'Mode' menu to add a tag to that image and then save it.
4, go to the other tab/window with that same image which you'd already loaded previously. Add any other tag to that image via the normal "edit" link, and save it.
5, Look at the tag history. It will credit you as adding tag1, then your second tag edit will be listing you as removing tag1 and adding tag2. Unless you were doing this on purpose, you'd have no idea tag1 was even there and wouldn't realise the site was removing it on your behalf.
Bottom line: it should not be doing this.
ETA: Active Bug (as of sept 11 2014).
Also causes problems especially with newly uploaded posts, where it's more likely two people may be editing the same image simultaneously. For example, person A is editing the tags, person B also starts editing the same tags. Person A saves their edits, everything looks normal. But when person B saves their edits, the site automatically removes person A's edits and replaces them with person B's edits. Because this bug leaves the site unable to accept the changes of both simultaneous edits, and instead defaulting back to a previous version of the tags, it erases any edits which occurred in the meantime by other people. The kicker is that person A and person B have no way of knowing the other person's tags were even added until both have saved and the tag history itemizes their automatic and silent removal by the site because of this bug. It's impossible to even know if it has occurred without checking the tag history and seeing back-to-back edits of person A adding tags, and person B 'removing' all those tags and replacing them with other tags, etc. Potentially this could create false appearance of tag vandalism for the person the site credits for the tags which the bug removed. An example of one time it happened to me and I actually noticed it had happened: https://e621.net/post_tag_history/index?post_id=531121 I've seen it happen a few times though, and even though the tag history looks like a tag war, I'm pretty sure in real life, neither user is even aware of why the tags they just added aren't there moments later and have to be added back again. I know I was confused until I figured out what was happening and why tags I'd never seen were being removed on "my" behalf in the tag history, etc.
It's a messy, silent bug that causes people to needlessly negate each other's tag edits without even knowing about it. It's a bit of a problem.
Still an active bug and issue as of sept 17/18 (depending on time zone of what "now" is, the site is slightly different than my own timezone). Just saw it occur here with editing a recently uploaded image's tags: https://e621.net/post_tag_history/index?post_id=535265 Someone else added two tags while I was adding one. Site removed their tags while adding mine, refusing to consider simultaneous edits as both being valid. It's a problem.
Updated by anonymous
The possible bug I'm reporting is that if you change your username three or more times, your previous usernames are not in order. Example: My first username was titled "Hatr." Then it was changed to "Arcaninetales." Then finally "TheClassyDoge." If that is the case, then the order of the names would be Hatr -> Arcaninetales -> TheClassyDoge. But the system reads it as Arcaninetales -> Hatr -> TheClassyDoge. The system shouldn't be reading it like that.
Updated by anonymous
Bug
Can't remove "~reio" tag from post #516811
Expected behavior
You should be able to remove it
Actual behavior
If I edit post #516811 and replace the "~reio" tag with "reio", e621 keeps the "~reio" tag and adds "reio".
If I edit post #516811 and remove the "~reio" tag completely, e621 doesn't delete it.
Steps to duplicate
See above.
Updated by anonymous
TheClassyDoge said:
The possible bug I'm reporting is that if you change your username three or more times, your previous usernames are not in order. Example: My first username was titled "Hatr." Then it was changed to "Arcaninetales." Then finally "TheClassyDoge." If that is the case, then the order of the names would be Hatr -> Arcaninetales -> TheClassyDoge. But the system reads it as Arcaninetales -> Hatr -> TheClassyDoge. The system shouldn't be reading it like that.
Looks like alphabetical order to me.
Updated by anonymous
Munkelzahn said:
Bug
Can't remove "~reio" tag from post #516811Expected behavior
You should be able to remove itActual behavior
If I edit post #516811 and replace the "~reio" tag with "reio", e621 keeps the "~reio" tag and adds "reio".
If I edit post #516811 and remove the "~reio" tag completely, e621 doesn't delete it.Steps to duplicate
See above.
Even weirder: if you look at the tag history for that image, it doesn't list "~reio" as being on the image anymore. It lists it as having been removed several tag edits ago, but it still lists it in the actual tag list right next to the image as being there. My guess is that's why it won't let anyone remove it: it thinks it's already gone, but didn't completely remove it. The site somehow got confused and sees the tag as being both there and not-there at the same time.
Updated by anonymous
Bug:
Tag aliases occasionally leave behind orphan tags.
For example, boot got aliased to boots recently, but the boot tag is still listed on some posts, such as post #255570. And those show the tag count in negatives..
And since they've been aliased (searching for boot finds everything tagged as boots), it's hard to locate and clean those up manually.
Updated by anonymous
Munkelzahn said:
Bug
Can't remove "~reio" tag from post #516811Expected behavior
You should be able to remove itActual behavior
If I edit post #516811 and replace the "~reio" tag with "reio", e621 keeps the "~reio" tag and adds "reio".
If I edit post #516811 and remove the "~reio" tag completely, e621 doesn't delete it.Steps to duplicate
See above.
I made that tag. Sorry!
I didn't know what to do with the tilde in the artist's username, and I was surprised it got accepted at all. I only used the tilde because I saw other tags existed starting with a tilde.
Updated by anonymous
Comments appearing to strip spaces around punctuation, but not really.
Bug: Comments added to the page by the reply box appear to strip spaces around punctuation. They appear normal upon refreshing/returning to the page.
Expected behavior: New comments show spaces around punctuation.
Actual behavior: They don't
Steps to duplicate: Comment on a page with spaces around a punctuation mark.
Updated by anonymous
Bug: Getting second result page in post search without results
Expected behavior: Pagination lists appropriate number of pages
Actual behavior: Got 2 pages, first was full (as excepted), second showed "No posts matched your search."
Steps to duplicate: https://e621.net/post/index/2/swizz
Updated by anonymous
vaddux said:
Bug: Getting second result page in post search without results
Expected behavior: Pagination lists appropriate number of pages
Actual behavior: Got 2 pages, first was full (as excepted), second showed "No posts matched your search."
Steps to duplicate: https://e621.net/post/index/2/swizz
As far as I know, this happens because there's images under that tag which were deleted. (technically they are still there, but only admins can see them). This allows them to restore them if the reasons change (like an artist requesting their work be taken down but later changes their mind about it). I'm sure it sometimes comes in handy if there's a dispute over something that was deleted, because the admins can still see and discuss it if needed.
Mostly it's unnoticeable to everyone else, but it can mean that the site will say there's more pictures than we can see. So I'm pretty sure that's why it sometimes happens.
Updated by anonymous
furrypickle said:
As far as I know, this happens because there's images under that tag which were deleted. (technically they are still there, but only admins can see them). This allows them to restore them if the reasons change (like an artist requesting their work be taken down but later changes their mind about it). I'm sure it sometimes comes in handy if there's a dispute over something that was deleted, because the admins can still see and discuss it if needed.Mostly it's unnoticeable to everyone else, but it can mean that the site will say there's more pictures than we can see. So I'm pretty sure that's why it sometimes happens.
I once saw a error page with a SQL-Query which contained a status != 'd'. Isn't that the case anymore?
Updated by anonymous
Bug: post #403301 is simultaneously convinced that a tag edit is both there and not at the same time.
Expected behavior: That removing the tag "horse_dildo" and replacing it with "horsecock_dildo" would do exactly that.
Actual behavior: It seems stuck between both. It won't show up as a thumb on the wiki of horse_dildo which makes it look like it's not there. But if you click to view the posts with the tag horse_dildo then it still shows up as there. When you view the image itself, the tag list only has "horse_dildo" listed. Despite numerous attempts to remove "horse_dildo" and add "horsecock_dildo". In the tag history for that image, it lists all the attempts, and when editing in mode or tagscripting it tells me that it successfully changed it, but it never seems to actually do it. If I try to do it directly, I get this error:
ActiveRecord::StatementInvalid in PostController#update
PGError: ERROR: duplicate key value violates unique constraint "posts_tags_post_tag_idx"
DETAIL: Key (post_id, tag_id)=(403301, 209949) already exists.
: INSERT INTO "posts_tags" ("tag_id", "post_id") VALUES(209949, 403301) RETURNING "id"
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08
Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in select_one'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in select_value'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:460:in insert'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2969:in create_without_timestamps'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/timestamp.rb:53:in create_without_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:266:in create'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2935:in create_or_update_without_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:250:in create_or_update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2602:in save_without_validation!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1099:in save_without_dirty!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/dirty.rb:87:in save_without_transactions!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1070:in create!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/reflection.rb:179:in create_association!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in insert_record'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2186:in with_scope'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in insert_record'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:119:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:435:in add_record_to_target_with_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:118:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:116:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:116:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:141:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:140:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:115:in <<'
/home/e621/e621-production/release-2014-06-08/app/models/post/tag_methods.rb:184:in commit_tags'
/home/e621/e621-production/release-2014-06-08/app/models/post/tag_methods.rb:85:in commit_tags'
/home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:259:in update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in select_one'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in select_value'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:460:in insert'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2969:in create_without_timestamps'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/timestamp.rb:53:in create_without_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:266:in create'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2935:in create_or_update_without_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:250:in create_or_update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2602:in save_without_validation!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1099:in save_without_dirty!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/dirty.rb:87:in save_without_transactions!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1070:in create!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/reflection.rb:179:in create_association!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in insert_record'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2186:in with_scope'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in insert_record'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:119:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:435:in add_record_to_target_with_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:118:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:116:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:116:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:141:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:140:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:115:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:188:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in evaluate_method'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:166:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:93:in run'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in run'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:276:in run_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:344:in callback'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:251:in create_or_update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2585:in save_without_validation'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1089:in save_without_dirty'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/dirty.rb:79:in save_without_transactions'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2680:in update_attributes_inside_transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2675:in update_attributes'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/1.8/benchmark.rb:308:in realtime'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:87:in dispatch'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:121:in _call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:130:in build_middleware_stack'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:9:in cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:28:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/head.rb:9:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/methodoverride.rb:24:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/params_parser.rb:15:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/session/cookie_store.rb:99:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/failsafe.rb:26:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in synchronize'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:106:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:47:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:41:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:41:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/rack/thread_handler_extension.rb:61:in process_request'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler/thread_handler.rb:126:in accept_and_process_next_request'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler/thread_handler.rb:94:in main_loop'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:463:in start_threads'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:457:in initialize'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:457
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in select_one'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in select_value'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:460:in insert'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2969:in create_without_timestamps'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/timestamp.rb:53:in create_without_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:266:in create'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2935:in create_or_update_without_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:250:in create_or_update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2602:in save_without_validation!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1099:in save_without_dirty!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/dirty.rb:87:in save_without_transactions!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:200:in save!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1070:in create!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/reflection.rb:179:in create_association!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in insert_record'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2186:in with_scope'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/has_many_through_association.rb:65:in insert_record'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:119:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:435:in add_record_to_target_with_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:118:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:116:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:116:in <<'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:141:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:140:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:115:in <<'
/home/e621/e621-production/release-2014-06-08/app/models/post/tag_methods.rb:184:in commit_tags'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:188:in transaction'
/home/e621/e621-production/release-2014-06-08/app/models/post/tag_methods.rb:85:in commit_tags'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in evaluate_method'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:166:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:93:in run'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in run'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:276:in run_callbacks'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:344:in callback'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:251:in create_or_update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2585:in save_without_validation'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/validations.rb:1089:in save_without_dirty'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/dirty.rb:79:in save_without_transactions'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2680:in update_attributes_inside_transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:2675:in update_attributes'
/home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:259:in update'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/1.8/benchmark.rb:308:in realtime'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:87:in dispatch'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:121:in _call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:130:in build_middleware_stack'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:9:in cache'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:28:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/head.rb:9:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/methodoverride.rb:24:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/params_parser.rb:15:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/session/cookie_store.rb:99:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/failsafe.rb:26:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in synchronize'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/lock.rb:11:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:106:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:47:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:41:in each'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/rack-1.1.6/lib/rack/urlmap.rb:41:in call'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/rack/thread_handler_extension.rb:61:in process_request'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler/thread_handler.rb:126:in accept_and_process_next_request'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler/thread_handler.rb:94:in main_loop'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:463:in start_threads'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:457:in initialize'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/passenger-enterprise-server-4.0.33/lib/phusion_passenger/request_handler.rb:457
Request
Parameters:
{"id"=>"403301",
"post"=>{"hide_google"=>false,
"parent_id"=>"",
"tags"=>"2013 3d anal anal_insertion anal_masturbation anal_penetration anatomically_correct anatomically_correct_penis animal_genitalia animated anus balls big_dildo butt cat cum cum_in_ass cum_in_mouth cum_inside cum_while_penetrated dildo dildo_sitting erection eyes_closed feline feline_penis feral flash fur gay h0rs3 hands-free horsecock_dildo hybrid insertion looking_at_viewer lube male mammal masturbation neck_bulge nude open_mouth oral oral_insertion orgasm panther penetration penis presenting sex_toy shadow shads smile solo the_shadow_of_light tongue tongue_out",
"description"=>"HQ version.",
"hide_anon"=>false,
"is_note_locked"=>"0",
"source"=>"http://www.furaffinity.net/view/12100455/",
"rating"=>"Explicit",
"is_rating_locked"=>"0"},
"reason"=>""}
[/section]
I gave it a day to see if it would sort itself out on its own, but it's just stuck somehow. ETA: oddly enough the tag history for that image only lists me trying to do this twice when I've actually tried at least 6 or 7 times so far without results. It also lists me as putting the tag on AND taking the tag off, when all 6 or 7 times I was taking "horse_dildo" off and adding "horsecock_dildo" on. So I don't know why the tag history is like that.
[b]Steps to duplicate:[/b] Try to remove "horse_dildo" and add "horsecock_dildo" to this image https://e621.net/post/show/403301 and it won't actually do it.
ETA: Something is still buggy but I kind of got it to behave. I finally tried directly editing the image directly plus only removing "horse_dildo" from the post with no other changes. And it finally let me remove "horse_dildo" but then automatically added "horsecock_dildo" to the image before I could edit it again to do that separately. Like it got unstuck and did the rest on its own. It shouldn't have been acting up like that, and the tag history makes absolutely no sense when compared to what it was actually doing. But for the moment it shows the tags it's supposed to, so I guess it's functional again.
Updated by anonymous
Not sure if this has already gone on record (I am not going to scroll through 10 pages to find out :V) Only a minor visual bug.
Bug: Text appearing incorrectly on initial submission.
Expected behavior: When submitting a comment on the forum or an image, your message appears immediately, properly formatted.
Actual behavior: This is a weird one. The comment appears, but it seems like if you include punctuation like a comma or period, the space in front of it gets deleted out. Note these errors do NOT persist on reloading the page. Clearly something is wrong with the AJAX formatting. No one else seems to have mentioned this, so perhaps it's just me? That or no one else has noticed.
Steps to duplicate: Seems to happen on making any comment or response.
Updated by anonymous
elad said:
Bug: Text appearing incorrectly on initial submission.Expected behavior: When submitting a comment on the forum or an image, your message appears immediately, properly formatted.
We're aware of it but can't seem to find the cause :( At least it's only cosmetic and temporary.
Updated by anonymous
hi cannot upload.
Updated by anonymous
I'm currently working on a little project where I need to pick some posts off a few tags. However, e621 doesn't seem to like me very much.
Bug: The "date" tag will often cause a statement timeout.
Expected behavior: Return a list of images created at the given date.
Actual behavior: Statement timeout like shown in this screenshot
Steps to duplicate: Pick a date and add it as a parameter to the search. The process will then eventually fail.
I haven't tried out all tags yet, but a few other tags seem to cause the same issue. (e.g. the "type" tag)
Updated by anonymous
Bj007pro said:
hi cannot upload.http://pastebin.com/V4ipcrFe[/quote]
The flash you're attempting to upload already exists (post #36334).
You put both "wolf" and "species:wolf" as tags onto your upload. First, you don't need to prefix tags that already have their types set. Second, there's a bug currently that will show an error page like the one you saw if you're adding a prefixed tag to a post that already has that tag, or you are adding the same tag twice and at least one of them is prefixed.
BTW, if you're uploading something that's already on the site, the system will try and merge your tags with the existing post's tags.
Updated by anonymous
JackThatBody said:
I'm currently working on a little project where I need to pick some posts off a few tags. However, e621 doesn't seem to like me very much.Bug: The "date" tag will often cause a statement timeout.
Expected behavior: Return a list of images created at the given date.
Actual behavior: Statement timeout like shown in this screenshot
Steps to duplicate: Pick a date and add it as a parameter to the search. The process will then eventually fail.
I haven't tried out all tags yet, but a few other tags seem to cause the same issue. (e.g. the "type" tag)
I'm getting a similar problem as this. However it manifests later in the day, it starts around 10am(10h) PST for me until early in the morning the next day. After that, it run normally. I only use basic parameters. Broader searches (such as searching individual tags) seem to work, though.
Updated by anonymous
Bug
In flag reasons, "post #1234" must be all lower-case
Expected behavior
In this flag reason, the post number should be clickable:
This post was flagged for deletion by ThatPurpleFox. Reason: Smaller version of POst #525479
Actual behavior
It's only clickable if the word "post" is all lower-case
Steps to duplicate
post #525475
Updated by anonymous
AFoxInTheShadows said:
I'm getting a similar problem as this. However it manifests later in the day, it starts around 10am(10h) PST for me until early in the morning the next day. After that, it run normally. I only use basic parameters. Broader searches (such as searching individual tags) seem to work, though.
Can confirm. The searching process seems to slow down in the evening (about 10 pm CET) and stops about one hour after. Next day, it runs normally again.
Edit: One thing I'd like to add is that the API doesn't seem to return the amount of comments on posts when searching for certain tags. I don't know whether this is a "feature" or not, but it's a bit of a shame since it's much much more informative than a boolean stating whether there are comments or not.
Updated by anonymous
Bug: Aliased away tags with minus amounts of posts will only show the first page's worth of results for the tag they've been aliased to. Expected behavior: That an aliased tag would show the same number of results as the tag it was aliased to, regardless if it lists "-30" posts or not on the wiki page for it.Actual behavior: If I go to an aliased-away tag with a minus number of posts, and then click to view the posts, the site will only show me the first page of results for the tag it was aliased to. It looks like theres only one page's worth, even if the tag it's aliased to is actually over 8000 posts. If I go to the normal tag it was aliased to, the first page of results will be identical, except that it will actually list the other pages at the bottom of the screen and allow me to access them. Steps to duplicate: https://e621.net/wiki/show?title=half_nude is aliased to half-dressed. But half_nude lists (-30) posts while half-dressed lists (8965) posts. I assumed this was a minor cosmetic glitch, but if I click that button to view all the posts under that tag, then half_nude will only show me the first page's worth of results, no other pages. While half-dressed will show me 29 pages of results. compare:https://e621.net/post?tags=half_nude --look at the bottom of the page, no other pages listed or accessible.https://e621.net/post?tags=half-dressed -- look at the bottom of the page, 29 pages accessible (more if you have a different setting for how many thumbs are shown per page)
They should be showing me the same results, but it's not. The same is true of speech_balloon showing a minus # of posts and only the first page of results when viewed, even though the tag it's aliased to speech_bubble shows more than one page of results. Again, they should be showing the same number of results no matter which tag you're accessing it from. Seems like a bug.
ETA: Fixed. Thanks!
Updated by anonymous
Bug: Editing tags via the "mode" menu > "Edit Posts" tool that's on pages of thumbnails is not working. Right now, the only reliable way to edit the tags of an image and make sure it actually does it, is to edit the image directly (ie. loading the image in a window, using the "edit" button on that page, editing the tags, and then clicking save so it can reload the page with the new tags. Note: Now that tag scripting is fixed, some types of editing can be done that way, and not just the long way around. But tag scripting is best for certain situations and not others. We still need both of these tagging tools to be functioning in order to edit things effectively on a large scale. One is fixed; one still needs fixing. Expected behavior: That both of the editing tools under the "Mode" menu on thumbnail pages would work reliably, and actually make every edit being attempted through those tools.Actual behavior: Using tag scripting, it will give the green bar notification that the edit was saved, but if you open that image up in a new screen, 9/10 times that image will not have the tag you tried to add. It won't even list you in the tag history as having ever edited the image. If you try to use the Mode option "edit posts", then it won't even give you the green notification bar, just radio silence, like you didn't just try to edit it at all. And again, if you open the image you just tried to edit into new window, you'll see that it won't have the edit you made or any record that you tried. Earlier today it would save only a random percentage of the edits you tried to make, and would sometimes create empty tag history entries on some of the ones it didn't actually save. So it appears to have gotten worse.
There's no sign of page errors at the same time, so it's not as if it's having troubles connecting to the site or server. It's just broken. Right now the only reliable way to edit an image is through loading the image individually into a window, and using the edit button in the "Options" menu or under the image itself. This obviously slows down the ability to tag, especially large tag projects.
Steps to duplicate: View any page of thumbs. Using the "Mode" menu of tools under the search bar, try to use the "edit posts" option, then double-check by opening that image you tried to edit into a new window and see if the tag you "added" is actually in the tag list now like it should be. In my experience, it's not doing it most times that it's attempted, and may not even show the green feedback notifications bar to even say it's trying to do it.
Next, try to make any edits via tag scripting. Right now it seems to give the green notifications bar as if it's working fine. But if you double-check the image, the edits will often not actually have been made. Earlier today, it would work successfully for a few images in a row, and then randomly not be working for the rest. So only a low percentage of edits would actually complete like they said it did. Right now I'm not sure it's actually processing any of them, or if it is, the success rate is much lower than earlier today, like maybe 1 our of 10 images edited this way would actually have done the edit it said it "finished".
ETA: Directly editing an image doesn't always work right either. Trying directly edit this image https://e621.net/post/show/64296 to remove "paula_abdul_-_straight_up" tag from the tag list doesn't work. I've tried twice at least. Tag history lists two times, and says the tag should be gone. But in the actual tag list it's still there. So apparently there's a couple things borked with tag editing right now. And that's kind of a big deal. =/ - Fixed.
ETA:
Tag Scripting is Fixed. Thanks!
the other mode menu editing tool, 'Edit Posts' is fixed now. Thank you!
Updated by anonymous
The tagging system is not picking up dashes. I uploaded two pics by artists with dashes in their names, Seth-Iova and Flynx-Flink, but when the pics were uploaded it read as sethiova and flynxflink. Even when I clicked edit and re-added the dash, it wouldn't work. Even putting Leosaeta instead of Seth-Iova didn't work, it still wouldn't change from sethiova.
Updated by anonymous
Pokelova said:
The tagging system is not picking up dashes. I uploaded two pics by artists with dashes in their names, Seth-Iova and Flynx-Flink, but when the pics were uploaded it read as sethiova and flynxflink. Even when I clicked edit and re-added the dash, it wouldn't work. Even putting Leosaeta instead of Seth-Iova didn't work, it still wouldn't change from sethiova.
I'm having the same problem as well when changing yusts to yus-ts from post #526947.
The tag history has it as yus-ts, but the tag on the left is yusts.
Updated by anonymous
I'm not sure if this is related to the previous reports, but tag scripting seems to have stopped working.
Example: I'm using a tag script 'anthro nipples', but applying it to the posts doesn't do anything. It still says "posts updated", but nothing else happens. No changes to the tags, and nothing shows up in the tag history.
(I wish I had noticed that sooner, by the way...)
Updated by anonymous
Pokelova said:
The tagging system is not picking up dashes. I uploaded two pics by artists with dashes in their names, Seth-Iova and Flynx-Flink, but when the pics were uploaded it read as sethiova and flynxflink. Even when I clicked edit and re-added the dash, it wouldn't work. Even putting Leosaeta instead of Seth-Iova didn't work, it still wouldn't change from sethiova.
I'm experiencing the same problems as well.
Updated by anonymous
The Edit Post option in the Mode selection isn't updating posts. Anyone else having problems?
Updated by anonymous
The dash problem and the tag script problem have been fixed and should be pushed live today (hopefully soon).
Updated by anonymous
tony311 said:
The dash problem and the tag script problem have been fixed and should be pushed live today (hopefully soon).
It's working now, thank you.
Updated by anonymous
This is regarding e926 so I don't know if I should post it here, but there it goes:
Bug: Explicit and questionable thumbs still appears in the e926 forum
Expected behavior: Just like explicit or questionable avatars, explicit thumbs should not appear in e926
Actual behavior: They appear
Steps to duplicate: Go to this link: https://e926.net/forum/show/136698 and see the explicit thumbs I posted via e926.
Sometimes I like to use e926 to see my messages and reply in forum during my work ours (just like I'm doiing now) and this could make it dangerous to do it.
Updated by anonymous
Bug: Can't unfav updated verions of posts from post show page.
Expected behavior: -fav visible, +fav hidden.
Actual behavior: +fav visible, clicking on it results with error "You have already faved this post", -fav hidden.
Steps to duplicate:
1. Fav a post.
2. Wait until updated/bigger version of post appears and till old one gets flagged and deleted.(favs goes to new one).
3. Show this new post.
It seems to happen only on my Android device's default browser.
Updated by anonymous
tony311 said:
The dash problem and the tag script problem have been fixed and should be pushed live today (hopefully soon).
Well the dash problem is fixed. (Thanks!)
But tag scripting AND editing posts in thumbnail "Mode" menu both are still not working. Not sure if the fix you mentioned was only partway made live (because the dashes issue is fixed now) but maybe the other stuff is still pending? Or if the fix didn't completely work yet and so you need to know this sort of feedback that it's not out of the woods yet...? All fixed.
ETA:
dash problem is fixed
tag scripting is fixed
'Mode' menu > 'Edit Posts' tool is fixed now, thanks!
Updated by anonymous
I can't set character tags. https://e621.net/post/show/527349/ The edna_krabapple tag should be a character tag, but everytime I put in character:edna_krabapple, it defaults as edna_krabapple_(character).
Updated by anonymous
JoeX said:
I can't set character tags. https://e621.net/post/show/527349/ The edna_krabapple tag should be a character tag, but everytime I put in character:edna_krabapple, it defaults as edna_krabapple_(character).
I've noticed that. I think it's meant to be a feature. But maybe it should have been discussed first, because it's causing a lot of problems with tagging categories and I don't think the one benefit it gives outweighs the problems it causes. With all due respect, maybe it sounded like a "sure thing" on paper, but it's not really ideal in practice. There's at least 4 incompatibilities with tagging that it causes. Thankfully there's a workaround or else I wouldn't be able to get category tagging done properly anymore. I'll PM it to you.
Some things are better off not being automated... =(
Updated by anonymous
furrypickle said:
I've noticed that. I think it's meant to be a feature. But maybe it should have been discussed first, because it's causing a lot of problems with tagging categories and I don't think the one benefit it gives outweighs the problems it causes. With all due respect, maybe it sounded like a "sure thing" on paper, but it's not really ideal in practice. There's at least 4 incompatibilities with tagging that it causes. Thankfully there's a workaround or else I wouldn't be able to get category tagging done properly anymore. I'll PM it to you.Some things are better off not being automated... =(
Actually, Krabapple isn't the correct spelling. The correct spelling is Krabappel.
Updated by anonymous
JoeX said:
I can't set character tags. https://e621.net/post/show/527349/ The edna_krabapple tag should be a character tag, but everytime I put in character:edna_krabapple, it defaults as edna_krabapple_(character).
It's something we switched to to see how well it works. Now when you use the type prefixes, it'll create a new tag with a type suffix if the tag already exists. This will prevent people accidentally changing the type of an existing tag when adding an artist tag or whatever (like tagging artist:carrot and accidentally changing carrot to an artist tag, when carrot_(artist) already exists).
If you need to change the type of a tag you can still do so through the tag index, but the feature was pushed a bit prematurely and that's still unavailable to members at the moment.
Updated by anonymous
Naydian said:
Bug: Can't unfav updated verions of posts from post show page.
Expected behavior: -fav visible, +fav hidden.
Actual behavior: +fav visible, clicking on it results with error "You have already faved t/his post", -fav hidden.
Steps to duplicate:
1. Fav a post.
2. Wait until updated/bigger version of post appears and till old one gets flagged and deleted.(favs goes to new one).
3. Show this new post.It seems to happen only on my Android device's default browser.
I didn't noticed it before, but this bug is on all favs.
Steps to duplicate:
1. Fav a post.
2. Reload page.
Can't duplicate on Chrome, there it works correctly.
Updated by anonymous
Naydian said:
It seems to happen only on my Android device's default browser.I didn't noticed it before, but this bug is on all favs.
Steps to duplicate:
1. Fav a post.
2. Reload page.Can't duplicate on Chrome, there it works correctly.
I used to have that problem. It's caused by JavaScript randomly crashing on the android default browser. When my device updated to version 4.4, the problem went away.
Updated by anonymous
For the tag history of post #527317, why the feline and mammal tags was added after I did a tag edit on it? When the tiger tag is used, is it supposed to be added automatically?
Also, why is interspecies listed twice in the tag history of post #528205?
Updated by anonymous
Mienshao said:
For the tag history of post #527317, why the feline and mammal tags was added after I did a tag edit on it? When the tiger tag is used, is it supposed to be added automatically?
That' what implications are for. If a tag implies another, that one will be automatically added. Like in this case, tiger implies feline, witch implies mammal. And as such, both got automatically added to the post.
Also, why is interspecies listed twice in the tag history of post #528205?
That's weird, though...
Seems like the system went haywire for some time and it caused tagging anomalies, like this tag showing up twice, or tags showing up with uppercase letters in them, or implications not being properly resolved. All of these can be seen in the tag histories you linked.
Updated by anonymous
And to add to what EsalRider said; thanks to the implications, you usually never have to add tags like feline or mammal manually. Just tag the top level and the rest will get implicated.
Mienshao said:
Also, why is interspecies listed twice in the tag history of post #528205?
That's a recent change. Those used to be pruned, but now... if you accidentally use the same tag twice (or more), it gets listed multiple times in the tag history.
Happens to me all the time, since I use macro shortcuts to tag. And often end up with combos that have dupes.
Updated by anonymous
EsalRider said:
That' what implications are for. If a tag implies another, that one will be automatically added. Like in this case, tiger implies feline, witch implies mammal. And as such, both got automatically added to the post.
Why would it be added to my edit? Numeroth added the tiger tag, the tags should have been added with his edit, not mine.
Updated by anonymous
Mienshao said:
Why would it be added to my edit? Numeroth added the tiger tag, the tags should have been added with his edit, not mine.
Huh. Now that's odd.
...all implications seem to get credited to the next tagger, unless the first tagger adds all implicated tags themselves. (ie. 'tiger feline mammal', instead of just 'tiger')
No wonder the tag history has seemed so messy recently. Definitely looks like a bug.
Updated by anonymous
Another tagging-related bug:
I just added a of tags to post #527173, and somehow it ended up tagged with clothed. Even though I'm certain that I didn't add it myself.
vvv Yep, I didn't notice that it was tagged as skimpy. It let me untag clothed (implied tag) without untagging skimpy, which shouldn't be possible.
Updated by anonymous
Genjar said:
Another tagging-related bug:
I just added a couple of tags to post #527173, and somehow it ended up tagged with clothed. Even though I'm certain that I didn't add it myself.
I'm pretty sure the clothed/clothing came from the skimpy tag. So that's what was implying it. But the pattern of system behavior based on what tags were there vs what the system did with it doesn't make sense:
The uploader added skimpy, which in turn added clothed and then clothing. Mistaken tag but so far the implication system seems to be functioning correctly.
But then it gets weird. Another user removed clothed and clothing, but overlooked skimpy...so nothing should have changed. However, the system successfully removed clothed and clothing until the next edit of the image's tags. Which was yours. Then it seemed to realise it needed to re-apply the implication and it re-added the tags clothed and clothing at the same time it applied your edit, crediting you with it. Which is nonsense. I removed skimpy and clothed and clothing and bulge. In the meantime you'd also removed clothing and clothed again. But if I'd only removed bulge, then it probably would have credited me with re-applying the implicated tags of clothed and clothing again. It's totally a bug.
Updated by anonymous
I have a feeling that post updating steps are executed in the wrong order. Like implications (and maybe aliases; haven't tested) are resolved before applying any changes. This way, if a tag was added that implied something, the implied tags would only be added on the next tag edit. The same applies to removing tags that are implied by other tags on the post; they won't show up again until another tag edit.
Edit: Problem seems to be partially solved.
https://e621.net/post_tag_history/index?post_id=301211
I removed mammal and canine, but not fox. Result: The tag history says that I removed them, yet the tags are still present on the image, without any further editing. So... Implications are now properly resolved, but the tag history is compiled early. I guess...
Updated by anonymous
From the changelog:
Fixed tag scripts not working (was applied a few days ago)
You might want to recheck that. They're still broken, as far as I can see. (Same as before: scripting doesn't actually add the tag.)
Updated by anonymous
tony311 said:
It's something we switched to to see how well it works.
As expected, it's not working.
There's already several *_(artist)_(artist) tags: https://e621.net/tag?name=*_%28*%29_%28*%29&type=&order=count&show_empty_tags=1
And same goes for other categories.
The worst I've seen so far is kiila_(dragonofdarkness1992)_(character)_(character), and the feature has only been live for a couple of days.
Any way to make it check for existing brackets, before adding more?
Updated by anonymous
Genjar said:
From the changelog:
You might want to recheck that. They're still broken, as far as I can see. (Same as before: scripting doesn't actually add the tag.)
As far as I can tell it does work. Try loading up https://e621.net/javascripts/application-min.js and searching for old_tags. If it returns something that looks like
Post.update(post_id,{"post[old_tags]":old_tags,"post[tags]":post.tags.join(" ")})}}
then you're still being served an outdated version of the file. If the only result you get for old_tags is
$("post_old_tags").value=post.tags.join(" ")
then you've got the new version. Also try using a tag script after you've loaded up the JS since that may have forced it to update.
Genjar said:
As expected, it's not working.
There's already several *_(artist)_(artist) tags: https://e621.net/tag?name=*_%28*%29_%28*%29&type=&order=count&show_empty_tags=1And same goes for other categories.
The worst I've seen so far is kiila_(dragonofdarkness1992)_(character)_(character), and the feature has only been live for a couple of days.
Any way to make it check for existing brackets, before adding more?
spight was aware of the problem but I'll pass it on to him in case he still needs to work out some kinks or something.
Updated by anonymous
tony311 said:
[about tag scripting]
For me, tag scripting has been working for a few days now. (thanks by the way!)
But I'm still waiting for the "Edit Tags" Mode through the same menu to be fixed. It stopped working around the same time tag scripting did, but so far it hasn't been fixed yet. I was wondering if this was oversight (like it got overlooked since tag scripting might have been a higher priority) or if it's just proving trickier to fix? Fixed. Thanks!
Updated by anonymous
tony311 said:
As far as I can tell it does work. Try loading up https://e621.net/javascripts/application-min.js and searching for old_tags. If it returns something that looks likePost.update(post_id,{"post[old_tags]":old_tags,"post[tags]":post.tags.join(" ")})}}then you're still being served an outdated version of the file. If the only result you get for old_tags is
$("post_old_tags").value=post.tags.join(" ")then you've got the new version. Also try using a tag script after you've loaded up the JS since that may have forced it to update.
Yep, that did it. I'm not sure why, but looks like I was still using the old version. Cleared Chrome's cache and it seems to work fine now. ...I should've tried that before reporting it, my bad.
Updated by anonymous
Genjar said:
As expected, it's not working.
There's already several *_(artist)_(artist) tags: https://e621.net/tag?name=*_%28*%29_%28*%29&type=&order=count&show_empty_tags=1And same goes for other categories.
The worst I've seen so far is kiila_(dragonofdarkness1992)_(character)_(character), and the feature has only been live for a couple of days.
Any way to make it check for existing brackets, before adding more?
It does. In every case I've found, these issues have been caused by tags with a type-specific suffix with the wrong type.
Examples:
https://e621.net/tag?name=diodki666*&type=&order=count&show_empty_tags=1
https://e621.net/tag?name=sierra11744_*&type=&order=count&show_empty_tags=1
https://e621.net/tag?name=kiila*&type=&order=count&show_empty_tags=1
We're working to find a solution to help users who mistakenly set these tags to the wrong type in the first place, which is the underlying issue, but being able to edit a tag in the previous manner was causing similar problems without making them obvious enough to fix.
Updated by anonymous
Found a bug. When searching users in the listing should you happen to enter 1 it will instead enter !, 2 will replace it with @, so on so forth with each number being replaced with a symbol.
Updated by anonymous
Esme_Belles said:
Found a bug. When searching users in the listing should you happen to enter 1 it will instead enter !, 2 will replace it with @, so on so forth with each number being replaced with a symbol.
You sure you're not touching the shift key?
Updated by anonymous
Xch3l said:
You sure you're not touching the shift key?
This can also be due to Sticky Keys, where pressing Shift toggles it on, or Shift Lock, which does what it says. I can usually get out of Shift Lock by mashing the keys ctrl, alt, shift in combos.
Updated by anonymous
Xch3l said:
You sure you're not touching the shift key?
Using a kindle, so, yes.
Updated by anonymous
Huh, I swear I replied to Savageorange... :/
It was something about that annoyance...
Esme_Belles said:
Using a kindle, so, yes.
So, you're not using a computer then, right? Erm... I dunno how does that work...
Updated by anonymous
So, I'm not sure if it's still a bug, but the tag prefixes still don't work. I would assume it's a bug, because it's not showing up in the site changelog.
Updated by anonymous
The timestamps on forum posts will randomly change between saying something was posted minutes ago (the accurate time) to saying it was posted 7 hours ago (bafflingly inaccurate).
If you refresh five or so times on the main page of the forum, you can watch the timestamps jump from saying something was only posted 45 minutes ago, to saying it was posted 2, 3, 5, or 7 hours ago, (jumping between older and then younger timestamps), back and forth, in under a minute's worth of refreshes. Using ctrl+F5 doesn't seem to make a difference, if anything it makes it change more often. Almost like it changes the data every time it accesses the page.
It's also happening with comments on uploads sometimes shown as occurring hours before the picture was even uploaded to comment on. Which is funny, but not useful.
Why this is a problem:
For the forum, this bug screws up the italics notification when there's a new post in the forum or not. And even when looking at the forum page it's hard to tell whether a thread had a new post on it or not when it sometimes lists it as last updated 7 hours ago but in reality that post was added to only an hour ago. And it can screw up it's ability to remember the "mark all posts as read" setting since it can't remember what time that post occurred anyways. It's also confusing to read a thread when you see the last post being listed as several hours older than the two posts above it on a thread.
ETA: Fixed!
Updated by anonymous
Theme keeps changing to Spring again.
Updated by anonymous
furballs_dc said:
Theme keeps changing to Spring again.
Yeah, this is happening for me too.
pls make it stahp
Updated by anonymous
Bug: Timestamps on forums are scrambled
Expected behavior: Unscrambled timestamps? How to put it... well, that. Read next line
Actual behavior: This. I just posted on forum #66904 and it says I did 7 hours ago
Steps to duplicate: No need to! Just look at the forums...
Edit: Dangit! Times corrected themselves... but there's still proof that times were wrong
Updated by anonymous
Xch3l said:
Bug: Timestamps on forums are scrambled
Not only them. Comments and posting times are affected too.
Updated by anonymous
Ryuzaki_Izawa said:
Yeah, this is happening for me too.pls make it stahp
Thirded. Also, finding that spaces in some of my posts are being unrecognized- I space my sentences right, but when it posts, all the sentences are cramped together- no spaces after periods, for example. If I try to edit the post, the space is actually there, however, meaning in those cases I have to put two or more spaces to get a single space to "stick".
Updated by anonymous
I have captured an example of this timestamp glitch.
Updated by anonymous
Bug: Shit's on fire, yo.
Image: http://i.imgur.com/1DZWHKM.png
What made the bug occur: entered -female into the search box, with no other tags.
Updated by anonymous
Something's wrong with the forum clock. I just posted in thread #137609, and it says that it was posted seven hours ago...
Updated by anonymous
Seems like this timestamp bug is bugging quite a few people. I noticed it earlier as well, but it was only fluctuating a few minutes, not 7 hours.
123easy said:
Also, finding that spaces in some of my posts are being unrecognized- I space my sentences right, but when it posts, all the sentences are cramped together- no spaces after periods, for example. If I try to edit the post, the space is actually there, however, meaning in those cases I have to put two or more spaces to get a single space to "stick".
This is a known bug, but only cosmetic. Nobody really knows just what is causing it, but you don't really have to worry about it. Since it only occures when the posted comment/forum post/whatever appears after submitting, you're the only one to see it like that. Any other time it will show up just as intended, without having to do anything. If your posts show up with spaces missing from here and there, just refresh.
Updated by anonymous
Just a thought, isn't the thousand separator screwing up dates or times?
Updated by anonymous
Bug: intermittent "Nobody here but us chickens!" error pages when doing any search that contains tag types for file format (i.e. type:jpg , type:png type:gif type:swf type:webm [/s]etc)Expected behavior: "That Nobody here but us chickens"/bad link/nonexistant page errors would not occur for valid pages, ever. Actual behavior: Intermittent "nobody here but us chickens"/bad link etc page error shows up a percentage of the time any search with file types is performed. Error might persist for one or more refreshes, but eventually refreshes will make it work like it's supposed to. Steps to duplicate: Perform a search with one of the tag type codes for file formats listed above. Or click here: animated type:gif . The initial page load is often the "nobody here but us chickens" error page. But if you refresh 1 to 5 times, it will actually work and complete the search without apparent issues. URL seems to stay the same both when it's claiming bad link and when it finally works again. Possibly related: There does seem to be a lot of scattered "website under heavy load" errors the last few hours. Even though the two don't seem connected and this isn't the type of error normally generated by a heavy load, just fyi in case it factors in somehow. Note, doesn't seem affected or related to heavy-load messages, etc. Happens equally when the site is running fast and without issues. ETA: Seems to be fixed now. Thanks! (If it still occurs it's at a much lower rate because testing it now doesn't seem to show the error over several tries.)
Updated by anonymous
So uh, for some reason it says that Huskyk9 have tagged about 30 pages worth of posts with the invalid_tag tag.
Updated by anonymous
Peekaboo said:
So uh, for some reason it says that Huskyk9 have tagged about 30 pages worth of posts with the invalid_tag tag.
That's probably due to all these tag aliases that he approved not too long ago: https://e621.net/mod_action?moderator=&body=invalid_tag&type=any
He tried to use our mass tag edit tool to clear all those out, but the jobs are stuck currently: https://e621.net/job_task
I've already alerted the devs about it. Once they finally prod the job queue to get it to run job tasks again, all those invalid_tags will disappear.
Updated by anonymous
Char said:
That's probably due to all these tag aliases that he approved not too long ago: https://e621.net/mod_action?moderator=&body=invalid_tag&type=anyHe tried use our mass tag edit tool to clear all those out, but the jobs are stuck currently: https://e621.net/job_task
I've already alerted the devs about it. Once they finally prod the job queue to get it to run job tasks again, all those invalid_tags will disappear.
Ah, goodie.
Thanks for the fast response.
Updated by anonymous