| // Single-object route | |
| Route: /api/{plural of object}/{id} | |
| example: /api/people/8 | |
| Allowable methods: GET, PATCH, DELETE | |
| // successful response | |
| { | |
| "id": 8, | |
| "name": "Alex", |
I have been experimenting with tooling around how to keep track of dask issues and wanted to write down what I've been trying.
Subscribe to all the repositories in the dask org. Then if you go to https://github.com/notifications, you'll be notified when things change
Look for:
| name: pre-commit-ci | |
| on: | |
| pull_request: | |
| branches: | |
| - main | |
| jobs: | |
| pre-commit-ci: | |
| name: Lint changed backend files | |
| runs-on: ubuntu-latest | |
| steps: |
| import os | |
| from distributed import WorkerPlugin | |
| class UploadFile(WorkerPlugin): | |
| """A WorkerPlugin to upload a local file to workers. | |
| Parameters | |
| ---------- | |
| filepath: str | |
| A path to the file to upload |
SpatioTemporal Asset Catalog (STAC) is a community-built specification that aims to standardize how people find and interact with geospatial data.
Below are some of the most valuable features of STAC.
If your data is not findable it does not exist. You need to be able to find where it is and know what it is in order to use it. Cataloging data means that: