-
Notifications
You must be signed in to change notification settings - Fork 534
Release 1.0.1 #345
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
Comments
How urgent is this? I might have found an issue with My suspects are the I'm currently preparing a TCK test that should detect if |
The 2-year anniversary is on the 29th of April :) |
I'll be ready to publish it but i think it's a good idea. Could we reference in this ticket issues we are going to address (or label them) ? In particular would this come with the soft breaking about request(0) not erroring ? |
Just FYI, jdk was successfully changed to reject request(0) for initial jdk9 release, even though I still think it was a bad idea. But better to conform to 1.0 spec anyway... |
Thanks @DougLea! |
@reactive-streams/contributors Has everyone updated their implementations to try the new TCK? |
Akka Streams passing: akka/akka#23267 👍 (Let's await some more impls to upgrade, at least 3 or 4 I'd say) |
RxJava 2.1.2 snapshot passing: ReactiveX/RxJava#5453 |
Please give the 1.0.1 Release Candidate 1 TCK a run so we can be sure it did not cause any unexpected regressions / changes. See here for libraries updating to 1.0.1 process: reactive-streams/reactive-streams-jvm#345 Thanks in advance!
I made a PR in Vert.X asking to check the RC: vert-x3/vertx-reactive-streams#9 |
I'll check in a moment today thanks @reactive-streams/contributors |
FYI VertX did not reply on my ticket so far. |
Give us one more day its one of those very few bank holiday in the US :) |
JDK 9b176 via this: 37 tests done, 2 failed, 15 ignored SubmissionPublisherTckTest.required_spec309_requestNegativeNumberMustSignalIllegalArgumentException
SubmissionPublisherTckTest.required_spec309_requestZeroMustSignalIllegalArgumentException
|
On 07/04/2017 11:53 AM, David Karnok wrote:
JDK 9b176 via this
<https://github.com/akarnokd/akarnokd-misc-java9/blob/master/src/hu/akarnokd/java9/benchmark/SubmissionPublisherTckTest.java>:
Thanks. I was in the midst of trying to reconstruct this.
37 tests done, 2 failed, 15 ignored
As discussed originally, We must use the usual JDK exception message
formats for all exceptions, not RS-spec rule quotes.
All other rs-tck tests accommodate this, but I hadn't checked against
the annoying non-positive argument check added months ago.
Can the text-match be loosened?
…-Doug
SubmissionPublisherTckTest.required_spec309_requestNegativeNumberMustSignalIllegalArgumentException
java.lang.AssertionError: Got expected exception [class
java.lang.IllegalArgumentException] but missing message part [3.9],
was: non-positive subscription request
SubmissionPublisherTckTest.required_spec309_requestZeroMustSignalIllegalArgumentException
java.lang.AssertionError: Got expected exception [class
java.lang.IllegalArgumentException] but missing message part [3.9],
was: non-positive subscription request
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACIWPw7qBSogE7r5DC3BTqfBQNBuJ4uqks5sKl_ogaJpZM4MbALd>.
|
Right, I guess we'll have to loosen up a bit - I'll handle that; |
@DougLea The text-match could be loosened—it is there to make sure that the IAE doesn't stem from something else (the alternative would be to introduce a new Exception type, which would IMO not pull its weight). |
@smaldini Ok :) |
1:9 and 2:13 do not mandate that the rule is referenced in the cause message so I think it'd actually be more reasonable to drop the requirement. Thoughts? (It is of course completely backwards compatible) |
Yeah, very good point. We even have to do so, otherwise the TCK would allow "not quite the spec abiding" impls to pass. Since the JDK's interfaces have their own style of messages, and will soon become the "main" interfaces, we should make sure they fit the rules (or rather, the rules in this case fit them). Sanity checking: Yes, it's definitely backwards compatible - we require less from implementations now. PRed separately from TCK change in case this requires more discussion, but seems pretty obvious: #386 |
You should go ahead then with RC2 i'll batch update, sorry i'm in the middle of some widespread polishing that is loosely connected to RS (properly recognizing 1.3 and 3.9). |
It was only staged, not closed, so won't get to central yet. |
@ktoso Yes please! |
Shipping |
Sorry, guys, between your confirmations and the release to Maven I had some urgent business matters to attend to. Thanks @ktoso for helping out!
|
No worries, let the businessing go well :-) It's out: http://repo1.maven.org/maven2/org/reactivestreams/reactive-streams/1.0.1-RC2/ |
@smaldini Any update on RC2? :) |
Yup we;re good on our side, I removed some exceptions to the tck but I have 2 remaining one I need to investigate regarding two test expectations regarding a processor. Also I used the 3.1 to get back on track for spec we discussed (allowing onError on request), so we don't have this exception anymore like rxjava, good citizen again. |
So when do you think we shall proceed to GA ? |
We're waiting for info if you're passing the TCK :-) |
Oh yes we do! |
Completely, right? Including the issues you mentioned above? |
If all TCK tests pass then I think we should ship 1.0.1 next week.
…--
Cheers,
√
On Aug 4, 2017 08:33, "ktoso" ***@***.***> wrote:
Completely, right? Including the issues you mentioned above?
If so, then I think we're good to call the 1.0.1, at least IMHO :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAqd6Gh3VOBVdYZUDHTsbkWOFi7wrr7ks5sUrtRgaJpZM4MbALd>
.
|
👍 We got back on track by adopting internal/external facing subscriber protocol so we respect the rules (especially the onError possible from request) |
RxJava 2 ready for 1.0.1! 👍 |
@rkuhn would you be able to do us the honors of cutting the release within the next 8h? From the following tag I just pushed: https://github.com/reactive-streams/reactive-streams-jvm/tree/v1.0.1 Let me know if you won't have time today and I'll try to sort it out some other way, ok? 👍 I'll prepare the website, then upload javadoc etc. |
Yes, I’ll do it around lunch time. |
Vielen dank, dr. Kuhn!
…--
Cheers,
√
On Aug 9, 2017 11:16 AM, "Roland Kuhn" ***@***.***> wrote:
Yes, I’ll do it around lunch time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAqd8wAoqvLNSBDqApIMLZHInWR0ME4ks5sWXjugaJpZM4MbALd>
.
|
The artifacts are staged at https://oss.sonatype.org/content/repositories/orgreactivestreams-1032, please let me know when to release them. |
👍 for release asap. |
Thanks @rkuhn, I'm currently working to make sure that website, documentation links etc are updated. Would you be OK with releasing them 4pm CEST? (That way I have an extra couple of hours to verify things over at my end) |
Sure thing!
|
@rkuhn Perfect, thank you! |
So, shall I press the button now? |
Yes! |
Will you or somebody post the 1.0.1 javadoc to
? |
I have a PR I will merge for that once I see the artifacts replicated to
Maven Central.
…--
Cheers,
√
On Aug 9, 2017 16:25, "David Karnok" ***@***.***> wrote:
Will you or somebody post the 1.0.1 javadoc to
http://www.reactive-streams.org/reactive-streams-1.0.1-javadoc/
?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#345 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAqdw3EzDL8kXElZ16fSyJ5ecDSKR0bks5sWcFcgaJpZM4MbALd>
.
|
The artifacts are on Maven Central. |
Excellent! reactive-streams.org has been updated, great work everyone!! 🎆🎆🎆🎆🎆🎂🎂😎 |
Excellent! 🎆 |
I propose that we, @reactive-streams/contributors, release 1.0.1 on the 2-year anniversary of 1.0.0
No semantically breaking changes.
Improved TCK? Improved docs? Improved spec?
The text was updated successfully, but these errors were encountered: