[Discussion] Microsoft Security Advisory 4021279: Vulnerabilities in .NET Core, ASP.NET Core Could Allow Elevation of Privilege

Microsoft Security Advisory 4021279: Vulnerabilities in .NET Core, ASP.NET Core Could Allow Elevation of Privilege
Executive Summary
Microsoft is releasing this security advisory to provide information about vulnerabilities in public .NET Core and ASP.NET Core. This advisory also provides guidance on what developers can do to update their applications correctly.
.NET Core & ASP.NET Core are the next generation of .NET that provide a familiar and modern framework for web and cloud scenarios. These products are actively developed by the .NET and ASP.NET team in collaboration with a community of open source developers, running on Windows, Mac OS X and Linux. When .NET Core was released, the version number was reset to 1.0.0 to reflect the fact that it is a separate product from its predecessor -.NET.
Discussion
To discuss the CoreFX Core issues please see https://github.com/dotnet/corefx/issues/19535
Issue CVEs and Description

CVE
Description

CVE-2017-0248
Security Feature Bypass

CVE-2017-0247
Denial of Service

CVE-2017-0249
Elevation of Privilege

CVE-2017-0256
Spoofing

Affected Software
The vulnerabilities affect any Microsoft .NET Core project if it uses the following affected package versions.

Package name
Package versions
Fixed package versions

System.Text.Encodings.Web
<IP_ADDRESS>.0
<IP_ADDRESS>.1

System.Net.Http
<IP_ADDRESS>.1
<IP_ADDRESS>.2

System.Net.Http.WinHttpHandler
<IP_ADDRESS>.0
<IP_ADDRESS>.1

System.Net.Security
<IP_ADDRESS>.0
<IP_ADDRESS>.1

System.Net.WebSockets.Client
<IP_ADDRESS>.0
<IP_ADDRESS>.1

Microsoft.AspNetCore.Mvc
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Core
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Abstractions
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.ApiExplorer
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Cors
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.DataAnnotations
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Formatters.Json
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Formatters.Xml
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Localization
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Razor.Host
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.Razor
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.TagHelpers
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.ViewFeatures
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Microsoft.AspNetCore.Mvc.WebApiCompatShim
1.0.0, 1.0.1, 1.0.2, <IP_ADDRESS>.0, 1.1.1, 1.1.2
<IP_ADDRESS>.3

Advisory FAQ
How do I know if I am affected?
.NET Core and ASP.NET Core have two types of dependencies: direct and transitive. If your project has a direct or transitive dependency on any of the packages and versions listed above, you are affected.
Note: As part of patching ASP.NET Core MVC we update every Microsoft.AspNetCore.Mvc.* package. If, for example, you have a dependency on Microsoft.AspNetCore.Mvc you should update to the appropriate version first (1.0.x should be updated to 1.0.4, 1.1.x should be updated to 1.1.3), and it will also update any other vulnerable  Microsoft.AspNetCore.Mvc dependency.
NET Core Project formats
.NET Core has two different project file formats, depending on what software created the project.

project.json is the format used in .NET Core 1.0 and Microsoft Visual Studio 2015.
csproj is the format used in .NET Core 1.1 and Microsoft Visual Studio 2017.

You must ensure you follow the correct update instructions for your project type.
Direct Dependencies
Direct dependencies are dependencies where you specifically add a package to your project. For example, if you add the Microsoft.AspNetCore.Mvc package to your project then you have taken a direct dependency on Microsoft.AspNetCore.Mvc.
Direct dependencies are discoverable by reviewing your project.json or csproj file.
Transitive Dependencies
Transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if you add the Microsoft.AspNetCore.Mvc package to your project it depends on the Microsoft.AspNetCore.Mvc.Core package (among others). Your project has a direct dependency on Microsoft.AspNetCore.Mvc and a transitive dependency on the Microsoft.AspNetCore.Mvc.Core package.
Transitive dependencies are reviewable in the Visual Studio Solution Explorer window, which supports searching, or by reviewing the project.lock.json file contained in the root directory of your project for project.json projects or the project.assets.json file contained in the obj directory of your project for csproj projects. These files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.
How do I fix my affected application?
You will need to fix both direct dependencies and review and fix any transitive dependencies. The Affected Packages and Versions above should each vulnerable package, the vulnerable versions and the patched versions.

Note: If you are using ASP.NET Core MVC in your projects you should first update the Microsoft.AspNetCore.Mvc version according to the affected versions table above. If you are currently using version 1.0.0, 1.0.1, 1.0.2 or 1.0.3 you should update your package version to 1.0.4. If you are using version 1.1.0, 1.1.1 or 1.1.2 you should update your package version to 1.1.3. This will update every MVC package to the fixed versions.

Fixing Direct Dependencies – project.json/VS2015
Open your project.json file in your editor. Look for the dependencies section. Below is an example dependencies section:
    "dependencies": {
      "Microsoft.NETCore.App": {
        "version": "1.0.1",
        "type": "platform"
      },
     "Microsoft.AspNetCore.Server.Kestrel": "1.0.1",
     "Microsoft.AspNetCore.Mvc ": "1.0.1",
    }

This example has three direct dependencies: Microsoft.NETCore.App, Microsoft.AspNetCore.Server.Kestrel and Microsoft.AspNetCore.Mvc.
Microsoft.NetCore.App is the platform the application targets, you should ignore this. The other packages expose their version to the right of the package name. In our example, our non-platform packages are version 1.0.1.
Review your direct dependencies for any instance of the packages and versions listed above. In the example above, there is a direct dependency on one of the vulnerable packages, Microsoft.AspNetCore.Mvc version 1.0.1.
To update to the fixed package, change the version number to be the appropriate package for your release. In the example, this would be updating Microsoft.AspNetCore.Mvc to 1.0.4.
After updating the vulnerable package versions, save your project.json file.
The dependencies section in our example project.json would now look as follows:
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.1",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.1",
    "Microsoft.AspNetCore.Mvc": "1.0.4",
  }

If you are using Visual Studio and save your updated project.json file, Visual Studio will restore the new package version. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and changing the Show output from drop-down list to Package Manager.
If you are not using Visual Studio, open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependency.
After you have addressed all of your direct dependencies, you must also review your transitive dependencies.
Fixing Direct Dependencies – csproj/VS2017
Open your projectname.csproj file in your editor, or right click the project in Visual Studio 2017 and choose Edit projectname.csproj from the content menu, where projectname is the name of your project. Look for PackageReference nodes. The following shows an example project file:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.1" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.2" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0 " />
  </ItemGroup>
</Project>

The example has two direct package dependencies, as seen by the two PackageReference elements. The name of the package is in the Include attribute, and the package version number is in the Version attribute that is exposed to the right of the package name. The example shows two packages Microsoft.AspNetCore version 1.1.1, and Microsoft.AspNetCore.Mvc.Core version 1.1.2.
Review your PackageReference elements for any instance of the packages and versions listed above. In the example above, there is a direct dependency on one of the vulnerable packages, Microsoft.AspNetCore.Mvc version 1.1.2.
To update to the fixed package, change the version number to the appropriate package for your release. In the example, this would be updating Microsoft.AspNetCore.Mvc to 1.1.3.
After updating the vulnerable package version, save your csproj file. The example csproj would now look as follows:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.1" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Core" Version="1.1.3" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0 " />
  </ItemGroup>
</Project>

If you are using Visual Studio and save your updated csproj file, Visual Studio will restore the new package version. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and changing the Show output from drop-down list to Package Manager.
If you are not using Visual Studio open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependency.
After updating your direct dependencies
Recompile your application.
If after recompilation you see a Dependency conflict warning, you must update your other direct dependencies to the appropriate version.
For example if your project refers to Microsoft.AspNetCore.Routing with a version number of 1.0.1 when you update your Microsoft.AspNetCore.Mvc package to 1.0.4, compilation will throw:
NU1012      Dependency conflict. Microsoft.AspNetCore.Mvc.Core 1.0.4 expected Microsoft.AspNetCore.Routing >= 1.0.4 but received 1.0.1
To fix this, edit the version for the expected package to be the version expected by updating your csproj or project.json in the same way that you used to update the vulnerable package versions.
After you have addressed all of your direct dependencies, you must also review your transitive dependencies.
Reviewing Transitive Dependencies
There are two ways to view transitive dependencies. You can either use Visual Studio’s Solution Explorer, or you can review your project.lock.json (project.json/VS2015) or project.assets.json (csproj/VS2017) file.
Using Visual Studio Solution Explorer (VS2015)
If you want to use Visual Studio 2015, open your project in Visual Studio 2015 and then press Ctrl+; to activate the search in Solution Explorer. Search for each of the vulnerable package names and make a note of the version numbers of any results you find.
For example, searching for Microsoft.AspNetCore.Mvc.Core in an example project that contains a reference to Microsoft.AspNetCore.Mvc shows the following results in Visual Studio 2015.

