Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Nathan Rauh
    @njr-11
    Given that the main MicroProfile number is still unavailable (requires a host code), I scheduled a one-time webex meeting for today's call. Let's give this a try and see how it goes,
    Meeting link:
    https://ibm.webex.com/ibm/j.php?MTID=m7f7f70a64874d7a9889d6fc7f8d67a2d
    Meeting number:
    145 548 5765
    MPCP12Nov20 (67271266 from phones and video systems)
    Nathan Rauh
    @njr-11
    One-time webex meeting for Thursday's (Dec 10) MicroProfile Context Propagation call:
    Meeting Link:
    https://ibm.webex.com/ibm/j.php?MTID=mafafd6613681f093db1bf4db8597715a
    Meeting number:
    145 325 2560
    Password:
    mpcp2020D10 (67272020 from phones and video systems)
    Stéphane Épardaud
    @FroMage
    @njr-11 Hi, I don't have anything useful to report today, so if nobody else shows up feel free to cut it short. Unless you have something in which case I can join
    Nathan Rauh
    @njr-11
    No problem. I started up the meeting anyway since I had posted it publicly just in case anyone else wanted to join with items to cover, but there wasn't anything else to cover, so I ended it early.
    Nathan Rauh
    @njr-11
    In between the last meeting and now I did track down what appears to be some existing potential integration points with SmallRye Mutiny https://smallrye.io/smallrye-mutiny/apidocs/io/smallrye/mutiny/infrastructure/Infrastructure.html Unfortunately the JavaDoc for this class is almost completely empty, making it unclear how much these methods accomplish and how close we could get to a correct solution with them.
    Stéphane Épardaud
    @FroMage
    Well SR-CP is already integrated with that
    and I've added a few methods to SR-CP to be able to influence which contexts are captured by Mutiny via annotations, but we haven't integrated it yet, so I can't really have enough feedback to bring this to the spec yet
    ATM Mutiny propagates all the contexts, which is what we're trying to solve with annotations on the outer method
    Nathan Rauh
    @njr-11
    Here is the one-time conference call info for this week's meeting. We will go over issue #206 which Emily raised to republish the 1.1 release as 1.2 in order to comply with the new MicroProfile Working Group release process.
    Meeting link:
    https://ibm.webex.com/ibm/j.php?MTID=m8c96f7cea87229adedf1d108d5feec6f
    Meeting number:
    145 547 2093
    Password:
    MPCP210114 (67272101 from phones and video systems)
    Stéphane Épardaud
    @FroMage
    ack
    Nathan Rauh
    @njr-11
    I created MP Context Propagation 1.2 release candidate 1 following the new release process:
    https://github.com/eclipse/microprofile-context-propagation/releases/tag/1.2-RC1
    I tested it out on OpenLiberty, where it runs cleanly as expected being that it's identical to v1.1 apart from the different release process. I also sent an email out to the MicroProfile list so that others can confirm that we've correctly followed the new process before proceeding to the 1.2 release.
    Stéphane Épardaud
    @FroMage
    Great
    Nathan Rauh
    @njr-11
    I've started working on getting a 1.2 final release created, and I have the artifacts at the following location for staging. I'm not sure how long they'll stick around before being auto-removed by sonatype, but they are at least available for now. For a final release, I can't push anything over to Maven yet.
        <repository>
            <id>orgeclipsemicroprofile-1416</id>
            <name>MP staging</name>
            <url>https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-1416</url>
        </repository>
    Nathan Rauh
    @njr-11
    MP Context Propagation 1.2 has been submitted for release review. We should find out sometime within the next 2 weeks if it is approved, after which we would be able to promote the artifacts on staging to be the final 1.2 release
    Nathan Rauh
    @njr-11
    One-time conference call info for this week's meeting:
    Meeting link:
    https://ibm.webex.com/ibm/j.php?MTID=md94e781ab7a2875ef1df20abc1a20912
    Meeting number:
    145 207 6508
    Password:
    mpcp210211
    Nathan Rauh
    @njr-11

    Yesterday, I learned that the staging location for our 1.2 final release had disappeared. Possibly the release process took too long? In any case, I resubmitted the build for it, and now we have a new staging location,

        <repository>
            <id>orgeclipsemicroprofile-1434</id>
            <name>MP staging</name>
            <url>https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-1434</url>
        </repository>

    Also, the ballot for approval of 1.2 is now set to conclude on March 10.

    Nathan Rauh
    @njr-11
    One-time conference call info for this week's meeting:
    Meeting link:
    https://ibm.webex.com/ibm/j.php?MTID=mcf1d3cb432597e0530d6f795402c4c73
    Meeting number:
    145 651 4816
    Password:
    mpcp210311 (67272103 from phones and video systems)
    Stéphane Épardaud
    @FroMage
    Hi, I don't have anything to report, so unless you have questions for me or news, I'l probably skip it
    Nathan Rauh
    @njr-11
    That's fine. The only news was already announced on the MicroProfile mailing list yesterday, that the vote for our 1.2 release was approved and we are free to proceed with that. I've released the artifacts for it to maven and they should be showing up soon if not there already. Other than that, just finishing off the release process
    Stéphane Épardaud
    @FroMage
    OK great, thanks
    Nathan Rauh
    @njr-11
    The release info for version 1.2 is now available here, including links to docs at their official location and the maven location,
    https://github.com/eclipse/microprofile-context-propagation/releases/tag/1.2
    Nathan Rauh
    @njr-11
    Everyone please see https://github.com/eclipse/microprofile-marketing/issues/420#issuecomment-807889940 - we will be able to start using a MicroProfile zoom account for the monthly meetings again, but first we need to find a couple of contributors to assign as admins for our project. Let me know if anyone is willing (it doesn't mean you need to do anything different, just that you will have access to start the call and record it and so forth if you ever need to). Also listed in that issue is the opportunity to submit an MP quote for anyone who would like to do that. See the link in Amelia's comment to the issue
    Nathan Rauh
    @njr-11

    One-time conference call info for this week's meeting (still using this until we get our Zoom admins decided on),
    https://ibm.webex.com/ibm/j.php?MTID=mfb86fd94bc927dc798da8c5006025759
    Meeting number:
    145 848 2193
    Password:
    MPCP2104 (67272104 from phones and video systems)

    Some agenda items will be figuring out our Zoom admins and discussing implications of Jakarta EE 10 for our spec - including whether there is anything we should be requesting from Jakarta Transactions or CDI specs (or others) to help integrate with context propagation.

    Nathan Rauh
    @njr-11
    Just a reminder that we will be using the MicroProfile web conf starting with today's meeting (20 minutes from now)
    https://eclipse.zoom.us/j/97956947287
    instead of the company-specific web conf number that we were temporarily using over the last 6 months or so
    Nathan Rauh
    @njr-11
    To anyone who is trying to join the meeting, it seems to not be recognizing me as someone who can claim the admin role and start the call. I'm getting no option for that. @FroMage if you happen to be trying to join, are you seeing the same? I'm wondering if the admin roles weren't set up yet or weren't done properly. Or, I just don't know the right place to look
    Nathan Rauh
    @njr-11
    The issue with the MicroProfile zoom web conference has been figured out now. It turns out that any meeting needs to be separately scheduled by John or Kevin in Zoom at the designated times, in addition to the MicroProfile calendar, so that we can join it. This means that the zoom call won't be used for impromptu meetings on short notice, and will primarily be for the scheduled ones, which I think we are fine with. They did offer that since our meeting for the month of May ended up being cancelled, to set one up for next Thursday (May 27) if we want it, and I said I'd run that by the group. Let me know if anyone would like to have that meeting. Otherwise, the next scheduled meeting is Thursday, June 10.
    Nathan Rauh
    @njr-11
    This month's MicroProfile call - this Thursday at the normal time (8:30am Central US time) - will be using the MicroProfile zoom call, which we now have access to:
    https://eclipse.zoom.us/j/97956947287
    Some things to discuss include plans for Jakarta EE 9 compatibility and when to start on it, and other functions such as the recently requested ManagedExecutor.allOf operation and if there are any updates on smallrye/smallrye-context-propagation#260
    Stéphane Épardaud
    @FroMage
    Huh, did I miss the meeting by messing up my timezone calculations?
    Nathan Rauh
    @njr-11
    For anyone who is trying to join the MP Context Propagation meeting- it seems we are back to the original problem where I cannot claim being the host and so cannot start the meeting. If @FroMage happens to be on - are you able to claim the host code?
    Stéphane Épardaud
    @FroMage
    Well, it tells me The meeting has not started
    The page will refresh in 5 seconds, or reload the page now.
    Nathan Rauh
    @njr-11
    I get "Waiting for the host to start this meeting" and then no option to actually enter in the host code and start it. Just like the original problem I reported to John/Amelia. They thought they had correct it, and we even did a practice meeting to confirm, but I wonder if they only halfway fixed it. I'll send another email to ask them about it
    Stéphane Épardaud
    @FroMage
    Oh well :)
    Nathan Rauh
    @njr-11
    Just a reminder for next week's meeting - It's at the normal time and Stéphane will be hosting it. I won't be able to attend, but I have updated our meeting minutes agenda https://docs.google.com/document/d/1Iy_k-Yaq3AnfWaZ97z2CjOf4LLt71UnaVw8NAbyeVDs/edit#heading=h.9vxk9dt6gaik with everything I know about the effort for Jakarta EE 9.1 compatibility for MicroProfile specs that was recently started, including a link to the issue that was opened against our spec and the global tracking issue for MP 5.0. It doesn't make any difference to me whether we use a point release or a major version release for this - I'll go along with whatever the rest of you decide during the meeting.
    Stéphane Épardaud
    @FroMage
    The meeting has not started
    The page will refresh in 5 seconds, or reload the page now.
    Well, this is just bad luck
    Ah no, it's in 30 minutes :)
    OK cool
    Stéphane Épardaud
    @FroMage
    Well it worked, after I created an account, but I was the only one, so not very useful.
    Nathan Rauh
    @njr-11
    @FroMage - sorry about that. I tried to arrange to have at least one other person from my company attending in my absence. I wonder if they ran into issues as well and didn't get them resolved in time
    Stéphane Épardaud
    @FroMage
    No problem
    Nathan Rauh
    @njr-11
    I created pull #211 following the instructions for MicroProfile 5.0/Jakarta EE 9 alignment under #210
    I asked about release numbers and was told that we will be using a point release (1.3) because there is no change to the spec API, only to the TCK tests (to use the jakarta package names)
    Nathan Rauh
    @njr-11
    Nathan Rauh
    @njr-11

    Reminder for this month's MP Context Propagation call:
    When Thu, August 12
    Where https://eclipse.zoom.us/j/97956947287 (map)
    Description Context Propagation public and editable agenda

    Join Zoom Meeting
    https://eclipse.zoom.us/j/97956947287

    Topic: MP Context Propagation Call
    Time: 08:30 AM Central Time (US and Canada)

    Nathan Rauh
    @njr-11
    I found out how the claim host option is supposed to work on the Zoom calls. According to this document, we should go to Participants, then select yourself in the list, then "Claim host" should appear as an option,
    https://docs.google.com/document/d/1xTBnhJ2SjDmLjM6OTyRVjSnjb6r5s8_opGjSyZnD5vA/edit#
    I think I missed the step about selecting myself from the list, and that is likely why I couldn't get it working during the meeting.
    Stéphane Épardaud
    @FroMage
    I can't make the call today, I'm sorry
    Nathan Rauh
    @njr-11
    No problem. I didn't have much to discuss other than to report that we're getting close to being able to submit a compatible certification request for our 1.3 implementation (had to wait for a Jakarta-capable MP Config implementation to catch up because the TCK uses that spec in testing ours).