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

fsnotify 0.3 #3678

Closed
4 of 5 tasks
snoyberg opened this issue May 29, 2018 · 7 comments
Closed
4 of 5 tasks

fsnotify 0.3 #3678

snoyberg opened this issue May 29, 2018 · 7 comments

Comments

@snoyberg
Copy link
Contributor

snoyberg commented May 29, 2018

fsnotify-0.3.0.0 (Michael Snoyman michael@snoyman.com @snoyberg) is out of bounds for:

@byorgey
Copy link
Contributor

byorgey commented May 29, 2018

Tested and revised diagrams-lib on Hackage to allow fsnotify < 0.4.

@bartavelle
Copy link
Contributor

Shipped filecache 0.4.0.

snoyberg added a commit that referenced this issue May 29, 2018
@domenkozar
Copy link
Contributor

@rkaippully any progress on starter? :)

@rkaippully
Copy link
Contributor

starter 0.3.0 released.

@bergmark bergmark reopened this Jun 23, 2018
@bergmark
Copy link
Member

Blocked by kelemzol/watch#3

@simonmichael
Copy link
Contributor

In case you didn’t see it: at kelemzol/watch#3 I ask for fsnotify 0.3 to be prioritised over fswatch.

@DanBurton
Copy link
Contributor

The following have been removed from the build plan due to build failures with fsnotify-0.3:

And the following due to fswatch's removal:

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

8 participants