similar to: Workers without rails environment

Hemant, From http://backgroundrb.rubyforge.org/ "Currently, when a worker is deleted/exits, its result/status is also gone (i.e. you can?t query the status of a worker which is not running). This behaviour is expected to change in future releases." Is this still true? I ask because I am checking for a status after a worker exits and the code seems to work. Thanks Rupert

Hi, I have successfully crossed all the hurdles to install Ruby on rails on a redhat 5 Linux based system. But the last and the biggest hurdle i am facing at this moment is installing backgrounrb :( I followed all the steps from the http://backgroundrb.rubyforge.org/ 1. sudo gem install chronic packet 2. script/plugin install svn://rubyforge.org/var/svn/backgroundrb [IMP:::: I had to drop

This might be a little late but I was engaged in my university examinations. Moreover, I have an exam even today so apologies for the delay. Also, I had to change my project from weighting schemes to improve to improve estimated total number of results as weighting schemes was demanding a lot of time going through it. I would really appreciate if you could review my proposal asap.

Thanks for your reply. So the way I understand is that it can be upgraded but with a downtime, which means that there are no clients writing to this gluster volume, as the volume is stopped. But post a upgrade we will still have the data on the gluster volume that we had before the upgrade(but with downtime). - Hemant On 9/13/17 2:33 PM, Diego Remolina wrote: > Nope, not gonna work... I

If an exception is thrown in a worker, will the worker process exit? If it does and I don''t want it to exit, do I need to rescue all exceptions in every worker method? Joe

Hi, I''m using backgroundrb 0.2.1 and having problem with worker processes staying around when the rails application does not explicitly delete them. Is there a way to automatically delete the worker processes when it has completed the job? Also does killing the process manually (using kill command) harm the backgroundrb server? I have some occasions where the backgroundrb server just

hi all, i have ruby : 1.8.7 rails :2.3.11 and rubygem:1.6.2 installed on my Windows sys. my application work without error .I have upgraded the environment to gem:1.8.12,rails:3.1.3 ,ruby:1.9.2 i have getting the following error on starting the Webrick server D:/Hemant/Suggestica_setup/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'': cannot load such

Greetings, I am Hemant Kumar Singh, a computer science undergrad studying in NIT Warangal, India. I am interested to work on the project "Weighting Schemes" under the guidance of Olly Bets and Gaurav Arora; this project requires basic(or better) C++ knowledge and I've done 2 years of basic C++ in my high school. Moreover, this is my 2nd semester pursuing a computer science major in

Thanks, as per my knowledge, after downloading the source code, and making changes and then making sure it works properly , recompiling it and then patch it and finally submit a pull request. But what all changes should I/can I make? Please provide me some insight into this. Thanks&Regards, Hemant Kumar Singh On Apr 10 2019, at 10:56 am, Gaurav Arora <gauravarora.daiict at gmail.com>

Sending again. Can somebody please take a look and let me know is this is doable? Folks, We have glusters with version 3.8.13 and we are using that for RMAN backups. We get errors/warnings, RMAN-03009: failure of backup command on C1 channel at 03/28/2018 16:55:43 ORA-19510: failed to set size of 184820 blocks for file

Nope, not gonna work... I could never go even from 3.6. to 3.7 without downtime cause of the settings change, see: http://lists.gluster.org/pipermail/gluster-users.old/2015-September/023470.html Even when changing options in the older 3.6.x I had installed, my new 3.7.x server would not connect, so had to pretty much stop gluster in all servers, update to 3.7.x offline, then start gluster and

Okay thanks, how do I make a patch and submit one? Do you have a link for the same? Thanks&Regards, Hemant Kumar Singh On Apr 10 2019, at 4:13 am, Olly Betts <olly at survex.com> wrote: > On Tue, Apr 09, 2019 at 04:07:58PM +0530, Hemant Kumar Singh wrote: > > The GSoC guide section recommends reading of the hacking. > > > I don't actually see a reference to

Hi, I am using backgroundrb to process audio files from a rails controller. Currently a new worker gets created every time the method is called on the worker, using this code: @job_key = MiddleMan.new_worker(:worker => :audio_file_worker, :job_key => Time.now.to_i) MiddleMan.worker(:audio_file_worker, @job_key).make_new_audio_file(params[:release_id]) I need to create the new

This has been asked before, never well attended perhaps. Any thoughts on testing your workers? Current implementation is broken. An empty test case like this: require File.dirname(__FILE__) + ''/../test_helper'' require "#{RAILS_ROOT}/lib/workers/market_summary_worker" require "#{RAILS_ROOT}/vendor/plugins/backgroundrb/lib/backgroundrb.rb" require

Following is the output of top command at my server and i find the high usage very much alarming. We are basically a team of three developers working on same machine(remotely), so we run mongrel_rails servers from out ~/public/app directories. We also run a cluster of mongrel servers using apache2.2. Is this much memory use normal? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+

Hello Ulrik, Can you please explain this code means how and what this code is doing because I'm not able to understand it, if you can explain it i can use it in future by doing some Lil bit manipulation. Thanks data_help <- data_help %>% mutate(Purchase_ID = 1:n()) %>% group_by(Purchase_ID) %>% do(split_items(.)) cat_help %>% gather("Foo",

I was looking to upgrade Gluster server from ver 3.5.X to 3.8.X. I have already tried it in offline upgrade mode and that works, I am interested in knowing if this upgrade of gluster server version can be in online upgrade mode. Many thanks in advance. -- - Hemant Mamtora

Hi, I am kind of lost on how to configure the backgroundrb workers to run from a remote host? Suppose I have my main rails app in 1.2.3.4, and I want my backgroundrb workers to run from a machine with ip 5.6.7.8, what do I put in my backgroundrb.yml file? How will my workers know which database server to load the models from? Thanks, Ram

What does the method query_all_workers() do? There is no documentation on what this method returns (1.0.1 version). Orion -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080118/9f9b8112/attachment.html

The arithmetic stuff has already been fixed in master with https://github.com/dovecot/core/commit /5cccb4af850bb3ba81e73a8fb4f6881c3e1d4046.patch https://github.com/dovecot/core/commit /ac7aa955db4c77bbb169baa5d104a4c128674646.patch I have not seen the second error ever, it would need more information, can you gdb to it and see what the actual value is? Aki > On 03 January 2019 at 13:38