Skip to content

Navigation Menu

Sign inAppearance 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
  Accelerator
  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

Sign upAppearance 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

Uh oh!

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

JasperFx / wolverine Public

Notifications You must be signed in to change notification settings
Fork 362
Star 2.3k

Code
Issues 40
Pull requests 3
Discussions
Actions
Projects
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security and quality
Insights

GH-3519: Isolate agent start failures so one wedged agent doesn't skip its siblings - #3535

#3535

Merged

jeremydmiller merged 1 commit into

mainJasperFx/wolverine:mainfrom

fix/3519-isolate-agent-start-failuresJasperFx/wolverine:fix/3519-isolate-agent-start-failuresCopy head branch name to clipboard

Jul 20, 2026

Conversation Commits1 (1)Checks Files changed

Merged

GH-3519: Isolate agent start failures so one wedged agent doesn't skip its siblings#3535
jeremydmiller merged 1 commit into
mainfrom
fix/3519-isolate-agent-start-failures

GH-3519: isolate agent start failures so one wedged agent doesn't ski…

aedb454

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

command-line on: pull_request

describe-handlers-smoke

http on: pull_request

test

.NET on: pull_request

build

fsharp on: pull_request

fsharp-codegen-compile-gate

tests on: pull_request 23

CIAWSSqs

CIAWSSqsCompliance

CIAWSSns

CIAzureServiceBus

CICosmosDb

CIEfCore

CIGrpc

CIKafka

CIMarten

CIMQTT

CIMySql

CINATS

CIOracle

CIPersistence

CIPolecat

CIPolecatWorkflow

CIPolecatSagas

CIPubsub

CIPulsar

CIRabbitMQ

CIRavenDb

CIRedis

CISqlite

CISqlServer

CICircuitBreaking

CIAotSmoke

describe-handlers-smoke

succeeded Jul 20, 2026 in 45s

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.