etc. What is their use case? All of these tasks Read- and Write- counterparts receive
- identifier of the row to be read or written. In our experience there's no such scenario when you need just a single row from table. Even more: there's no way to find out the size of the table. So is anybody actually using these tasks in this specific implementation?
or using FlowRunner, without using an agent?
has been released and here are a few notable changes: 😛refect-duck:😛refect-duck: Nicer support for tasks with multiple results ⚠️ Improved logs and warnings ♻️ Cleaner flow-run restarts when using resource managers #️⃣ Squashed bug in flow-hashing for idempotency A big thank you to our contributors who helped out with this release! Full changelog:https://github.com/PrefectHQ/prefect/releases/tag/0.13.17
Mac Gréco Péralte Chéry
From November 20 docker introduced pull limits for images what cause me to have this error in Code build
build: commands: - python --version - pyenv global 3.7.7 - python --version - pip install $(grep -ivE "pywin32" requirements.txt) - prefect backend cloud - prefect auth login -t $PREFECT_ACCESS_TOKEN - aws ecr get-login-password --region us-east-2 | docker login --username AWS --password-stdin <http://xxxxxxxx.dkr.ecr.us-east-2.amazonaws.com|xxxxxxxx.dkr.ecr.us-east-2.amazonaws.com> - python3.7 flows/my_flow.py
When i go to the site i can read: "Anonymous free users will be limited to 100 pulls per six hours, and authenticated free users will be limited to 200 pulls per six hours." So i created a account on docker to raise my limits to 200 pull per 6 hours. So i understand the problem occurs when prefect is pulling the base prefect docker image to build my flow image because i have reached my 100 pulls / 6 hours anonymous limit My question is where should i put my docker account token to pull the prefect base image via my newly created docker account?
File "/root/.pyenv/versions/3.7.7/lib/python3.7/site-packages/prefect/environments/storage/docker.py", line 619, in pull_image output = client.pull(self.base_image, stream=True, decode=True) File "/root/.pyenv/versions/3.7.7/lib/python3.7/site-packages/docker/api/image.py", line 415, in pull self._raise_for_status(response) File "/root/.pyenv/versions/3.7.7/lib/python3.7/site-packages/docker/api/client.py", line 261, in _raise_for_status raise create_api_error_from_http_exception(e) File "/root/.pyenv/versions/3.7.7/lib/python3.7/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception raise cls(e, response=response, explanation=explanation) docker.errors.APIError: 500 Server Error: Internal Server Error ("toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: <https://www.docker.com/increase-rate-limit>")
it got this error message ( see thread) and, the log message said
Task 'init_run': Starting task run...
After that, All remaining tasks stuck in
Task 'init_run': Finished task run for task with final state: 'ClientFailed'
state for hours. Any ideas what happened? Maybe my flow need to know how to handle this