Cider warning post 0.3.25

[Peter Fraenkel]

When a project has a dependency on versions of core.typed 0.3.26 or later,
cider will generate a warning on startup:


"WARNING: CIDER's version (0.14.0) does not match cider-nrepl's
version (nil). Things will break!”.

The same thing happens with later versions of cider as well. This was
reported to me as a problem with squiggly clojure
<https://github.com/clojure-emacs/squiggly-clojure>, but the problem can be
replicated with only the dependency on typed. It doesn't appear that
things in fact do break, and you can verify from lein deps or
cider.nrepl.version/version that the version is in fact correct. The logic
by which cider decides what version of cider-nrepl it thinks it's running
is not clear to me.

Is this a known problem? I am wondering if it has anything to do with AOT?

[Ambrose Bonnaire-Sergeant]

Try using

:classifier "slim"

in the core.typed dep to remove AOT files. Does that help?

Post by Peter Fraenkel
When a project has a dependency on versions of core.typed 0.3.26 or later,
"WARNING: CIDER's version (0.14.0) does not match cider-nrepl's
version (nil). Things will break!”.
The same thing happens with later versions of cider as well. This was
reported to me as a problem with squiggly clojure
<https://github.com/clojure-emacs/squiggly-clojure>, but the problem can
be replicated with only the dependency on typed. It doesn't appear that
things in fact do break, and you can verify from lein deps or
cider.nrepl.version/version that the version is in fact correct. The logic
by which cider decides what version of cider-nrepl it thinks it's running
is not clear to me.
Is this a known problem? I am wondering if it has anything to do with AOT?

[Peter Fraenkel]

That "fixes" the problem, so my unfounded intuition that AOT was involved
seems to be correct. I still have no idea why....

On Tuesday, February 21, 2017 at 2:06:34 PM UTC-5, Ambrose

Post by Ambrose Bonnaire-Sergeant
Try using
:classifier "slim"
in the core.typed dep to remove AOT files. Does that help?

Post by Peter Fraenkel
When a project has a dependency on versions of core.typed 0.3.26 or
"WARNING: CIDER's version (0.14.0) does not match cider-nrepl's
version (nil). Things will break!”.
The same thing happens with later versions of cider as well. This was
reported to me as a problem with squiggly clojure
<https://github.com/clojure-emacs/squiggly-clojure>, but the problem can
be replicated with only the dependency on typed. It doesn't appear that
things in fact do break, and you can verify from lein deps or
cider.nrepl.version/version that the version is in fact correct. The logic
by which cider decides what version of cider-nrepl it thinks it's running
is not clear to me.
Is this a known problem? I am wondering if it has anything to do with AOT?

[Ambrose Bonnaire-Sergeant]

Where does this error message originate?

Post by Peter Fraenkel
That "fixes" the problem, so my unfounded intuition that AOT was involved
seems to be correct. I still have no idea why....
On Tuesday, February 21, 2017 at 2:06:34 PM UTC-5, Ambrose

Post by Ambrose Bonnaire-Sergeant
Try using
:classifier "slim"
in the core.typed dep to remove AOT files. Does that help?

Post by Peter Fraenkel
When a project has a dependency on versions of core.typed 0.3.26 or
"WARNING: CIDER's version (0.14.0) does not match cider-nrepl's
version (nil). Things will break!”.
The same thing happens with later versions of cider as well. This was
reported to me as a problem with squiggly clojure
<https://github.com/clojure-emacs/squiggly-clojure>, but the problem
can be replicated with only the dependency on typed. It doesn't appear
that things in fact do break, and you can verify from lein deps or
cider.nrepl.version/version that the version is in fact correct. The logic
by which cider decides what version of cider-nrepl it thinks it's running
is not clear to me.
Is this a known problem? I am wondering if it has anything to do with AOT?