The search results appear as a tree. In these results, you can see we have found references to Microsoft.AspNetCore.Mvc, version 1.0.1, ` vulnerable version.
The first entry under the References heading refers to the target framework your application is using. This will be .NETCoreApp, .NETStandard or .NET-Framework-vX.Y.Z (where X.Y.Z is an actual version number) depending on how you configured your application. Under your target framework will be the list of packages you have directly taken a dependency on. In this example, the application takes a dependency on Microsoft.AspNetCore.Mvc. Microsoft.AspNetCore.Mvc in turn has leaf nodes that list its dependencies and their versions. In this case the Microsoft.AspNetCore.Mvc package takes a dependency on a vulnerable version of Microsoft.AspNetCore.Mvc.Core and numerous other packages.
Manually reviewing project.lock.json (project.json/VS2015)
Open the project.lock.json file in your editor. We suggest you use an editor that understands json and allows you to collapse and expand nodes to review this file; both Visual Studio and Visual Studio Code provide this functionality.
If you are using Visual Studio the project.lock.json file is “under” the project.json file. Click the right pointing triangle, ▷, to the left of the project.json file to expand the solution tree to expose the project.lock.json file. The following image shows a project with the project.json file expanded to show the project.lock.json file.

Search the project.lock.json file for each of the vulnerable packages, using the format AssemblyName/. If you find any vulnerable assembly name in your search examine the line on which they are found, the version number is after the / and compare to the vulnerable versions table above. For example a search result that shows Microsoft.AspNetCore.Mvc.Core/1.0.1 is a reference to v1.0.1 of Microsoft.AspNetCore.Mvc.Core.   If your project.lock.json file includes references to any of the vulnerable packages shown above then you will need to fix the transitive dependencies.
Fixing transitive dependencies (project.json/VS2015)
If you have not found any reference to any vulnerable packages this means none of your direct dependencies depend on any vulnerable packages or you have already fixed the problem by updating the direct dependencies.
If your transitive dependency review found references to any of the vulnerable packages you must add a direct dependency to the updated package to your project.json file to override the transitive dependency. Open your project.json and find the dependencies section. For example:
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.1",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.Mvc": "1.1.0"
  }

For each of the vulnerable packages your search returned you must add a direct dependency to the updated version by adding it to the project.json file. You do this by adding a new line to the dependencies section, referring the fixed version. For example, if your search showed a transitive reference to the vulnerable System.Net.Security version 4.0.0 you would add a reference to the appropriate fixed version, 4.0.1. Edit the project.json file as follows:
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.1",
      "type": "platform"
    },
    "System.Net.Security": "4.0.1",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.Mvc": "1.1.1"
  }

After you have added direct dependencies to the fixed packages, save your project.json file.
If you are using Visual Studio save your updated project.json file and Visual Studio will restore the new package versions. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and changing the Show output from drop-down list to Package Manager.
If you are not using Visual Studio open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependencies.
Using Visual Studio Solution Explorer (VS2017)
If you want to use Solution Explorer, open your project in Visual Studio 2017, and then press Ctrl+; to activate the search in Solution Explorer. Search for each of the vulnerable package names and make a note of the version numbers of any results you find.
For example, searching for Microsoft.AspNetCore.Mvc.Core in an example project that contains a package that takes a dependency on Microsoft.AspNetCore.Mvc shows the following results in Visual Studio 2017.

The search results appear as a tree. In these results, you can see we have found references to Microsoft.AspNetCore.Mvc.Core version 1.1.2.
Under the Dependencies node will be a NuGet node. Under the NuGet node will be the list of packages you have directly taken a dependency on and their versions. In this example, the application takes a direct dependency on Microsoft.AspNetCore.Mvc. Microsoft.AspNetCore.Mvc in turn has leaf nodes that list its dependencies and their versions. In the example the Microsoft.AspNetCore.Mvc package takes a dependency on a version of Microsoft.AspNetCore.Mvc.ApiExplorer which in turn takes a dependency on a vulnerable version of Microsoft.AspNetCore.Mvc.Core.
Manually reviewing project.assets.json (VS2017)
Open the project.assets.json file from your project’s obj directory in your editor. We suggest you use an editor that understands json and allows you to collapse and expand nodes to review this file; both Visual Studio and Visual Studio Code provide this functionality.
Search the project.assets.json file for each of the vulnerable packages, using the format AssemblyName/. If you find any vulnerable assembly name in your search examine the line on which they are found, the version number is after the / and compare to the vulnerable versions table above. For example a search result that shows Microsoft.AspNetCore.Mvc.Core/1.1.0 is a reference to v1.1.0 of Microsoft.AspNetCore.Mvc.Core.   If your project.assets.json file includes references to any of the vulnerable packages shown above then you will need to fix the transitive dependencies.
If you have not found any reference to any vulnerable packages this means none of your direct dependencies depend on any vulnerable packages or you have already fixed the problem by updating the direct dependencies.
If your transitive dependency review found references to any of the vulnerable packages you must add a direct dependency to the updated package to your csproj file to override the transitive dependency. Open your projectname.csproj file in your editor, or right click on the project in Visual Studio 2017 and choose Edit projectname.csproj from the content menu, where projectname is the name of your project. Look for PackageReference nodes, for example:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.1" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.3" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0" />
  </ItemGroup>
</Project>

For each of the vulnerable packages your search returned you must add a direct dependency to the updated version by adding it to the csproj file. You do this by adding a new line to the dependencies section, referring the fixed version. For example, if your search showed a transitive reference to the vulnerable System.Net.Security version 4.3.0 you would add a reference to the appropriate fixed version, 4.3.1.
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="System.Net.Security" Version="4.3.1" />
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.1" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.3" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0" />
  </ItemGroup>

After you have added the direct dependency reference, save your csproj file.
If you are using Visual Studio, save your updated csproj file and Visual Studio will restore the new package versions. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and changing the Show output from drop-down list to Package Manager.
If you are not using Visual Studio, open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependencies.
Rebuilding your application
Finally rebuild your application, test as you would do normally and redeploy using your favored deployment mechanism.
Other Information
Reporting Security Issues
If you have found a potential security issue in .NET Core, please email details to<EMAIL_ADDRESS>Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including Terms and Conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET Core or ASP.NET Core organizations. These are located at https://github.com/dotnet/ and https://github.com/aspnet/. The Announcements repo for each product (https://github.com/dotnet/Announcements and https://github.com/aspnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:

David Fernandez of Sidertia Solutions for reporting the ASP.NET Core Denial of Service Vulnerability (CVE-2017-0247)
Joonwoo Yu, Hyoung-Kee Choi of Sungkyunkwan University for reporting the .NET Security Feature Bypass (CVE-2017-0248)
Mikhail Shcherbakov for reporting the ASP.NET Core Spoofing Vulnerability (CVE-2017-0256)

Revisions

V1.0 (May 9, 2017): Advisory published.

Is it ok to leave the Microsoft.NETCore.App platform version at 1.1.1 and only update the affected dependencies? The 1.1.2 runtime does not appear to be available on the official download page (https://www.microsoft.com/net/download/core#/runtime).

It's coming, but yes, it's fine to just update the packages. Updating the runtime would force the package update, but it's unnecessary in this case.

I have followed the instructions here and also updated my runtime and sdk to the latest and now I get the below message. Do I have to do anything else or worry about the message?

Restoring NuGet packages...
Detected package downgrade: Microsoft.NETCore.App from 1.1.2 to 1.1.1
 V8.Api (>= 1.0.0) -> Microsoft.AspNetCore.Mvc.Razor.ViewCompilation (>= 1.1.1) -> Microsoft.NETCore.App (>= 1.1.2)
 V8.Api (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1)
Detected package downgrade: Microsoft.NETCore.App from 1.1.2 to 1.1.1
 V8.Mvc (>= 1.0.0) -> Microsoft.AspNetCore.Mvc.Razor.ViewCompilation (>= 1.1.1) -> Microsoft.NETCore.App (>= 1.1.2)
 V8.Mvc (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1)
Detected package downgrade: Microsoft.NETCore.App from 1.1.2 to 1.1.1
 V8.Mvc (>= 1.0.0) -> Microsoft.VisualStudio.Web.CodeGeneration.Design (>= 1.1.1) -> Microsoft.NETCore.App (>= 1.1.2)
 V8.Mvc (>= 1.0.0) -> Microsoft.NETCore.App (>= 1.1.1)
Time Elapsed: 00:00:04.1569238
========== Finished ==========

@flatproject For VS tooling see https://github.com/dotnet/corefx/issues/19535 - someone else has asked and been answered. If that doesn't work for you then ping @mlorbetske
For AspNetCore.MVC packages did you update every version number? You can't mix and match, if, for example you pulled AspNetCore.Mvc up to 1.1.3 then all other packages need to be pulled up too. If these aren't direct dependencies then you'd need to add a direct dependency to the right versions, or figure out which package is pulling in the older versions and contact the author of that package.

@blowdart Great thanks. I hadn't notice the conversation in #https://github.com/dotnet/corefx/issues/19535
Just added the <RuntimeFrameworkVersion>1.1.2</RuntimeFrameworkVersion> to the top property group on all my projects and everything seems good (I have already updated all version numbers to the recommended).

Great, I'm glad you're all sorted :)

How long roughly until the specific details of the underlying cause/fixes will be released? If I recall it was about a week for the DOS issue?

You mean a PR so you can peek at the code? Probably about the same, maybe a little later as build is running right now.

Sorry, yes, that's what I meant. Was just interested as to roughly when we'd be able to look at the fix PR(s). 👍

@blowdart - most new Security Advisory issues have a Mitigation factors section, for example:

If your application is behind a forwarding proxy such is Internet Information Server, Azure Application Gateway or nginx you will not be affected.

Would like to clarify if the issues identified in this advisory are mitigated by using an Azure Application Gateway?
Thx.


update  coveralls to 0.8.23

fix the error of Coveralls when run travis job
Coveralls encountered an exception:
NoMethodError
undefined method `coverage' for #<SimpleCov:...

