|
1
|
.
|
|
2
|
(snip)
|
|
3
|
.
|
|
4
|
== 62 InsertBuiltinRoles: migrating ===========================================
|
|
5
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
6
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
7
|
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
|
|
8
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
|
|
9
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
|
|
10
|
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
|
|
11
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
|
|
12
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
|
|
13
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
14
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
15
|
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
|
|
16
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
|
|
17
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from block in position_scope_was at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:57)
|
|
18
|
DEPRECATION WARNING: The behavior of `attribute_was` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `attribute_before_last_save` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
|
|
19
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
|
|
20
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from remove_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:92)
|
|
21
|
== 62 InsertBuiltinRoles: migrated (0.0861s) ==================================
|
|
22
|
.
|
|
23
|
(snip)
|
|
24
|
.
|
|
25
|
== 20091114105931 AddViewIssuesPermission: migrating ==========================
|
|
26
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
27
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
28
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
|
|
29
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
30
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
31
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
|
|
32
|
== 20091114105931 AddViewIssuesPermission: migrated (0.0245s) =================
|
|
33
|
.
|
|
34
|
(snip)
|
|
35
|
.
|
|
36
|
== 20170418090031 AddViewNewsToAllExistingRoles: migrating ====================
|
|
37
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
38
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
39
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
|
|
40
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
41
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
42
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
|
|
43
|
== 20170418090031 AddViewNewsToAllExistingRoles: migrated (0.0126s) ===========
|
|
44
|
|
|
45
|
== 20170419144536 AddViewMessagesToAllExistingRoles: migrating ================
|
|
46
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
47
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
48
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
|
|
49
|
DEPRECATION WARNING: The behavior of `changed` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.keys` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
50
|
DEPRECATION WARNING: The behavior of `changed_attributes` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_changes.transform_values(&:first)` instead. (called from position_scope_changed? at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:96)
|
|
51
|
DEPRECATION WARNING: The behavior of `attribute_changed?` inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after `save` returned (e.g. the opposite of what it returns now). To maintain the current behavior, use `saved_change_to_attribute?` instead. (called from update_position at /Users/maeda/redmines/rails-5.1/lib/redmine/acts/positioned.rb:78)
|
|
52
|
== 20170419144536 AddViewMessagesToAllExistingRoles: migrated (0.0112s) =======
|