text:
Redis component instrumentation (tracing) causes app to crash on start if Redis is unavailable

The Redis component defaults to adding OpenTelemetry tracing for Redis. However if the configured Redis instance is unavailable at application start, the TelemetryHostedService  will attempt to initialize all instrumentation and the Redis instrumentation initialization attempts to resolve the IConnectionMultiplexer from DI which attempts to connect to the instance (see here). It seems an exception on this path will crash the startup of the app.

Stack trace
2024-03-14T15:57:24.5746136 fail: Microsoft.Extensions.Hosting.Internal.Host[11]
      Hosting failed to start
      StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.
         at StackExchange.Redis.ConnectionMultiplexer.ConnectImpl(ConfigurationOptions configuration, TextWriter log, Nullable`1 serverType, EndPointCollection endpoints) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 708
         at StackExchange.Redis.ConnectionMultiplexer.Connect(ConfigurationOptions configuration, TextWriter log) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 673
         at Microsoft.Extensions.Hosting.AspireRedisExtensions.<>c__DisplayClass3_0.<AddRedis>b__2(IServiceProvider sp) in D:\src\GitHub\dotnet\astra\src\Components\Aspire.StackExchange.Redis\AspireRedisExtensions.cs:line 82
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(ServiceIdentifier serviceIdentifier)
         at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
         at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
         at OpenTelemetry.Trace.TracerProviderBuilderExtensions.<>c__DisplayClass4_0.<AddRedisInstrumentation>b__1(IServiceProvider sp)
         at OpenTelemetry.Trace.OpenTelemetryDependencyInjectionTracerProviderBuilderExtensions.<>c__DisplayClass2_1`1.<AddInstrumentation>b__1()
         at OpenTelemetry.Trace.TracerProviderBuilderSdk.AddInstrumentation[TInstrumentation](Func`1 instrumentationFactory)
         at OpenTelemetry.Trace.OpenTelemetryDependencyInjectionTracerProviderBuilderExtensions.<>c__DisplayClass2_0`1.<AddInstrumentation>b__0(IServiceProvider sp, TracerProviderBuilder builder)
         at OpenTelemetry.Trace.OpenTelemetryDependencyInjectionTracingServiceCollectionExtensions.ConfigureTracerProviderBuilderCallbackWrapper.ConfigureBuilder(IServiceProvider serviceProvider, TracerProviderBuilder tracerProviderBuilder)
         at OpenTelemetry.Trace.TracerProviderSdk..ctor(IServiceProvider serviceProvider, Boolean ownsServiceProvider)
         at OpenTelemetry.Trace.TracerProviderBuilderBase.<>c.<.ctor>b__3_0(IServiceProvider sp)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(ServiceIdentifier serviceIdentifier)
         at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
         at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
         at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
         at OpenTelemetry.Extensions.Hosting.Implementation.TelemetryHostedService.Initialize(IServiceProvider serviceProvider)
         at OpenTelemetry.Extensions.Hosting.Implementation.TelemetryHostedService.StartAsync(CancellationToken cancellationToken)
         at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)
         at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)

For the health checks we seem to guard against this by deferring the actual resolution of the connection until the health check runs https://github.com/dotnet/aspire/blob/11b012853a0c3c00f3510b1a96c0156a06129d29/src/Components/Aspire.StackExchange.Redis/AspireRedisExtensions.cs#L173-L177
We might need a similar guard for OpenTelemetry initialization. Not sure if any other components are impacted.

@DamianEdwards - can you provide a repro project for this?

RedisConnectionException: It was not possible to connect to the redis server(s). Error connecting right now. To allow this multiplexer to continue retrying until it's able to connect, use abortConnect=false in your connection string or AbortOnConnectFail=false; in your code.

We default AbortOnConnectFail=false by default. So I think something about your setup is overriding this.
https://github.com/dotnet/aspire/blob/9df25bb1588eb88afcc551de348cc0f98bfe2d28/src/Components/Aspire.StackExchange.Redis/AspireRedisExtensions.cs#L244-L251

Repro steps:

Create a new solution using the Aspire Starter App template and ensure the "Use Redis for caching" option is selected
Edit the Program.cs in the AppHost project so that the Redis container pauses on start:var cache = builder.AddRedis("cache")
    .WithEntrypoint("sleep").WithArgs("1d");

Run the AppHost project

From https://github.com/StackExchange/StackExchange.Redis/blob/main/docs/Configuration.md?plain=1
| connectRetry={int}     | ConnectRetry         | 3                          | The number of times to repeat connect attempts during initial Connect                                   |
| connectTimeout={int}   | ConnectTimeout       | 5000                       | Timeout (ms) for connect operations                                                                       |
You can up the connectTimeout if you expect it to be longer.
The issue is that the OTel instrumentation package needs to start "listening" to the IConnectionMultiplexer on app startup. If the Tracing was moved to be part of StackExchange.Redis itself, the Redis OTel instrumentation package could completely go away.
cc @mgravell @NickCraver

I don't think what we have right now is usable given that an application can't start if a configured Redis instance is unavailable. That's the opposite of resilient 😄

Could the OTel instrumentation defer listening until socket connect via ConfigurationOptions.BeforeSocketConnect or similar?

This seems to work https://github.com/dotnet/aspire/compare/main...damianedwards/defer-redis-tracing

That seems like a good approach. I wasn't aware we could register the ConnectionMultiplexer after the fact.

authors: DamianEdwards eerhardt

repo: dotnet/aspire


text:
Add resource relationship to app model

Description
Fixes https://github.com/dotnet/aspire/issues/2595
This PR adds:

Relationship annotation and WithRelationship extension method to app model
WithRelationship calls are in various methods that add or reference resources.
Relationship field to resource service proto contract
Relationship field to ResourceViewModel.
UI to resource details to display References and Back references
Color to resource name on resources page and resource names in detail's references UI

Checklist

Is this feature complete?

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

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

[ ] Yes
[ ] No

Did you add public API?

[x] 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

[ ] 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

[ ] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[ ] No

Microsoft Reviewers: Open in CodeFlow

From an app model perspective I am happy with where this is at except for the XML doc comments ;)

I think this is ready for folks to review.
UI feedback is welcome on adding colors to resources. This is the same thing the dashboard does in telemetry pages, i.e. frontend could be assigned a blue color that shows up in various UI including the span waterfall on trace detail.

I think this is looking good. Just a few minor things and a bit of a UX nit:

Why not just hyperlink the resource name?

Yeah, it doesn't look that great. However, it's the UI we're using everywell else. Buttons looking a bit ugly is why I've been switching to the action column with ... button.
I'll play around with options later. I don't want to hold this PR up on a new UI design for row links.

I am not a fan on the colors, I think it is too noisy indeed.

All feedback applied.

I've already removed the colors. To avoid colors and UI discussion being a blocker, this PR can be merged without them, and then we can discuss later whether they're wanted or not.
Adding (or removing) them isn't difficult.

source: gharchive/pull-request

authors: JamesNK davidfowl mitchdenny

license: MIT

license_type: permissive

license_source: github-api


text:
Azure DevOps Pipeline doesn't support .NET 6? (VS2019 on windows-latest pool)

Description
I upgraded my project from .NET 5 to .NET 6 and wanted to execute a "build, test and publish" pipeline on Azure DevOps. That fails because the hosted agent does not support .NET 6 by default.
pool:
  vmImage: 'windows-latest'

I added an UseDotNet task in order to install the .NET 6 SDK which works, but that the build task failed ...
- task: UseDotNet@2
  displayName: 'Install .NET 6 SDK'
  inputs:
    packageType: 'sdk'
    version: '6.0.x'
    performMultiLevelLookup: true

telling me, that Visual Studio 2019 does not support .NET 6.
##[warning]C:\hostedtoolcache\windows\dotnet\sdk\6.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(134,5): Warning NETSDK1182: Targeting .NET 6.0 in Visual Studio 2019 is not supported.

I tried to set the "Compatible Visual Studio version", but than seems to be ignored:
    vsVersion: '17.0.0'

I would expect, that after the official release of .NET 6 the "latest" hosted agents would also support this new version.
Configuration
Regression?
Other information

@richlander who would know about what's supported on the latest images?
I am using vmImage: windows-2022 on my pipeline with .NET 6 SDK and that works for me. I haven't tried with windows-latest yet to see if it would work for me as well. I can give it a try and report back.

@mairaw Thank you, if I switch to windows-2022 the build process starts (and fails later with NETSDK1152: Found multiple publish output files with the same relative path). With that host I can also remove the UseDotNet task.
It would be fine, if the windows-latest would always work with the actual .NET version ;)

I'm trying to find the owner for this so we can have a definitive answer.

I'm trying to find the owner for this so we can have a definitive answer.

That'd be great. The UseDotNet task worked for me, but I'd much rather define that I'm using .net 6 in one place (within the project, not also in the pipeline) and for everything else to reference that.

telling me, that Visual Studio 2019 does not support .NET 6.

VS 2019 (windows) does not support .NET 6, for example as per the downloads page of the .NET 6 SDK:

Visual Studio support
Visual Studio 2022 (v17.0)
Visual Studio 2019 for Mac (v8.10)

How are you building your applicaton? If you use the - task: DotNetCoreCLI@2 tasks to build your app, you should be fine on the windows-latest image. If you use the visual studio build tasks, they will not work (as windows-latest is still VS2019)

NETSDK1152: Found multiple publish output files with the same relative path

This is likely not related to the build image. Does an equivalent dotnet publish command work in your project folder or publishing from your local Visual Studio 2022?

Ok, I found this page now Microsoft-hosted agents with the installed software on the different hosts.

Windows Server 2022 with Visual Studio 2022 --> windows-2022
Windows Server 2019 with Visual Studio 2019 --> windows-latest OR windows-2019

