microsoft/SWE-Sharp-Bench huggingface dataset:
Repository: restsharp/RestSharp

Issue:
IsSuccessful always false when using RestResponse<T>
When using the latest RestSharp version, the property `IsSuccessful` of `RestReponse<T>` is always `false`. When using `RestResponse`, `IsSuccessful` is set to `true` whenever the request was successful.

## Expected Behavior

The value of `IsSuccessful` does not depend on whether you use `RestResponse<T>` or `RestResponse`.

## Actual Behavior

The value of `IsSuccessful` does depend on whether you use `RestResponse<T>` or `RestResponse`.

## Steps to Reproduce the Problem

Code example:

```csharp
    public class Program
    {
        class GithubRepo
        {
            public int Id { get; set; }
            public string Name { get; set; }
        }

        public static async Task Main(string[] args)
        {
            var restClient = new RestClient("https://api.github.com/");
            var request = new RestRequest("repos/RestSharp/RestSharp", Method.Get);
            var response1 = await restClient.ExecuteAsync<GithubRepo>(request);
            var response2 = await restClient.ExecuteAsync(request);
            
            Console.WriteLine(response1.IsSuccessful);
            Console.WriteLine(response2.IsSuccessful);            
        }
    }
```

This outputs:

```
False
True
```

Using RestSharp 106, the result is
```
True
True
``` 

## Specifications

  - Version: 107.0.0.-preview.13
  - Platform: .NET Core 3.1 @ Ubuntu 
  - Subsystem:


Hints:

Patch:
diff --git a/src/RestSharp/Response/RestResponse.cs b/src/RestSharp/Response/RestResponse.cs
index dafd9b3d8..eed4b500d 100644
--- a/src/RestSharp/Response/RestResponse.cs
+++ b/src/RestSharp/Response/RestResponse.cs
@@ -42,6 +42,7 @@ public static RestResponse<T> FromResponse(RestResponse response)
             ErrorMessage      = response.ErrorMessage,
             ErrorException    = response.ErrorException,
             Headers           = response.Headers,
+            IsSuccessful      = response.IsSuccessful,
             ResponseStatus    = response.ResponseStatus,
             ResponseUri       = response.ResponseUri,
             Server            = response.Server,


Test patch:
diff --git a/test/RestSharp.IntegrationTests/StatusCodeTests.cs b/test/RestSharp.IntegrationTests/StatusCodeTests.cs
index ff035f47f..af4f44ed3 100644
--- a/test/RestSharp.IntegrationTests/StatusCodeTests.cs
+++ b/test/RestSharp.IntegrationTests/StatusCodeTests.cs
@@ -36,6 +36,7 @@ public async Task ContentType_Additional_Information() {
         var response = await _client.ExecuteAsync<TestResponse>(request);
 
         response.StatusCode.Should().Be(HttpStatusCode.OK);
+        response.IsSuccessful.Should().BeTrue();
     }
 
     [Fact]
Repository: serilog/serilog

Issue:
Consider using `Major.0.0.0` or `Major.Minor.0.0` assembly versioning
Since Serilog 4.0.0 uses an assembly version 4.0.0.0, we've still got some wiggle-room to tweak the assembly versioning policy. Because new features _do_ cause issues when assembly versions are mismatched, `Major.Minor.0.0` is the most general versioning scheme that is likely to work for us.

See also #2073 and https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/versioning.


Hints:

Patch:
diff --git a/src/Serilog/Serilog.csproj b/src/Serilog/Serilog.csproj
index cafe30469..8a5a3d4f8 100644
--- a/src/Serilog/Serilog.csproj
+++ b/src/Serilog/Serilog.csproj
@@ -2,6 +2,7 @@
   <PropertyGroup>
     <Description>Simple .NET logging with fully-structured events</Description>
     <VersionPrefix>4.0.1</VersionPrefix>
+    <AssemblyVersion>$(VersionPrefix.Substring(0, 3)).0.0</AssemblyVersion>
     <Authors>Serilog Contributors</Authors>
     <!-- .NET Framework version targeting is frozen at these two TFMs. -->
     <TargetFrameworks Condition=" '$(OS)' == 'Windows_NT'">net471;net462</TargetFrameworks>


Test patch:
diff --git a/test/Serilog.Tests/MethodOverloadConventionTests.cs b/test/Serilog.Tests/MethodOverloadConventionTests.cs
index a2fedb014..9e2d1750b 100644
--- a/test/Serilog.Tests/MethodOverloadConventionTests.cs
+++ b/test/Serilog.Tests/MethodOverloadConventionTests.cs
@@ -35,7 +35,7 @@ public class MethodOverloadConventionTests
     /// </para>
     ///
     /// <para>