(https://travis-ci.org/github/sferik/rails_admin/jobs/734694843#L762-L775)

Thanks for the PR, but I've chosen not limiting the upper limit:
https://github.com/sferik/rails_admin/commit/81b5fd31fcbe941a368b8badfe014880b2a4e033#diff-d09ea66f8227784ff4393d88a19836f321c915ae10031d16c93d67e6283ab55fR28


Replace silab COUNTOF by equivalent method

Replace silab COUNTOF by equivalent method

This is defined in the silabs SDK like so:
#define COUNTOF(a) (sizeof(a) / sizeof(a[0]))

@wehale @selissia OK to put that in types_stub.h?

This is defined in the silabs SDK like so:
#define COUNTOF(a) (sizeof(a) / sizeof(a[0]))

@wehale @selissia OK to put that in types_stub.h in terms of licensing?

Yes.

as CHIP defines (and elsewhere uses) ArraySize(), prefer the fix uses that instead of COUNTOF()


Library import SVG files are not proportionally scaled

When creating / adding an image library and importing multiple SVG files, the added images are squashed into a square-shaped image, and are not scaled proportionally.
I created a video capture illustrating the issue. The yellow long bar with red circles gets squashed at first. But if instead dragging the same file onto the "library" area in the UI, the proportions are respected.
https://youtu.be/3BaDbizIlxw
Also, here are the SVG-files, for reproduction
https://www.dropbox.com/sh/qx3kopgon7avdg2/AADEgEq6nZQKN0-6P2TsHxEXa?dl=0

Thanks for the report. This will be fixed in the next release.

Awesone! It's working fine now - no SVG scaling proportion issues in 12.3.2


Save job settings when the trigger starts

This fixes issues where the configVersion doesn't get saved  to the config.xml.
Any changes to the plugin don't get saved until the job changes manually, this way the configVersion will get updated as things get updated.

@arcivanov would you please review, and then I will release 1.28.6?

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

LGTM :+1:

Fixes #197


How to use this progress while uploading file in byte[] format?

I'm trying this library to upload the file (image/video/audio) in byte[] format. But its not working well,
It directly shows the progress percent upto 90, Please help me to fix this, Thanks in advance!

You can break points in this place


[KYUUBI #1649] Determine the yarn command in stop-application.sh.

Why are the changes needed?

When HADOOP_HOME is not set, the stop-application.sh script cannot kill the yarn task even if the yarn command exists. #1649
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[X] Add screenshots for manual tests if appropriate

[X] Run test locally before make a pull request

Codecov Report

Merging #1650 (aa8c08d) into master (7d68aa0) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1650      +/-   ##
============================================
- Coverage     59.60%   59.58%   -0.02%
  Complexity      193      193
============================================
  Files           265      265
  Lines         13082    13082
  Branches       1649     1649
============================================
- Hits           7797     7795       -2
- Misses         4625     4626       +1
- Partials        660      661       +1

Impacted Files
Coverage Δ

...he/kyuubi/engine/spark/repl/KyuubiSparkILoop.scala
90.16% <0.00%> (-3.28%)
:arrow_down:

Continue to review full report at Codecov.

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

thanks, merging to master


NYSDOT fixes for updated version

 Issue by landonreed
Wednesday May 16, 2018 at 13:40 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/pull/163

This PR collects a number of bug fixes from the final testing and review before deployment for NYSDOT.

landonreed included the following code: https://github.com/catalogueglobal/datatools-ui/pull/163/commits

:tada: This issue has been resolved in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Do not block on barrier in remote mode

Without this, we block the barrier in the main thread which stops execution. Also, fix the computation of request delay.

Why wait on the barrier at all then?

Why wait on the barrier at all then?

Because to unblock the wait() on the barrier outside the if condition and the barrier is initialized with 2. This seemed clean enough to me.


Add BinaryJaccardResult

Codecov Report
Attention: Patch coverage is 83.33333% with 8 lines in your changes missing coverage. Please review.

Project coverage is 99.53%. Comparing base (1167f69) to head (f5108f0).
Report is 3 commits behind head on main.

Files with missing lines
Patch %
Lines

src/arkas/result/jaccard.py
82.97%
8 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              main     #196      +/-   ##
===========================================
- Coverage   100.00%   99.53%   -0.47%
===========================================
  Files           68       69       +1
  Lines         1655     1703      +48
  Branches       166      169       +3
===========================================
+ Hits          1655     1695      +40
- Misses           0        8       +8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Needs-Triage: MS Teams extension event passed the wrong parameters, resulting in the unavailable zoom extension function

The ‘value.data’ passed the string "{}" instead of {} of the object type, which caused our parameter conversion to fail

There was no such parameter before July 29th, and it suddenly appeared after the 29th, and it was still a wrong parameter. Our service was running well before.

@Meghana-MSFT Can you help check this issuer,  this impacted us really badly, all of our users couldn't use our product anymore. Thank you very much.

@KaratLee - Thanks for raising your query.
We will look into it and let you know the updates.

@Meghana-MSFT This field （data:"{}"） should be newly added by Microsoft Teams, because there was no such field before, and our service has not been changed for a long time.

@KaratLee - We checked the Zoom extension in both we and Desktop client. It is working fine at our end. We do not see data field in the payload.

https://github.com/MicrosoftDocs/msteams-docs/assets/81138249/fa2692b8-3a9f-4007-a5ee-0f4eda8d97c8
Could you please share your Teams version details. Are you facing this issue only on web?

@Meghana-MSFT Teams client also has problems. Teams client version: <IP_ADDRESS>54

We checked it in this version - <IP_ADDRESS>64 (64-bit).

@Meghana-MSFT This is not a single or occasional problem, almost all of our customers experience this problem

@Meghana-MSFT Don't use the company intranet, try it with an external network？

@KaratLee - I tried this with home network.

@Meghana-MSFT Can you get someone else to try it, yours is the first one I know that works...

@Meghana-MSFT Can you help me check why Microsoft Teams sends data: "{}" to us? We will urgently release to remove the data: "{}" in the request data, but this problem has too much impact on our online It’s too big, almost all users are unavailable, can you help check the reason? Thank you very much

The fix has reached General ring for Production. Could you please check and confirm once. Thank you.


Initial generics support

Hand merge with some changes from https://github.com/aspnet/Identity/pull/643

@divega This PR has been updated as we discussed, I removed the test that was trying to customize and changing the uniqueness of our login providers, the other 2 tests pass.  I also copied the test over to the SqlServer, and those pass as well, so I think this should be good to go.

Great to see this is now getting traction... thanks for listening

104f2161915b1a4e7d0013f3de3b8d9a212a5d27


Missing ~/ggllm/ggllm.cpp/build/bin/ during initial config

Installation on Ubuntu22 fails at step 8 of Initial Config.   There isn't a ~/ggllm/ggllm.cpp/build/bin/ directory.  Nothing exists below ~/ggllm/ggllm.cpp/build/ after following the previous steps.  This prevents me from progressing, even if I skip that test step, as other steps afterwards refer to the non-existent bin directory.

Hi, are you referring to the step 8 of the deployment ? (it's related to cognito)
https://aws-samples.github.io/aws-genai-llm-chatbot/guide/deploy.html
Regarding the error, it's seems related to the Falcon model.
Can you try disabling it or using a model hosted on AWS Jumpstart  (Mistral7b_Instruct 0.3)


Fix typo in examples/hyperopt/README.md

Code Pull Requests
capabililies -> capabilities
uing -> using

 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.

Thank you! Would you mind checking also here? https://github.com/ludwig-ai/ludwig-docs


No correct way to write a vectorized cuda kernel

It seems that eager compilation is depreciated as the example from the docs raises an error.
import math
from numba import vectorize, cuda
import numpy as np

@vectorize(['float32(float32, float32, float32)',
            'float64(float64, float64, float64)'],
           target='cuda')
def cu_discriminant(a, b, c):
    return math.sqrt(b ** 2 - 4 * a * c)

N = 10000
dtype = np.float32

# prepare the input
A = np.array(np.random.sample(N), dtype=dtype)
B = np.array(np.random.sample(N) + 10, dtype=dtype)
C = np.array(np.random.sample(N), dtype=dtype)

D = cu_discriminant(A, B, C)

The official mitigation for this depreciation is to remove the signature. However when doing this we get an error:
import math
from numba import vectorize, cuda
import numpy as np

@vectorize(target='cuda')
def cu_discriminant(a, b, c):
    return math.sqrt(b ** 2 - 4 * a * c)

N = 10000
dtype = np.float32

# prepare the input
A = np.array(np.random.sample(N), dtype=dtype)
B = np.array(np.random.sample(N) + 10, dtype=dtype)
C = np.array(np.random.sample(N), dtype=dtype)

D = cu_discriminant(A, B, C)

raises: No matching version.  GPU ufunc requires array arguments to have the exact types.  This behaves like regular ufunc with casting='no'
(ran with '0.54.1')

@GuillaumeLeclerc thank you for raising this! @gmarkall would you be able to take a look at this?

The current version of Numba master doesn't raise the error anymore. We should check when the RC is cut that it still doesn't occur, then close this issue if that's the case at that point. For that reason, I'm adding this to the 0.55RC milestone, but no action is needed right now.

I can confirm the behaviour has not changed (and is not planned to change) so I'm closing this now as the error doesn't appear with the reproducer on master.


Adding the jupyter notebook for MXNet

@gautamkmr we don't need samples/notebook/mxnet/.mxnet.yaml.swp, can you remove that?


Update tutorials

This updates the two tutorials we already had and adds new one, focused on using CellRank when no RNA velocity information is present.

@michalk8, the updating of our two old tutorials is done and waiting for your review. In the meantime, I will start with the new tutorial.

Thanks @Marius1311 , I've left some comments in ReviewNB.

Thanks Mike! I added a putative link to the external page https://cellrank.readthedocs.io/en/latest/external.html - is that correct? Links are checked automatically anyway, aren't they?

I've left my comments in ReviewNB.

Thanks! That's a really helpful tool I find.

Thanks Mike! I added a putative link to the external page https://cellrank.readthedocs.io/en/latest/external.html - is that correct? Links are checked automatically anyway, aren't they?

Not really, because you're still using latest, not stable.
Links are not checked automatically, not is spell-checking.

Okay, I re-directed all links to stable, but probably missed a few.

I'm done with all your comments in ReviewNB.

Just need your help with surpressing these ugly warnings, can't figure out how to do it.

Just need your help with surpressing these ugly warnings, can't figure out how to do it.

Ok, I will handle it.

Warnings are being filtered now (I've fixed some that we produce), note to self MatplotlibDeprecationWarning is a subclass of UserWarning.

@Marius1311 please could you stick to using cellrank Jupyter kernel? otherwise, tests are broken, see
kernel_name = 'py38_devel'

    def get_kernel_spec(self, kernel_name):
        """Returns a :class:`KernelSpec` instance for the given kernel_name.

        Raises :exc:`NoSuchKernel` if the given kernel name is not found.
        """
        if not _is_valid_kernel_name(kernel_name):
            self.log.warning("Kernelspec name %r is invalid: %s", kernel_name,
                             _kernel_name_description)

        resource_dir = self._find_spec_directory(kernel_name.lower())
        if resource_dir is None:
>           raise NoSuchKernel(kernel_name)
E           jupyter_client.kernelspec.NoSuchKernel: No such kernel named py38_devel

Ok, got it, thanks!

Hi @michalk8, the beyond_rna_velocity is ready for a final round of your review!

Thanks @Marius1311 , will review it shortly.

I've fixed some typos, but apart from that, it's really great, I have no objections. I will go over the rest of the tutorials as well and fix latest -> stable.


Extend README.md with Homebrew alternative

Hello,
I suggest to extend the README.md with the following apt-get snip to install graphicsmagick without Homebrew.
$ sudo add-apt-repository ppa:dhor/myway
$ sudo apt-get update
$ sudo apt-get install graphicsmagick

Done, thanks


Flutter 2.13 candidate.0

Merge cherry picks for SliverReorderableList and Slider regressions in 3.0

Linux build_tests_1_2 is failing. Is it related to this change?

Thanks for checking, I reran it to deflake it.


Consider replacing usages of ConcurrentHashMap

Problem Description
ConcurrentHashMap is implemented using synchronized blocks. We recently found an issue that was causing some of our tests to hang due to the use of this class (see #8813). We should consider replacing usages of this class for our own maps and locks to avoid these problems.
A quick search shows 110 matches in our codebase, many of which are in tests.

Related: https://mail.openjdk.org/pipermail/loom-dev/2024-May/006632.html

Created issues for each of the places that require additional analysis. Issues #8966, #8967, #8968, #8969, #8970, #8971, #8972, #7973. All issues have been assigned.


bug on OperaGX

You cannot move vertically the brush

Well, you can move it with the sliders but you cant with keys

Excellent, thank you for the info! I'll look into it!


refactor: [M3-6377] - MUI v5 - Components > ProductInformationBanner

Description 📝
MUI migration SRC > Components > ProductInformationBanner
Major Changes 🔄

Run tss-react codemod on ProductInformationBanner
Renamed Props to    ProductInformationBannerProps.
Changes default exports to named exports.

How to test 🧪

Verify all the references of ProductInformationBanner.
Verify e2e tests pass

@cpathipa let's merge in develop like Hana suggested first


Athenaakrami patch 1

Added the TA Guide

Apologies if this is an unhelpful comment, but I suspect from the many commits here that you were committing to see the rendered version. In the github markdown editor there is a "preview" tab, which will show you the rendering without making a commit. You may find this more convenient.


[PE-D][Tester B] The app allows too short Telegram usernames.

The application doesn't handle error when I try to add new student with too short telegram (e.g. @a). https://core.telegram.org/method/account.checkUsername.

Labels: type.FunctionalityBug severity.Low
original: kienvumrpm/ped#5

This fix can be implemented. Would solve some of the telegram name too long issues as well

Cannot be fixed in the code, maybe can add in the UG or something


Python vesion conflicts

In the notification function code, I can not invode the package of Flask_event, It seems that the newsest Python 12.0 has changes some names of the functions into that page.
What should I do?

Please use Python 3.10


Prevent loss of data between restarts in local environment

See ticket #1164 on the CAS3 Trello board.

This PR is intended to resolve an issue identified in a CAS3 retrospective where, when running the API locally or within the ap-tools utility, data added or modified is not preserved between restarts. This is caused by some repeatable Flyway migrations in the local+dev+test folder containing TRUNCATE TABLE statements.
To resolve this, the repeatable migrations containing TRUNCATE TABLE statements have been moved to a new dev+test folder to preserve the behaviour for the dev and test environments, where it is desired. Similar migrations (without the TRUNCATE TABLE) statements have been created in a local folder to yield a similar initial set of data upon first run of the API application. If restoring the local database to a known state is desired, the TRUNCATE TABLE SQL statements can be executed locally using a tool such as DBeaver, or the Docker volume for the database can be destroyed and recreated.
The application configurations for each of the three affected environments have been updated to ensure that the application locates migrations from the appropriate new folder for its environment.

Thanks for doing this - it was a pain locally!


added hover effects

The following hovers have been added

This PR resolved #52

@ayushichoudhary-19 Great job that hover effect looks cool. I am merging this PR. Congratulations on creating your first pull request!


Question - Individual forms for each tab

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request
[x] question

Hi,
I was working with tab example. Is it possible to

Each tab should have a submit button and when I click on submit on first page validation must happen on only first tab and when I click submit on second tab validation must happen on only second tab
When I click on submit on  first tab the data in the first tab must be passed to the datatabase
Only after first tab data is saved into the database the second tab must be enabled

Thanks

Angular version: 5.0

yes possible, try to move form inside tab component to be able to control each form separately.
I can't provide a full example, you can do it by yourself :) and if you encounter any issue let me know !

Ok @aitboudad thanks I am doing as you said

@aitboudad correct we can do using above example but I have created tabs referring to this
https://plnkr.co/edit/hMZo3sXMqk35NckwYJCy?p=preview
how  in this case I can create a form inside a tab?

I have replicated the example
https://stackblitz.com/edit/ngx-formly-ui-bootstrap-pcwqtr
Please look into it when u have time
Thank u

Hi, I could find a better way, the only clean way to handle a such case is https://formly-js.github.io/ngx-formly/examples/advanced/tabs

Thank you @aitboudad . As u said I have used above approach and I was able to create individual forms and also able to validate individual forms.Only problem is I am not able to submit individual form
When I submit it will submit entire model this is because we have [options]="options[index]" and  [form]="form.at(index)" but we don't have something like [model]="model[i]" . Can we submit individual form model?

to get the individual model use form.at(index).value instead of model.


Setup MDAnalysis matrix for tests

Fixes #15
Yikes, well adding this matrix more than tripled the CI time.
Is this how you envisioned the MDAnalysis matrix @IAlibay?

Still in draft status because I want to remove the packaged actions and point to the public repos instead, but that depends on merging https://github.com/MDAnalysis/install-mdanalysis/pull/1 .
However, would be great to get opinions from @IAlibay @orbeckst @fiona-naughton on getting people to test a matrix of MDAnalysis versions this way! Effectively, the environment is still built from a yaml as previously, but the install-mdanalysis action manually uninstalls MDA and re-installs its own version. I think this is the least intrusive way to do it, but would love to hear thoughts


Clear blackboard data upon puzzle select

https://www.loom.com/share/063b55cb1d6248f980381a94db9608b9

According to Jay there is a small bug fix needed? Will wait for you to push that up Amolik to re-review


with A(B(X)) flow seems to mix up types of A's argument and B's return value

I'm trying to add type annotations to my Redux code and I'm getting errors that seem backwards.  Here is some of my code:
reduxTypes.js:
/* @flow */

export type Action = {
  type: string,
  error?: boolean,
  payload?: ?any,
  meta?: Object,
};

export type Store<S> = {
  dispatch: (action: Action) => ?any,
  getState: () => S,
};

...

pluginTypes.js
...
export const NOT_LOADED = 'NOT_LOADED';
export const LOADING = 'LOADING';
export const LOADED = 'LOADED';

export type LoadStatus = 'NOT_LOADED' | 'LOADING' | 'LOADED';

export type PluginStatus = {
  loadStatus: LoadStatus,
  loadError?: Error,
};

export type Plugin = {
  key: string,
  name: string,
  status?: PluginStatus,
  ...
}

pluginActions.js:
/* @flow */

import type {Plugin, PluginStatus} from '../flowtypes/pluginTypes';

import createAction from './createAction';

...

export const INSTALL_PLUGIN = 'INSTALL_PLUGIN';

export type InstallPluginAction = {
  type: 'INSTALL_PLUGIN',
  payload: Plugin,
};

export const installPlugin: (plugin: Plugin) => InstallPluginAction = createAction(INSTALL_PLUGIN);

pluginMiddleware.js:
/* @flow */

import Immutable from 'immutable';
import Promise from 'bluebird';

import type {Middleware} from '../../mindfront-react-components/flowtypes/reduxTypes';
import type {Plugin, PluginStatus} from '../flowtypes/pluginTypes';
import {LOADING, NOT_LOADED, LOADED} from '../flowtypes/pluginTypes';
import type {LoadPluginAction} from '../actions/pluginActions';

import {
  setPluginStatus,
  LOAD_PLUGIN,
  installPlugin,
} from '../actions/pluginActions';

const loadPluginHandler: Middleware = store => next => (action: LoadPluginAction) => {
  next(action);
  let key = action.payload;
  ...
  store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
};

...

From that I get a slew of errors:
$ flow status
app/middleware/pluginMiddleware.js:32
 32:     store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
  4:   type: string,
             ^^^^^^ string. Expected string literal `SET_PLUGIN_STATUS`. See: mindfront-react-components/flowtypes/reduxTypes.js:4
 34:   type: 'SET_PLUGIN_STATUS',
             ^^^^^^^^^^^^^^^^^^^ string literal `SET_PLUGIN_STATUS`. See: app/actions/pluginActions.js:34

This doesn't make sense.  store.dispatch needs {type: string, ...}, setPluginStatus returns {type: 'SET_PLUGIN_STATUS', ...}.  Where's the contradiction?
app/middleware/pluginMiddleware.js:32
 32:     store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
  6:   payload?: ?any,
                  ^^^ null. This type is incompatible with. See: mindfront-react-components/flowtypes/reduxTypes.js:6
 35:   payload: PluginStatus,
                ^^^^^^^^^^^^ object type. See: app/actions/pluginActions.js:35

Again, store.dispatch needs {payload?: ?any}, setPluginStatus returns {payload: PluginStatus}.
It's as though flow has mixed of the types of store.dispatch's argument and setPluginStatus's return value, so it thinks I'm trying to flow {type: string, payload?: ?any} into {type: 'SET_PLUGIN_STATUS', payload: PluginStatus}, when in fact I'm doing the reverse (which should work, right?)
Or am I doing something wrong?
Here are the rest of the errors, for reference:
app/middleware/pluginMiddleware.js:32
 32:     store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
  6:   payload?: ?any,
                  ^^^ undefined. This type is incompatible with. See: mindfront-react-components/flowtypes/reduxTypes.js:6
 35:   payload: PluginStatus,
                ^^^^^^^^^^^^ object type. See: app/actions/pluginActions.js:35

app/middleware/pluginMiddleware.js:32
 32:     store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
  7:   meta?: Object,
              ^^^^^^ undefined. This type is incompatible with. See: mindfront-react-components/flowtypes/reduxTypes.js:7
 36:   meta: {
             ^ object type. See: app/actions/pluginActions.js:36

app/middleware/pluginMiddleware.js:32
 32:     store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
 11:   dispatch: (action: Action) => ?any,
                          ^^^^^^ property `error`. Property not found in. See: mindfront-react-components/flowtypes/reduxTypes.js:11
 32:     store.dispatch(setPluginStatus(key, {loadStatus: LOADING}));
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ object type

app/middleware/pluginMiddleware.js:34
 34:       .catch((error: Error) => store.dispatch(setPluginStatus(key, {loadStatus: NOT_LOADED, loadError: error})))
                                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
 11:   dispatch: (action: Action) => ?any,
                          ^^^^^^ property `error`. Property not found in. See: mindfront-react-components/flowtypes/reduxTypes.js:11
 34:       .catch((error: Error) => store.dispatch(setPluginStatus(key, {loadStatus: NOT_LOADED, loadError: error})))
                                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ object type

app/middleware/pluginMiddleware.js:35
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ function call
  4:   type: string,
             ^^^^^^ string. Expected string literal `INSTALL_PLUGIN`. See: mindfront-react-components/flowtypes/reduxTypes.js:4
 27:   type: 'INSTALL_PLUGIN',
             ^^^^^^^^^^^^^^^^ string literal `INSTALL_PLUGIN`. See: app/actions/pluginActions.js:27

app/middleware/pluginMiddleware.js:35
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ function call
  6:   payload?: ?any,
                  ^^^ null. This type is incompatible with. See: mindfront-react-components/flowtypes/reduxTypes.js:6
 28:   payload: Plugin,
                ^^^^^^ object type. See: app/actions/pluginActions.js:28

app/middleware/pluginMiddleware.js:35
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ function call
  6:   payload?: ?any,
                  ^^^ undefined. This type is incompatible with. See: mindfront-react-components/flowtypes/reduxTypes.js:6
 28:   payload: Plugin,
                ^^^^^^ object type. See: app/actions/pluginActions.js:28

app/middleware/pluginMiddleware.js:35
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ function call
 11:   dispatch: (action: Action) => ?any,
                          ^^^^^^ property `error`. Property not found in. See: mindfront-react-components/flowtypes/reduxTypes.js:11
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ object type

app/middleware/pluginMiddleware.js:35
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ function call
 11:   dispatch: (action: Action) => ?any,
                          ^^^^^^ property `meta`. Property not found in. See: mindfront-react-components/flowtypes/reduxTypes.js:11
 35:       .then((plugin: Plugin) => store.dispatch(installPlugin(plugin)));
                                                    ^^^^^^^^^^^^^^^^^^^^^ object type

mindfront-react-components/flowtypes/reduxTypes.js:4
  4:   type: string,
             ^^^^^^ string. Expected string literal `LOAD_PLUGIN`
 20:   type: 'LOAD_PLUGIN',
             ^^^^^^^^^^^^^ string literal `LOAD_PLUGIN`. See: app/actions/pluginActions.js:20

mindfront-react-components/flowtypes/reduxTypes.js:6
  6:   payload?: ?any,
                  ^^^ null. This type is incompatible with
 21:   payload: string,
                ^^^^^^ string. See: app/actions/pluginActions.js:21

mindfront-react-components/flowtypes/reduxTypes.js:6
  6:   payload?: ?any,
                  ^^^ undefined. This type is incompatible with
 21:   payload: string,
                ^^^^^^ string. See: app/actions/pluginActions.js:21

mindfront-react-components/flowtypes/reduxTypes.js:17
 17: export type Middleware = (store: Store) => (next: (action: Action) => ?any) => (action: Action) => ?any;
                                                                ^^^^^^ property `error`. Property not found in
 21:   next(action);
            ^^^^^^ object type. See: app/middleware/pluginMiddleware.js:21

mindfront-react-components/flowtypes/reduxTypes.js:17
 17: export type Middleware = (store: Store) => (next: (action: Action) => ?any) => (action: Action) => ?any;
                                                                ^^^^^^ property `meta`. Property not found in
 21:   next(action);
            ^^^^^^ object type. See: app/middleware/pluginMiddleware.js:21

Found 16 errors

Haven't looked in depth, but it would be really helpful if you could spend some time deriving an isolated repro case. The code pasted above introduces a lot of complexity that makes it hard to reproduce locally. There could be 2+ things going wrong here, and unfortunately we don't have enough time to investigate issues with this much code.

Yeah, I know that was a mountain.  I'll post another issue if I can come up with a simpler case.  Thanks!

Okay, this is another issue of mutability.  I had thought that { type: 'SET_PLUGIN_STATUS' } was a subtype of { type: string }.


Using normalization of the map

It would like to visualize a HealSparse map with a logarithmic scale, however pcolormesh does not accept the norm kwarg as skyproj already passes vmin and vmax.
Minimum example
fig = plt.figure(figsize=(6,6))
ax = fig.add_subplot(111)
sp = skyproj.HammerSkyproj(ax=ax)
_ = sp.draw_hspmap(hsp, norm=mpl.colors.LogNorm())

raises
ValueError: Passing a Normalize instance simultaneously with vmin/vmax is not supported.  Please pass vmin/vmax directly to the norm when creating it.
This uses Matplotlib 3.7.2 and skyproj 1.0.3.

Fixed with #57


Add functionality to convert schema

Following up on #36
We would like to be able to convert columns in a dataset to some type specified by the user. This could for example be done by allowing the user to specify a schema on the cmdline, that is used to convert the dataset to if it is different from the schema in the dataset itself.
One challenge is how to store this modified dataset, because there is no place for this in the directory structure.

I wonder if we're headed towards using a hash of the metadata as a dirname

I wonder if we're headed towards using a hash of the metadata as a dirname

Yes, it will become very challenging to distinguish between instances of a certain dataset with different schema's... Besides that, we need to take into account that 1) some properties are optional (but we can fix that with defaults) and 2) users should be able to prune entries and right now, they can just use the directory structure to prune multiple entries underneath a given directory.

Update: with #62 a uuid is now generated as dirname to store dataset variants.


Issue with Acive Directory - User successfully logged in, but not authenticated

Laravel Version: 5.8.29
Adldap2-Laravel Version: 6.0
PHP Version:7.2
LDAP Type: Active Directory

Description:
Hello,
I'm trying to use adldap2 on Laravel without the admin account.
I set my connection, adn overwrote the login function in LoginController.php. It looks like this :
public function login(Request $request){
        $credentials = $request->only($this->username(), 'password');
        $username = $credentials[$this->username()];
        $password = $credentials['password'];

        $auth = Adldap::auth();

        if($auth->attempt($username, $password, $bindAsUser = true)){
            Auth::attempt($credentials, true);
            return redirect('/fiches');
        }
        return redirect('/login');
    }

In my log file, I can see that the user passes the authentication :
[2019-08-05 11:10:54] local.INFO: User 'Simon LAMBERT' has been successfully found for authentication.
[2019-08-05 11:10:54] local.INFO: User 'Simon LAMBERT' is authenticating with username<EMAIL_ADDRESS>
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Attempting - Username: login
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Binding - Username<EMAIL_ADDRESS>[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Bound - Username<EMAIL_ADDRESS>
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Passed - Username: login
[2019-08-05 11:10:54] local.INFO: LDAP (ldap:/ldap:389) - Connection: default - Operation: Binding - Username:
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Bound - Username:
[2019-08-05 11:10:54] local.INFO: User 'Simon LAMBERT' has successfully passed LDAP authentication.
[2019-08-05 11:10:54] local.INFO: User 'Simon LAMBERT' has been successfully logged in.

But right after the user is authenticating, there is a search operation with a weird GUID.
This happends everytime I load a page that has the 'auth' middleware.
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Search - Base DN: dc=domain,dc=lan - Filter: (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))(objectguid=I���?��E�z� ��Y)) - Selected: (*,objectguid) - Time Elapsed: 2.28
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Search - Base DN: dc=domain,dc=lan - Filter: (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))(objectguid=I���?��E�z� ��Y)) - Selected: (*,objectguid) - Time Elapsed: 2.14
[2019-08-05 11:10:54] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Search - Base DN: dc=domain,dc=lan - Filter: (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))(objectguid=I���?��E�z� ��Y)) - Selected: (*,objectguid) - Time Elapsed: 0.61
[2019-08-05 11:12:00] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Search - Base DN: dc=domain,dc=lan - Filter: (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))(objectguid=I���?��E�z� ��Y)) - Selected: (*,objectguid) - Time Elapsed: 2.37

