Skip to content

MAINT: enlarge timeout for cosmodc2 notebook #139

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Sep 26, 2025
Merged

MAINT: enlarge timeout for cosmodc2 notebook #139

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bec33d2
MAINT: enlarge timeout for cosmodc2 notebook
bsipocz Sep 23, 2025
9c18693
MAINT: more timeout as I just had a local run with 42mins
bsipocz Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions tutorials/cosmodc2/cosmoDC2_TAP_access.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ kernelspec:
display_name: Python 3 (ipykernel)
language: python
name: python3
execution:
timeout: 2600
---


Expand Down Expand Up @@ -79,8 +81,8 @@ result = service.run_async(adql)
result
```

The above query shows that there are 597,488,849 redshifts in this table.
Running ``count`` on an entire table is an expensive operation, therefore we ran it asynchronously to avoid any potential timeout issues.
The above query shows that there are 597,488,849 redshifts in this table.
Running ``count`` on an entire table is an expensive operation, therefore we ran it asynchronously to avoid any potential timeout issues.
To learn more about synchronous versus asynchronous PyVO queries please read the [relevant PyVO documentation](https://pyvo.readthedocs.io/en/latest/dal/index.html#synchronous-vs-asynchronous-query).

+++
Expand Down