Skip to content

[BUG] CONFIGURATION.md documents limits.event.createdAt.minNegativeDelta but the real setting is maxNegativeDelta #677

Description

@Priyanshubhartistm

Describe the bug

CONFIGURATION.md lists this setting:

| limits.event.createdAt.minNegativeDelta | Maximum number of secodns an event's created_at can be in the past. ... |

The actual key read by the code and shipped in resources/default-settings.yaml
is maxNegativeDelta, not minNegativeDelta:

  • resources/default-settings.yamlcreatedAt: { maxNegativeDelta: 0 }
  • src/handlers/event-message-handler.ts and
    src/app/static-mirroring-worker.tslimits.createdAt?.maxNegativeDelta

An operator copying the documented key name will silently get no effect, because minNegativeDelta is never read. (There is also a typo, "secodns" → "seconds", on the same line.)

Expected behavior

Document the key as limits.event.createdAt.maxNegativeDelta and fix the typo.

System

Linux, Docker

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions