Fork me on GitHub
#untangled
<
2016-04-06
>
tony.kay03:04:37

I just beefed up the testing tutorial even more. It covers enough of protocol testing now that most people will be able to use the majority of it.

tony.kay03:04:45

Has a few exercises (to be expanded)

tony.kay03:04:03

@currentoor: Be sure to look around at how I’m using devcards in the tutorial. I’ve made a macro in there (probably will be moved into untangled-client) that helps you embed an Untangled application in a devcard. The new server exercises use this to good effect to make a full-stack app run in a devcard!

tony.kay03:04:31

(or rather the client side of a full-stack app…you sitll have to run the server ;) )

tony.kay03:04:16

The devcard atom is used for app state, which allows you to inspect the app state in the card (though you have to hand-normalize this, or use tree->db manually).

tony.kay04:04:19

@donavan: More to proofread simple_smile

tony.kay04:04:58

@ethangracer: @adambros Looks like we have a bug in the unhappy path for server interactions. If the server is not up at all I’m seeing reader errors (from transit). We probably need to catch those and set the fetch state to error (and/or run fallback)

currentoor04:04:24

@tony.kay: nice! Just a few hours ago I was thinking of how to write a macro to make devcard setup easier.

tony.kay04:04:52

well, there ya go!

currentoor04:04:07

also my employer has decided to move forward with untangled!

currentoor04:04:55

@tony.kay: at some point can we have that skype session you mentioned? I’d like to help make untangled great

currentoor04:04:09

and we’ll be using it in production

tony.kay04:04:10

Absolutely. What time zone you in?

currentoor04:04:15

same as yours

tony.kay04:04:27

I’m giving a talk in Portland on Thursday

tony.kay04:04:34

hope to get that up on YouTube

currentoor04:04:52

what’s the talk about?

tony.kay04:04:04

of course 😉

tony.kay04:04:22

you anywhere nearby?

tony.kay04:04:37

Ah, not an easy drive

tony.kay04:04:53

I’m driving up from Bend, OR

currentoor04:04:23

yeah i saw pictures of bend and looked the rent prices, made me very jealous

tony.kay04:04:31

esp on the rent

currentoor04:04:05

so skype session next week then? i had a few questions, or i can just ask them here?

tony.kay04:04:47

I can chat now for a few if you want. let me PM you info

currentoor04:04:53

k sounds good

adamkowalski04:04:08

@tony.kay: is the talk going to be on youtube later?

adamkowalski04:04:28

awesome, where will it be held anyway? I actually live nearby so if it is open to the public I would love to stop by

tony.kay04:04:55

Go to http://meetup.com…the Clojure PDX meetup

tony.kay04:04:59

it’s at puppet labs

adamkowalski04:04:29

thanks! I will definitely check it out

mahinshaw04:04:44

@tony.kay: Those read errors you were seeing, can that be reproduced by simply shutting down the server?

tony.kay04:04:45

Great, see you there I hope

tony.kay04:04:14

@mahinshaw: Um. I’m seeing them with the server shut down on my devcard full-stack thing in the server part of the tutorial

tony.kay04:04:25

so, I assume so, but it could be an artifact of that

mahinshaw04:04:51

I tried shutting down a server for the my project, and couldn’t reproduce it. We do throw some xhrio errors in that case though.

tony.kay04:04:19

I was seeing the xhrio errors, but the app state marker stayed “loading” instead of “failed"

tony.kay04:04:32

and I saw an exception from reader/transit

tony.kay04:04:54

Tutorial might be behind on server dep, now that I think of it

tony.kay04:04:03

probably should try that first simple_smile

tony.kay04:04:48

oh wait…server is down…and I’m running latest client

tony.kay04:04:08

perhaps I need to bump om-next dependency to alpha32…I might be seeing weirdness related to the porting stuff you just did

tony.kay04:04:36

oh wait….I did not push that to clojars yet

tony.kay04:04:48

bleh…tomorrow. Need to stop for tonight

mahinshaw04:04:55

hahahahahahahaha!

tony.kay04:04:20

yep…brain fried, core dumped

tony.kay04:04:29

see you in the A.M.

mahinshaw04:04:53

see you tomorrow.