I didn't expect, that the "windows-latest" is no the latest ... :(  (clean code: meaningful names?)  With that info it's clear.
And your are right, I got the NETSDK1152 error also on a local publish. (I changed the target framework, fixed the bugs, run the tests and than I tried directly the pipeline.) There was an obsolete appsettings.json file in a second project.
With that I run into the next error during the test execution in the pipeline:
- task: VSTest@2
  displayName: 'Run tests & publish results"'
  inputs:
    testRunTitle: 'Hardware Independent'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'
    testAssemblyVer2: '$(testDll)'
    codeCoverageEnabled: true
    runInParallel: true
    rerunFailedTests: true
    rerunMaxAttempts: 3
    testFiltercriteria: 'TestCategory~hardware independent'

I didn't set "vsTestVersion" which should use again the "latest" Version. But it looks for a vstest.console from a visual studio installation with version [16.0,17.0) but couldn't find it?
Starting: Run tests & publish results"
==============================================================================
Task         : Visual Studio Test
Description  : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test (VsTest) runner. Test frameworks that have a Visual Studio test adapter such as MsTest, xUnit, NUnit, Chutzpah (for JavaScript tests using QUnit, Mocha and Jasmine), etc. can be run. Tests can be distributed on multiple agents using this task (version 2).
Version      : 2.170.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/test/vstest
==============================================================================
SystemVssConnection exists true
SystemVssConnection exists true
Running tests using vstest.console.exe runner.
======================================================
Test selector : Test assemblies
Test filter criteria : TestCategory~hardware independent
Search folder : D:\a\1\s
Action when minimum tests threshold not met : donothing
Minimum tests expected to be run: 0
VisualStudio version selected for test execution : latest
Attempting to find vstest.console from a visual studio installation with version [16.0,17.0).
Attempting to find vstest.console from a visual studio build tools installation with version [16.0,17.0).
Attempting to find vstest.console from a visual studio installation with version [15.0,16.0).
Attempting to find vstest.console from a visual studio build tools installation with version [15.0,16.0).
##[error]Error: Visual Studio 2015 is not found. Try again with a version that exists on your build agent machine.
Finishing: Run tests & publish results"

The VSTest@2 doesn't support VS 2022 or 17.0 yet?

Value is not accepted. Valid values: "latest", "16.0", "15.0", "14.0", "toolsInstaller".

Setting vsTestVersion: '16.0' doesn't help.  I open an issue at microsoft/azure-pipelines-tasks for that.

Good to hear about your progress! personally I‘m mostly using the DotNetCLI task as well to run tests and publish result (works for SDK-based test projects)

I fixed it adding this to xaml file:
steps:
- task: UseDotNet@2
  displayName: Use .NET 6.0
  inputs:
    packageType: 'sdk'
    version: '6.0.x'

But you don't use VSBuild or VSTest Task, do you?

I fixed it adding this to yaml file:
steps:
- task: UseDotNet@2
  displayName: Use .NET 6.0
  inputs:
    packageType: 'sdk'
    version: '6.0.x'

I agree that this works, and I'm grateful for it. It'd also be nice to have a more permanent fix. This won't work if there's a .net 6.1, or when .net 7 comes out.

But you don't use VSBuild or VSTest Task, do you?

I use DotNetCoreCLI@2.

Imao .NET 6 SDK should be added to vmImage: 'windows-latest' as default.
It is marked as recommended when downloading .NET and it is the current Long-term support (LTS) version.
https://dotnet.microsoft.com/download/dotnet

As long as the latest image is the Windows Server 2019 with Visual Studio 2019 it wouldn't help in all cases, for example VSTasks won't run, because .NET 6 needs VS 2022.
The latest image should always be the lastest and not the second latest.

What is microsoft doing? Why is windows-latest not latest? Why does VSTest ignore visual studio 2022? Why is Dotnet 6 a 'full' release when Microsoft doesn't properly support it?

What is microsoft doing? Why is windows-latest not latest? Why does VSTest ignore visual studio 2022? Why is Dotnet 6 a 'full' release when Microsoft doesn't properly support it?

I remember when .Net 5.0 was released, it also did't work without UseDotNet@2 fix. They fixed it later. I don't remember the exact time.

i have the same error

I have the same problem

So at this point windows-latest does not default to windows-2022, which is needed to build/unit test .NET 6 (C# 10) projects.
Here is a working pipeline that I pulled from these 2 blog posts:
(Azure DevOps - The Feature 'Global Using Directive' is currently in Preview)[https://webdev.box33.net/blog/the-feature-global-using-directive-is-not-supported-net-6][https://webdev.box33.net/blog/the-current-net-sdk-does-not-support-net-6]
(Azure Devops - The current .NET SDK does not support targeting .NET 6.0)[
This is a fully working Azure DevOps pipeline for a .NET 6.0 project using C# 10.0:
# ASP.NET Core (.NET Framework)
# Build and test ASP.NET Core projects targeting the full .NET Framework.
# Add steps that publish symbols, save build artifacts, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/dotnet-core

trigger:
- master

pool:
  vmImage: 'windows-2022'

variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'

steps:

# Add this Command to Include the .NET 6 SDK
- task: UseDotNet@2
  displayName: Use .NET 6.0
  inputs:
    packageType: 'sdk'
    version: '6.0.x'

# Add a Command To List the Current .NET SDKs (Sanity Check)
- task: CmdLine@2
  inputs:
    script: 'dotnet --list-sdks'

- task: NuGetToolInstaller@1

- task: NuGetCommand@2
  inputs:
    restoreSolution: '$(solution)'

- task: VSBuild@1
  inputs:
    solution: '$(solution)'
    msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactStagingDirectory)\WebApp.zip" /p:DeployIisAppPath="Default Web Site"'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

- task: VSTest@2
  inputs:
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

(disclaimer: not working for MS/GH, this comes from experience following the updates for a quite a while)
New images are usually tested for a few months to make sure people starting to use it (like all of us) don't run into unexpected issues in build scripts. That means waiting to see if people migrating to VS 2022 / .NET 6 / * open issues for something not working.
Then default image changes are rolled out incrementally - monitoring build failures and tickets. Again, you don't want to break thousands of people by changing the defaults unexpectedly and without prior notice. I too would be happy to not wake up the whole company being unable to complete work due to stuck CI/CD builds just because VS 2022 came out and most projects are still on .NET 3.1 LTS / VS2019 and not being updated on Day 0.
If you are asking for changing windows-latest immediatly, I would ask to keep it the current way.
From https://github.com/actions/virtual-environments/issues/4488:

When will windows-latest be replaced by windows-2022?

it will be announced, but not early than next year

Thanks to @dasMulli for the info. The behaviour that you discribe, would I expect if I use something like windows-stable ... ;)

I followed up internally on this as well. Here's the response I got:
"It is a long process for us to update the windows-latest label to point to the latest Windows image. The moment we do this, we break a number of customers. So, when we release a new image like windows-2022, we give a long notice (about 3-4 months), wait for people to gradually move their builds, and then update the image label. FYI, windows-latest pointed to windows-2016 until 3 months ago. You can follow the shifts in these labels from our release notes and from the GitHub pages.
Release notes: https://docs.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-194-update
Sample item in release notes about latest image: https://docs.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-193-update#macos-latest-label-will-soon-point-to-macos-11-image"
I'd keep an eye on the Microsoft-hosted agents article for updates. But for now, the windows-2022 is the right one to use.
Closing this issue since this behavior is by design according to the product team.

FYI, windows-latest pointed to windows-2016 until 3 months ago

As others have already pointed out, should the name really be windows-latest then, if it can take months for it to actually use the latest version?
The reasons for why a switch can't happen over night make sense, but the name is still extremely misleading. Especially for people who set up a new project. I concur with others here that windoes-stable would be much more appropriate.

@EnCey suggest you open that as in issue on https://github.com/actions/virtual-environments

Use .NET 6.0 SDK --> Takes 1.30minute. Are there any options to improve this?

If you select windows-2022 as host, the SDK is directly available. No need for the UseDotNet task.

Hmm, didn't work on my end. It still took some time to download & install the SDK.
Ended up using ubuntu to speed it up. Seems a bit weird that this is faster than a windows image?
Or is it normal as it is like slimmer / faster?

It is a long process for us to update the windows-latest label to point to the latest Windows image. The moment we do this, we break a number of customers.

Sorry, but this is nonsense: customers that choose to use the windows-latest image are not Microsoft's problem. If they want an image that won't change out from under them, they should have selected a specific image like windows-2019, or built their own.
Stop mollycoddling developers who are too lazy to setup build and release pipelines correctly.

I have the same problem, only that i'm using sonarcloud and i get this

Same here.  .net core 6 builds fine on windows 2022 agent

Here's the issue tracking this update: https://github.com/actions/virtual-environments/issues/4856

Hitting the same issue here as well

It is a long process for us to update the windows-latest label to point to the latest Windows image. The moment we do this, we break a number of customers.

Sorry, but this is nonsense: customers that choose to use the windows-latest image are not Microsoft's problem. If they want an image that won't change out from under them, they should have selected a specific image like windows-2019, or built their own.
Stop mollycoddling developers who are too lazy to setup build and release pipelines correctly.

While I agree to an extent, I want to counter with the fact that this implicitly codifies the notion that Developers and DevOps should not be distinct from one another, and that Developers need to know literally everything to do literally anything, which is a death spiral.
I'm running into this upgrading to .NET 6 when I've literally never had to interact with this aspect of Azure DevOps for my 5 years of experience with it.
I do otherwise agree that "latest" is "latest", and that they should have a different keyword if you want "latest-verified"

I'd suggest that you start a discussion on the https://github.com/actions/virtual-environments repo about this. This is not something the .NET team controls it.

This in fact works very well. Thank you for sharing it! Do you mind sharing how you were able to get to this file? We've tried applying sections of this into the "GUI" pipeline process but can't get it to work. Yet this file works very well for .net core 6.

'task: NuGetCommand@2',  sometimes finds an old cached version of NuGet. Try to add 'task: NuGetToolInstaller@1' before this task.

Update Agent Specification in Azure DevOps pipeline to Windows 2022

Update Agent Specification in Azure DevOps pipeline to Windows 2022

Yes it's working.

I have the same problem, only that i'm using sonarcloud and i get this

You need to use both net6.0 and net3.1 to run sonarcloud with net6.0. Works for me :)

