twice set for stream.readDeadline

[terryding77]

go-yamux/stream.go

Lines 311 to 325 in 736c1cb

	func (s *Stream) forceClose() {
	s.stateLock.Lock()
	switch s.state {
	case streamClosed:
	// Already successfully closed. It just hasn't been removed from
	// the list of streams yet.
	default:
	s.state = streamReset
	}
	s.stateLock.Unlock()
	s.notifyWaiting()
	s.readDeadline.set(time.Time{})
	s.readDeadline.set(time.Time{})
	}

go-yamux/stream.go

Lines 328 to 333 in 736c1cb

	func (s *Stream) cleanup() {
	s.session.closeStream(s.id)
	s.readDeadline.set(time.Time{})
	s.readDeadline.set(time.Time{})
	}

I find in Stream.forceClose and stream.cleanup functions, we set the readDeadline twice, is there any trick for deadline? or it just the wrong typo for writeDeadline?

[Stebalien]

Nice catch! Yeah, that's wrong. It likely only leaked timers for a short period of time but still...

Mind submitting a PR to fix it?