-
Notifications
You must be signed in to change notification settings - Fork 202
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
Dapr List doesn't find my running Daprd + Scheduler processes && Unable to test Dapr Init changes for Scheduler #1406
Comments
Looks like dapr init with scheduler is required for 1.14, but is not the scheduler apis. Will come back to the apis after 1.14, but I still need input on |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
I am trying to test the CLI code locally for Scheduler changes. This has proved to not be as simple as I had hoped for. I am looking for suggestions on ways around my blockers, as this change is required for this release.
Currently, I am running into 2 issues that are preventing my scheduler cli work from being tested.
./dist/darwin_arm64/release/dapr list
to find my running daprd + scheduler. I have tried running them inside docker and separately by running the binaries. This is a blocker, as I am unable to test my./dist/darwin_arm64/release/dapr job schedule --name=cassie --schedule="@hourly" --app-id=sub
command bc the cli cant find my running instances./dist/darwin_arm64/release/dapr init
to verify if it will successfully create my scheduler upon adapr init
. My understanding is that scheduler should be deployed as default, for users to use as they would like, but will be an explicit opt in feature for reminders. Therefore, I need to be able to test my changes such that I can see if scheduler is created with adapr init
. The problem is that scheduler isn't in master in dapr, I have it all locally but can't find a way to test it without an rc of the image bundle.Steps to repro:
Checkout my dapr branch w/ scheduler in it: dapr/dapr#7716
from
cmd/scheduler
run:go build -tags=allcomponents -v
&&./scheduler
from
cmd/daprd
run:go build -tags=allcomponents -v
&&./daprd --app-id=sub --scheduler-host-address=localhost:50006 --dapr-grpc-port=3501 --metrics-port=9091
from cli directory: checkout my branch: #1405 (I opened as a draft PR for ease of getting assistance on this)
run
make build
run
./dist/darwin_arm64/release/dapr list
where it doesn't find my running daprd or schedulerrun
./dist/darwin_arm64/release/dapr job schedule --name=cassie --schedule="@hourly" --app-id=sub
where it still can't find my instancesThings I've tried:
I tried running both in docker as well with:
But
./dist/darwin_arm64/release/dapr list
was still unable to find my instances. Same if I run them in my IDE, the cli cant find the processesI have tried setting that
--image-registry
flag on thedapr init
as well, but still face the same issue.The text was updated successfully, but these errors were encountered: