Hugh Secker-Walker

Results 14 issues of Hugh Secker-Walker

Dockerized version of the Express example. Me wonders if the intent was to add the two parameters of the API call as numbers, rather than catenate them...?

Alternate fix for #78 and #189 Builds on #193 , returning to its original intent Uses random hex string for Job.id, generated and registered in Queue prior to adding job...

bug

Use a single script, `docker-test.sh` to build an image and run a container to do testing. This is a less intrusive, more focussed version of #234 ``` $ ./docker-test.sh --help...

**[ This PR is made obsolete by #239 ]** See Testing section at bottom of README: https://github.com/hughsw/bee-queue/blob/docker-testing-sq1/README.md#testing

**[ This PR is made obsolete by #237]** Changes to fix problem reported in #189 and #78 This fix adopts an approach mentioned in #78 of making a separate Redis...

Adapt the existing ping pong example to a container implementation. Readme: https://github.com/hughsw/bee-queue/blob/ping-pong-1-docker-example/examples/docker/01-ping-pong-1/Readme.md

A minimalist Hello World for Bee-Queue using Docker containers in a networked setting with client and worker running in different Node JS processes. The main goal of this very terse...

I have seen jobs that have successfully completed, but do not emit either of `succeeded` or `failed`. The problem seems more likely on jobs that finish quickly. It also may...

bug
duplicate

I'm evaluating bee-queue for use in a client's project. I am not able to get the 'retrying' Queue Local Event to fire. Instead the 'failed' event gets fired, even though...

bug

This fixes the problem reported in #184 This fix could conceivably break code that has worked around the problem, e.g. by looking at `job.options.retries` or `job.status` in their queue failed...