source: gharchive/issue

authors: AidanRRR BrendanSluke EnCey HydTechie IanKemp LittleLittleCloud Niraiyaa Ogglas PaladiAlexandru Pentadome Prinsn RyantheLeon SiripuramKrishnakumar benjaminoerskov brux88 coinzdude dasMulli davidrevoledo mairaw mikeKuester oyvost schovan

repo: dotnet/core


text:
Download of .NET 5.0

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/edit
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
My OS is Wn10. During the download of .NET 5.0 all was ok ,up to the final step : Edit your code.
On this last step,on Program.cs,  I have added the 3rd line : "Console.WriteLine ( "The current time...etc.)"   and a "screwdriver " has appeared on the left of this line; I was not able to understand its meaning.  Having written,and saved, the 3rd line,  I tried to enter again on Prompt (as required, to close the installation) , but I got the message (in Italian) : No Project has been found... ; I was not able to understand what was wrong .

I think you are missing a semicolon at the end. If you copy and paste exactly, does it show errors again?
Console.WriteLine("The current time is " + DateTime.Now);

We'll need a bit more information to try to help you. Could you please perhaps send a screenshot of what you are seeing?
cc @mairaw

authors: BBuno maryamariyan ryank425


text:
installation issue

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: linux
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
unable to install / run dotNet and C# on my Lenovo duet 5 chromebook

To install dotnet on Linux use sudo command. It'd be more faster and efficient

Can you please provide any steps that you have tried?

Which Linux distribution do you use?
Try this if you're on Ubuntu.
sudo apt-get update

Then install dotnet
sudo apt-get install -y dotnet6

Then install runtime
sudo apt-get install -y dotnet-runtime-6.0

This should work but if you're using different distro apt-get won't work.


text:
Fix wrong image preview

The current image shows an installer image for.NET 6 like that;

It should show 7.0 instead. This PR fixes #7742

 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: aligoren sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for creating the PR @aligoren. It seems @dcwhittaker hadn't noticed you opened the issue and the PR at the same time. Since she made the updates already on #7745, I'll close this one. Thanks for reporting the problem!

authors: aligoren dnfadmin mairaw


text:
Resolve ANTLR warnings by defining named lexer tokens

This PR addresses Issue #37, Proposal 4 (https://github.com/ECMA-TC49-TG2/csharpstandard/issues/37#issuecomment-767636955). Specifically, it

Adds definitions for 6 named lexer tokens, and then refers to them in various lexer rule alternatives
Adds some ANTLR-related commentary
Defines New_Line as a strict superset of New_Line_Character
Fixes an error in Single_Regular_String_Literal_Character
Changes identfier => Identifier in expressions.md
Changes Right_shift => Right_Shift in classes.md

For now this is a Draft PR, as I want to explore the idea of replacing the use of certain terminals in the syntactic grammar with the 6 new named lexer tokens (for example, 'default' in a switch statement becomes DEFAULT).
I explored that and decided to not go down that path, as explained in https://github.com/ECMA-TC49-TG2/csharpstandard/issues/37#issuecomment-780859388.

Note for meeting: I don't think there have been changes since the last meeting, so we may wish to skip this.

authors: RexJaeschke jskeet

repo: dotnet/csharpstandard


text:
remove unused entries for triageconversationdata connection string from helix-service manifests

This storage account is unused so we should delete everything about it.

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[X] Internal Infrastructure Improvements

Release Note Description
No release note needed

This issue is only here to appease automation that checks for a github issue in a PR: https://dnceng.visualstudio.com/internal/_git/dotnet-helix-service/pullrequest/41488

Done and rolled out

repo: dotnet/dnceng


text:
Migrate Xamarin.Forms Effect docs

MAUI now includes support for effects, but there are some small changes from Xamarin.Forms: https://github.com/dotnet/maui/pull/1574

This doesn't need adding to the MAUI docs, as there are better approaches using handlers.

repo: dotnet/docs-maui


text:
Snap based install of .NET can lead to segmentation faults.

Source: https://github.com/dotnet/runtime/issues/51322#issuecomment-890306629 and https://github.com/dotnet/runtime/issues/3775#issuecomment-534263315 and https://github.com/dotnet/runtime/issues/3464
Also, according to this comment Snap issues have been closed "to reflect current priorities."
Shouldn't this be reflected in the documentation? Why do the docs provide instructions on installation via snap when it isn't a "current priority" and it doesn't work?

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

ID: a40005eb-f935-d50d-10ce-c1e0a47ea70e
Version Independent ID: 91f4a9b7-09d0-f18e-af4a-c0af28a8948f
Content: Install .NET on Linux with Snap - .NET
Content Source: docs/core/install/linux-snap.md
Product: dotnet
Technology: dotnet-install
GitHub Login: @adegeo
Microsoft Alias: adegeo

Associated WorkItem - 45520

Thank you for letting me know. I'll prioritize getting a note added to the article.

Note: Opened an internal discussion on this.

At this point we're still waiting. I'm going to close this for now and when new info about snap becomes available, I'll reopen this.

authors: adegeo devhawk

repo: dotnet/docs


text:
Grammar Issue

