Upgrade to head #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Repairs formatting issue of tables in spec README
…on` be thrown. Updates the TCK, Spec and example implementations.
Modifies rules 1.09 and 2.13 to mandate `java.lang.NullPointerException`...
…ubscribe-√ Fixes #211 by clarifying
…te-of-1.09-√ Fixes #210 by removing 1.12 and repurposing its TCK checks for 1.09
adds TCK verification to ensure signal ordering is proper, also amends the examples to reflect the spec change.
Attempt to clarify the signalling sequence in the spec
…s-jar-√ Fixes #217 by including the examples project in the publish task
…tion-processor-spec-213 fix #212 issue on spec 213 testing wrt Processor
This rule is in conflict with 1:11 which allows a Publisher to treat multiple Subscribers as either as unicast or multicast recipients. The verification of proper multicast behavior (which 1:12 specified) has been retained, the test methods renamed accordingly.
remove rule 1:12 (produce same elements to all Subscribers)
=tck minor test name fixup, it is a required test
Fixed wrong footnote reference in README.md
+ add better readme on what this method is + add better javadoc on this method - removes reference to old style spec annotation from readme + proposing to change method name to "createFailed..." as it is the wording used in the spec and reactive manifesto (footnote 1.1) + more info in tck/README that it is not legal to signal on* before sub Resolves #237, #235
Addresses a couple of typos in the examples for AsyncSubscriber and Sync...
!tck - clarifies error publisher, and method name change (?)
+tck #236 example subscriber whitebox tested, and whitebox fixed
SubscriberBlackboxVerificationRules explained
=tck #362 signal onComplete in 201 blackbox verification
+tck #362 complete subscriber under test once done in 205
=tck #362 blackbox 209 must issue onSubscribe before any other signal
+tck #362 wait for request signal in 209, and new additional tests
…ce-drop-fix optional_spec111 test addition.
We use the `#.##` style in referring to rules everywhere, this one ref was using a different style - fixed that.
Be consistent in reference style
More apostrophe fixes
add patriknw to CopyrightWaivers
Prepare 1.0.1
=tck #384 dont check for cause message when checking 3.9
…rule-ktoso =spec #384 amend spec to allow not mentioning rule number in exception message
Updating versions to 1.0.1-RC2 and clarifying changes in RELEASE-NOTE…
* Fix links to "Terminal state" * add angelsanz to CopyrightWaivers.txt
* Bridge between Reactive-Streams and JDK 9 Flow API * Apply changes based on ktoso's feedback * Use oraclejdk9, resolve build.gradle conflict * Change txt/code to use "Reactive Streams" as designator * NPE to use the updated parameter name. * Rename bridge class, tester class (+javadoc)
* Java 9 Flow bridge: add Subscriber converters * Fix return type javadoc
* Example synchronous range Publisher * Udpated with rule numbers in comments * Mentioning rule 3.9 again in emit() * Move classes to the unicast package.
* Add JDK9 TCK, using adapters * Fixing wrapping and unwrapping of the wrappers themselves. * Renames the converters to "toX" for RS and "toFlowX" for Flow. Fixes so that the dist url for gradle is http iso https (TravisCI bug?) Adds regression test for bridge converters. * fix formatting * cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.