Skip to content

Write a README.md explaining goals and rationale #2

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

Closed
viktorklang opened this issue Mar 3, 2014 · 1 comment
Closed

Write a README.md explaining goals and rationale #2

viktorklang opened this issue Mar 3, 2014 · 1 comment

Comments

@viktorklang
Copy link
Contributor

No description provided.

@rkuhn
Copy link
Member

rkuhn commented Mar 26, 2014

fixed by #1

@rkuhn rkuhn closed this as completed Mar 26, 2014
ktoso referenced this issue in ktoso/reactive-streams Aug 11, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
ktoso referenced this issue in ktoso/reactive-streams Aug 11, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
ktoso referenced this issue in ktoso/reactive-streams Aug 11, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
ktoso referenced this issue in ktoso/reactive-streams Aug 11, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
ktoso referenced this issue in ktoso/reactive-streams Aug 11, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
ktoso referenced this issue in ktoso/reactive-streams Aug 20, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
+ moved 3.2 from subscriber tests to publisher tests
+ moved 3.4 to publisher
+ moved 3.6 spec to Publisher
+ check rule 3.3, assuming publisher breaks the reccursion
+ Splitting subscriber whitebox / blackbox tests
+ both got verifications of rule 2.3
+ whitebox is the previous impl
+ blackbox is tests which work without any additional probes
  it mostly wrapps the subscriber in order to check things
+ better 2.10 verification in blackbox
+ test was testing onComplete instead of onError like it should
+ better blackbox tests for 2.9
+ more java-doc style java-docs (added {@link}s)
+ minor cleanups and refactors to make BlackboxProxy more understandable

Awaiting either more feedback or maybe an initial merge so we can
continue working on the TCK from there on?
ktoso referenced this issue in ktoso/reactive-streams Aug 22, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
+ moved 3.2 from subscriber tests to publisher tests
+ moved 3.4 to publisher
+ moved 3.6 spec to Publisher
+ check rule 3.3, assuming publisher breaks the reccursion
+ Splitting subscriber whitebox / blackbox tests
+ both got verifications of rule 2.3
+ whitebox is the previous impl
+ blackbox is tests which work without any additional probes
  it mostly wrapps the subscriber in order to check things
+ better 2.10 verification in blackbox
+ test was testing onComplete instead of onError like it should
+ better blackbox tests for 2.9
+ more java-doc style java-docs (added {@link}s)
+ minor cleanups and refactors to make BlackboxProxy more understandable
+ added missing delegation of boundedDepthOfOnNextAndRequestRecursion
+ improved error message when expecting error message
ktoso referenced this issue in ktoso/reactive-streams Sep 2, 2014
* Make spec rules linkable (#2.13) and use links in TCK
* Verified 1-element-publishers are testable with TCK (skips unsupported tests)
+ moved 3.2 from subscriber tests to publisher tests
+ moved 3.4 to publisher
+ moved 3.6 spec to Publisher
+ check rule 3.3, assuming publisher breaks the reccursion
+ Splitting subscriber whitebox / blackbox tests
+ both got verifications of rule 2.3
+ whitebox is the previous impl
+ blackbox is tests which work without any additional probes
  it mostly wrapps the subscriber in order to check things
+ better 2.10 verification in blackbox
+ test was testing onComplete instead of onError like it should
+ better blackbox tests for 2.9
+ more java-doc style java-docs (added {@link}s)
+ minor cleanups and refactors to make BlackboxProxy more understandable
+ added missing delegation of boundedDepthOfOnNextAndRequestRecursion
+ improved error message when expecting error message
ttulka added a commit to ttulka/reactive-streams-jvm that referenced this issue Jun 12, 2017
The problem with crashing onXXX is that you may end up in an undefined
state where even calling onError fails.
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

No branches or pull requests

2 participants