Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[202205] Advance sonic-dbsyncd submodule #14225

Merged
merged 2 commits into from
Mar 21, 2023

Conversation

vivekrnv
Copy link
Contributor

@vivekrnv vivekrnv commented Mar 13, 2023

4dcfb61 Handled the error case of negative age (https://github.com/sonic-net/sonic-buildimage/pull/57)

Why I did it

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

Description for the changelog

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@vivekrnv vivekrnv requested a review from lguohan as a code owner March 13, 2023 18:23
@vivekrnv
Copy link
Contributor Author

/azpw run Azure.sonic-buildimage

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vivekrnv
Copy link
Contributor Author

/azpw run Azure.sonic-buildimage

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vivekrnv
Copy link
Contributor Author

/azpw run Azure.sonic-buildimage

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Collaborator

@yxieca should we create a branch for this repo in 202205 instead of taking master into it?
from my POV the major fix is in one commit: Handled the error case of negative age.

@yxieca
Copy link
Contributor

yxieca commented Mar 17, 2023

@yxieca should we create a branch for this repo in 202205 instead of taking master into it? from my POV the major fix is in one commit: Handled the error case of negative age.

Sounds like we are deviating from the master branch? If so, we should create 202205 branch. Please confirm.

@vivekrnv
Copy link
Contributor Author

@yxieca should we create a branch for this repo in 202205 instead of taking master into it? from my POV the major fix is in one commit: Handled the error case of negative age.

Sounds like we are deviating from the master branch? If so, we should create 202205 branch. Please confirm.

Yeah i think so.

@yxieca
Copy link
Contributor

yxieca commented Mar 17, 2023

@yxieca should we create a branch for this repo in 202205 instead of taking master into it? from my POV the major fix is in one commit: Handled the error case of negative age.

Sounds like we are deviating from the master branch? If so, we should create 202205 branch. Please confirm.

Yeah i think so.

#14307

4dcfb61 Handled the error case of negative age (#57)

Signed-off-by: Vivek Reddy <vkarri@nvidia.com>
@yxieca yxieca merged commit 3e732b0 into sonic-net:202205 Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants