This topic was automatically generated from Slack. You can find the original thread here.
Igor Martynov : Hi, everyone! Amazing how great your work is! Maybe you can help me with spell-checker for using with pipedream? I mean, the lib to check the user’s input. (Something like ‘simple-spellchecker’) but optimized to work in this environment?
Dylan Sather (Pipedream) : Hi , thanks!
Were you not able to get simple-spellchecker working? I got something simple working in this workflow - let me know if that helps
Igor Martynov : Oh, 404: Page not found
Dylan Sather (Pipedream) : sorry I thought I made my code public, try now
Igor Martynov : Aha!
Igor Martynov : got it, I used the other method. Thank you very much!
Igor Martynov : How long the compiled listener is cached?
Dylan Sather (Pipedream) : what do you mean by “compiled listener”?
Igor Martynov : I mean, there is a listener to an event, on a generic http address provided by a platform. The first call has always the long timeout, the second and others in the row are much faster… So I supposed that the “listener” are alive for a period of time…
Igor Martynov : By the way: spellCheck method generates an error:
Igor Martynov : An unexpected error ocurred: Error: EROFS: read-only file system, mkdir '/opt/ee/node_modules/simple-spellchecker/dict/tmp-************
Dylan Sather (Pipedream) : Yes, we spin up a virtual machine to handle incoming invocations. Generally you can expect that to live for around ~20-30 minutes of inactivity (unfortunately this part is controlled by AWS and we don’t have control over how long the VM stays alive). That is, if you keep sending events, the same VM should generally stay “warm”. If you stop sending events for a period of roughly 20-30 min, the VM will spin down
Dylan Sather (Pipedream) : Does that package give you the ability to specify where the write occurs, or is that abstracted from you? You have full access to /tmp if you’re able to redirect it to write there
Igor Martynov : Check pm please