Fork me on GitHub
#untangled
<
2016-12-28
>
ianchow01:12:19

thanks for the clarification tony. i had the wrong idea that each df/load resulted in separate network calls. if the loads are batched and processed in order, then i probably won’t have to use df/load-data anymore.

fragamus06:12:30

@tony.kay I ditched intellij and made sure I was running a recent version of lein. I deleted my .m2 I still get the same errors. I really want to use clojure / om-next / untangled; I feel not so great bugging you guys with this basic stuff. Anyone have any suggestions?

fragamus06:12:12

I am running it exactly as recommended in the README.md

fragamus07:12:10

lein -v Leiningen 2.7.1 on Java 1.8.0_112 Java HotSpot(TM) 64-Bit Server VM

adambros07:12:34

@fragamus Try removing your ~/.lein/profiles.clj

adambros07:12:51

That's usually it in this kind of problem

tony.kay14:12:23

@fragamus yes, what @adambros said. That is my #1 suspect as well. If that doesn’t work, what do you see from lein deps :tree?

fragamus17:12:38

I do not have a ~/.lein/profiles.clj My lein deps :tree appears in my 10:36 PM post above.

tony.kay17:12:50

let me look

tony.kay18:12:27

I don't see a top-level clojure or clojurescript dependency. What is your project.clj look like?

tony.kay18:12:44

@fragamus ^^^

tony.kay18:12:58

which demo is that?

tony.kay18:12:03

on which branch?

tony.kay18:12:37

on develop, that recipe works for me:

# lein --version
Leiningen 2.7.0 on Java 1.8.0_112 Java HotSpot(TM) 64-Bit Server VM

fragamus18:12:41

My environment must be wrong but I set up leiningen the way it said to do on their web page.

fragamus18:12:09

lein --version Leiningen 2.7.1 on Java 1.8.0_112 Java HotSpot(TM) 64-Bit Server VM

tony.kay18:12:25

# lein run -m clojure.main
Clojure 1.8.0
user=> (start-figwheel)
STARTING FIGWHEEL ON BUILDS:  nil
Figwheel: Starting server at 
Figwheel: Watching build - dev
Compiling "resources/public/js/compiled/app.js" from ["src/client" "dev/client"]...
Successfully compiled "resources/public/js/compiled/app.js" in 11.099 seconds.

tony.kay18:12:57

I'm using home brew for lein, I think

fragamus18:12:08

lein run -m clojure.main

fragamus18:12:00

hang on... i was on branch master... switching...

tony.kay18:12:08

should be the same

tony.kay18:12:19

master, if anything, should be more stable

fragamus18:12:48

compiling...

tony.kay18:12:35

hm. strange

tony.kay18:12:43

(reset-autobuild)

tony.kay18:12:39

well, that looks better

tony.kay18:12:47

did you fork or clone the repo?

tony.kay18:12:15

actually, at the moment master and develop are identical git checkout develop; git diff master

tony.kay18:12:49

wondering if you had munged a file

tony.kay18:12:57

and switching branches fixed it, perhaps

fragamus18:12:57

tony... not sure i think mi cloned this time

fragamus18:12:00

git checkout develop; git diff master Already on 'develop' Your branch is up-to-date with 'origin/develop'.git checkout develop; git diff master Already on 'develop' Your branch is up-to-date with 'origin/develop'.git checkout develop; git diff master Already on 'develop' Your branch is up-to-date with 'origin/develop'.

tony.kay18:12:06

well, my only guess at this point is you had a munged file. Looks like your two branches are the same too

tony.kay18:12:45

A handy command to know to make sure you're at a clean slate (assuming all code changes are checked in):

git clean -xfd
wipes out everything not tracked (including IDE control files).

tony.kay18:12:10

git checkout -- .
is a nice one for throwing away changes.

fragamus18:12:22

i was doing that... fresh checkout and xfd all of that

tony.kay18:12:35

well, it is working now it seems

fragamus18:12:51

thanks i will spin up the sever and see

tony.kay18:12:41

ok, now make sure you use localhost:8080 😉

fragamus18:12:24

yes I am on localhost:8080

tony.kay18:12:31

where are you seeing this error?

fragamus18:12:04

in chrome developer view

tony.kay18:12:22

I thought it was failing to compile

fragamus18:12:50

console output

tony.kay18:12:00

try firefox

tony.kay18:12:50

guessing you have some kind of chrome extension that is borking you

tony.kay18:12:19

yeah. Some kind of clj/cljs plugin I'm guessing?

fragamus18:12:03

React Developer Tools 0.15.4

fragamus18:12:45

It comes right up in firefox

fragamus18:12:11

Now BIG thank you. Apologies to the channel for this madness.

tony.kay18:12:32

no problem. Let me know when you verify which plugin it was. I'm surprised the React one is to blame

fragamus18:12:42

i fragged all my extensions one by one, trying it again in a new tab each time. It continued to fail. then i quit and restarted chrome and it still failed.

tony.kay18:12:12

wow. We do push an install of devtools through the network

tony.kay18:12:19

for clj data structure viewing

fragamus18:12:26

so we still have a mystery but if no one else is experiencing it i say we drop it. I will use firefox.

tony.kay18:12:41

look in user.cljs

tony.kay18:12:48

comment out the devtools lines

tony.kay18:12:02

I use nothing but chrome and it is fine

tony.kay18:12:30

anyhow. glad you got it working

tony.kay18:12:45

Chrome is better with those devtools, as debugging shows data structures more nicely

tony.kay18:12:55

even with source tracing

fragamus18:12:07

well clearly i have done something to my environment, but I don't know what I did

fragamus18:12:59

i deleted all mention of devtools in user.clj and then i did (reset-autobuild) and I created a new tab in chrome but the error persists. BUT... no worries I am up and running and would rather code than solve this weirdness.

fragamus19:12:50

I ran an incognito window in chrome and tried it... works fine.

fragamus19:12:14

OH I did a control-reload page and it works now in regular chrome

fragamus19:12:07

I guess we have all learned something...

fragamus19:12:19

Don't be a newb/idiot

tony.kay19:12:30

well, if you figure out what kind of cached weirdness you had, let me know. OH. In chrome devtools options: I "enable custom formatters" and "disable caching when devtools is open"

tony.kay19:12:41

the disable caching might have saved you