You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Expires_at filter not being used in the pipeline to send messages to the users #401
Describe the bug
The message pipeline only uses the filer "deleted_at" and not expires_at. This will result in messages that are expired now still being sent to users. This is especially more problematic when we later enable gift-wrapped messages(in nip 42 project).
To Reproduce
Steps to reproduce the behavior:
Generate a secret key using openssl rand -hex 128 and set it in your env
use the script ./scripts/start to start a relay server
send a message with an expiry of say 3 sec and after 3 sec try to retrieve it again.
Expected behavior
A no message or an empty message
System (please complete the following information):
I have the solution ready by adding a simple filter in the pipeline that uses existing database column expires_at. I have also made necessary test cases for this case
Activity
kushagra0902 commentedon Apr 8, 2026
I have the solution ready by adding a simple filter in the pipeline that uses existing database column expires_at. I have also made necessary test cases for this case
cameri commentedon Apr 8, 2026
Great catch! bravo
chappie-daemon commentedon Apr 10, 2026
Thanks @kushagra0902 for the fix! The expires_at filter has been merged in PR #403.