6 replies

Debouncing an Effect: avoid setTimeout, use Effect.sleep + fiber/fork

hello! can we use setTimeout within a running effect? i have an effect that i want to debounce, in my case i dont really care about the errors that can occur inside:

const handleGoogleWebhook = Effect.fn(function*() {
  const runtime = Effect.runtime<never>()

  setTimeout(() => {
    Runtime.runPromise(runtime, handleSomething)    
  }, 5000)
  ...
})

const handleGoogleWebhook = Effect.fn(function*() {
  const runtime = Effect.runtime<never>()

  setTimeout(() => {
    Runtime.runPromise(runtime, handleSomething)    
  }, 5000)
  ...
})

however when running this code i can see that the callback function is called 2-3 minutes after (it's not really consistent, however it's never even close to 5 seconds)
I wonder if using setTimeout can conflict with how effect are running, should i instead use fork related functions?

Effect Community•3w ago•

6 replies

bebenzer

Debouncing an Effect: avoid setTimeout, use Effect.sleep + fiber/fork

hello! can we use setTimeout within a running effect? i have an effect that i want to debounce, in my case i dont really care about the errors that can occur inside:

const handleGoogleWebhook = Effect.fn(function*() {
  const runtime = Effect.runtime<never>()

  setTimeout(() => {
    Runtime.runPromise(runtime, handleSomething)    
  }, 5000)
  ...
})

const handleGoogleWebhook = Effect.fn(function*() {
  const runtime = Effect.runtime<never>()

  setTimeout(() => {
    Runtime.runPromise(runtime, handleSomething)    
  }, 5000)
  ...
})

Debouncing an Effect: avoid setTimeout, use Effect.sleep + fiber/fork

Similar Threads

Debouncing an Effect: avoid setTimeout, use Effect.sleep + fiber/fork

Similar Threads

Similar Threads

Similar Threads