Bug: idempotent functions return None on replay when the stored response is falsy (0, False, "", [], {})

オープン
  • 何か問題がありますか？
#8,700 コメント 3 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@thebadalov がすでに取り組んでいます。

2026年10月29日 から。

  • #8701 @thebadalov による — オープン

評価

この issue はまだ評価されていません。

説明

bug idempotency
Expected Behaviour

When an idempotent function returns a falsy value (0, False, "", [], {}), a retry with the same payload should return that same value from the persistence store.

Current Behaviour

The first call returns the value and it is stored correctly, but every replay returns None.

IdempotencyHandler._handle_for_status reads the stored response with:

serialized_response = self.output_serializer.from_dict(response_dict) if response_dict else None

so any falsy response_dict becomes None. #8090 pointed out this line together with the write path in _get_function_response. The write path was changed to is not None, but the read path still uses a truthiness check, so the value is saved and then dropped on replay.

Code snippet
from aws_lambda_powertools.utilities.idempotency import idempotent_function
from aws_lambda_powertools.utilities.idempotency.exceptions import (
    IdempotencyItemAlreadyExistsError,
    IdempotencyItemNotFoundError,
)
from aws_lambda_powertools.utilities.idempotency.persistence.base import BasePersistenceLayer, DataRecord


class InMemoryPersistenceLayer(BasePersistenceLayer):
    def __init__(self):
        super().__init__()
        self.records = {}

    def _get_record(self, idempotency_key) -> DataRecord:
        if idempotency_key not in self.records:
            raise IdempotencyItemNotFoundError
        return self.records[idempotency_key]

    def _put_record(self, data_record: DataRecord) -> None:
        if data_record.idempotency_key in self.records:
            raise IdempotencyItemAlreadyExistsError
        self.records[data_record.idempotency_key] = data_record

    def _update_record(self, data_record: DataRecord) -> None:
        self.records[data_record.idempotency_key] = data_record

    def _delete_record(self, data_record: DataRecord) -> None:
        self.records.pop(data_record.idempotency_key, None)


persistence_layer = InMemoryPersistenceLayer()


@idempotent_function(data_keyword_argument="order", persistence_store=persistence_layer)
def count_items(order):
    return len(order["items"])


order = {"order_id": "o-1", "items": []}
print(count_items(order=order))  # 0
print(count_items(order=order))  # None, expected 0

I see the same with CachePersistenceLayer on a real Redis server: 0, False, "", [] and {} all come back as None on replay, while None and truthy values are returned correctly.

Possible Solution

Use is not None, matching the write path:

serialized_response = self.output_serializer.from_dict(response_dict) if response_dict is not None else None

DataRecord.response_json_as_dict() already returns None when there is no stored data, and a function that returns None is stored as null, so that case keeps returning None.

Steps to Reproduce

Run the snippet above. Any persistence layer is affected, since the check is in the shared handler.

Powertools for AWS Lambda (Python) version

latest (3.37.0, also on develop)

AWS Lambda function runtime

3.13

Packaging format used

PyPi

Debugging logs
N/A, the replay returns None without an error
主要言語
Python
スター
3.3k
フォーク
511
平均マージ
3日 4時間
マージ済み PR（30日）
98

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aws-powertools/powertools-lambda-python のほかの issue

aws-powertools/powertools-lambda-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。