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

Unreachable error with git repository (chmod event) #99

Closed
Kerollmops opened this issue Nov 13, 2016 · 1 comment
Closed

Unreachable error with git repository (chmod event) #99

Kerollmops opened this issue Nov 13, 2016 · 1 comment

Comments

@Kerollmops
Copy link

Kerollmops commented Nov 13, 2016

Trying some events with git actions, I found some strange behaviour.

I am on OSX Sierra beta 10.12.2 (16C41b)

To reproduce this:

$> # listen to this directory
$> RUST_BACKTRACE=1 ./target/release/examples/monitor_debounced /tmp/hello
$>
$> mkdir /tmp/hello
$> cd /tmp/hello
$> touch hello
$> git init
$> RUST_BACKTRACE=1 ./target/release/examples/monitor_debounced /tmp/hello
watching /tmp/hello
Create("/private/tmp/hello/hello")
Some(CREATE) # that's my println debug at line 117
thread '<unnamed>' panicked at 'internal error: entered unreachable code', src/debounce/mod.rs:118
stack backtrace:
   1:        0x1003baada - std::sys::imp::backtrace::tracing::imp::write::he3d1bfbdbf113480
   2:        0x1003bde6f - std::panicking::default_hook::{{closure}}::h575f1b40d2e88f07
   3:        0x1003bcb5f - std::panicking::default_hook::h3d5dccce8125d0cf
   4:        0x1003bd196 - std::panicking::rust_panic_with_hook::h00b81bb3dcbd51f2
   5:        0x10034bb63 - std::panicking::begin_panic::h70ee11343cda1bc2
   6:        0x1003a94d8 - notify::debounce::Debounce::check_partial_rename::hcbf233e36f356a5c
   7:        0x1003a9e62 - notify::debounce::Debounce::event::h1601b8a062e67e75
   8:        0x1003a8172 - notify::debounce::EventTx::send::h9136acde8e818b2e
   9:        0x1003a33d1 - notify::fsevent::send_pending_rename_event::h8813d6188d6441e8
  10:        0x1003a5169 - notify::fsevent::callback::h843bd243c277573c
  11:     0x7fffa703db02 - implementation_callback_rpc
  12:     0x7fffa703b70d - _Xcallback_rpc
  13:     0x7fffa703b7cb - FSEventsD2F_server
  14:     0x7fffa7040fec - FSEventsClientProcessMessageCallback
  15:     0x7fffa5e517dc - __CFMachPortPerform
  16:     0x7fffa5e516c8 - __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__
  17:     0x7fffa5e51640 - __CFRunLoopDoSource1
  18:     0x7fffa5e49524 - __CFRunLoopRun
  19:     0x7fffa5e48973 - CFRunLoopRunSpecific
  20:     0x7fffa5e884f0 - CFRunLoopRun
  21:        0x1003af6c8 - notify::fsevent::FsEventWatcher::run::{{closure}}::hf9485ba872fe490f
  22:        0x1003a1cba - <std::panic::AssertUnwindSafe<F> as core::ops::FnOnce<()>>::call_once::h0986629d799f6b84
  23:        0x10034c4c3 - std::panicking::try::do_call::h075cdc0f1c38c144
  24:        0x1003be42a - __rust_maybe_catch_panic
  25:        0x10034c0f2 - std::panicking::try::h83b082fadfa7802d
  26:        0x10034a16e - std::panic::catch_unwind::h4efcd890cc4b3a3b
  27:        0x1003aeea2 - std::thread::Builder::spawn::{{closure}}::he27652165ddf436f
  28:        0x10037c783 - <F as alloc::boxed::FnBox<A>>::call_box::h95de920981a48031
  29:        0x1003bc5a4 - std::sys::imp::thread::Thread::new::thread_start::h990fb082eb5abe34
  30:     0x7fffbb7c6aaa - _pthread_body
  31:     0x7fffbb7c69f6 - _pthread_start
@RHavar
Copy link

RHavar commented Nov 14, 2016

Another (possibly easier) way to trigger this is in macos is to watch ~/Desktop and then take a screenshot.

I get the same thing that causes the error:
Some(CREATE) # that's my println debug at line 117

@dfaust dfaust closed this as completed in 6f58cce Nov 14, 2016
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

2 participants