Repository navigation
[Bug]: Ingest Interval not triggered anymore #753
Description
Activity
@o-love
Quick question: Can we either use"ingestion_trigger_age_seconds": 120.5,so that it's clear what the value represents, OR (even better IMHO) use a string with duration
"ingestion_trigger_age": "2m30s",To clarify
ingestion_trigger_ageaccepts both strings in ISO format and seconds in numeric format.Regarding the parsing.
While I do think golang style time durations are nicer. The python standard library prints and parses time deltas using ISO strings.
This is also part of the server config and not directly end user facing and shouldn't be something changed to often.So I think it is best to stick with the Python standard library rather than defining custom string formats.
@sscargal, thoughts?
If we want golang style there are probably some regex patterns already well tested online to do it.I don't have a strong preference either way. Perhaps keeping the Python ISO approach, given it's not a user-facing property, is preferred at this time.
However, we could decide whether renaming the property to make its intent clearer would be appropriate. For example,
ingestion_trigger_interval(or possiblyingest_intervalfor brevity) is clearer and more self-explanatory thaningestion_trigger_age, especially since it defines the interval between ingestion checks. "Age" is somewhat ambiguous and less standard in timing/interval settings across the software industry.
Describe the bug
I started MemMachine with Neo4j for semantic memory and added one memory via the API.
The ingest trigger did not kick in after 10min.
Steps to reproduce
compose
Expected behavior
The ingest loop should kick in after (I think it used to be) 2min.
Environment
compose.
Additional context
No response