@coolwednesday @Umang01-hash can you please review this .

@coolwednesday @Umang01-hash can you please review this .

@Umang01-hash @coolwednesday any updates..

@coolwednesday @Umang01-hash the example tests are failing now successfully as per the issue mentioned..

@HarK-github Thanks for the contribution — the functionality looks promising!
However, the PR is currently failing due to a test error, and we’ll need to get that resolved before merging to avoid breaking the pipelines.

Would you be open to taking a look at the failing test and updating the PR? Happy to help if you need any guidance along the way.

@Umang01-hash Can you run the test again?

Hi @HarK-github, we have re-run the pipeline, and it failed for two prior versions of go.
You can go through and check whats the exact issue and fix it, we can discuss on the same if you face any issue.

@aryanmehrotra Hey .. How can i test the workflowpipeline myself ? right now I have to keep asking for it..

Rather than creating a PR directly on the gofr-repo, you can create a PR on your forked version's development that should also trigger the pipeline and you will have complete access there.

@Umang01-hash @aryanmehrotra Issue is resolved please check .

@HarK-github The added “wait-for-services” logic is not the correct or efficient solution. It should be rejected or replaced with Docker healthchecks if—and only if—service startup timing is genuinely causing flakiness.

The new waiting script introduces multiple sequential sleep loops (potentially adding 2–5 minutes to every CI run), even when all services are already healthy. GitHub Actions service containers (MySQL, Redis, Kafka) become available automatically once ports are exposed, so manual port polling is usually unnecessary.

If there are rare startup race conditions, a cleaner and faster solution is to rely on Docker healthchecks, for example:

services:
  mysql:
    image: mysql:8.2.0
    ports:
      - 2002:3306
    env:
      MYSQL_ROOT_PASSWORD: password
      MYSQL_DATABASE: test
    options: >-
      --health-cmd='mysqladmin ping -h localhost -ppassword --silent'
      --health-interval=5s
      --health-timeout=5s
      --health-retries=10
      --health-start-period=5s

This allows GitHub Actions to automatically wait until the container is healthy before running tests—without manual sleeps or custom loops.

Also as requested above why we have these changes ?? please revert all of them back.

@Umang01-hash Can you run the test again?

@HarK-github I re-ran the workflow and the examples test are failing for all go versions. Please have a look and resolve it.

@Umang01-hash I have tried changing the workflow and still there are two failing tests. As attached in the picture, the current workflow pipeline is passing these failures without exiting with error. Example Unit Testing (v1.25) has no issues. Also @coolwednesday said the current tests are failing, so I guess my workflow is correct, the unit tests are wrong. @aryanmehrotra Could you help me with this..

Hey There !

If you are unable to connect to kafka, the workflow needs to handle the configs for the tests properly. Maybe kafka might be running at some other port. I noticed the conversation thread talked about changing ports. If something like that was done. I think that can be the main cause.