Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 27, 2022

Bumps hazelcast from 5.1 to 5.1.3.

Release notes

Sourced from hazelcast's releases.

v5.1.3

This document lists the new features, enhancements, fixed issues, and removed or deprecated features for Hazelcast Platform 5.1.3 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

==== 5.1.3 Release Notes ====

  1. Enhancements
  1. Fixes
  • When the hazelcast.socket.buffer.direct property is enabled, clusters no longer throw exceptions in response to text protocols such as the REST API. hazelcast/hazelcast#21700

v5.1.2

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast 5.1.2 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

Fixes

  • Fixed an issue where a cluster could not be formed when security is enabled, various client permissions are set, and multiple members are started simultaneously. #21510
  • Fixed an issue where a cluster was unresponsive when you perform a health check to see the members are in the safe state; cluster members were hanging in the REPLICA_NOT_SYNC state during such health checks. #21208
  • Fixed an issue where the list of members in the cluster was reset to an empty list when the UUID of a cluster changes after its restart: this was causing startup failures since Hazelcast could not manage the events due to the empty member list after a restart. #21178
  • Fixed an issue where the statistics like puts and removals were not increasing when these operations are executed through Transactional interface. #21107
  • Fixed a data race in SingleProtocolEncoder; while one method of this interface is called from the input thread, another one is called from the output thread which was causing the race. #20994
  • Fixed an issue where the automatic module name in hazelcast-5.x.jar could not be detected using Gradle. The reason was /META-INF/MANIFEST.MF not being the first or second entry in the JAR file; now this manifest file is the second entry. #20976

v5.1.1

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.1.1 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

Fixes

  • Fixed an issue where the partition migrations were failing when there is a single map in the cluster with Merkle trees enabled. #20929
  • Fixed a potential deadlock during partition migrations and inability to make progress while performing graceful shutdown with persistence enabled. #20813
Commits

Dependabot compatibility score

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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [hazelcast](https://github.com/hazelcast/hazelcast) from 5.1 to 5.1.3.
- [Release notes](https://github.com/hazelcast/hazelcast/releases)
- [Commits](hazelcast/hazelcast@v5.1...v5.1.3)

---
updated-dependencies:
- dependency-name: com.hazelcast:hazelcast
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 27, 2022
@yuce yuce merged commit ab81caf into master Dec 28, 2022
@dependabot dependabot bot deleted the dependabot/maven/examples/paging-predicate/member-with-comparator/com.hazelcast-hazelcast-5.1.3 branch December 28, 2022 08:46
mdumandag added a commit that referenced this pull request Mar 28, 2023
* fix custom lookup serializer for class error

* change __subclasses__ to __mro__

* add test for custom global serialization

* Add put_all() to MultiMap [API-1235] (#600)

Added multimap put-all

* Bump hazelcast in /examples/paging-predicate/member-with-comparator (#602)

Bumps [hazelcast](https://github.com/hazelcast/hazelcast) from 5.1 to 5.1.3.
- [Release notes](https://github.com/hazelcast/hazelcast/releases)
- [Commits](hazelcast/hazelcast@v5.1...v5.1.3)

---
updated-dependencies:
- dependency-name: com.hazelcast:hazelcast
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Convert `Config` classes to public API [API-1280] (#521)

* Convert `Config` classes to public API

These were converted into private classes during the 4.0 migration,
as we were only supporting keyword arguments for the client configuration.

However, that led to a poor user experience, as we had to use `**kwargs`,
instead of listing all the configuration elements in the client constructor.
(IDEs become painfully slow once we list all keyword arguments, as there
are too many of them)

The solution to this problem is to make the Config classes public API
and make the client able to use it directly.

```python
config = Config()
config.cluster_name = "dev2"

client = HazelcastClient(config)
```

We provide full type hints for config elements.

* bump the client version used in tests

* address review comments

* shutdown clients in teardown method

* Add code sample to show how Hazelcast works with Pandas DataFrames. (#604)

Added code sample to show how Hazelcast works with Pandas DataFrames.

* fix the problems of added test

* test after updating branch

* test after updating branch

* test after updating branch

* add another test

* fix some typos and unnecessary parts

* fix the test

* fix the test

* Update custom_global_serialization_test.py

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Nevzat Seferoglu <nevzatseferoglu@gmail.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Metin Dumandag <metin@hazelcast.com>
Co-authored-by: Meltem Tokgöz <meltemtgz@gmail.com>
Co-authored-by: Metin Dumandag <29387993+mdumandag@users.noreply.github.com>
@mdumandag mdumandag added this to the 5.2.0 milestone Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants