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

[bugfix] fix agent sidecar behavior when index files are updated #598

Merged
merged 1 commit into from
Jul 28, 2020

Conversation

rinx
Copy link
Contributor

@rinx rinx commented Jul 28, 2020

Signed-off-by: Rintaro Okamura rintaro.okamura@gmail.com

Description:

Current version v0.0.48, when agent-sidecar detects the changes in index files, it terminates itself immediately because the implementation is wrong.
In this PR, i've fixed it.

Related Issue:

nothing.

How Has This Been Tested?:

nothing.

Environment:

  • Go Version: 1.14.4
  • Docker Version: 19.03.8
  • Kubernetes Version: 1.18.2
  • NGT Version: 1.12.0

Types of changes:

  • Bug fix [type/bug]
  • New feature [type/feature]
  • Add tests [type/test]
  • Security related changes [type/security]
  • Add documents [type/documentation]
  • Refactoring [type/refactoring]
  • Update dependencies [type/dependency]
  • Update benchmarks and performances [type/bench]
  • Update CI [type/ci]

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you successfully ran tests with your changes locally?

Checklist:

  • I have read the CONTRIBUTING document.
  • I have checked open Pull Requests for the similar feature or fixes?
  • I have added tests and benchmarks to cover my changes.
  • I have ensured all new and existing tests passed.
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly.

Signed-off-by: Rintaro Okamura <rintaro.okamura@gmail.com>
@pull-assistant
Copy link

Score: 1.00

Best reviewed: commit by commit


Optimal code review plan

     🐛 fix agent sidecar behavior

Powered by Pull Assistant. Last update d2da9ad ... d2da9ad. Read the comment docs.

@vdaas-ci
Copy link
Collaborator

[CHATOPS:HELP] ChatOps commands.

  • 🙆‍♀️ /approve - approve
  • 💌 /changelog - add changelog comment
  • 🍱 /format - format codes and add licenses
  • /gen-test - generate test codes
  • 🏷️ /label - add labels
  • /rebase - rebase master

@github-actions github-actions bot added size/S type/bug Something isn't working labels Jul 28, 2020
@rinx rinx requested a review from kpango July 28, 2020 12:13
@codecov
Copy link

codecov bot commented Jul 28, 2020

Codecov Report

Merging #598 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #598      +/-   ##
==========================================
- Coverage   11.79%   11.79%   -0.01%     
==========================================
  Files         407      407              
  Lines       21229    21231       +2     
==========================================
  Hits         2505     2505              
- Misses      18447    18449       +2     
  Partials      277      277              
Impacted Files Coverage Δ
pkg/agent/sidecar/service/observer/observer.go 0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 98074e3...d2da9ad. Read the comment docs.

Copy link
Collaborator

@kpango kpango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kpango kpango merged commit 1658914 into master Jul 28, 2020
@kpango kpango deleted the bugfix/agent-sidecar/fix-sidecar-behavior branch July 28, 2020 12:59
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.

3 participants