Moreover, the user doesn't seem to be authenticated as I am redirected to the login page.
As I'm trying to bind with the samaccountname, my ldap_auth.php looks like this :
        'ldap' => [

            'locate_users_by' => 'samaccountname',

            'bind_users_by' => 'samaccountname',

        ],

If I use the distinguished name, I get a weird thing on line :
[2019-08-05 11:10:54] local.INFO: User 'Simon LAMBERT' is authenticating with username<EMAIL_ADDRESS>
and the authentication doesn't work.
Thanks a lot.
Simon

Hi @6monlambert,
You don't need to overwrite the LoginController::login() method or call Adldap::auth()->attempt(). This will not actually authenticate users into your Laravel application. This will only call an ldap_bind() to your configured server.
You need to call the regular Laravel Auth::attempt() method on the Auth facade:
use Illuminate\Support\Facades\Auth;

if (Auth::attempt($request->only('username', 'password'))) {
    // Authenticated.
}

Also, you must change your bind_users_by to distinguishedname, and set your configured account_suffix to either null or ''.
This should resolve your issues.
Let me know if you still require assistance, thanks!

Hello @stevebauman,
Thanks for you reply.
I got the authentication working.
I'm still facing an issue though. I'd like the authenticated user to perform the ldap binds after the authentication.
I'm currently using a binding account that performs binds every time I go on a new page :
> [2019-08-07 09:47:25] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Binding - Username<EMAIL_ADDRESS>
> [2019-08-07 09:47:25] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Bound - Username<EMAIL_ADDRESS>
> [2019-08-07 09:47:25] local.INFO: LDAP (ldap://ldap:389) - Connection: default - Operation: Search - Base DN: dc=domain,dc=lan - Filter: (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))(objectguid=�iU�D O��\�25F_)) - Selected: (*,objectguid) - Time Elapsed: 1.61

Is it possible to do this with the authenticated user ? (I'm using the NoDatabaseUserProvider class).
Morevover, I didn't have time to search a lot, but is it possible to create multiple rules to match groups in the Active Directory, and then filter the access to some pages of the application (and not the authentication) based on these rules ?
Thanks a lot,
Simon.


Enhance stage feature

Checkstyle will be updated later.

Codecov Report

Merging #86 (fa93356) into master (5d378ba) will increase coverage by 0.07%.
The diff coverage is 57.69%.

@@             Coverage Diff              @@
##             master      #86      +/-   ##
============================================
+ Coverage     72.23%   72.31%   +0.07%
- Complexity      435      456      +21
============================================
  Files            74       76       +2
  Lines          1365     1423      +58
  Branches        143      156      +13
============================================
+ Hits            986     1029      +43
- Misses          328      340      +12
- Partials         51       54       +3

Impacted Files
Coverage Δ

src/main/java/seedu/workbook/model/Model.java
100.00% <ø> (ø)

...in/java/seedu/workbook/model/internship/Stage.java
72.72% <0.00%> (+2.72%)
:arrow_up:

...eedu/workbook/model/internship/util/StageUtil.java
57.89% <57.89%> (ø)

...java/seedu/workbook/logic/commands/AddCommand.java
88.23% <60.00%> (-11.77%)
:arrow_down:

...va/seedu/workbook/model/internship/Internship.java
88.23% <100.00%> (+0.23%)
:arrow_up:

...n/java/seedu/workbook/commons/util/StringUtil.java
92.85% <0.00%> (-1.88%)
:arrow_down:

...ava/seedu/workbook/logic/commands/EditCommand.java
93.24% <0.00%> (-0.10%)
:arrow_down:

...c/main/java/seedu/workbook/model/ModelManager.java
100.00% <0.00%> (ø)

...orkbook/model/internship/InternshipComparator.java
70.58% <0.00%> (ø)

...orkbook/model/internship/UniqueInternshipList.java
92.85% <0.00%> (+0.17%)
:arrow_up:

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


changed default value of final_conv_length to 'auto' in Deep4Net

After last changes, default value of final_conv_length in Deep4Net is None and code fails. Before it was mandatory to provide this paramter. I'm setting default to `"auto" -> it should not break earlier code as before it had to be specified.

good catch! and what about shallow? should be same Problem there no?

for shallow filter_time_length is set to 25 by default, it was the same before recent changes and it still works as before :)

Thank you @sliwy =)


