chore(deps): bump github.com/aerospike/aerospike-client-go/v5 from 5.7.0 to 5.10.0

[dependabot]

Bumps github.com/aerospike/aerospike-client-go/v5 from 5.7.0 to 5.10.0.

Release notes

Sourced from github.com/aerospike/aerospike-client-go/v5's releases.

Major fix release

This is a Major fix release. We recommend you update to this version ASAP. A bug might occur when a client performing a scan hits a "Partition Unavailable" during an unstable cluster (in both high availability (AP) and strong consistency (CP) modes). Previous versions of the client aborted the scan and put the connection back into the pool, which might cause unprocessed results to be sent to a different transaction (of the same client), possibly resulting in incorrect application behavior. This has been fixed by Go Client v5.10.0 and v6.4.0.

• Fixes

  • [CLIENT-1822] Scan/Query/Other streaming commands, including some Batch could put a faulty connection back to the pool after a cluster event where in certain conditions its buffer contents would end up in another scan and mix the results.
  • Update go.mod, redact buggy versions and update required Go version to v1.16
  • Fixes a few test errors for server v6.1+.
  • Adds a nil check for error in the execution retry.

• Improvements

  • Update the examples for the new scan/queries.
  • Avoid indirection for []byte conversion during reflection. Resolves #382.

Re-release to resolve github tag mixup

This is only a retag of v5.9.0, since that release bungled up tagging properly and causes issues with go.mod according to #386

Major fix release

This is a major fix release. We recommend upgrading to this release if you are using Scan/Queries.

• Fixes
  • [CLIENT-1783] Fix client crashes when tracker is nil during Scan/Queries. PR #379, thanks to adumovic
  • Fix client.Get when policy.FilterExpression and bin names are both provided.

Major fix release

This is a major fix release. We recommend upgrading to this release if you are using authentication.

• Improvements

  • Adds notices regarding Auth issue to CHANGELOG and clarifies how to change code for an old breaking change in v3.
  • Forward compatibility with Server v6 regarding queries and scans not sending a fresh message header per partition.

• Fixes

  • [CLIENT-1695] Fixes a potential nil deference in sessionInfo.isValid() method.
  • Fixes an issue where with default policies and after certain errors the replica node was not selected on retry.

Changelog

Sourced from github.com/aerospike/aerospike-client-go/v5's changelog.

September 14 2022: v5.10.0

This is a Major fix release. We recommend you update to this version ASAP.

• Fixes

  • [CLIENT-1822] Scan/Query/Other streaming commands, including some Batch could put a faulty connection back to the pool after a cluster event where in certain conditions its buffer contents would end up in another scan and mix the results.
  • Update go.mod, redact buggy versions and update required Go version to v1.16
  • Fixes a few test errors for serrver v6.1+.
  • Adds a nil check for error in the execution retry.

• Improvements

  • Update the examples for the new retriable scan/queries
  • Avoid indirection for []byte conversion during reflection. Resolves #382.

June 30 2022: v5.9.0

[IMPORTANT NOTE] A bug might occur when a client performing a scan hits a “Partition Unavailable” during an unstable cluster (in both high availability (AP) and strong consistency (CP) modes). Previous versions of the client aborted the scan and put the connection back into the pool, which might cause unprocessed results to be sent to a different transaction (of the same client), possibly resulting in incorrect application behavior. This has been fixed by Go Client v5.10.0 and v6.4.0.

This is a major fix release. We recommend upgrading to this release if you are using .

• Fixes
  • [CLIENT-1783] Fix client crashes when tracker is nil during Scan/Queries. PR #379, thanks to adumovic
  • Fix client.Get when policy.FilterExpression and bin names are both provided.

April 7 2022: v5.8.0

[IMPORTANT NOTE] A bug might occur when a client performing a scan hits a “Partition Unavailable” during an unstable cluster (in both high availability (AP) and strong consistency (CP) modes). Previous versions of the client aborted the scan and put the connection back into the pool, which might cause unprocessed results to be sent to a different transaction (of the same client), possibly resulting in incorrect application behavior. This has been fixed by Go Client v5.10.0 and v6.4.0.

This is a major fix release. We recommend upgrading to this release if you are using authentication.

• Improvements

  • Adds notices regarding Auth issue to CHANGELOG and clarifies how to change code for an old breaking change in v3.
  • Forward compatibility with Server v6 regarding queries and scans not sending a fresh message header per partition.

• Fixes

  • [CLIENT-1695] Fixes a potential nil deference in sessionInfo.isValid() method.
  • Fixes an issue where with default policies and after certain errors the replica node was not selected on retry.

Commits

• d4cd311 Update CHANGELOG
• 27c6e37 [CLIENT-1822] Continue processing records when PARTITION_UNAVAILABLE is recei...
• d804989 Update CHANGELOG
• 915b76a Update the examples for the new retriable scan/queries
• 1ee56d3 Update min Go version to v1.16 and retract the faulty modules in go.mod, refl...
• 0852923 [CLIENT-1822] Scan/Query/Other streaming commands could put a faulty connecti...
• a76504c USe a direct []byte conversion during reflection. Resolves #382
• 978d078 Fix a few test errors for serrver v6+
• de4fe2e Add a nil check for error to be on the safe side
• ce96a78 Update CHANGELOG
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)