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

change time point calculate in ttl #4683

Merged
merged 10 commits into from
Oct 9, 2022

Conversation

pengweisong
Copy link
Contributor

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

When insert ttl field with now() which is calculated by time(NULL). When check if the ttl field valid, we use time::WallClock before, which will drift from time(NULL) with time going.

How do you solve it?

both use time(NULL)

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

  • Unit test(positive and negative cases)
  • Function test
  • Performance test
  • N/A

Affects:

  • Documentation affected (Please add the label if documentation needs to be modified.)
  • Incompatibility (If it breaks the compatibility, please describe it and add the label.)
  • If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
  • Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

@pengweisong pengweisong added the ready-for-testing PR: ready for the CI test label Sep 27, 2022
critical27
critical27 previously approved these changes Sep 28, 2022
panda-sheep
panda-sheep previously approved these changes Sep 28, 2022
Copy link
Contributor

@panda-sheep panda-sheep left a comment

Choose a reason for hiding this comment

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

Good,thx

critical27
critical27 previously approved these changes Sep 28, 2022
@codecov-commenter
Copy link

Codecov Report

Base: 84.69% // Head: 84.73% // Increases project coverage by +0.04% 🎉

Coverage data is based on head (8fa710d) compared to base (450e58e).
Patch coverage: 92.61% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4683      +/-   ##
==========================================
+ Coverage   84.69%   84.73%   +0.04%     
==========================================
  Files        1358     1358              
  Lines      135674   135801     +127     
==========================================
+ Hits       114911   115077     +166     
+ Misses      20763    20724      -39     
Impacted Files Coverage Δ
src/clients/storage/StorageClient.h 100.00% <ø> (ø)
src/common/hdfs/HdfsCommandHelper.cpp 0.00% <0.00%> (ø)
src/graph/executor/admin/ShowHostsExecutor.cpp 92.55% <0.00%> (-1.00%) ⬇️
src/graph/executor/algo/BatchShortestPath.cpp 98.29% <ø> (ø)
src/graph/executor/algo/SingleShortestPath.cpp 97.56% <ø> (ø)
src/meta/processors/job/BalanceJobExecutor.h 75.00% <ø> (ø)
src/meta/processors/job/BalancePlan.h 100.00% <ø> (ø)
src/meta/processors/job/JobExecutor.h 100.00% <ø> (+50.00%) ⬆️
src/meta/processors/job/JobManager.h 100.00% <ø> (ø)
src/storage/CommonUtils.h 98.27% <ø> (ø)
... and 86 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@critical27
Copy link
Contributor

@shanlai Tell me if you have verified it~

critical27
critical27 previously approved these changes Oct 9, 2022
panda-sheep
panda-sheep previously approved these changes Oct 9, 2022
Copy link
Contributor

@panda-sheep panda-sheep left a comment

Choose a reason for hiding this comment

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

Good job

@critical27 critical27 merged commit 42b0c9e into vesoft-inc:master Oct 9, 2022
@Sophie-Xie Sophie-Xie added the cherry-pick-v3.3 PR: need cherry-pick to this version label Oct 9, 2022
Sophie-Xie added a commit that referenced this pull request Oct 9, 2022
* change time point calculate in ttl

* fix ttl test

* enlarge the ttl sleep interval in the test

* fix ttl in index

* Revert "enlarge the ttl sleep interval in the test"

This reverts commit e37bf51.

* change wall time in mock data

Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com>
critical27 pushed a commit that referenced this pull request Oct 12, 2022
* optimize for the last step of go n steps plan (#4690)

* optimize for the last step of go n steps plan

* improve some comments

* change time point calculate in ttl (#4683)

* change time point calculate in ttl

* fix ttl test

* enlarge the ttl sleep interval in the test

* fix ttl in index

* Revert "enlarge the ttl sleep interval in the test"

This reverts commit e37bf51.

* change wall time in mock data

Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com>

* fix graph crash (#4698)

* fix_ambiguous_case (#4701)

* fix_ambiguous_case

* change in any order to in order'

* fix map hash method (#4707)

Co-authored-by: jie.wang <38901892+jievince@users.noreply.github.com>
Co-authored-by: pengwei.song <90180021+pengweisong@users.noreply.github.com>
Co-authored-by: jimingquan <mingquan.ji@vesoft.com>
@shanlai
Copy link

shanlai commented Oct 17, 2022

@critical27 Verification passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-v3.3 PR: need cherry-pick to this version ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants