Error handling in clients in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to catch errors when connecting to Redis.

Redis

try {
  const client = redis.createClient();
  await client.connect();
} catch ([1]) {
  console.error('Connection error:', [1]);
}

Drag options to blanks, or click blank then click option'

Aerror

Berr

Cexception

De

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable name not declared in the catch block.

Leaving the catch parentheses empty.

The catch block receives the error object, commonly named err to handle connection errors.

2fill in blank

medium

Complete the code to listen for Redis client error events.

Redis

client.on('error', function([1]) {
  console.log('Redis error:', [1]);
});

Drag options to blanks, or click blank then click option'

Aerror

Bexception

Ce

Derr

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable name different from the one used inside the function.

Not passing any parameter to the function.

The error event handler receives an error object, commonly named err.

3fill in blank

hard

Fix the error in the code to properly handle Redis command errors.

Redis

client.get('key', function(err, reply) {
  if ([1]) {
    console.error('Command error:', err);
    return;
  }
  console.log('Value:', reply);
});

Drag options to blanks, or click blank then click option'

Aerr

Berror

Creply

Dexception

Attempts:

3 left

💡 Hint

Common Mistakes

Checking the reply instead of the error.

Using a wrong variable name for the error.

Check if err exists to detect command errors before using the reply.

4fill in blank

hard

Fill both blanks to handle Redis connection errors and close the client.

Redis

client.on('error', function([1]) {
  console.error('Redis error:', [1]);
  client.[2]();
});

Drag options to blanks, or click blank then click option'

Aerr

Berror

Cquit

Ddisconnect

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong parameter names in the error handler.

Calling a non-existent method to close the client.

The error event handler receives err. To close the client, call client.quit().

5fill in blank

hard

Fill all three blanks to retry connecting on error with a delay.

Redis

client.on('error', async function([1]) {
  console.error('Error:', [1]);
  await new Promise(resolve => setTimeout(resolve, [2]));
  await client.[3]();
});

Drag options to blanks, or click blank then click option'

Aerr

B1000

Cconnect

Derror

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names or delay values.

Calling the wrong method to reconnect.

Use err as the error parameter, wait 1000 milliseconds, then call client.connect() to retry.

Practice

1. What is the primary way to handle errors when using a Redis client in your application code?

easy

A. Use a separate database for error handling

B. Ignore errors and retry commands automatically

C. Use try-catch blocks or promise catch to handle errors

D. Restart the Redis server on every error

Solution

1. Step 1: Understand error handling in client code

   Errors from Redis commands or connection issues can be caught using try-catch blocks in synchronous code or promise catch in asynchronous code.

2. Step 2: Identify the correct method to catch errors

   Using try-catch or promise catch allows your application to respond gracefully to errors without crashing.

3. Final Answer:

   Use try-catch blocks or promise catch to handle errors -> Option C

4. Quick Check:

   Error handling = try-catch or promise catch [OK]

Hint: Always wrap Redis calls in try-catch or promise catch [OK]

Common Mistakes:

• Ignoring errors leads to crashes
• Restarting server is not a client error handling method
• Assuming errors fix themselves automatically

2. Which of the following is the correct way to listen for connection errors in a Node.js Redis client?

easy

A. client.on('error', (err) => console.error('Error:', err))

B. client.catch((err) => console.error(err))

C. client.on('connect', () => console.log('Connected'))

D. client.error(() => console.log('Error occurred'))

Solution

1. Step 1: Identify event listener for errors

   Redis clients emit an 'error' event when connection or command errors occur.

2. Step 2: Choose the correct syntax for error event listener

   The correct syntax is client.on('error', callback), where callback receives the error object.

3. Final Answer:

   client.on('error', (err) => console.error('Error:', err)) -> Option A

4. Quick Check:

   Error event listener = client.on('error') [OK]

Hint: Use client.on('error', callback) to catch connection errors [OK]

Common Mistakes:

• Using wrong event names like 'error' as a method
• Confusing 'connect' event with 'error'
• Trying to use .catch on client object directly

3. Given the following Node.js Redis client code, what will be logged if the key 'user:1' does not exist?

client.get('user:1').then(value => console.log(value)).catch(err => console.error(err))

medium

A. Empty string

B. undefined

C. An error message

D. null

Solution

1. Step 1: Understand Redis GET behavior for missing keys

   When a key does not exist, Redis returns a null value, not an error.

2. Step 2: Analyze the promise resolution

   The promise resolves with null, so console.log prints null, and catch is not triggered.

3. Final Answer:

   null -> Option D

4. Quick Check:

   Missing key GET returns null [OK]

Hint: Missing keys return null, not errors [OK]

Common Mistakes:

• Expecting an error for missing keys
• Confusing undefined with null
• Assuming empty string is returned

4. Consider this Redis client code snippet in Node.js:

client.get('key').then(value => {
  console.log(value.toUpperCase());
}).catch(err => console.error('Error:', err));

What error will occur if 'key' does not exist in Redis?

medium

A. TypeError: Cannot read property 'toUpperCase' of null

B. SyntaxError: Unexpected token

C. ReferenceError: value is not defined

D. No error, prints empty string

Solution

1. Step 1: Identify the value when key is missing

   Redis returns null for missing keys, so value is null.

2. Step 2: Understand what happens calling toUpperCase on null

   Calling toUpperCase() on null causes a TypeError because null has no methods.

3. Final Answer:

   TypeError: Cannot read property 'toUpperCase' of null -> Option A

4. Quick Check:

   Calling method on null causes TypeError [OK]

Hint: Check for null before calling string methods [OK]

Common Mistakes:

• Assuming no error occurs on null
• Confusing TypeError with SyntaxError
• Not handling missing key results

5. You want to safely get a user's name from Redis and convert it to uppercase, handling missing keys without errors. Which code snippet correctly handles errors and missing keys in a Node.js Redis client?

A) client.get('user:name').then(name => console.log(name.toUpperCase())).catch(console.error);

B) client.get('user:name').then(name => {
  if (name) console.log(name.toUpperCase());
  else console.log('Name not found');
}).catch(console.error);

C) try {
  const name = client.get('user:name');
  console.log(name.toUpperCase());
} catch (e) {
  console.error(e);
}

D) client.get('user:name', (err, name) => {
  if (err) throw err;
  console.log(name.toUpperCase());
});

hard

A. Option A

B. Option B

C. Option C

D. Option D

Solution

1. Step 1: Analyze each code snippet for error and null handling

   The first snippet calls toUpperCase() without checking for null, causing a TypeError if the key is missing. The second snippet checks if (name) before calling toUpperCase(), safely handling missing keys and logging 'Name not found'. The third snippet uses synchronous try-catch, which won't catch asynchronous promise errors from client.get(). The fourth snippet uses a callback but does not check if name is null before calling toUpperCase(), risking a TypeError.

2. Step 2: Select the snippet that safely handles missing keys and errors

   The second snippet correctly checks for null and handles errors with catch, making it safe and correct.

3. Final Answer:

   Option B -> Option B

4. Quick Check:

   Check null before method call + catch errors [OK]

Hint: Always check for null before string methods and catch errors [OK]

Common Mistakes:

• Calling methods on null without checks
• Using try-catch with promises incorrectly
• Throwing errors inside callbacks without handling