Skip to content

Conversation

jrschumacher
Copy link

Close #710

Definition of Ready

  • I am happy with the code
  • Short description of the feature/issue is added in the pr description
  • PR is linked to the corresponding user story
  • Acceptance criteria are met
  • All open todos and follow ups are defined in a new ticket and justified
  • Deviations from the acceptance criteria and design are agreed with the PO and documented.
  • No debug or dead code
  • My code has no repetitions
  • Critical parts are tested automatically
  • Where possible E2E tests are implemented
  • Documentation/examples are up-to-date
  • All non-functional requirements are met
  • Functionality of the acceptance criteria is checked manually on the dev system.

@muhlemmer
Copy link
Collaborator

@jrschumacher I see the PR is still in draft. Is there still work you intend to do here? Typically we wait with reviews until a PR is marked "ready for review".

@muhlemmer muhlemmer added the waiting For some reason, this issue will have to wait. This can be a feedback that is being waited for, a de label Mar 20, 2025
@muhlemmer muhlemmer moved this from 📋 Sprint Backlog to 📨 Product Backlog in Product Management Mar 27, 2025
@muhlemmer muhlemmer moved this from 📨 Product Backlog to 👀 In review in Product Management Aug 19, 2025
@muhlemmer muhlemmer self-requested a review August 19, 2025 11:21
@muhlemmer muhlemmer marked this pull request as ready for review August 19, 2025 11:21
@muhlemmer muhlemmer requested a review from IAM-marco August 27, 2025 08:55
var ErrStartServerListenAndServe = errors.New("server.ListenAndServe():")
var ErrStartServerShutdown = errors.New("server.Shutdown():")

func StartServer2(ctx context.Context, port string, opts ...func(*startServerOpts)) {
Copy link
Contributor

@IAM-marco IAM-marco Sep 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you rename this to a more meaningful name? StartServerWithOptions maybe?

Also, it would be useful to have some docs that explain how is StartServer2 different from StartServer

Comment on lines +136 to +138
if options.errorChannel != nil {
*options.errorChannel <- fmt.Errorf("%w %v", ErrStartServerListenAndServe, err)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering what's the behaviour in case I call Startserver2() without any option. In that case, errorChannel will be nil. If so, I think the server will shutdown silently without any message to the user of that happening. I would, at least, put a log.Error when errorChannel == nil. Same goes for lines 148 - 150.

@elinashoko
Copy link

Hey @jrschumacher can you pls have a look at Marco's feedback/comments? Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
os-contribution waiting For some reason, this issue will have to wait. This can be a feedback that is being waited for, a de
Projects
Status: 👀 In review
Development

Successfully merging this pull request may close these issues.

Use of log.Fatal causes upstream application to exit
5 participants