Release notes for Optimizely updates

Steps To Reproduce

1. Create a console application and add the Episerver Social comments NuGet package to the project.
2. Define a filter to retrieve a page of comments from Episerver Social using the CommentService.
3. Issue the request and notice that it returns successfully.
4. Update the application to set the culture of the current thread to "tr-TR" prior to issuing the request to Episerver Social.
5. An AuthenticationException occurs.

Expected

• The request successfully authenticates and returns a page of comments.

Actual

• An AuthenticationException occurs.

An exception occurs when a client requests a page of results (any feature) with a size of int.MaxValue.

On the client this exception appears as:

EPiServer.Social.Common.SocialException: An error occurred while processing the request
   at EPiServer.Social.Common.Rest.ResponseMessageHandler.<UnexpectedError>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at EPiServer.Social.Common.Rest.ResponseMessageHandler.<HandleUnsuccessful>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at EPiServer.Social.Comments.Rest.CommentResponseMessageHandler.<HandleUnsuccessful>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at EPiServer.Social.Comments.Rest.CommentResponseMessageHandler.<HandleGetByCriteria>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at EPiServer.Social.Comments.Rest.HttpCommentRepository.<GetAsync>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at EPiServer.Social.Comments.CommentService.Get(Criteria`1 criteria)
   at UseaConnectivity.Program.Main(String[] args) in C:\Users\chba\documents\visual studio 2015\Projects\UseaConnectivity\UseaConnectivity\Program.cs:line 31

Steps to reproduce

1. Create an application that requests Social content (for example, comments) with a page size of int.MaxValue. (Sample code below)

            try
            {
                var criteria = new Criteria<CommentFilter>
                {
                    PageInfo = new PageInfo { PageSize = int.MaxValue }
                };
 
                var pageOfComments = commentService.Get(criteria);
 
                Console.WriteLine(pageOfComments.Results.Count());
            }
            catch (Exception ex)
            {
                Console.Error.WriteLine(ex);
            }

2. Notice the exception that occurs.

Workaround

• As a workaround, a page size of int.MaxValue - 1 can be requested instead.

Fix

The fix for this issue is a server side change. No client update is necessary.

This change adds support for CMS 11 to the Episerver Social framework packages.

Production usage is demonstrating occasional long request times when activities are added. This does not have an obvious impact on the client, since these requests occur in the background, however the requests are taking 15-25 seconds to complete on the back end.

To date, the issue has not occurred frequently but it has happened on multiple occasions. A sample taken from a recent EMEA alert can be found below.

serviceName="fabric:/EPiServer.Social.Cloud.ActivityStreams.Application/Host" serviceTypeName="HostType" replicaOrInstanceId="131438386567417851" partitionId="4c819f26-d963-43d3-be09-f9844168291a" applicationName="fabric:/EPiServer.Social.Cloud.ActivityStreams.Application" applicationTypeName="EPiServer.Social.Cloud.ActivityStreams.ApplicationType" nodeName="_epso-emea-scaleset-wtsaiuhym_2" tenantId="xxxxxxxxxxxxxxxxxxxxxxxxxxx" loggerId="e3bac210-67f6-4b7f-9c78-178f0ff175da" calledMethod="IFeedItemRepository:AddAsync(Activity, Extension)" calledMethodStartTime="12:06:54 PM" calledMethodDurationTimeMsec="15062.826900"

The issue occurs when activities are added in scenarios with an exceptionally high volume of subscribers.

Note: This behavior is not observable from the client side. The processing impact is incurred within the cloud.

Steps to reproduce:

1. Populate a Social instance with > 1 million subscriptions for a single target.
2. Using the Social client APIs, publish an activity for that target.
3. Monitor the time elapsed to complete feed item generation for the activity.
4. Notice that the time to process the activity is unnecessarily long.

A developer portal for provisioning trial instances of Episerver Social is now available: https://demo.social.episerver.net.

Adds an "Any" expression, which filters content when a field contains at least one of the values specified in a collection.

• If the field identified in the expression contains a single value, the "Any" expression selects all content where the field's value is present in the specified collection.
• If the field identified in the expression contains an array of values, the "Any" expression selects all content where at least one of the value's in the field's array is present in the specified collection.

Adds an OrExpression to the Episerver Social expression library, providing access to a logical OR operator in the definition of filters for retrieving social content.

Internal enhancements improving performance when filtering for Composite social content.

Adds a Mean property to the RatingStatistics class, which provides the mean rating value for target. This value is calculated as the sum of all ratings for the target divided by the total count of ratings for the target.

Queries for RatingStatistics can also be sorted be sorted by this value.

The SocialAuthenticationException has been enhanced with supporting information to aid in the troubleshooting of any unexpected failure to authenticate with Episerver Social.