github/Discord.Net
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DefaultWebSocketClient's internal methods should not use a canceltoken on locks

Browse Source
This commit is contained in:
RogueException
2016-08-17 11:53:32 -03:00
parent 0b25554c31
commit ee4cc96b2c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/Discord.Net/Net/WebSockets/DefaultWebsocketClient.cs
View File

@@ -51,7 +51,7 @@ namespace Discord.Net.WebSockets
public async Task ConnectAsync(string host)
{
await _sendLock.WaitAsync(_cancelToken).ConfigureAwait(false);
await _sendLock.WaitAsync().ConfigureAwait(false);
try
{
await ConnectInternalAsync(host);
@@ -83,7 +83,7 @@ namespace Discord.Net.WebSockets
public async Task DisconnectAsync()
{
await _sendLock.WaitAsync(_cancelToken).ConfigureAwait(false);
await _sendLock.WaitAsync().ConfigureAwait(false);
try
{
await DisconnectInternalAsync();
@@ -118,7 +118,7 @@ namespace Discord.Net.WebSockets
public async Task SendAsync(byte[] data, int index, int count, bool isText)
{
await _sendLock.WaitAsync(_cancelToken).ConfigureAwait(false);
await _sendLock.WaitAsync().ConfigureAwait(false);
try
{
if (_client == null) return;