Add factories for ledger, transaction, operation

Having factories aids in testing for developers that use this gem. The file is included in lib, but isn't loaded unless require 'stellar-base/factories'.
The downside is that the file is shipped into production, so will take up disk space, but it will not be loaded into memory.
The upside is that the developer just needs to require FactoryBot and the factories file to be able to use it.
I'm open to revising this, and I wanted to get thoughts before adding other factories.

@bartekn what are your thoughts on this?


Graph shows incorrect results for some sensor data

Home Assistant release (hass --version):
Current dev
Component/platform:
GUI / history
Description of problem:
If sensors repeatedly show the same reading, the repeated value is not logged into the history database.
However when it comes to draw a graph - this can produce odd results
In the case shown - my gas sensor produces readings every 15 mins. Most of these are zero since I just use gas in the mornings and evenings.
However the HA gui draws a graph line that connects the first '0' reading with the first non zero reading.

Expected:
The reading of the sensors should be graphed accurately - showing flat lines and peaks.

nest temperatures had a similar problem which was fixed with this commit.

should there be a property for each sensor component: "allow_interpolation" / "interpolatable" that return false for components with discrete measured states (the gas usage sensor, thermostat, etc) and return true (default) for sensors that measures continous entities such as temperatures?

The issue here is not with the graphing. Interpolation should be done between every reading. Graphs will not be interpolated if no unit of measurement is available.
The underlying problem here is that Home Assistant filters out any state change that is exactly the same as the previous one. See also issue #1135 and Pivotal Story #113224701
There is currently no solution for this problem. There is no way we can detect properly which sensors should get all state changes fired nor does the Home Assistant core support this.

