Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to Clojure 1.8 - byte-streams 0.2.2 #10

Open
drbobbeaty opened this issue Jun 22, 2016 · 4 comments
Open

Update to Clojure 1.8 - byte-streams 0.2.2 #10

drbobbeaty opened this issue Jun 22, 2016 · 4 comments

Comments

@drbobbeaty
Copy link
Contributor

I'm starting to work with this library and Clojure 1.8.0, and as-is, this isn't working well - but if I preload the byte-streams v0.2.2 and exclude that from durable-queues, then it seems to work just fine.

I would suggest upgrading to [byte-streams "0.2.2"] in this project, and then it should be fine.

@jaju
Copy link
Contributor

jaju commented Jul 19, 2016

@drbobbeaty - Just curious. I am using durable-queue, and am using 1.9.0-alpha10. Haven't seen anything weird for small runs. What do you mean by "isn't working well?"

Thanks.

@drbobbeaty
Copy link
Contributor Author

That the version of byte-streams needs to be updated. A new clojure dev might not know to exclude the older version from this library, and preload the newer one. Given the relationship of the authors (same guys :) it seems a simple fix for this library.

That's it. Just the version, as I've noted.

@ztellman
Copy link
Contributor

What is the issue you're seeing, specifically? I wouldn't have guessed
there would be an issue.
On Tue, Jul 19, 2016 at 11:20 AM Bob Beaty [email protected] wrote:

That the version of byte-streams needs to be updated. A new clojure dev
might not know to exclude the older version from this library, and
preload the newer one. Given the relationship of the authors (same guys :)
it seems a simple fix for this library.

That's it. Just the version, as I've noted.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#10 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB6PwCL_ZAoEHhN2Ok8RxM_-Zbt7H36ks5qXJb5gaJpZM4I8PzA
.

@drbobbeaty
Copy link
Contributor Author

Sorry... just saw this...

There is no breaking issue with the code. This is simply a lein deps :tree issue where you see the conflict in the versions.

The code runs, but in a large project, it's a little more maintenance than necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants