util
/
rq
mirror of https://github.com/peter4431/rq.git
4
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,395 Commits
2 Branches
0 Tags
3.3 MiB
main
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '51efc20371'
${ noResults }
Commit Graph

1395 Commits (51efc203713958e1f0a0ae774c9e752a1998a7d6)
 

Author SHA1 Message Date
Yannis Spiliopoulos b38aaab8a7 Inline unhandled failure handler 9 years ago
Yannis Spiliopoulos 14d8783212 Rename function 9 years ago
Yannis Spiliopoulos 94d5caed15 Make clearer the puprose of test 9 years ago
Selwin Ong 11f9833816 Merge pull request #722 from probablytom/master 
Added better signal name lookup
 9 years ago
Yannis Spiliopoulos 9b774771db Fix style of conditional 9 years ago
Tom Wallis 89a380ef4b Added better signal name lookup 9 years ago
Yannis Spiliopoulos 3362fe2ba5 Test killing work_horse after we start monitoring 9 years ago
Yannis Spiliopoulos 08de4190e7 Dry the code. Export handling failed current job to a method 9 years ago
Yannis Spiliopoulos c4fd1659ea Fix docstring for monitor_work_horse 9 years ago
Yannis Spiliopoulos f9d5897922 Solves issue 702 
In order to solve issue 702 we have to check whether a work-horse
terminated unexpectedly (by inspecting the exit code of the work-horse
process). If it exited unexpectedly we check if the job has either been
marked as finished, failed or other valid states. If it's not in any
valid state we mark it as failed and move it to the failed queue.
Since the process was terminated unexpectedly (think OOM) we do not
have any exception context and we can't run any custom exception handlers.

There is still a chance that the job will finish successfully but the
work-horse process will be killed before the job is marked as finished
and we will erroneously mark it as failed. The users should take care
to write idempotent jobs.
 9 years ago
Yannis Spiliopoulos 93d286a6c7 Split execute job to expose issue 702 
In order to create a test for issue 702 we had to split execute_job
to a fork_work_horse function and a monitor_work_horse function.
 9 years ago
Yannis Spiliopoulos c00d3681f9 Failing test to demonstrate issue #702 
Test that demonstrates that if a work-horse process is terminated unexpectedly
the job being processed could be stuck at the "Started" state
(https://github.com/nvie/rq/issues/702)
 9 years ago
Vincent Driessen 07adca6ca3 Bump dev version 9 years ago
Vincent Driessen 46c39654d0 Merge old tag 0.6.0 so it becomes part of master again 
Otherwise, there's no linear history between this old tag and any new,
future, tags.  This is likely been a manual mistake when I released
0.6.0, so this is corrected now.
 9 years ago
Selwin Ong 3b12d104e1 Merge pull request #715 from samuelcolvin/heroku-worker 
adding heroku worker
 9 years ago
Samuel Colvin 7efd036a2c move ShutDownImminentException into exceptions.py 9 years ago
Samuel Colvin 0e26db9e08 correct wording in docstring and tests 9 years ago
Samuel Colvin 9f9c887645 better function names and process double SIGRTMIN 9 years ago
Samuel Colvin 2b544e5b17 add tests to HerokuWorker 9 years ago
Samuel Colvin e2f89b3171 fix for python 2.6 9 years ago
Samuel Colvin 18ba4658a4 adding heroku worker as per #584 9 years ago
Selwin Ong 0c5fe6251e Merge pull request #641 from kampfschlaefer/fix_connection_stack_in_stock_worker 
Fix connection stack in stock worker
 9 years ago
Arnold Krille 8e99706b16 run python 3.5 on travis, adopt timeouts 
Also
- Report the five slowest tests to watch for risk of timeout
- Double timeouts.
  Maybe that helps pypy on travis to finish successfully.
 9 years ago
Arnold Krille df22f127eb Test the worker in its own subprocess 
- run with an empty queue
- schedule one job (which uses get_current_connection and get_current_job) and
run `rqworker`
- schedule a job that itself schedules `access_self` and run `rqworker`
- Make sure the job didn't fail by assuring the failed queue is still empty
  afterwards.
- Install this package locally when running in travis.
  This actually unifies the behaviour of tox and travis as tox also builds the
  package and then installs it into each test environment.
- fix flake8 (as run by tox)
 9 years ago
Arnold Krille acbcea0c66 Add the workers connection to _connection_stack 
This allows jobs to use get_current_connection() with a resolvable connection.
And then these jobs can schedule new jobs for example (my use-case). Or attach
information to their job-object.

Also pop the pushed connection after running the jobs. This is needed for some
tests that check the _connection_stack afterwards;-) And also for use-cases
where the workers are used multiple times.

fixes nvie/rq#479
 9 years ago
Vincent Driessen bc4fc5595f Merge pull request #714 from samuelcolvin/py35 
add python 3.5
 9 years ago
Samuel Colvin facd5f6eab add python 3.5 to travis 9 years ago
Selwin Ong cc5b3c1e64 Merge pull request #707 from jlopex/javi/cancel_on_failed_queue 
Fix Job.cancel() method on failed queue
 9 years ago
Javier Lopez e92b57d128 test_job.py: Add cancel test on failed queue 9 years ago
Javier Lopez 8e24d3a92d job.py: Fix cancel failure on failed queue 9 years ago
Vincent Driessen 6a57d321f2 Ignore flake8 checks in local.py 9 years ago
Selwin Ong 636e34e55f Updated changelog. 9 years ago
Selwin Ong 7b1df1e878 Bump version to 0.6.0. 9 years ago
Selwin Ong 766bb60006 Merge branch 'dependent-jobs-with-result-ttl' 9 years ago
Selwin Ong e9d227c3df Dependent jobs are now correctly enqueued even if their parent jobs have result_ttl=0. 9 years ago
Selwin Ong 8b7b0e5584 Merge pull request #701 from jlopex/javi/fix_issue_700 
Fixes issue #700
 9 years ago
Selwin Ong 779a1683c7 Merge pull request #691 from amyangfei/delete_job_fix 
Don't call job.cancel if job has finished
 9 years ago
Javier Lopez 091c2568c9 test_job.py: Add test for cancel_job function 9 years ago
Javier Lopez c5e62c70bb job.py: Use fetch to get a complete Job instance 9 years ago
amyangfei 724c844378 Don't call job.cancel if job has finished 9 years ago
Selwin Ong 1116089b43 Merge pull request #697 from jlopex/fix_logging 
worker.py: Fix default logging_level
 9 years ago
Javier Lopez 3668c6f5d5 worker.py: Fix default logging_level 9 years ago
Selwin Ong 94dfb943b1 Merge pull request #690 from liorsbg/master 
Fix for Issue #644
 9 years ago
liorsbg 4c5d04105a Fix for #644 9 years ago
Selwin Ong cd0414361c Merge pull request #687 from jlopex/javi/allow_quiet_worker_class 
Allow Worker work method to specify the log verbosity
 9 years ago
Javier Lopez 43cb51064a Allow Worker work method to specify the log verbosity 9 years ago
Selwin Ong 189a962c8d Merge pull request #681 from ccurvey/master 
have worker use the passed-in connection if provided
 9 years ago
Chris Curvey 4326e19140 have worker use the passed-in connection if provided 9 years ago
Selwin Ong 4d204eed36 Merge pull request #672 from flycutter-zfz/source_reading 
Correct the comment of job's requeue function.
 9 years ago
Selwin Ong b43ae54016 Merge pull request #674 from kampfschlaefer/ignore_lambdas_in_flake8 
Ignore lambdas in flake8
 9 years ago