Skip to content

Navigation Menu

Appearance settings

View all features
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

deepset-ai / haystack Public

Notifications You must be signed in to change notification settings
Fork 3.2k
Star 26.6k

Code
Issues 96
Pull requests 58
Discussions
Actions
Projects
Security and quality 1
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security and quality
Insights

fix: keep pipeline snapshots reusable after resume - #13076

#13076

Draft

Afloat16 wants to merge 1 commit into

deepset-ai:maindeepset-ai/haystack:mainfrom

Afloat16:fix/pipeline-snapshot-replayAfloat16/haystack:fix/pipeline-snapshot-replayCopy head branch name to clipboard

Conversation Commits1 (1)Checks Files changed

Draft

fix: keep pipeline snapshots reusable after resume#13076
Afloat16 wants to merge 1 commit into
deepset-ai:mainfrom
Afloat16:fix/pipeline-snapshot-replay

fix: keep pipeline snapshots reusable after resume

4449a89

Select commit

Loading

Failed to load commit list.

Uh oh!

There was an error while loading. Please reload this page.

Sign in for the full log view

Linked issue review sync on: pull_request_target 1

sync

Handled internally PR guard on: pull_request_target 1

guard

Labeler on: pull_request_target 1

triage

Check API reference changes on: pull_request

First-time contributor PR limit on: pull_request_target 1

limit

PR flood guard on: pull_request_target 1

guard

Check Release Notes on: pull_request

Slow Integration Tests on: pull_request

Check Release Notes on: pull_request

CodeQL on: pull_request

ClusterFuzzLite PR fuzzing on: pull_request

Tests on: pull_request

Detect docstrings edit on: pull_request

Annotations

1 warning

.github/workflows/linked_issue_review.yml#L1

On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target

Job log options

Download log archive

This job was skipped

Loading

Re-running jobs...

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.