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

Merge next into Fred deprecate closer and do not delete class (used in plugins) #1

Open
wants to merge 641 commits into
base: fred-deprecate-closer
Choose a base branch
from

Conversation

ArneBab
Copy link

@ArneBab ArneBab commented Nov 30, 2024

This PR updates the fred-deprecated-closer branch to next. It also reverts the removal of the Closer class, because that’s used from plugins.

After finishing the review of hyphanet#830 I’d love to merge it. For that we’ll need this updated to next — this PR does that.

For the review see hyphanet#830 (comment)

The big changes for updating to next are:

Please check whether they are OK and merge them into your branch. If they are, we can merge For the review see hyphanet#830 into next.

Bombe added 30 commits February 27, 2024 15:00
I could not resist fixing the broken javadoc tag.
ArneBab and others added 30 commits November 13, 2024 07:47
Show GitHub Actions status using shields.io
Wrapper validation now hosted at gradle/actions repo.
These have been around since 2011.

* The realtime parameter of getRoutingBackedOffUntil was set to `true`
  for both realtime and bulk.
* The bulk backoff parameter in getPeerNodeStatus was not used due to
  it having the wrong name (the equally named field was used instead).

Fixes db3329d
While beneficial for memory usage, reusing mutable objects may lead to
all kinds of data consistency issues. It's just not worth saving the few
bytes.
The underlying byte[] is mutable and could accidentally be changed after
instantiation of the wrapper object. To ensure that the hashCode or the
(natural or fast) order of the object does not change, the data must be
copied defensively.
These are files with merge issues against next.
This required quite a few manual fixes.
This reverts commit f4fed4c.

We cannot remove the Closer, because it may be used in plugins.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants