Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ttilley/fssm issues and pull requests
#54 - Replace deprecated `exists?` by `exist?`
Pull Request -
State: open - Opened by boutil over 1 year ago
#53 - fixed not working use rb-inotify
Pull Request -
State: open - Opened by webuilder240 over 7 years ago
- 1 comment
#52 - Update README
Pull Request -
State: closed - Opened by dhruvaljain over 8 years ago
- 1 comment
#51 - Fix tests for new rspec versions
Pull Request -
State: closed - Opened by lucasmoura almost 9 years ago
#50 - Add license to gemspec
Pull Request -
State: open - Opened by codegoalie about 10 years ago
#49 - Please teach me how to monitoring unit test
Issue -
State: open - Opened by onigra over 10 years ago
#48 - Can FSSM use regular expression to match string not containing a word?
Issue -
State: open - Opened by castus over 10 years ago
#47 - notification instead of polling on windows
Issue -
State: open - Opened by ccoenen almost 11 years ago
#46 - Bugfix for FSSM::Tree::Cache on UNC.
Pull Request -
State: open - Opened by kou1okada almost 11 years ago
#45 - Fixed FSSM::Pathname.segments method to work correctly.
Pull Request -
State: closed - Opened by kou1okada about 11 years ago
#44 - Fixed FSSM::Pathname.segments method to work correctly.
Pull Request -
State: closed - Opened by kou1okada about 11 years ago
#43 - Fixed FSSM::Pathname.segments method to work correctly.
Pull Request -
State: closed - Opened by kou1okada about 11 years ago
#42 - License missing from gemspec
Issue -
State: open - Opened by bf4 over 11 years ago
#41 - FSSM is essentially dead
Issue -
State: closed - Opened by bhaak about 12 years ago
- 1 comment
#40 - Suppress undesired recommendation
Issue -
State: closed - Opened by woto almost 13 years ago
#39 - Callback for all changes
Issue -
State: closed - Opened by ai almost 13 years ago
- 1 comment
#38 - Fssm breaks with jruby
Issue -
State: closed - Opened by dhavaldeshpande about 13 years ago
- 12 comments
#37 - fssm 0.2.8 builds native extension in wrong place
Issue -
State: closed - Opened by codekitchen about 13 years ago
- 2 comments
#36 - Do not alter $LOAD_PATH from library itself
Issue -
State: closed - Opened by luislavena about 13 years ago
- 6 comments
#35 - Detecting modifications between 2 given times.
Issue -
State: closed - Opened by capitanscott about 13 years ago
- 3 comments
#34 - add rbfchange
Pull Request -
State: closed - Opened by drvo about 13 years ago
- 1 comment
#33 - Use RbConfig instead of deprecated Config
Pull Request -
State: closed - Opened by mattbrictson over 13 years ago
- 9 comments
#32 - FSSM Crashes for filename changes
Issue -
State: closed - Opened by zauberparacelsus over 13 years ago
- 3 comments
#31 - "An optimized backend is available for this platform!"
Issue -
State: closed - Opened by mathiasschopmans over 13 years ago
- 6 comments
#30 - fssm 0.2.7 fails tests with rb-inotify 0.8.6 installed
Issue -
State: closed - Opened by graaff over 13 years ago
- 5 comments
#29 - Incorrect path segments for cygwin path
Issue -
State: closed - Opened by sankl over 13 years ago
- 1 comment
#28 - rb-inotify breaks threads
Issue -
State: closed - Opened by me over 13 years ago
- 5 comments
#27 - crazy talk from FSSM on Ubuntu
Issue -
State: closed - Opened by mepatterson almost 14 years ago
- 6 comments
#26 - rb-fsevent backend doesn't work
Issue -
State: closed - Opened by chriseppstein almost 14 years ago
- 6 comments
Labels: backend, rb-fsevent, critical
#25 - improve documentation around using FSSM inside an OO class
Issue -
State: open - Opened by mepatterson almost 14 years ago
- 2 comments
#24 - Multiple monitors not executing all Ruby code
Issue -
State: closed - Opened by mybuddymichael almost 14 years ago
- 3 comments
#23 - rb-fsevent backend can only monitor a single path at a time
Issue -
State: closed - Opened by philsmy about 14 years ago
- 16 comments
#22 - Can FSSM watch a file by name ?
Issue -
State: closed - Opened by jtilghman about 14 years ago
- 2 comments
#21 - fssm should listen close event on inotify backend
Issue -
State: closed - Opened by esamattis about 14 years ago
- 9 comments
Labels: backend
#20 - investigate Tree implementation in em-dir-watcher
Issue -
State: open - Opened by ttilley about 14 years ago
Labels: feature
#19 - FSSM when watching a text file, throws error when file is changed.
Issue -
State: closed - Opened by jtilghman about 14 years ago
- 10 comments
Labels: Pathname, windows
#18 - Monitor directories
Issue -
State: closed - Opened by masylum about 14 years ago
- 3 comments
#17 - Support rb-fsevent
Issue -
State: closed - Opened by nex3 about 14 years ago
- 3 comments
#16 - FSSM::Monitor.file doesn't work
Issue -
State: closed - Opened by nex3 about 14 years ago
- 5 comments
#15 - Use Pathname as superclass for FSSM::Pathname instead of String
Pull Request -
State: closed - Opened by Twisol about 14 years ago
- 1 comment
#14 - Patch for FSSM::Pathname to work on Rubinius
Pull Request -
State: closed - Opened by Twisol about 14 years ago
- 6 comments
#13 - Pathname#to_s stack overflow on Rubinius
Issue -
State: closed - Opened by Twisol about 14 years ago
- 7 comments
#12 - symlink resolution broken with fsevents
Issue -
State: closed - Opened by nemurimasu over 14 years ago
- 1 comment
Labels: backend
#11 - Support for CREATE vs CLOSE_WRITE
Issue -
State: closed - Opened by mpawl over 14 years ago
- 2 comments
#10 - Polling Backend, Errno::ENOENT on some deletes (race condition?)
Issue -
State: closed - Opened by rickhull almost 15 years ago
- 1 comment
#9 - API oddity: why two arguments for block?
Issue -
State: closed - Opened by denisdefreyne almost 15 years ago
- 1 comment
#8 - Warning: Unable to load rb-inotify >= 0.3.0. Inotify will be unavailable.
Issue -
State: closed - Opened by lwille almost 15 years ago
- 2 comments
#7 - 100% CPU usage then crashes on Ubuntu 9.10
Issue -
State: closed - Opened by alexebird almost 15 years ago
- 3 comments
#6 - inotify backend doesn't re-watch the directory after it's been deleted
Issue -
State: closed - Opened by nex3 about 15 years ago
- 2 comments
#5 - Too many inotify events are caught
Issue -
State: closed - Opened by nex3 about 15 years ago
- 1 comment
#4 - Odd Bug with rb-inotify backend
Issue -
State: closed - Opened by nex3 about 15 years ago
- 2 comments
#3 - is it fixed for ubuntu
Issue -
State: closed - Opened by millisami about 15 years ago
- 3 comments
#2 - JRuby Support
Issue -
State: closed - Opened by chriseppstein about 15 years ago
- 5 comments
#1 - Windows locking issue
Issue -
State: closed - Opened by chriseppstein over 15 years ago
- 8 comments