Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

flyteorg / flytekit Public

Notifications You must be signed in to change notification settings
Fork 305
Star 255

Code
Pull requests 162
Actions
Security
Insights

Additional navigation options

Code
Pull requests
Actions
Security
Insights

Fix: Make sure decks created in elastic task workers are transferred to parent process#1837

Merged

fg91 merged 4 commits intomasterflyteorg/flytekit:masterfrom fg91/fix/elastic-plugin-deckflyteorg/flytekit:fg91/fix/elastic-plugin-deckCopy head branch name to clipboard

Sep 19, 2023

+68-6

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Sep 18, 2023

Transfer decks created in the worker process to the parent process
fg91
committed
Add test for decks in elastic tasks
fg91
committed
Update plugins/flytekit-kf-pytorch/flytekitplugins/kfpytorch/task.py
fg91
committed
Update plugins/flytekit-kf-pytorch/flytekitplugins/kfpytorch/task.py
fg91
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.