SignalR Functional Tests very slow on some TC agents when VS Test Diagnostics enabled

SignalR Tests were running very slowly on one of the build agents (aspnetci-a-100), and it looked to be due to the fact that VS Test diagnostics were on. It looks like the logging may have been slowing the tests down enough on that agent (and only that agent) so that it took >60 mins to run the whole build, causing TeamCity to shut it down.
We're not yet sure exactly why this is happening, so for now I have simply blocked the SignalR project build from running on that agent, to work around the issue (other agents are not having this problem). This bug is to keep track of the issue and allow us to track further investigation (now that the immediate issue is mitigated).
cc @ryanbrandenburg
I was seeing long-running test notifications like the following:
[16:34:38]  [xUnit.net 00:39:52.25] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: WebSockets, path: "/hubT")', Elapsed: 00:02:30
[16:35:08]  [xUnit.net 00:40:23.19] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: WebSockets, path: "/hubT")', Elapsed: 00:03:01
[16:36:22]  [xUnit.net 00:41:35.97] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:00:57
[16:36:53]  [xUnit.net 00:42:07.74] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:01:29
[16:37:24]  [xUnit.net 00:42:38.97] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:02:00
[16:37:55]  [xUnit.net 00:43:09.98] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:02:31
[16:38:26]  [xUnit.net 00:43:40.93] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:03:02
[16:38:58]  [xUnit.net 00:44:11.92] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:03:33
[16:39:29]  [xUnit.net 00:44:43.18] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:04:04
[16:40:00]  [xUnit.net 00:45:14.31] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:04:35
[16:40:31]  [xUnit.net 00:45:45.17] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "json", transportType: LongPolling, path: "/default")', Elapsed: 00:05:06
[16:41:50]  [xUnit.net 00:47:04.49] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/hubT")', Elapsed: 00:00:58
[16:42:20]  [xUnit.net 00:47:35.05] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/hubT")', Elapsed: 00:01:29
[16:42:52]  [xUnit.net 00:48:05.79] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/hubT")', Elapsed: 00:01:59
[16:43:23]  [xUnit.net 00:48:37.06] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/hubT")', Elapsed: 00:02:31
[16:43:54]  [xUnit.net 00:49:08.38] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/hubT")', Elapsed: 00:03:02
[16:45:01]  [xUnit.net 00:50:15.12] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/dynamic")', Elapsed: 00:00:59
[16:45:32]  [xUnit.net 00:50:46.68] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/dynamic")', Elapsed: 00:01:31
[16:46:04]  [xUnit.net 00:51:17.86] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/dynamic")', Elapsed: 00:02:02
[16:46:35]  [xUnit.net 00:51:49.51] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/dynamic")', Elapsed: 00:02:33
[16:47:06]  [xUnit.net 00:52:20.66] Microsoft.AspNetCore.SignalR.Client.FunctionalTests: [Long Running Test] 'Microsoft.AspNetCore.SignalR.Client.FunctionalTests.HubConnectionTests.CanStopAndStartConnection(protocolName: "messagepack", transportType: WebSockets, path: "/dynamic")', Elapsed: 00:03:05

