Deprecated: Function get_magic_quotes_gpc() is deprecated in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 99

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 619

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 832

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later. http://resque.github.io/ Wed, 25 Jan 2023 14:11:41 +0000 Wed, 25 Jan 2023 14:11:41 +0000 Jekyll v3.9.2 <p>Hey y’all, <a href="https://github.com/chrisccerami">Chris Cerami</a> here. It hasn’t been quite as long in the making as 1.26.0, but after 11 months, Resque 1.27.0 has been released.</p> <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1">#Gemfile</span> <span class="n">gem</span> <span class="s2">"resque"</span><span class="p">,</span> <span class="s2">"~&gt; 1.27.0"</span> </code></pre></div></div> <p>Then just <code class="language-plaintext highlighter-rouge">bundle install</code>.</p> <h2 id="whats-new">What’s new?</h2> <p>There have been a bunch of bug fixes in 1.27.0, as well as a few changes and additions. As always, the changelog can be found <a href="https://github.com/resque/resque/blob/master/HISTORY.md#1270-2017-02-08">here</a>. While it had originally been a goal to keep the changelog up to date during development, we didn’t quite succeed there. Going forward, we would very much like to keep it up to date as pull requests are merged, to help keep history clear and accurate.</p> <h2 id="thanks-to-the-resque-team">Thanks to the Resque team!</h2> <p>I’d like to say a quick thank you to everyone who has contributed to Resque in the past year. Whether you were reviewing pull requests, submitting patches, opening issues, everyone has been super helpful in maintaining this bit of software we all rely on. It’s been great to work with all of you!</p> Wed, 08 Feb 2017 07:18:00 +0000 http://resque.github.io/2017/02/08/resque-1.27.0-released.html http://resque.github.io/2017/02/08/resque-1.27.0-released.html <p>Please welcome <a href="https://github.com/chrisccerami">@chrisccerami</a> as the latest committer to Resque! Chris has been helping out a lot recently, and doing great work.</p> Sat, 02 Apr 2016 09:09:34 +0000 http://resque.github.io/2016/04/02/welcome-chris.html http://resque.github.io/2016/04/02/welcome-chris.html <p>It’s been two long years, and a week. But today, I cut 1.26.0. Add this to your <code class="language-plaintext highlighter-rouge">Gemfile</code>:</p> <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="n">gem</span> <span class="s2">"resque"</span><span class="p">,</span> <span class="s2">"~&gt;1.26.0"</span> </code></pre></div></div> <p>After a <code class="language-plaintext highlighter-rouge">bundle install</code>, you’ll be good to go.</p> <h2 id="why-so-long">Why so long?</h2> <p>Way back when, my day job was working on open source Ruby projects. So was several of our other contributors’. We had big plans for Resque: a 2.0. Resque is a very old codebase, and is one of the larger and most widely deployed Ruby projects. There’s lots of good work that could be done, and a 2.0 is freeing: it allows you to reach for the sky.</p> <p>But times change. I’m the only active maintainer left, and I don’t even primarily work in Ruby anymore. So I put the kibosh on 2.0, and will be spending my time maintinaing Resque rather than re-thinking it. If you use Resque, I would love your help, and we’ve gotten some contributions from several new people in the last few months.</p> <h2 id="whats-new">What’s new?</h2> <p>Mostly, fixing bugs. You can see the changelog entry <a href="https://github.com/resque/resque/blob/master/HISTORY.md#1260-2016-03-10">here</a>. One of the things that we’ll be doing in the future is keeping the changelog up to date as we do development, rather than right before a release. The work of putting together the changelog has made releasing tough in the past.</p> <p>Another notable change: we have also adopted the <a href="http://contributor-covenant.org/">Contributor Covenant</a> 1.4. We want Resque contribution to be pleasant for all.</p> <p>One of the things we did was reach out to companies that we knew were on a fork of Resque and bring their patches back into the mainline, so they can use the official releases again. If your company is still on a fork, I would love to help you migrate to the official release again. Get in touch.</p> <p>Finally, <code class="language-plaintext highlighter-rouge">1.x</code> work is done on the <code class="language-plaintext highlighter-rouge">master</code> branch again, which is now the default branch. The few remaining open PRs that are targetted against <code class="language-plaintext highlighter-rouge">1-x-stable</code> will be manually merged into master by me when they’re ready.</p> <h2 id="ruby-version-support">Ruby version support</h2> <p>As Resque has a lot of legacy deployments, we support very old Rubies, including ones that are not supported by the Ruby project itself. However, I <a href="https://github.com/resque/resque/commit/2fda1d6dae0b7570a5e76606c81a236a9110c408">recently modified the rubies we test in CI</a>. We now have three “tiers” of Ruby support:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Tier 1: blocking ---------------- These are tested in CI, and we won’t cut a release without it passing. This list is: * 1.8.7 * 1.9.3 * 2.3.0 ... also known as the last release in each version line. Tier 2: community ----------------- We consider these Ruby versions supported, but won’t test in CI. Patches to fix breakage on these versions are very welcome, but we probably won’t actively prioritize efforts ourselves. This list is: * 1.9.2 * 2.0.0 * 2.1.0 * 2.2.0 Unsupported ----------- We don’t support these versions at all. If you can submit a fix for breakage on these versions, we’ll take it if it doesn’t break newer versions, but won’t guarnatee that they won’t end up broken in the future. This list is: * 1.9.1 * 1.9.0 * All versions before 1.8.7 </code></pre></div></div> <p>However, at this point, I truly wonder how much Resque is used on Ruby 1.8 or 1.9. I can barely even get 1.8 on my computer these days, and mostly rely on Travis telling me what’s going on with it. I am considering dropping 1.8.7 and 1.9.3 to ‘community’. If you don’t want that to happen, please get in touch. I mostly am just wondering if I’m doing this work for no real reason, not because I truly want to drop these rubies. It’s one less thing to worry about.</p> Thu, 10 Mar 2016 09:09:35 +0000 http://resque.github.io/2016/03/10/resque-1.26.0-released.html http://resque.github.io/2016/03/10/resque-1.26.0-released.html <p>Hello, world.</p> <p>Resque’s website has been nonexistant for a long time, and posting Resque information to my personal blog isn’t as good as having a Resque-specific space. So here we are!</p> <p>This blog will contain infrequent posts about Resque’s development. If you use Resque, you will probably want to subscribe.</p> <h2 id="where-resque-is-at">Where Resque is at</h2> <p>We’re going to be releasing 1.26.0 soon, after two years. We were originally working on Resque 2.0, but have decided to drop it, due to a lack of time. When that decision was made, several people had plenty of time to work on Resque, and were being paid for it, but that’s no longer the case. So future development will be focused on maintaining 1.x.</p> <p>If you would like to contribute to Resque, please <a href="mailto:steve@steveklabnik.com">get in touch</a>. We would love to have you.</p> Thu, 10 Mar 2016 09:09:35 +0000 http://resque.github.io/2016/03/10/hello-world.html http://resque.github.io/2016/03/10/hello-world.html