Spawn tasks with current tracing subscriber #1138
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Before this PR, tracing logs work with the default subscriber (which is the usual case), but when one sets a custom tracing subscriber, it isn't passed across
tokio::spawnboundaries.In this PR I'm adding the method
.with_current_subscriber()to server tasks. This allows the logging subscriber to be carried into the spawned tasks.My use case is capturing logging for integration tests, for which I need to set a custom tracing subscriber. I think this PR shouldn't change anything in the common case of a global subscriber.