Skip to content
dotnet logo

.NET

.NET is a free, cross-platform, open source developer platform for building many different types of applications.

Here are 14,074 public repositories matching this topic...

ahsonkhan
ahsonkhan commented Sep 16, 2019

We can improve test coverage of certain branches within JsonElement (when it's backed by JsonNode):

Metric Value
Covered lines: 629
Uncovered lines: 13
Coverable lines: 642
Total lines: 2096
Line coverage: 97.9% (629 of 642)
Covered branches: 213
Total branches: 225
Branch coverage: 94.6% (213 of 225)

Edge cases while enumerating JSON objects and JSON a

react-native-windows
messani
messani commented Aug 30, 2019

Steps to Reproduce

  1. Code
using System;

namespace Test
{
  class MainClass
  {
    public static void Main(string[] args)
    {
      throw new Exception("blabla");
    }
  }
}
  1. Run:
    MONO_DEBUG=suspend-on-unhandled mono ./Test.exe

Current Behavior

Unhandled Exception:
System.Exception: blabla
at Test.MainClass.Main (System.String[] args) [0x000

sandersaares
sandersaares commented Mar 20, 2019

I was confused to find that my timeout policy was not throwing a TimeoutRejectedException on timeout.

static void Dingus(CancellationToken ct)
{
    Console.WriteLine($"It's 12 o'clock and all is well");

    // Just wait until cancelled.
    ct.WaitHandle.WaitOne();
}

It appears that using the optimistic strategy, it is necessary to actually throw `OperationCancelled

CESARDELATORRE
CESARDELATORRE commented Sep 6, 2019

As mentioned by Diego, these additions would help by simplifying the API usage for users even further and it should be pretty easy to implement for us: 👍

@divega commented: dotnet/machinelearning-samples#617 (review)

@CESARDELATORRE, I did a deferred review. The experience seems pretty good.

1:
And I agree with you that it could be even better

IdentityServer4
leastprivilege
leastprivilege commented Oct 9, 2019

We have to many quickstarts - and updating them for each release is just too much work. Relying on external help has not proven to be feasible.

I'd like to simplify them - along the lines or our new grant types guidance

core

  • Machine to Machine communication (aka client credentials)
  • ASP.NET Core authentication only (using code flow) + external authentication
  • ASP.NET Core authen
BenchmarkDotNet
simonech
simonech commented Jun 24, 2019

For each Job, it adds plots about density, cumulative mean, and so on. But two files are named BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--density.png and BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--facetDensity.png, with the -- instead of single. Like some iteration variable is empty (since later there are names with -Default-
![image](https://user-images.github

MartinCarpentier
MartinCarpentier commented Dec 29, 2018

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

mmillican
mmillican commented May 27, 2016

I'm attempting to use WMI monitoring in Opserver on a domain environment. Our sys-admin created a domain user which has permissions for WMI. At first, I tried setting the app pool to run as the specified domain user, but still wasn't seeing any data.

After poking around in the config classes, I updated my DashboardSettings.json WMI section to

"wmi": {
     "nodes": [ "web01", "web02", 
Styxxy
Styxxy commented Jan 30, 2018

From conversation in PR #368

Documentation should be updated how to use Windows Authentication to make API calls.

There are two options to solve this, create a HttpClient yourself, or set the clienthandlerfactory in the RefitSettings;

// Option 1 : create HttpClient yourself
var client1 = RestService.For<IMyService>(
    new HttpClient(new HttpClientHandler() { AllowAutoRedi
Aaronontheweb
Aaronontheweb commented Sep 26, 2019

Version: N/A

For users who are interested in using Akka.Persistence.Query, CQRS, EventSourcing, projections, and so forth - the only practical way to combine data from multiple persistent entities without knowing in advance what those entity IDs are is to use Akka.Persistence.Query's EventsByTag queries.

Unfortunately, if you start writing to Akka.Persistence without using any tags at all,

You can’t perform that action at this time.