Evan Zacks

One approach is something like https://github.com/CompSciLauren/awesome-git-hooks/pull/30/commits/68793f5518110efb6af2fa48634f95629bb8070b where we install the hook during `@setup` and restore the original (if any) during `@teardown`. It's not the most elegant, and there is some...

I'll take this one.

I'll take this one.

You can avoid purging dangling symlinks by applying zackse/boto_rsync@1813325e20006be131745ba4aca1091ded17ab28, which will skip any files that cannot be stat()'ed.

Hi @delner, thanks for your continued investigation on this. Can you confirm whether your test apps show the expected/matching counts for metrics as well as traces? Not to interrupt this...

Hi @delner, thank you for your response and investigation. We were able to replicate the problem where certain metrics/spans go missing in an isolated/test environment. It seems related to distributed...

Here is the trace flame graph before upgrading the downstream service to 1.3.0: After:

Thanks, @delner. We really appreciate the continued work on this. 👍

It all comes down to available cycles... Can't commit just yet, but I'm game for discussion. A few thoughts: If we don't have a convention for storing symlink metadata in...

Yes, good point -- I should have written "ancestor" where I wrote "parent". I think it is relatively easy to check for direct ancestors to the sync source directory, or...