The text advises, "Use past tense (as in this example) when the event reports something that has happened."  However, the example referred to, "Progress," is not a past tense form of "to progress." (It is present indefinite, IIRC.)  This could be improved by changing the name to a past tense verb, such as "MadeProgress" or "Progressed", or by removing the parenthetical reference to the example.  (The latter approach still leaves an example that conflicts with the advice given, so it's not ideal.)

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

ID: 0e2507bc-e567-23f9-aeb9-f7529baa7032
Version Independent ID: c42718d0-15b4-a87f-4353-e15656686889
Content: Introduction to Events
Content Source: docs/csharp/events-overview.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for your feedback, @johnechiappetta. Since this is just a signature with no implementation, it's difficult to determine the intent of the event. But progress events are typically status events and therefore present tense events -- that is, they're intended to indicate what proportion of an operation has currently been completed. Given that, the use of Progress seems correct (though I have to confess that I see it didn't quite see it as a verb).
It could be argued that a present participle ("Progressing") better conforms to the naming convention, though it seems to me that it does so at the expense of clarity. MadeProgress seems to also be less clear, as is MakingProgress.
It's also true that event naming convensions seem to be violated more often than not. For example, In .NET, click events appear to be named both Click and Clicked to express the same basic kind of event,  even though the event is informational and therefore a past event.
I do think, though, that the text becomes less confusing by remove the parenthetical reference to the example.
Thoughts?

Adding the "up for grabs" label.  I think the correct fix is in the previous comment:

I do think, though, that the text becomes less confusing by remove the parenthetical reference to the example.

authors: BillWagner johnechiappetta rpetrusha


text:
Field description is not clear

I don't think after reading through this page, user will be able to adjust those parameters for their application. To actually playing with those parameters, users need to first find a suitable data set and figure out how to create a pipeline with the correct trainer. Maybe add some examples like scikit-learn (they basically have at least one runnable example for each component exposed to users) could help?

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

ID: fa672bcd-5d84-52b5-bd24-b35e9db51355
Version Independent ID: 5df92e70-d059-03dd-b024-138f0a35e367
Content: AveragedLinearArguments Class (Microsoft.ML.Trainers.Online)
Content Source: dotnet/xml/Microsoft.ML.Trainers.Online/AveragedLinearArguments.xml
Product: dotnet-ml-api
GitHub Login: @sfilipi
Microsoft Alias: johalex

Hi @wschin, great feedback! I will pass to the product team, as these pages are generated from the code comments. Have you seen the tutorials in the ML.NET Guide?

It seems this API no longer exists. Closing. FYI @natke

authors: JRAlexander mairaw wschin


text:
Move C# compiler pages to single dir

Contributes to #1491 and #2363
I haven't yet touched the TOC, this is big enough for one PR. Note these pages weren't listed in any TOC in their previous location either - and the next part of #2363 is to get rid of the TOC entirely.
I hope the folder redirect works - let me know if it needs changing. 😊

Hey @BillWagner - any news on the directory redirection feature? 🙂
It's been a while - do you think we should either write the files out explicitly? Or if not, perhaps just close this PR until things are ready. Let me know what you thinks best - thanks!

@ChrisMaddock I wish I had better news.
The folder level redirection is still in the backlog.
I think it's stale enough that closing it makes sense. At least for now.
I'm hoping we can have a better plan between now and .NET 5.0. I'm working on some options.

No worries - thanks @BillWagner. 👍

authors: BillWagner ChrisMaddock


text:
Use 'T1 etc for type variables in F#

F# style guidelines prefer the use of 'T1 etc for type variables.
Pointed out on twitter https://twitter.com/jordan_n_marr/status/1420043164535173125

Thanks!


text:
Remove unused branches

@livarcocc , can you confirm that removing the MSBuild entry is ok?
@GrabYourPitchforks, can you confirm that removing the utf8string branches from Jenkins is ok?

Its ok. Confirmed for msbuild.

It's fine to remove them from CI since we're about to merge into master. Please don't delete the branches from source control just yet, though, since we're still cherry-picking commits.

authors: GrabYourPitchforks chcosta livarcocc

repo: dotnet/dotnet-ci

license: mit

license_source: bigquery


text:
command not found: mlnet

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.

Are you running in MacOS or windows

Sorry we don't have enough information to investigate. Please fill out the template if you still need help. Thanks!

repo: dotnet/machinelearning-modelbuilder


text:
Renaming the property of an inject service does not work

Describe the bug:
I have an @injected service and try to rename the property holding the value.
Version used:
VS2022 17.2 Preview 1
To reproduce:
@inject IEnumerable<int> emumerable // rename here

@code
{
    void M()
    {
        foreach (var a in emumerable) // expect result here
        {
        }
    }
}

Try to rename emumerable to enumerable.
Expected behavior:
All occurences of the emumerable name within the Razor file should be replaced with enumerable
Actual behavior:
The example usage of the instance in the foreach loop is not renamed and left behind as a compilation error.
Additional context:
There's already a highlighting issue before the rename operation. Clicking either the @inject property or the usage in the foreach does not highlight the other. Both also show a different tooltip, what C# language thing they are: The @inject property is (local variable) object emumerable while the usage in the foreach loop is IEnumerable<int> Test.emumerable { get; set; }

Any progress on this? It really slows down refactoring efforts.

The problem persists for ages and it's really anoying as it can break the code badly.

This is still an issue in mid 2024. How can we elevate this to get it fixed? Makes refactoring much more tedious. :(

authors: KrystofZacek Tragetaschen gabephudson oldominion

repo: dotnet/razor


text:
Port #9863 to main

Ensure we include the line count and end char index in remapped spans
Make the source span in tests have non-default values to ensure they get mapped too

@dotnet/razor-compiler for review

Merging with a single approval as this is just code flow.


text:
Adding a new source file to a Mutli-TF project doesn't correctly populate the editor context navigation bar

Create a C# .net core project
Change TF -> TFs and add netstandard1.5 to the list, i.e. change it to <TargetFrameworks>netcoreapp1.0;netstandard1.5<TargetFrameworks>.
Open Program.cs and verify both netstandard and netcoreapp show up in the editor context navigation bar
Now right click the project in the solution explorer and add a new source file

Expected: New source file also has both netstandard and netcoreapp in the editor context navigation bar
Actual: New source file only has both netcoreapp in the editor context navigation bar
I have a strong feeling this is due to CPS only triggering design time builds only for the active project config.

I debugged further into this and it seems CPS is indeed triggering design time builds and evaluations for both the configured projects, and we are correctly passing down the newly added source file for both the Roslyn workspace project contexts, but the navigation bar still shows only one project for the new source file.

Investigated this further, and my previous comment is not fully correct. CPS does trigger an evaluation with newly added source file for both the configured projects, but the PublishTreeAsync invocation here never returns for non-active configured project (netstandard1.5), and hence we never add the newly added source file to the Roslyn Workspace. I believe the fix is to invoke PublishTreeAsync API only if we are dealing with active project context.

Let's retarget this to master for now and wait for more feedback about this.

@srivatsn How about the Roslyn pull requests for #1613 and #1013? Do we want to also retarget them to master?

Yes

Really for 15.3 instead of 15.1? This means that .NET Core development in VS will be unusable until update 3. 🙁

@fubar-coder There is a way to trick it into working, what you need to do is put a semicolon after the final target so
netcoreapp1.0;netstandard1.5
becomes
netcoreapp1.0;netstandard1.5;
However this causes another issue in that when you add a new class it will only be available for one of the targets. So to get it back for both edit the  csproj in visual studio and swap the target framework order around and save it, this will cause it to then apear for all the target frameworks.

This really not a practical solution, especially when VS suddenly gets the idea that it wants to revert your changes to the csproj (which happens quite often)

@fubar-coder It may not be the best solution but it is a workaround, we have been using this since we installed VS 2017 on the 8th March and have had no issues with the change we made to csproj being reverted.
I agree with you in that this should be fixed sooner than the 15.3 milestone as it is an absolute pain, especially when you forget and spend 10 minutes trying to figure out why your code will not compile.

@DazFahy I tested this workaround and it doesn't work. It's the same behaviour as before: After adding a certain amount of class files, I get the Miscellaneous Files instead of the target framework moniker in the editor window and the intellisense doesn't see the new class. Unloading and reloading is the only way to (almost) reliably make the new class available.
IOW: This bug needs to be fixed ASAP. Otherwise, VS2017 isn't really recommended for library developers targeting multiple frameworks.

Tagging @davkean

authors: DazFahy fubar-coder mavasani srivatsn

repo: dotnet/roslyn-project-system


text:
ArgumentException at Line 104 ProjectLockFileWatcher.cs when creating a new .Net Core Console Project

On VS D15Prerel 26012.0
objDirectory = _projectServices.Project.MakeRooted(objDirectory); throws ArgumentException.
Because  objDirectory is empty from the previous statement
var objDirectory = (string) await configurationGeneral.BaseIntermediateOutputPath.GetValueAsync().ConfigureAwait(false);
Stack Trace
at Microsoft.Requires.NotNullOrEmpty(String value, String parameterName)
at Microsoft.VisualStudio.ProjectSystem.PathHelper.MakeRooted(UnconfiguredProject unconfiguredProject, String path)
at Microsoft.VisualStudio.ProjectSystem.VS.ProjectLockFileWatcher.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.VisualStudio.ProjectSystem.VS.ProjectLockFileWatcher.<ProjectTree_ChangedAsync>d__11.MoveNext()

Seems like the none of the XAML rule property is working and I don't see any CPS error in the output during the project load

When we fix the rules, we should make this not crash if its empty.

@srivatsn Can you get someone to have a look at this tomorrow morning - sounds like the builds are broken.

This may be a race condition on restoring. That property is coming from the SDK (common.props)
$([System.IO.Path]::GetFullPath('$(RepositoryRootDirectory)bin\obj$(MSBuildProjectName)'))</BaseIntermediateOutputPath>
And opening an existing project (which already restored at least once) does not repro the issue.

But in the new SDK attribute, the props are always present and there is no restore needed at all.

Looks like the SDK attribute is what's causing the problem. Older projects didn't have it so that's why those are working fine.
@srivatsn Who has more context on the SDK change? On the surface it looks like we may be missing matching MsBuild support and that's what's causing the missing imports. This is the build output of a manually modified project (hand created from the shipping template):
"E:\My Documents\Visual Studio 2017\Projects\ConsoleApp16\ConsoleApp16\Broken.csproj" (default target) (1) ->
E:\My Documents\Visual Studio 2017\Projects\ConsoleApp16\ConsoleApp16\Broken.csproj : error MSB4040: There is no target in the project.

I installed today's build and it's working.
Do you have this directory: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Sdks?

Yes:

I'm going to update my build to today's. If this is already fixed there's no sense in trying to drill down further. As a follow up, for preventing the crash in general - It looked like a whack a mole since the project is unusable without it's imports so there were many more errors after patching this one. Ideally we would block the project load on cases like this.

This is fixed on later builds, opened a new bug to handle missing targets gracefully.

authors: RaulPerez1 basoundr davkean srivatsn


text:
Add reference packages for NuGet.Packaging and NuGet.ProjectModel > 5.8.0 to SBRP

A change was recently made to the runtime in 6.0 which takes a dependency on NuGet 5.8.0.  Generating the 5.8.0 reference packages is not trivial for the following reasons.

It introduces a cycle
/repos/source-build-reference-packages/src/referencePackages/src/system.security.cryptography.cng/5.0.0/System.Security.Cryptography.Cng.csproj : error NU1108: Cycle detected.  [/repos/source-build-reference-packages/.dotnet/sdk/5.0.100-rc.1.20452.10/NuGet.targets]
/repos/source-build-reference-packages/src/referencePackages/src/system.security.cryptography.cng/5.0.0/System.Security.Cryptography.Cng.csproj : error NU1108:   System.Security.Cryptography.Cng -> NETStandard.Library 1.6.1 -> System.Security.Cryptography.X509Certificates 4.3.0 -> System.Security.Cryptography.Cng (>= 4.3.0). [/repos/source-build-reference-packages/.dotnet/sdk/5.0.100-rc.1.20452.10/NuGet.targets]

The dependency chain brings in 5.0.0-preview3 references.  This looks to be solved by using 5.8.1 instead.

The GenSBRPReferencePackages tool is generating Microsoft.NetCore.App 2.1.0 as a reference package.

This was discovered while doing the Runtime ArPow work.  Without this it will cause a prebuilt reference.

[Triage] This is not a blocker; we are shipping without it prebuilt clean.  If this becomes a blocker, it can be reopened.

repo: dotnet/source-build


text:
The tarball is not only made up of source codes

Can I build from source without internet from the tarball I received, but without the archived packages (artifacts)?
Packages in packages / archive are not source codes
Can't sdk be built entirely from source codes alone?

Hi. I think https://github.com/dotnet/source-build/issues/1930 answers this in more detail. Summary: no, you need a set of working SDK/artifacts to build .NET. Once you have built source-build (and source-build-reference-packages) once, you can use that to build subsequent releases from sources (only). We do this in Fedora where we built (bootstrapped) .NET 5.0 once and are now using our self-built .NET 5.0 to build subsequent versions.
Please let us know if there's additional information that you need.

The only two directories that contain binaries are packages/archive and .dotnet. Remove those two and you're left with only source code.
To build it you need a dotnet-sdk archive, a Private.SourceBuilt.Artifacts and a Package.SourceBuild.ReferencePackages. The former two are built by this repo and can only be built with themselves, but the last one can be built from source, with this repo: https://github.com/dotnet/source-build-reference-packages (see the pre-arcade branch)

[Triage] Thanks to @omajid and @mid-kid for providing answers.  Closing but feel free to continue discussing.

authors: MichaelSimons deflarten mid-kid omajid


text:
Smarter behavior in sln with multitargetted projects

Hello,
I develop a library which targets multiple .Net core frameworks/standards. In the same solution I have a samples folder for example projects that target only netcoreapp2.2.
If the library project uses <TargetFrameworks>netcoreapp3.0;netcoreapp2.2</TargetFrameworks> and a sample project uses <TargetFramework>netcoreapp3.0</TargetFramework> everything is good.
However if a sample project only targets netcoreapp2.2 and has a <ProjectReference> to the library VS Code flags all sorts of errors in the sample project. Omnisharp-vscode seems to only see the referenced project as targettiing the first framework listed in its <TargetFrameworks> entry.
This has left me in a position where my project has hundreds of errors in "normal" state while opened in VSCode but where a dotnet build runs perfectly on the command line.
If it helps my project is https://github.com/Finbuckle/Finbuckle.MultiTenant
Clone that and open the sln in VSCode and you will see what I mean.

Also I'll add that the obj folders some target frameworks are flagged for errors but the first listed target framework's obj folder is correctly ignored,

Yeah, this is a pretty big project system-level feature. Currently OmniSharp just loads the first target specified. It doesn't have a robust system for handling multiple targets like the Visual Studio project system does.

Thanks for the info, I was able to fix my issue by rearranging my target frameworks so the newest framework is first.

Hi !
As I'm running into the same kind of using on one of my project ... Is there any news on addressing this issue ?
I'm about to move away from Windows as my dev OS and this is very critical to me.
Thanks in advance for your answer and keep up the good work

This is an O# issue. If you are still running into this problem, please open a new issue at https://github.com/OmniSharp/omnisharp-roslyn/issues

authors: AndrewTriesToCode JoeRobich achandlerwhite candoumbe cartermp xqrzd

repo: dotnet/vscode-csharp


text:
OmniSharp doesn't load on my systems if the root folder has a C# submodule

Issue Description
If I have a project with a Git submodule, OmniSharp doesn't work - it doesn't even seem to load (OmniSharp Log window is empty)
I can reproduce this reliably on two machines that are similar (one is a Manjaro VM and one is Manjaro dual-boot)
Steps to Reproduce

git clone https://github.com/deengames-prototypes/haven-island
git submodule update --init
Open VSCode to the root of haven-island

Expected Behavior
OmniSharp should run as normal.
Actual Behavior
OmniSharp doesn't even load; no autocorrect, etc.
Logs
OmniSharp log
Post the output from Output-->OmniSharp log here
(Empty)
C# log
Post the output from Output-->C# here
(Also empty)
Environment information
VSCode version: 1.42.1
C# Extension: 1.21.12
Mono Information
        OmniSharp using global mono :6.4.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.1.100
 Commit:    cd82f021f4
Runtime Environment:
OS Name:     manjaro
OS Version:
OS Platform: Linux
RID:         arch-x64
Base Path:   /usr/share/dotnet/sdk/3.1.100/
Host (useful for support):
Version: 3.1.1
Commit:  a1388f194c
.NET Core SDKs installed:
3.1.100 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-vscode
1.21.12

Csharp-ASPNETCore
rahulsahay
1.11.0

godot-tools
geequlim
1.0.3

mono-debug
ms-vscode
0.15.8

powershell
ms-vscode
2020.1.0

python
ms-python
2020.2.64397

vscode-nxunit-test-adapter
wghats
0.1.3

vscode-test-explorer
hbenl
2.17.0

@nightblade9 Can you please share the OmniSharp log from the Output pane? I followed your steps and was able to load

@nightblade9 Can you please share the OmniSharp log from the Output pane? I followed your steps and was able to load

As I said, there is no output - both C# and Omnisharp Log are empty under the Output pane.

@nightblade9  Could you uninstall and reinstall the C# extension perhaps?

@JoeRobich I tried that again just now, it doesn't change anything. (Uninstall, reload, reinstall, close VSCode, re-open VSCode, same behaviour).
Perhaps it's something to do with my installations of Mono, MonoDevelop, etc.? I'm not sure - VSCode behaves fine for non-submodule repos (eg. if I open a window in the root of source/Puffin, everything works fine.

Can you try disabling all other extensions? Empty output is very unusual for us. =p

I uninstalled all extensions, and reinstalled just the C# one. Same behaviour.

If you're interested in a more rapid exchange, I'm on Discord right now.

User: Nightblade#3155
Server: https://discord.gg/frKXYtG

I fired up my trusty Ubuntu VM and wasn't able to reproduce what you are seeing.  Can you share the Log (Extension Host) output?

Can you share the Log (Extension Host) output?

[2020-02-21 20:33:58.294] [exthost] [info] extension host started
[2020-02-21 20:33:58.412] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.csharp {"startup":false,"extensionId":{"value":"ms-vscode.csharp","_lower":"ms-vscode.csharp"},"activationEvent":"onLanguage:csharp"}
[2020-02-21 20:33:58.416] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.12/dist/extension
[2020-02-21 20:33:58.622] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-02-21 20:33:58.628] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-02-21 20:33:58.631] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-02-21 20:33:58.632] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/emmet/dist/extension
[2020-02-21 20:33:58.652] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.git","_lower":"vscode.git"},"activationEvent":"*"}
[2020-02-21 20:33:58.652] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/git/dist/main
[2020-02-21 20:33:58.732] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-02-21 20:33:58.733] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/merge-conflict/dist/extension
[2020-02-21 20:33:58.737] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-02-21 20:33:58.740] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/search-result/dist/extension.js
[2020-02-21 20:33:58.741] [exthost] [info] ExtensionService#_doActivateExtension vscode.vscode-account {"startup":true,"extensionId":{"value":"vscode.vscode-account","_lower":"vscode.vscode-account"},"activationEvent":"*"}
[2020-02-21 20:33:58.741] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/vscode-account/dist/extension.js
[2020-02-21 20:33:59.398] [exthost] [info] eager extensions activated
[2020-02-21 20:40:58.454] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-server-ready {"startup":false,"extensionId":{"value":"vscode.debug-server-ready","_lower":"vscode.debug-server-ready"},"activationEvent":"onDebugResolve"}
[2020-02-21 20:40:58.454] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/debug-server-ready/dist/extension
[2020-02-21 20:40:58.468] [exthost] [info] ExtensionService#_doActivateExtension vscode.grunt {"startup":false,"extensionId":{"value":"vscode.grunt","_lower":"vscode.grunt"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2020-02-21 20:40:58.468] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/grunt/dist/main
[2020-02-21 20:40:58.470] [exthost] [info] ExtensionService#_doActivateExtension vscode.gulp {"startup":false,"extensionId":{"value":"vscode.gulp","_lower":"vscode.gulp"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2020-02-21 20:40:58.470] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/gulp/dist/main
[2020-02-21 20:40:58.472] [exthost] [info] ExtensionService#_doActivateExtension vscode.jake {"startup":false,"extensionId":{"value":"vscode.jake","_lower":"vscode.jake"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2020-02-21 20:40:58.472] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/jake/dist/main
[2020-02-21 20:40:58.473] [exthost] [info] ExtensionService#_doActivateExtension vscode.npm {"startup":false,"extensionId":{"value":"vscode.npm","_lower":"vscode.npm"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2020-02-21 20:40:58.473] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/npm/dist/main
[2020-02-21 20:40:58.477] [exthost] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"extensionId":{"value":"vscode.typescript-language-features","_lower":"vscode.typescript-language-features"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2020-02-21 20:40:58.477] [exthost] [info] ExtensionService#loadCommonJSModule file:///opt/visual-studio-code/resources/app/extensions/typescript-language-features/dist/extension

