node_redis throws depreciated EVALSHA error when restarting a Redis instance

Created by: bencooling

I'm getting the following error with Redis version 3.0.7 and 2.8.23.

I'm a little confused as what to expect from Bull if Redis becomes unavailable for any period of time; if I follow the steps listed below node_redis throws, the job isn't added into Redis and no failed event is fired by Bull?

1. Start Redis
2. Add a job
3. Stop Redis
4. Add a job
5. Restart Redis

node_redis: Deprecated: The EVALSHA command contains a argument of type OperationalError.
This is converted to "Error: NOSCRIPT No matching script. Please use EVAL." by using .toString() now and will return an error from v.3.0 on.
Please handle this in your code to make sure everything works as you intended it to.
{ [Error: ERR value is not an integer or out of range]
  cause: { [Error: ERR value is not an integer or out of range] command: 'EVALSHA', code: 'ERR' },
  isOperational: true,
  command: 'EVALSHA',
  code: 'ERR' }