No solution available now, closing.


Documentation for Dev_SDCard_Program.L5X

Hi Jeremy,
maybe you wrote a very helpful bit of code but unfortunately I cannot figure out what it does and how to use it:
src/System/Dev_SDCard_Program.L5X
I would like to read data from a file on the SD Card. In case your code should do this,

where do I input the filename?
where is the content of the file saved?
where did you get the magic numbers from and what do they mean? (e.g. Msg.AttrAll.Class = 16#031a, MsgAttrAll.Flags = 16#0200, MsgAttrAll.Path = '$1F$00$00$00', the values in MsgAttrAllResp, 16#031A in line 13 of Sys_SDCard)

I've also found the Sample Code CF_Read_Write_Example from Rockwell but it gave an error when importing for our controller and it's far more complicated to understand (because of Ladder Code and the size and number of routines) and blows up the code due to the many routines instead of nice AOIs.) So it would be great to be able to use your code.
If it's simpler for you to write a bit here than making a proper documentation in the Wiki I will make a PR for writing this documentation and probably add some comments to the code that would have helped me.

Hi, aliskimon!
Apologies for my hiatus. I am in the process of a documentation (and overall) overhaul of content here.
I agree that Rockwell sample code can sometimes be cumbersome and confusing to understand.
My SDCard AOI, then and currently parses info from a Rockwell CIP object:

