GH-725: RecordContext should provide access to lastFailureReason

[jvissers]

Exposes lastFailureReason from Recordcontext

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

jvissers seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[jvissers]

I have signed the agreement.

…

On Mon, Mar 4, 2024 at 9:52 AM cla-assistant[bot] ***@***.***> wrote: [image: CLA assistant check] <https://cla-assistant.io/confluentinc/parallel-consumer?pullRequest=726> Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement <https://cla-assistant.io/confluentinc/parallel-consumer?pullRequest=726> before we can accept your contribution. ------------------------------ *jvissers* seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account <https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/#commits-are-not-linked-to-any-user> . You have signed the CLA already but the status is still pending? Let us recheck <https://cla-assistant.io/check/confluentinc/parallel-consumer?pullRequest=726> it. — Reply to this email directly, view it on GitHub <#726 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWRQDDKD3SJFAWNPTCXUYDYWQY3JAVCNFSM6AAAAABEEZT7YCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZWGAZTSMBRGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rkolesnev]

Hi @jvissers - is there a mismatch between email configured on your GH client / to do the commit and configured on your GH account? I think CLA bot is cross-checking on that - if they don't match - that may trip it over.
Can you please add the change to the CHANGELOG.adoc - it is a small change - but i think it is a useful one - so would be good to highlight in the changelog.

Thanks.

[rkolesnev]

Here is a GH troubleshooting link for account / local account setup - if that helps troubleshooting-commits
Looking at the commit here - your username is not resolved as a link to GH user - there may be something missing in your local account setup - potentially that prevents CLA bot from working properly - as it cant resolve author on the commit to your GH user.

[jvissers]

I've updated changelog, updated the git config for this project locally and pushed my changes. Apparently still not everything is working as desired. I've followed the link for troubleshooting-commits, but that doesn't seem to reflect what I'm seeing. For one this ("over blue ? to the right of the username") as gets mentioned here: "To read a message about why the commit is not linked, hover over the blue? to the right of the username.", is not showing. What else can I do?

…

On Mon, Mar 4, 2024 at 1:40 PM Roman Kolesnev ***@***.***> wrote: Here is a GH troubleshooting link for account / local account setup - if that helps troubleshooting-commits <https://docs.github.com/en/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user> Looking at the commit here - your username is not resolved as a link to GH user - there may be something missing in your local account setup - potentially that prevents CLA bot from working properly - as it cant resolve author on the commit to your GH user. — Reply to this email directly, view it on GitHub <#726 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWRQDGEHKVX4I7U6P3JHLTYWRTVHAVCNFSM6AAAAABEEZT7YCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZWGQ4TMNRTGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rkolesnev]

could you please try to squash the commits on your branch or reset and recommit and then force push the changes?

Basically the first commit still has your oracle email associated with it - the local changes are not retrospective so they only applied to the 2nd commit (change to the changelog).

I am hoping that force-push with new commit(s) that have updated email - will let the check to re-evaluate properly.
Alternatively - new PR would need to be created - and should go through fine as long as commits in it are using your Gmail email.

Thanks.

If you run git log on your branch - you should only have commits with Author: jvissers <vissers.j@gmail.com> and not Author: jvissers <jan.vissers@oracle.com> -- as this one is not linked to your GH account i guess.