Run MemGator as a persistent process rather than using one-off execution

machawk1 / wail

:whale2: Web Archiving Integration Layer: One-Click User Instigated Preservation

https://matkelly.com/wail

MIT License

345 stars 32 forks source link

Run MemGator as a persistent process rather than using one-off execution #481

Closed machawk1 closed 3 years ago

machawk1 commented 3 years ago

As discussed in #480 and an undocumented TODO since integrating MemGator.

/cc @ibnesayeed

machawk1 commented 3 years ago

15e1943 does not invoke the querying process to the MemGator instance at startup. Attempting to fix (i.e., start) the MemGator process on app launch runs into a race condition of the UI being ready to update the status.