microsoft / microsoft/kiota-ruby
Conflict between microsoft_kiota_faraday (Kiota SDK) and Sidekiq 8.1 in Rails 8 app
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 8
- Avg merge
- 11h 9m
- Merged PRs (30d)
- 24
Description
Environment:
Ruby 3.4
Rails 8.1
Sidekiq 8.1
Trying to use Kiota SDK (microsoft_kiota_abstractions + microsoft_kiota_faraday + microsoft_kiota_authentication_oauth) for Microsoft Graph
Problem:
When adding the Kiota gems, Bundler fails with dependency conflicts (mainly in faraday, concurrent-ruby, or adapters), preventing the server or Sidekiq from booting.
Examples of typical errors observed:
Gem::ConflictError: unable to activate X (required by Kiota) because Y (required by Sidekiq 8.1) conflicts
Runtime errors related to thread-safety or multi-handle in Faraday
Attempts made:
bundle update
Downgrade Sidekiq to ~7.3 (works, but not ideal)
Lazy require of Kiota gems within the service (partially mitigates, but does not resolve global boot)
Impact:
Prevents the use of the official Kiota SDK in Rails 8 + Sidekiq 8.1 apps without downgrades or heavy workarounds.
Suggestion:
Check compatibility of Kiota gems with Sidekiq 8.x
Consider adding a Faraday version constraint or adapter to coexist with Sidekiq
Reproducible environment:
Rails 8.1 + Sidekiq 8.1 + gem 'microsoft_kiota_faraday'
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing Bundler resolution in the stated Ruby 3.4, Rails 8.1, and Sidekiq 8.1 environment with microsoft_kiota_faraday, then record the exact dependency or runtime conflict. Done means identifying a confirmed compatibility issue or dependency constraint that allows the Kiota gems and Sidekiq to boot together without downgrading Sidekiq.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100