Fork me on GitHub
#hoplon
<
2017-11-09
>
opyate10:11:22

good morning, romans. I have a small example here https://github.com/opyate/hoplon-demo Problem: if you tag "INTERNAL TRANSFER" with something, then click "Load more", the new "INTERNAL TRANSFER" aren't tagged. Just checking if I'm mis-using the spreadsheet-ness of Javelin

thedavidmeister15:11:16

@opyate could you make a simple version of what you're trying to do?

opyate15:11:36

@thedavidmeister haha, that is the simple version. The original version uses IndexedDB and channels, with CSV upload functionality.

thedavidmeister16:11:51

@opyate i haven't pulled it down, but you shouldn't deref cells passed to dom elements

thedavidmeister16:11:11

don't do (em @date)

opyate16:11:58

thanks, I'll make the changes and report back

thedavidmeister16:11:11

you only deref when you want a single value at a specific point in time

thedavidmeister16:11:16

e.g. when an event triggers

thedavidmeister16:11:45

the point of cells is to manage many values over indefinite time for you 🙂

opyate16:11:31

wowzers, deref really messes it up. I now have just 2 "INTERNAL TRANSFER" after "loading" - which is correct - instead of 7. (screenshots in https://github.com/opyate/hoplon-demo/tree/master/doc) Thanks for the pointer (no pun intended!) @thedavidmeister

jjttjj19:11:02

I'm getting this really weird issue with castra where the castra request is failing silently on the server when the rpc function returns a result that's over a certain "size"... size at this point appearing to be just the size of the output of the transit encoding function result. Things work when the transit payload is under 5100 characters but fail above 5300 characters. anyone aware of what might be causing this? are there any bugs or limitations on size in castra or transit? The only thing I've been able to find is the transit writing function in castra.middleware below

(def clj->json
  (atom #(let [out (ByteArrayOutputStream. 4096)]
           (t/write (t/writer out :json) %2)
           (.toString out))))
but increasing the ByteArrayOutputStream size doesn't seem to help either

dm319:11:32

are there really zero logs/errors/printouts?

dm319:11:56

do you get any HTTP response back at all?

jjttjj20:11:30

I have a slightly weird setup using pedestal + castra. Your answer reminded me that I blacklisted pedestal.* logging output due to its excessiveness. I now see a

clojure.lang.ExceptionInfo: java.io.IOException in Interceptor :io.pedestal.http.impl.servlet-interceptor/ring-response - org.eclipse.jetty.http.BadMessageException: 500: Request header too large
which gives me something to figure out at least. Thanks!