This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-30
Channels
- # aleph (25)
- # announcements (20)
- # babashka (29)
- # babashka-sci-dev (12)
- # beginners (27)
- # biff (3)
- # clojure (29)
- # clojure-europe (21)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojurescript (3)
- # clr (5)
- # code-reviews (4)
- # data-science (7)
- # datahike (6)
- # datascript (3)
- # emacs (9)
- # fulcro (5)
- # graalvm (10)
- # malli (15)
- # nbb (7)
- # off-topic (17)
- # pathom (9)
- # polylith (4)
- # practicalli (15)
- # reitit (3)
- # releases (2)
- # rum (1)
- # shadow-cljs (73)
- # squint (34)
- # tools-deps (3)
- # xtdb (11)
continuing the reliable http service discussion here: found https://github.com/mccutchen/go-httpbin but it doesnt have releases, maybe we can build and host the binaries somewhere and pull into the CI when needed? the code in the repo seems quite well done and self contained to be used in most places
@rahul080327 worth an experiment, I'd say let's test it inside the babashka.curl library in a branch
and else we'll just mark http tests as :flaky and skip those on master, I still think that's better than having to run a go binary locally tbh
yeah no doubts on the flaky tests approach, this is more from an "integration tests" perspective
we wont be doing https calls with this though, setting that up with certs is gonna be a headache
pff, flaky tests already https://github.com/babashka/http-client/actions/runs/3807243454/jobs/6476752096#step:6:1544
I prefer the low tech solution, it's the only way to not make the local testing more complicated
yeah i'll go look for more options
maybe you could try the tests with https://httpbingo.org/ if thats any better 😛
given any hosted service, its gonna suck at some point i suppose