Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
230f6910
Commit
230f6910
authored
Jul 27, 2016
by
Stan Hu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add a log message when a project is scheduled for destruction for debugging
parent
17be364d
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
1 deletion
+4
-1
app/models/project.rb
app/models/project.rb
+4
-1
No files found.
app/models/project.rb
View file @
230f6910
...
@@ -1157,7 +1157,10 @@ class Project < ActiveRecord::Base
...
@@ -1157,7 +1157,10 @@ class Project < ActiveRecord::Base
def
schedule_delete!
(
user_id
,
params
)
def
schedule_delete!
(
user_id
,
params
)
# Queue this task for after the commit, so once we mark pending_delete it will run
# Queue this task for after the commit, so once we mark pending_delete it will run
run_after_commit
{
ProjectDestroyWorker
.
perform_async
(
id
,
user_id
,
params
)
}
run_after_commit
do
job_id
=
ProjectDestroyWorker
.
perform_async
(
id
,
user_id
,
params
)
Rails
.
logger
.
info
(
"User
#{
user_id
}
scheduled destruction of project
#{
path_with_namespace
}
with job ID
#{
job_id
}
"
)
end
update_attribute
(
:pending_delete
,
true
)
update_attribute
(
:pending_delete
,
true
)
end
end
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment