text:
Add support for loading environment variables from a .env file

Is your feature request related to a problem? Please describe.
Currently environment variables must exist on process.env before running the codegen cli

I'd like to be able to load and reference variables defined in a .env file in the codegen.yml file
Describe the solution you'd like

Using dotenv to either load a .env file if it exists or a cli flag to do so
Describe alternatives you've considered

Using the programmatic approach

Additional context

@jflewis We support require extensions, so I think you should be able to do: require: dotenv/config in your codegen.yml and it will work.

@dotansimha Sorry for the late response, haven't had an opportunity to take a look at this.
It seems that this doesn't exactly work. While the require: dotenv/config does load the .env file (which is great news), this action is happening after the parsing of the YML. So I am unable to use .env in combination with ENV variables in the yml.

@jefflewis Ohh I see, it makes sense, because in order to get require values, we need to load the yml file. Keeping open, we'll try to find a solution for it soon.

@jflewis

It's very ugly but it'd be workaround until this issue fixed.
$ node --require dotenv/config ./node_modules/.bin/graphql-codegen --config codegen.yml

I think that allowing to specify -r to the codegen should do the trick (just like we can set watch from the cli but also from the config file).
This way, if you need something to get loaded before the codegen reads the yml, you can use -r and we'll make sure to load it before.

Implemented in: https://github.com/dotansimha/graphql-code-generator/pull/2016

Available in 1.3.0 🎉

Stopped working after upgrading to 1.8.1

@lednhatkhanh I guess 1.8.0 doesn't work as well?
@kamilkisiela can you please take a look? maybe it's related to cosmiconfig?

@lednhatkhanh it seems like loading env vars works, can you please share a reproduction in a new issue?

Stopped working after upgrading to 1.8.1

happened to me as well.
it seems like env vars aren't loaded in the yml file even though i'm using --require dotenv/config

@dotansimha Just checked again and it's not working, using -r dotenv/config and the env variables do not get loaded

Thanks, I created a new issue to track this: https://github.com/dotansimha/graphql-code-generator/issues/2722

@lednhatkhanh @cnt0705
Fixed in: https://github.com/dotansimha/graphql-code-generator/pull/2758
Alpha available: 1.8.2-alpha-c7249947.43

@dotansimha I upgraded to the latest @graphql-codegen/cli (1.17.10).
Passing this options used to work in 1.12.1
graphql-codegen -r dotenv/config dotenv_config_path=../../.env

But in 1.17.10 I'm seeing this error:
Cannot find module 'dotenv_config_path=../../.env'

Any input would be greatly appreciated

@johnnyBira 1.12 is pretty old. I'm not sure i'm able to compare that.
You can use DOTENV_CONFIG_PATH env var for that

Can you direct me to the docs please? @dotansimha