-    /// A similar <see cref="ReadOnlySpan{T}"/> accepting method does not exists in the <see cref="ILogger"/> interface,
+    /// A similar <see cref="ReadOnlySpan{T}"/> accepting method does not exist in the <see cref="ILogger"/> interface,
     /// and introducing it is a breaking change.
     /// </para>
     /// </remarks>
diff --git a/test/Serilog.Tests/VersioningTests.cs b/test/Serilog.Tests/VersioningTests.cs
new file mode 100644
index 000000000..fe5c88e5e
--- /dev/null
+++ b/test/Serilog.Tests/VersioningTests.cs
@@ -0,0 +1,20 @@
+namespace Serilog.Tests;
+
+public class VersioningTests
+{
+    [Fact]
+    public void AssemblyIsExplicitlyVersioned()
+    {
+        var version = typeof(Log).Assembly.GetName().Version;
+        Assert.NotNull(version);
+        Assert.False(version.Major is 0 or 1);
+    }
+
+    [Fact]
+    public void AssemblySubordinateVersionPartsAreZero()
+    {
+        var version = typeof(Log).Assembly.GetName().Version;
+        Assert.True(version?.Build is 0);
+        Assert.True(version.Revision is 0);
+    }
+}
\ No newline at end of file
Repository: serilog/serilog

Issue:
JsonFormatter RenderedMessage writes invalid output
**Description**
When using JsonFormatter with renderMessage enabled to write console output, the JSON output is not created correctly and results in invalid JSON.

**Reproduction**
1. Configure a default logger with a sinkConfiguration that uses the JsonFormatter with renderMessage = true
2. Log a message
3. The output results in invalid quoted JSON at the renderedMessage with an extra quote, for example:

`{
    "Timestamp": "2023-06-21T09:48:56.0952245+02:00",
    "Level": "Error",
    "MessageTemplate": "Testmessage with value: {TestMessageValue}"",
    "RenderedMessage": "Testmessage with value: 1",
    "Properties": {
        "TestMessageValue": "1"
    }
}`

**Expected behavior**
Using Serilog 2.12.0 the output would result in valid JSON, we would expect the same behaviour in the latest version.

**Relevant package, tooling and runtime versions**
Serilog 3.0.0

**Additional context**
Code where the extra quote is added can be found here:
https://github.com/serilog/serilog/blob/main/src/Serilog/Formatting/Json/JsonFormatter.cs#L69



Hints:

Patch:
diff --git a/src/Serilog/Formatting/Json/JsonFormatter.cs b/src/Serilog/Formatting/Json/JsonFormatter.cs
index 3ea6b3836..fab5e95e7 100644
--- a/src/Serilog/Formatting/Json/JsonFormatter.cs
+++ b/src/Serilog/Formatting/Json/JsonFormatter.cs
@@ -66,7 +66,7 @@ public void Format(LogEvent logEvent, TextWriter output)
 
         if (_renderMessage)
         {
-            output.Write("\",\"RenderedMessage\":");
+            output.Write(",\"RenderedMessage\":");
             var message = logEvent.MessageTemplate.Render(logEvent.Properties);
             JsonValueFormatter.WriteQuotedJsonString(message, output);
         }


Test patch:
diff --git a/test/Serilog.Tests/Formatting/Json/JsonFormatterTests.cs b/test/Serilog.Tests/Formatting/Json/JsonFormatterTests.cs
index 39c76d285..006255a34 100644
--- a/test/Serilog.Tests/Formatting/Json/JsonFormatterTests.cs
+++ b/test/Serilog.Tests/Formatting/Json/JsonFormatterTests.cs
@@ -274,4 +274,20 @@ public void SequencesOfSequencesAreSerialized()
         var h = (string)d.Properties.AProperty[0][0];
         Assert.Equal("Hello", h);
     }
+
+    [Fact] // See https://github.com/serilog/serilog/issues/1924
+    public void RenderedMessageIsIncludedCorrectlyWhenRequired()
+    {
+        var p = new MessageTemplateParser();
+        var e = new LogEvent(Some.OffsetInstant(), Information, null,
+            p.Parse("value: {AProperty}"), new[] { new LogEventProperty("AProperty", new ScalarValue(12)) });
+
+        var formatter = new JsonFormatter(renderMessage: true);
+
+        var buffer = new StringWriter();
+        formatter.Format(e, buffer);
+        var json = buffer.ToString();
+
+        Assert.Contains(@",""MessageTemplate"":""value: {AProperty}"",""RenderedMessage"":""value: 12"",", json);
+    }
 }