Bump Discord.Net from 2.4.0 to 3.12.0 #130
Annotations
10 errors and 11 warnings
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L52
No overload for 'DiscordUserUpdated' matches delegate 'Func<Cacheable<SocketGuildUser, ulong>, SocketGuildUser, Task>'
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L67
'SocketUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L68
'SocketUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L68
'SocketUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L90
'SocketGuildUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketGuildUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L90
'SocketUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L115
Operator '==' cannot be applied to operands of type 'method group' and 'int'
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L123
'SocketUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L130
'SocketUser' does not contain a definition for 'Activity' and no accessible extension method 'Activity' accepting a first argument of type 'SocketUser' could be found (are you missing a using directive or an assembly reference?)
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L130
Argument 1: cannot convert from 'method group' to 'ReadOnlySpan<char>'
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
src/Sergen.Core/Services/ServerFileStore/LocalServerFileStore.cs#L30
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Core/Services/Containers/Docker/DockerInterface.cs#L90
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Core/Services/Containers/Docker/DockerInterface.cs#L324
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Main/Services/SergenBackgroundWorker.cs#L19
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Main/Services/SergenBackgroundWorker.cs#L25
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Main/Services/Chat/ChatWhitelist/DiscordAllowList.cs#L59
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L108
The result of the expression is always 'true' since a value of type 'DateTime' is never equal to 'null' of type 'DateTime?'
|
src/Sergen.Main/Services/Chat/ChatEventHandler/Discord/DiscordEventHandler.cs#L175
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Core/Services/ServerFileStore/LocalServerFileStore.cs#L30
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
src/Sergen.Core/Services/Containers/Docker/DockerInterface.cs#L90
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
The logs for this run have expired and are no longer available.
Loading