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

Consul name resolution in-memory cache #963

Closed
wants to merge 73 commits into from

Conversation

a-elsheikh
Copy link
Contributor

Description

Added service cache to consul nr component

Issue reference

#934

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

nameresolution/consul/consul.go Outdated Show resolved Hide resolved
@a-elsheikh a-elsheikh requested a review from yaron2 June 22, 2021 10:19
@yaron2
Copy link
Member

yaron2 commented Jul 12, 2021

@a-elsheikh have you tested this in your environment?

@a-elsheikh a-elsheikh requested review from a team as code owners July 13, 2021 09:44
@a-elsheikh
Copy link
Contributor Author

@a-elsheikh have you tested this in your environment?

In self-hosted mode, yes - it would be best if someone could evaluate the behaviour on k8s

@pkedy pkedy self-assigned this Jul 26, 2021
@pkedy
Copy link
Member

pkedy commented Jul 26, 2021

@a-elsheikh After the 1.3.0 release, I will spend some cycles to test this on K8s.

nameresolution/consul/consul.go Show resolved Hide resolved
nameresolution/consul/watcher.go Show resolved Hide resolved
@yaron2
Copy link
Member

yaron2 commented Aug 30, 2021

@artursouza can you continue reviewing this please?

@a-elsheikh
Copy link
Contributor Author

@artursouza any updates on this?

@pkedy pkedy removed their assignment Aug 8, 2022
@berndverst berndverst added the autoupdate automatically keeps PR up to date against master label Aug 15, 2022
@berndverst
Copy link
Member

@a-elsheikh could you please merge master into the branch again to address the potential conflict? I tried pushing a commit but it does not appear you are giving maintainers edit access to your PR / branch.

@codecov
Copy link

codecov bot commented Aug 16, 2022

Codecov Report

Patch coverage: 90.47% and project coverage change: +2.09% 🎉

Comparison is base (33a5fd2) 34.97% compared to head (c7d9e20) 37.07%.

❗ Current head c7d9e20 differs from pull request most recent head 803d29d. Consider uploading reports for the commit 803d29d to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #963      +/-   ##
==========================================
+ Coverage   34.97%   37.07%   +2.09%     
==========================================
  Files         241      212      -29     
  Lines       29887    26904    -2983     
==========================================
- Hits        10454     9975     -479     
+ Misses      18552    16152    -2400     
+ Partials      881      777     -104     
Files Changed Coverage Δ
nameresolution/consul/consul.go 79.01% <87.80%> (+5.33%) ⬆️
nameresolution/consul/watcher.go 92.07% <92.07%> (ø)
nameresolution/consul/configuration.go 96.13% <100.00%> (+1.44%) ⬆️

... and 228 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@berndverst berndverst removed the autoupdate automatically keeps PR up to date against master label Aug 29, 2022
@ItalyPaleAle
Copy link
Contributor

It looks like this PR is outdated and probably irrelevant at this point. Ok to close this?
CC: @berndverst

@badgeratu
Copy link

It's definitely not outdated, we've been waiting patiently for a re-review as we believe we've addressed all comments. If you could push that it would be greatly appreciated, this is still a vital feature required by us.

@ItalyPaleAle
Copy link
Contributor

Ok, thanks for confirming. If you can fix the merge conflicts, I'll review it for Dapr 1.11.

@alberthuang24
Copy link
Contributor

I also really need this feature

@berndverst
Copy link
Member

berndverst commented May 1, 2023

@badgeratu because we do not have write access to your fork we cannot shepherd this PR -- so this PR will constantly encounter merge conflicts that only you can resolve.
It's very difficult to merge PRs where we as maintainers do not have automatic write access to the remote fork.

Can you invite contrib maintainers directly to have write access to your fork so we can unblock this pr (it seems you have disabled the feature to give repo maintainers this ability automatically at an organizational level)? The maintainers are: @ItalyPaleAle @yaron2 @berndverst @artursouza

We are days (or maybe just one day) away from code freeze for 1.11. If we find that tests pass after addressing merge conflicts and updating the branch then this is likely good to go - but we'll re-review then.

@a-elsheikh
Copy link
Contributor Author

hey @berndverst thanks for reaching out - as this fork exists under the corporate area we've limited flexibility in amending the permissions. In any case, I've got eyes on this now so am happy to iterate with the maintainers to see it done now that there is engagement.

@berndverst
Copy link
Member

@a-elsheikh @badgeratu can you please ping me in Discord (@bernd) once you have resolved merge conflicts and fixed DCO here?

I will try to get this merged - we are now at code freeze for 1.12 - but if you can get this resolved Monday we can still try to get it in!

Signed-off-by: Abdulaziz Elsheikh <abdulaziz.elsheikh@gmail.com>
@ItalyPaleAle
Copy link
Contributor

Closing as it's been re-created as #3121

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pinned Issue does not get stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants