Skip to content

Instantly share code, notes, and snippets.

Exception in thread "main" clojure.lang.ExceptionInfo: Error in component :config in system com.stuartsierra.component.SystemMap calling #'com.stuartsierra.component/start {:reason :com.stuartsierra.component/component-function-threw-exception, :function #'com.stuartsierra.component/start, :system-key :config, :component #vitality.components.configuration.ConfigurationComponent{:settings nil, :files (#object[java.net.URL 0x3089312a "file:/Users/bermonpainter/Dropbox%20(Personal)/Sites/vitality/resources/config/base.edn"] #object[java.net.URL 0xc143ceb "file:/Users/bermonpainter/Dropbox%20(Personal)/Sites/vitality/resources/config/content.edn"])}, :system #<SystemMap>}, compiling:(/private/var/folders/39/fhbhjjj14kx17bp5zrvwn9fm0000gn/T/form-init7738826316965973041.clj:1:125)
at clojure.lang.Compiler.load(Compiler.java:7239)
at clojure.lang.Compiler.loadFile(Compiler.java:7165)
at clojure.main$load_script.invoke(main.clj:275)
at clojure.main$init_opt.invoke(main.clj:280)
at clojure.main$initialize.invoke(
[Log] Error processing request! (application.min.js, line 4769)
Exception:
clojure.lang.ExceptionInfo: Invalid handler response
at clojure.core$ex_info.invoke (core.clj:4593)
vitality.services.dashboard.controller$fn__20263$fn__20264.invoke (controller.clj:164)
clojure.core.async$thread_call$fn__6148.invoke (async.clj:405)
clojure.lang.AFn.run (AFn.java:22)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:617)
Error processing request!
Exception:
clojure.lang.ExceptionInfo: Interceptor Exception: java.lang.IllegalArgumentException: Access key cannot be null.
at clojure.core$ex_info.invoke (core.clj:4593)
io.pedestal.impl.interceptor$throwable__GT_ex_info.invoke (interceptor.clj:31)
io.pedestal.impl.interceptor$try_f.invoke (interceptor.clj:53)
io.pedestal.impl.interceptor$enter_all_with_binding.invoke (interceptor.clj:141)
io.pedestal.impl.interceptor$enter_all$fn__7983.invoke (interceptor.clj:156)
clojure.lang.AFn.applyToHelper (AFn.java:152)
clojure.lang.ExceptionInfo: Interceptor Exception: Communications link failure
The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
at clojure.core$ex_info.invoke (core.clj:4593)
io.pedestal.impl.interceptor$throwable__GT_ex_info.invoke (interceptor.clj:31)
io.pedestal.impl.interceptor$try_f.invoke (interceptor.clj:53)
io.pedestal.impl.interceptor$enter_all_with_binding.invoke (interceptor.clj:141)
io.pedestal.impl.interceptor$enter_all$fn__7188.invoke (interceptor.clj:156)
clojure.lang.AFn.applyToHelper (AFn.java:152)
clojure.lang.AFn.applyTo (AFn.java:144)
Possibly confusing dependencies found:
[lein-sass "0.3.0"] -> [com.cemerick/pomegranate "0.2.0"] -> [org.sonatype.aether/aether-connector-wagon "1.13.1"] -> [org.codehaus.plexus/plexus-utils "2.0.7"]
overrides
[lein-sass "0.3.0"] -> [com.cemerick/pomegranate "0.2.0"] -> [org.apache.maven.wagon/wagon-http "2.2"] -> [org.apache.maven.wagon/wagon-http-shared4 "2.2"] -> [org.apache.maven.wagon/wagon-provider-api "2.2"] -> [org.codehaus.plexus/plexus-utils "3.0"]
and
[lein-sass "0.3.0"] -> [com.cemerick/pomegranate "0.2.0"] -> [org.apache.maven.wagon/wagon-http "2.2"] -> [org.apache.maven.wagon/wagon-provider-api "2.2"] -> [org.codehaus.plexus/plexus-utils "3.0"]
and
[lein-sass "0.3.0"] -> [com.cemerick/pomegranate "0.2.0"] -> [org.apache.maven.wagon/wagon-provider-api "2.2"] -> [org.codehaus.plexus/plexus-utils "3.0"]
Consider using these exclusions:

Open Conference Expectations

This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.

We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.

These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea

http://codepen.io/bpainter/pen/IkByq
A little nesting goes a long way.
http://codepen.io/bpainter/pen/aophg
- Only be as specific as you need to be.
- General rule of thumb - Don't nest more than 3 levels. It's a good indicator that you're being overly specific with your selectors.
- Always review your output (especially when you're first starting out). If the CSS being generated starts to look a bit off, review how you're writing your Sass.
@bpainter
bpainter / index.html
Created April 16, 2013 12:04
A CodePen by Bermon Painter. @content directive
<h1>@content directive</h1>
<p>We can take our media queries a step farther and create a mixin out of them. The @content directive in Sass allows you to pass entire sections of CSS rules back through a mixin.</p>
<article role="main">
Main content
</article>
<aside role="complementary">
Secondary content
</aside>
@bpainter
bpainter / index.html
Created April 16, 2013 12:04
A CodePen by Bermon Painter. Media Queries
<h1>Media Queries</h1>
<p>One of the nice things that Sass will let you do with media queries is nest them. This helps keep like sections of CSS chunked together and easier to maintain.</p>
<article role="main">
Main content
</article>
<aside role="complementary">
Secondary content
</aside>
@bpainter
bpainter / index.html
Created April 16, 2013 12:04
A CodePen by Bermon Painter. Control Directives - if, else if, else
<h1>Control Directives - if, else if, else</h1>
<p>One of the features that makes Sass more robust that other preprocessors is the wide variety of control directives.</p>
<button type="submit">Submit to our will</button>
<button type="reset">Start Over</button>
<button class="cancel">Give Up</button>