Expected Behavior / New Feature

Support sticky sessions for ServiceDiscoveryProviders

Actual Behavior / Motivation for New Feature

When using websockets with ocelot in a distributed system, problem can arise since ocelot, as far as i know, doesn't support sticky sessions when working with service discovery providers.

The functionality could be great if it could work with both consul

Is your feature request related to a problem? Please describe.

Similar to OrchardCMS/OrchardCore#11200 this is about making the built-in setup recipes lightweight: Lucene is a feature that you don't need on every site, especially that due to it storing files on the local file system that need to be preserved (i.e. not temp files) it needs special considerations for h

Improve the tier prices feature - add info like "Buy 2 in x.xx$ and save x%"

Bug Report

Currently, the SDK allows LogRecord options to be changed after the object was being built by the LoggerFactory.
This could introduce unnecessary complexity toward different states (before/after options got updated) and making it harder to maintain.

Discussion: open-telemetry/opentelemetry-dotnet#2891 (comment)

**What is the expected behav

The <post-read-time /> TagHelper is used to calculate the number of minutes we guess it will take to read the article. This calculation uses a simple arithmetic around the number of words Post.Content.

There is a hypothesis that suggests we should also include 30 seconds per image in the post.

The task here is to find the number of images in Post.Content and add it to the number