Batch Consumer breaks when Consumer Timeout is reached

Contact Details
No response
Version
8.x (develop, pre-release), 8.x
On which operating system(s) are you experiencing the issue?
Windows
Using which broker(s) did you encounter the issue?
RabbitMQ
What are the steps required to reproduce the issue?
1. Set consumer_timeout in RabbitMQ settings to 1.5 minutes
2. Create Batch consumer with TimeLimit 2 minutes and MessageLimit 10
3. Generate 9 messages
4. Wait
5. The consumer will throw errors and will process those messages multiple times

What is the expected behavior?

Maybe a warning or even an error at start up saying that you can't have "consumer_timeout" less than "TimeLimit" for a Batch consumer.
Another possible way, override either consumer_timeout with TimeLimit or TimeLimit with consumer timeout, so that it works properly
Maybe after recovering the connection and processing messages, it should actually acknowledge them. Currently it throws timeout error, but it's not possible that it hit the 1.5 minute timeout, since the connection was just restarted and my processing function is just logging text to console.

What actually happened?
Connection is broken due to timeout, then it is restored and messages are processed right away, but they are not acknowledged. After a few more minutes connection is broken once again, then it recovers and again starts processing same messages without acknowledging them.
Related log output, including any exceptions
11:02:39.237-D Starting bus: rabbitmq://localhost/
11:02:39.318-D Connect: guest@localhost:5672/
11:02:39.477-D Connected: guest@localhost:5672/ (address: amqp://localhost:5672, local: 57287)
11:02:39.556-D Endpoint Ready: rabbitmq://localhost/LAPTOP6B26JPGF_RabbitConsumer_bus_ptqyyygdgcre6oj1bdqmm7wffs?temporary=true
11:02:39.595-D Declare queue: name: TextMessage, durable, x-consumer-timeout: 10000, consumer-count: 0 message-count: 0
11:02:39.625-D Declare exchange: name: TextMessage, type: fanout, durable
11:02:39.637-D Bind queue: source: TextMessage, destination: TextMessage
11:02:39.735-D Consumer Ok: rabbitmq://localhost/TextMessage - amq.ctag-c6Ccabqsa_t5luyYZDPKwQ
11:02:39.736-D Endpoint Ready: rabbitmq://localhost/TextMessage
11:02:39.741-I Bus started: rabbitmq://localhost/
Listening for messages. Hit <return> to quit.
11:03:53.859-D Consumer Model Shutdown: rabbitmq://localhost/TextMessage - amq.ctag-c6Ccabqsa_t5luyYZDPKwQ, Concurrent Peak: 6, 406-PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more
11:03:53.870-D Consumer Stopping: rabbitmq://localhost/TextMessage (Consume Loop Exited)
Processing batch of 6 messages
Got message: 8/6/2024 9:04:53 AM High Priority 1 High
Got message: 8/6/2024 9:04:53 AM High Priority 2 High
Got message: 8/6/2024 9:04:53 AM High Priority 3 High
Got message: 8/6/2024 9:04:53 AM High Priority 4 High
Got message: 8/6/2024 9:04:53 AM High Priority 5 High
Got message: 8/6/2024 9:04:53 AM High Priority 6 High
11:04:54.013-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-6a24-08dcb5f68e97 MassTransit.Batch<Messages.TextMessage> MyHighTextMessageConsumer(00:00:00.0046474)
11:04:54.052-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-924c-08dcb5f68e7b Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.1097546)
11:04:54.052-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-6792-08dcb5f68e97 Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.1097765)
11:04:54.052-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-5e5a-08dcb5f68e97 Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.1097921)
11:04:54.052-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-6a24-08dcb5f68e97 Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.1097895)
11:04:54.052-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-1ada-08dcb5f68e6d Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.1097337)
11:04:54.052-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-9769-08dcb5f68e7b Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.1097292)
11:04:54.819-D Endpoint Completed: rabbitmq://localhost/TextMessage
11:04:54.822-D Consumer Completed: rabbitmq://localhost/TextMessage: 6 received, 6 concurrent, amq.ctag-c6Ccabqsa_t5luyYZDPKwQ
11:04:54.819-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-924c-08dcb5f68e7b

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:04:54.819-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-6792-08dcb5f68e97

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:04:54.819-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-5e5a-08dcb5f68e97

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:04:54.819-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-6a24-08dcb5f68e97

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:04:54.819-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-9769-08dcb5f68e7b

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:04:54.819-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-1ada-08dcb5f68e6d

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:04:55.834-D Declare queue: name: TextMessage, durable, x-consumer-timeout: 10000, consumer-count: 0 message-count: 6
11:04:55.845-D Declare exchange: name: TextMessage, type: fanout, durable
11:04:55.846-D Bind queue: source: TextMessage, destination: TextMessage
11:04:55.863-D Consumer Ok: rabbitmq://localhost/TextMessage - amq.ctag-c6Ccabqsa_t5luyYZDPKwQ
11:04:55.863-D Endpoint Ready: rabbitmq://localhost/TextMessage
11:05:55.834-D Consumer Model Shutdown: rabbitmq://localhost/TextMessage - amq.ctag-c6Ccabqsa_t5luyYZDPKwQ, Concurrent Peak: 6, 406-PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more
11:05:55.834-D Consumer Stopping: rabbitmq://localhost/TextMessage (Consume Loop Exited)
Processing batch of 6 messages
Got message: 8/6/2024 9:06:55 AM High Priority 1 High
Got message: 8/6/2024 9:06:55 AM High Priority 2 High
Got message: 8/6/2024 9:06:55 AM High Priority 3 High
Got message: 8/6/2024 9:06:55 AM High Priority 4 High
Got message: 8/6/2024 9:06:55 AM High Priority 5 High
Got message: 8/6/2024 9:06:55 AM High Priority 6 High
11:06:55.875-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-6a24-08dcb5f68e97 MassTransit.Batch<Messages.TextMessage> MyHighTextMessageConsumer(00:00:00.0005789)
11:06:55.890-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-1ada-08dcb5f68e6d Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.0262725)
11:06:55.891-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-5e5a-08dcb5f68e97 Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.0272401)
11:06:55.913-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-6792-08dcb5f68e97 Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.0484478)
11:06:55.913-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-9769-08dcb5f68e7b Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.0484459)
11:06:55.913-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-924c-08dcb5f68e7b Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.0484479)
11:06:55.954-D RECEIVE rabbitmq://localhost/TextMessage 2c730000-c333-088f-6a24-08dcb5f68e97 Messages.TextMessage MassTransit.Batching.BatchConsumer<Messages.TextMessage>(00:02:00.0904530)
11:06:56.451-D Endpoint Completed: rabbitmq://localhost/TextMessage
11:06:56.460-D Consumer Completed: rabbitmq://localhost/TextMessage: 6 received, 6 concurrent, amq.ctag-c6Ccabqsa_t5luyYZDPKwQ
11:06:56.461-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-6792-08dcb5f68e97

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:06:56.504-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-924c-08dcb5f68e7b

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:06:56.575-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-6a24-08dcb5f68e97

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:06:56.575-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-1ada-08dcb5f68e6d

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:06:56.575-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-9769-08dcb5f68e7b

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:06:56.593-E T-FAULT rabbitmq://localhost/TextMessage 2c730000-c333-088f-5e5a-08dcb5f68e97

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=491, text='Channel is already closed: AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more', classId=0, methodId=0', classId=0, methodId=0
   at MassTransit.RabbitMqTransport.RabbitMqReceiveLockContext.Complete() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqReceiveLockContext.cs:line 24
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 67
   at MassTransit.Transports.PendingReceiveLockContext.Execute(Func`2 action) in /_/src/MassTransit/Transports/PendingReceiveLockContext.cs:line 79
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 71
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 108
   at MassTransit.Transports.ReceivePipeDispatcher.Dispatch(ReceiveContext context, ReceiveLockContext receiveLock) in /_/src/MassTransit/Transports/ReceivePipeDispatcher.cs:line 115
   at MassTransit.RabbitMqTransport.RabbitMqBasicConsumer.<>c__DisplayClass21_0.<<HandleBasicDeliver>b__0>d.MoveNext() in /_/src/Transports/MassTransit.RabbitMqTransport/RabbitMqTransport/RabbitMqBasicConsumer.cs:line 168
11:06:57.470-D Declare queue: name: TextMessage, durable, x-consumer-timeout: 10000, consumer-count: 0 message-count: 6
11:06:57.480-D Declare exchange: name: TextMessage, type: fanout, durable
11:06:57.481-D Bind queue: source: TextMessage, destination: TextMessage
11:06:57.499-D Consumer Ok: rabbitmq://localhost/TextMessage - amq.ctag-c6Ccabqsa_t5luyYZDPKwQ
11:06:57.499-D Endpoint Ready: rabbitmq://localhost/TextMessage
11:07:57.470-D Consumer Model Shutdown: rabbitmq://localhost/TextMessage - amq.ctag-c6Ccabqsa_t5luyYZDPKwQ, Concurrent Peak: 6, 406-PRECONDITION_FAILED - delivery acknowledgement on channel 2 timed out. Timeout value used: 10000 ms. This timeout value can be configured, see consumers doc guide to learn more
11:07:57.470-D Consumer Stopping: rabbitmq://localhost/TextMessage (Consume Loop Exited)

Link to repository that demonstrates/reproduces the issue
https://github.com/Sirozha1337/rabbitmq-masstransit-batch-timeout-repro

I know, this is just an example. In my real life scenario this consumer_timeout was buried inside rabbitmq.conf (and was much longer naturally).
Yes, I understand and using this approach now. But when I encountered this issue, it was not obvious from the documentation and the error log. Maybe consumer_timeout should be mentioned here: https://masstransit.io/documentation/concepts/consumers#batch-consumers

Also, maybe there should be other type of BatchConsumer, that doesn't fetch messages from the queue until there are enough messages to fill the batch or if time limit is exceeded.

It's 100% a RabbitMQ thing.
RabbitMQ specific details in the general batch consumer documentation isn't likely to happen.

Messages are pushed from the broker, not pulled, so an "other type of batch consumer" isn't even feasible.

Messages are pushed from the broker, not pulled, so an "other type of batch consumer" isn't even feasible.

Ah, ok, I see. Though I don't agree about feasibility, at least with RabbitMQ as a transport. Something like this could be done by starting/stopping the consumer with BasicConsume/BasicCancel, but I guess the solution will be messy because of the possible concurrency issues.

I kept this issue open to give myself a reminder to add cancellation to batch consumers, now that's done and this will be closed.


Sql query with enum produces a where clause with the string value instead of the underlying (int) type

I have the following enum definition:
public enum Discriminator
{
    Something = 1
}

The sql produced when filtering using the enum like this:
_db.Addresses.Where(x => x.Discriminator == Discriminator.Something).ToList();

is:
SELECT [x].[Id], [x].[Discriminator]
FROM [network].[Address] AS [x]
WHERE [x].[Discriminator] = Something

It should instead be (according to #1381):
SELECT [x].[Id], [x].[Discriminator]
FROM [network].[Address] AS [x]
WHERE [x].[Discriminator] = 1

As a small fix I have changed the GenerateLiteral() in DefaultSqlQueryGenerator.cs to:
    protected virtual string GenerateLiteral([NotNull] object value)
    {
		if (value is Enum)
		{
			return string.Format(CultureInfo.InvariantCulture, "{0:d}", value);
		}
		else
		{
			return string.Format(CultureInfo.InvariantCulture, "{0}", value);
		}
    }

@natemcmaster want to give this one a try?

@divega Sure. I'll take a wack at it.

@rmja Can you provide a repro project? I was unable to get the error.
I created this sample project to reproduce the error and this is the SQL generated:
@__p_0: 1

SELECT [x].[Id], [x].[Discriminator]
FROM [Address] AS [x]
WHERE [x].[Discriminator] = @__p_0

Hi @natemcmaster. This bug was previously seen for simple queries like the one I describe in the original post, but since then, it has somehow been fixed. However, when I use the Enum as a discriminator for a polymorphic setup, then the error is still present. I have made a reproducing example here: https://gist.github.com/rmja/691506a58907c07f9ce2
My setup is slightly different, as it uses an ef base that I have modified to allow for discriminators of type object instead of string. Here is the patch:
$ git diff --cached
diff --git a/src/EntityFramework.Relational/Metadata/IRelationalEntityTypeExtensions.cs b/src/EntityFramework.Relational/Metadata/IRelationalEntityTypeExtensions.cs
index 80fb2cd..b1cf1de 100644
--- a/src/EntityFramework.Relational/Metadata/IRelationalEntityTypeExtensions.cs
+++ b/src/EntityFramework.Relational/Metadata/IRelationalEntityTypeExtensions.cs
@@ -10,6 +10,6 @@ namespace Microsoft.Data.Entity.Relational.Metadata
         string Table { get; }
         string Schema { get; }
         IProperty DiscriminatorProperty { get; }
-        string DiscriminatorValue { get; } // TODO: should be object
+        object DiscriminatorValue { get; }
     }
 }
diff --git a/src/EntityFramework.Relational/Metadata/ReadOnlyRelationalEntityTypeExtensions.cs b/src/EntityFramework.Relational/Metadata/ReadOnlyRelationalEntityTypeExtensions.cs
index 9f52ac1..00b8604 100644
--- a/src/EntityFramework.Relational/Metadata/ReadOnlyRelationalEntityTypeExtensions.cs
+++ b/src/EntityFramework.Relational/Metadata/ReadOnlyRelationalEntityTypeExtensions.cs
@@ -36,8 +36,8 @@ namespace Microsoft.Data.Entity.Relational.Metadata
                     (string)_entityType.RootType()
                         .GetAnnotation(DiscriminatorPropertyAnnotation).Value);

-        public virtual string DiscriminatorValue
-            => _entityType[DiscriminatorValueAnnotation] as string
+        public virtual object DiscriminatorValue
+            => _entityType[DiscriminatorValueAnnotation]
                ?? _entityType.DisplayName();

         protected virtual IEntityType EntityType => _entityType;
diff --git a/src/EntityFramework.Relational/Metadata/RelationalEntityTypeExtensions.cs b/src/EntityFramework.Relational/Metadata/RelationalEntityTypeExtensions.cs
index 47ac403..6ef84a8 100644
--- a/src/EntityFramework.Relational/Metadata/RelationalEntityTypeExtensions.cs
+++ b/src/EntityFramework.Relational/Metadata/RelationalEntityTypeExtensions.cs
@@ -68,7 +68,7 @@ namespace Microsoft.Data.Entity.Relational.Metadata
             }
         }

-        public new virtual string DiscriminatorValue
+        public new virtual object DiscriminatorValue
         {
             get { return base.DiscriminatorValue; }
             [param: CanBeNull] set { EntityType[DiscriminatorValueAnnotation] = value; }
diff --git a/src/EntityFramework.Relational/Query/Sql/DefaultQuerySqlGenerator.cs b/src/EntityFramework.Relational/Query/Sql/DefaultQuerySqlGenerator.cs
index ec12634..d11a5f2 100644
--- a/src/EntityFramework.Relational/Query/Sql/DefaultQuerySqlGenerator.cs
+++ b/src/EntityFramework.Relational/Query/Sql/DefaultQuerySqlGenerator.cs
@@ -860,6 +860,9 @@ namespace Microsoft.Data.Entity.Relational.Query.Sql
         protected virtual string GenerateLiteral([NotNull] object value)
             => string.Format(CultureInfo.InvariantCulture, "{0}", value);

+        //protected virtual string GenerateLiteral(Enum value)
+        //    => string.Format(CultureInfo.InvariantCulture, "{0:d}", value);
+
         protected virtual string GenerateLiteral(int value)
             => value.ToString();

The commented lines in the last file "fixes" the problem. Here is the produced invalid SQL:
exec sp_executesql N'SELECT [x].[Id], [x].[Discriminator]
FROM [Address] AS [x]
WHERE ([x].[Discriminator] IN (EmployeeAddress, CustomerAddress) AND [x].[Discriminator] = @__p_0)',N'@__p_0 int',@__p_0=1
go

I have tried to use, in MyContext.cs in the repro, e.g.:
customer.Relational().DiscriminatorValue = (int)Discriminator.CustomerAddress;

instead of:
customer.Relational().DiscriminatorValue = Discriminator.CustomerAddress;

but that leads to invalid cast exception.
Let me know if you need more info.

Thanks for posting this very detailed repro. This helps a lot when trying to replicate the errors you see.
It appears to me the invalid SQL you are seeing is a result of the changes you made to EF. The patch you included takes care of compiler type-checking, but doesn't account for the type-assumptions in query. The SQL generation produces invalid SQL because query generation assumes the discriminator value is a string (for now). Allowing DiscriminatorValue to support object will require additional changes to the query pipeline.
This issue has grown into feature request rather than a bug in query. I'd recommend closing this issue and creating a new issue to request DiscriminatorValue as an object, not just a string.

@natemcmaster you are right. The error is not the same as the one I original posted, as it is now only visible in the inheritance setup. I will close and make a feature request.


No entries in playlist on random mix

Hello,
When I upgraded from 1.7.1 to 1.8.0 I noticed that when create a "Random Mix" under My Music that nothing gets shows in the queue. The mix still plays and I can still move to previous and next tracks.
This is in Chrome verison 83 on OSX; I did not check other browsers. I confirmed that it works normally when I downgraded back to 1.7.1.

This will be the issue with disc/track numbers discussed on forms.slimdevices.com. Already fixed in 1.8.1 - released 4 days ago.

Thanks! Apologies for the duplicate.


🎉🎊🍾 [New Feature] Implement the feature about URL with variable for Flask web framework.

Target

Implement the feature about URL with variable for Flask web framework.

Effecting Scope

Add new feature without any breaking changes.

Description

Let the function generates Python code for API function to be abstract method and move the implementation into sub-classes.
Add the logic to process the API which has variable(s) in URL for web framework Flask.
Add more tests to cover this feature.

About the one issue which be reported by SonarQube, it will be fixed in next PR so ignore it now.


Control-Autopilost model

Hi Prof. Fossen,
I use the "Course autopilot" module in the MSS Simulink Library /Control/Autopilots. Can you help me to explain how the module work? Besides,  where is the source code of the module?
Thank you very much.

You find the Simulink library blocks after typing: >>mssSimulink, in the Matlab workspace. The course autopilot is based on Algorithm 15.1 in my Wiley (2021) textbook. This is a SISO PID pole-placement algorithm for vehicles. You will also find the algorithm in my lecture notes, which can be downloaded from [https://wiley.fossen.biz]. The design of heading and course autopilots are explained in detail in my book; see Chapters 7 and 15.3.4.


Rewrite PDB secondary structure reading to use file order of residues

Fixes issue #342 by rewriting how secondary structures are read in PDB files. Instead of relying on a map with ordered residue information, this PR sets a 'flag' which contains the current residue secondary structure (as a string) and the final residue which has the given secondary structure. This, in effect, causes secondary structures to be read in the same order as the PDB.

I tried to parse the whole PDB archive with 0.9.3 and this, and this fixes all segfaults!

Glad there are no more segfaults! Don't have as much time to code with my new position - but I'll still try to contribute!

I checked half of the PDB archive before my script crashed, and none have HELIX or SHEET records after ATOM records. So even if this is not guaranteed by the standard as far as I understand, I think we can merge this!

Great!
On Thu, Jul 30, 2020, 10:57 AM Guillaume Fraux<EMAIL_ADDRESS>wrote:

I checked half of the PDB archive before my script crashed, and none have
HELIX or SHEET records after ATOM records. So even if this is not
guaranteed by the standard as far as I understand, I think we can merge
this!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chemfiles/chemfiles/pull/343#issuecomment-666426240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPGUAMJNLQWES3ZSSZF5B3R6GC5ZANCNFSM4NQHEZMQ
.


Support PyTorch=1.5

Hi.
Currently the pointgroup library doesn't compile correctly in Pytorch 1.5.
I get the following errors when i try to compile

In file included from src/pointgroup_ops.cpp:8:0:
src/bfs_cluster/bfs_cluster.cpp:32:58: error: ‘THCState_getCurrentStream’ was not declared in this scope

src/bfs_cluster/bfs_cluster.cpp:9:80: error: ‘AT_CHECK’ was not declared in this scope

These two errors can be easily solved and the pointgroup library can be made compatible with PyTorch 1.5. In bfs_cluster.cpp following changes need to be made:

Replace THCState_getCurrentStream with at::cuda::getCurrentCUDAStream().
https://stackoverflow.com/questions/55919123/cuda-for-pytorch-cuda-c-stream-and-state
Replace AT_CHECK with TORCH_CHECK.

With the above mentioned changes, i was able to compile Pointgroup library with PyTorch 1.5, and Cuda 10.2.
Thanks.

Thanks!
I have made some corresponding changes in 'pointgroup_ops' to make it compatible with Pytorch 1.5.

Hi @sidml
May I ask how did you resolve the compatibility issues on spconv part? I am using the same environment with you (PyTorch 1.5 + cuda 10.2), but I cannot compile spconv in the first stage. And for pointgroup_ops, the new commit from @llijiang leads to a ImportError: libcudart.so.10.0. I guess it is still not compatible with CUDA-10.2.
I am digging into the details, but please let me know if you have already solved it. Thank you in advance.

Torch 1.5 has a problem with the nonzero function, the call for ballquery_batch_p gives an error due to the nonzero call.
/pytorch/torch/csrc/utils/python_arg_parser.cpp:756: UserWarning: This overload of nonzero is deprecated:         nonzero(Tensor input, *, Tensor out) Consider using one of the following signatures instead:         nonzero(Tensor input, *, bool as_tuple) CUDA kernel failed : invalid configuration argument
Does anyone have a similar problem?


get_work optimizations

This combines three optimizations for get_work. The first one removes the number of dependencies computation from ranking, as I noticed that this was a large component of get_work time and I no longer think it makes much of a difference overall. Next, I limit upstream_status computation to not look past DONE tasks, giving a decent performance boost when many tasks are DONE. Finally, I remove unnecessary computation in get_work that occurs after finding a best_task.

LGTM. Very nice that you split up the commits. I really want to merge. Anyone else wants to review first?

LGTM

Thanks @daveFNbuck! :)

No problem. I hope this works well for you guys too.
On Wed, Jul 8, 2015 at 5:13 AM, Arash Rouhani<EMAIL_ADDRESS>wrote:

Thanks @daveFNbuck https://github.com/daveFNbuck! :)
—
Reply to this email directly or view it on GitHub
https://github.com/spotify/luigi/pull/1046#issuecomment-119554695.


Make message bubble text color black if primary color has high luminance value

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @tneot01 in #feedback.

Done, needs testing


Inconsistency in UI for read-only access (Docker)

Bug description
A user with read-only access to some environment sees 2 sets of Docker instance stats:

/home page ("Environments") shows actual numbers

/$id/docker/dashboard page one click away ("Environment info") shows zeroes because no configuration was made yet, besides creating that user and granting RO access to the env.

Documentation I could find says: Read-Only User has read-only access to the resources they are entitled to see (resources created by members of their team, and public resources).
I can change those zeroes to something like "0 running, 1 stopped" by changing ownership of some random container. It behaves as it should per documentation.
Expected behavior
Numbers should match at both pages. Home page should display zeroes in my case, because the user has not been entitled to see 'real' numbers
Technical details:

Portainer version: BE 2.18.2
Docker version (managed by Portainer): 20.10.3
Platform (windows/linux): Linux on Synology NAS
Command used to start Portainer: docker run -d -p 59000:9000 --name=portainer --restart=always --pull=always -v /var/run/docker.sock:/var/run/docker.sock -v /volume1/share1/portainer/data:/data cr.portainer.io/portainer/portainer-ee:latest
Browser: Brave, Edge, Firefox
Use Case (delete as appropriate): Using Portainer at Home
Have you reviewed our technical documentation and knowledge base? Yes

Confirmed.
Thanks for raising the issue.


Use MixAll.isPropertyValid() in Validators.checkBrokerConfig()

The issue tracker is used for bug reporting purposes ONLY whereas feature request needs to follow the RIP process. To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
It is recommended to start a discussion thread in the mailing lists or github discussions in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
Generally, fixing an issue goes through the following steps:

Understand the issue reported;
Reproduce the unexpected behavior locally;
Perform root cause analysis to identify the underlying problem;
Create test cases to cover the identified problem;
Work out a solution to rectify the behavior and make the newly created test cases pass;
Make a pull request and go through peer review;

As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
BUG REPORT

Please describe the issue you observed:

What did you do (The steps to reproduce)?

What is expected to see?

What did you see instead?

Please tell us about your environment:

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

FEATURE REQUEST

Use MixAll.isPropertyValid() in Validators.checkBrokerConfig().

There is an todo, so I attempt to fix it.

Hi is any one working on this , can i contribute to this?
@Oliverwqcwrw @derecknowayback

@aditya-32 @derecknowayback has submitted a PR(#6551), and you may help review it.

Hi is any one working on this , can i contribute to this? @Oliverwqcwrw @derecknowayback


Update locales/vi-VN/translation.json

Description
Fixed translation errors in Vietnamese locale file locales/vi-VN/translation.json

Changelog Entry
Added
None
Changed

locales/vi-VN/translation.json

Removed
None

Thanks!


jest --coverage fails with cov_xxx is not a function

🐛 Bug Report
Jest works fine without coverage:
> yarn run jest src/__tests__/util.js
yarn run v1.22.4
$ /Users/xxx/proj/node_modules/.bin/jest src/__tests__/util.js
 PASS  src/__tests__/util.js
  ✓ simple equivalence (3 ms)
  ✓ array equivalence
  ✓ unicode equivalence (1 ms)

Test Suites: 1 passed, 1 total
Tests:       3 passed, 3 total
Snapshots:   0 total
Time:        1.006 s
Ran all test suites matching /src\/__tests__\/util.js/i.
✨  Done in 1.98s.

And fails mysteriously with coverage:
> yarn run jest src/__tests__/util.js --coverage
yarn run v1.22.4
$ /Users/xxx/proj/node_modules/.bin/jest src/__tests__/util.js --coverage
 FAIL  src/__tests__/util.js
  ● Test suite failed to run

    TypeError: cov_8p5fsfkjt is not a function

      at Object.<anonymous> (src/util.js:3267:1)
      at Object.<anonymous> (src/__tests__/util.js:1:1)

----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |       0 |        0 |       0 |       0 |
----------|---------|----------|---------|---------|-------------------
Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.025 s
Ran all test suites matching /src\/__tests__\/util.js/i.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I certainly have a total mess in my project (and thus ashamed to post a link), but this is just... too unexpected.
In short, it's a CRA project with config override, type:module and I'm testing simple utilities.
(there's JSX, babel, etc., in the project, but nothing fancy in this code under test or tests).
If there are some hints how to narrow down the scope, I'd appreciate it :)
envinfo

  System:
    OS: macOS 10.15.4
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 13.12.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
  npmPackages:
    jest: ^26.0.1 => 26.0.1

Uh-oh, fixed by "ripping all babel config out of project.json", nevermind!


Enable "chunked compression" of DataArrays in VTU files

This PR factors the DataArray compression for VTU files into a common function, and generalizes the data header we write from a single chuck that contains all the data to now handle chunks of a client-selectable size. However, note that at the moment the client-facing method (as opposed to the implementation method) hard-codes a default 4 MB size.
This PR does not implement any threading for the chunk compressions.
I tested this PR by running the VTU test, then running the tet4.vtu file through an MFEM driver to confirm it reads the compressed data correctly.

Thanks, this looks great so far. I think we also should add at least one test where the mesh is big enough to require multiple compressed blocks, to ensure that part of the code is working correctly.
It's probably easiest to procedurally generate a mesh of n disjoint elements. That way, the vertex positions and connectivity lists are trivial to implement, but the mesh can be made arbitrarily large (without having to store a big mesh file in the data directory).

Sure, that's a good idea. I'm on the hook for slides today, but I'll write the test tomorrow morning.


Create basic widgets from Tk

Implement all Tk widgets into rTk.
Basic: Frame, Lable, Button, Entry
Medium: Canvas, OptionMenu, CheckButton, RadioButton
Advanced: Menu + MenuButton, ListBox, Scale

Most cWidgets (custom Widgets) have been created.
Frame, Lable, Button, Entry and OptionMenu are all fully completed.
Canvas has been started.
The rest still need completing with full documentation and examples.


Change Metadata about a Test Set Submission

Hi,
I want to change the metadata about one of my submissions to 3d detection leaderboard. The id is CenterPoint. Basically, I used two frames but forgot to change the field in the info file. Could you help me fix this or refer me to anyone that can fix this?

Hi,
I usually do not mutate users' data. It is easier if you submit a new version and i can delete your last version.
Pei

Hi,
I usually do not mutate users' data. It is easier if you submit a new version and i can delete your last version.
Pei

Thanks! Could you delete my old submission then?

Thanks! Could you delete my old submission then?

Deleted.

Deleted.


Meta

Add correct description + url to:

meta descriptions on index.html
package.json
readme.md

@carderne @Naigege What description do you want to add?

@olafveerman
For readme.md, we could use the About text? Will share shortly.
For the other two, what you have should be sufficient I think.

A visualization of the electricity grid in Sub Saharan Africa.


compile error

Hi, I try to install it in Ubuntu, I download the source code and run make all.
Then I got such errors
python2.7 setup.py build_ext --inplace
Autogenerating opengl sources
Compiling contexts/ctx_mesa.pyx because it changed.
[1/1] Cythonizing contexts/ctx_mesa.pyx
Error compiling Cython file:
...
"""
^
contexts/ctx_mesa.pyx:1:0: 'opendr-master.contexts.ctx_mesa' is not a valid module name
Traceback (most recent call last):
File "setup.py", line 153, in
main()
File "setup.py", line 149, in main
setup_opendr([mesa_ext()])
File "setup.py", line 63, in setup_opendr
ext_modules=cythonize(ext_modules)
File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 877, in cythonize
cythonize_one(*args)
File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 997, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: contexts/ctx_mesa.pyx
Makefile:3: recipe for target 'all' failed
make: *** [all] Error 1
Can you help me?

Same problem with Ubuntu 16.04. Any help?

you can use pip to install opendr, if the problem persists

Same problem with 16.04 when using this git version as above. And with pip I get:
pip install opendr
Collecting opendr
Using cached opendr-0.76.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-r609yikz/opendr/setup.py", line 40
print "Downloading %s" % osmesa_fname
^
SyntaxError: Missing parentheses in call to 'print'
----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-r609yikz/opendr/

@runa91, you're likely running it with pip from python 3.. This package only supports python 2.

Same problem. Did you solve it?
I am using pip to install with Python 2.7 but I get the following error:
Cython.Compiler.Errors.CompileError: contexts/ctx_mesa.pyx
Command "python setup.py egg_info" failed with error code 1

I have successfully installed by using 'pip install opendr‘ with python2!!!!

@SpiritBear000 Please let us know the information how to solve this problem.

@SpiritBear000 Please let us know the information how to solve this problem.

Just using command ‘pip install opendr’ . But only work in python2 env

Just using command ‘pip install opendr’ . But only work in python2 env

I have successfully installed opendr with python2, but not with pip install opendr.
take the following steps:

git clone opendr repo:

git clone https://github.com/mattloper/opendr

wget download OSMesa to opendr/contexts directory:

wget http://files.is.tue.mpg.de/mloper/opendr/osmesa/OSMesa.Linux.x86_64.zip

create conda environment with python2.7. (opendr only works for python2.x. I use python3.x in the beginning and it failed)
install opendr

cd opendr && python setup.py install

After install, copy the opendr directory to site-packages of your anaconda environment directory (such as: anaconda --> envs --> pythonx.x --> lib --> pythonx.x --> site-packages). Otherwise, you will encounter some errors like:
ModuleNotFoundError: No module named 'opendr.contexts.ctx_mesa'

Another error may occur:
No module names '_constraints'

This can be fixed with modifying the line which import _constants.py to absolute path (from opendr.contexts._constants import *) in opendr/contexts/ctx_base.pyx

I have successfully installed opendr with python2, but not with pip install opendr.
take the following steps:

git clone opendr repo:

git clone https://github.com/mattloper/opendr

wget download OSMesa to opendr/contexts directory:

wget http://files.is.tue.mpg.de/mloper/opendr/osmesa/OSMesa.Linux.x86_64.zip

create conda environment with python2.7. (opendr only works for python2.x. I use python3.x in the beginning and it failed)
install opendr

cd opendr && python setup.py install

After install, copy the opendr directory to site-packages of your anaconda environment directory (such as: anaconda --> envs --> pythonx.x --> lib --> pythonx.x --> site-packages). Otherwise, you will encounter some errors like:
ModuleNotFoundError: No module named 'opendr.contexts.ctx_mesa'

Another error may occur:
No module names '_constraints'

This can be fixed with modifying the line which import _constants.py to absolute path (from opendr.contexts._constants import *) in opendr/contexts/ctx_base.pyx

This is the conda list:
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main
_openmp_mutex             5.1                       1_gnu
backports-functools-lru-cache 1.6.6                    pypi_0    pypi
ca-certificates           2023.08.22           h06a4308_0
certifi                   2020.6.20          pyhd3eb1b0_3
chumpy                    0.70                     pypi_0    pypi
cloudpickle               1.3.0                    pypi_0    pypi
cycler                    0.10.0                   pypi_0    pypi
cython                    3.0.5                    pypi_0    pypi
decorator                 4.4.2                    pypi_0    pypi
kiwisolver                1.1.0                    pypi_0    pypi
libffi                    3.4.4                h6a678d5_0
libgcc-ng                 11.2.0               h1234567_1
libgomp                   11.2.0               h1234567_1
libstdcxx-ng              11.2.0               h1234567_1
matplotlib                2.2.5                    pypi_0    pypi
ncurses                   6.4                  h6a678d5_0
networkx                  2.2                      pypi_0    pypi
numpy                     1.16.6                   pypi_0    pypi
opencv-python             <IP_ADDRESS>                 pypi_0    pypi
opendr                    0.77                     pypi_0    pypi
pillow                    6.2.2                    pypi_0    pypi
pip                       19.3.1                   py27_0
pyparsing                 2.4.7                    pypi_0    pypi
python                    2.7.18               h42bf7aa_3
python-dateutil           2.8.2                    pypi_0    pypi
pytz                      2023.3.post1             pypi_0    pypi
pywavelets                1.0.3                    pypi_0    pypi
readline                  8.2                  h5eee18b_0
scikit-image              0.14.5                   pypi_0    pypi
scipy                     1.2.3                    pypi_0    pypi
setuptools                44.0.0                   py27_0
six                       1.16.0                   pypi_0    pypi
sqlite                    3.41.2               h5eee18b_0
subprocess32              3.5.4                    pypi_0    pypi
tk                        8.6.12               h1ccaba5_0
transforms3d              0.3.1                    pypi_0    pypi
wheel                     0.37.1             pyhd3eb1b0_0
zlib                      1.2.13               h5eee18b_0


Fix --alt-adios2-dir option of build_visit script

Description
Resolves #3505
Type of change

[x] Bug fix
[ ] New feature
[ ] New Documentation
[ ] Other (please describe below)

How Has This Been Tested?
Tested on my workstation (Fedora 29).
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[ ] I have added debugging support to my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have added any new baselines to the repo
[ ] I have assigned reviewers (see VisIt's PR procedures for more information).

@dpugmire Can you please review this PR? I need this to build VisIt with the latest ADIOS2.


Add a temporary fix for travis-ci build

Trying to fix travis-ci build due to a lerna bug in v2.1.2
https://github.com/lerna/lerna/pull/897#issuecomment-324817648

This doesn't seem to fix the build failing completely 😕

It turned out that this issue caused by migration of Travis build environments from Ubuntu Precise to Ubuntu Trusty which has yarn v0.17.8 pre installed. Sorry for my misunderstanding.


bugfix: use the '__' format for model contract names

Description
To avoid having conflicts between several models with a same name but in different namespaces, the model contract name now follow the following format: <namespace>__<name>.
Note that the double underscore __ is used as the separator between namespace and name. That means it should not be used in namespace and name. So, we probably should  raise a warning/error if it's the case.
Related issue
https://github.com/dojoengine/dojo/issues/2349
Tests

[X] Yes
[ ] No, because they aren't needed
[ ] No, because I need help

Added to documentation?

[ ] README.md
[ ] Dojo Book
[X] No documentation needed

Checklist

[X] I've formatted my code (scripts/prettier.sh, scripts/rust_fmt.sh, scripts/cairo_fmt.sh)
[X] I've linted my code (scripts/clippy.sh, scripts/docs.sh)
[X] I've commented my code
[X] I've requested a review after addressing the comments

Summary by CodeRabbit

New Features

Enhanced naming conventions for various models and events to improve clarity and organization.
Introduced new contract selector structures for better contract path management.

Bug Fixes

Updated references in model registrations and event names to prevent potential conflicts and improve functionality.
Revised expected values in test assertions to align with updated logic and behavior.

Chores

Cleaned up import statements in the codebase to streamline dependencies and improve maintainability.
Modified formatting scripts to allow users to choose between checking and applying formatting.

I'm trying to see any other option than having an arbitrary separator that may be messed up depending on how the user names the contract.
But it seems we don't have much alternative for now.

Yes, I agree but I think it's not a really big constraint to avoid using __ in a struct name (for models or events) or in a contract name (for contracts). And we can check it at compile time to raise a warning/error to inform the dev and avoid him searching for hours why something fails 😅

Replaced by https://github.com/dojoengine/dojo/pull/2457.


correcting the disk calculation

Description

Issue

Closes: #

I believe the original is correct, if you take into account evictionHard then the original is correct

Please add a description to the PR and a reason why this change is proposed

my bad, current calculations are correct.


oxygenctl bump is causing deployment to fail

After commit 9952bd346c94006c5b5ace53ec9e654f3323facf deployment always fails with one of the following reasons:

Failed to create build. Labels is invalid
Failed to create deployment. Namespace must exist (if build has been successful)

Rollback to commit before oxygenctl bump to 4.4.0 solves the issue.

I was wrong, using the previous version does not work, it just worked once for me, but after retry it failed again. I don't know what's the problem, but 5 days ago I could successfully deploy new storefront versions to Shopify and now it fails. Even if I retry to deploy storefront commit that was successfully deployed 7 days ago it would fail now with one of the errors mentioned avobe

I was wrong, using the previous version does not work, it just worked once for me, but after retry it failed again. I don't know what's the problem, but 5 days ago I could successfully deploy new storefront versions to Shopify and now it fails. Even if I retry to deploy storefront commit that was successfully deployed 7 days ago it would fail now with one of the errors mentioned avobe

Sorry did not see this at the time, but I am guessing the problem has been resolved now?


Corrected toc entry for the New-AzureADMSAdministrativeUnitMember cmdlet

Docs Build status updates of commit 463c75f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mapping/groupMapping-2.0-preview.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@CelesteDG, please review this to correctly map once of the newly released cmdlets on the TOC. Thanks.


Classify.py issue

Hi,
I was trying to run the samovar pipeline. All went very smooth until the classify step.
I've encountered an indentation issue in the classify.py script (try/except at row 36).
After having fixed it another error came out.
Traceback (most recent call last):
  File "/scratch/galeoni/software/samovar/pipeline/3.classifyAndFilter/classify.py", line 36, in <module>
    predictionArray[i] = np.array(eval(L)[3:])#field 0 is chrom; field 1 is pos; field 2 is minor allele base; rest are features
  File "<string>", line 1, in <module>
TypeError: list indices must be integers, not tuple

I've run it with python 2.7.15 that should be ok since I've noticed that classify was tested even with python 2.7.10.
Since I'm not a pythonist do you have any suggestion to how fix it?
Thanks in advance,
Gabriele

I updated the file with corrected indentation in the latest commit. The "classify" step on the example dataset works for me now, on Python 2.7.15 - do you still have an issue?

Hi,
with the new release, it seems to works as expected!
Thanks,
Gabriele

Hi,
It seems that I spoke too soon.
After having tried the new release I was able to successfully run all the samovar pipeline with the example dataset. This was true also for some dataset that I'm working on. However, there were two samples, out of 8, for which the pipeline retrieved the very same error during the classify step as before.
Traceback (most recent call last):   File "./classify.py", line 36, in <module>     predictionArray[i] = np.array(eval(L)[3:])#field 0 is chrom; field 1 is pos; field 2 is minor allele base; rest are features   File "<string>", line 1, in <module> TypeError: list indices must be integers, not tuple
Since all the bam files were processed in the very same way and with the same parameters I'm not able to understand why the software is complaining. In particular options were:
--variantspacing of generateVarFile.py set to 50000
--max in train.py set to 30000
Do you have any suggestions?
Thanks in advance,
Gabriele

Are you able to print the specific line from the features file that causes this error? (e.g. with a try-except block) It could be that the features file was incorrectly formatted by the filter step.

Dear Charlotte,
I think that I found Waldo!
As you suggested I took a look at the vector files of the two not working
samples. I've found that only in these there was a missing terminator
character in one row.
I'll paste here an example, ][ in bold:
[u'6', 43903132, 'C', 45, 0.6888888888888889, 0.5806451612903226,
0.17777777777777778, 0.1935483870967742, 6, 0.1935483870967742, 37.0, 1.0,
0.13333333333333333, 20.166666666666668, 1.0, 0.6666666666666666, 67.5,
35.0, 0.72, 0.5555555555555556, 28.96, 1.92, 2.28, 71.56,
0.2023701002734731, 37.0, 19.5, 13.375, 0.875, 58.5, 0.19084461637653127,
33.91891891891892, 25.243243243243242, 21.45945945945946,
1.945945945945946, 57.054054054054056*][*u'6', 86030497, 'T', 33,
0.9393939393939394, 0.5806451612903226, 0.15151515151515152,
0.16129032258064516, 5, 0.16129032258064516, 37.0, 1.0,
0.15151515151515152, 26.6, 28.0, 0.0, 49.2, 35.53846153846154,
0.6923076923076923, 0.7878787878787878, 27.807692307692307,
16.26923076923077, 5.153846153846154, 57.69230769230769,
0.16681695220919748, 37.0, 26.6, 28.0, 0.0, 49.2, 0.15638207945900254,
35.642857142857146, 25.892857142857142, 19.928571428571427,
4.785714285714286, 55.42857142857143]
Adding a terminator character solved the problem.
Thanks for your support,
Gabriele
On Fri, Apr 5, 2019 at 8:29 PM Charlotte Darby<EMAIL_ADDRESS>wrote:

Are you able to print the specific line from the features file that causes
this error? (e.g. with a try-except block) It could be that the features
file was incorrectly formatted by the filter step.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cdarby/samovar/issues/1#issuecomment-480377971, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AmfWObOmxJVfQN99JlkgEUSaM-kt48oUks5vd5YOgaJpZM4beFT7
.

--
Gabriele Leoni,
PhD student in Functional Genomics
Scuola Internazionale Superiore di Studi Avanzati (SISSA)
E-mail<EMAIL_ADDRESS><EMAIL_ADDRESS>*Tel: *0403787772


refactor: Move error / logging functionality from telemetry-utils to core-interfaces

This is part of an effort to remove the container-utils package. The objective is to move the error types in that package to core-interfaces. In order to do this, we first have move the necessary type dependencies from container-definitions and telemetry-utils into core-interfaces. This PR tackles moving the relevant items from telemetry-interfaces.

Associated PR moving items from container-definitions: #16868


Add position data to OnDragEnd callback

This PR adds localPosition/globalPosition data to the DragEndDetails argument of the onDragEnd callback. Those offsets return position of the cursor when the callback is triggered.
Fixes #140377

(triage fly-by comment): it looks like this change is failing many checks. Can you please take a look? Thank you!

@goderbauer All the tests have passed. This should be good for review now :)

(triage) @whiskeyPeak Just checkin in to see if you can address the two nits given above so we can land this? Thanks.


Set up project builds on Windows and MacOS.

Make sure the project builds on Windows and MacOS.

And I think appveyor can be removed now

It is harmless, I will ignore it for now :) Jenkins is the pain, today.


Component doesn't remove ancestryChangedHandle from the component class' trove when an instance is untagged

Right now there's a minor memory leak with the Component module. When an instance is untagged, it will disconnect the ancestryChangeHandle connection and remove it from watchingInstances, but not from the component class' trove. To fix this, InstanceUntagged should be something along these lines:
local function InstanceUntagged(instance: Instance)
	local watchHandle = watchingInstances[instance]
	watchingInstances[instance] = nil

	self[KEY_TROVE]:Remove(watchHandle)

	TryDeconstructComponent(instance)
end

You can kill two birds with one stone by using Trove:Remove() to disconnect the connection and to remove its reference from the component class' trove.

Sorry for the exactly 1-year delay on this. Looking into this now.


Change log level from warning to error

This is a proposal to change the log level from warning to error in the AckProcessor processor.
I changed it in order to be more in line with the semantics of the AckProcessor. In my mind, exceptions are errors and should be logged as this.
Plus, the PSR Log Interface gives us some hint on the right log level we should use:

error level doc
warning level doc

Makes sense. :)
Thanks!


CREATE AN ABOUTUS PAGE

Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'Hacktoberfest' contributors of 'FIFA WORLD CUP 2022 Project'.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID (If not, then put NA) :
Approach for this Project :
What is your participant role? (Mention the Open Source Program name. Eg. HRSoC, GSSoC, GSOC, Hactoberfest etc.)

DESCRIPTIONS:

The AboutUs should contact the details about FIFA WORLD CUP 2022.
Design of the page should match with index page.
The project file must be uploaded in the Projects Folder.

Hi @Nirvik07 . I would love to give this issue a go. Could you assign this to me?

Would love to take on this issue

@scarnation you can't work on this. It is first come, first assign case according to the code of conduct of Hactoberfest and Open Source.

@appledora please fill out the google form in the contributing.md. If you have already done, then start with your issue.

Thanks @Nirvik07 , I will fill up the form.

alright

can i get assigned another screen


Error converting array to scalars in subset.subset_shape

xclim version: 0.16.0
Python version: PAVICS
Operating System: PAVICS

Description
I was subsetting a shapefile to be used to calculate ensemble percentiles. The shapefile has multiple watershed sub-boundaries.
What I Did
import geopandas as gpd
shp = 'GIS-Data/Beaver.shp'
gdf = gpd.GeoDataFrame.from_file(shp)

# use more percentiles in this example
perc_val = [5, 10, 25, 50, 75, 90, 95]

fig = gdf.plot(facecolor='white')
with ProgressBar():
    dsEnsPoly = subset.subset_shape(dsEns, shape=shp)
    dsPercPoly = ensembles.ensemble_percentiles(dsEnsPoly, values=perc_val)

What I Received
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-30-5aaec4dd7e8c> in <module>
     10 fig = gdf.plot(facecolor='white')
     11 with ProgressBar():
---> 12     dsEnsPoly = subset.subset_shape(dsEns, shape=shp)
     13     dsPercPoly = ensembles.ensemble_percentiles(dsEnsPoly, values=perc_val)
     14     dsPercPoly.sel(time='2041').tg_mean_p50.plot()

/usr/local/envs/birdy/lib/python3.7/site-packages/xclim/subset.py in func_checker(*args, **kwargs)
    206             formatted_args.append(argument)
    207
--> 208         final = func(*formatted_args, **kwargs)
    209
    210         for k, v in conv.items():

/usr/local/envs/birdy/lib/python3.7/site-packages/xclim/subset.py in subset_shape(ds, shape, raster_crs, shape_crs, buffer, wrap_lons, start_date, end_date)
    477     # Get the shape's bounding box
    478     bounds = poly.bounds
--> 479     lon_bnds = (float(bounds.minx.values), float(bounds.maxx.values))
    480     lat_bnds = (float(bounds.miny.values), float(bounds.maxy.values))
    481

TypeError: only size-1 arrays can be converted to Python scalars

Further Investigation
poly = gpd.GeoDataFrame.from_file('GIS-Data/Aguasabon_Project.shp')
poly
bounds = poly.bounds
bounds
#float(min(bounds.minx.values))
#float(max(bounds.maxx.values))

minx	miny	maxx	maxy
0	-87.464326	49.216421	-86.632188	49.816493
1	-87.441197	49.067714	-86.342397	50.158592
2	-87.347309	48.771573	-86.930992	49.280212
The last two comments could fix the issue if they meet the intent of the rest of the code.

@kckornelsen thx for the bug report.  I am not sure that we tested a mutli polygon shape for the subsetting here.  Should be a simple fix.

Woups, exactly, the call should be poly.total_bounds. When we added multi polygon support to create_mask*, we forgot to change it there. Working on it.

GeoSeries.total_bounds

@aulemahal beat me to it.

@kckornelsen while waiting for the update you could potentially try to use a workaround  similar to belwo by making a mask of the multiple poygons via subset.create_mask..   This should assign the polygon index value of the geodataframe to the xarray dataset.   Note I didn't actually test the code so let me know if you need more assistance
    bbox = dict(lon=poly.total_bounds[0::2], lat=poly.total_bounds[1::2])
    ds = subset.subset_bbox(ncfile, lon_bnds=bbox['lon'], lat_bnds=bbox['lat'])
    mask_2d = subset.create_mask(x_dim=ds.lon, y_dim=ds.lat, poly=poly)
    mask_2d = mask_2d.transpose()
    ds = ds.assign_coords(region=mask_2d)
    # select single region with index == 0
    ds1 = ds.sel(region=0)


rathole::server: Failed to read hello

Describe the bug
rathole server端频繁出现error日志
client和server可以正常通信
To Reproduce
Steps to reproduce the behavior:

启动server端之后一段时间就会出现这种情况

Configuration
Configuration used to reproduce the behavior:
#server.toml
[server]
bind_addr = "<IP_ADDRESS>:7000" # `2333` specifies the port that rathole listens for clients

[server.services.my_nas_ssh]
token = "K8twY" # Token that is used to authenticate the client for the service. Change to a arbitrary value.
bind_addr = "<IP_ADDRESS>:5000" # `5202` specifies the port that exposes `my_nas_ssh` to the Internet

[server.services.my_asus]
token = "K8twY"
bind_addr = "<IP_ADDRESS>:5001"

[server.services.my_haikang]
token = "K8twY"
bind_addr = "<IP_ADDRESS>:5002"

[client]
remote_addr = "xxxx:7000"
default_token = "K8twY"

[client.services.my_nas_ssh]
local_addr = "<IP_ADDRESS>:1025"

[client.services.my_asus]
local_addr = "<IP_ADDRESS>:80"

Logs

nohup: ignoring input
Feb 11 15:19:21.776  INFO rathole::server: Listening at <IP_ADDRESS>:7000
Feb 11 15:19:21.776  INFO config_watcher{path="server.toml"}: rathole::config_watcher: Start watching the config
Feb 11 15:19:22.637  INFO connection{addr=<IP_ADDRESS>:60892}: rathole::server: Try to handshake a control channel
Feb 11 15:19:22.645  INFO connection{addr=<IP_ADDRESS>:50017}: rathole::server: Try to handshake a control channel
Feb 11 15:19:22.655  INFO connection{addr=<IP_ADDRESS>:60892}: rathole::server: Control channel established service=my_nas_ssh
Feb 11 15:19:22.655  INFO connection{addr=<IP_ADDRESS>:60892}:handle{service=my_nas_ssh}:run_tcp_connection_pool: rathole::server: Listening at <IP_ADDRESS>:5000
Feb 11 15:19:22.663  INFO connection{addr=<IP_ADDRESS>:50017}: rathole::server: Control channel established service=my_asus
Feb 11 15:19:22.663  INFO connection{addr=<IP_ADDRESS>:50017}:handle{service=my_asus}:run_tcp_connection_pool: rathole::server: Listening at <IP_ADDRESS>:5001
Feb 11 16:22:31.616 ERROR connection{addr=<IP_ADDRESS>:33886}: rathole::server: Failed to read hello: early eof
Feb 11 20:43:04.271 ERROR connection{addr=<IP_ADDRESS>:51530}: rathole::server: Failed to read hello: early eof
Feb 11 21:22:48.898 ERROR connection{addr=<IP_ADDRESS>:32033}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 21:22:59.348 ERROR connection{addr=<IP_ADDRESS>:44769}: rathole::server: Failed to read hello: early eof
Feb 11 21:22:59.600 ERROR connection{addr=<IP_ADDRESS>:58508}: rathole::server: Failed to deserialize hello: invalid value: integer `671088768`, expected variant index 0 <= i < 2
Feb 11 21:23:10.762 ERROR connection{addr=<IP_ADDRESS>:10343}: rathole::server: Failed to read hello: early eof
Feb 11 21:36:30.045 ERROR connection{addr=<IP_ADDRESS>:53265}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 21:36:31.087 ERROR connection{addr=<IP_ADDRESS>:53355}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 21:36:31.531 ERROR connection{addr=<IP_ADDRESS>:53558}: rathole::server: Failed to deserialize hello: invalid value: integer `197398`, expected variant index 0 <= i < 2
Feb 11 22:31:59.848 ERROR connection{addr=<IP_ADDRESS>:60030}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 22:32:08.322 ERROR connection{addr=<IP_ADDRESS>:36068}: rathole::server: Failed to read hello: early eof
Feb 11 22:32:15.952 ERROR connection{addr=<IP_ADDRESS>:46508}: rathole::server: Failed to read hello: early eof
Feb 11 22:32:19.203 ERROR connection{addr=<IP_ADDRESS>:55428}: rathole::server: Failed to deserialize hello: invalid value: integer `638`, expected variant index 0 <= i < 2
Feb 11 22:32:25.176 ERROR connection{addr=<IP_ADDRESS>:60604}: rathole::server: Failed to read hello: early eof
Feb 11 22:32:33.467 ERROR connection{addr=<IP_ADDRESS>:42594}: rathole::server: Failed to read hello: early eof
Feb 11 22:32:40.569 ERROR connection{addr=<IP_ADDRESS>:54110}: rathole::server: Failed to read hello: early eof
Feb 11 22:32:41.813 ERROR connection{addr=<IP_ADDRESS>:34752}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 22:32:50.190 ERROR connection{addr=<IP_ADDRESS>:38882}: rathole::server: Failed to read hello: early eof
Feb 11 22:32:52.098 ERROR connection{addr=<IP_ADDRESS>:45594}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 22:33:02.363 ERROR connection{addr=<IP_ADDRESS>:50432}: rathole::server: Failed to read hello: early eof
Feb 11 22:33:06.202 ERROR connection{addr=<IP_ADDRESS>:35838}: rathole::server: Failed to deserialize hello: invalid value: integer `1229407554`, expected variant index 0 <= i < 2
Feb 11 22:33:15.711 ERROR connection{addr=<IP_ADDRESS>:44772}: rathole::server: Failed to read hello: early eof
Feb 11 22:33:23.291 ERROR connection{addr=<IP_ADDRESS>:52748}: rathole::server: Failed to read hello: early eof
Feb 11 22:33:32.425 ERROR connection{addr=<IP_ADDRESS>:33012}: rathole::server: Failed to read hello: early eof
Feb 11 22:33:34.242 ERROR connection{addr=<IP_ADDRESS>:41710}: rathole::server: Failed to deserialize hello: invalid value: integer `66326`, expected variant index 0 <= i < 2
Feb 11 22:33:42.033 ERROR connection{addr=<IP_ADDRESS>:46484}: rathole::server: Failed to read hello: early eof
Feb 11 22:33:44.908 ERROR connection{addr=<IP_ADDRESS>:54124}: rathole::server: Failed to deserialize hello: invalid value: integer `671088768`, expected variant index 0 <= i < 2
Feb 11 22:33:52.979 ERROR connection{addr=<IP_ADDRESS>:57382}: rathole::server: Failed to read hello: early eof
Feb 11 22:33:59.953 ERROR connection{addr=<IP_ADDRESS>:37312}: rathole::server: Failed to read hello: early eof
Feb 11 22:34:07.715 ERROR connection{addr=<IP_ADDRESS>:47338}: rathole::server: Failed to read hello: early eof
Feb 11 22:34:08.732 ERROR connection{addr=<IP_ADDRESS>:55454}: rathole::server: Failed to deserialize hello: invalid value: integer `58`, expected variant index 0 <= i < 2
Feb 11 22:34:13.274 ERROR connection{addr=<IP_ADDRESS>:59080}: rathole::server: Failed to deserialize hello: invalid value: integer `1230262351`, expected variant index 0 <= i < 2
Feb 11 22:34:17.082 ERROR connection{addr=<IP_ADDRESS>:36534}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 11 22:34:25.484 ERROR connection{addr=<IP_ADDRESS>:40924}: rathole::server: Failed to read hello: early eof
Feb 11 22:34:31.826 ERROR connection{addr=<IP_ADDRESS>:49032}: rathole::server: Failed to read hello: early eof
Feb 11 22:34:39.139 ERROR connection{addr=<IP_ADDRESS>:58018}: rathole::server: Failed to read hello: early eof
Feb 12 01:06:58.354 ERROR connection{addr=<IP_ADDRESS>:63305}: rathole::server: Failed to deserialize hello: invalid value: integer `788529155`, expected variant index 0 <= i < 2
Feb 12 02:35:44.661 ERROR connection{addr=<IP_ADDRESS>:64736}: rathole::server: Failed to deserialize hello: invalid value: integer `788529155`, expected variant index 0 <= i < 2
Feb 12 03:08:53.713 ERROR connection{addr=<IP_ADDRESS>:42403}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 12 03:09:04.493 ERROR connection{addr=<IP_ADDRESS>:55301}: rathole::server: Failed to read hello: early eof
Feb 12 03:09:04.794 ERROR connection{addr=<IP_ADDRESS>:12143}: rathole::server: Failed to deserialize hello: invalid value: integer `671088768`, expected variant index 0 <= i < 2
Feb 12 03:09:15.160 ERROR connection{addr=<IP_ADDRESS>:31433}: rathole::server: Failed to read hello: early eof
Feb 12 04:07:05.687 ERROR connection{addr=<IP_ADDRESS>:34398}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 12 05:20:57.872 ERROR connection{addr=<IP_ADDRESS>:33924}: rathole::server: Failed to read hello: early eof
Feb 12 06:46:23.682 ERROR connection{addr=<IP_ADDRESS>:33674}: rathole::server: Failed to deserialize hello: invalid value: integer `197398`, expected variant index 0 <= i < 2
Feb 12 09:06:28.299 ERROR connection{addr=<IP_ADDRESS>:19879}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 12 09:06:39.169 ERROR connection{addr=<IP_ADDRESS>:45711}: rathole::server: Failed to read hello: early eof
Feb 12 09:06:40.430 ERROR connection{addr=<IP_ADDRESS>:55052}: rathole::server: Failed to deserialize hello: invalid value: integer `671088768`, expected variant index 0 <= i < 2
Feb 12 09:06:52.572 ERROR connection{addr=<IP_ADDRESS>:2330}: rathole::server: Failed to read hello: early eof
Feb 12 12:24:59.340 ERROR connection{addr=<IP_ADDRESS>:49752}: rathole::server: Failed to read hello: early eof
Feb 12 12:27:52.476 ERROR connection{addr=<IP_ADDRESS>:64831}: rathole::server: Failed to deserialize hello: invalid value: integer `788529155`, expected variant index 0 <= i < 2
Feb 12 14:13:59.870 ERROR connection{addr=<IP_ADDRESS>:52560}: rathole::server: Failed to read hello: early eof
Feb 12 14:46:57.080 ERROR connection{addr=<IP_ADDRESS>:64072}: rathole::server: Failed to deserialize hello: invalid value: integer `788529155`, expected variant index 0 <= i < 2
Feb 12 15:01:00.158 ERROR connection{addr=<IP_ADDRESS>:59847}: rathole::server: Failed to deserialize hello: invalid value: integer `542393671`, expected variant index 0 <= i < 2
Feb 12 15:01:11.738 ERROR connection{addr=<IP_ADDRESS>:54290}: rathole::server: Failed to read hello: early eof
Feb 12 15:01:11.925 ERROR connection{addr=<IP_ADDRESS>:35659}: rathole::server: Failed to deserialize hello: invalid value: integer `671088768`, expected variant index 0 <= i < 2
Feb 12 15:01:22.576 ERROR connection{addr=<IP_ADDRESS>:3118}: rathole::server: Failed to read hello: early eof
Feb 12 15:24:27.210 ERROR connection{addr=<IP_ADDRESS>:64391}: rathole::server: Failed to deserialize hello: invalid value: integer `788529155`, expected variant index 0 <= i < 2
Feb 12 15:43:15.551 ERROR connection{addr=<IP_ADDRESS>:64559}: rathole::server: Failed to deserialize hello: invalid value: integer `788529155`, expected variant index 0 <= i < 2
Feb 12 15:44:07.719 ERROR connection{addr=<IP_ADDRESS>:7161}: rathole::server: Failed to deserialize hello: invalid value: integer `872415506`, expected variant index 0 <= i < 2

Environment:

OS: CentOS Linux release 7.9.2009 (Core)
rathole --version output:

rathole
Build Timestamp:     2022-01-21T16:24:41.600163352+00:00
Build Version:       0.3.9
Commit SHA:          Some("3cab131fc4294e689cd42f0eb4070e71b0e13537")
Commit Date:         Some("2022-01-21T16:18:37+00:00")
Commit Branch:       Some("detached HEAD")
cargo Target Triple: x86_64-unknown-linux-musl
cargo Profile:       release
cargo Features:      base64,client,default,hot_reload,noise,notify,server,snowstorm,tls,tokio_native_tls

CPU architecture: Linux iZg7370jfvwvncZ 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Are these IP addresses known to you? I picked some of them and looked them up. They came from all over the world and looked like some random scanners.
It's common to encounter scanners on the Internet. They're harmless because rathole has an authentication method and they just blindly send traffic. To mitigate the problem, you can change the listen port to a higher and random one, instead of 7000.
Also I will find time to add an option to suppress these unuseful errors.

我不清楚这些ip是哪里的,我会更换个端口看下是否还会出现这些问题

请问下作者你的openwrt是安装在什么设备上的,配置是什么样的,我用的是ASUS TR-AX56U V2路由器,RAM和ROM都是256M的,在这个上面rathole运行大概3天就会产生大概120多k日志,路由器数据无法写入iptables,导致路由器无法联网

日志放不下可以调整日志等级 或者直接用>/dev/null 忽略所有日志，等等
连接稳定情况下是不会产生太多日志的。更换了高端口之后还是出现像上面发的一样的被扫描的日志吗？
---Original---
From: @.>
Date: Thu, Feb 17, 2022 15:23 PM
To: @.>;
Cc: "Yujia<EMAIL_ADDRESS>Subject: Re: [rapiz1/rathole] rathole::server: Failed to read hello (Issue #131)
请问下作者你的openwrt是安装在什么设备上的,配置是什么样的,我用的是ASUS TR-AX56U V2路由器,RAM和ROM都是256M的,在这个上面rathole运行大概3天就会产生大概120多k日志,路由器数据无法写入iptables,导致路由器无法联网
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

一般对日志没有需求的时候 也可以不用tee把日志保存成文件
---Original---
From: @.>
Date: Thu, Feb 17, 2022 15:23 PM
To: @.>;
Cc: "Yujia<EMAIL_ADDRESS>Subject: Re: [rapiz1/rathole] rathole::server: Failed to read hello (Issue #131)
请问下作者你的openwrt是安装在什么设备上的,配置是什么样的,我用的是ASUS TR-AX56U V2路由器,RAM和ROM都是256M的,在这个上面rathole运行大概3天就会产生大概120多k日志,路由器数据无法写入iptables,导致路由器无法联网
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

还没有换高端口做测试,后面我会测试下
我看华硕路由器的JFFS 分区不宜频繁的写入,决定使用香橙派的zero2开发板作为反向代理服务器,这样可以使代理更稳定而不影响其他的设备联网,还可以启动两个及以上的进程来做备份代理,在华硕路由器上现在无法启动两个进程
请问下作者你的openwrt是安装在什么设备上的,配置是什么样的

我试了高端口之后暂时没有出现像上面发的一样的被扫描的日志

我用的是 	NETGEAR R6100 ，不过负载比较小。


Please update tools working with MTM LV60 play, thanks so much

Please update tools working with MTM LV60 play, thanks so much

Currently it just skips lvl 60 mtms, Lost World plays automatically anyway so no need to change anything.

i mean, tools not working with mtm lv60 use Ticket Space for metamon island.

You mean bring metamon back to Island? I havent tried it yet so not sure how it works

Please kind Sir. Update the program. We are unable to use the lvl 60 metamons after bringing them back to metamon island. Your program is extremely important to the community, dont forget us please. The auto battle function is way worse for us (since its more expensive and less effective). Using your program will help us in this bearmasket.

Please kind Sir. Update the program. We are unable to use the lvl 60 metamons after bringing them back to metamon island. Your program is extremely important to the community, dont forget us please. The auto battle function is way worse for us (since its more expensive and less effective). Using your program will help us in this bearmasket.

need  to know about function to auto-reset metamon exp from 395 to 0 , for  lev60 metamon, so we can add in the bot

Request URL: https://metamon-api.radiocaca.com/usm-api/resetMonster
{
"code": "SUCCESS",
"data": null,
"message": "",
"result": 1
}

{
"code": "ITEM_NUM_ERROR",
"data": null,
"message": "Insufficient quantity.",
"result": -1
}

TY very much

Request URL: https://metamon-api.radiocaca.com/usm-api/resetMonster
{ "code": "SUCCESS", "data": null, "message": "", "result": 1 }

How to update it? Please.

https://github.com/MetaMon-game-player/MetamonPlayer/pull/30
this version the bot  allow you to go and reset the 395 exp, while he skip errors and go ahead

#30
this version the bot allow you to go and reset the 395 exp, while he skip errors and go ahead

thank you
it work perfectly

but it doesn't reset metamon xp when it reach to 395xp and user should manually rest it

i'm working on it....  don't know the docs about metamon island API, i can only try

{ "code": "ITEM_NUM_ERROR", "data": null, "message": "Insufficient quantity.", "result": -1 }

in code  response i obtain always " none" ... maybe i miss something

fixed all
check  code in pull request
https://github.com/MetaMon-game-player/MetamonPlayer/pull/32

You mean bring metamon back to Island? I havent tried it yet so not sure how it works
i fixed all the new issues, please, i need more knowledge about API docs, do you have ?

Request URL: https://metamon-api.radiocaca.com/usm-api/resetMonster
Hi , could you find information about HEALTH VALUE and function to restore it ?

{ "code": "HEALTHY_PROP_ERROR", "data": null, "message": "Restoring health value require Anti-Fatigue Potion.", "result": -1 }
respond
{ "code":"HEALTHY_PROP_ERROR", "data":null, "message":"Restoring health value require Anti-Fatigue Potion.", "result":-1 }

which function ?

{ "code": "HEALTHY_PROP_ERROR", "data": null, "message": "Restoring health value require Anti-Fatigue Potion.", "result": -1 }
respond
{ "code":"HEALTHY_PROP_ERROR", "data":null, "message":"Restoring health value require Anti-Fatigue Potion.", "result":-1 }

https://github.com/MetaMon-game-player/MetamonPlayer/pull/32/commits/8acb422269d57af6245a65481379ecc189880741


Errors when debugging

As a noob,I find it hard to debug your programs.There are too many problems...
Dear author,would you please provide even one complete code that could run directly?
Besides,I would really appreciate it if you explain how to make personal files similar with 'zhihu-word2vec-title-desc.bin-100'.

zhihu-word2vec-title-desc.bin-100'.  I  have the same qusetion? how can i get  the file "zhihu-word2vec-title-desc.bin-100'"

yeah. for 'zhihu-word2vec-title-desc.bin-100', you can use data to pre-trained word embedding. for example, use word2vec or fasttext to pre-trained it. then you will get it.

UPDATE: if you want to try a model now, you can go to folder 'a02_TextCNN', run 'python -u p7_TextCNN_train.py', it will use sample data to train a model, and print loss and F1 score periodically.

thank you so much!
在 2018-04-16 22:19:11，brightmart<EMAIL_ADDRESS>写道：
UPDATE: if you want to try a model now, you can go to folder 'a02_TextCNN', run 'python -u p7_TextCNN_train.py', it will use sample data to train a model, and print loss and F1 score periodically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[tool_crash] HttpException

Command
flutter drive \ --driver=test_driver/integration_test_driver.dart \ --target=integration_test/alert_test.dart --dart-define=EMAIL=secret \ --dart-define=PASS=secret/

Steps to Reproduce

Connect Samsung Duos Phone
Have these libraries in Application
Run Integration test

Logs
HttpException
"HttpException: Connection closed before full header was received, uri"
https://github.com/flutter/flutter/issues?q=is%3Aissue+HttpException%3A+Connection+closed+before+full+header+was+received%2C+uri+%3D+http%3A%2F%2F<IP_ADDRESS>%3A64759%2Fbg6LZ71nTfg%3D%2Fws
Flutter Doctor:
[✓] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19045.2251], locale en-GB)
• Flutter version 2.10.5 at C:\Users\user\flutter2
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (8 months ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
• Android SDK at C:\Users\user\AppData\Local\Android\sdk
• Platform android-33, build-tools 33.0.0
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[!] Visual Studio - develop for Windows (Visual Studio Community 2022 17.3.3)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.3.32825.248
✗ The current Visual Studio installation is incomplete. Please reinstall Visual Studio.
[✓] Android Studio (version 2021.3)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
[✓] VS Code (version 1.74.0)
• VS Code at C:\Users\user\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.54.0
[✓] Connected device (4 available)
• SM A700FD (mobile) • 3ca4f48a • android-arm    • Android 6.0.1 (API 23)
• Windows (desktop)  • windows  • windows-x64    • Microsoft Windows [Version 10.0.19045.2251]
• Chrome (web)       • chrome   • web-javascript • Google Chrome 108.0.5359.124
• Edge (web)         • edge     • web-javascript • Microsoft Edge 108.0.1462.46
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 1 category.

 all end with
"Oops; flutter has exited unexpectedly: "HttpException: Connection reset by peer ..."

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.1, on macOS 13.1 22C65 darwin-x64, locale
en-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.74.3)
[!] Proxy Configuration
! NO_PROXY is not set
[✓] Connected device (4 available)
[✓] HTTP Host Availability