Sorry, I don't have more time to look at this tonight.
You could try changing the logging for OmniSharp to debug but it seems like things are failing before it gets loaded.

You could look at the Electron developer tools (Help > Toggle Developer Tools) console to see if anything logged there (unlikely)
You can post a picture of the ProcessExplorer (Help > Open Process Explorer) so we can see if OmniSharp is running

I couldn't figure out how to open Omnisharp Logging Level, can you provide more instructions?
The devtools / JS console in VSCode shows this:
[Extension Host] rejected promise not handled within 1 second: undefined
t.log @ /opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:259
/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js:1597   ERR An unknown error occurred. Please consult the log for more details.

Process explorer doesn't show anything I can identify as OmniSharp:

When I just open puffin:

VSCode doesn't show any errors in the JS console / devtools
Process Explorer shows mono --assembly-loader=strict /home/nightblade/.vscode/extensions/ms-vscode.csharp-1/... under window (Welcome - Puffin - Visual Studio Code) > extensionHost

I found a work-around in this issue: F1 > OmniSharp: Select Project > HavenIsland.sln and everything loads/runs as expected.
@JoeRobich when you get a minute, can you please try something to verify my hypothesis: from the cloned root, run git submodule update --init and then close and re-open VSCode to see if the problem reproduces.
I am 100% sure this worked before (for weeks) - I don't know why it's suddenly breaking on a multi-solution project. But that same GitHub issue (or another one) indicates that VSCode doesn't work with multi-root solutions (I have two .sln files in this workspace).

Closing as issue was resolved.


text:
Send named pipe name to roslyn and razor

Update Roslyn to: https://dev.azure.com/dnceng/internal/_build/results?buildId=2484529&view=results
Update Razor to: https://dev.azure.com/dnceng/internal/_build/results?buildId=2484091&view=results