Class code is 0x31A.
Instance Id is 1.
Uses the CIP Get_Attributes_All service (0x01).
Msg.Attribute Id is set to zero for this service.
Msg.ReqLen is also set to zero for this service.
No need to worry about the Msg.Flags, and I rarely interact with them beyond diagnostics.

Within the SDCard block, a couple of utility AOIs are used to set these parameters:
Msg_SetParams(SetParams, 16#031A, 1, 0, 0, Ref_Msg);
Msg_SetPathToIO(SetPath, Ref_Module, Ref_Msg);
MSG(Ref_Msg);

Msg_SetParams() sets the parameters mentioned above: CIP Class, Instance, Attribute, and RequestLength.
Msg_SetPathToIO() handles setting the Msg.Path to the correct destination, using a MODULE reference.

The MODULE reference is provided at the point of the AOI call ('Local' refers to the controller itself):

To further add, the current AOI doesn't do any sort of file handling.
I am working a general-purpose version of this.


wingetcreate storing installers in %temp% folder

Description
When creating new or updating existing manifest, wingetcreate is given a download link to the installer so that it can download the application and generate sha256. I've noticed that wingetcreate stores the installer in %temp% folder after generating sha256. I like this behavior because if I had to do some testing with the installer or get some metadata from it, I would not have to download the installer again. But this could cause storage issue after many submissions so I would like to have a option to clear the installers via the application itself.
Solution
add some command like wingetcreate cache clean to clear the installers.
(optional)
some extra commands like wingetcreate cache --list will display all the installers that wingetcreate downloaded. Doesn't have to be exact appname just the installer's name. Output could look similar to when we type dir command in a folder. This feature could be easily added if wingetcreate stored installers in it's own directory somewhere instead of %temp% folder so that it can just clone what dir command does.

We may follow the pattern from the Windows Package Manager and use %TEMP%\wingetcreate.
The default behavior may be switched to delete the installer after the hash is calculated unless there is a setting to retain for some period of time.

We may follow the pattern from the Windows Package Manager and use %TEMP%\wingetcreate.
The default behavior may be switched to delete the installer after the hash is calculated unless there is a setting to retain for some period of time.


Showing fake AP's but not deauthing

Just compiled using latest android IDE with patched libraries for esp8266 , so far it's showing the rick roll ap's but not deauthing.
I selected the proper wifi channel in the code. The other deauther script this code is based off of works fine for me... now sure why this isn't working
Am I missing something?  Does this script deauth 1 time only? then transmit rick roll beacons there after?

Nope! This code is still buggy, and isn't completely functional as of now. I haven't been able to get the ESP8266 to send deauth frames and set up fake APs simultaneously (it's either one or the other, which is why the deauther script this is based off works just fine), and I've put this project on hold for a while. But I am aware of this issue and it's the first thing on my to-do for this project, so I'll try to get to it as soon as I can.


Persist cascade state when navigating pages

Persist cascade state when navigating pages. Currently, if you turn off the cascade and then move to the next page - the cascade will reset back to on automatically.

So I solved this by adding two cascade settings: a per page cascade setting that can be toggled with the checkbox and a default cascade setting controlled through the Settings dialog. Each page starts with the default but can be toggled as needed for that page without affecting the starting point.
9760247467f17966bd0d0d3ea7ab54761bfc1c36


In 3D, iso-categorical rendering of labels doesn't show labels correctly

🐛 Bug
The background of labels (correspond to value 0) should be transparent. In "translucent" rendering, it works fine. But in "iso categorical" rendering, it seems that background is replaced with some opaque colors.
Rendering used to be fine in 0.4.16.
To Reproduce
Steps to reproduce the behavior:

Run following code
import napari
import numpy as np
viewer = napari.Viewer()
labels = np.zeros((40,40,40), dtype=np.int16)
labels[10:30, 10:30, 10:30] = 1
layer = viewer.add_labels(labels)
layer.color_mode = "direct"
layer.color = {1: [1,0,0,1]}

View in 3D mode.

Expected behavior
Background should be transparent.
Environment

Please copy and paste the information at napari info option in help menubar here:

napari: 0.4.17rc4
Platform: Windows-10-10.0.22621-SP0
Python: 3.9.7 | packaged by conda-forge | (default, Sep 29 2021, 19:20:16) [MSC v.1916 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.6
NumPy: 1.23.2
SciPy: 1.9.1
Dask: 2022.9.0
VisPy: 0.11.0
magicgui: 0.5.1
superqt: 0.3.2
in-n-out: 0.1.5
app-model: 0.0.9
npe2: 0.6.1

OpenGL:
- GL version: 4.6.0 - Build <IP_ADDRESS>21
- MAX_TEXTURE_SIZE: 16384

Screens:
- screen 1: resolution 1368x912, scale 2.0
- screen 2: resolution 1920x1080, scale 1.0

Any other relevant information:

Additional context

Here's what it looks like to me anyways:
Live:

RC4 (same with main):

Git bisect indicates this commit:
https://github.com/napari/napari/commit/d4b28364a2d1cc832b1eba06cc33ab5849514f62
CC: @perlman
layer.color_mode = "auto" also makes the cube visible again.

Here better video to show the problem using labels that touches the border. Its cover case is linked by @psobolewskiPhD in the previous code.
https://user-images.githubusercontent.com/3826210/195834147-f855e3c1-f0ac-425a-8859-5e7c225f4473.mp4

The error was introduced in #4935

The error was introduced in #4935

Yup, I also did a git bisect—what an awesome tool! my favorite git thing I think—posted above 😉


Text(guid)

Splitting out from #1090
Ensure Text(guid) works.
Confirm this works with creating strings from dataverse Ids. The scenario there is making URLs out of dataverse records.

Fixed in PR: https://github.com/microsoft/Power-Fx/pull/1134


[c++] Add metadata functions to SOMAGroup

Split-off from https://github.com/single-cell-data/TileDB-SOMA/issues/1240
This includes the implementing following functions from tiledb::Group:

get_metadata
has_metadata
metadata_num
set_metadata
delete_metadata

#1339


[1.0] I can't get to the on-tap behind a hidden element?

http://jsbin.com/wedogi/edit?html,console,output
I can't get to the on-tap behind a hidden element?

The hidden element is not really hidden. If you remove the p-test not hidden from the DOM, you'll still seeing the word "test" surrounded by a red border. Fix this issue and tell us if the tap event is still not fired.

Yes but doesn't it suppose to be hidden as in display none? I have lots of pages stacked on top of each other in my app?

I guess it's supposed to be hidden. Why you create pages dynamically ? Have you tried to add a section into the iron-pages ?

You have a :host rule that is taking higher precedence than the [hidden] rule.

lol I wouldn't found that out in a million years haha thanks :D


Correct aws_ebs README.md's IAM instructions

/assign @sebgoa
The masters manage EBS volumes for the nodes, so only they need the IAM permissions mentioned in the README.

I'm completely unfamiliar with AWS ecosystem, but just to confirm, you can attach the EBS volume to an instance (that has no ebs:AttachVolume permissions) through another instance that has permissions?

@ahmetb Correct! The master actually does pretty much all of the manipulations of EC2 instances so you don't have to grant IAM perms to the entire cluster. This minimizes attack surface if you NoSchedule taint your master.

/lgtm

/lgtm
Thanks @gtaylor


[bug] Scope in OAuth2.0 requires percent encoding

client.generateOAuth2AuthLink(...) function generates url with scope scope=tweet.read+users.read+offline.access which doesn't have percent encoding.
This url returns HTTP 400 as mentioned in  https://twittercommunity.com/t/http-400-with-redirect-is-requested-error-description-from-oauth2-authorize-endpoint/164764/14
Based on Twitter's doc, https://developer.twitter.com/en/docs/authentication/oauth-2-0/authorization-code
Scope requires percent encoding.

You will need to have the proper encoding for this URL to work, be sure to check out our documentation on the percent encoding.

Hi,
Thank you for your report. You're right, I missed that because opening the link in Chrome automatically fixes the issue.
This will be fixed soon :)


versions: cloud-hypervisor 0.9.0

Highlights for cloud-hypervisor version 0.9.0 include:
virtiofs updates to new dax implementation based in qemu 5.0
Fixed random issues caused due to seccomp filters
io_uring Based Block Device Support
If the io_uring feature is enabled and the host kernel supports it then io_uring will be used for block devices. This results a very significant performance improvement.
Block and Network Device Statistics
Statistics for activity of the virtio network and block devices is now exposed through a new vm.counters HTTP API entry point. These take the form of simple counters which can be used to observe the activity of the VM.
HTTP API Responses
The HTTP API for adding devices now responds with the name that was assigned to the device as well the PCI BDF.
CPU Topology
A topology parameter has been added to --cpus which allows the configuration of the guest CPU topology allowing the user to specify the numbers of sockets, packages per socket, cores per package and threads per core.
Release Build Optimization
Our release build is now built with LTO (Link Time Optimization) which results in a ~20% reduction in the binary size.
Hypervisor Abstraction
A new abstraction has been introduced, in the form of a hypervisor crate so as to enable the support of additional hypervisors beyond KVM.
Snapshot/Restore Improvements
Multiple improvements have been made to the VM snapshot/restore support that was added in the last release. This includes persisting more vCPU state and in particular preserving the guest paravirtualized clock in order to avoid vCPU hangs inside the guest when running with multiple vCPUs.
Virtio Memory Ballooning Support
A virtio-balloon device has been added, controlled through the resize control, which allows the reclamation of host memory by resizing a memory balloon inside the guest.
Enhancements to ARM64 Support
The ARM64 support introduced in the last release has been further enhanced with support for using PCI for exposing devices into the guest as well as multiple bug fixes. It also now supports using an initramfs when booting.
Intel SGX Support
The guest can now use Intel SGX if the host supports it. Details can be found in the dedicated SGX documentation.
Seccomp Sandbox Improvements
The most frequently used virtio devices are now isolated with their own seccomp filters. It is also now possible to pass --seccomp=log which result in the logging of requests that would have otherwise been denied to further aid development.
Notable Bug Fixes
Our virtio-vsock implementation has been resynced with the implementation from Firecracker and includes multiple bug fixes.
CPU hotplug has been fixed so that it is now possible to add, remove, and re-add vCPUs (#1338)
A workaround is now in place for when KVM reports MSRs available MSRs that are in fact unreadable preventing snapshot/restore from working correctly (#1543).
virtio-mmio based devices are now more widely tested (#275).
Multiple issues have been fixed with virtio device configuration (#1217)
Console input was wrongly consumed by both virtio-console and the serial. (#1521)

Fixes: #2864
Signed-off-by: Jose Carlos Venegas Munoz<EMAIL_ADDRESS>

/test

/test-clh

/test-clh-docker

/test-clh-docker

/test-clh-docker

Seems that clh is not happy to be updated with out a new version of virtiofsd, and virtiofsd PR is not happy if clh is not updated so closing this in favor of https://github.com/kata-containers/runtime/pull/2840 that includes both upgrades.


Redesign select-inputs

Redesign dropdown-select-inputs to ...

[ ] ... have no border radius at the bottom when opened so it flows over to the option list
[x] ... change background color when opened so the options list has a neutral background color
[ ] ... use the same font as everything else (Inter)

@CuzImBisonratte might you look over the javascript code. I did my best but catching events that are out of focus isn't my favorite...

@rosenclosed

@CuzImBisonratte might you look over the javascript code. I did my best but catching events that are out of focus isn't my favorite...

Why dont you use something like the focus-selector:
select:focus {
    background-color: red;
}

Then the only thing you would need to try is to disable focus when open and clicked again (to close) which would be easy because jquery has a focus()-Function that toggles focus.
Then you also would not need an additional class that gets applied via js.


Add Fiber Types to Interface Form Factors

When setting up devices to be patch/panels/ODF it would be good to have the ability to select a Fiber type...
Suggested List (Based on data from https://en.wikipedia.org/wiki/Optical_fiber_connector)
E2000
E2000 APC (Angled version of above)
SC Simple
SC Duplex (A Pair)
LC Simplex
LC Duplex (A Pair)
MPO / MTP (You may need to be able to allow multiple connections on this type of connector)
ST Simplex
ST Duplex

# Fiber
IFACE_FF_SCS = 6000
IFACE_FF_SCD = 6010
IFACE_FF_LCS = 6100
IFACE_FF_LCD = 6110
IFACE_FF_E2K = 6200
IFACE_FF_E2KAPC = 6210
IFACE_FF_MPOMTP = 6300
IFACE_FF_STS = 6400
IFACE_FF_STD = 6410

    [
        'Fiber',
        [
            [IFACE_FF_SCS, 'SC Simplex'],
            [IFACE_FF_SCD, 'SC Duplex'],
            [IFACE_FF_LCS, 'LC Simplex'],
            [IFACE_FF_LCD, 'LC Duplex'],
            [IFACE_FF_E2K, 'E2000'],
            [IFACE_FF_E2KAPC, 'E2000 APC'],
            [IFACE_FF_MPOMTP, 'MPO / MTP'],
            [IFACE_FF_STS, 'ST Simplex'],
            [IFACE_FF_STD, 'ST Duplex'],
        ]
    ],

NetBox does not yet support patch panels or physical cable plant management. Please see #20.


Tdarnell pxe integration

Integrate PXE into base RH MCGO validated pattern

Apologies for the PR mess here, was just trying to fix the kubeconform error that was getting thrown during merge workflows.


wrong assertion in TestTendermintServerApp

dropping this here because I am working on a Tendermint upgrade, but don't have a windows system at hand and it's a separate issue (as this commit bare the message:  "fix some more tests on windows").
@angrybayblade seems to be this commit: cda49e8
https://github.com/valory-xyz/open-autonomy/blob/2822968f858def392ebfd4d48906ce1a81548234/tests/test_deployments/test_app.py#L200-L208
would expect: assert all(f.exists() for f in expected_file_names), expected_file_names
P.S. nested remove_prefix function no longer needed

This can be solved without Windows access.

addressing in #1012


Can we drop the pyproj dependency?

In recent months we have greatly simplified OSMnx's requirements:

we dropped the rtree dependency #900
we dropped the dateutil dependency #919
we made matplotlib an optional dependency #976
we will be dropping the gdal optional dependency #916

I believe there's one more we can do. Currently we require pyproj because we use its is_projected function to check whether a CRS is projected or not (in the projection module). However, crs objects come with an is_projected attribute (docs). Could we just access it directly like gdf.crs.is_projected rather than importing pyproj to calling its function?

Yes we can just access the crs object like GeoSeries.crs.is_projected. See the GeoPandas docs. Resolution in #980.


Crashing report - Testnet 3.3 - Docker - Ducca#5707

Launched Block Producer and Snark Worker in docker.
VPS with 8 cores 16 RAM.

The first error is that it cannot download the archive:

[Info] Could not download genesis ledger from $uri: $error
	uri: "https://s3-us-west-2.amazonaws.com/snark-keys.o1test.net/genesis_ledger_accounts_e7fd308899bca6956b093b635988ea06630adbf540e13d38dcd2f7ab629da53c_f094d0eb814dbbff2f41f3f69c414331566f2c4a884c309944899ea59f101b9a.tar.gz"
	error: "(monitor.ml.Error\n (\"Process.run failed\"\n  ((prog curl)\n   (args\n    (--fail -o\n     /tmp/s3_cache_dir/genesis_ledger_accounts_e7fd308899bca6956b093b635988ea06630adbf540e13d38dcd2f7ab629da53c_f094d0eb814dbbff2f41f3f69c414331566f2c4a884c309944899ea59f101b9a.tar.gz\n     https://s3-us-west-2.amazonaws.com/snark-keys.o1test.net/genesis_ledger_accounts_e7fd308899bca6956b093b635988ea06630adbf540e13d38dcd2f7ab629da53c_f094d0eb814dbbff2f41f3f69c414331566f2c4a884c309944899ea59f101b9a.tar.gz))\n   (exit_status (Exit_non_zero 22)) (stdout \"\")\n   (stderr\n    (\"  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\"\n     \"                                 Dload  Upload   Total   Spent    Left  Speed\"\n     \"\\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\"\n     \"curl: (22) The requested URL returned error: 404 Not Found\" \"\"))))\n (\"Raised at file \\\"src/error.ml\\\" (inlined), line 9, characters 14-30\"\n  \"Called from file \\\"src/or_error.ml\\\", line 72, characters 17-32\"\n  \"Called from file \\\"src/deferred1.ml\\\", line 17, characters 40-45\"\n  \"Called from file \\\"src/job_queue.ml\\\" (inlined), line 131, characters 2-5\"\n  \"Called from file \\\"src/job_queue.ml\\\", line 171, characters 6-47\"))"

And Crash 2 hours after starting:

2020-09-17 09:26:43 UTC [Error] Error verifying transaction snark: $error
        error: "((rpc_error (Connection_closed (\"EOF or connection closed\")))\n (connection_description (\"Client connected via TCP\" (7aea31cfa2b4 38443)))\n (rpc_tag rpc_parallel_plain_0) (rpc_version 0))"
2020-09-17 09:26:43 UTC [Error] Error verifying transaction snark: $error
        error: "((rpc_error (Connection_closed (\"EOF or connection closed\")))\n (connection_description (\"Client connected via TCP\" (7aea31cfa2b4 38443)))\n (rpc_tag rpc_parallel_plain_0) (rpc_version 0))"
2020-09-17 09:26:46 UTC [Info] starting refreshing cpl 0 with key CIQAAA44GAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA (routing table size was 0)
2020-09-17 09:26:46 UTC [Info] failed when refreshing routing table
+ echo 'Coda process exited with status code 99'

Logs for 2 hour:
crash.log

Snark Worker crashed every 5 minutes:
error: "((rpc_error (Connection_closed (\"EOF or connection closed\")))\n (connection_description (\"Client connected via TCP\" (07176ec01a6e 39551)))\n (rpc_tag rpc_parallel_plain_0) (rpc_version 0))"

I believe this was fixed by #6036


Provided Flow in Repository does not work with latest IE Flow Creator Version

Issue-template
Summary
Provided Flow in Repository does not work with latest IE Flow Creator Version
https://github.com/industrial-edge/Developer-Guide-Hands-on-App/blob/main/src/solution/IE Flow Creator Flows/flow_data_gen.json
When importing flow in function you get following error message

to fix error variable must be declared

Version of the used components

IE Flow Creator: V1.10.0

Should be fixed by #14