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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): update redis client to v4 in legacy mode #21548

Conversation

blaggacao
Copy link
Contributor

@blaggacao blaggacao commented Jul 1, 2023

@ankush Hopefully this is a more palatable version of #20925 馃槃 and the further refactoring to actually use the v4 api of that PR can then be added eventually as a second step (if needed).

The version bump also requires frappe/bench#1466 due to localhost being interpreted as ipv6 ::1.

I added a temp fix for CI that must be reverted once that bench PR is merged and has duly propagated.

@blaggacao blaggacao requested a review from a team as a code owner July 1, 2023 16:00
@blaggacao blaggacao requested review from shariquerik and removed request for a team July 1, 2023 16:00
@blaggacao blaggacao changed the title chore: update redis client to v4 in legacy mode build(deps): update redis client to v4 in legacy mode Jul 1, 2023
@blaggacao blaggacao force-pushed the update-redis-client-to-4-legacy-mode branch 2 times, most recently from 0e00144 to cfa770d Compare July 1, 2023 16:15
@codecov
Copy link

codecov bot commented Jul 1, 2023

Codecov Report

Merging #21548 (fa6c389) into develop (00e5dab) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop   #21548   +/-   ##
========================================
  Coverage    63.86%   63.86%           
========================================
  Files          765      765           
  Lines        69353    69353           
  Branches      6271     6271           
========================================
  Hits         44291    44291           
  Misses       21487    21487           
  Partials      3575     3575           
Flag Coverage 螖
server 69.04% <酶> (-0.01%) 猬囷笍

Flags with carried forward coverage won't be shown. Click here to find out more.

@blaggacao

This comment was marked as outdated.

@ankush
Copy link
Member

ankush commented Jul 2, 2023

@blaggacao the fix in bench wont fix existing installs. What breaks with localhost?

It seems to work fine for me. Can you share some error/traceback?

@blaggacao
Copy link
Contributor Author

blaggacao commented Jul 2, 2023

@ankush I think this might be a better fix across "affected" * node versions, then.

The issue is ERRCONNECT on ::1.

* IMO, it's not unreasonable to assume localhost as ::1, it's part of the standard, after all.

@ankush
Copy link
Member

ankush commented Jul 2, 2023

@surajshetty3416 we might need the fix to make node work on systems which are preferring ipv6 (idk if there's any real cost to forcing ipv4 in code since we are using it only on localhost 馃し)

@blaggacao
Copy link
Contributor Author

blaggacao commented Jul 2, 2023

Going forward, I'd recommend to not use dns (i.e. localhost), but the raw ip (i.e. 127.0.0.1), since on some container environments (prominently minimal ones) localhost resolution does not work, even if runc / containerd try hard to inject correct resolution.

It's also a good way to avoid 'hard' problems. 馃槃

@blaggacao blaggacao force-pushed the update-redis-client-to-4-legacy-mode branch from a33c45d to fa6c389 Compare July 3, 2023 19:11
@stale
Copy link

stale bot commented Jul 10, 2023

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing.

@stale stale bot added the inactive label Jul 10, 2023
@stale stale bot closed this Jul 13, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants