Tried adding (:gen-class) to myproject.proto namespace, but no luck.

also happens on host machine that's running Java Oracle 20.0.01

Requiring myproject.proto NS from prod.clj does not help

this is not an electric issue

did you resolve it?

No 😕 Temporary workaround by deploying dev build to prod

this is likely the root problem causing the rest of your problems

my pain is no logs

just reactorfailure

logs are not broken, please check out a clean starter app and convince yourself they work

you can add more logs to your app's boot sequence

I compared mine to the starter-app and seems to be same

you can also turn log level up to trace

ok will try that

maybe I need to catch exception in jetty side

i want to be clear: if logs are broken, it is your fault

sure, but I've had logging issues before so I'd rather mention it than be stuck for hours

Electric Does Not Have Logging Issues, if you suspect otherwise please checkout a clean starter app and confirm that it is true, and save yourself the hours of pain debugging something that is not broken

ok - just trying to get things working 🙂

https://github.com/hyperfiddle/electric/blob/master/.github/workflows/test_and_deploy.yml

logback.xml:

<!-- Jetty logger config. See  and
ask ChatGPT. `scan` and `scanPeriod` enable hot reload of logger config, leave on! -->
<configuration scan="true" scanPeriod="5 seconds">
    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>%highlight(%-5level) %logger: %msg%n</pattern>
        </encoder>
    </appender>

    <root level="DEBUG">
        <appender-ref ref="STDOUT" />
    </root>

    <logger name="hyperfiddle" level="DEBUG" additivity="false"><appender-ref ref="STDOUT" /></logger>
    <!-- <logger name="hyperfiddle.electric.impl.io" level="INFO" additivity="false"><appender-ref ref="STDOUT" /></logger> -->
    <logger name="quey" level="DEBUG" additivity="false"><appender-ref ref="STDOUT" /></logger>
</configuration>

@U09K620SG I've added an nREPL into my uberjar build. How do I trigger an Electric run from REPL to try and see an error, please? (e/run something)?

this doesn't seem to work:

(ns scratch
  (:require [hyperfiddle.electric :as e]
            [hyperfiddle.electric-dom2 :as dom]))

(e/defn Test []
  (dom/div "hi"))

(e/run (Test.))

OK this runs "in prod" but obviously fails because DOM stuff missing on server for my components:

(ns scratch
  (:require [hyperfiddle.rcf :as rcf :refer (tests tap %)]
            [hyperfiddle.electric :as e]
            [hyperfiddle.electric-dom2 :as dom]
            [missionary.core :as m]
            [hyperfiddle.history :as history];; for core
            [quey.manage.core :as core]
            [datomic.api :as d]))

(e/defn SanityTest [!x]
  (prn "hi")
  (let [x (e/watch !x)                       ; reactive x
        a (inc x)]                           ; reactive a depends on reactive x
    (tap (+ a (inc x)))))
  ;(d/q nil nil))

;(e/run Test)

(tests "Electric baseline program - a dataflow diamond"

  (def dispose (e/run (core/Page. [:thing]))) ;; fails because DOM stuff

  ;; rest is jsut here to test

  (def !x (atom 0))
  (def dispose (e/run (SanityTest. !x)))
  % := 2
  (swap! !x inc)
  % := 4
  (swap! !x inc)
  % := 6
  (dispose))

For me, this error was caused by requiring xtdb.api or anything that requires xtdb.api in user.clj . Similarly, at dev/repl time, this was not an issue, but occurred only with uberjars. Requiring xtdb.api (or anything that requires it) in prod.clj was not a problem. I was able to work around it by avoiding requiring utils/start-xtdb! in user.clj and instead doing (def start-xtdb! (delay @(requiring-resolve 'utils/start-xtdb!))) . It was really hard to track down, had to do a full "binary search" on my code vs the electric-starter-app code. @U09K620SG FYI

@U5S5570KH I can’t remember but try moving user.clj footgun to ~/src-dev and adding “src-dev” to :paths for :dev alias.

So that user.clj won't get included in the uberjar build?

Yeah. I think this resolved a different error, but maybe it helps: https://www.karimarttila.fi/clojure/2023/03/14/creating-uberjar-for-clojure-fullstack-app.html

e/snapshot ?

use e/watch to bridge atoms to electric, which you already know, i think you might be over thinking it

(e/server (println (e/client (e/watch !x)))) accomplishes your goal of running an effect on the server every time an atom changes

oops, did you delete a question? or somehow i replied to wrong thread

Ah, no. I ended up figuring it out! I definitely was overthinking it.

The incremental compiler model is very powerful, I just need to get more in the habit of thinking that way.