jobs

I am testing the queue functions in Laravel 5.1. I can make jobs queue up in my db table, called jobs, and I can get them to run successfully. I also created a queue failure table called failed_jobs. To test it, inside the jobs table I manipulate the payload data to make it fail then I run the queue worker daemon like so, so it will put the job in the failed_jobs table after one failed attempt: php artisan queue:work --daemon --tries=1 --queue=myqueue When the job fails it is immediately put into failed_jobs table as expected. FYI I have set things up just like the Laravel 5.1 docs recommend:

Why is the "Run As" drop down list is always empty when I try to set up a SQL Agent Job? I am trying to set up some SQL Agent Jobs to run using a proxy account. I am a member of the SQLAgentUserRole, SQLAgentReaderRole, and SQLAgentOperatorRole. When I try to add a step to to the job, I select SQL Integration Services Package and the Run As drop down list is empty. Anyone who is a sysadmin can view the proxy. Shouldn't I be able to use the proxy as a member of SQLAgentUserRole, SQLAgentReaderRole, and SQLAgentOperatorRole? What am I missing here? (The proxy account is active to the subsystem:

I am currently developing a RubyGem that provides an executable. The executable keeps track of the state of some log files using the FSSM gem. This executable should get started, do something in background, and get stopped later on. For example: $ my_executable start # do something different... $ my_executable stop I would first start a new process, that does the file watching stuff, inside the start method. But I don't know how to address this process for stopping it. What's the best way to provide such a behavior? Regards pid = Process.fork{exec 'gcalctool'} #don't use 'system' or

While trying to do something quite possibly beyond the means of PowerShell I seem to have ran into a brick wall. I have a main form script, which orchestrates most of my functions but I need another script to open a listener (system.Net.Sockets.Udpclient.Receive) and keep feeding in information to a textbox in the main form throughout the entire program's running. For the life of me I can't get around this daft non-child environment that jobs suffer from; no dot sourcing, no global scoped variables, nothing. I can put an object-listener on it for statechanged to completion and then open

I want to have a correct use case diagram for an online job portal system. Here is my attemp: I have some doubts: I can't see where making "Login" use case witch is an important use case for this system. This use case diagram is not showing the difference between a simple visitor and a registered one. The former could view vacancies, view advice without the obligation for having an account. The latter could view vacancies, view advice, upload CV (after be logged), apply for a job (after be logged) ... Is having two actors "Simple visitor" and "Registred Visitor" in my diagram will be correct?

I have an export function that read the entire database and create a .xls file with all the records. Then the file is sent to the client. Of course, the time of export the full database requires a lot of time and the request will soon end in a timeout error. What is the best solution to handle this case? I heard something about making a queue with Redis for example but this will require two requests: one for starting the job that will generate the file and the second to download the generated file. Is this possible with a single request from the client? Excel Export: Use Streams . Following is

Using Kue , how do I schedule a job to be executed once every Thursday? The Kue readme mentions that I can delay a Job, but what about repeatedly executing the Job at a specific time? I can do what I want with a cron job, but I like Kue's features. What I want is to process a Job once anytime on Thursday, but only once. I had a similar question and I basically came up with the following. If anyone else has a different solution I would love to see some other ideas. var jobQueue = kue.createQueue(); // Define job processor jobQueue.process('thursday-jobs', function (job, done) { var