-
-
Notifications
You must be signed in to change notification settings - Fork 995
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: predis/predis
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.4.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: predis/predis
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.4.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 69 files changed
- 6 contributors
Commits on Feb 26, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 274cb86 - Browse repository at this point
Copy the full SHA 274cb86View commit details
Commits on Mar 5, 2026
-
Fix sentinel discovery methods not catching StreamInitException (#1650)
* Fix sentinel discovery methods not catching StreamInitException The getMaster(), getSlaves(), and updateSentinels() methods only catch ConnectionException when connecting to Sentinel nodes. StreamInitException (thrown by stream_socket_client() failures) extends PredisException directly, not ConnectionException, so it propagates uncaught — preventing fallback to the next Sentinel node. This causes complete application failure when any single Sentinel is unreachable, even if other Sentinels are healthy. Add StreamInitException to the catch clause using a union type in all three methods. This is more precise than catching PredisException, which would also swallow ServerException (e.g. "ERR No such master with that name") and mask configuration errors. See also #1577 which applied a similar fix to retryCommandOnFailure(). * Fix coding standards and add changelog entry - Remove spaces around | in union catch (php-cs-fixer) - Add CHANGELOG.md entry for #1650 * Codestlye fixes --------- Co-authored-by: Wolfgang Kerschbaumer <wolfgang.kerschbaumer@bergfex.at> Co-authored-by: vladvildanov <vladyslav.vildanov@redis.com>
Configuration menu - View commit details
-
Copy full SHA for d0f6671 - Browse repository at this point
Copy the full SHA d0f6671View commit details -
Add upstream_driver option for CLIENT SETINFO upstream reporting (#1645)
* Add driver_info option for CLIENT SETINFO upstream reporting * Use null default for upstreamDriver and ternary operator * Remove redundant null initialization * fix: remove trailing newline from VERSION file * fix: update copyright year to 2026 in DriverInfo files * refactor: rename driver_info to upstream_driver * fix: code style issues * docs: update CHANGELOG to reflect upstream_driver rename
Configuration menu - View commit details
-
Copy full SHA for 7388d91 - Browse repository at this point
Copy the full SHA 7388d91View commit details
Commits on Mar 9, 2026
-
Configuration menu - View commit details
-
Copy full SHA for f57dfcb - Browse repository at this point
Copy the full SHA f57dfcbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 87390e7 - Browse repository at this point
Copy the full SHA 87390e7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2033429 - Browse repository at this point
Copy the full SHA 2033429View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.4.1...v3.4.2