@johnnyBira
dotenv supports setting configuration via environment variables (see https://github.com/motdotla/dotenv#preload), so instead of using a CLI flag for codegen, you can just set an environment variables that will effect dotenv directly.

This makes sense. Thanks for taking the time explaining @dotansimha

How can I use another env file like .env.local

@Dav3rs
DOTENV_CONFIG_PATH=.env.local graphql-codegen -r dotenv/config

nv/config

This does not work on windows though

You can use cross-env to use that kind of env var definition(not related to codegen but npm scripts in general);
cross-env DOTENV_CONFIG_PATH=.env.local graphql-codegen -r dotenv/config

@ardatan Thanks, already figured that out

@ardatan Thanks, already figured that out

According to the example provided by the documentation for the --require flag first you have to indicate the config file location with the --config flag and then you can use the dotenv cli options.
Ex.
graphql-codegen --require dotenv/config --config ./codegen.yml dotenv_config_path=./.env.development.local

I'm currently working on Windows 11.

If anyone need to load .env variables for codegen.ts in a nextJS project I just want to place a solution here:
/* eslint-disable @typescript-eslint/ban-ts-comment */
/* eslint-disable no-process-env */
import { CodegenConfig } from "@graphql-codegen/cli";
import { loadEnvConfig } from "@next/env";

// @ts-ignore
loadEnvConfig(process.cwd());

const variable = process.env.VARIABLE;

This way you will utilize the @next/env package to load any variables from the .env file used for the NextJS project

For anyone coming across this in 2023 and getting lost in the comments, this is what I had to do make it work in the command line:
codegen.yml:
schema:
  - https://graphql.myapi.com:
      headers:
        Authorization: ${API_TOKEN} # NOT {process.env.API_TOKEN}
documents: './src/graphql/**/*.graphql'
# [...] snipped

.env
API_TOKEN=ABCDEF123467890

Command:
graphql-codegen --require dotenv/config

If anyone need to load .env variables for codegen.ts in a nextJS project I just want to place a solution here:
/* eslint-disable @typescript-eslint/ban-ts-comment */
/* eslint-disable no-process-env */
import { CodegenConfig } from "@graphql-codegen/cli";
import { loadEnvConfig } from "@next/env";

// @ts-ignore
loadEnvConfig(process.cwd());

const variable = process.env.VARIABLE;

This way you will utilize the @next/env package to load any variables from the .env file used for the NextJS project

How to do this for a React-Vite project?

authors: DGVIP Dav3rs LarsEjaas arcataroger ardatan cnt0705 dotansimha jefflewis jflewis johnnyBira lednhatkhanh mecirmartin mislavlukach nwazuo otofu-square


text:
@oneOf support broken with interfaces

Issue workflow progress
Progress of the issue based on the Contributor Workflow

[x] 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.
Please make sure the Codegen and plugins version under package.json matches yours.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug

To Reproduce
Steps to reproduce the behavior:
Here's a sandbox showing the broken output:
https://codesandbox.io/s/kind-proskuriakova-h2i4te?file=/types.ts

My GraphQL schema:

directive @oneOf on INPUT_OBJECT

input IntFilterInput @oneOf {
  eq: Int
  ne: Int
  gt: Int
  gte: Int
  lt: Int
  lte: Int
  in: [Int]
}

My codegen.yml config file:

schema: schema.graphql
generates:
  types.ts:
    config:
      declarationKind: interface
    plugins:
      - typescript

Expected behavior
To don't generate invalid TypeScript code.
More specifically either override the interface setting and use type or fall back to no special @oneOf handling.
Environment:

@graphql-codegen/typescript: 2.4.2

@n1ru4l Since I'm quite busy with other things right now, I hope the linked CodeSandbox above is enough for now.
I'll see what I can do if I have a free minute.

I've suggested a fix in #8586

source: gharchive/issue

repo: dotansimha/graphql-code-generator

license: MIT

license_type: permissive

license_source: github-api


text:
增加一个 DoH 接口用于返回 DWeb Records

比如这是 ETH.LIMO 项目为 .eth 维护的 DoH 服务器：
https://dns.eth.limo/dns-query
如果发起一个这样的请求：
curl --http2 -H "accept: application/dns-json" "https://dns.eth.limo/dns-query?name=vitalik.eth"

就可以拿到这样的一个结果：
{
  "Status": "0",
  "RD": false,
  "RA": false,
  "AD": false,
  "CD": false,
  "TC": false,
  "Question": [
    {
      "type": 16,
      "name": "vitalik.eth"
    }
  ],
  "Answer": [
    {
      "type": 16,
      "name": "vitalik.eth",
      "data": "dnslink=/ipfs/QmWxRwMg3bHyJxfAuPnUky2yNgNt51qmZqC99Ffenjxa94/",
      "ttl": 600
    }
  ]
}

如果 .bit 的 Indexer HTTP Server 上也有这样的一个可以把 DWeb Record 返回为 TXT DNSLink 的服务器，那么把这个服务器配置进 Kubo，Kubo 就可以实现用 IPFS Gateway 解析和访问 .bit 上的 IPFS DWeb 网站。
相关文档：
https://blog.v2ex.com/EA7C9A0D-133C-4416-9C55-919AB7350FCC/

比如 V2EX 的 IPFS Gateway 上配置了 .eth 的 DoH 服务器之后，就可以支持这样的效果：
https://ipfs.v2ex.pro/ipns/olivida.eth/

增加 DoH 接口还可以给 Kubo 提 PR，合并进去的话，也会吸引到更多的社区支持。

非常好的提议，目前也在排期中。当然，如果有开发者感兴趣也可以给我们提 PR。

看到这个 issue 被标记为 completed 了，是这个功能现在已经有了吗？

authors: livid paicha scorpiotzh

repo: dotbitHQ/das-account-indexer


text:
Blazor data binding doc needs a parameter

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/data-binding.md?plain=1#L162
The above line needs to be changed to:
private void Set(string value) {}

The missing parameter is causing the following errors:
...\Microsoft.NET.Sdk.Razor.SourceGenerators\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Pages_BindTest_razor.g.cs(306,240,306,243): error CS1503: Argument 1: cannot convert from 'method group' to 'Func<string, Task>'
...\Microsoft.NET.Sdk.Razor.SourceGenerators\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Pages_BindTest_razor.g.cs(350,420,350,423): error CS1503: Argument 2: cannot convert from 'method group' to 'Action<string>'

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b211df59-e1c9-86c0-c904-31fa3c361e6d
Version Independent ID: 3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Content: ASP.NET Core Blazor data binding
Content Source: aspnetcore/blazor/components/data-binding.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @toddlucas ... I'll take a look at this.

This came over from Javier's sample. Let see if I can find that ..........

Interesting ...... he doesn't have it here in his sample app ......
https://github.com/javiercn/BindGetSetAfter701/blob/main/BindGetSetAfter701/Client/Pages/Index.razor#L45
Let me get back to this in the morning. I drove seven hours yesterday 🚗 from Pensacola to Cocoa Beach to look at a house that I'm interested in buying, and I just drove seven hours back 😩. I'm ToAsT 💀. I'll take a closer look and get back to you tomorrow on this.

The following makes more sense to me ...
@page "/bind-get-set"
@using Microsoft.AspNetCore.Components.Forms

Bind Get Set Examples

Elements

<input type="text" @bind:get="text1" @bind:set="(value) => { text1 = value; }" /> @text1

<input type="text" @bind:get="text2" @bind:set="SetAsync1" /> @text2

Components

<InputText @bind-Value:get="text3" @bind-Value:set="(value) => { text3 = value; }" /> @text3

<InputText @bind-Value:get="text4" @bind-Value:set="SetAsync2" /> @text4

@code {
    private string text1 = "";
    private string text2 = "";
    private string text3 = "";
    private string text4 = "";

    private Task SetAsync1(string value)
    {
        text2 = value;
        return Task.CompletedTask;
    }

    private Task SetAsync2(string value)
    {
        text4 = value;
        return Task.CompletedTask;
    }
}

🤔 This one looks good. It makes the same point with less code ...
@page "/bind-get-set"
@using Microsoft.AspNetCore.Components.Forms

Bind Get Set Examples

Elements

<input type="text" @bind:get="text"
    @bind:set="(value) => { text = value; }" />

<input type="text" @bind:get="text" @bind:set="SetAsync1" />

Components

<InputText @bind-Value:get="text"
    @bind-Value:set="(value) => { text = value; }" />

<InputText @bind-Value:get="text" @bind-Value:set="SetAsync2" />

@code {
    private string text = "";

    private Task SetAsync1(string value)
    {
        text = value;
        return Task.CompletedTask;
    }

    private Task SetAsync2(string value)
    {
        text = value;
        return Task.CompletedTask;
    }
}

Those weren't good. I'll take your approach to maintain the sync Set method, but I'll have them update the value of text ...
@page "/bind-get-set-original"
@using Microsoft.AspNetCore.Components.Forms

Bind Get Set Examples

Elements

<input type="text" @bind:get="text" @bind:set="(value) => { text = value; }" />
<input type="text" @bind:get="text" @bind:set="Set" />
<input type="text" @bind:get="text" @bind:set="SetAsync" />

Components

<InputText @bind-Value:get="text" @bind-Value:set="(value) => { text = value; }" />
<InputText @bind-Value:get="text" @bind-Value:set="Set" />
<InputText @bind-Value:get="text" @bind-Value:set="SetAsync" />

@code {
    private string text = "";

    private void Set(string value)
    {
        text = value;
    }

    private Task SetAsync(string value)
    {
        text = value;
        return Task.CompletedTask;
    }
}

authors: guardrex toddlucas


text:
Add a link to EFCore.NamingConventions

https://github.com/efcore/EFCore.NamingConventions

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8875eb79-99ff-662b-c189-86eb8cdb5488
Version Independent ID: fa03a7fa-1922-7aa1-acda-b0d216ef37cb
Content: Tools & Extensions - EF Core
Content Source: entity-framework/core/extensions/index.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @ErikEJ
Microsoft Alias: avickers

/cc @roji

Resolved by #2272

authors: AndriySvyryd ajcvickers bricelam


text:
Please specify where those code snippets should be placed

Can you please specify where those example code snippets should be used

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fc418ab9-0592-f610-e751-40cb501220da
Version Independent ID: 822e8923-2647-f573-0c74-66af903776d8
Content: Data Seeding - EF Core
Content Source: entity-framework/core/modeling/data-seeding.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @AndriySvyryd
Microsoft Alias: avickers

The docs have this above the code snippets:

As an example, this will configure seed data for a Blog in OnModelCreating:

Is that not sufficient?

Also, below the snippets there's a link to the full sample project

authors: AndriySvyryd roji shamyratpashiyev96


text:
subscribing qos is 0, but receive retained msg qos is 2

Describe the bug
My mqtt Server has some reatined message with qos 2.
The server return retained message with qos 2 after client subscribe with qos 0.
Which component is your bug related to?

Server (MQTTnet 4.1.2.350)

To Reproduce

Publish some msg with qos is 2 and retained.
Subscribe with qos is 0

Expected behavior
Receive retained msg with the qos as the same with subscription.
Code example
I use 3.1.2 is fine, but it get fault when i upgrade to 4.x.
I found 3.1.2 code bellow, it will overwrite before publishing retained msg.
//MQTTnet 3.1.2
async Task<MqttPublishPacket> CreatePublishPacket(MqttQueuedApplicationMessage queuedApplicationMessage)
{
    var publishPacket = _channelAdapter.PacketFormatterAdapter.DataConverter.CreatePublishPacket(queuedApplicationMessage.ApplicationMessage);
    //Use the qos of subscription
    publishPacket.QualityOfServiceLevel = queuedApplicationMessage.SubscriptionQualityOfServiceLevel;

    //...(ignored)

    return publishPacket;

Thank you.

This will be released in version 4.1.3.x.

repo: dotnet/MQTTnet


text:
SqlConnection.Open() lock forever unde linux (Pi4+Raspbian Buster)

Similar problem to:
https://github.com/dotnet/corefx/issues/30961#issue-339998608
SqlConnection.Open() will lock forever and never return.
This problem happens with 3.0 preview6 (but also with v2.2.x project) on a Rpi4 (2gb) with Buster Linux installed.
No issue on rpi3/3+ with stretch installed, it works fine.
Sql.Data.Client.dll is 3.0.0-preview6-19303
Note: connection to Sql Server 2014

Hi @dobova86,
I'm not sure if this problem is coming from the driver's end, with the Rpi4 and Raspbian Buster being very recent releases. Could you try redirecting this issue to Raspbian team instead?

I will try to inform Raspbian Buster group.
I've no clue at the moment about the issue, but seems related to some Buster network low-end problem.

Hi @dobova86
I will close the issue for now.
If you need further assistance, please feel free to reopen or create a new issue.

Just for your info, this bug is still present in preview8 on debian buster, but at the moment no more info or solution.

authors: cheenamalhotra dobova86 peterbae

repo: dotnet/SqlClient


text:
Include net8.0 in ExtUtilities and TestUtilities

Fixes Kerberos pipeline errors (tracked internally)

Not needed anymore

source: gharchive/pull-request


text:
Write dashboard logs to disk

If an end user sees a dashboard error, they don't have a straightforward way to see more information themselves or provide information to us.
The dashboard should write logs to disk somewhere. Logs should be rolling, size limited, warning level (or info?) and above.
If an end user has a problem with the dashboard, we can ask them to provide logs.

@JamesNK  what package will we be using for logging?

Probably serialog. However, there was pushback on doing this. I don't think it will happen in GA.

Moving to backlog. We're going to log to the apphost console for p6 like we do with DCP logs.

authors: JamesNK davidfowl kvenkatrajan

repo: dotnet/aspire


text:
Add support for optionally generating a settings file

Background and Motivation

There are various scenarios where it's useful to be able to launch a project in the "normal way", outside of Aspire launching it, but still have that project be configured with the right Aspire settings in order to connect to Aspire services and the Aspire OpenTelemetry dashboard.
Scenarios include:

MAUI and other .NET Mobile projects (e.g. Uno) where there may not be support initially for an integrated launch experience
MAUI and other .NET Mobile projects (e.g. Uno) when there is support for an integrated launch experience, but users still want the ability to launch outside of Aspire to support the typical inner loop scenario here https://twitter.com/GFlisch4u/status/1811635668327539021, just restarting MAUI app via Shift-F5 / F5 in VS
Client apps that are launched by some other program, a service, with custom CLI args from the command line, etc.
Web apps where the user wishes to set the web app as the startup project and still have that work

This API meets that need, by allowing the settings, normally passed via environment variables, to optionally be written to a settings file (e.g. a JSON file). Writing the settings file can happen in addition to building/launching the project normally, allowing both Aspire integrated and standalone startup to work, or it be the only option, with Aspire configured to not build/launch the project, just generate settings. The API here supports both use cases.
Proposed API
namespace Aspire.Hosting;

public static class ProjectResourceBuilderExtensions
{
+     /// <summary>
+    /// Adds a settings file to the project resource, to optionally persist settings that are normally set via environment variables.
+    /// The settings file can be generated with or without also launching the project.
+    /// </summary>
+    /// <param name="builder">The <see cref="IDistributedApplicationBuilder"/>.</param>
+    /// <param name="settingsFilePath">The path to settings file, absolute or relative to app host directory.</param>
+    /// <param name="settingsFileType">The settings file type, C# code (for use with IConfigurationBuilder.AddInMemoryCollection) or JSON (for use with IConfigurationBuilder.AddJsonFile).</param>
+    /// <param name="onlyGenerateSettings">Indicate whether to skip build/running this resource, only generating settings.</param>
+    public static IResourceBuilder<ProjectResource> WithSettingsFile(this IResourceBuilder<ProjectResource> builder, string settingsFilePath, SettingsFileType settingsFileType, bool onlyGenerateSettings)

+    /// <summary>
+    /// Adds a settings file to the project resource, to optionally persist settings that are normally set via environment variables.
+    /// The settings file can be generated with or without also launching the project.
+    /// </summary>
+    /// <param name="builder">The <see cref="IDistributedApplicationBuilder"/>.</param>
+    /// <param name="settingsFileOptions">The options to use for settings file generation.</param>
+    /// <returns></returns>
+    public static IResourceBuilder<ProjectResource> WithSettingsFile(this IResourceBuilder<ProjectResource> builder, SettingsFileOptions settingsFileOptions)

+    /// <summary>
+    /// Adds a .NET project to the application model, just generating a settings file for the project.
+    /// </summary>
+    /// <param name="builder">The <see cref="IDistributedApplicationBuilder"/>.</param>
+    /// <param name="name">The name of the resource. This name will be used for service discovery when referenced in a dependency.</param>
+    /// <returns>A reference to the <see cref="IResourceBuilder{T}"/>.</returns>
+    /// <remarks>
+    /// <para>
+    /// This overload of the <see cref="AddProject(IDistributedApplicationBuilder, string, string)"/> method adds a project to the application
+    /// model where Aspire only generates a settings file for the project, not otherwise trying to build or run it. This is useful for projects
+    /// that you wish to always launch manually, but have them connect to Aspire services and OTEL.
+    /// </para>
+    public static IResourceBuilder<ProjectResource> AddSettingsOnlyProject(this IDistributedApplicationBuilder builder, string name,
+        string settingsFilePath, SettingsFileType settingsFileType)
}

A draft PR implementing this API is here: https://github.com/dotnet/aspire/pull/5016.

Usage Examples
builder.AddProject<Projects.MyFrontend>("mywebapp")
       .WithSettingsFile("..\\MyWebApp\\obj\\appsettingsAspire.g.json", SettingsFileType.Json, onlyGenerateSettings: false)
       .WithExternalHttpEndpoints()
       .WithReference(basketService)
       .WithReference(catalogService);

builder.AddSettingsOnlyProject("mymauiapp", "..\\MyMauiApp\\obj\\appsettingsAspire.g.cs", SettingsFileType.CSharp)
       .WithExternalHttpEndpoints()
       .WithReference(basketService)
       .WithReference(catalogService);

Alternative Designs
Initially, I considered having a separate project type for projects that generate settings. But allowing settings to optionally be generated for any .NET project, via a settings file IResourceAnnotation, allows more flexibility and emphasizes this is optional functionality in addition to integrated launch. Plus it required less changes to add. It seems like a nicer design all around.

Risks

I think this is unnecessary - Aspire can handle env variables, and this is just adding extra orchestration steps that arent necessary. A whole project for a settings file seems too much too.

At no point does wiring things up from Aspire mean you cant switch to the individual startup project - so you can just always switch around. I have been running frontends separately to test them and it doesn't change anything.

I think this is unnecessary - Aspire can handle env variables, and this is just adding extra orchestration steps that arent necessary. A whole project for a settings file seems too much too.

Just to be clear, the proposal here doesn't (necessarily) add a whole project for the settings file. The settings file is an optional addition to an existing project (via WithSettingsFile).

At no point does wiring things up from Aspire mean you cant switch to the individual startup project - so you can just always switch around. I have been running frontends separately to test them and it doesn't change anything.

Yes, you can do this, but how do those projects get the right settings to use, to connect back to Aspire hosted services or the Aspire dashboard?

I'm not super enthused about this API myself. Seems to me the root of the issue is passing environment variables into mobile apps when you launch them. Android for example has the concept of a Wrap script:
https://developer.android.com/ndk/guides/wrap-script
Maybe there is some prior art here we can lean on which is idiomatic within each target ecosystem?

I'm not super enthused about this API myself. Seems to me the root of the issue is passing environment variables into mobile apps when you launch them. Android for example has the concept of a Wrap script:
https://developer.android.com/ndk/guides/wrap-script
Maybe there is some prior art here we can lean on which is idiomatic within each target ecosystem?

We can't use the Android wrap script because that's embedded into the app at build time. But we have another custom way to pass environment variables at launch time to Android apps, which looks like it should get into 17.12, so I think we'll have Aspire integrated launch support in VS 17.12 for MAUI. All that said, I still see value with this proposal. There are multiple scenarios, especially with mobile, where you want to be able to launch the app the traditional way (not thru AppHost in VS), but still use Aspire and dashboard. I added another one to the bulleted list above - device test tools like Appium, BrowserStack, xharness, etc. want to do the app deploy and launch - that's the way they are built. Tools like Appium will not just do the initial app launch but also relaunch the app for each test (optional) or on crash. All that tooling isn't built to launch through AppHost (especially not thru VS, as it's generally CLI based). But it's still useful to test with Aspire, running in CI or locally. And then there are the other scenarios I mentioned above, like especially faster inner dev loop, but also Rider, CLI, etc.
I just see this proposal as giving users more options & greater compatibility with existing workflows. Integrated launch is nice. But sometimes you want - or need - to launch the traditional way & still use Aspire services/dashboard. It's nice to support both.

authors: BretJohnson maddymontaquila mitchdenny


text:
[WebToolsE2E][Aspire] The displayed string for Structured is not fully displayed for some localization.

INSTALL STEPS

Clean machine: Win11 x64 23h2
Install VS 17.12 P4 VAL (with Aspire 9.0.0)
Install latest Aspire 9.1.0-preview.1.24611.1

REPRO STEPS

Create .NET Aspire Starter App > .NET 9.0 (Standard Term Support) > Create
Build and F5
Change the display language in Settings, check [Spanish, Polish, Turkey and Russian]
Check the displayed string for Structured logs

NOTE

This issue is reproduced with the following language: Spanish, Polish, Turkey and Russian.
Resizing the page doesn't fully displayed the localized Structured string.

ACTUAL
The localized Structured string is not fully displayed.

EXPECTED
The localized Structured string should be fully displayed.

Can we get some guidance on whether this is a requirement, because this seems to be expected? Because some of these strings are quite long... ie Seguimientos.

authors: adamint vmykagapuz


text:
[release/8.0] dapr change the app port depending on the app protocol

Backpoirt https://github.com/dotnet/aspire/pull/3184 to release/8.0
Fixes https://github.com/dotnet/aspire/issues/2367
Customer Impact
Described in https://github.com/dotnet/aspire/issues/2367. Basically, if a DAPR-enabled Aspire app uses anything other than HTTP for communication, it will fail to communicate with the DAPR sidecar, so pretty bad.
Testing
@paule96 did manual testing and added pretty comprehensive automated test coverage of the change.
Risk
Low IMO. The change is well localized and small.
Regression
Not really--the initial implementation of the feature only covered HTTP case
Microsoft Reviewers: Open in CodeFlow

Where did we end up with using HTTPS by default as well? Separate issue?

approved for obvious reasons.

Where did we end up with using HTTPS by default as well? Separate issue?

Needs more design, post GA.

authors: danmoseley davidfowl karolz-ms


text:
Fix path to TestShop.AppHost in contributing.md

Description
The instructions in contributing.md for running the TestShop AppHost project had an incorrect path. I corrected the documentation with the correct path so that the instructions are accurate.
Fixes #6479
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[x] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

Thank you for the PR!


text:
.NET Core application consumes 100% CPU on a core inside a Docker container

What we're seeing:

In a relatively simple .NET Core 2.1 application, with no hard-loops, we're seeing 100% utilization on a processor core
This is running in a Docker container on a raspberry pi.
This happens at some random point, usually after the code has been up for a number of days. This has made reproducing / isolating the issue difficult.

What kind of debug tools are available?
How can we debug this? Is there a way to get a dump of the call stack from the command line?
Source
This is happening somewhere in the agent part of our IoT code:
https://github.com/Boondocks/Boondocks/tree/develop/src/Agent

This appears to be related to: https://github.com/dotnet/coreclr/issues/18486
And debugging is hampered by: https://github.com/dotnet/coreclr/issues/18889

repo: dotnet/core


text:
MSTest projects fail to build with .Net Core 2.2.102 on Azure Devops

Issue Title
An MS Test project (netcoreapp2.0, or netcoreapp2.1) fails to build on Azure Devops since the installation of .Net Core 2.2.102
General
The error is this:
2019-01-25T17:43:36.3668681Z ##[warning]MSTestProject\MSTestProject.csproj(0,0): Warning NU1604: Project dependency Microsoft.NETCore.App does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results.
2019-01-25T17:43:36.3677628Z D:\a\1\s\MSTestProject\MSTestProject.csproj : warning NU1604: Project dependency Microsoft.NETCore.App does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results.
2019-01-25T17:43:36.3944076Z ##[error]MSTestProject\MSTestProject.csproj(0,0): Error : NETSDK1061: The project was restored using Microsoft.NETCore.App version 1.0.0, but with current settings, version 2.0.0 would be used instead. To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish. Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore. For more information, see https://aka.ms/dotnet-runtime-patch-selection.
2019-01-25T17:43:36.3952399Z D:\a\1\s\MSTestProject\MSTestProject.csproj : error : NETSDK1061: The project was restored using Microsoft.NETCore.App version 1.0.0, but with current settings, version 2.0.0 would be used instead. To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish. Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore. For more information, see https://aka.ms/dotnet-runtime-patch-selection.
2019-01-25T17:43:36.4363349Z Done Building Project "D:\a\1\s\MSTestProject\MSTestProject.csproj" (default targets) -- FAILED.
2019-01-25T17:43:36.4704580Z Done Building Project "D:\a\1\s\MSTestProject.sln" (default targets) -- FAILED.

I have a minimal repro here, which is just an MSTest project based on netcoreapp2.1. There is a 3-step Azure Devops pipeline (using all default values) to go with this:

These builds work correctly on Azure Devops with version 2.1.403.
If I "Pin" the version to 2.1.403 in DevOps the build works fine.
Desktop builds work just fine, which is really weird.

I had this same problem attempting to build a Roslyn analyzer solution which uses .NET Standard 1.3.  I was using the default NuGet version chosen by Azure DevOps, which was 4.1.0.
I added the "NuGet Tool Installer" task to the start of my build pipeline with and specified the version as "4.x" and ticked the box for "Always download the latest matching version".  My build is now working successfully.

authors: DMEvans cleemullins


text:
dotnet is not recognised

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Did you close and reopen your command line window?

It is working fine.

authors: carlossanlop prishee


text:
.NET Core 3.1 - RijndaelManaged - Initialization vector 256 bits not supported

.NET Core 3.1 - RijndaelManaged - Initialization vector 256 bits not supported
RijndaelManaged does not support Initialization vector 256 bits in .NET CORE.
Hey,
If .NET Core 3.1 still does not support 256 initialization vector why documentation does not reflect that?
Look at this:
//RijndaelManaged
// Legal min key size = 128
// Legal max key size = 256
// Legal min block size = 128
// Legal max block size = 256
Anybody can't get the same result! Why does the documentation is not refleting the truth?
https://docs.microsoft.com/pt-br/dotnet/api/system.security.cryptography.symmetricalgorithm.legalkeysizes?view=netcore-3.1

@bartonjs should I transfer this to the api docs repo or runtime?

@mairaw this looks like a duplicate of https://github.com/dotnet/runtime/issues/37127

Closing as dupe.

authors: GrabYourPitchforks dericferreira mairaw vcsjones


text:
DataFrame LoadSql Method

I was playing around with the DataFrame library to start to build a SQL reconciliation tool, and I noticed that there is no easy way to go from SQL query to DataFrame.
I have some code for that can create the DataFrame from a SqlDataReader, but we may want an easier to use API than that.
One idea is to follow the convention used for the LoadCsv function and make something similar to the pandas function read_sql.
I am happy to put a PR together depending on the approach chosen.

One idea is to follow the convention used for the LoadCsv function and make something similar to the pandas function read_sql.

I'm assuming this will take in a raw SQL query as an argument to LoadSql? We should get input from @eerhardt and possible @tannergooding who most recently worked on some SQL readers. In particular, how .NETy is it to take in a SQL query as a parameter? What's the alternative otherwise?

A thing we need to be conscious about is that the dependencies of the core DataFrame library don't grow too unwieldy. Whenever we add a new dependency to the core DataFrame library, we have to consider if it is beneficial for the majority of use cases.
I definitely see the value in an easy API to load a DataFrame from SQL, but I don't believe it is "core" to the library. For example, DataFrame is used in https://github.com/dotnet/spark, which wouldn't want/need a dependency on SQL libraries.
So I would see something like this as an extension to the DataFrame library that ships in a separate NuGet package. We've designed the DataFrame API such that external libraries can "fill" or "load" one up from other data sources (ex. SQL).

Hi. I see that the code had been written for this, is there a design conflict or just the unit test that's is missing to merge this to main?
thanks

is there a design conflict or just the unit test that's is missing to merge this to main?

It looks like it is blocked on adding tests.

How extensive the test have to be?

The tests should exercise the main functionality to ensure it works, and doesn't get broken in the future.

I try and help so it can be merge on the main.

That would be great!

👍🏾 will try and give a shot then

authors: eerhardt pgovind rspaulino tzinckgraf

repo: dotnet/corefxlab

license: mit

license_source: bigquery


text:
Removed no longer necessary hacks.

These were workarounds for deficiencies in the language/compiler that are now fixed.

CC: @jaredpar @jcouv @OmarTawfik

Very nice!

authors: KrzysztofCwalina VSadov


text:
Add Debugging Info

Today, the debugging experience for R2R code at the assembly level is poor.

There is symbol information directly embedded in the R2R PE by crossgen that we're currently not emitting.
We need to follow up on our initial thread with Noah and Andy as to what information we need to put in the generated R2R image.

Fixed by https://github.com/dotnet/corert/pull/6322

repo: dotnet/corert


text:
Android emulator unable to call local web api via 10.0.2.2 via http or https - stuck after hours of trying

Section: Connect to local web services from Android emulators and iOS simulators
Looks and reads as well-written.  However unfortunately after failing to gain success implementing the advice in the first portion of the document entitled "Local web services running over HTTP", I decided to instead deploy "Local web services running over HTTPS".  The document is not clear that one should choose one or the other.  I decided that was the case; this could be made more clear in the intro.
I could not achieve success because on my web api, when I used Swagger to directly reach the http endpoint (via the http port), I received a "CORS" error with a lot of detail that was unhelpful.  Since I have seen no other mention of CORS related to MAUI / Android / iOS reaching a local development web api, I chose to not go down the path of implementing "CORS".
So I decided to implement: "Local web services running over HTTPS".
I trusted the local certificate (it was already trusted - I'm not sure when that ever happened in the past.)
I located the file in my Maui app that references "10.0.2.2" via a text search since your document doesn't give much direction on where to find that, and being a newbie to Maui, I didnt' know.
in "Bypass the certificate security check", the description made sense.  The sample code following: "The following example shows a class that configures the AndroidMessageHandler class on Android and the NSUrlSessionHandler class on iOS to trust localhost communication over HTTPS:" ... well.. I didn't know where I should put that, so I created a class file within the same namespace as where the httpClient is initialized.
namespace MTRMauiClient.DataServices
{
    public class RestDataService : IRestDataService
    {
        private readonly HttpClient _httpClient;
        private readonly string _baseAddress;
        private readonly string _url;
        private readonly JsonSerializerOptions _jsonSerializerOptions;

        public RestDataService(HttpClient httpClient)
        {
//HERE IS THE Sample code under paragraph:
//"The resulting HttpClientHandler object can then be passed as an argument to the HttpClient constructor for debug builds:"
#if DEBUG
            HttpMessageHandler handler = new HttpsClientHandlerService();
            HTTPClient client = new HttpClient(handler.GetPlatformMessageHandler());
#else
            client = new HttpClient();
#endif

There is an error for line HttpMessageHandler handler = new HttpsClientHandlerService(); indicating:

CS0029: Cannot implicitly convert type 'MTRMauiClient.DataServices.HttpsClientHandlerService' to 'System.Net.Http.HttpMessageHandler'

I clearly didn't copy/paste the sample code into the correct place.
Also, if the DI process supplies an httpClient parameter, why are we "NEWING UP" a new HttpClient ?
This makes me question if I am putting this code in the correct place, because the info in the document wasn't sufficient for me to be confident in knowing where to place it.
I am completely stuck.  Neither route has allowed me to successfully call my web api from the Maui app.
After spending a few hours last night, and my entire day today fighting with this, I'd like to suggest that this is an exceedingly weak and wasteful section of this otherwise amazing platform.
I will greatly appreciate any assistance.  I don't know where to turn after this because I'm pretty much I've reviewed virtually every forum post on this topic.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 663379bf-421a-57f1-39b7-e92f830de0ed
Version Independent ID: 663379bf-421a-57f1-39b7-e92f830de0ed
Content: Connect to local web services from Android emulators and iOS simulators - .NET MAUI
Content Source: docs/data-cloud/local-web-services.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hello. I think the code may have an error in it. It doesn't compile correctly. I want to guess that it was supposed to be a static method. I was able to get it to work by changing the handler service code to the following (I cut out the iOS bits, they remain unchanged)
public class HttpsClientHandlerService
{
    public static HttpMessageHandler GetPlatformMessageHandler()
    {
#if ANDROID
        var handler = new CustomAndroidMessageHandler();
        handler.ServerCertificateCustomValidationCallback = (message, cert, chain, errors) =>
        {
            if (cert != null && cert.Issuer.Equals("CN=localhost"))
                return true;
            return errors == System.Net.Security.SslPolicyErrors.None;
        };
        return handler;
#elif IOS
    // some code
#else
    throw new PlatformNotSupportedException("Only Android and iOS supported.");
#endif
    }

#if ANDROID
    internal sealed class CustomAndroidMessageHandler : Xamarin.Android.Net.AndroidMessageHandler
    {
        protected override Javax.Net.Ssl.IHostnameVerifier GetSSLHostnameVerifier(Javax.Net.Ssl.HttpsURLConnection connection)
            => new CustomHostnameVerifier();

        private sealed class CustomHostnameVerifier : Java.Lang.Object, Javax.Net.Ssl.IHostnameVerifier
        {
            public bool Verify(string hostname, Javax.Net.Ssl.ISSLSession session)
            {
                return Javax.Net.Ssl.HttpsURLConnection.DefaultHostnameVerifier.Verify(hostname, session) ||
                    hostname == "10.0.2.2" && session.PeerPrincipal?.Name == "CN=localhost";
            }
        }
    }
#elif IOS
  // some code
#endif
}

And then you use it directly like so:
HttpClient client = new HttpClient(HttpsClientHandlerService.GetPlatformMessageHandler());

The reason a new HttpClient is created is so that you can pass in the message handler instance for bypassing invalid certificates (when you're in dev mode), otherwise you don't need to create a new one.
Regarding the CORS error, I don't know, that seems more like a problem on the ASP.NET side of things.
@davidbritch Am I correct in these assumptions Dave? I can fix this article if I am.

@adegeo Afraid not. The code in the article compiles and works as is.
@tradegear At the top of the article there's a link to a sample, that has all the code in it. That should make it clear exactly where everything should live.

Ahh I figured out what is going on with the code. I'll open a PR

authors: adegeo davidbritch tradegear

repo: dotnet/docs-maui


text:
Debian ARM64 Setup Guide

From @reed123 on Wednesday, 06 February 2019 23:51:54
title says it all, i feel that there should be a setup guide for a case like this(or if possible can you link me one)
Copied from original issue: aspnet/AspNetCore#7332

From @muratg on Wednesday, 06 February 2019 23:57:30
Setup what exactly? One of the runtimes? SDK?
cc @richlander

From @reed123 on Thursday, 07 February 2019 16:00:52
set up the runtime on arm64
On Wed, Feb 6, 2019 at 6:57 PM Murat Girgin notifications@github.com
wrote:

Setup what exactly? One of the runtimes? SDK?
cc @richlander https://github.com/richlander
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/AspNetCore/issues/7332#issuecomment-461236469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGe_XDIVfM6qwkRaPc6yUgFz_wEkuy3Jks5vK2wFgaJpZM4amWJk
.

--
Sent By: Reed Kemp
Via: GMail [https://mail.google.com]
Send Me A Email: [http://emailreed.gdn] (beta)

@leecow can you here?

https://github.com/dotnet/core/blob/master/Documentation/linux-setup.md#installation-from-a-binary-archive basically covers what's needed.

Does that solve the issue @muratg?

@reed123?

Closing due to the lack of response. @reed123 if that doesn't solve your issue, please get back to us.

Yes sorry for lack of reply, that solves my problem
On Mon, Jun 3, 2019 at 6:59 PM Maira Wenzel notifications@github.com
wrote:

Closing due to the lack of response. @reed123 https://github.com/reed123
if that doesn't solve your issue, please get back to us.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/issues/10365?email_source=notifications&email_token=ABT36XHJN6WD2C6ZRWO6EXLPYWO6VA5CNFSM4GU64TN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW25RFI#issuecomment-498456725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABT36XF2YVKMIXLWMXL2XW3PYWO6VANCNFSM4GU64TNQ
.

--
Sent By: Reed Kemp
Via: GMail [https://mail.google.com]
Send Me A Email: [http://emailreed.gdn] (beta)

authors: leecow mairaw muratg reed123

repo: dotnet/docs


text:
missing function definitions

It would help if you provided function definitions since this doens't compile. e.g. FryEggsAsync

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 17d27a0d-c072-8c9f-7e31-3de60bee9ae8
Version Independent ID: e0c09794-e712-19ff-cb9f-12648d60d4f6
Content: Asynchronous programming in C#
Content Source: docs/csharp/programming-guide/concepts/async/index.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

All the code is in our samples repository
Can you tell me which version doesn't compile? It would if it matches the samples repository.

@BillWagner my interpretation of this is that @markus27183 is asking to see the FryEggsAsync definition like declared at https://github.com/dotnet/samples/blob/master/snippets/csharp/tour-of-async/AsyncBreakfast-V3/Program.cs#L73 or https://github.com/dotnet/samples/blob/master/snippets/csharp/tour-of-async/AsyncBreakfast-final/Program.cs#L84.
Not sure if this implementation is not show on purpose or not.

Excelent!
Just when i finished trying to write mine own definitions i started to read comments but that was good thing.
Any way i noticed one irrelevant mistake in mine code and checked yours final -
WHERE IS MY JUICE ? :D

Hi
I was unable to find the definitions for the methods ApplyJam and ApplyButter.  It is quite likely that all of these are implemented in the samples repository in Github.
While, I appreciate that you have put in efforts to provide the full source code via Github, I do not like the idea of frequently navigating out of the MSDN documentation. This destroys my mental model and makes my learning experience unproductive.
Thanks.

This is how my experience was

I begin reading through the article and encounter the first snippet of code
I see a method PourCofee. I do a CTRL+F and I do not find anything on the page.
Ignore and move on
I see methods FryEggs and FryBacon. Again do a CTRL+F and find nothing. I patiently move on to the next line
Move on to next snippet. I see a method ToastBreadAsync but as usual no body .
This experience keeps repeating over and over again.

The fragmented user experience left me so embittered that I abandoned reading the article and looked for other sources.
Again, putting all code is definitely a good idea, but I am out!

@BillWagner if the code is in your samples repository that information would be helpful to put in the actual article instead of buried down in the comments section

@BillWagner, apparently the samples repository moved since the links provided here are broken. Can you provide the new location?

@BillWagner Link is broken...please provide new location for code

Took a little while to track down but looks like they moved to docs repo here: https://github.com/dotnet/docs/tree/master/samples/snippets/csharp/tour-of-async/AsyncBreakfast-final with the implementations in the Program.cs file here: https://github.com/dotnet/docs/blob/master/samples/snippets/csharp/tour-of-async/AsyncBreakfast-final/Program.cs

authors: BillWagner SeniorSSS coosmiin kenwithee mairaw markus27183 sdg002 suttonb tlynch001


text:
Copy and paste with a shotgun

Would it be possible to put this page in the correct order?
For instance, in "Create a display utility method", there is a sentence
"The Transform() method populated ImagePath in ImagePrediction along with the predicted fields."
We have, at that point, not seen the Transform() method, nor ImagePrediction.
This is not about the sentence in particular, but the whole structure(sic) of the page, which looks like a full program has been loaded into a shotgun and shot at the page, with random pieces of code all over the place. In order to try to follow we have to scroll up and down the page continuously.
This is one of the better described pages available, but I cannot follow what is going on logically.
AB#1596621

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7ca0a402-fa67-fbd4-4cbc-604b4b59c97c
Version Independent ID: c8a996eb-82ed-a4bd-94d8-ef0b32158c67
Content: Tutorial: Retrain TensorFlow image classifier - transfer learning - ML.NET
Content Source: docs/machine-learning/tutorials/image-classification.md
Product: dotnet-ml
GitHub Login: @JRAlexander
Microsoft Alias: johalex

Thanks for the feedback @nfnpmc.
This issue can be added to AB#1596621

Fixed by #14531. @nfnpmc, we'd love if you would take another look at the tutorial and let us know what you think!

Hi Nat,
Somebody has done a brilliant job of sorting out that page, thanks very much.
Regards, nfnpmc
On Friday, 27 September 2019, 22:58:43 BST, Nat Kershaw (MSFT) <notifications@github.com> wrote:

Fixed by #14531. @nfnpmc, we'd love if you would take another look at the tutorial and let us know what you think!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you @nfnpmc!  That was me :-)

authors: luisquintanilla natke nfnpmc


text:
.NET Core 2.2 on Ubuntu 18.04

$ sudo apt-get install dotnet-sdk-2.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-sdk-2.2
E: Couldn't find any package by glob 'dotnet-sdk-2.2'
E: Couldn't find any package by regex 'dotnet-sdk-2.2'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ff5c1c2a-7d86-703c-038e-062f5dcfc5b0
Version Independent ID: cab4f67f-f338-8990-6454-853a0f01627e
Content: Prerequisites for .NET Core on Windows
Content Source: docs/core/windows-prerequisites.md
Product: dotnet-core
GitHub Login: @mairaw
Microsoft Alias: mairaw

@leecow @vivmishra can you take a look at this issue? Where should we move this too?

Just tested fine with a clean 18.04 Docker image.
@evermeire - The repo registration information will be hiding in /etc/apt/sources.list.d. If you performed the repo registration steps detailed at https://dotnet.microsoft.com/download/linux-package-manager/ubuntu18-04/sdk-current then you should find a microsoft-prod.list file that has a single line: deb [arch=amd64] https://packages.microsoft.com/ubuntu/18.04/prod bionic main.

In the /etc/apt/sources.list.d I had the following two files:

microsoft-prod.list.distUpgrade
microsoft-prod.list.save

The both contain the line:
deb [arch=amd64] https://packages.microsoft.com/ubuntu/18.04/prod bionic main
I created a third file with the following:
sudo cp microsoft-prod.list.save microsoft-prod.list
Still the same issue when attempting to install 2.2.
I had a co-worker who is running Ubuntu 18.04 after upgrading from Ubuntu 16.10 and he has no problems installing.  I have another co-worker who installed 18.04 clean a few months ago and has the same issue I have.

My machine runs Ubuntu 18.04 and I cannot  install .net core SDK 2.2. It is only 2.1 which is available. I followed https://dotnet.microsoft.com/download/linux-package-manager/rhel/sdk-2.2.101 and I've selected Ubuntu 18.04.

@leecow @richlander should I move this issue to https://github.com/dotnet/core/?

This is issue is stale. I'm going to close it unless there is still a problem.

authors: Thraka evermeire leecow mairaw radu99999


text:
Update .NET Standard to include disclaimer for .NET Framework

This is intended to be a better fix for #10448. We should remain truthful to the applicability rules of NuGet while also calling out that consuming .NET Standard 1.5+ from .NET Framework 4.6.1 really isn't a great experience that that the consumer should upgrade to .NET Framework 4.7.2.
Fixes #7305
/cc @SimonCropp

I merged for him 😄

Thanks peoples

authors: SimonCropp mairaw terrajobst


text:
Update entry to .NET 6

Shouldn't this be updated too?
/cc @nishanil @IEvangelist

Thanks @mairaw This was a miss!

authors: mairaw nishanil


text:
Fixed multiple typos in f# signatures chapter

There were a few typos in f# signatures chapter. E.g. the type alias while declaring member functions within Type2 was different within the same type. A few other minor typos were also corrected.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Sure. Thanks for the quick update. :+1:

authors: dnfclas jittrfunc


text:
Update index.md

fix variable name

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: prime167 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

repo: dotnet/dotNext


text:
Add operational style api for egressed artifacts

Note this follows a similar approach as the Azure Sdk (https://docs.microsoft.com/en-us/azure/azure-maps/creator-long-running-operation)
Some design considerations/possible changes

Status and error return the same status code but slightly different structure. We could use our own 2xx code here to make it easier for callers to determine the state.
There is no bounds on the operations we track. They stay around forever.
202 Accepted is a good return value but can be easily missed by the client. E.g. curl with egress without a -v just shows nothing.
We could consider a redirect for the above as well.

Remaining items:

[ ] Add more logging and comments
[x] Consider a name pass over all the newly introduced types
[x] Unit tests
[x] Account for infinite duration tasks
[ ] Update documentation

/azp run

repo: dotnet/dotnet-monitor


text:
Suggestion: Enable horizontal scrollbar

System Information (please complete the following information):

Windows OS: Windows-10-Enterprise-21H1
ML.Net Model Builder (Preview): 16.6.1.2131904 (Main Branch)
Microsoft Visual Studio Enterprise 2019: 16.10.2
.Net: 5.0.301

Describe the bug

On which step of the process did you run into an issue: All tabs: Scenario, Environment, Data, Train, Evaluate, Consume, Next steps
Clear description of the problem:  most text or button will not pop down a line on small screens, so hope to enable the horizontal scrollbar.

To Reproduce
Steps to reproduce the behavior (see below .GIF):

Expected behavior
Enable horizontal scrollbar or realize the text/ button to pop to the next line on a small screen for all tabs.

@romalpani What is the minimum window size we need to support?

@beccamc
Here are the guidelines for VS Win UI and resolutions. Let me know if you have any questions.
https://devdivdesignguide.azurewebsites.net/processes/craftsmanship-checklist/#resolution-and-screen-size

This is a nice to have, but has not been requested by any customers. Moving to chopping block for a Jake/Bri decision  if we should invest in this.  We have previously removed horizontal scroll bars Issue 1229.  The experience here would have to turn on scroll when a certain min width is reached.
We haven't failed any accessibility testing for the current experience.

I am trying to see how the UI reacts to more scaling factors of 100%, 150%, 200%, 250% but for some reason; I am unable to scale correctly.
If the UI is not cutting off at these scales, then I think we are fine.

By Design

authors: JakeRadMSFT beccamc romalpani vzhuqin

repo: dotnet/machinelearning-modelbuilder


text:
Cannot Add machine learning in VS2019 if installed VS2022.

System Information (please complete the following information):

Windows OS: Windows-10-Enterprise-21H1
ML.Net Model Builder (Preview): 16.7.2.2140201 (Main Branch)
Microsoft Visual Studio Enterprise 2019: 16.10.4
Microsoft Visual Studio Enterprise 2022 Preview: 17.0.0 Preview 2.1
.Net: 5.0.302

Describe the bug

On which step of the process did you run into an issue: Add Machine Learning in VS2019
Clear description of the problem: This OS installed VS2022 and VS2019, the model builder is the latest main build: 16.7.2.2140201, then if you want to use VS2019 to add Machine Learning, pop up Microsoft Visual Studio dialog said: The 'ModelBuilderPackage' package did not load correctly.

To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio 2019 start window;

Choose the C# Console App (.NET Core) project template with .Net 5.0;

Add>Machine Learning by right click on the project;

Pop up Microsoft Visual Studio dialog said: The 'ModelBuilderPackage' package did not load correctly.

ActivityLog.xml:
ActivityLog.zip

Restarting VS2019, this issue still occurs;

Also tried to uninstall and reinstall VS2019, then updated model builder to latest main build;

Updated Log:
dd_VSIXInstaller_20210805000540_1ad0.log

Open Manage Extensions, find that the Installed ML.NET Model Builder is for VS2022;

Navigate to Online>Model Builder find the model builder for VS2019 is not installed;

Click "Download" button to install the model builder for VS2019;

Pop up the VSIX Installer message that this extension is already installed.

Expected behavior
VS2022 should not affect the functionality of model builder in VS2019.
Additional context
Not affect adding Model Builder in VS2022.

Can't reproduce it somehow, the update works normal on my computer, can you try again..

Yes, can add machine learning in VS2019 with latest main build and installed VS2022.
Microsoft Visual Studio Enterprise 2019 Version: 16.11.0

ML.NET Model Builder version: 16.7.2.2141201

But I met another issue in VS2022 , cannot update model builder to current latest main build: 16.7.2.2141201, I'm not sure whether this behavior affects the validation result of this issue, could you help to take a look?
Microsoft Visual Studio Enterprise 2022 Preview (64-bit) Version: 17.0.0 Preview 3.0

Manage Extensions:

Added Main build under Additional Extension Galleries:

Can repro this issue on latest main build: 16.7.2.2141802, please see below GIF.

Steps:

Install  VS2022 from VS build >= 31618.209, and  update Model Builder to latest main build: 16.7.2.2141802 in Manage Extensions>Update box;
Open VS2019, add model builder by right click on C# Console App (.NET Core) project;
Prompt below dialog that: The 'ModelBuilderPackage' package did not correctly.

Open Manage Extensions, find the installed ML.Net Model Builder is for 2022 instead of 2019.

I still have trouble reproducing it

@beccamc @JakeRadMSFT @zewditu maybe give it a try and validate it?

@LittleLittleCloud  I can repro this issue on latest main build: 16.7.4.2145201

This machine itself has already installed VS2022 with latest main model builder, see below screenshot:

Then download + install VS2019 version 16.11.2 and update the model builder to latest through Manage Extensions;

Open VS2019, find cannot add model builder and the installed ML.NET Model Builder is for VS2022, see below screenshots:

Moving back to committed as Bri is also seeing this problem

The log
    <description>CreateInstance failed for package [ModelBuilderPackage]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
   at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
   at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
   at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
</description>
    <guid>{A1473B8C-F40E-4509-8A84-66BBA12B3E7F}</guid>

Indicates that VS2019 can't create an instance of ModelBuiler because it can't find file or assembly Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0. Which means that the model builder extension installed on VS2019 is for VS2022. The error is an expected behavior as the installed MB is for VS2022.
I'm suspecting that something wrong when @vzhuqin upgrade model builder. As the installed model builder on VS2019 was for VS2022 according to previous conversation, simply upgrading MB extension from extension manager won't fix this issue as the updated extension will still be for VS2022 only.
@vzhuqin Can you UNINSTALL ModelBuilder completely on VS2019 and then check two things

try reinstall from main branch through extension manager, and see if the correct model builder is installed. You can confirm it through description, which has "for VS2019" as suffix. This is to verify that extension manager can download the correct extension after the recent feed update.
try to install vsix directly by downloading this vsix and double click. This is to verify that ModelBuilder VS2019 can work in VS2019.

Update
In my case, VS2019 installs ModelBuilder for VS2022 even when VS2019 ones is selected

So it could be the regression of recent feed update in VS

Update
Install from vsix works on VS2019

@LittleLittleCloud  sorry for the delay.

Try 1:

I always met error during uninstall Model builder in VS2019, so prepared one machine which only installed VS2022, then installed VS2019: 16.11.2 .
Update model builder for 2019 through Manager Extensions.

Open VS2019, see model builder for 2019 is installed.

Open VS2022, find the model builder for 2022 needs to update, so I update model builder for 2022 through Manager Extensions, open VS2022 after updated, see error: the installed ML.NET Model builder is for VS2019. I doubt whether cannot update model builder from Main through Manage Extensions if the machine installed VS2019 and VS2022, could you help to see if which step is wrong?

Please give me some time to do  Try 2 , will update the result later.

Update:
As meet install trouble for VS2022 int preview, so installed VS2022 preview 4.0 to do "try 2".
Try 2:

Prepare one clean machine to install VS2022 and VS2019;

Download and install latest: 16.7.4.2146301 Microsoft.ML.ModelBuilder.Gallery.Dev16 from vsix ;

Open VS2019, see the installed model builder is correct, it is for VS2019;

Open VS2022, update model builder for VS2022 through Manage Extensions;

5. Issue: Find that the installed model builder is for VS2019.

It's probably fixed in latest VS release doesn't it? @JakeRadMSFT

@vzhuqin Can you try this again and see if it still repros?

Hi @beccamc , yes, i can repro this issue on latest main: 16.12.1.2206302

Microsoft Visual Studio Enterprise 2019 Version 16.11.9

Microsoft Visual Studio Enterprise 2022 (64-bit) Version 17.0.5

This might be because of the private feed. Customers don't use the private feed so it might not be an issue for them. Let's validate with the package from the VS Marketplace.

@v-Hailishi can you please validate whether this is an issue. See comment above.

@luisquintanilla Following are the validate steps and results:

Install VS2022 Enterprise 17.1.3 with ML.NET Model builder version 16.7.4.2151101 & VS2019 Enterprise 16.11.11 with ML.NET Model builder(Preview) version 16.1.0.2027905.
At this time, machine leaning can be added successfully for both VS2022&2019.

Update ML.NET Model builder version to 16.13.1.2210302 for VS2022 from the VS Marketplace.
Update ML.NET Model builder version to 16.13.1.2210301 for VS2019 from the VS Marketplace.
At this time, machine leaning also can be added successfully for both VS2022&2019.

Add private feed https://privategallery.blob.core.windows.net/gallery/refs/heads/main/atom.xml (Main branch) to VS2022&2019

Update ML.NET Model builder version to the latest main branch 16.13.5.2220401 for VS2022
At this time, machine leaning can be added successfully for VS2022

Update ML.NET Model builder version to the latest main branch 16.13.5.2220401 for VS2019 from the private update.
**At this time, cannot add machine leaning with error for VS2019. Besides, you can fine that ML.NET Model builder 2022 is installed in VS2019. **

If I am understanding this correctly the problem will only happen if you're also subscribed to our private feed. In this case, are we okay marking this as fixed? @luisquintanilla

cc: @JakeRadMSFT

@JakeRadMSFT to look into it. It might only be an issue with private feed.

Confirmed that this is related to private gallery. Closing as fixed.

authors: LittleLittleCloud beccamc luisquintanilla v-Hailishi vzhuqin


text:
It is not predicting rather doing pop up for error  "col1 was expected to be Single but couldn't be parsed"

Unsure what went wrong that it is not working.

System Information (please complete the following information):

Model Builder or CLI Version:
Visual Studio Version (if applicable):

Describe the bug

On which page of the tutorial did you run into an issue (URL):
Clear description of the problem:

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@KumarChandra-iima what your scenario is your scenario?
could you double check the datatype of col1 in advanced data option?
it seem that its type is "Single" but the value you provided is not able to be parsed into type single.
If you tell us more detailed information we can help more .

Fixed!
Actually I was supposed to use the other column. only column configuration
was required to be adjusted.
On Wed, Jan 17, 2024 at 1:21 PM zewditu Hailemariam <
@.***> wrote:

@KumarChandra-iima https://github.com/KumarChandra-iima what your
scenario is your scenario?
could you double check the datatype of col1 in advanced data option?
it seem that its type is "Single" but the value you provided is not able
to be parsed into type single.
If you tell us more detailed information we can help more .
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/2820#issuecomment-1895270841,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFDX5LOVYUMKYUAXOZWBKP3YO57HVAVCNFSM6AAAAABB2A7S7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJVGI3TAOBUGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: KumarChandra-iima zewditu


text:
Enable ML.NET Model Builder is not in Preview Features (VS16.6)

System Information (please complete the following information):

Model Builder Version: 16.1.0.2026302
Visual Studio Version: 16.6

Describe the bug
Hi, I have upgraded my vs to 16.6. There isn’t any “Enable ML.NET Model Builder” in Preview Features for enabling it.
To Reproduce
Steps to reproduce the behavior:

Go to Tools
Click on Options
Click on Preview Features

Expected behavior
Seeing "Enable ML.NET Model Builder"
Screenshots
If applicable, add screenshots to help explain your problem.

I have the same issue. Please fix this.

Hi, Same over here.
Visual Studio 16.6 as well.

Same here VS 16.6.0

I was able to fix this issue by uninstalling the "ML.NET Model Builder (Preview)" extension and installing it again.

I was able to fix this issue by uninstalling the "ML.NET Model Builder (Preview)" extension and installing it again. After re-installing, I did not get the popup to enable the preview feature when I tried to add Machine Learning to my project.

It's not worked for me.

Ditto... doesn't show and un-install/re-install doesn't work

Not sure how to uninstall the "ML.NET Model Builder (Preview)"

Not sure how to uninstall the "ML.NET Model Builder (Preview)"

Run VS installer and select modify then Individual components. But it doesn't work.

Hi, I had a similar problem before with Visual Studio 2019 16.6 Preivew 4 but this is a different issue.
You don't have to uninstall (unless you had it installed previously) but you might not have (unknowingly) installed it.
If it doesn't work at all, I have tried several things and it didn't work, including the below.
There are 2 workarounds:

Use Visual Studio 2019 16.7 Preview 1, it works perfectly
Uninstall (instructions below) and install the old extension https://marketplace.visualstudio.com/items?itemName=MLNET.07

Obviously, if you want to have the latest features and you can't get it working with VS 2019 16.6, 16.7 Preview 1 is the second-best thing.

Run Visual Studio Installer
Modify
Individual Components
Enter "Model Builder" in Search components
Check "ML.NET Model Builder (Preview)"
Modify (-275MB)

And to install it back, repeat the same thing:

Run Visual Studio Installer (already running if you followed previous steps)
Modify
Individual Components
Enter "Model Builder" in Search components
Check "ML.NET Model Builder (Preview)"
Modify (360MB)

Figure: Modify Visual Studio 2019 16.6

Figure: Model Builder

Figure: No matter what I do, it's not there.

Figure: You can install the old extension if the built-in one doesn't work, just uninstall Model Builder in Visual Studio Installer.

Same VS 2019 16.6

Same VS 2019 16.6
try All above and nothing work..

@monarqueje01, as mentioned above, this is the old version of Model Builder.
Use it if you really want to use Model Builder and you don't mind using the old version.
There are 2 major features you won't be able to access (aside from nicer look):

Significantly improved image classification
Recommendations

This will probably be fixed by 16.6.1 or if you want to test these features try these workarounds (they didn't work for me):

https://twitter.com/alexslotte/status/1263187069125431297
https://github.com/dotnet/machinelearning-modelbuilder/issues/757

Apologies for this issue. We had a bug that only showed up in the release versions of VS. You can try out 16.7 Preview 1 or any of the 16.6 previews and it'll work.
This will be fixed in 16.6.1 which should go out this week.

Also thanks @jernejk for helping people out! <3 the community involvement!

Thanks all!

Fix will go out with 16.6.1 which is now targeting Monday.

Thanks for your patience! We've fixed this issue in VS 16.6.1 and that went out today. Please update and you should see that this issue has been resolved. If you're stilling having any issues, don't hesitate to reach out again!
Thanks for using Model Builder!
Cheers,
Jake

Just want to confirm that it seems to be working :)

authors: AndrewPetz JakeRadMSFT ababilone aslotte attrib75 danieldamianov devenchawlayyc elamey jernejk monarqueje01 paradisehuman


text:
AspNetCore shared framework is missing System.Drawing.Common.dll in 3.0

From https://github.com/dotnet/core/issues/3734, inlining a few details:

When installing rh-dotnet30-dotnet-runtime-3.0 as suggested here:
https://dotnet.microsoft.com/download/linux-package-manager/rhel/runtime-current
The folder: /opt/rh/rh-dotnet30/root/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App/3.0.0
is missing System.Drawing.Common.dll
Which is part of the AspNetCore binaries here:
https://dotnet.microsoft.com/download/dotnet-core/3.0

We are using this assembly (System.Drawing.Common.dll) to edit png images.

I don't think there's any good reason for source-build to be different, somehow the dependency may have broken?

@dagood have you had the chance to look into this?
cc @omajid

I haven't been planning to, I filed this for source-build triage. For a rough direction, seems like this would be caused by some CoreFX => ASP.NET Core dependency problem, or maybe simply some logic in ASP.NET or source-build. @dleeapho @dseefeld @crummel @adaggarwal @NikolaMilosavljevic

This doesn't appear to be an issue anymore.  The latest versions 3.0.3 and 3.1.10 both have System.Drawing.Common.dll present.

This doesn't appear to be an issue anymore.  The latest versions 3.0.3 and 3.1.10 both have System.Drawing.Common.dll present.

authors: dagood dseefeld tmds

repo: dotnet/source-build


text:
Reconsider location of SB-specific scripts in VMR

Now that the unified build project is underway, the VMR is no longer specific to source build. We should reconsider the location of the prep.sh script. This file is specific to source build and is located at the root of the repo. Perhaps it should be moved to the eng directory or even eng/source-build. There is also another script related to source build in development at https://github.com/dotnet/installer/pull/18726 that this would apply to.

This file is specific to source build and is located at the root of the repo.

My 2 cents: this script is meant to be called by all maintainers that build .NET from source.
At the root of the repo it is more accessible, and it has more visibility.
cc @omajid

I don't have strong feelings about this change.

this script is meant to be called by all maintainers that build .NET from source.

In a distro-build scenario, such as building .NET 8 for Fedora, we don't invoke prep.sh at all. The majority of work that prep.sh does is downloading dependencies, which is something we want to avoid in distro build scenarios.
That said, for development on the VMR itself, prep.sh is very useful indeed.

In a distro-build scenario, such as building .NET 8 for Fedora, we don't invoke prep.sh at all. The majority of work that prep.sh does is downloading dependencies, which is something we want to avoid in distro build scenarios.

It's used for bootstrapping the initial build, right?

Those of us on the source build team use it A LOT. However, the fact is that the VMR's primary scenario is changing away from source build. As evidence to this, it no longer builds in source build configuration by default. There's always been a strong desire to limit the amount of files at the root of a repo. It's basically a given that onboarding new source build developers is something that will require a read through documentation. So trying to enable discoverability for this script isn't really a goal, IMO.

Let's consider source-build also a primary scenario, and not make it secondary to Microsoft's build.

We discussed this in the source-build planning meeting today and agreed with @tmds that we should keep the prep script at the root of the VMR.

authors: MichaelSimons mthalman omajid tmds


text:
Modal OnClose event not called when Modal closed with ESC key (when closed for the first time).

Describe the bug
When a Modal is closed for the very first time using the ESC key, the OnClose handler is not invoked. If it is opened again and then closed the ESC the OnClose handler is then invoked.
To Reproduce
A single file component is shown below.

Click the button to open the Modal.
Press the ESC key on keyboard.
Note that below the text "Step 3: Verify modal close events below." nothing is logged, suggesting the OnClose handler was not invoked.
Click the button again to open the Modal.
Press the ESC key on keyboard.
Note that below the text "Step 3: Verify modal close events below.", a close event is now logged.

    <Modal @ref="Modal">
        <ModalDialog Title="Test Modal" OnClose="ModalOnClose" Size="Size.Large">
            <BodyTemplate>
                Step 2. Press ESC to close.
                The first time you do this, the Close is not registered
            </BodyTemplate>
        </ModalDialog>
    </Modal>
    <button class="btn btn-primary" @onclick="() => Modal?.Show()">Step 1. Click to Show Modal</button>

Step 3: Verify modal close events below.

    @foreach (var modalEvent in ModalEvents)
    {

@modalEvent

    }

@code
{

    public List<string> ModalEvents { get; } = new();
    public Modal? Modal { get; set; }

    public Task ModalOnClose()
    {
        ModalEvents.Add($"Modal Closed: {DateTimeOffset.Now:O}");
        StateHasChanged();
        return Task.CompletedTask;
    }
}

Further technical details

BootstrapBlazor version: Tried with 6.12.0 and 7.0.0
Include the output of dotnet --info

.NET SDK:
 Version:   7.0.100
 Commit:    e12b7af219

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.100\

Host:
  Version:      7.0.0
  Architecture: x64
  Commit:       d099f075e4

.NET SDKs installed:
  5.0.302 [C:\Program Files\dotnet\sdk]
  5.0.408 [C:\Program Files\dotnet\sdk]
  6.0.111 [C:\Program Files\dotnet\sdk]
  6.0.202 [C:\Program Files\dotnet\sdk]
  6.0.203 [C:\Program Files\dotnet\sdk]
  6.0.306 [C:\Program Files\dotnet\sdk]
  7.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

The IDE (VS / VS Code/ VS4Mac) you're running on, and its version: VS Code

@m-chandler sorry for the delayed reply. I will repro this and fix it.

@m-chandler this is a bug. will fix it next release

@m-chandler I had redesign Modal component

    <Modal @ref="Modal111" OnCloseAsync="ModalOnClose">
        <ModalDialog Title="Test Modal" Size="Size.Large">
            <BodyTemplate>
                Step 2. Press ESC to close.
                The first time you do this, the Close is not registered
            </BodyTemplate>
        </ModalDialog>
    </Modal>
    <button class="btn btn-primary" @onclick="() => Modal111?.Show()">Step 1. Click to Show Modal</button>

Step 3: Verify modal close events below.

    @foreach (var modalEvent in ModalEvents)
    {

@modalEvent

    }

@code
{

    public List<string> ModalEvents { get; } = new();
    public Modal? Modal111 { get; set; }

    public Task ModalOnClose()
    {
        ModalEvents.Add($"Modal Closed: {DateTimeOffset.Now:O}");
        StateHasChanged();
        return Task.CompletedTask;
    }
}

move the OnClose of ModalDialog to OnCloseAsync of Modal

@ArgoZhang tested, looks good thanks. I'll wait for the next stable release, I'll leave it for you to close when you're ready ✔ .

@m-chandler hi, I have released version 7.0.3`. thank you for submitting the issue. now closed it

authors: ArgoZhang m-chandler

repo: dotnetcore/BootstrapBlazor


text:
🛑 PAH is down

In 12b8ee9, PAH (https://www.pembroke-animal-hospital.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PAH is back up in d4470c4.

repo: dougdragon/uptime


text:
🛑 H2Health is down

In b7f282e, H2Health (https://h2health.org) was down:

HTTP code: 500
Response time: 414 ms

Resolved: H2Health is back up in a7a2c9d.


text:
Progress and Quality both higher on optimizer than reality.

Required Information
Class:LTW (all)
Level:70
Craftsmanship:1685
Control:1620
CP:493
Recipe Name: Procoptodon Leather (all)
Recipe Level: 70****
Solver Seed: not using solver, just testing rotations with no rng
Expected Behaviour
my series of prudent touches should increase quality by 305,373,444,518
my careful synth II should increase progress by 337
screenshot of optimizer's expectation
Actual Behaviour
my prudents are 301,368,438,511
my careful synth II is 321
screenshot of game reality
Steps To Reproduce
I purposefully made a simple test rotation just to show the difference in values, making sure to show that I input my stats correctly as well, no food or anything. I see incorrect values with all 70**** recipes on all jobs with all skills that don't do a set % increase.
I hope you guys can figure this out, my confidence is shook after i thought i made some working rotations with the optimizer and then they didn't work in game :(

Sorry, level 70**** recipe support is experimental. I included the recipes
with a guess at what their effective level was, but it seems this was
wrong. I should probably filter out 70**** recipes until we get more data.

What kind of data would be useful? I may have the time to do some testing and collect some if it would help.

4_star_data.xlsx
@doxxx
Here are some actual data in the game. I think you should understand it.

Thanks, I'll take a look.

We have a new set of formulas for progress and quality increase. These changes are available on the beta site (ffxiv-beta.lokyst.net). Please let me know if these discrepancies are resolved.

repo: doxxx/ffxiv-craft-opt-web

license: Zlib


text:
Update recipe db for 5.4

I ran the scraper

https://github.com/doxxx/lodestone-recipe-db-scraper/pull/26
actually i ran it with this change to get the collectables

updated for 5.

Updated for 5.4


text:
Slow parsing H1 schema

It takes two minutes to parse (huge) Activity query from the H1 schema:
$ time gqlspection -q activity -f h1.json -d 1

h1.json

Well, after replacing recursive query generation with iterative version in #33 the query generation went down from 2 minutes to a couple of seconds. The depth calculation was adjusted as well, so the comparison isn't completely fair, but overall it looks like the rest of optimizations could wait for now.

repo: doyensec/GQLSpection


text:
Counts reported for G positions

Hi,
In the bedgraph output, I was expecting only the C postions in CpG sites. However, when my reads map to both the OT and OB strands, methyldackel reports methylated counts for both the C and G positions in CpG sites. Is this expected? How do I interpret the counts for the G positions?

Ok, I got it. When read maps to the bottom strand, the G position on the OT is actually C for the OB.


text:
⚠ 366.ru has degraded performance

In 90b96fe, 366.ru (https://366.ru) experienced degraded performance:

HTTP code: 200
Response time: 4957 ms

Resolved: 366.ru performance has improved in 2774f24.


text:
⚠ gorzdrav.org has degraded performance

In fb09235, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 6597 ms

Resolved: gorzdrav.org performance has improved in 8688494.


text:
feature: add Select api into SupernodeLocator

Signed-off-by: lowzj zj3142063@gmail.com
Ⅰ. Describe what this PR did
Providing a way for users to chooses a supernode based on the giving key.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1345 into master will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1345      +/-   ##
==========================================
- Coverage   50.78%   50.77%   -0.02%
==========================================
  Files         129      129
  Lines        8360     8362       +2
==========================================
  Hits         4246     4246
- Misses       3769     3771       +2
  Partials      345      345

Impacted Files
Coverage Δ

dfget/locator/locator.go
100.00% <ø> (ø)

dfget/locator/static_locator.go
68.49% <0.00%> (-1.93%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2443cba...7140edf. Read the comment docs.

LGTM

authors: codecov-io lowzj wangforthinker

repo: dragonflyoss/Dragonfly


text:
add err handling in test

Ⅰ. Describe what this PR did
add err handling in test
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
maybe need test
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #915 into master will decrease coverage by 6.88%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #915      +/-   ##
==========================================
- Coverage   46.57%   39.68%   -6.89%
==========================================
  Files         111      109       -2
  Lines        6611     6410     -201
==========================================
- Hits         3079     2544     -535
- Misses       3287     3657     +370
+ Partials      245      209      -36

Impacted Files
Coverage Δ

pkg/stringutils/stringutils.go
0% <0%> (-100%)
:arrow_down:

pkg/queue/queue.go
0% <0%> (-100%)
:arrow_down:

pkg/ratelimiter/ratelimiter.go
0% <0%> (-89.86%)
:arrow_down:

pkg/fileutils/fileutils.go
0% <0%> (-80.74%)
:arrow_down:

pkg/httputils/http_util.go
6.28% <0%> (-62.14%)
:arrow_down:

pkg/netutils/netutils.go
0% <0%> (-58.58%)
:arrow_down:

pkg/syncmap/syncmap.go
0% <0%> (-21.65%)
:arrow_down:

supernode/daemon/mgr/cdn/manager.go
19.78% <0%> (-6.44%)
:arrow_down:

supernode/server/server.go
40.74% <0%> (-2.12%)
:arrow_down:

client/request.go
35.78% <0%> (-1.45%)
:arrow_down:

... and 24 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4dffe50...c9c479e. Read the comment docs.

you add some err return in function but I haven't find other functions that use this function do with the err

@Starnop
I read all your suggestions.
thanks, and I will fix it.

@Starnop
I deleted all controversial changes.

LGTM.

authors: Starnop codecov-io hwdef yunfeiyanggzq


text:
can't run selfdrive/ui/ui ,can anybody help me ?

Describe the bug
: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Warning, could not open: /dev/shm/modelV2
_ui: cereal/messaging/socketmaster.cc:67：SubMaster::SubMaster(const std::vector<const char *> &, const std::vector<const char *> &, const char *, const std::vector<const char *> &): 假设 ‘socket != 0’ 失败。
OS Version
Ubuntu 20.04
openpilot version or commit
No response
Additional info
: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Warning, could not open: /dev/shm/modelV2
_ui: cereal/messaging/socketmaster.cc:67：SubMaster::SubMaster(const std::vector<const char *> &, const std::vector<const char *> &, const char *, const std::vector<const char *> &): 假设 ‘socket != 0’ 失败。

Assuming this is after you install needed lib and compiled op? Do pipenv shell and then scons -u -j8; ./ui inside ui dir

it's work after I clean " /dev/shm " , thanks

repo: dragonpilot-community/dp-devel


text:
build: run cargo update to make it compile for riscv64

What does this PR accomplish?

🩹 Bug Fix
🪣 Misc

Changes proposed by this PR:

Run cargo update to update  the dependencies in the lock file. The main motivation is to update ring from 0.16.20(which doesn't support riscv64: https://github.com/briansmith/ring/issues/1182) to 0.17 so that cargo-spellcheck can be built on riscv64 architecture.
Notes to reviewer:

📜 Checklist

[ ] Works on the ./demo sub directory
[ ] Test coverage is excellent and passes
[ ] Documentation is thorough

Thank you!

authors: drahnr kxxt

repo: drahnr/cargo-spellcheck


text:
Support dynamic decorates_assigned

It would be great to be able to pass a Proc to decorates_assigned to enable dynamic assignment of the decorator based on the model.
For example I have a PagesController in which it makes sense to wrap each different page in different Decorator. Currently I have to do this with a method call before render, but would be great to be able to pass a Proc that decides the Decorator type (AboutPageDecorator, HomePageDecorator etc) based on the requested page.

Sounds interesting, please sketch out a PR.

authors: Undistraction jcasimir

repo: drapergem/draper


text:
Fortunac/retrowrite bug fixes

Fixes a bug in wp, where we were looking at the target of a function call to determine how much to increment the stack pointer when visiting a call site. The correct behavior is to increment the stack pointer by 8 for the return address. We will have to update this in the future when we start supporting other architectures.

This looks really great. Great job, Chloe!

authors: codyroux fortunac


text:
fix(sheets-data-validation): data validation validator status render error

close https://github.com/dream-num/univer-pro/issues/2857

Pull Request Checklist

[ ] Related tickets or issues have been linked in the PR description (or missing issue).
[ ] Naming convention is followed (do please check it especially when you created new plugins, commands and resources).
[ ] Unit tests have been added for the changes (if applicable).
[ ] Breaking changes have been documented (or no breaking changes introduced in this PR).

/update-snapshots

repo: dream-num/univer


text:
是否能动态加载json文件

你好，我使用 java -jar .moco-runner-1.1.0-standalone.jar http -p 10001 -c "*.json"  加载多配置文件。发现新增一个json文件，如user.json时，并不能自动加载。而是需要重启项目才行。 希望能够动态加载配置文件

Do you mean that you add a new JSON file to your directory?

Do you mean that you add a new JSON file to your directory?

I have the same question. @dreamhead After run  java -jar .moco-runner-1.1.0-standalone.jar http -p 10001 -c "*.json"
, I add a new JSON file to current directory.  It doesn't work.

There is no such feature for now.
Moco can detect file content change, rather than a new file.

没生效呢。启动方式是        HttpServer server = MocoJsonRunner.jsonHttpServer(port, Moco.file(file));
runner = Runner.runner(server);
runner.start();

authors: 1657486787 beclever dreamhead liuyuanxiang

repo: dreamhead/moco


text:
Readme example yields blank page with no error

Hi, I've installed this as per the instructions in the readme but the example code given to retrieve all lists yields a blank page - no output at all. I'm running php5.5 on windows - any ideas where to start? Thanks

For anyone else who runs into this rather frustrating issue, you can resolve by opening the Mailchimp.php file and changing the value of $verify_ssl to false

repo: drewm/mailchimp-api


text:
Bug or bad karma?

Hello guys.
Sorry to bother.
Yesterday i was testing the Ionic push notification on both ios and android - with production certificate (all properly setup).
It wasn't working. I wasn't receiving any notification.
The Send push - from inside ionic.io dashboard - was working. I was receiving successfully the notifications on both ios and android.
But the cURL request wasn't working at all, both through my API or through Postman.
I had also opened a SO question:
https://stackoverflow.com/questions/39575790/ionic-push-notification-not-receiving-in-ios
But today magically everything works fine..
Without any change in the code whatsoever..
Do you know what could be the reason?
There has been some update in ionic cloud or was just an unlucky day yesterday?

@FrancescoMussi You were just unlucky. I introduced a bug to a system that push happens to use for 1 thing (facepalm) which caused some (but not all) pushes to fail. We've since pushed a fix that addressed the new bug and everything is in proper order.
Cheers! :beers:

Okay thanks! I was starting to doubt my whole life!

authors: FrancescoMussi ericb

repo: driftyco/ionic-cloud


text:
Ionic 2: White screen of death when calling nav.setRoot() from app.module.ts

Ionic version:  (check one with "x")
[2] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
Current behavior:
Call nav.SetRoot() from app.module.ts, white screen of death, see gif.
Expected behavior:
Normal navigation occurs
Steps to reproduce:
This is a well known bug that keeps being closed/marked as fixed.  This is NOT fixed.  It is a critical problem in the nav code of the framework.
This really needs to be addressed before apps can be deemed production ready.
See gif:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:

Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: OS X El Capitan
Node Version: v4.3.0
Xcode version: Xcode 8.1 Build version 8B62```

Hello, thanks for using Ionic! Sorry your having this issue, would you be able to post a repo or a plunker that we can use to reproduce this?

Here's a plunkr:
http://plnkr.co/edit/fYpX4KikzWFRo7repnkG?p=preview
But it doesn't happen on rc2, which the plunkr is based on.
The gif above is from ionic serve on 2.0.0

Hello, I have same problem with 2.0.0 version.
I go through nav.canGoBack() and after nav.pop() there is only blank screen.

Update: I have found the issue.  There is a situation where calling setRoot(), THEN calling popToRoot() causes the white screen.
Commenting out the popToRoot() and just using setRoot() fixes this issue.
Is this expected behaviour?

I have white screen after setRoot() and simply pop() afterwards..

Hello @daveshirman , thanks for updating the plunker and sorry it has taken me a few days to get back to you (: So yeah, this is going to be whats causing the issue. In this case when you run setRoot it will go ahead and navigate your app to the root page. With you calling popToRoot right after this it breaks the nav stack. Because this was user error I am going to close this for now.

But I have white screen after setRoot() -> push() -> pop(). I think, that there is a bug..

@jgw96 I don't think it should be possible for popToRoot() to pop ALL the pages off the stack, that's ludicrous!
See @lumitor2 's issue too, which is clearly related.

repo: driftyco/ionic


text:
bug: FormBuilder and ion-select : item is not selected

Type: bug
Ionic Version: 2.x
Platform: all
In the below example 'Banana' option is NOT selected.
It was working perfectly with Ionic 3.0.1
form: FormGroup;
constructor(fb: FormBuilder) {
this.form = fb.group({
fruit: ["banana"],
});
}

apple
banana
cherimoya

All my packages are updated as mentioned here : https://github.com/driftyco/ionic/releases/tag/v3.1.0

Hello! While we appreciate you opening an issue with us i am going to close this issue and ask that you open a new one that has the issue template filled out please. Thanks for using Ionic!

Hello there @MisterEffix , I'm having the same problem. have you found any fix?

Yes it's solved in the last ionic version