noAckTimeoutId is not cleared when no handlers match the request

[Pouja]

noAckTimeoutId is not cleared at https://github.com/slackapi/bolt-js/blob/main/src/receivers/AwsLambdaReceiver.ts#L262

If no handler is listening to an incoming request from Slack. The library properly makes a 404 message. But it does not clear the timeout. Causing an open handle.

@slack/bolt version

4.0.0-rc.3

Your App and Receiver Configuration

    this.app = new App({
      token: this.options.apiToken,
      receiver: this.awsLambdaReceiver,
      agent: proxyAgent,
      signingSecret: this.options.signingSecret,
      endpoints: this.options.apiEndpoint,
      logger: this.mapLogger(),
      botId: 'XXXX',
      botUserId: 'XXXX',
    });

Node.js runtime version

v20.11.1

Steps to reproduce:

(Share the commands to run, source code, and project settings)

1. Create a new app with AwsLambdaReceiver as receiver.
2. Dont add any handlers.

Expected result:

No timeouts are leaked outside the execution

Actual result:

Timeout being cleared.

Requirements

For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. 🙇

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[filmaj]

Thanks for filing this. I've confirmed the issue in a test. Should have a fix for it shortly. It will get merged into the bolt v4 branch and will be released in 4.0.0-rc.4.

PR up for this here: #2285

[filmaj]

Hey @Pouja I just released bolt version 4.0.0-rc.4 that addresses this issue. I will leave this issue open until we merge and release the final 4.0.0 non-RC version.

[filmaj]

Hello! Bolt v4 is live on npm, and a fix for this issue is available in that version.

[Pouja]

Awesome, thank you!