This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-04
Channels
- # announcements (1)
- # architecture (18)
- # aws (7)
- # babashka (63)
- # beginners (38)
- # bristol-clojurians (1)
- # circleci (1)
- # clj-kondo (10)
- # clojars (4)
- # clojure (159)
- # clojure-berlin (3)
- # clojure-europe (4)
- # clojure-italy (7)
- # clojure-losangeles (6)
- # clojure-nl (7)
- # clojure-spec (3)
- # clojure-uk (109)
- # clojurescript (54)
- # css (1)
- # cursive (38)
- # data-science (2)
- # datascript (3)
- # datomic (14)
- # docker (2)
- # duct (11)
- # fulcro (47)
- # jobs (8)
- # jobs-discuss (3)
- # kaocha (4)
- # malli (3)
- # nyc (2)
- # off-topic (30)
- # overtone (3)
- # re-frame (17)
- # reagent (33)
- # shadow-cljs (29)
- # spacemacs (3)
- # specter (4)
- # tools-deps (13)
- # xtdb (13)
Hi y’all. I’m working on a project that’s using Overtone’s nice OSC api to connect to a lightboard (yes, it’s as cool as it sounds). However, I was running into some issues with the receiving server (i.e. the osc-server
bits). What seems to be happening is whenever the server receives an OSC message and starts the listener/handler processing, it adds a key to the message:
(assoc msg
:src-host (.getHostName src)
:src-port (.getPort src))
Unfortunately it seems InetSocketAddress#getHostName
makes a name server request to attempt to resolve the IP to a proper hostname. The network my laptop, and the lightboard is on, has no real internet access. This leads to a long delay while #getHostName
waits for the timeout.I’m wondering if the preferred solution for a PR would be to switch from #getHostName
to #getHostString
(no reverse lookup), or to add an option for backwords compatibility between those two methods.
Sadly I’m also no longer at said lightboard, which means it would be a bit of a pain to set up a mock/isolated test environment to test any changes, but if it’s necessary I can work something up.