Skip to content

Navigation Menu

Appearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

apify
apify-sdk-python

Repository navigation

Code
Issues (14)
Pull requests (6)
Discussions
Actions
Security and quality
Insights

feat: reattach named child runs after migration or resurrection - #1149

#1149

Open

vdusek wants to merge 5 commits into

masterapify/apify-sdk-python:masterfrom

feat/named-child-runsapify/apify-sdk-python:feat/named-child-runsCopy head branch name to clipboard

Conversation Commits5 (5)Checks Files changed

Open

feat: reattach named child runs after migration or resurrection#1149
vdusek wants to merge 5 commits into
masterfrom
feat/named-child-runs

Commits

Commits on Oct 6, 2026

feat: reattach named child runs after migration or resurrection
vdusek
committed
e6a3638
docs: mention missing recorded runs in the child run name docstring
vdusek
committed
ee91c8d
fix: share one child run registry across concurrent named starts
vdusek
committed
0925146
test: add e2e tests for named child runs
vdusek
committed
a841e9d
feat: reject a malformed child run registry and cover the remaining call paths
vdusek
committed
8e76335

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.