Skip to content
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

Mentoring request #11464

Closed
toblich opened this issue Jul 27, 2023 · 5 comments
Closed

Mentoring request #11464

toblich opened this issue Jul 27, 2023 · 5 comments
Assignees

Comments

@toblich
Copy link

toblich commented Jul 27, 2023

Question: Have you read the mentoring guide? Please only submit this request for general mentoring (not GSoC).

Answer: Yes I have read the mentoring guide.

What is your background? Any experience with Go, Kubernetes, React, Typescript, etc.?

Answer: I have previous experience in Go and Kubernetes.

Is there any particular issue you'd like to work on? You may want to check out the list of good first issues.

Answer: I would like to work with issue #11463, which I reported

Do you want to work with your mentor async (i.e. by Slack messaging or issue comments), or sync (e.g. using Zoom video)? Please include your time-zone if you want to work sync.

Answer: Both sync and async work for me, I'm open to whichever is preferrable for the mentor. My timezone is UTC-3.

@stale
Copy link

stale bot commented Aug 13, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.

@agilgur5
Copy link

Hey sorry this hasn't gotten any attention! Workflows gets a good amount of mentoring requests and does not have many people who can do so.

I can help you out with this. For specific questions, let's use the issue & PR. If you have any more general questions, for instance, around the build system etc, let's use this space.

Can message me on CNCF Slack if needed as well, but I'd prefer to keep things in the repo where it has posterity and can help other readers.

@agilgur5 agilgur5 self-assigned this Sep 11, 2023
@toblich
Copy link
Author

toblich commented Sep 11, 2023

Hey @agilgur5, thank you! I've just opened #11799, but I have 2 questions first

  • Testing: I don't see a trivial way to unit test this case with what's already in place, as the changed feature relies on watching k8s events, so I've opened the PR without any new tests (just manual validation). Please let me know if you think this is enough or not.
  • The PR template asks for running make pre-commit -B, which fails when I attempt to run it and deletes ~300 files under sdks/java/client/docs (which obviously is completely unrelated to my change). I'm ignoring all these deletions for the time being, but it's unexpected. Do you have any context on why this happens?

@agilgur5
Copy link

agilgur5 commented Sep 11, 2023

I've just opened #11799, but I have 2 questions first

Awesome! Thanks for your quick efforts despite the lag time here!

  • Testing: I don't see a trivial way to unit test this case with what's already in place, as the changed feature relies on watching k8s events, so I've opened the PR without any new tests (just manual validation).

Yes this may require an E2E test to confirm. They are in test/e2e/. Though off the top of my head, I'm not sure if there are existing tests for the watch functionality. Sometimes we do rely on manual validation.

In this case, I think it would be more important to confirm that there are no regressions to other functionality, as the watch is already broken for this use-case (so it ain't getting better without changes).

  • The PR template asks for running make pre-commit -B, which fails when I attempt to run it and deletes ~300 files under sdks/java/client/docs (which obviously is completely unrelated to my change). I'm ignoring all these deletions for the time being, but it's unexpected. Do you have any context on why this happens?

If part of the build fails, it can result in the Swagger / OpenAPI codegen being faulty or incomplete. That, in turn, can cause the SDK codegen to then be incorrect. Basically build failure cascade. make clean is usually enough to reset to a clean state and run build from again.

@agilgur5
Copy link

agilgur5 commented Jan 6, 2024

Closing this as #11799 did not get further activity and was later closed by OP in favor of #11855. The formal mentoring program also has been discontinued per #11802 / #11805

@agilgur5 agilgur5 closed this as completed Jan 6, 2024
@argoproj argoproj locked as resolved and limited conversation to collaborators Jul 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants