On Wed, Jan 10, 2024 at 05:49:58PM +, Simon Horman wrote:
> On Wed, Jan 10, 2024 at 06:38:48PM +0100, Ilya Maximets wrote:
> > On 1/10/24 18:18, Simon Horman wrote:
> > > On Wed, Jan 10, 2024 at 12:28:22PM +0100, Dumitru Ceara wrote:
...
> > >> TBH I'd just apply both this patch and the test
On Wed, Jan 10, 2024 at 06:38:48PM +0100, Ilya Maximets wrote:
> On 1/10/24 18:18, Simon Horman wrote:
> > On Wed, Jan 10, 2024 at 12:28:22PM +0100, Dumitru Ceara wrote:
> >> On 1/8/24 16:31, Ilya Maximets wrote:
> >>> On 1/8/24 16:05, Ilya Maximets wrote:
> On 1/5/24 18:35, Terry Wilson
On 1/10/24 18:18, Simon Horman wrote:
> On Wed, Jan 10, 2024 at 12:28:22PM +0100, Dumitru Ceara wrote:
>> On 1/8/24 16:31, Ilya Maximets wrote:
>>> On 1/8/24 16:05, Ilya Maximets wrote:
On 1/5/24 18:35, Terry Wilson wrote:
> On Fri, Jan 5, 2024 at 9:56 AM Simon Horman wrote:
>>
On Wed, Jan 10, 2024 at 12:28:22PM +0100, Dumitru Ceara wrote:
> On 1/8/24 16:31, Ilya Maximets wrote:
> > On 1/8/24 16:05, Ilya Maximets wrote:
> >> On 1/5/24 18:35, Terry Wilson wrote:
> >>> On Fri, Jan 5, 2024 at 9:56 AM Simon Horman wrote:
>
> On Mon, Dec 18, 2023 at 05:31:24PM
On 1/8/24 16:31, Ilya Maximets wrote:
> On 1/8/24 16:05, Ilya Maximets wrote:
>> On 1/5/24 18:35, Terry Wilson wrote:
>>> On Fri, Jan 5, 2024 at 9:56 AM Simon Horman wrote:
On Mon, Dec 18, 2023 at 05:31:24PM -0600, Terry Wilson wrote:
> Currently python-ovs claims to be "db change
On 12/19/23 00:31, Terry Wilson wrote:
> Currently python-ovs claims to be "db change aware" but does not
> parse the "monitor_canceled" notification. Transactions can continue
> being made, but the monitor updates will not be sent. This handles
> monitor_cancel similarly to how ovsdb-cs currently
On 1/8/24 16:05, Ilya Maximets wrote:
> On 1/5/24 18:35, Terry Wilson wrote:
>> On Fri, Jan 5, 2024 at 9:56 AM Simon Horman wrote:
>>>
>>> On Mon, Dec 18, 2023 at 05:31:24PM -0600, Terry Wilson wrote:
Currently python-ovs claims to be "db change aware" but does not
parse the
On 1/5/24 18:35, Terry Wilson wrote:
> On Fri, Jan 5, 2024 at 9:56 AM Simon Horman wrote:
>>
>> On Mon, Dec 18, 2023 at 05:31:24PM -0600, Terry Wilson wrote:
>>> Currently python-ovs claims to be "db change aware" but does not
>>> parse the "monitor_canceled" notification. Transactions can
On Fri, Jan 5, 2024 at 9:56 AM Simon Horman wrote:
>
> On Mon, Dec 18, 2023 at 05:31:24PM -0600, Terry Wilson wrote:
> > Currently python-ovs claims to be "db change aware" but does not
> > parse the "monitor_canceled" notification. Transactions can continue
> > being made, but the monitor
On Mon, Dec 18, 2023 at 05:31:24PM -0600, Terry Wilson wrote:
> Currently python-ovs claims to be "db change aware" but does not
> parse the "monitor_canceled" notification. Transactions can continue
> being made, but the monitor updates will not be sent. This handles
> monitor_cancel similarly to
Bleep bloop. Greetings Terry Wilson, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: The subject summary should end with a dot.
Subject: python: idl: Handle
Currently python-ovs claims to be "db change aware" but does not
parse the "monitor_canceled" notification. Transactions can continue
being made, but the monitor updates will not be sent. This handles
monitor_cancel similarly to how ovsdb-cs currently does.
Signed-off-by: Terry Wilson
---
12 matches
Mail list logo
