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

Getting tasks to be called from stream.py #1

Open
rmvanwyk opened this issue Oct 18, 2019 · 0 comments
Open

Getting tasks to be called from stream.py #1

rmvanwyk opened this issue Oct 18, 2019 · 0 comments

Comments

@rmvanwyk
Copy link

Hey Chris!

After our conversation I was still struggling to be able to call a task located in stream.py. I've messed around with it for a bit and traced it to the inconsistency in naming between "stream" and "stream_input". I'm not sure if this is due to the app name and queue names being different or what but after making the changes described below, I was able to start calling tasks from the "stream" microservice.

  1. stream.start => stream_input.start
    https://github.com/chodges15/uServicesCelery/blob/master/src/http_interface/http_interface.py#L47

  2. --app=stream.app => --app=stream_input.app
    https://github.com/chodges15/uServicesCelery/blob/master/docker-compose.yml#L20

  3. rename stream.py to stream_input.py

  4. app = Celery(”stream) => app = Celery(”stream_input”)
    https://github.com/chodges15/uServicesCelery/blob/master/src/stream_input/stream.py#L19

I know that 1, 2, & 3 need to be done together to actually get the service running, but I'm not convinced that #4 is necessary. Just wanted to document this for my own sanity sake and also for if you ever want to get that Start Stream button working!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant