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

Upgrade to Reactor 2020.0 #2588

Merged
merged 2 commits into from May 18, 2021
Merged

Conversation

shakuzen
Copy link
Member

@shakuzen shakuzen commented Apr 30, 2021

Re-attempts #2359. This is using the tryEmitNext method instead of emitNext to avoid any failure handling - we want to drop elements on failure.
This implementation hopefully obviates #2378.
Opened as a draft until we branch 1.7.x so main is ready for 1.8 development.
This will make the implementation of #792 straightforward since Reactor Netty added support for UDS in 1.0.0.

@shakuzen shakuzen added enhancement A general enhancement registry: statsd A StatsD Registry related issue labels Apr 30, 2021
@shakuzen shakuzen added this to the 1.8 backlog milestone Apr 30, 2021
@@ -66,7 +66,7 @@ void bufferMultipleStrings() {
"fourteen bytes"
);

Flux<String> buffered = BufferingFlux.create(source, "\n", 27, Long.MAX_VALUE);
Flux<String> buffered = BufferingFlux.create(source, "\n", 27, 1000);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -79,8 +80,7 @@
private final HierarchicalNameMapper nameMapper;
private final Map<Meter.Id, StatsdPollable> pollableMeters = new ConcurrentHashMap<>();
private final AtomicBoolean started = new AtomicBoolean();
DirectProcessor<String> processor = DirectProcessor.create();
FluxSink<String> fluxSink = new NoopFluxSink();
Sinks.Many<String> sink = new NoopManySink();
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I was working on this, I wished there was a built-in no-op implementation, but then I wondered if we really need one. If we don't subscribe, then it is almost a no-op. Maybe our NoopManySink isn't really needed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's explore this in a separate change.

@shakuzen shakuzen marked this pull request as ready for review May 12, 2021 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A general enhancement registry: statsd A StatsD Registry related issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant