[BUG] Publish failing with more than 3 apis and having huge specification

Open
#667 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, csharp
Domain
api, cloud

Research direction

No source file, test, or entry point is named. Reproduce publishing four or more APIs with large OpenAPI specifications and capture where the PessimisticConcurrencyConflict occurs; done means multi-API publishing succeeds reliably without requiring individual publishes.

Written by the indexing model from the issue text.

Description

Release version

v6.0.1.1

Describe the bug

Publish is failing with 4 apis and having huge specifications.
When we publish all 4 individually, they are publishing without any issues.

Expected behavior

Publish to be successful for any number of apis.

Actual behavior

Producing errors, randomly. Each run fails in different place
Content is '{"error":{"code":"PessimisticConcurrencyConflict","message":"Operation on the API is in progress","details":null}}'.

Reproduction Steps

Publish with 4 or more apis having huge opsn api specification

Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.