rcf/set-timeout! not having effect at node REPL
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
(ns dustin.y2021.hello_node_repl
(:require [hyperfiddle.rcf :as rcf :refer [tests ! %]]
["plaid" :as plaid-api]))
(hyperfiddle.rcf/set-timeout! 100)
(tests
hyperfiddle.rcf/*timeout* := 100
(defn setTimeout [f ms] (js/setTimeout ms f))
(rcf/! 1) (setTimeout 10 (fn []
(rcf/! 2) (setTimeout 200 (fn []
(rcf/! 3)))))
% := 1
% := 2
% := ::rcf/timeout)
✅
✅
✅
❌ dustin/y2021/hello_node_repl.cljs:6:1
in %42888
expected: :hyperfiddle.rcf/timeout
actual: 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the snippet from dustin/y2021/hello_node_repl.cljs in the Node REPL, starting with the rcf/set-timeout! call and the nested setTimeout callbacks. Trace why the final assertion sees 3 instead of ::rcf/timeout; done means the shown timeout assertion behaves as expected at the Node REPL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, node.js
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100