However, the logs for the tests themselves showed very short running times (0.025281s in the example below):
[0.001s] [TestLifetime] [Information] Starting test "CanStopAndStartConnection_json_WebSockets_dynamic" at "2018-07-18T22:55:29"
[0.001s] [ServerLogScope] [Information] Server log scope started.
[0.001s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] Waiting on Connection Lock in StartAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:288).
[0.001s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] Starting HubConnection.
[0.001s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] Starting HttpConnection.
[0.001s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] Establishing connection with server at 'http://<IP_ADDRESS>:49655/dynamic'.
[0.001s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.LoggingHttpMessageHandler] [Verbose] Sending HTTP request POST 'http://<IP_ADDRESS>:49655/dynamic/negotiate'.
[0.002s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URP" started.
[0.003s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request starting HTTP/1.1 POST http://<IP_ADDRESS>:49655/dynamic/negotiate  0
[0.003s] [SERVER Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler] [Debug] AuthenticationScheme: Bearer was not authenticated.
[0.003s] [SERVER Microsoft.AspNetCore.Routing.RouteBase] [Debug] Request successfully matched the route with name '(null)' and template '/dynamic/negotiate'.
[0.003s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager] [Debug] New connection eElBhrFObvfkcSX0p5LLsA created.
[0.003s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher] [Debug] eElBhrFObvfkcSX0p5LLsA - Sending negotiation response.
[0.003s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URP" completed keep alive response.
[0.004s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] Established connection 'eElBhrFObvfkcSX0p5LLsA' with the server.
[0.004s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request finished in 1.1844ms 200 application/json
[0.004s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Starting transport 'WebSockets' with Url: http://<IP_ADDRESS>:49655/dynamic?id=eElBhrFObvfkcSX0p5LLsA.
[0.004s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Information] eElBhrFObvfkcSX0p5LLsA - Starting transport. Transfer mode: Text. Url: 'ws://<IP_ADDRESS>:49655/dynamic?id=eElBhrFObvfkcSX0p5LLsA'.
[0.004s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URQ" started.
[0.005s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request starting HTTP/1.1 GET http://<IP_ADDRESS>:49655/dynamic?id=eElBhrFObvfkcSX0p5LLsA
[0.005s] [SERVER Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler] [Debug] AuthenticationScheme: Bearer was not authenticated.
[0.005s] [SERVER Microsoft.AspNetCore.Routing.RouteBase] [Debug] Request successfully matched the route with name '(null)' and template '/dynamic'.
[0.005s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher] [Debug] eElBhrFObvfkcSX0p5LLsA - Establishing new connection.
[0.005s] [SERVER Microsoft.AspNetCore.SignalR.HubConnectionHandler] [Debug] eElBhrFObvfkcSX0p5LLsA - OnConnectedAsync started.
[0.005s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Socket opened using Sub-Protocol: '(null)'.
[0.007s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Transport 'WebSockets' started.
[0.007s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Information] eElBhrFObvfkcSX0p5LLsA - HttpConnection Started.
[0.007s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Information] eElBhrFObvfkcSX0p5LLsA - Using HubProtocol 'json v1'.
[0.007s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Sending Hub Handshake.
[0.007s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Received message from application. Payload size: 32.
[0.007s] [SERVER Microsoft.AspNetCore.SignalR.Internal.DefaultHubProtocolResolver] [Debug] eElBhrFObvfkcSX0p5LLsA - Found protocol implementation for requested protocol: json.
[0.008s] [SERVER Microsoft.AspNetCore.SignalR.HubConnectionContext] [Information] eElBhrFObvfkcSX0p5LLsA - Completed connection handshake. Using HubProtocol 'json'.
[0.008s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Message received. Type: Text, size: 19, EndOfMessage: True.
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Handshake with server complete.
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Receive loop starting.
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Sending PingMessage message.
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Sending PingMessage message completed.
[0.008s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Received message from application. Payload size: 11.
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Information] eElBhrFObvfkcSX0p5LLsA - HubConnection started.
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Releasing Connection Lock in StartAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:331).
[0.008s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Waiting on Connection Lock in InvokeCoreAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:442).
[0.008s] [Microsoft.AspNetCore.SignalR.Client.Internal.InvocationRequest.NonStreaming] [Verbose] eElBhrFObvfkcSX0p5LLsA - Invocation 1 created.
[0.009s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Preparing blocking invocation '1' of 'Echo', with return type 'System.String' and 1 argument(s).
[0.009s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Registering Invocation ID '1' for tracking.
[0.009s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Issuing Invocation '1': System.String Echo(System.String).
[0.009s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Sending InvocationMessage message '1'.
[0.009s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Sending InvocationMessage message '1' completed.
[0.009s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Received message from application. Payload size: 70.
[0.009s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Releasing Connection Lock in InvokeCoreAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:455).
[0.009s] [SERVER Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher] [Debug] eElBhrFObvfkcSX0p5LLsA - Received hub invocation: InvocationMessage { InvocationId: "1", Target: "Echo", Arguments: [ SignalR ] }.
[0.009s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Message received. Type: Text, size: 49, EndOfMessage: True.
[0.010s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Processing 49 byte message from server.
[0.010s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Resetting keep-alive timer, received a message from the server.
[0.010s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Received Completion for Invocation 1.
[0.010s] [Microsoft.AspNetCore.SignalR.Client.Internal.InvocationRequest.NonStreaming] [Verbose] eElBhrFObvfkcSX0p5LLsA - Invocation 1 marked as completed.
[0.010s] [Microsoft.AspNetCore.SignalR.Client.Internal.InvocationRequest.NonStreaming] [Verbose] eElBhrFObvfkcSX0p5LLsA - Invocation 1 disposed.
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Waiting on Connection Lock in StopAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:347).
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Releasing Connection Lock in StopAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:374).
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Stopping HubConnection.
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Terminating receive loop.
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Waiting for the receive loop to terminate.
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Waiting on Connection Lock in ReceiveLoop (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:840).
[0.011s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Releasing Connection Lock in ReceiveLoop (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:849).
[0.012s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Disposing HttpConnection.
[0.012s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Information] eElBhrFObvfkcSX0p5LLsA - Transport is stopping.
[0.012s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Send loop stopped.
[0.012s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Waiting for the application to finish sending data.
[0.012s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Transport stopped.
[0.012s] [SERVER Microsoft.AspNetCore.SignalR.HubConnectionHandler] [Debug] eElBhrFObvfkcSX0p5LLsA - OnConnectedAsync ending.
[0.012s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Information] eElBhrFObvfkcSX0p5LLsA - HttpConnection Disposed.
[0.012s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URQ" reset.
[0.012s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Socket closed.
[0.012s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - Canceling all outstanding invocations.
[0.012s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URP" received FIN.
[0.012s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] eElBhrFObvfkcSX0p5LLsA - Shutting down connection.
[0.012s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URQ" disconnecting.
[0.012s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager] [Debug] eElBhrFObvfkcSX0p5LLsA - Removing connection eElBhrFObvfkcSX0p5LLsA from the list of connections.
[0.012s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] eElBhrFObvfkcSX0p5LLsA - HubConnection stopped.
[0.012s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URQ" reset.
[0.012s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URP" disconnecting.
[0.012s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] Waiting on Connection Lock in StartAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:288).
[0.013s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URQ" sending FIN.
[0.013s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request finished in 7.4594ms 101
[0.013s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URP" sending FIN.
[0.013s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] Starting HubConnection.
[0.013s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URQ" stopped.
[0.013s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] Starting HttpConnection.
[0.013s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] Establishing connection with server at 'http://<IP_ADDRESS>:49655/dynamic'.
[0.013s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] eElBhrFObvfkcSX0p5LLsA - Receive loop stopped.
[0.013s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URP" stopped.
[0.013s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.LoggingHttpMessageHandler] [Verbose] Sending HTTP request POST 'http://<IP_ADDRESS>:49655/dynamic/negotiate'.
[0.014s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URR" started.
[0.014s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request starting HTTP/1.1 POST http://<IP_ADDRESS>:49655/dynamic/negotiate  0
[0.014s] [SERVER Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler] [Debug] AuthenticationScheme: Bearer was not authenticated.
[0.014s] [SERVER Microsoft.AspNetCore.Routing.RouteBase] [Debug] Request successfully matched the route with name '(null)' and template '/dynamic/negotiate'.
[0.014s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionManager] [Debug] New connection 3wLQUDyohkcmLBP0ohjpaw created.
[0.015s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Sending negotiation response.
[0.015s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URR" completed keep alive response.
[0.015s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] Established connection '3wLQUDyohkcmLBP0ohjpaw' with the server.
[0.015s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request finished in 1.0609ms 200 application/json
[0.015s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Starting transport 'WebSockets' with Url: http://<IP_ADDRESS>:49655/dynamic?id=3wLQUDyohkcmLBP0ohjpaw.
[0.015s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Information] 3wLQUDyohkcmLBP0ohjpaw - Starting transport. Transfer mode: Text. Url: 'ws://<IP_ADDRESS>:49655/dynamic?id=3wLQUDyohkcmLBP0ohjpaw'.
[0.016s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URS" started.
[0.016s] [SERVER Microsoft.AspNetCore.Hosting.Internal.WebHost] [Information] Request starting HTTP/1.1 GET http://<IP_ADDRESS>:49655/dynamic?id=3wLQUDyohkcmLBP0ohjpaw
[0.016s] [SERVER Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler] [Debug] AuthenticationScheme: Bearer was not authenticated.
[0.016s] [SERVER Microsoft.AspNetCore.Routing.RouteBase] [Debug] Request successfully matched the route with name '(null)' and template '/dynamic'.
[0.017s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.HttpConnectionDispatcher] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Establishing new connection.
[0.017s] [SERVER Microsoft.AspNetCore.SignalR.HubConnectionHandler] [Debug] 3wLQUDyohkcmLBP0ohjpaw - OnConnectedAsync started.
[0.017s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Socket opened using Sub-Protocol: '(null)'.
[0.017s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Transport 'WebSockets' started.
[0.017s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Information] 3wLQUDyohkcmLBP0ohjpaw - HttpConnection Started.
[0.017s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Information] 3wLQUDyohkcmLBP0ohjpaw - Using HubProtocol 'json v1'.
[0.017s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Sending Hub Handshake.
[0.018s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Received message from application. Payload size: 32.
[0.018s] [SERVER Microsoft.AspNetCore.SignalR.Internal.DefaultHubProtocolResolver] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Found protocol implementation for requested protocol: json.
[0.018s] [SERVER Microsoft.AspNetCore.SignalR.HubConnectionContext] [Information] 3wLQUDyohkcmLBP0ohjpaw - Completed connection handshake. Using HubProtocol 'json'.
[0.018s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Message received. Type: Text, size: 19, EndOfMessage: True.
[0.018s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Handshake with server complete.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Receive loop starting.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Sending PingMessage message.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Sending PingMessage message completed.
[0.019s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Received message from application. Payload size: 11.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Information] 3wLQUDyohkcmLBP0ohjpaw - HubConnection started.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Releasing Connection Lock in StartAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:331).
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Waiting on Connection Lock in InvokeCoreAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:442).
[0.019s] [Microsoft.AspNetCore.SignalR.Client.Internal.InvocationRequest.NonStreaming] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Invocation 1 created.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Preparing blocking invocation '1' of 'Echo', with return type 'System.String' and 1 argument(s).
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Registering Invocation ID '1' for tracking.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Issuing Invocation '1': System.String Echo(System.String).
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Sending InvocationMessage message '1'.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Sending InvocationMessage message '1' completed.
[0.019s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Received message from application. Payload size: 70.
[0.019s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Releasing Connection Lock in InvokeCoreAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:455).
[0.020s] [SERVER Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Received hub invocation: InvocationMessage { InvocationId: "1", Target: "Echo", Arguments: [ SignalR ] }.
[0.020s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Message received. Type: Text, size: 49, EndOfMessage: True.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Processing 49 byte message from server.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Resetting keep-alive timer, received a message from the server.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Received Completion for Invocation 1.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.Internal.InvocationRequest.NonStreaming] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Invocation 1 marked as completed.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.Internal.InvocationRequest.NonStreaming] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Invocation 1 disposed.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Waiting on Connection Lock in StopAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:347).
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Releasing Connection Lock in StopAsyncCore (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:374).
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Stopping HubConnection.
[0.020s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Terminating receive loop.
[0.021s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Waiting for the receive loop to terminate.
[0.021s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Waiting on Connection Lock in ReceiveLoop (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:840).
[0.021s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Releasing Connection Lock in ReceiveLoop (/_/src/Microsoft.AspNetCore.SignalR.Client.Core/HubConnection.cs:849).
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Disposing HttpConnection.
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Information] 3wLQUDyohkcmLBP0ohjpaw - Transport is stopping.
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Send loop stopped.
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Message received. Type: Text, size: 11, EndOfMessage: True.
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Receive loop stopped.
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Transport stopped.
[0.021s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Waiting for the application to finish sending data.
[0.021s] [Microsoft.AspNetCore.Http.Connections.Client.HttpConnection] [Information] 3wLQUDyohkcmLBP0ohjpaw - HttpConnection Disposed.
[0.021s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URS" reset.
[0.021s] [SERVER Microsoft.AspNetCore.Http.Connections.Internal.Transports.WebSocketsTransport] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Socket closed.
[0.026s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - Canceling all outstanding invocations.
[0.026s] [SERVER Microsoft.AspNetCore.Server.Kestrel] [Debug] Connection id "0HLFD05SJ7URS" disconnecting.
[0.026s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Verbose] 3wLQUDyohkcmLBP0ohjpaw - Shutting down connection.
[0.026s] [SERVER Microsoft.AspNetCore.SignalR.HubConnectionHandler] [Debug] 3wLQUDyohkcmLBP0ohjpaw - OnConnectedAsync ending.
[0.026s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URR" received FIN.
[0.026s] [Microsoft.AspNetCore.SignalR.Client.HubConnection] [Debug] 3wLQUDyohkcmLBP0ohjpaw - HubConnection stopped.
[0.026s] [ServerLogScope] [Information] Server log scope stopped.
[0.026s] [SERVER Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HLFD05SJ7URS" reset.
[0.026s] [TestLifetime] [Information] Finished test "CanStopAndStartConnection_json_WebSockets_dynamic" in 0.025281s

I'm going to close this as it's mostly for tracking what happened and how we worked around it. It looked like a file locking issue on agent 100, so if it reoccurrs we can revisit the issue.


seems the RSS feed is not longer active, so breaks the whole module

Was trying to use this to watch for when matches go live, so I could automatically start a hltv-livescore but I was getting a strange error. I've looked at the URL you are requesting to get the data and it seems that it is no longer active

Yep, saw that a couple weeks ago. Either we'll need to find the new API end point or scrape HLTV.

Sorry this took a while – newest version should fix it.


Person state continuous trigger.

Problem/Motivation
Latest release of v0.8.0 has an issue with the listen_state on person entities.
Expected behavior
The listen state should behave as any other listen_state call.
Actual behavior
When you listen for a state change on a person entity the state change gets repeatedly called.
Steps to reproduce
set up a listen state call on a person and call to a method that includes a log print. The log with get called over and over with no state changes happening from the person. A simple example is this:
class TestRoutine(hass.Hass):
    def initialize(self):
        self.listen_state(self.test_routine_cb, 'person.person')

    def test_routine_cb(self, *kwargs):
        # Print to log.
        self.log('I am here!')

The main state may be unchanged, the state attributes probably did change.
Please note that listening to a state change entails the whole state, including it's attributes.
This is not a bug, but how Home Assistant works.

Something here is different.  I only say that because I have had an automation that uses this listen state for more then two years in a presence detection system with no issues.  And it's even currently running correctly in version 0.7.2 as soon as I update to 0.8.0 the call goes haywire with no code changes.

@josephkiser04 That would be a change with AppDaemon itself, not the add-on. The add-on isn't providing or changing that logic that is defined from upstream AppDaemon.
I guess this issue, in that case, isn't in the right issues tracker?

@frenck omg you are absolutely right I do apologize for bugging you lol! I will open an issue over there. Thanks!


scss.additionalData not working in slot, when set alias in vite.config.ts/js

Describe the bug
As title.
Reproduction
By the way, I use :slotted().
vite.config.ts
import path from 'path';
import { UserConfig } from 'vite';

const alias = parseAlias({
  '': 'src',
  'com': 'src/component',
  ...
});

export default {
  alias,
  cssPreprocessOptions: {
    scss: {
      additionalData: `
        @use 'src/scss/_variable' as var;
        ...
      `,
    },
  },
} as UserConfig;

function parseAlias(config: Record<string, string>) {
  const _config: Record<string, string> = {};
  Object.keys(config).forEach(i =>
    _config[`/@${i}/`] = path.resolve(__dirname, config[i]));
  return _config;
}

vite.config.js
import path from 'path';

const alias = parseAlias({
  '': 'src',
  'com': 'src/component',
  ...
});

module.exports = {
  alias,
  cssPreprocessOptions: {
    scss: {
      additionalData: `
        @use 'src/scss/_variable' as var;
        ...
      `
    }
  }
};

function parseAlias(config) {
  const _config = {};
  Object.keys(config).forEach(i =>
    _config[`/@${i}/`] = path.resolve(__dirname, config[i]));
  return _config;
}

System Info

vite: 1.0.0-rc.13
window: 10
nodejs: 14.15.3
yarn: 1.22.10
vue: 3.0.4
@vue/compiler-sfc: 3.0.4

I'm not sure what happend @use 'src/scss/_variable' with alias, them are not related.

I seem to find that the problem is caused by using defineAsyncComponent..?
Please refer to this sample, and set isTransitionBug =  false
https://github.com/pgy108103/vue3_vite_issue_sample

The additionalData is already works. You can see .tip element for this. For the style of slot, it should be same as  https://github.com/vitejs/vite/issues/1262. So i colse this.


Fixed wrong import causing build fail.

Dont merge until build success, I think I accidentally imported wrong junit thats why fail 4 hours ago


Fail application startup when could not find a secret at path (Vault location is not resolvable/Not found)

We are all human beings and occasionally may accidentally make a typo when enumerating our secret paths. Sometimes values of some properties that are stored in certain paths can be ignored and a simple info message about an unresolvable path could be enough (such functionality currently present), but not when the value of that property is critical for my application and in such cases I want my application to fail on startup instead.
Currently, I can not think of a good solution but I have noticed some interesting code in LeaseAwareVaultPropertySource class. It has a property called ignoreSecretNotFound which seems to be always true. And if we take a look at line 178 we can see there such piece of code:
Exception loadError = this.loadError;
if (this.notFound || loadError != null) {

	String msg = String.format("Vault location [%s] not resolvable", this.requestedSecret.getPath());

	if (this.ignoreSecretNotFound) {
		if (logger.isInfoEnabled()) {
			logger.info(String.format("%s: %s", msg, loadError != null ? loadError.getMessage() : "Not found"));
		}
	}
	else {
		if (loadError != null) {
			throw new VaultPropertySourceNotFoundException(msg, loadError);
		}
		throw new VaultPropertySourceNotFoundException(msg);
	}
}

So maybe some kind of configuration property could be added which will enable switching the value of ignoreSecretNotFound?

The easiest was to ensure a failure is referencing the key in a
@value property injection.

But what about the code snippet that I've posted? Seems like else clause is never executed...


Automatically detect virtualenv

What feature request would you like to suggest?
It would be nice if creosote could simply detect the virtualenv it is installed in instead of having to pass it explicitly. A script can easily detect the current virtualenv by checking sys.base_prefix. If sys.base_prefix is different from sys.prefix, you're in a virtualenv.
Will the feature request break backwards compatibility?
I don't think this would break any backward compatibility. For example, you could:

Check for .venv (current default)
Check for sys.base_prefix
Give error if no virtualenv is found

Hi @bendavis78 yeah this sounds doable.
I'm just wondering if the sys attributes are better than to look for $VIRTUAL_ENV, which I believe exists when you have activated a virtual environment.

@bendavis78 I finally came around looking at this but I'm not sure I can implement this without potentially breaking the default behavior for some users.
Imagine the default value is [".venv"] and that you are running creosote with this, but having another virtual environment activated.
I can't see myself implementing this right now, but I could add this, feature flagged. This would mean you'd have to run creosote with a parameter anyways; e.g. creosote --use-feature auto-detect-venv. I guess this might defeat the purpose of not having to specify any arguments, or do you think it would be useful for you?


Patch Android build for Sauce Labs debugging

To better debug an issue with Sauce Labs they would like us to set android:usesCleartextTraffic="true" in the <application> section of the AndroidManifest.xml file.
This setting needs to be removed before this issue can be closed.

@nodlesh FYI


Add Support for XinFin ( XDC ) Network.

Description
Add support for XinFin XDC.Network, XDC.
Derivation path is "m/44'/550'/0'/0/0"
XinFin XDC.Network is an enterprise-ready hybrid Blockchain technology company optimised for international trade and finance. The XinFin XDC.network is powered by the native coin called XDC. The XDC protocol is architected to support smart contracts, 2000TPS, 2seconds transaction time, KYC to Masternodes (Validator Nodes). The XDC.Network uses XinFin Delegated Proof of Stake (XDPoS), with the intending to create a ‘highly-scalable, secure, permission, and commercial grade’ blockchain network.

Testing instructions
See XDCNetwork tests, C++/swift/kotlin.

Types of changes

Checklist

[X] Prefix PR title with [WIP] if necessary.
[X] Add tests to cover changes as needed.
[X] Update documentation as needed.
[X] I have read the guidelines for adding a new blockchain
[X] If there is a related Issue, mention it in the description (e.g. Fixes #<issue_number> ).

Thanks for your interest, but we don't have a plan to add XDC atm

Hello @hewigovens,
Any specific reason ?

Hi @hewigovens
Could you please let us know why we have been rejected?  Also, please view PR below...We have made payments now twice and this is starting to become frustrating.
#https://github.com/trustwallet/assets/pull/1865

Hi @hewigovens @optout21,
Circling back to this PR from last year, I understand you dint had plans to add XDC network at that point in time. I am reaching out to you again for adding XDC network to Trust Wallet. Our users base has grown many folds now and believe adding XDC network to Trust wallet would be beneficial for both of us.
We are also now being ranked as Top 50 Blockchains and seeing the staggering growth and penetration i strongly believe users having access to Trust wallet for XDC would be beneficial for the both the community.
Looking forward to hearing back from you.

The XDC Network has seen a lot of growth over the last year and is now amongst the most impactful EVM-compatible blockchains in the industry. Interest from the community in Trust Wallet has always been there but is on the rise due to an increasing number of new users. XDC support in Trust Wallet could bring good attention and growth to Trust Wallet and give it access to a growing community of users. Can we open this discussion again and make it happen?


Broken register calculation in this version

After Vector35/arch-ppc#2 I have to open another issue, I believe the version I compiled myself from this source code behaves differently (and wrong) from the version that's included with Binary Ninja.
With the version in Binary Ninja I get this disassembly (correct):

With the version I'm compiling myself (most recent commit on the dev branch, most recent version of capstone), I get this disassembly (wrong):

Now it thinks that "addi r0, r4" with the last two bytes being ff fa would result in 0x0000fffa in the register, but that's wrong. It should be 0xfffffffa (-6). This makes all the offset calculations wrong, like for the jump table.
Could this be a bug in the capstone code?
Can someone tell me which exact version of capstone is used to compile the ppc-capstone in the current Binary Ninja, so I can try that as well to rule out a capstone bug?

We've resolved this by having Capstone as a submodule, fixed at a particular commit, this one from Mar 5, 2017.
$ git clone https://github.com/vector35/arch-ppc
$ cd arch-ppc
$ git submodule update --init --recursive
Submodule 'capstone' (https://github.com/capstone-engine/capstone.git) registered for path 'capstone'
Cloning into '/private/tmp/arch-ppc/capstone'...
Submodule path 'capstone': checked out 'bac2b3b2023d2d3ad76398c76d64ceb308a606cb'

I'll update arch-ppc's readme to mention this, and also there should be an upgrade to capstone 5 soon: https://github.com/capstone-engine/capstone/tree/5.0.


code lens for TypeScript should not show references for anonymous functions

For Anonymous functions code lens is displayed although it has only one reference.
This is a lot of noise for nothing.
foo(): number[] {
    /** 1 reference */
    return [1, 2, 3].filter(n => n > 1);
}

In my opinion these lenses can be removed completely.

This issue lacks

name of the language/extensions that you are using/showing

This issue lacks
* name of the language/extensions that you are using/showing

You are right. My bad. I fixed it. Sorry.

Requires:

"typescript.referencesCodeLens.enabled": true
"typescript.referencesCodeLens.showOnAllFunctions": true

I added in those required settings and am seeing the screenshot below. Seems to now only say 0 references instead of one but the code lens still exists

I think the screenshot shows the expected (fixed) behavior. Previously the references code tense was on the line with return. There are zero references because there are no uses of that class or method

yep - this is exactly what I wanted.


Allow users to create domains

I would like to request a feature to allow users access to create new domains. It would seem that any feature allowing end users to add domains should have some limits involved to keep them abusing the system such as number of domains or possibly number of records. I would also think that limiting the type of domain (Native, Master, Slave) would be important.

@jonsparks Great! Can you submit a PR when it's ready? Thank you so much!

@jonsparks Great! Can you submit a PR when it's ready? Thank you so much!

Looks like this never happened. Anyone else working on something like this? I'm still interested.

Interesting feature. I gonna work on this after merging all PR.

Great @ngoduykhanh looking forward to it. You might want to check out @jonsparks work before you begin. It looks like he did do some work on it.

I'm still interested in this. 👍 How's the progress?

I will work on this after finishing the configuration management and security part which discuss at #342. You guys can leave your thoughts there :).

Great work. Any plan to allow assigning a dns template to a specific user?


Cannot read property 'kind' of undefined at Object.parenthesizeArrayTypeMember

TypeScript Version:  3.1.0-dev.20180802

Search Terms:

Cannot read property 'kind' of undefined
Optional element in tuple
ReadonlyArray
Strict mode

Code
type Foo = [object, object?];

const bar: ReadonlyArray<Foo> = [{}, {}];

Expected behavior:
An error along the lines of:
Type '{}[]' is not assignable to type '[object, (object | undefined)?][]

Actual behavior:
./node_modules/typescript/lib/tsc.js:67968
                throw e;
                ^

TypeError: Cannot read property 'kind' of undefined
    at Object.parenthesizeArrayTypeMember (./node_modules/typescript/lib/tsc.js:50576:24)
    at Object.createOptionalTypeNode (./node_modules/typescript/lib/tsc.js:47850:24)
    at typeReferenceToTypeNode (./node_modules/typescript/lib/tsc.js:26572:44)
    at typeToTypeNodeHelper (./node_modules/typescript/lib/tsc.js:26383:28)
    at typeReferenceToTypeNode (./node_modules/typescript/lib/tsc.js:26560:43)
    at typeToTypeNodeHelper (./node_modules/typescript/lib/tsc.js:26383:28)
    at signatureToSignatureDeclarationHelper (./node_modules/typescript/lib/tsc.js:26827:52)
    at createTypeNodesFromResolvedType (./node_modules/typescript/lib/tsc.js:26666:43)
    at createTypeNodeFromObjectType (./node_modules/typescript/lib/tsc.js:26547:35)
    at createAnonymousTypeNode (./node_modules/typescript/lib/tsc.js:26502:42)

Conditions
It seems this bug is only triggered if:

a ReadonlyArray is used – Array doesn't seem to trigger it
strict mode is enabled
the last element of the tuple is optional

Playground Link:
Playground. Be sure to enable strictNullChecks to replicate.

FYI I am experiencing this error in the current release version (3.0.3).
Any idea whether it is likely to be fixed any time soon, or should I refactor my code to work around it?

I'm using using tsc 3.0.3 and I got this error when doing a rather large merge  I'm not sure how to find which file is causing it. Are there any tricks to find the offending file?

I just hit this too. My repro is quite different to OP's, but the PR at #26433 fixes it. Hope it gets merged soon.


Optimize compilation time by adjusting the order of the repository

ref: link
Optimize repository order
When Gradle resolves dependencies, it searches through each repository in the declared order. To reduce the time spent searching for dependencies, declare the repository hosting the largest number of your dependencies first. This minimizes the number of network requests required to resolve all dependencies.

I believe most of our dependencies are androidx dependencies found in the google maven repo, so it would seem the current order is correct. Unless the transient dependencies greatly outnumber the declared ones.

I believe most of our dependencies are androidx dependencies found in the google maven repo, so it would seem the current order is correct. Unless the transient dependencies greatly outnumber the declared ones.

You are right. This is my clean build stats:

So this pr should be ignore.


Feature singlenode taskrunner lock

Acquiring a lock for the primary node to run tasks which should run only on a single node.
Used a distributed lock with singleton pattern.

I would like our own implementation to be made considering all the scenarios listed below:

There should be only one master node executing the task at any particular moment in time
If master node has died or stopped, the other node should automatically be assigned a master role and continue to execute tasks
It should be possible to use locking mechanism not only for master node detection, but also to run migrations (but this case is slightly different because one node should be execution migrations and other nodes should wait until it is done and then run migration code as well, but it would not do anything because all migration would already be applied by the master node)
-Imagine you run tasks every minute. There could be a case when task execution takes longer than a minute - in such a case it should be possible to say if the tasks runner should skip new tasks until the current is executed or it could queue new tasks and only execute it when the current is done. I think for a start we should just skip new tasks if a previous one is not completed yet. That is where task level lock comes to play.


Development Mode Error

I followed this tutorial. It worked fine in the local host. When I deployed it in my azure website, I obviously changed the reply url to the public link. So I was able to select an account, enter password, and allow the permissions, but then I got this error:
An error occurred while processing your request.
Request ID: 0HLF7H4694HLM:00000006
Development Mode
Swapping to Development environment will display more detailed information about the error that occurred.
Development environment should not be enabled in deployed applications, as it can result in sensitive information from exceptions being displayed to end users. For local debugging, development environment can be enabled by setting the ASPNETCORE_ENVIRONMENT environment variable to Development, and restarting the application.
I changed the environment mode to Production in my App, same error. I'm starting to suspect it has to do with something else. Any help?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a4c264c0-0c5c-298e-bb45-9b4891c8d162
Version Independent ID: ce69b990-0b4c-abda-cd2d-68f85cd8031e
Content: Microsoft Account external login setup with ASP.NET Core
Content Source: aspnetcore/security/authentication/social/microsoft-logins.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

See https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/troubleshoot?view=aspnetcore-2.1
And try setting the ASPNETCORE_ENVIRONMENT environment variable to Development,

Thank you for your quick response, Rick. This link did not have the answer, however, I was able to solve it. Turns out, when you deploy your web app, you must go to the appsettings.json file, and replace the "DefaultConnection" from "ConnectionStrings" with a server key generated in azure or some other database service. Indeed the log is misleading, since when the app is deployed, it is in Production mode, but the debugger notes a local default connection string, so it gets confused and assumes it is in Development mode instead.
This tutorial is very complete, but I strongly recommend the writers to include this key piece of information, since it is essential for deploying the app.

@donalatorre  a link to https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-webapp-using-vs?view=aspnetcore-2.1 should solve the problem

Hello,
When I paste the following code in the Startup, I get an error on ApplicationUser. It says the type or namespace ApplicationUser could not be found or you are missing an assembly reference. I was wondering if know why?
services.AddIdentity<ApplicationUser, IdentityRole>()
.AddEntityFrameworkStores()
.AddDefaultTokenProviders();

Hi, I think your solution "...appsettings.json file, and replace the "DefaultConnection" from "ConnectionStrings" with a server key generated in azure..." could really help me. Would you be able to give me some more information about where you found the server key generated in Azure please - and also the syntax you used in the JSON file? Would really appreciate your help. Cheers

Hi Dona, I having the same issue. I put the right serve connection string in my appsetting.json file but still getting the same error. can you please help me out with this.

deploy to IIS not azure, getting the same error, anything else?

had the same issue, turned out to be the this call
//.AddValidationKeyFromFile(Configuration.GetSection("SigninKeyCredentials"), _loggerFactory.CreateLogger())
that caused the trouble. use the developersigningcredentials seems to work fine.

I think this will help
all you need is to display the real error by adding these lines in startup:
app.UseDeveloperExceptionPage();
app.UseDatabaseErrorPage();
without the condition of if (env.IsDevelopment())
and remove these lines if exists
app.UseExceptionHandler("/Error");
app.UseHsts();
then just let the app displaying the error like in development mode so you can search about it and fix it

Thank you for your quick response, Rick. This link did not have the answer, however, I was able to solve it. Turns out, when you deploy your web app, you must go to the appsettings.json file, and replace the "DefaultConnection" from "ConnectionStrings" with a server key generated in azure or some other database service. Indeed the log is misleading, since when the app is deployed, it is in Production mode, but the debugger notes a local default connection string, so it gets confused and assumes it is in Development mode instead.
This tutorial is very complete, but I strongly recommend the writers to include this key piece of information, since it is essential for deploying the app.
Can you please help me how to find the server key generated in Azure

This has nothing to do with Azure deployment. That's a different article.

i face same problem in 3.1 . any one help me?

I think this will help
all you need is to display the real error by adding these lines in startup:
app.UseDeveloperExceptionPage();
app.UseDatabaseErrorPage();
without the condition of if (env.IsDevelopment())
and remove these lines if exists
app.UseExceptionHandler("/Error");
app.UseHsts();
then just let the app displaying the error like in development mode so you can search about it and fix it
after you fix the error(s) you can remove these changes so users can not see the error :)

@abdullah-alimam, Your solution helped me a lot.
Here's how my I solved my problem:
I had the same problem (ASP.NET CORE 3.1) but changing "ASPNETCORE_ENVIRONMENT" did not helped.
Seeing @abdullah-alimam 's answer, I found that in Startup.cs, Configure method, this code was hiding the real issue.
 if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }

Then I deleted the If block and added Database error pages ( You might need to Install Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore from NuGet )
app.UseDatabserrorPages();

So your Startup.cs will look like this
app.UseDeveloperExceptionPage();
app.UseDatabaseErrorPage();

app.UseHttpsRedirection();

//Others will be Okay

Then you will see the real errors on the webpage. For me it was
Login failed for user IIS APPPOOL\DefaultAppPool

So I had to run a GRANT SCRIPT.  Hope this helps somebody.

@abdullah-alimam's  solution worked for me. Thanks


OpenNSFW with Docker

I would like to share how to run NSFT with docker

Build a caffe docker image (GPU)

$ cd open_nsfw
$ wget https://raw.githubusercontent.com/BVLC/caffe/master/docker/standalone/gpu/Dockerfile
$ docker build -t caffe:cpu ./

To build for cpu only get the Dockerfile for cpu from Caffe repo
$ wget https://raw.githubusercontent.com/BVLC/caffe/master/docker/standalone/cpu/Dockerfile

When the image it's ready, we check caffe installation

$ docker run -ti caffe:cpu caffe --version
caffe version 1.0.0-rc3

We run bash in this folder as mapped volume with the option --volume in order to run the training manually

docker run -ti --volume=$(pwd):/workspace caffe:cpu bash

so we are in the docker caffe image
root@8855e6188183:/workspace#

Run nsfw in the current container volume

root@8855e6188183:/workspace#python ./classify_nsfw.py --model_def nsfw_model/deploy.prototxt --pretrained_model nsfw_model/resnet_50_1by2_nsfw.caffemodel anderson_210.jpg

and we are done
NSFW score:   0.14057905972

@loretoparisi thanks!  This looks great. There is already a PR for running the nsfw model with docker. Can you take a look/review?

@jay-mahadeokar I will, thanks.

I have updated the PR thread with more info about running open_nsfw with caffe:gpu so with nvidia CUDA basically configuration. See https://github.com/yahoo/open_nsfw/pull/2

Hi guys
when i try to run: wget https://raw.githubusercontent.com/BVLC/caffe/master/docker/standalone/gpu/Dockerfile
I get an error: ERROR 404: Not Found.
Trying to follow the link also gives an error: 404

@Romamr1 the file is https://github.com/BVLC/caffe/blob/master/docker/gpu/Dockerfile


Dependabot creates "---" as commit message

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pip, pipenv
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
See example commits:

https://github.com/Taxel/PlexTraktSync/commit/386accbca6a6e641e2f2affff4a45d8b3412aac4
https://github.com/Taxel/PlexTraktSync/commit/c17a733fdb2cce458075f4023115a91dad863e7d

They were both merged with @dependabot squash and merge:

https://github.com/Taxel/PlexTraktSync/pull/1958#issuecomment-2123288196
https://github.com/Taxel/PlexTraktSync/pull/1956#issuecomment-2122541656

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Duplicate of #9784


error on invalid/unused noqa comments

# should be an error, invalid code
def foo():  # noqa: asdf
    ...

# should be an error, noqa comment has no effect
def bar():  # noqa: D103
    """asdf"""

# should be an error, a space is required after the colon, so this just ignores all errors not just D103
def baz():  # noqa:D103
    ...

But my package 'pyasdfstyle' would have reported an error on the first function foo:

Function not named 'asdf'  [asdf]

There would be no way to differentiate between the errors for pydocstyle and the errors for pyasdfstyle.

it shouldn't be reusing the same ignore comments that other linters use in the first place


[Changelog] Update for Hammer-2

[skip ci]

@carbonin as time permits, can you review.

@miq-bot assign simaishi

Hammer backport details:
$ git log -1
commit 81e7dbe39825bab4c66c6f73e39ae320b74c5f4b
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Mon Feb 4 15:35:22 2019 -0500

    Merge pull request #18420 from JPrause/hammer2_cl

    [Changelog] Update for Hammer-2

    (cherry picked from commit ed96bca75b3627dff160c95226290309db653892)


[5.5] Allow having "dot macros"

This pull request adds the option to register "dot macros". This is useful, for example, on the preset command, where now I could macro a bulma function and a bulma.auth function for the auth views.

Tests are failing.

No plans on adding this.


feat: AWS xray tracing config

TIS21-4226

No idea how to test this at this point :)

If you run the daemon locally you can see data in the AWS console.
There's some docker compose config floating around on slack, but I'm not sure if the fully fixed config is or not.

Xray daemon config is now in the handbook

Juicy errors now!
2023-03-28T11:12:18.370+01:00  INFO 21764 --- [nio-8210-exec-4] u.n.h.t.t.c.api.VerifyResource           : Received callback for credential verification.
2023-03-28T11:12:18.375+01:00 ERROR 21764 --- [nio-8210-exec-4] c.a.x.s.LogErrorContextMissingStrategy   : Suppressing AWS X-Ray context missing exception (SegmentNotFoundException): Failed to begin subsegment named 'completeCredentialVerification': segment cannot be found.
2023-03-28T11:12:18.394+01:00 ERROR 21764 --- [nio-8210-exec-4] c.a.x.s.LogErrorContextMissingStrategy   : Suppressing AWS X-Ray context missing exception (SegmentNotFoundException): Failed to begin subsegment named 'getTokenClaims': segment cannot be found.

Ok cool, thanks for confirming @Judge40 .
Given we are not going 'live' by any realistic measure for the next couple of months at least, shall we just park this piece of work and pick it up when Xray catches up with us? :)


3D model shakes on iOS 12

First, thanks for this good library.
My environment:

Device: iPhone6s, iPhoneX
OS: iOS 12

NNC Version:

NNC.json(default neural network in jeelizFaceFilter tag 1.1)

I was using it well on iOS 11. but I updated it to iOS 12 and I found the 3d model shaking. Is it a problem with ios12?

No this is not a pb with IOS12,
Maybe light conditions. I cannot do nothing with your bug report.
Try to play with the stabilization parameters, this is explained in the readme

thanks~


Replace RestClient gem with HTTP

Here are the reasons for replacing gem:

RestClient produces a warning when sending multipart requests with this gem's monkeypatch
Monkeypatching should be avoided
HTTP gem supports sending needed multipart requests without monkeypatch

#59 now reuses the connection


DependencyWarning: urllib3 (1.23) or chardet (3.0.4) doesn't match a supported version

Issue Template
Hi, here's a little bug on the new version of Twint that I'm facing on my machine.
Initial Check

Make sure you've checked the following:

[] Python version is 3.5 or higher.
yep 3.6 installed
[] Using the latest version of Twint.
Yep.
[] I have searched the issues and there are no duplicates of this issue/question/request.
Also

Command Ran

sudo pip3 install -r requirements.txt

gives the following result : no problem
Description of Issue
Requirement already satisfied: aiohttp in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 1))
Requirement already satisfied: aiodns in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 2))
Requirement already satisfied: beautifulsoup4 in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 3))
Requirement already satisfied: cchardet in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 4))
Requirement already satisfied: elasticsearch in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 5))
Requirement already satisfied: pysocks in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 6))
Requirement already satisfied: pandas in /home/herve/.local/lib/python3.6/site-packages (from -r requirements.txt (line 7))
Requirement already satisfied: multidict<5.0,>=4.0 in /home/herve/.local/lib/python3.6/site-packages (from aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: async-timeout<4.0,>=3.0 in /home/herve/.local/lib/python3.6/site-packages (from aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: attrs>=17.3.0 in /home/herve/.local/lib/python3.6/site-packages (from aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: idna-ssl>=1.0 in /home/herve/.local/lib/python3.6/site-packages (from aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: yarl<2.0,>=1.0 in /home/herve/.local/lib/python3.6/site-packages (from aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: chardet<4.0,>=2.0 in /home/herve/.local/lib/python3.6/site-packages (from aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: pycares>=1.0.0 in /home/herve/.local/lib/python3.6/site-packages (from aiodns->-r requirements.txt (line 2))
Requirement already satisfied: urllib3>=1.21.1 in /home/herve/.local/lib/python3.6/site-packages (from elasticsearch->-r requirements.txt (line 5))
Requirement already satisfied: python-dateutil>=2.5.0 in /home/herve/.local/lib/python3.6/site-packages (from pandas->-r requirements.txt (line 7))
Requirement already satisfied: numpy>=1.9.0 in /home/herve/.local/lib/python3.6/site-packages (from pandas->-r requirements.txt (line 7))
Requirement already satisfied: pytz>=2011k in /home/herve/.local/lib/python3.6/site-packages (from pandas->-r requirements.txt (line 7))
Requirement already satisfied: idna>=2.0 in /home/herve/.local/lib/python3.6/site-packages (from idna-ssl>=1.0->aiohttp->-r requirements.txt (line 1))
Requirement already satisfied: six>=1.5 in /home/herve/.local/lib/python3.6/site-packages (from python-dateutil>=2.5.0->pandas->-r requirements.txt (line 7))
but when I start twint.py
$ python3 twint.py -s hpiedcoq --csv -o test.csv
/usr/lib/python3/dist-packages/requests/init.py:80: RequestsDependencyWarning: urllib3 (1.23) or chardet (3.0.4) doesn't match a supported version!
RequestsDependencyWarning)
Traceback (most recent call last):
File "twint.py", line 117, in
main()
File "twint.py", line 114, in main
twint.Search(c)
AttributeError: module 'twint' has no attribute 'Search'
Environment Details

Linux? Ubuntu 18.04 uptodate

Ok my bad. I had the old twint.py in the directory.
By invoking Twint.py it works but I still have the error

/usr/lib/python3/dist-packages/requests/init.py:80: RequestsDependencyWarning: urllib3 (1.23) or chardet (3.0.4) doesn't match a supported version!
RequestsDependencyWarning)

That's a recent problem with requests it looks like:

[https://github.com/requests/requests/issues/4673(https://github.com/requests/requests/issues/4673)
https://bugs.archlinux.org/task/58878

You probably need to update it again?


Port WinPath's lib to using WinPath.Library

WinPath's core functionality is now fully dependent on WinPath.Library.


Fix homepage to use SSL in Logic Cask

The HTTP URL is already getting redirected to HTTPS. Using the HTTPS URL directly
makes it more secure and saves a HTTP round-trip.

Looks good, thanks! :+1:


[BUG] LabeledUtterance id is int32 but client response data bigger than it.

LabeledUtterance id is int32 but client response data bigger than it.

Environment:

Name and version of the Library package used: Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring 3.1.0
Windows 10 .NET Core 3.1.403
IDE and version : Visual Studio 16.7.7

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@jsquire any updates on this?
Same issue when deleting example

Hi @hebaelfadly.  Unfortunately, I am only serving as first triage and have no insight into the Cognitive Services offerings nor their team process for triaging.   I'll need to defer to @cahann, @kayousef for updates.

hi @hebaelfadly , thanks for reporting the bug. I will be working with @moabba on triaging the bugs in on of our coming sprints.

@cahann @moabba Do you have any updates on this issue.


password arg not works.

redis-7000.conf

masterauth Qunar@2005
requirepass Qunar@2005
and other redis.conf is the same one

redis client code

_startup_nodes = [
    dict(host=node.split(':')[0], port=int(node.split(':')[1]))
    for node in CONF.REDIS.nodes
]
try:
    self.redis = StrictRedisCluster(
        startup_nodes=_startup_nodes,
        decode_responses=True,
        password= "Qunar@2005"
    )
except Exception as ex:
    print 'except, ', str(ex)

redis-cli works to authenticate password.

/home/q/redis/src/redis-cli -h <IP_ADDRESS> -p 7000 -c -a Qunar@2005
<IP_ADDRESS>:7000> set a b
-> Redirected to slot [15495] located at <IP_ADDRESS>:7003
OK

but error occur using redis-py-cluster
ERROR sending 'cluster slots' command to redis server: {'host': '<IP_ADDRESS>', 'port': 7000}
it works if not set auth info between client code and configure file.

help me to handle the password issue. thanks a lot

It would be bad because there is travis tests that runs on password protected cluster nodes to test just that support. If it is reproducible then it would mean a major defect.
If possible, could you try to reproduce the problem on a different installation or machine all together  just to be extra sure?

I reproduce the problem  when set protected-mode no

I find a issue about code
def get_redis_link(self, host, port, decode_responses=False):
    return StrictRedis(host=host, port=port, decode_responses=decode_responses)

password is not set as param of StrictRedis.

the version is 1.1.0

when to release new version. @Grokzen

I am seeing the same issue where the password is not being set in 1.1.0 release.

@hanbaga I can confirm that it works as intended in unstable and that i can run the following code with a cluster that is password protected
from rediscluster import StrictRedisCluster

startup_nodes = [{"host": "<IP_ADDRESS>", "port": "7100"}]

# Note: decode_responses must be set to True when used with python3
rc = StrictRedisCluster(startup_nodes=startup_nodes, decode_responses=True, password= "abc123")
rc.get("foobar")

and it works as i expect.
The only thing that i can complain about in the unstable branch is that the exception that is raised when wrong password is provided.
A note about the mentioned get_redis_link. It sure looks abit wierd right now that i do not explicitly send in a password field or something.  If you look in this variable https://github.com/Grokzen/redis-py-cluster/blob/unstable/rediscluster/nodemanager.py#L20 you see that the password is sent into the nodemanager and is preserved for any connection to a redis node that is made from inside the nodemanager. Inside the get_redis_link method https://github.com/Grokzen/redis-py-cluster/blob/unstable/rediscluster/nodemanager.py#L103 you find that the connection kwargs is sent along into the acctual redis connection object and the password is sent along in there.
To make a long story short, i will close this issue when i make the next release and i do not have an ETA when that will be right now.

Just a note, it was implemented in this commit 5f66761c4dbf7b686f17ad3b90f172e92f004cf8

Closing this as fixed/implemented and it will be part of next release.

sorry ,i want to ask about how to client redis cluster with password, now I  can client redis single with password

@lostsquirrel Look at the example a few comments up. Or try the same method as you do in a normal redis-py instance and it should work out the same.

OK，i got it ，thank you for your reply. Happy new year!
发自我的 iPhone

在 2019年1月4日，21:18，Grokzen<EMAIL_ADDRESS>写道：
@lostsquirrel Look at the example a few comments up. Or try the same method as you do in a normal redis-py instance and it should work out the same.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Radar can't handle B (maybe other ranks too?) mobs?

Hey there, i just tested the new radar overlay and got an error message while i encountered a B-Mob. Don't know what's the problem but maybe you can figure it out?
Radar: BrowserConsole: Uncaught TypeError: Cannot use 'in' operator to search for 'B' in undefined (Source: .../cactbot/ui/radar/radar.js, Line: 73)
Thanks for your hard work! :)

Sorry for this issue.  I had tested using a cactbot/user/radar.js file that made this issue not show up.
I think if you point your radar overlay at https://quisquous.github.io/cactbot/ui/radar/radar.html instead of the local file, it'll have the fix I just landed.


MNT: rerender with older abaseil again

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #28.
Here's a checklist to do before merging.

[x] Bump the build number if needed.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Sorry for noise with this abseil migration. It seems that a windows build failed for build 5, but I don't think it is important to rebuild. This PR should help users resolve more cleanly. If it still gives problems, we can mark build 5 as broken with repo data patches, but I find that to be annoying.

Sorry for noise with this abseil migration. It seems that a windows build failed for build 5, but I don't think it is important to rebuild. This PR should help users resolve more cleanly. If it still gives problems, we can mark build 5 as broken with repo data patches, but I find that to be annoying.

No problem!


Fix limitations of js.UndefOr with A | B

Review by @nicolasstucki

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2596/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3350/
Test PASSed.

LGTM


Facing the issue too many requests with GoogleSearch.

With concurrent request to googlesearch, receiving the following:
    642 def http_error_default(self, req, fp, code, msg, hdrs):
--> 643     raise HTTPError(req.full_url, code, msg, hdrs, fp)

HTTPError: HTTP Error 429: Too Many Requests

Any idea to add proxy to the google search?

can you share the code please?

@VinciGit00
You can replicate the above issue with the sample code below:
`import concurrent.futures
import time
from googlesearch import search
def fetch_url(query):
return list(search(query, stop=10))
def main():
query = "Weather in Pakistan"
batch_size = 50
res = []
with concurrent.futures.ThreadPoolExecutor(max_workers=batch_size) as executor:
    future_to_url = {executor.submit(fetch_url, query): i for i in range(batch_size)}

    for future in concurrent.futures.as_completed(future_to_url):
        try:
            urls = future.result()
            res.append(urls)
        except Exception as e:
            print(f"Error fetching data: {e}")

return res

if name == "main":
result = main()
print(len(result))`
Need proxy to avoid the too many request issue.

ok but how do you integrate it with scrapegraph?

Basically, In scrapegraphai we are using google search, but we need to replace with the following to have the proxy as input parameter:
googlesearch-python
from googlesearch import search
search(query, num_results=max_result, proxy = proxy)

ok I will update

ok pls update to the new beta


chore(package): update @types/node to version 8.0.46

Coverage remained the same at 98.14% when pulling 8cfa34c4bbca06e63bc5fa1435d3f54bce800a7c on<EMAIL_ADDRESS>into 2a3024e3e4306b149aae710026e198c2c794a1cc on master.


How to reuse a configuration from config.yml

Hi,
I have a configuration saved in my config.yml.
And i would like use this configuration in a javascript file.
For example :
CKEDITOR.replace('myId', myConfigurationArray);
But i havent access to my configuration by this way.
Have you got any idea how to do that ?
Thanks by advance.

If I understand well, you would like to manually create your CKEditor instance without using the form component?

In kind of, yes it's that.
I'm not sure i use the good way, but i create instance of CKEditor on demand by user (with a button).
So i have many instances of CKEditor on the same page.

Are you talking about the form collection type?

Humm, it's probably a problem in my code.
Yes it's a form collection type but it's a little more complex :

I have many widgets on right, and i drag'n drop to the left to add widget in my page.
For all available widgets (on right), i have data-prototype and i recreate my widget after drag'n drop to the left.
In left, it's not really a collection because it's a collection set.

In theory, the data-prototype wraps all the javascript code needed to load CKEditor. When appending the code in your page, the CKEditor should appear... Isn't it?

It appears because i declare CKEDITOR.replace(), else it doesn't work.
Have you got the good way to work with a collection ?
I will create a simple version of my functionnality and i wil testing where is the problem.

Without seeing how you generate the right side of your form and how you handle the drag & drop, I can't really help :s

I will refactoring my code and i will back to you after.

You are right, i used the wrong method to create more CKEditor instances.
It works perfectly, the problem was my code. I close this issue.


nan

hello I have a problem with highlighting the text that comes before the hastag. I'll show you a picture.

@12-13-mm I don't understand your request, can you elaborate, please ?


Dense reconstruction

Hello, first of all congratulations on your excellent work, I used doppelgangers for sparse reconstruction of 35 photos and then used colmap for dense reconstruction, but the number of images that could be densely reconstructed at this time was only 3. I would appreciate it if you could help me with this problem. My threshold is set to 0, and in my understanding it should not filter out any image pairs.

Hello, I hope the question has been resolved. If not, have you checked how many pairs were deleted when you set the threshold to 0? It should print a message like 'Total', cursor.rowcount, 'Records deleted successfully' (https://github.com/RuojinCai/doppelgangers/blob/main/doppelgangers/utils/process_database.py#L50).
For a sanity check, did you check, without running the doppelganger algorithm, if all 35 images can be registered in dense reconstruction?


Add Table of content

Issue Title
Please enter the title of the issue related to your pull request.
Add Table of Contents to README

[x] I have provided the issue title.

Info about the Related Issue
What's the goal of the project?
The goal of the project is to enhance the README by adding a Table of Contents (TOC) to make navigation easier for users.

[x] I have described the aim of the project.

Name
Please mention your name.
Alolika Bhowmik

[x] I have provided my name.

GitHub ID
Please mention your GitHub ID.
alolikabhowmik

[x] I have provided my GitHub ID.

Identify Yourself
Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, Hacktoberfest).
GSSoC 2024 Contributor

[x] I have mentioned my participant role.

Closes
Enter the issue number that will be closed through this PR.
Closes: #736

[x] I have provided the issue number.

Describe the Add-ons or Changes You've Made
Give a clear description of what you have added or modified.
I have added a Table of Contents section to the README to improve its usability and navigation.

[x] I have described my changes.

Type of Change
Select the type of change:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Describe how your changes have been tested.
I have manually verified the TOC functionality by checking if all the links lead to the correct sections in the README.

[x] I have described my testing process.

Checklist
Please confirm the following:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.

@vanshchauhan21 The task has been completed. Kindly review the PR
Dont forget to add label" GSSOC-EXT" and the correct level assigned


Fix Info->IndexConfig->Mirros Jackson deserialization

Mirrors is a list of strings not a string.
I'm not sure how it passed on Travis-CI, but it broke our internal
Jenkins build.

@mattnworb @johnflavin

Sorry. I had to guess at the type of object because the API docs are totally deficient here.
$ grep Mirrors docs/reference/api/docker_remote_api_v1.*.md
docs/reference/api/docker_remote_api_v1.18.md:                        "Mirrors": null,
docs/reference/api/docker_remote_api_v1.19.md:                    "Mirrors": null,
docs/reference/api/docker_remote_api_v1.20.md:                    "Mirrors": null,
docs/reference/api/docker_remote_api_v1.21.md:                    "Mirrors": null,
docs/reference/api/docker_remote_api_v1.22.md:                    "Mirrors": null,
docs/reference/api/docker_remote_api_v1.23.md:                    "Mirrors": null,
docs/reference/api/docker_remote_api_v1.24.md:                    "Mirrors": null,

It passed on Travis because it wasn't really tested. I added a lot of tests for various fields in Info, but most of them were compared to anything() if that. The only tests for the RegistryConfig object are:
    assertThat(info.registryConfig(), notNullValue());
    assertThat(info.registryConfig().indexConfigs(), hasKey("docker.io"));

No test for any of the fields inside the IndexConfig, which is where mirrors is.

@johnflavin No worries. Yes, the docs are missing real mirrors values.


Fix build warnings in NSOperation

The Data parts of this are handled by: https://github.com/apple/swift-corelibs-foundation/pull/553 (which brings Data+NSData to mostly Swift3 parity).

@michael-lehew : I have reverted the NSData changes from this PR. Thanks.

looks good to me; built manually on linux.


Remove IoT project finalizers if delete fails

Type of change

Enhancement / new feature

Description
Attempt to stabilze IoT tests, but making sure IoT project resources are removed

@enmasse-ci run tests profile=iot

@dejanb @famartinrh Would it be possible instead to ensure that the device registry is deleted after the iotprojects etc. during cleanup?

@lulf I think there's still work to make sure tests clean up properly. This fix is just to make sure we don't mess the whole build/cluster when that happen. I put warn log in there, so we can track when this is happening and further investigate.

:x: Test Summary :x:
TEST_PROFILE: iot
TEST_CASE:
TOTAL: 35
PASS: 30
FAIL: 1
SKIP: 4
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

InfinispanDeviceRegistryTest testTenantDeletionTriggersDevicesDeletion. in io.enmasse.systemtest.iot.isolated.registry.InfinispanDeviceRegistryTest


prop value change does not propagating to the input

We have a component that wraps , when value is updated, the underlying input value is not updated for some reason even though 's prop value is update . See screenshot

I don't understand what you're saying.
Explain with code snippets.

I guess I get what you mean:

					<ReactInput
						{ ...input_props }
						ref={ ref => this.input = ref }
						value={ this.state.value }

So the input value is maintained in state and when the property changes it's not updated in state.
I'll implement the update.

I released the new version, try it.


add @view and @viewExist

Related to #20274
add blade @view and @viewExist directive.

No plans to add this.


PR: Remove/update outdated refs to Mac OS X, Mac DMG installers and Continuum.io

Fixes #5978
First PR, but figured it was good to start small...hopefully I haven't messed too much stuff up. Removed the outdated references to the Mac DMG installers that are apparently no longer offered, to fix issue #5978 .
Also, as a tangentially related general formatting note (I didn't modify anything to this effect here, of course), it might make more sense to replace the numbers with bullets or (perhaps better yet) just simple headings under the Linux section, as they don't represent a sequential list of steps nor an ordered list of preferable alternatives, as a numbered list would imply. If its important enough, I can make another PR to do so.

it might make more sense to replace the numbers with bullets

I don't understand too well what do you mean by this, so please open a new PR about it.

Given it was an update to the same section and in a similar vein as the previous, and perhaps too small for a separate PR, I figured it might be in scope to update the deprecated Mac OS X name to the current macOS as well. Works for you?

I don't understand too well what do you mean by this, so please open a new PR about it.

Sure. To keep things clean and avoid merge conflicts (it would involve a change on the same line as the updated Windows Anaconda URL), should I just wait until this is merged to formally open that PR? Also, is it necessary to open an issue as well, for completeness?
Also, Anaconda is available for Linux and may be an easier option but isn't listed there, just distribution-specific methods. Should a similar bullet/subsection mentioning it as an option be added to that section? That would also be a separate PR I would assume?

should I just wait until this is merged to formally open that PR?

Sure, I'll merge it as soon our CIs finish.

Also, is it necessary to open an issue as well, for completeness?

Nop, don't worry about it.

Should a similar bullet/subsection mentioning it as an option be added to that section?

Ok, please do that too, in the same PR you're going to your other changes.

Ok, please do that too, in the same PR you're going to your other changes.

Thanks, will do.

Interesting. Here it says all checks have passed, but on the AppVeyor page it makes clear that only the Python 2.7 check has passed, and shows the Python 3.6 currently running about 60s in. Bug?
Also, out of an abundance of curiosity, how does it work forward-porting this into master?

Ready to go with the other PR as soon as this gets merged; all checks are good to go.
Also, curious about the AppVeyor status reporting inconsistency; I'll watch for whether it reoccurs on my next PR. If so, should one of us submit a bug report to someone? If confirmed, that could potentially mislead maintainers to think all builds passed when only the first one did; if something causes the 3.6 build to fail that doesn't affect 2.7 (and isn't caught by the other tests), then bad code could get merged without anyone knowing.

^_^

@CAM-Gerlach, I'll send you a message on Gitter. You'll receive a notification about it in your email. It's just to talk with you privately :-)

Sure thing.

I don't know why but Gitter doesn't allow me to start a conversation with you. Could you write me an email instead? My address is in my profile.

Sent

@ccordoba12 Reply sent, just FYI—there was some problem sending it at first so want to make sure it got through.


Youtube: fix repeated scrobbling

Listen to timeupdate events generated by <video> element instead of
using MutationObserver
Use currentTime and duration properties of <video> element
instead of text values in .ytp-time-*

Fixes #918
UPD: progress -> timeupdate

The updated connector doesn't recognize now playing song because videoSelector has never class playing-mode.
diff --git a/connectors/v2/youtube.js b/connectors/v2/youtube.js
index 5edd041..cb2f517 100644
--- a/connectors/v2/youtube.js
+++ b/connectors/v2/youtube.js
@@ -68,7 +68,7 @@ Connector.getUniqueID = function() {
 };

 Connector.isPlaying = function() {
-       return $(this.videoSelector).hasClass('playing-mode');
+       return $('#player-api .html5-video-player').hasClass('playing-mode');
 };

 Connector.isStateChangeAllowed = function() {

Whoops, that was ".html5-video-player" class, haven't noticed that. Reverted

(and I'm wary of the fact that progress events are generated very rarely(1 time per ~6 secs), so sometimes there can be no progress events at the last 5% of song and it won't be marked for repeat)

@f1u77y I noticed you call the Connector.onStateChanged function directly. In this case the result of the Connector.isStateChangeAllowed function is ignored.

In this case the result of the Connector.isStateChangeAllowed function is ignored

OK but isn't it better just to use this function inside default implementation of Connector.onStateChanged rather then outside of it? (I see you're talking about the same)

The video element generates 'progress' events about 8-10 times per song

Ahh, I misused this event(it's about loading progress but not playing). Will fix.

Is there a way to watch these events somewhere in dev console?

monitorEvents

monitorEvents

Ok, thanks.
Seems like the connector works fine.

OK but isn't it better just to use this function inside default implementation of Connector.onStateChanged rather then outside of it?

Yep, I meant the same thing.

@f1u77y I noticed some regression after merging this PR. Here are steps to reproduce:

Open Youtube front page.
Select any music video that should be recognized by the extension.

The selected music video won't be recognized, but it actually should.
Can you reproduce the issue? If so, have you any thoughts on how to fix it w/o reverting the commit?

Yes, that's because the video loads in the same page. We should search for the video element with MutationObserver

@f1u77y Ideally we should also stop search if video element is found and start search again if video element is missing on the page (e.g. user moves back on front page).

@f1u77y https://github.com/alexesprit/web-scrobbler/commit/5e92958834ba3c021581f44b29b24a0c0d55980b perhaps looks too complicated but I don't know how to simplify the code/reimplement by using another approach . Have you a better solution?

I wrote mostly the same code, and I don't see any way to do it in a better way.
(BTW, usage of MutationObserver with all flags on looks like overkill, doesn't it?)

(BTW, usage of MutationObserver with all flags on looks like overkill, doesn't it?)

I enabled only two flags which are required to observe visibility state of the video element.

Youtube changed something on their website, so the connector from this PR works fine again.


Wiki page not render properly

I've install the wiki app on a fresh new bench instance (without erpnext install). And when i go to the home page, that what i got.
I trie to add a new wiki page, and it notadd a new sidebar link, and nothing change.

I follow all step, and after I tried again by installing the missing NPM dependencies
What is my mistake !
Thx by advance.

I need more context (wiki version, frappe version etc) to help you out.
Can you also try going to /app and see if you've done the initial setup (selecting languages, nation, currency etc)? I've seen sometimes pages being deformed when setup isn't done

Oh sorry I forget to add that.
Wiki 0.0.1 last version form GitHub (today)
Frappe 14.29

I believe there's a latest Frappe version maybe update to it.

I new in bench. So do I have to restart from a new site ? (Now it's not a problem if that solve the issue)

I'm not sure if creating a new site is going to help

(Also I run it inside Docker, I don't know if that change anything)

Maybe install bench the other way and see if it works? (theoretically it shouldn't change anything)

I started over from scratch and everything worked fine. I'm still on docker, but this time I installed wiki before the first launch of the site.
Thank you all the same for the help, but for this great job you have done.


Missing links to download current firmware

Where can one find the latest firmware?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 36b7b2d0-f11a-4b73-3a9d-3032da7fd36f
Version Independent ID: dd269642-3af1-ab93-de7a-f7171b17ee7b
Content: Update Azure Kinect DK firmware
Content Source: articles/kinect-dk/update-device-firmware.md
Product: kinect-dk
GitHub Login: @tesych
Microsoft Alias: tesych

@sedwardstx Thanks for the feedback! We are currently investigating and will update you shortly.

@sedwardstx just follow download links
@SnehaAgrawal-MSFT please close this issues.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Create Manishak798.json

closes #1884
Checklist for profile addition

[x] Name the PR fix: add Manishak798.
[x] You've added file named Manishak798.json in the profiles directory.
[x] You've linked the PR to the correct issue.

Merge my profile


activation-manager errors and spammage

the setup works and deploys succesfully - however the activationmanager seems to have an issue with your script

Although the entire log is not visible, it seems that, due to some network restriction, the activation-manager container could not instal curl and jq and therefore it cannot continue normally.
We'll update the chart in a future release to use a custom container for the activation manager with all the logic built-in, instead of having a generic one that required additional dependencies.

odd, - if i kubectl exec into the activation manager and add the jq + curl ~ "apk add curl jq"
then the error does indeed go away

and then to verify that the deactivation manager works, i delete the pod

that doesn't really look good tho.

ah, changing https to http - let it run through its termination with reported "success"
` args:
- |
apk add curl jq
stop() {
echo 'Deactivating using the MD Core API'
curl -H "apikey: $APIKEY" -X POST "https://localhost:$REST_PORT/admin/license/deactivation"
echo 'Deactivating using activation server API'
curl -X GET "https://$ACTIVATION_SERVER/deactivation?key=$LICENSE_KEY&deployment=$DEPLOYMENT"
exit 0
}
trap stop SIGTERM SIGINT SIGQUIT
      until [ -n $DEPLOYMENT ] && [ $DEPLOYMENT != null ]; do
          echo 'Checking...'
          export DEPLOYMENT=$(curl --silent -H "apikey: $APIKEY" "http://localhost:$REST_PORT/admin/license" | jq -r ".deployment")
          echo "Deployment ID: $DEPLOYMENT"
          sleep 1
      done
      echo "Waiting for termination signal..."
      while true; do sleep 1; done
      echo "MD Core pod finished, exiting"
      exit 0`

`      - args:
- |
echo 'Starting activation manager, waiting 20sec for interfaces to be up'
sleep 20
apk update && apk add curl jq
stop() {
echo 'Deactivating using the MD Core API'
curl -H "apikey: $APIKEY" -X POST "http://localhost:$REST_PORT/admin/license/deactivation"
echo 'Deactivating using activation server API'
curl -X GET "http://$ACTIVATION_SERVER/deactivation?key=$LICENSE_KEY&deployment=$DEPLOYMENT"
exit 0
}
trap stop SIGTERM SIGINT SIGQUIT
      until [ -n $DEPLOYMENT ] && [ $DEPLOYMENT != null ]; do
          echo 'Checking...'
          export DEPLOYMENT=$(curl --silent -H "apikey: $APIKEY" "http://localhost:$REST_PORT/admin/license" | jq -r '.deployment')
          echo "Deployment ID: $DEPLOYMENT"
          sleep 1
      done
      echo "Waiting for termination signal..."
      while true; do sleep 1; done
      echo "MD Core pod finished, exiting"
      exit 0`

also this whole approach seems prone to error, since you dont really know what kubernetes will kill when a pod is recycled/killed.
i would recommend looking into lifecycle hooks  https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/
for your deactivation setup.

Actually our initial approach was with lifecycle hooks but we noticed that the "PreStop" hook did not meet all requirements for proper deactivation. For example, the hook would not fire when manually restarting or scaling a deployment, which would leave unused deployment ids still activated.
We'll continue to improve the activation/deactivation logic until we have a "metering" based license system which will make this process unnecessary .

oh alright, yeah that would be an issue, odd k8s doesn't handle this case...
well - true - looking very much forward to your metering approach !

Hello,
is there any progress on the metering type of licensing or does this sidecar work properly now? We have very big production issues when licenses get deactivated and files not processed.

I've checked with the dev team for the metering feature and it's not going to be released soon. As a result, we've refactored the activation manager container and published a dedicated image that can be imported and used offline if needed. The changes are available in the latest release.

I wrote my own license manager which monitors the state of the licenses on all cores and automatically deactivates / activates them. Not sure how we were able to use metadefender in production for so long. Looks like we were just lucky that the pods were not created on different nodes regularly.


New linter plugin: SublimeLinter-contrib-tailor

Linter for swift using tailor
Repo Link -> https://github.com/vaemoi/SublimeLinter-contrib-tailor

Please make a release and I'll put it in Package Control. Thanks!

Sorry, not quite sure what a release is?

Sorry, brainfart. Done!

Hello just checking in, was there anything I missed on this repo?
Thanks again!

Hey just checking in, was there anything specific I missed in my release?
Thanks again!

Nope, i'm just slow! Sorry!!! It should appear in Package Control within an hour.
https://github.com/SublimeLinter/package_control_channel/commit/b438f8229e3bd9c9751e92c29cb4fe2e596c3eeb