@ryzngard looks like there is some issue with override completion on .net8 linux (consistently failing).  Most likely caused by some roslyn change.  I don't think I'll be able to look until next week (I'm out starting early afternoon tomorrow).  I'm not sure the insertion can go in with the bug

@ryzngard looks like there is some issue with override completion on .net8 linux (consistently failing).  Most likely caused by some roslyn change.  I don't think I'll be able to look until next week (I'm out starting early afternoon tomorrow).  I'm not sure the insertion can go in with the bug

Can you force merge or do I need to ask a higher authority (as if there is one 😅)

@ryzngard looks like there is some issue with override completion on .net8 linux (consistently failing).  Most likely caused by some roslyn change.  I don't think I'll be able to look until next week (I'm out starting early afternoon tomorrow).  I'm not sure the insertion can go in with the bug

Can you force merge or do I need to ask a higher authority (as if there is one 😅)

I can force merge this, but I don't think we should.  There is definitely a regression caused by the roslyn changes that breaks override completion on linux.  Until we figure out why and to what extent, I don't think we can release a change with this.

Oh sorry, misread on mobile. Understood. I'll see if I can take a few minutes to look otherwise I can coordinate with you

authors: dibarbet ryzngard


text:
no have title

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

Can you please provide more information about the issue you're having?

repo: dotnet/website-feedback


text:
Feat en localization

EN localization changes
Description
Changes to Locales/en.json to better match English language standards

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant elightcap

repo: dotnetcore/BootstrapBlazor


text:
🛑 Biseri-jadrana.si is down

In 1168f88, Biseri-jadrana.si (https://www.biseri-jadrana.si/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Biseri-jadrana.si is back up in afa91af.

repo: dotsi/bitamiuptime


text:
🛑 Biseri-jadrana.si is down

In e2ce0a4, Biseri-jadrana.si (https://www.biseri-jadrana.si/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Biseri-jadrana.si is back up in ab2ff86.


text:
Update logback-classic to 1.5.3

About this PR
📦 Updates ch.qos.logback:logback-classic from 1.4.14 to 1.5.3
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.qos.logback", artifactId = "logback-classic" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback", artifactId = "logback-classic" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #167.

repo: doubleloop-io/applied-fp-workshop-scala


text:
export states

Usage: pummel export --states SORT_DIR
(Presumably I did something slightly wrong with git--what's up with Merge pull request 1 from ...?)

Not exactly sure, bit it probably has to do with you doing your PRs from master. Better practice is to do it on a separate branch off of my master for each PR.
Will look at these changes in a bit.

CLI for this added in 5ff9876

authors: dougalsutherland flaxter

repo: dougalsutherland/pummeler


text:
Error Converting Value "LOOM" to type 'System.Guid'

Hello all,
Just trying out the various services and hit across this problem, seems pretty straight forward but just wanted to report it.
When I use the CoinbaseAccountsService.GetAllAccountsAsync method, I get the above error. On inspection of the json data, it's clear to see that some of the accounts have, as expected, GUIDs but other accounts seem to have the actual currency value set as the id.
Here's a snapshot of the data that's being returned from the api.
{
        "id": "27386189-c528-5988-89f0-114389046db3",
        "name": "BTC Wallet",
        "balance": "0.00000000",
        "currency": "BTC",
        "type": "wallet",
        "primary": true,
        "active": true,
        "available_on_consumer": true,
        "hold_balance": "0.00",
        "hold_currency": "GBP"
    },
    {
        "id": "LOOM",
        "name": "LOOM Wallet",
        "balance": "0.00000000",
        "currency": "LOOM",
        "type": "wallet",
        "primary": false,
        "active": true,
        "available_on_consumer": false,
        "hold_balance": "0.00",
        "hold_currency": "GBP"
    }

The results contain 26 accounts in total. 11 seem to be classic accounts (LTC Wallet, ETH Wallet) with the expected GUIDs, the remaining ones seem to be somewhat newer currencies all with IDs representing their currency, e.g LOOM, MANA, DNT, CVC, ZIL etc. Looks like coinbase have perhaps ditched the GUID approach for a more human-readable id?
I was able to avert this error locally by switching out the CoinbaseAccount Id property type to string followed by updating the associated tests. Of course this could be troublesome for existing implementations.

hi @ThatBlokeCalledJay thanks for catching this. I don't really understand why these are no longer all the same GUID type. Their documentation makes no note of this either and it seems to be a fairly new thing. I think switching the id to a string is the only option here even though it's breaking.
change is made here https://github.com/dougdellolio/coinbasepro-csharp/commit/da0245c4dd9c3f39ea85334cc9047fb6836770a0 and will go out with the next release.
much appreciated!

authors: ThatBlokeCalledJay dougdellolio

repo: dougdellolio/coinbasepro-csharp


text:
🛑 VNUX.dev is down

In d445ab5, VNUX.dev (https://vnux.dev) was down:

HTTP code: 429
Response time: 257 ms

Resolved: VNUX.dev is back up in dbd0777.

repo: dougdragon/uptime


text:
ROSInitException: time is not initialized,Exception AttributeError: "TransformListener instance has no attribute 'tf_sub'"

Hello! I use the kinova_j2s7s300 to reproduce the experiment, and encounter the following error when run the kinova_open_loop_grasp.py:
rospy.exceptions.ROSInitException: time is not initialized. Have you called init_node()?
Exception AttributeError: "TransformListener instance has no attribute 'tf_sub'" in <bound method TransformListener.del of <tf2_ros.transform_listener.TransformListener instance at 0x7fc27fa29ef0>> ignored
After  reconneting the robot, the problem still exists. I run the kinova_robot.launch,wrist_camera.launch and kinova_open_loop_grasp.py in the system environment (ubuntu16.04, python2.7) and run run_ggcnn.py in the anaconda virtual environment created for the implement of tensorflow. Do you have other suggestions for solving the problem?

Hey @Assets01
looks like something changed in TF that broke this old code.  I pushed a quick change that should fix it so that the TF buffer is initialised after the node.  I'm not in a position to test this at the moment so let me know if this doesn't work.

Hey @Assets01
looks like something changed in TF that broke this old code. I pushed a quick change that should fix it so that the TF buffer is initialised after the node. I'm not in a position to test this at the moment so let me know if this doesn't work.

Hi!, sorry for taking so long to reply, I will try it and reply as soon as possible.


text:
Original air date

Hi, enjoying the service so far.
I think it would be nice to add the original posting date in the show-notes, if possible.
Thanks!

Hey, glad you're enjoying it! And thanks for the suggestion. It's actually already supposed to do this, but it's not working with some podcast feeds. I'll try to track down the problem.
Here's what it's supposed to look like when it works:

There are (at least) three RSS elements that might be displayed as show notes in a podcast app. If more than one is present, Overcast will display only one in this order of preference: <content:encoded>, <description>, <itunes:summary>. Other podcast apps may differ.
Currently, only <description> is getting updated with the original publication date.

Hi Doug, sorry for the delay in getting back to you.
That original air date now shows for the podcast, which is great! I added
another podcast (Cortex on Relay FM) and it seems like the shownotes in the
original RSS feed are being swapped with one of the others that you
mentioned. Not a big deal to me since I open them in a web browser anyways,
but wanted to let you know in case it's an easy fix.
Appreciate the service!
On Sat, Feb 17, 2024 at 1:57 PM Doug Waldron @.***>
wrote:

@nbousfield https://github.com/nbousfield I just published an update
that should fix this issue. Could you please test it and report back to let
me if it's working for you? Your existing podcast feeds should update the
next time you refresh the feed, which might happen automatically, or you
might have to force each feed to refresh, depending on what app you use.
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/dougwaldron/podcast-rewind/issues/73#issuecomment-1950406545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEDKGKGVVTANMB6ZOEAKJTYUERTHAVCNFSM6AAAAABDFZC6DOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGQYDMNJUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @nbousfield, I'm not sure what you mean, could you share an example of what you're seeing or a screenshot maybe? Thanks.

authors: dougwaldron nbousfield

repo: dougwaldron/podcast-rewind

license: Unlicense


text:
Stuck at Block 10000H

Hi there
Not sure how to debug this it just stops at block 10000H.
I had a look at database tables  and they are empty too
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Creating initial db schema
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Entering fresh mode: no indices
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Adjusting schema to mode: fresh-bulk
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Entering fresh mode: minimum indices
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Adjusting schema to mode: bulk
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Entering normal mode: all indices
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Adjusting schema to mode: normal
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Entering fresh mode: minimum indices
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Adjusting schema to mode: bulk
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Entering fresh mode: no indices
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Adjusting schema to mode: fresh-bulk
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::db::pg] Adjusting schema to mode: fresh-bulk
[2022-02-17T18:34:52Z INFO  bitcoin_indexer] Node chain-head at 146362H
[2022-02-17T18:34:52Z INFO  bitcoin_indexer::node::prefetcher] Starting block fetcher starting at genesis block

Block 0H: ceac4f4dc5aa01eb7fe5b36410cd7a1cb0f89856c76401a69d1b30fb8bc0e3bf
Block 1000H: 19c1b92ac5ac4457ca873a7d1e40a675913d7cbe102f208b72407984721c44ba
Block 2000H: 4dd81876e67fe947c2088ef002bb1dd3d9f64add4339af736b9948d9fa7ebd1f
Block 3000H: 4315a14679fe131c94404784fc5f7012e9ab951cbc0e464bb105a4f0e555ce39
Block 4000H: ee39880e4fbc5b1f4a0f4310a8410d491e3c5833c03c5d7027217da4328efcd3
Block 5000H: 955c292a31ef8e472736f983e9205c38510fdc8f96a4641f1cf0832e3971c77e
Block 6000H: 8fc3873307839882d2f5ac58b6849ee66c58286cb518baf646528de3116e70d4
Block 7000H: d38dee425335979c5047dd761692502459cc1e12736ec7ff2d53b718569f984e
Block 8000H: 370780d486dfe5354fc8937e48dd46c3172dc30dd43f7e1f915524e47ec6856b
Block 9000H: 9182dccdc36aaf4aaa8ade8e25a9ffe955216572ce07414a42157699014a2dfc
Block 10000H: 404abb998428aa89a7bb75baa8a1a6f463e8f28b9e909616ad1c71143b0f3df6

Sorry wrong chain , would this work with altcoins ?

repo: dpc/rust-bitcoin-indexer


text:
Reset all arrays in clearCanvas

This fixes changing the color and line weight after clicking the clear button

This is probably going to be superseded by Cheny's rework of the drawing system.

Yeah, there's probably no need to merge this.

authors: Zarel divergentdave dpitch40


text:
🛑 File Service is down

In abfabfc, File Service (https://files.dplayzgames06.tk) was down:

HTTP code: 530
Response time: 1143 ms

Resolved: File Service is back up in 0b62eaf after 13 minutes.

repo: dplayz/status


text:
Runtime error when formatting a 11,000 line JSON object

Describe the bug
WARNING: Formatting is slow for /.../bla.ts
Error formatting /.../bla.ts. Message: RuntimeError: unreachable
    at rust_oom (<module>[2564]:0x2082f4)
    at __rg_oom (<module>[2629]:0x209386)
    at __rust_alloc_error_handler (<module>[950]:0x197bef)
    at alloc::alloc::handle_alloc_error::h210cb584d6b73817 (<module>[2628]:0x209378)
    at dprint_core::formatting::printer::Printer::create_save_point::hc25a66a6d7763c48 (<module>[2321]:0x1f744e)
    at dprint_core::formatting::printer::Printer::print::h54956938edc782af (<module>[2320]:0x1f6d57)
    at dprint_core::formatting::print::print_with_allocator::h429b9a976822ed5f (<module>[2379]:0x1fc881)
    at dprint_plugin_typescript::format_text::format_text::he3704691515788c7 (<module>[879]:0x185663)
    at format (<module>[885]:0x186aaf)
Had 1 error(s) formatting.

dprint-plugin-typescript version: 0.51.0
Input Code
roughly:
/* Some comment */
export const ARR: object[] = [
  deeply nested JSON object here that sprawls out to 11,000 LOC after formatting is done (it actually successfully formats in the playground; file size is ~ 180KB)
];

I managed to reproduce this issue with a similar stack trace that also suggests it has something to do with SavePoint allocation.

Stack trace
WARNING: Formatting is slow for /.../bla.ts
Error formatting /.../bla.ts. Message: RuntimeError: unreachable
    at rust_oom (<module>[28566]:0x89fe73)
    at __rg_oom (<module>[28632]:0x8a0f0a)
    at __rust_alloc_error_handler (<module>[14369]:0x5d73d2)
    at alloc::alloc::handle_alloc_error::h7e572dc94824aec0 (<module>[28631]:0x8a0efc)
    at alloc::raw_vec::RawVec<T,A>::allocate_in::h7bedab50d38c4625 (<module>[27571]:0x870406)
    at alloc::raw_vec::RawVec<T,A>::with_capacity_in::h2c11cdc9238c5068 (<module>[27616]:0x873ee7)
    at alloc::vec::Vec<T,A>::with_capacity_in::hbe12bb9cd214986b (<module>[27248]:0x86388c)
    at <T as alloc::slice::hack::ConvertVec>::to_vec::hd2030c85f59b92b1 (<module>[26568]:0x843e0f)
    at alloc::slice::hack::to_vec::had323318b5e1aecc (<module>[27654]:0x874ea4)
    at alloc::slice::<impl [T]>::to_vec_in::h6293782134c6653f (<module>[26569]:0x843e89)
    at <alloc::vec::Vec<T,A> as core::clone::Clone>::clone::h81b4dfbb9049a460 (<module>[27273]:0x8644f1)
    at dprint_core::formatting::printer::Printer::update_state_to_save_point::h5de2a1fa79d8dead (<module>[28071]:0x8874bd)
    at dprint_core::formatting::printer::Printer::handle_info::hb81ebc04c15f5235 (<module>[28064]:0x885c39)
    at dprint_core::formatting::printer::Printer::handle_print_node::h55df3fad81921239 (<module>[28055]:0x88489b)
    at dprint_core::formatting::printer::Printer::inner_print::h8636c6873157a580 (<module>[28052]:0x884009)
    at dprint_core::formatting::printer::Printer::print::h2106ee4f9f3144e5 (<module>[28051]:0x883dfd)
    at dprint_core::formatting::print::print_with_allocator::ha65371126ab5aaa1 (<module>[27545]:0x86ef48)
    at dprint_core::formatting::print::format::{{closure}}::hc822682b15471c3b (<module>[14143]:0x5ca8e8)
    at dprint_core::formatting::utils::thread_local_bump_allocator::with_bump_allocator_mut::{{closure}}::h3ca08085a69f9948 (<module>[8020]:0x28a40f)
    at std::thread::local::LocalKey<T>::try_with::ha79e732553774186 (<module>[8741]:0x2bfb6e)
    at std::thread::local::LocalKey<T>::with::he0b5a83d6864c190 (<module>[8740]:0x2bfa64)
    at dprint_core::formatting::utils::thread_local_bump_allocator::with_bump_allocator_mut::hb4d7977f86e93377 (<module>[8019]:0x28a3a5)
    at dprint_core::formatting::print::format::he4b6ad3685a92b4d (<module>[14142]:0x5ca889)
    at dprint_plugin_typescript::format_text::format_text::h256f13bdc4a57cdf (<module>[14316]:0x5d5642)
    at <dprint_plugin_typescript::wasm_plugin::TypeScriptPluginHandler as dprint_core::plugins::plugin_handler::PluginHandler<dprint_plugin_typescript::configuration::types::Configuration>>::format_text::h987229111c55cc3f (<module>[5366]:0x1ccce9)
    at format (<module>[8758]:0x2c14e2)
Had 1 error(s) formatting.

I also found that applying the following diff will allow formatting to complete without encountering an allocation error.
diff --git a/crates/core/src/formatting/printer.rs b/crates/core/src/formatting/printer.rs
index 39bf6bb8..32ba3f29 100644
--- a/crates/core/src/formatting/printer.rs
+++ b/crates/core/src/formatting/printer.rs
@@ -259,7 +259,7 @@ impl<'a> Printer<'a> {
     }

     let next_node = self.current_node.as_ref().unwrap().get_next();
-    self.possible_new_line_save_point = Some(self.create_save_point("newline", next_node));
+    self.possible_new_line_save_point = None
   }

   #[inline]

To me this suggests that processing bla.ts results in a large amount of PossibleNewLine and/or SpaceOrNewLine signals being produced. Which then leads to bump allocating many of these possible newline save points.
Unfortunately though, this isn't a proper solution. I will continue investigating and hopefully have a patch or suggested fix shortly.

Nice find @joshleeb!

authors: joscha joshleeb

repo: dprint/dprint-plugin-typescript


text:
Missing space for export default function doX() with spaceBeforeParentheses

Describe the bug
Missing space after the function name when using spaceBeforeParentheses for export default function doX() statement.
https://dprint.dev/playground/#code/GYVwdgxgLglg9mABAgpgCgJSIN4ChEGIBOKUIRSAjLgL664oAeADnEVIqJLAolAO5xMOfIRJkKiAEy16TVu0QATFMACGIADYcu0eEigALEuix5CxUuSQBmWkA/config/N4KABGBEBmCuB2BjALgSwPbwCIFNEBsBDAJ0LUwDoBnAB0MRwCEdp1icAFEneZACxxVBkAFxhkxWDhABfEEA/plugin/typescript
Input Code
export default function three() {
    return 3
}

Expected Output
export default function three () {
    return 3
}

Actual Output
export default function three() {
    return 3
}

The problem is actually with swc and the fact that it reports the exported default function declaration as a function expression. Opened an issue.

This is expected because that's controlled via "functionExpression.spaceBeforeParentheses": true. It's a function expression and not declaration at export default ... (not a bug in swc). It's why you can do export default function() {} without a name.
That said, for formatting concerns, this is often considered to be like a declaration and so maybe this option should change the behaviour of that too.

Oh wait, you might be right. I'll look into it more after I finish eating.

Yeah, this should be treated as a function declaration https://262.ecma-international.org/14.0/#prod-ExportDeclaration

authors: ad-si dsherret todor-a


text:
Removed super().init from registry.py file

Proposed change

Removed super().init from registry.py file to fix the issue #1200
The EntityLoader is not inherited by any base class. So removed the super().init(*args, **kwargs) line from init method to avoid type error.
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency upgrade (version update)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

Coverage: 99.737% (+5.0e-05%) from 99.737% when pulling 34315a02790007bf0ae619681c6e99fe1bc9529f on GobinathBaskaran:type_error_fix into c548af93873a8ae81c4bf353a15e1ce3baec59bd on dr-prodigy:beta.

thanks @GobinathBaskaran !

The v0.25 introduced the lazy loading mechanism which made some python-holidays use cases backward incompatible. It's still allows using top-level import for consuming the holidays data (you betcha!):
import holidays
print(holidays.US(years=2023))

However, if you're going to use a class for inheritance you must import it from its original location, e.g.,
from holidays.countries.united_states import US
# from holidays.countries import US works too

class MyHolidays(US):
  pass

MyHolidays()

works fine whereas
from holidays import US

class MyHolidays(US):
  pass

MyHolidays()

version does not work that way any longer.
As the proposed PR won't resolve the root cause I'm not merging it (at least for now).

@arkid15r Thanks for letting me know. Can you please close this PR.

repo: dr-prodigy/python-holidays


text:
🛑 gorzdrav.org is down

In a098a4a, gorzdrav.org (https://gorzdrav.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: gorzdrav.org is back up in b14109d.


text:
🛑 gorzdrav.org is down

In bfd9b6d, gorzdrav.org (https://gorzdrav.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: gorzdrav.org is back up in ad6dac0.


text:
Srollbars still Bright white

Srollbars still Bright white

this is kinda fixed in https://github.com/dracula/mailspring/pull/17

authors: Keloran NicTanghe

repo: dracula/mailspring


text:
Syntax errors

I'm getting the following error when launching example.js.

What version of node are you using?

I could solve it by using version 4.x

Yes, since the readme says in bold "This will only work with Node >= 4.0.0".

I had v5 before.

Are you using the newest version of parentbot?
Also could you show the whole error stack since some of it gets cut off?

Yes, I have the newest version.
I'm abroad now so I can't send you the error.
Sent from my iPad

On 25 Jan 2016, at 00:12, Kyle Smith notifications@github.com wrote:
Are you using the newest version of parentbot?
Also could you show the whole error stack since some of it gets cut off?
—
Reply to this email directly or view it on GitHub.

Closing due to inactivity.

authors: dragonbanshee steeveensib

repo: dragonbanshee/node-steam-parentbot


text:
Why we need static and single TypePool?

Q: 为什么使用静态或者全局类型池？(Why we need static and single TypePool?)
A: 我不反对局部或临时类型池的设计，你可以 fork 这个项目自行实现，它们对于内存更加友好（但也只是微小优势而已），但在我看来，全局类型池在多方面更好：

它能够显式连接 Type 和它的 Item View，能够在同一地方统一 register，这将避免分散，带来很好的直观性和可管理性；
一个应用不会有超级大量的类型定义，类型 class 和 provider 对象都是非常轻薄的对象，直接静态存于内存，并不会导致内存泄漏和大的内存占用问题，几乎可以忽略；
至于要不要支持 optional 的局部类型池参数，我也是不喜欢支持的，前面说了，这是没必要的，而且若是可选（optional）也会使用户疑惑：“到底要还是不要？”

因此我喜欢和坚持使用全局静态类型池，它不会带来什么问题，而且好处诸多，有人给我提交了使用反射的方法来自动获取类型连接，为了避免性能话题，我不喜欢反射，而且将类型连接变得复杂和不可见性未必是好事。我一直坚持的原则是：写简单的代码，写可读的代码，实现复杂的需求（你们看我的代码是不是感觉很自然而然而且可读性十分好？）

#15

Supported local type pool! #29

repo: drakeet/MultiType


text:
I18n human_attribute_name confilct

When human_attribute_name is called, it checks ancestors of decorated model using this code
    def lookup_ancestors
      self.ancestors.select { |x| x.respond_to?(:model_name) }
    end

Then, it calls #model_name of all found ancestors including Draper::Decorator and crashes
I fixed it by delegating self.lookup_ancestors to object_class in my ApplicationDecorator,  but not sure it is   a good idea

@JelF Are you still experiencing this issue? If so, can I get more details (e.g. draper version, rails version, stack trace, etc.)? I can't seem to reproduce it at all:

@codebycliff no more, seems it have been fixed

Sounds good. I will close it then.

authors: JelF codebycliff

repo: drapergem/draper


text:
Homebrew and /usr/local

It has always bugged me that Homebrew installs itself into /usr/local and claims ownership over it instead of root:wheel. For the longest time, Homebrew’s git repository was installed directly in that path (nowadays in /usr/local/Homebrew). Nevertheless, Homebrew still insists on changing the ownership of /usr/local/bin and /usr/local/lib, which means that the installing user can install any binaries or libraries without additional privileges.
==> The following existing directories will be made group writable:
/usr/local/bin
/usr/local/include
/usr/local/lib
/usr/local/lib/pkgconfig
==> The following existing directories will have their owner set to my_admin_account:
/usr/local/bin
/usr/local/include
/usr/local/lib
/usr/local/lib/pkgconfig
==> The following existing directories will have their group set to admin:
/usr/local/bin
/usr/local/include
/usr/local/lib
/usr/local/lib/pkgconfig

Since /usr/local/bin takes precedence over /usr/bin and /bin (in /etc/paths), any malicious program could simply put binaries or libraries there and effectively ‘overwrite’ the ones installed in other system paths.
$ cat /etc/paths
/usr/local/bin
/usr/bin
/bin
/usr/sbin
/sbin

I am of the opinion that this is a bad practice and it should be mentioned explicitly. I personally have installed Homebrew in ~/.homebrew, despite their advice against it. I have not come across any problems so far.

How do you install binary files that are already provided by MacOS (e.g. git or ruby) if homebrew does not take precedence over /usr/bin and /bin?

@hidi: export PATH=“/usr/local/bin:$PATH”

You recommend giving homebrew priority over /usr/bin and /bin. But that's exactly what this guide is supposed to prevent. So this cannot be a solution.

authors: Eitot hazcod hidisem627

repo: drduh/macOS-Security-and-Privacy-Guide


text:
WIP Issue #177 - Adding an authentication middleware API

Draft of an Authentication middleware API inspired from Http4s.
The AuthenticationAdvanced example shows the proposed design.
Missing tests and documentation.

Took note of all the remarks, I'll take care of it later. Thanks for taking the time to review :).

This is fixed in RC 18

authors: remiguittaut tusharmath


text:
Default to First Scene if None

I generated a .gltf file using another tool. When processing it with gltf-to-3d-tiles, I found that self.scene = None in Slicer.__init__().
This is easily fixed by setting self.scene = 0 to make the tool resilient, though it is probably an error in the previous tool that I used that caused no scene to be set in that resulting data.
A high-level error message could be preferable to this:
File "...\gltf-to-3d-tiles\gltf\slicer.py", line 24, in __init__
    root = self.scenes[self.scene].nodes[0]
TypeError: list indices must be integers or slices, not **NoneType**

There is precedent for defaulting to the first scene in the glTF spec:
https://github.com/KhronosGroup/glTF/issues/815

fixed in commit 218172d11c54d63be2cc06f7753fafbe397f6226


text:
Add depend strategy for reflections

Describe the enhancement requested
Currently, when creating a reflection, dbt-dremio triggers it on dremio and instantly finishes the job if the trigger was successful. We would like to be able to configure a strategy that makes dbt wait for the completion of the reflection job on dremio, before marking it as successful and moving on to the next item in the dbt DAG. This would also allow us to get feedback on a reflection failure.
The configuration keyword could be strategy with the possible values depend or trigger, the later being the current and default value.
Justification for this enhancement
This feature would allow for better control and debugging of reflection jobs.

Hi there, any feedback for this issue?

repo: dremio/dbt-dremio


text:
fix travis.yml and improve readme.md

Hello, I can't check every if the code is fully working but this should fix travis work.

Hi @Erim32 , Thank you for your contribution!

Hi @saoron , it's a pleasure, :-)
PS: in your last edit of the README  you ecrase the fix for labels URL.

I wanted to remove Codacy and cleanup a bit. Your help is very much appreciated. Please drop me an email at yossi@dride.io, I would like to get to know you :)

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: dride/Cardigan


text:
watch.BuildUpdate is not exported

Noticed that the watches.config have changed.
I have custom watches and I am using require("@ionic/app-scripts").buildUpdate  which is exported from build rather than watch, which is resulting in triggering build without doing anything else.

Ionic App Scripts Version: 0.0.43

I can do a quick PR if you confirm that the buildUpdate should be exported from the watch rather than build file.

Also, notice that "js" files are not handled within the function. For my project its mandatory to handle this.

Any update re this please? I really want to use the the debounce functionality in 0.0.43

@alan-agius4,
Can you do a PR with what you need?
Thanks,
Dan

repo: driftyco/ionic-app-scripts


text:
Adding (temporary) aliases (or interception) for old commands?

Users testing the v3 beta CLI seem to often forget the new syntax and use old commands:
https://forum.ionicframework.com/t/native-3-x-installing-geolocation-plugin-error/86334
https://stackoverflow.com/questions/43232826/ionic-platforms-update-returns-an-error
https://forum.ionicframework.com/t/error-unknown-plugin-ionic-cli-plugin/85483
ALL documentation out there now will use the old commands, probably forever. Using the old syntax shouldn't lead the users into a non-explained error the CLI certainly could anticipate.
Wouldn't it be useful to map the old commands to a helper that outputs an information about the new syntax but also aliases to the new one (or intercepts the request so at least there is no error)?

Ok seems syntax in CLI v3 beta changed again, so this may not be necessary or useful. Let's see what it settles on.

We are mapping legacy commands to their respective equivalents. build, compile, emulate, platform, plugin, prepare, resources, and run all give helpful error messages.
Let me know if something could be better here. The goal is to prepare ourselves for future platform support, and a command like ionic build is very ambiguous.

authors: dwieeb piotrowski

repo: driftyco/ionic-cli


text:
ion-img exception when using ng-content

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
An exception is being thrown Cannot read property 'isImgsUpdatable' of null ;
Looks like the DI for Content is being lost. Even though it is present in a parent component.
Expected behavior:
No exception
Steps to reproduce:
In my application I have like a layout system which is using ng-content, DI seems to be lost for the Content for a reason or another. I tried to create custom components and tested the DI and it does work. So it doesn't seem to be a limitation from Angular.
http://plnkr.co/edit/WZFafhdPqir6XaR4xIzt?p=preview
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Ionic 2 RC5

In this case, ion-img needs to be a direct child of ion-content. It cannot work with content projection because of how it gets a reference to the ion-content.
Also, ion-img is meant to be used with virtual scroll.

repo: driftyco/ionic


text:
Disable scrolling while swipe to go back

I'm currently working on an app that implements PTR and SwipeToGoBack.
When I swipe to go back to the previous page sometimes I accidentally trigger the PTR because vertical scrolling or the PTR isn't disabled.
I think while swiping back, vertical scrolling should be disabled.
I appreciate any suggestion for a workaround...

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!