Sqlite is not currently supported due to its BulkInsert implementation.

I'm trying to execute the BulkInsertOrUpdateAsync function over a Sqlite but it doesn't work.
This is how I'm creating the context:

Does SQLite support these bulk operations?

What exactly is the exception, and can you write a test where the issue would be reproducible.

This is the exact exception; System.NotSupportedException: 'Sqlite is not currently supported due to its BulkInsert implementation.' It happens when executing the BulkInsertOrUpdateAsync function whit the IncludeGraph option.

using EFCore.BulkExtensions;
using Microsoft.Data.Sqlite;
using Microsoft.EntityFrameworkCore;
using System;
using System.Data.Common;
using System.Linq;
using System.Threading.Tasks;
namespace NetCoreConsole
{
class Program
{
static async Task Main(string[] args)
{
var connection = await CreateConnectionAsync();
var dbContext = await CreateContextAsync(connection);
var states = Enumerable.Range(1, 10).Select(x => new State
{
Id = x,
Code = $"st-{x}",
Name = $"state-{x}",
City = new City
{
Id = x,
Code = $"ct-{x}",
Name = $"city-{x}",
}
});
        await dbContext.BulkInsertOrUpdateAsync(states.ToList(), new BulkConfig { IncludeGraph = true });
        Console.WriteLine($"There are {dbContext.States.Count()} State rows!");
    }

    public static async Task<DbConnection> CreateConnectionAsync()
    {
        var connection = new SqliteConnection("Filename=:memory:");
        await connection.OpenAsync();

        return connection;
    }

    public static async Task<TestDbContext> CreateContextAsync(DbConnection connection)
    {
        var optionsBuilder = new DbContextOptionsBuilder<TestDbContext>();
        optionsBuilder.UseSqlite(connection);
        SQLitePCL.Batteries.Init();

        var context = new TestDbContext(optionsBuilder.Options);
        await context.Database.EnsureDeletedAsync();
        await context.Database.EnsureCreatedAsync();

        return context;
    }

    public class TestDbContext : DbContext
    {
        public DbSet<State> States { get; set; }

        public TestDbContext(DbContextOptions options) : base(options) { }
    }

    public class State
    {
        public int Id { get; set; }
        public string Code { get; set; }
        public string Name { get; set; }

        public int CityId { get; set; }
        public City City { get; set; }
    }

    public class City
    {
        public int Id { get; set; }
        public string Code { get; set; }
        public string Name { get; set; }
    }
}

}

This is a simple console program to reproduce the error.
Program.txt

Sqlite does not support IncludeGraph.


Support for OpenAPI description in a Infragistics AppBuilder integration use case

What happened?
It seems that DAB does not generate enough information when an endpoint is called by Infragistics AppBuilder that requires some details to be able to use the endpoint correctly, see the description here. I searched for possibilities to configure the expressivness of DABs openapi interface but did not find any information about such a possibility. In a Infragistics forum post, see here, the problem is described and solved with access to the underlying endpoint source code, i don't feel confident to go to the source code of DAB to check this. Thanks for your time in helping me out with this topic.
Version
latest
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
REST
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

It has been determined that Infragistics AppBuilder is looking for a missing property in the schema, see below

It is unclear if this is required by the OpenAPI specs or if it is a miss interpretation by Infragistics.

Here's the code that creates the Schema with "properties" but no "type".
https://github.com/Azure/data-api-builder/blob/466c18a9c2eb9ccc808020319749f7681b13cfed/src/Core/Services/OpenAPI/OpenApiDocumentor.cs#L938-L941

I think this needs to be considered as a bug.
The lack of the "type" permits any other type as valid:

The mere presence of "properties" is not enough to specify type object.

Thanks make sense. How do we go forward from here ?

Thank you for reporting, @chrohrbach. I'm working on a fix.
I found a relevant thread that discusses whether type is a required property. Consensus is that type isn't required:

https://github.com/OAI/OpenAPI-Specification/issues/1657

OpenAPI-Specification discussion

https://github.com/PaloAltoNetworks/docusaurus-openapi-docs/issues/430

Example of how different tooling handles type or missing type differently.

Ultimately, different tooling handles the presence of the type property differently. Some may try to guess the type when not present:

e.g. object when the property properties exists.

That said, there is no reason why DAB shouldn't add this so that Infragistics tooling can work. I'm curious whether this is the only error that Infragistics emits when evaluating the OpenAPI document generated by DAB.

Thx for you work

Hi @seantleonard ,
Thank you for picking up this. While it's true that type is not required, I think it's incorrect in the context of DAB response.

type + properties means "it must be an object and the properties are as described
properties only means "it can be any type, when it's an object the properties are as described
(see my validation example with a plain integer in the previous post).

DAB response is always an object and it's best described as such as it will improve compatibility.
I'm glad you agreed, I just wanted to provide additional input for the decision.
Thanks again

Hi @seantleonard ,
Thank you for picking up this. While it's true that type is not required, I think it's incorrect in the context of DAB response.

type + properties means "it must be an object and the properties are as described
properties only means "it can be any type, when it's an object the properties are as described
(see my validation example with a plain integer in the previous post).

DAB response is always an object and it's best described as such as it will improve compatibility. I'm glad you agreed, I just wanted to provide additional input for the decision. Thanks again

Sorry to imply that I was trying to justify whether to do this or not. I fully intend to do so.
I intended to figure out whether type was required because I wanted to identify why https://github.com/microsoft/OpenAPI.NET didn't complain about missing type. An error if type were required would have helped prevent this becoming an issue in the first place. Thanks for bringing this to my attention.

Related #2262


Additional User model properties

Is it possible to configure the User model properties to return other data from the x api?  Or possibly set a custom User object at runtime?
For instance
You are current providing isVerified
this.isVerified = user.is_blue_verified;
But, I would like to get the verified_type as well
this.isVerified = user.is_blue_verified;
this.verifiedType = user.legacy.verified_type;

It's not possible to configure the User model by the consumer of the API, and any additional fields must be included by changing the User model at the source level.
However, you can get access to the raw response data using the FetcherService class. From the raw response, you can pick up whatever fields you like.
I can keep this issue open on my end and add the requested properties to the User model in the meantime.

Great, I will take a look. Thx


TypeError when mixed with the Tasks plugin (interferes with Preview mode processing from Tasks)

When both Tasks and Banners are enabled, there is a TypeError output to the console from Banners and the Preview mode processing of checkbox lists that Tasks performs doesn't work. The error only shows up in the console if both Banners and Tasks are enabled. If I disable Tasks then the error from the Banners code does not appear. This does not prevent Banners from putting the image at the top of Preview, though. I was going to submit a Tasks bug but the error is coming from the Banners code (at least judging by the stack trace below).
There might be issues inter-operating with other plugins but Tasks is the only one that I have that is causing an issue.
Uncaught (in promise) TypeError: Cannot read property 'hasClass' of null
    at BannersPlugin.eval (eval at <anonymous> (app.js:1), <anonymous>:1542:69)
    at Generator.next (<anonymous>)
    at eval (eval at <anonymous> (app.js:1), <anonymous>:31:71)
    at new Promise (<anonymous>)
    at __awaiter (eval at <anonymous> (app.js:1), <anonymous>:27:12)
    at eval (eval at <anonymous> (app.js:1), <anonymous>:1540:57)
    at Function.<anonymous> (app.js:1)
    at app.js:1
    at Object.next (app.js:1)
    at app.js:1

Obsidian Version: 0.12.15
Banners Version: 1.1.0
Tasks Version: 1.3.0

Found the problem. I was basically doing a bad check for parent elements, and the Tasks plugin probably made the needed changes to make that apparent, so this could be apparent with other plugins/scenarios too.
The plugin should only do things with the frontmatter block, so that's fixed now and will be in the next release. Merci for the heads up!


rktlet: add network plugin name flag

According to the CRI Networking Specification[1], the runtime shim is
responsible of managing pod's network life cycle. However, the current
CRI API doesn't expose options like network-plugin, cni-bin-dir, or
cni-conf-dir.
This adds a new --net option to the rktlet so users can specify what
network they want to use for pods. We rely on rkt to set up the network
so these are the paths where rkt looks for CNI configurations and
binaries:

Network configurations: /etc/rkt/net.d
Plugin binaries: /usr/lib/rkt/plugins/net

Note that rkt also includes some plugins[2] in the default stage1.

LGTM


Css is not Attached to Education Website

Describe the Feature you want to end
Add CSS
Expected behavior
The website will look more attractive.
Screenshots (optional)

Additional context (optional )
I want to work on it . Please assign this issue to me

I want to work on it . Please assign this issue to me

Hi, I want to work on this issue, could you please assign this issue to me?

I Have a good Knowledge of CSS ,'
Please assign it to me

I would like to work on this issue.
I'm proficient in CSS, please assign it to me.

please assign me this issue under GSSoC'23.


Adding a network.count metric for meraki

Enable with
         preferences:
           show_network_attr: true

This will add in a network.count metric for meraki networks, listing out each network's tags.

Sounds good, staging going out now.


Why only 5 Residual Blocks?

Hey,
Just wondering why you opted for 5 Residual Blocks as oppose to the 16 suggested in the paper?
Was this a runtime performance decision?
Kind regards,
Liam

@l-oneil for runtime performance


Need Boss Death Sound(s)

Not sure if we need a different sound for wizard/poop monster - @wadek2 ?
This will play when boss is destroyed, as it is blinking red/destroyed

@esalling23 These are in this folder under "Bad" then "Wizard Hit": https://drive.google.com/drive/folders/1jSCwT-fL0zIqUXmf9B5Pe86QMUekYmUa?usp=sharing

I think they should have different sounds. On Tuesday Karen said she was going to have a sound for the poop monster hit (like a splat).

I thought those were the sounds for individual hits, not the actual boss being defeated - do we have a specific sound for the wizard/monster being defeated? this would be before the player gets the "Super" screen, as the wizard is animating to its death

@esalling23 Wait, you're right. Her Google doc from Tuesday says:
STILL TO DO:
Tracks:
-Finish Victory Fanfare
-Shorten Boss themes
-Clean up tracks
Sounds
-Wizard laugh
-Wizard defeat
-Unhypnotise villager
-Critter hit
-1 or 2 bubble pops x x
-Pew pew ambience
-Poop monster splat
-Poop monster defeat splat?

I'll email her now to follow up.


For 5.0.0, use bootstrapping flow for previously-source-built nupkgs rather than downloading them from N-1

Could stop using the cached N-1 => N flow. (Until we get into 5.0 servicing?)

I brought this up with the team and we think it makes sense for 5.0.0. Instead of downloading a previously-source-built.tar.gz, we'll pack up the nupkgs produced by the production build. I'm hopeful it's a tweak to the tarball generation code rather than something drastic. (We'll still produce previously-source-built.tar.gz files so that we can go back to a sort-of N-1 => N flow for 5.0.1.)

https://github.com/dotnet/source-build/pull/1828#issuecomment-726367688
With this, we shouldn't have to do https://github.com/dotnet/source-build/issues/1878, because they solve the same problem.

Done in https://github.com/dotnet/source-build/pull/1881.


RightAlt+I openes inspect.

Some keyboard have RightAlt+I as another character: î
It is annoying to have inspect menu pop up every time I type that character.
PS: I don't only type in English, so that character pops up quite frequently for me.

Fixed, will release an update soon.


[BUG] Responsive menu doesn't appear after set custom font_size

Hello folks,
I tried to minimize the default font because a little bit giant for me. After followed official instruction and documentation, I created new font family, I set on params.toml
font = "my_font" #this one installed correctly in new root folder data/fonts
font_size = "s".
After that, I tried to test my website in desktop and tablet (horizontal), perfect. But in mobile phone and tablet (vertical mode) , same on developer mode in desktop version, responsive menu doesn't appear.
Maybe a bug in css style?
Please check it.
Cheers!

The "bug" appear if the google_fonts has:
"Ubuntu:400,700|Merriweather|Roboto+Mono"
Second setting and responsive menu work correctly:
"Ubuntu:300,400|Merriweather:300,400|Roboto+Mono:300,400"
font_size = s (both combination).

Sure, if you change the fonts, you'll need to include new fonts for the font weights that are used on your site. In the current version of Academic this is just normal and bold. If you're not sure, you can include all main variants.


RTC feed freezes after few minutes since updating to 1.8.5

With 1.8.4 it didn't happen, I have the feed running on my HA dashboard for 16 hours a day every day. Updating to 1.8.5 and the camera feed freezes after something like 20 minutes.
Reverting back to 1.8.4 fixes the problem for me. My tablet is Fire HD 10 (2021), running Fully Kiosk app.

You need to provide more info about your setup. More than 40 files changed since v1.8.4

What kind of information do you think would help in trying to debug?
I have the camera coming in from the tuya smartlife integration.
My go2rtc.yaml  file looks like this:
api:
  listen: <IP_ADDRESS>:1984
  password: '123'
  username: admin
rtsp:
  password: '123'
  username: admin
streams:
  my_camera:
    - echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera

I then have the camera in a card like this:
  - type: custom:webrtc-camera
    url: rtsp://admin:123@<IP_ADDRESS>:8554/my_camera?mp4

go2rtc add-on log:
21:32:08.071 INF go2rtc version 1.8.5 linux/amd64
21:32:08.073 INF [rtsp] listen addr=:8554
21:32:08.076 INF [api] listen addr=<IP_ADDRESS>:1984
21:32:08.080 INF [webrtc] listen addr=:8555
21:32:08.083 INF [hass] listen addr=<IP_ADDRESS>:1984
21:42:14.343 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"
21:53:04.299 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"
22:03:05.835 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"

These warnings were also present in 1.8.4 too but maybe something in 1.8.5 doesn't like these and is causing a freeze.

Tuya already talking a lot. Check the other issues. This is a duplicate. And it looks like this is not go2rtc problem

I don't see another issue related to feed freezing. If it was tuya then why would 1.8.4 work.

https://github.com/AlexxIT/go2rtc/issues/908
Are you really sure that v1.8.4 doesn't has this problem?

Positive 100% on 1.8.4 my feed does not freeze, I have it running all day on the dashboard.
And the logs produce the same EOF warning.
22:15:30.865 INF go2rtc version 1.8.4 linux/amd64
22:15:30.865 INF [rtsp] listen addr=:8554
22:15:30.866 INF [api] listen addr=<IP_ADDRESS>:1984
22:15:30.866 INF [webrtc] listen addr=:8555
22:15:30.870 INF [hass] listen addr=<IP_ADDRESS>:1984
22:26:37.788 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"
22:36:39.459 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"
22:46:40.939 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"
22:56:42.445 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"
23:06:43.953 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url="echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.camera"

Reconnection issue should be fixed in latest master version

I've tried the master version, and the feed still freezes every ten minutes (Tuya Pet Feeder), so I have to use automation to restart go2rtc addon every ten minutes lol


Create MicrosoftAzureandGP.md

Docs Build status updates of commit 1f89e49:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 46, Column 5: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/free/search/?OCID=AID2200277_SEM_ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&ef_id=ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&msclkid=ae067f8b5cdd14162ab71d3f9d0ecdcf' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 64, Column 4: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/free/search/?OCID=AID2200277_SEM_ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&ef_id=ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&msclkid=ae067f8b5cdd14162ab71d3f9d0ecdcf' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 83, Column 5: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 83, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1f89e49:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 46, Column 5: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/free/search/?OCID=AID2200277_SEM_ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&ef_id=ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&msclkid=ae067f8b5cdd14162ab71d3f9d0ecdcf' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 64, Column 4: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/free/search/?OCID=AID2200277_SEM_ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&ef_id=ae067f8b5cdd14162ab71d3f9d0ecdcf:G:s&msclkid=ae067f8b5cdd14162ab71d3f9d0ecdcf' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 83, Column 5: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 83, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1311c31:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@theley502 Is there a reason why you want the link to get an Azure account to be based on search rather than a direct link to https://azure.microsoft.com/free/?

Docs Build status updates of commit 1facce7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 89, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp001.png'.
Line 89, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub' is duplicated. Within an article, alt text must be unique.
Line 93, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp002.png'.
Line 93, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 86bde1b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/media/azuregp001.png
:white_check_mark:Succeeded
View

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 89, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub' is duplicated. Within an article, alt text must be unique.
Line 93, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp002.png'.
Line 93, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub' is duplicated. Within an article, alt text must be unique.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 47ae1ee:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/media/azuregp001.png
:white_check_mark:Succeeded
View

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 91, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp002.png'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2edcc06:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/media/azuregp001.png
:white_check_mark:Succeeded
View

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 87, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub image 1' is duplicated. Within an article, alt text must be unique.
Line 91, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp002.png'.
Line 140, Column 1: [Warning: insecure-link - See documentation] Link 'http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 158, Column 307: [Warning: insecure-link - See documentation] Link 'http://www.microsoft.com/licensing/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 171, Column 208: [Warning: insecure-link - See documentation] Link 'http://go.microsoft.com/fwlink/?linkid=293448&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 171, Column 418: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/microsoft-azure-leads-the-industry-in-iso-certifications/#:~:text=We%20are%20happy%20to%20announce%20that%20Microsoft%20Azure,to%20meet%20a%20wide%20range%20of%20regulatory%20obligations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 174, Column 132: [Warning: insecure-link - See documentation] Link 'http://go.microsoft.com/fwlink/p/?linkid=131004&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 233, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp003.png'.
Line 233, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub image 1' is duplicated. Within an article, alt text must be unique.
Line 244, Column 511: [Warning: hard-coded-locale - See documentation] Link 'http://azure.microsoft.com/en-us/pricing/details/virtual-machines/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 244, Column 511: [Warning: insecure-link - See documentation] Link 'http://azure.microsoft.com/en-us/pricing/details/virtual-machines/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 246, Column 9: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics/s-e/gp/MDGP2018_System_Requirements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 268, Column 14: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/availability' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 276, Column 436: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview?view=azuresql' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 283, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-and-updates' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 295, Column 457: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/concepts-and-best-practices' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 301, Column 22: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 302, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-cli' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 246, Column 9: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/dynamics/s-e/gp/MDGP2018_System_Requirements' will be broken in isolated environments. Replace with a relative link.
Line 268, Column 14: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/virtual-machines/availability' will be broken in isolated environments. Replace with a relative link.
Line 276, Column 436: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview?view=azuresql' will be broken in isolated environments. Replace with a relative link.
Line 276, Column 436: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview?view=azuresql
Line 283, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-and-updates' will be broken in isolated environments. Replace with a relative link.
Line 295, Column 457: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/virtual-network/concepts-and-best-practices' will be broken in isolated environments. Replace with a relative link.
Line 301, Column 22: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-portal' will be broken in isolated environments. Replace with a relative link.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6e192f1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/media/azuregp001.png
:white_check_mark:Succeeded
View

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 87, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub image 1' is duplicated. Within an article, alt text must be unique.
Line 91, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp002.png'.
Line 140, Column 1: [Warning: insecure-link - See documentation] Link 'http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 158, Column 307: [Warning: insecure-link - See documentation] Link 'http://www.microsoft.com/licensing/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 171, Column 208: [Warning: insecure-link - See documentation] Link 'http://go.microsoft.com/fwlink/?linkid=293448&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 171, Column 418: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/microsoft-azure-leads-the-industry-in-iso-certifications/#:~:text=We%20are%20happy%20to%20announce%20that%20Microsoft%20Azure,to%20meet%20a%20wide%20range%20of%20regulatory%20obligations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 174, Column 132: [Warning: insecure-link - See documentation] Link 'http://go.microsoft.com/fwlink/p/?linkid=131004&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 233, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp003.png'.
Line 233, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub image 1' is duplicated. Within an article, alt text must be unique.
Line 244, Column 511: [Warning: hard-coded-locale - See documentation] Link 'http://azure.microsoft.com/en-us/pricing/details/virtual-machines/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 244, Column 511: [Warning: insecure-link - See documentation] Link 'http://azure.microsoft.com/en-us/pricing/details/virtual-machines/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 246, Column 9: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics/s-e/gp/MDGP2018_System_Requirements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 268, Column 14: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/availability' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 276, Column 436: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview?view=azuresql' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 283, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-and-updates' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 295, Column 457: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/concepts-and-best-practices' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 301, Column 22: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 302, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-cli' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 309, Column 344: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 310, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 329, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist?view=azuresql' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 371, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics-gp/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 386, Column 90: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics-gp/installation/microsoft-sql-server-configuration' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 387, Column 256: [Warning: hard-coded-locale - See documentation] Link 'http://technet.microsoft.com/en-us/library/ms345223(v=sql.110).aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 387, Column 256: [Warning: insecure-link - See documentation] Link 'http://technet.microsoft.com/en-us/library/ms345223(v=sql.110).aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2cb55a5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/installation/MicrosoftAzureandGP.md
:warning:Warning
View
Details

dynamics-gp/installation/media/azuregp001.png
:white_check_mark:Succeeded
View

dynamics-gp/installation/MicrosoftAzureandGP.md

Line 87, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub image 1' is duplicated. Within an article, alt text must be unique.
Line 91, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp002.png'.
Line 140, Column 1: [Warning: insecure-link - See documentation] Link 'http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 158, Column 307: [Warning: insecure-link - See documentation] Link 'http://www.microsoft.com/licensing/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 171, Column 208: [Warning: insecure-link - See documentation] Link 'http://go.microsoft.com/fwlink/?linkid=293448&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 171, Column 418: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/microsoft-azure-leads-the-industry-in-iso-certifications/#:~:text=We%20are%20happy%20to%20announce%20that%20Microsoft%20Azure,to%20meet%20a%20wide%20range%20of%20regulatory%20obligations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 174, Column 132: [Warning: insecure-link - See documentation] Link 'http://go.microsoft.com/fwlink/p/?linkid=131004&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 233, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'media/azuregp003.png'.
Line 233, Column 1: [Warning: duplicate-alt-text - See documentation] Alt text 'Azure sub image 1' is duplicated. Within an article, alt text must be unique.
Line 244, Column 511: [Warning: hard-coded-locale - See documentation] Link 'http://azure.microsoft.com/en-us/pricing/details/virtual-machines/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 244, Column 511: [Warning: insecure-link - See documentation] Link 'http://azure.microsoft.com/en-us/pricing/details/virtual-machines/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 246, Column 9: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics/s-e/gp/MDGP2018_System_Requirements' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 268, Column 14: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/availability' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 276, Column 436: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/business-continuity-high-availability-disaster-recovery-hadr-overview?view=azuresql' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 283, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-and-updates' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 295, Column 457: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/concepts-and-best-practices' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 301, Column 22: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 302, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-cli' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 309, Column 344: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 310, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 329, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist?view=azuresql' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 371, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics-gp/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 386, Column 90: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dynamics-gp/installation/microsoft-sql-server-configuration' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 387, Column 256: [Warning: hard-coded-locale - See documentation] Link 'http://technet.microsoft.com/en-us/library/ms345223(v=sql.110).aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 387, Column 256: [Warning: insecure-link - See documentation] Link 'http://technet.microsoft.com/en-us/library/ms345223(v=sql.110).aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Ignoring remaining warnings...


expose admin ports in service

This PR exposes the admin port in app-sre deployment

LGTM
Please update the routes file in app-interface as well.


Needs to display errors

In brackets version 1.8.0-17108 needs to display the reason the compiling has failed and it's hanging, instead of just stating that it's timed out.

@gfaiers What version of the plugin are you using and what OS are you using?

2.05 plugin
Windows 10 OS.
Using it a bit more in depth, it feels like it just crashes randomly? Currently developing a simple clock in sass and it needs me to close and reopen brackets every 2 mins due to it timing out.
Regards,
Geoff Faiers
www.gfaiers.com
On 13 January 2017 at 09:00:45 -00:00, Brainzyy<EMAIL_ADDRESS>wrote:

@gfaiers https://github.com/gfaiers What version of the plugin are you using and what OS are you using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/jasonsanjose/brackets-sass/issues/186#issuecomment-272393492, or mute the thread https://github.com/notifications/unsubscribe-auth/ARKUqKbNY3xSrI7YKqAaaMbHspFuqDeOks5rRz09gaJpZM4Lionp.

@gfaiers I'll check it out ASAP, but I have exams right now, so don't have much time.

@gfaiers My exams are done and I can look at this now. Can you maybe supply me with a project (in private if you prefer that), so that I can check out the random crashes.

@gverm the projects I've had this issue with are on my account now; although it's not to do with the projects, it happens even if I make a new project.  Next time I notice it I'll look at what I did prior, think it happens every time I use Brackets, but if I do something else with it, not straight into working on css.


Patch filters v2 new

Major changes:

add the new custom whole dir prefix \
disable * only path components in filters
improve filters validity checks with many bug fixes
various bug fixes in filters
fix crashes in ja/ru (message formatter)
fix potential NPE error in debug code during sync
reduce debug overhead during sync

Sorry for the many commits. I did not have time to clean and provide less but more structured history. They show the main changes at first, before i fixed and cleaned in the last ones

Added a small fix for Add dir button checks

please see issue track for details

added a check in file filters with path (undocumented support for file filters with path) to not allow asterisk in path, except in the file name

Hopefully my last enhancement in filters
The previous way invalid_chars[] was implemented was not good because editFilter() cannot know the type of filter we're editing
Now, editFilter() is passed the filter type directly and we can properly make specific checks on file and dir filters when Ok button is pressed and before adding the invalid filters
In SMBSync3, this can also be used to add more checks when editing existing wifi filters
Hope you can merge this long pull request
I am holding any further commits until all this is validated by you
Best regards

Hopefully my last enhancement in filters
The previous way invalid_chars[] was implemented was not good because editFilter() cannot know the type of filter we're editing
Now, editFilter() is passed the filter type directly and we can properly make specific checks on file and dir filters when Ok button is pressed and before adding the invalid filters
In SMBSync3, this can also be used to add more checks when editing existing wifi filters
Hope you can merge this long pull request. I am holding any further commits until all this is merged
Best regards
Edit: review of yesterday changes and small cleanup

Your changes have been merged.
Best regards.


fix(cdn): olny refresh bug

:tada: This PR is included in version 1.7.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update or remove TODOs

This updates or removes all TODOs in the code base. If being updated, the corresponding GitHub issue will be linked
with the TODO.
Closes #492.

This is looking great so far! And I really like your choice of imbedding code into the issues, so the developer knows where to look. I have a couple suggestions when your creating your issues.
In general, I would try to be as specific as possible where the issue is when your writing these issues, such as such as component and part. Imbedding the code definitely helps with this, but I think this will make it crystal clear.

For example in #498: instead of saying "this check" say something like "the isRelevantId() check for determining controlParts in OSCALControlModifiication.js

This might be a little more difficult to address and you might have to ask who left the TODO, but generally we also want to note the "why" of the fix when creating an issue. This could be such as the NIST standard has been updated (and link a reference to documentation) or this is a new user feature. Some of these might be okay to skip for now and we come back to address the "why" later.

Consistency in spacing. We want the TODO to be "attached" to the code it's documenting, so generally, remove the blank lines between the TODO and the following code.
Consistency in formatting. Let's put the URL on its own line at the end of the comment. We don't want comment lines to get too long because they get hard to read.

Thank you for the feedback! My most recent commit has fixed these styling inconsistencies and also should have addressed your requested changes.


Hint for Radial Chart Not Customizable w/ Data

Is there any way to create a customizable hint (specifically) on a radial chart that displays reads in data from an outside source (i.e. a JSON.
We want our hint to say something like
"theta: 75"
"name: apples"
But, we want to make a donut chart that displays the hint, WITHOUT the geometry, which it currently does as shown in the picture below:

Currently our data looks like this:
[      {theta: 75, name: 'apples'},      {theta: 95, name: 'oranges'} ]
<RadialChart
                    className={'donut-chart-example'}
                    innerRadius={140}
                    radius={200}
                    const getAngle={d => d.theta}
                    data={this.props.json.data}
                    onValueMouseOver={v => this.setState({ value: v })}
                    onSeriesMouseOut={v => this.setState({ value: false })}
                    width={500}
                    height={500}
                    padAngle={0.04}
                    >
                    {value !== false && <Hint value={value}>
                        </Hint>}
</RadialChart>

Hey @ec13000ibm , did you find any fix or work around for this issue?


Rename planes to channels

To have a name that is more in line with NoCs, channels are closer to Virtual Channels (VCs). See Mello et al., "Virtual Channels in Networks on Chip: Implementation and Evaluation on Hermes NoC"

yeah I agree, makes sense


Add useActiveImportMap option to resolveModuleSpecifier

I already wrote the implementation for it since I need the feature: ayoreis/importmap.
It uses import.meta.resolve which takes into account the current import map, and compares that to serialiseURL(new URL(specifier, import.meta.url)), if not equal (meaning using import map) it returns the import.meta.resolve resolved, if equal it returns the manually resolved one.
When useActiveImportMap is true It does not account for the user-specified importMap option, which could be implemented, but since neither Deno nor the browser has a way of specifying more than one import map I left it like this.
I also didn't write automatic tests yet (I did do by manually testing different locations and import maps).
Do you want to merge this? I also made other changes while working on this, you can merge those if you wish.

Just realized this won't work with with import map scopes.

What is the use case of this exactly?

I made a ponyfill for dynamic imports to be used in Deno Deploy and deno compiledd modules. I use esbuild with esbuild_deno_loader (that uses this) to compile a module to an IIFE and run that (via Function), and I want it to resolve using the current import maps without the user needing to pass it as an argument.

Thanks for your suggestion. I would like to keep that repo as a bare spec implementaion without any runtime specific stuff.


Same tag should not be be added to same user multiple times

currently if the super user adds the same tags multiple times to the user it gets added ,we need to fix that and make sure that a tag is applied to a user only one time with the same level

Hey @vinayak-trivedi shall I take this task


make langchain_community a prod requirement

Fixes: https://github.com/ansible/ansible-ai-connect-service/issues/1113
Fixes: https://issues.redhat.com/browse/AAP-25218

I believe we should make Langchain optional since we don't need it for the SAAS service https://setuptools.pypa.io/en/latest/userguide/dependency_management.html#optional-dependencies


same cv splits across models

adds random_state() to KFold to have the same  splits across models
adds checks for cross_validate object, currently only allowing KFold

closes #261

Codecov Report
Attention: Patch coverage is 94.73684% with 1 line in your changes missing coverage. Please review.

Project coverage is 92.48%. Comparing base (3daa3ed) to head (421b56e).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

autoemulate/utils.py
85.71%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #265      +/-   ##
==========================================
+ Coverage   92.45%   92.48%   +0.03%
==========================================
  Files          62       62
  Lines        3618     3635      +17
==========================================
+ Hits         3345     3362      +17
  Misses        273      273

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


IS Analytics dashboard not displaying data in real time

Describe the issue:
The dashboard of IS Analytics 5.8 is not showing data in real time. Data in the widgets is only updated when the dashboard is restarted.
Environment information**:**

Product Version: IS Analytics 5.8.0

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Add prelude support

This PR will enable prelude snippet support. What does that mean? Some modules require some shared code to express examples more easily (and to reduce repetitive writing). Such as the pages/belt_docs/set.mdx file.
How to use it?
Preferably in the beginning of the module description, you add your prelude as a codeblock with a re prelude metastring. This will still render the codeblock like any other example, but in the testing script, it will do following extra tasks:

It will test all preludes before executing any examples (if a prelude doesn't work, all examples will fail anyways)
If the preludes do work, the test script will find and concatenate all prelude codeblocks, and prepend them to each example code before execution

Also this PR fixes an issue with line number parsing / replacement when a syntax parse error occurs.
Fixes #55

@ryyppy my only concern is that most people probably won't read the Module description. So they might miss it an now copy & pasting the example will fail.
We could add a small link/hint to the prelude the examples that use it, but not sure if it's too noisy.

@nikgraf What if we had a copy button which always includes the prelude (when necessary)?

@fhammerschmidt I think it's a missleading UX if the copy button contains more than the actual visible text. (maybe that's the reason I also never use them and just select and copy text). If others do that as well they would miss out on the working example.

@nikgraf to think about it from a concrete perspective: If I would go ahead and copy the example for let's say, some Set function, and I get a compile error that the CmpInt module is missing, I'd probably go back to the docs page and CMD-F for said module and find the prelude example... I don't think it will cause many troubles (maybe we will get a lot of feedback, then we need to think about it anyways)


Function references

This patch, written by @dhil and I, implements the (complete) function references proposal, forming the wasmtime side of the existing pull request bytecodealliance/wasm-tools#701.   It is missing some obvious things:

call_ref is simply translated as a cranelift indirect_call.    A faster cranelift indirect call that does not check the callee signature can (and should) eventually be added and used.   Further, no null check is elided.
The wasm-tools PR has advanced past the version we depend on here.    We hope to update all at once, once the wasm-tools side has fully settled.    This will result in the removal of a number of ValType::Bot branches, the addition of the type annotation on call_ref, and a handful of other convenient things.    The version we depend on is called func-ref-2, if you need to reference it*.
Wasmtime, too, has of course advanced past our parent.   I tried to rebase on the latest changes, but due to particular Cargo.toml changes, I think this will be much easier when we've retargetted to the latest wasm-tools#701 and can keep our dependencies consistent in the history

Otherwise, things should be mostly obvious.    Typed function references are represented by the existing untyped function references.   Even though it's held up by wasm-tools, we ended up with a fairly polished changeset that we figured we could send out and get feedback on.    There's no rush on our end, as we've been happily using this in our typed continuations work for some time now.    But we're happy to discuss any changes, problems, or suggestions!
* We added a public peek method to the validator to attain a signature for call_ref.   This is now unnecesary because call_ref comes with a type annotation, and will disappear fairly conveniently.

call_ref is simply translated as a cranelift indirect_call. A faster cranelift indirect call that does not check the callee signature can (and should) eventually be added and used. Further, no null check is elided.

call_indirect doesn't check the function signature, nor does it check for null pointers.

I'm interested in resuming work on this patch and dedicating the necessary time to bring it into an acceptable state. I have a patch which merges this PR with the recent changes to main (c.f. effect-handlers/wasmtime#13). I will merge that patch into this PR later today.
I think the current status is as follows:

Compatible with latest wasm-tools
All new function reference instructions have been implemented (save for return_call_ref) (tested on x86_64).
10 test case failures:

failures:
    wast::Cranelift::spec::function_references::br_table
    wast::Cranelift::spec::function_references::br_table_pooling
    wast::Cranelift::spec::function_references::linking
    wast::Cranelift::spec::function_references::linking_pooling
    wast::Cranelift::spec::function_references::return_call_ref
    wast::Cranelift::spec::function_references::return_call_ref_pooling
    wast::Cranelift::spec::function_references::table
    wast::Cranelift::spec::function_references::table_pooling
    wast::Cranelift::spec::function_references::type_equivalence
    wast::Cranelift::spec::function_references::type_equivalence_pooling

test result: FAILED. 872 passed; 10 failed; 10 ignored; 0 measured; 0 filtered out; finished in 77.91s

Here return_call_ref is expected to fail as we have not implemented the tail calls proposal. I haven't worked out why linking and type_equivalence fail yet. The test br_table fails because of how the wast crate of wasm-tools elaborates single element tables
(module
  (type $t (func))
  (func $tf)
  (table $t (ref null $t) (elem $tf)))

The table test fails due to the incompleteness of the type reconstruction procedure wasmtime::values::Val::ty(). The procedure has to infer the nullability of an ExternRef or FuncRef by looking at their respective shape, which is impossible.
I will probably need some help with this latter issue as it seems to require a slight redesign/refactor to keep source value type information around, at least in the wast crate of wasmtime. I will probably also need some help with diagnosing the remaining failure cases. I am also positive that there are several code quality improvements that need to be implemented in order to make this PR satisfactory.

This review got auto-assigned to me but I think @fitzgen and @alexcrichton have the right context for the review here.

@alexcrichton @fitzgen I have reverted the changes to the wasmtime public API. The end result is not too bad; there are a couple of more test failures now. I haven't looked into the failures in detail yet.

Some things I'm seeing:

I sent https://github.com/effect-handlers/wasmtime/pull/19 to surface the failures here on this PR
One test failure, wast::Cranelift::spec::function_references::linking, relates to this function which needs to be souped up for typed function references. Note though that this function will need to grow &ModuleTypes arguments to perform the subtyping check between two different modules (this is basically the same code that's in wasmparser, just at link-time instead of validation-time).
wast::Cranelift::spec::function_references::table looks like it may be a bug in table initialization?
wast::Cranelift::spec::function_references::br_table is failing due to https://github.com/bytecodealliance/wasm-tools/pull/952 I think
wast::Cranelift::spec::function_references::type_equivalence looks like it may be some sort of code generator bug? Unsure.

There are additionally a number of tests as you've found which all panic due to the one you inserted to avoid changes to the public API. Those tests will need to be skipped as-is from the upstream testsuite, but they can be copied to to tests/misc_testsuite with updates to run in Wasmtime.

Some things I'm seeing:
* I sent [Get more CI passing effect-handlers/wasmtime#19](https://github.com/effect-handlers/wasmtime/pull/19) to surface the failures here on this PR

* One test failure, `wast::Cranelift::spec::function_references::linking`, relates to [this function](https://github.com/bytecodealliance/wasmtime/blob/ef7af28ef095277f5979dcbc6ff03964c1e0ba12/crates/wasmtime/src/types/matching.rs#L183-L193) which needs to be souped up for typed function references. Note though that this function will need to grow `&ModuleTypes` arguments to perform the subtyping check between two different modules (this is basically the same code that's in `wasmparser`, just at link-time instead of validation-time).

* `wast::Cranelift::spec::function_references::table` looks like it may be a bug in table initialization?

* `wast::Cranelift::spec::function_references::br_table` is failing due to [Support for Wast table initialisation syntactic sugar with typeful references wasm-tools#952](https://github.com/bytecodealliance/wasm-tools/pull/952) I think

* `wast::Cranelift::spec::function_references::type_equivalence` looks like it may be some sort of code generator bug? Unsure.

There are additionally a number of tests as you've found which all panic due to the one you inserted to avoid changes to the public API. Those tests will need to be skipped as-is from the upstream testsuite, but they can be copied to to tests/misc_testsuite with updates to run in Wasmtime.

Excellent, thank you! I am down to two failures now type_equivalence and table.

I have been trying to track down the remaining two failures. In the table.wast file, the problem is that tables aren't properly initialised. Looking at the code it indeed seems like table initialisers get ignored altogether (https://github.com/bytecodealliance/wasmtime/blob/main/crates/environ/src/module_environ.rs#L303-L307), which would explain why table entries always seem to be initialised to null (c.f. https://github.com/bytecodealliance/wasmtime/blob/main/crates/runtime/src/instance.rs#L872-L874). From reading the code, I understand that great care is being taken to ensure lazy initialisation of tables, and thus, I wonder what semantics you want for tables with initialising expressions? @alexcrichton @fitzgen

Looking at the code it indeed seems like table initialisers get ignored altogether

Indeed! Table intializers were added with the function-references proposal so that's why they're "ignored". When we updated wasmparser we probably should have made it an error if a non-null initializer was indicated.
I think what you'll want to do is to update TableInitialization to store the default initializer and then update try_func_table_init to not use FuncTable if there's a non-null initializer. We can probably lazy-initialize with initializers but that's fine to to in a future PR. It's probably best to get the base set of functionality working first.

Commit 5de9a246fc0c8a0b9ae7a4a60b2ce74cceba86ce implements a fix for the table initialisation problem, though, it is ended up a bit more roundabout than I initially anticipated. If I understand correctly, TableInitialization is global per module, so to avoid penalising pre-function-references code I introduced a new table initialisation strategy EagerFuncTable, which eagerly initialises all table fields. I am not sure whether this aligns with what you had in mind.
As for the final failing test type-equivalence, it fails, seemingly, because the type test for call_indirect is nominal rather than structural (c.f. https://github.com/bytecodealliance/wasmtime/blob/6dc3eb717d7cf9b3539557ea7b393dd51225336d/crates/cranelift/src/func_environ.rs#L1662C1-L1665). Here is a minimal example to reproduce:
(module
  (type $s0 (func (param i32)))
  (type $s1 (func (param i32 (ref $s0))))
  (type $t1 (func (param (ref $s1))))

  (func $s1 (type $s1))
  (table funcref (elem $s1))

  (func (export "run")
    (call_indirect (type $t1) (ref.func $s1) (i32.const 0))
  )
)
(assert_return (invoke "run"))

I am not quite sure what the best course of action is here. I would have expected type/type signature canonicalisation to solve this problem.

which eagerly initialises all table fields. I am not sure whether this aligns with what you had in mind.

Seems reasonable to me! One adjustment I might recommend though is to reuse the existing TableInitialization::Segments initializer. That's the "eager" mode which is optimized, if possible, to TableInitialization::FuncTable which is lazy initialization. During that optimization you can add a check that if anything is not null-initialized then the optimization can be skipped. I think this'll all have the same effect as what you've implemented but avoids EagerTableInitializer and Segments being sort of duplicates of each other.
I'll look more into the call_indirect issue now.

Ok so I can definitely imagine that canonicalization has a bug in it and something isn't working as expected. My guess is that something is hashing a module-local u32 when it actually needs to hash something module-independent, or something like that.
That being said I'm not sure that your reduction showcases the issue? You're invoking, indirectly, a function that takes two parameters with only one parameter. In that sense I think a runtime error is expected there?

which eagerly initialises all table fields. I am not sure whether this aligns with what you had in mind.

Seems reasonable to me! One adjustment I might recommend though is to reuse the existing TableInitialization::Segments initializer. That's the "eager" mode which is optimized, if possible, to TableInitialization::FuncTable which is lazy initialization. During that optimization you can add a check that if anything is not null-initialized then the optimization can be skipped. I think this'll all have the same effect as what you've implemented but avoids EagerTableInitializer and Segments being sort of duplicates of each other.
I'll look more into the call_indirect issue now.

I have attempted to clean this up in the latest commit. Is this closer to what you had in mind?

Ok so I think the issue is in two locations:

Here in the engine-level signature registry, which is a hash map of types across modules registered in an engine.
Here where there's a module-level map of types-to-indexes which should be deduplicating the above types but isn't.

This bug is due to derive(Hash) on WasmFuncType which delegates all the way through to WasmHeapType which hashes the raw index. I think the best solution would be to remove the auto-derived trait impls from WasmType about equality and hashing, and then work backwards from there. The raw WasmHeapType::Index should probably take a SignatureIndex to assist in deduplicating within a module. That should solve the second bullet above.
The first bullet above, however, is much more difficult. That'll need to perform a "deep hash" of the entire structural type since it must be module-independent (and SignatureIndex is module-local). If the second bullet is enough to get tests passing for this PR though then that seems ok to defer to an issue and get this landed instead.
(to clarify, at this point I think it's fine to land this PR so long as it passes CI, it's been long enough and I'm sure y'all are tired of rebasing. It's ok to defer work so long as there's issues on file and the work is gated, which it all is)

No need to worry about conversion into a wasmparser type, that in theory shouldn't happen (or at least not that I know of). For conversion from a wasmparser type it may mean that a From impl needs to be removed in favor of a method on ModuleTypes or something like that where the indexing/hashing context is available.
So thinking more on this, sort of what this wants is WasmType<T> where a Module store WasmType<SignatureIndex> but an Engine stores a WasmType<VMSharedSignatureIndex>. I think then the derive(Hash) should continue to work with PartialEq as well?

I am OK with trying this approach, but it is a sizeable refactoring I think as WasmType<T> implies a type bound on Table, Global, and EntityType (at least). I suppose for each of those the same logic applies: at the module level we want T = SignatureIndex and at the engine level T = VMSharedSignatureIndex (if relevant).
The From trait will need to be removed, or at least supported by an alternative to support conversion from typed references.
Should I give this refactoring a go?

If you're ok with it, I think it's ok to set the test to ignore and land this. It's true that this refactoring will require a bit of finesse, but it's one I'm happy to take on myself rather than having y'all do yet-more work on top of what you've already got here.
Otherwise I'd be happy to merge this with a green CI run (which will require ignoring tests) and a list of items to tackle tracked in an issue (such as fixing the failing tests, this possible refactoring, the embedder API, etc)

@dhil to answer this question (over here for a bit more visibility) my thinking is that at the wasm AST layer there's only "this index" as a type but at the Wasmtime layer we'll be able to be more principled than that by having, for example:
enum WasmHeapType {
    Func,
    Extern,
    TypedFunc(SignatureIndex),
    Array,
    TypedArray(StorageType),
    Struct,
    TypedStruct(StructIndex),
    // ..
}

or something along the lines of that where WasmHeapType stores effectively the discriminant of what it refers to rather than requiring the indexing operation to then verify the type of the result.
One of the things I was worried about was that there was the pervasive assumption that WasmHeapType::Index(_) was a function which won't be true once the GC proposal was implemented. I wanted to head off issues there by having the Wasmtime-level name be called TypedFunc so it's clear that all the cases handling Func and TypedFunc are only there for handling function-related things. In the future when more variants are added it'll require adding more match arms to handle in all these places.

I've opened a issue to track the unresolved bits of this PR. See #6455. I hopefully I managed to cover them all.

Seems like there are some conflicts and this needs a rebase/merge.

Seems like there are some conflicts and this needs a rebase/merge.

I have synchronised with upstream again. Hopefully everything ticks green again :-)

🎊


How to output two file formats, not all (With YAML pipeline)

Is it possible to output only two file types instead of all?

You can configure this using the format option:
steps:
- task: dependency-check.dependencycheck.dependency-check-build-task.dependency-check-build-task@5
  displayName: 'Dependency Check'
  inputs:
    projectName: 'Puma Prey'
    scanPath: '**/*.csproj'
    format: 'HTML,JSON,JUNIT'
    failOnCVSS: 9
    additionalArguments: '--scan "$(Build.SourcesDirectory)\**\packages.config"'

Valid options are:
CSV,HTML,JSON,JUNIT,XML


fix(storage): assert vnode hint existence in state table

Signed-off-by: Bugen Zhao<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
We encode vnode in the mem-table now, so the original implementation of iter_with_prefix only applies to iterating with a superset of the distribution key, which meets the pattern of streaming executors for now.
We should not use unwrap_or to give it a default value, instead, we should assert its existence.
This PR also improves code styles and removes some code duplication.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

e2e fails. 😕 Is the distribution of the local agg state table correct? cc @xxchan @st1page

e2e fails. 😕

Blocked by #5012.

e2e fails. 😕

Blocked by #5012.

fixing...


Remove inline styles

I left tests out of it, and Translations there were some tests failing when I used StyleSheet in translations, saying create is undefined. Probably circular references?

Probably circular references?

Yes.


Component relative path

Need to use relative path...
Get inspiration from http://blog.thoughtram.io/angular/2016/06/08/component-relative-paths-in-angular-2.html

done


have_selector could be more picky with its input

Heya,
I discovered a couple of points in our tests where we weren't testing what we thought we were.  Along the lines of :
  rendered.should have_selector(".banner", :content=>"wooo")

or
  rendered.should have_selector("#header") do |header|
     header.should have_selector("ul.navlinks")
   end

Both of which silently pass - however, capybara doesn't support a :content option (it should be :text), and it doesn't support passing blocks to have_selector (a common mistake from Webrat switchers).
Any thoughts about making capybara warn or even raise an error on unexpected input here?

I had the same problem with :content passing silently. Would be useful to have a warning.

Ditto here. It's worth noting that the rspec docs specifically use the :content option in an example of FactoryGirl/Capybara, implying that it works.

@jnicklas apologies about that. I'm pretty sure RSpec's doco is not the only source of confusion here, but we didn't help matters by posting an incorrect example in the RDoc. The doc error is fixed (thanks to @jwow313), but won't be reflected on rubydoc.info until the next rspec-rails release.

How about this pull request? https://github.com/jnicklas/capybara/pull/602


gazebo collision error

I tried example_cafe.launch.py now with only jackal robot added from ubuntu20.04 foxy.
By the way, when I checked the gazebo collision, it looks like the collision is rotated in the y-axis. I wonder where you set the collision model. Where can i find it?

Hi!
Yes, we were not capable of placing the collision of the human models in the correct place. Anyway we are not using the collision for moving the agents nor avoiding obstacles. We are using the positions of the model to detect and avoid collisions. On the robot side, we rely on the robot sensors to detect and avoid the humans.

Thank you for your response.
From my understanding, humans avoid using positions, and robots detect humans using sensor data, is that correct? Also, I'm concerned about collision models overlapping and potentially causing problems later, so I'd like to turn them off. How can I do that?

Honestly, I do not know.
What I can say is that we had not have problems with the collisions models at any case.


Fix building portable profile directory to be cross platform.

Hi @bholmes, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

The same PR is in #38.  Closing


Broken Link Inbox Feature

At the bottom of the Inbox feature section, there is a broken link for configuring inbox views. Was this feature removed?

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

ID: 873335b6-f72e-ce95-06cb-fde638f22e49
Version Independent ID: 1ec331ff-c458-efd9-fbf7-ce0327d7d83c
Content: Overview of the Customer Service workspace application for Dynamics 365 Customer Service
Content Source: ce/customer-service/csw-overview.md
Service: dynamics-365-customerservice
GitHub Login: @lalexms
Microsoft Alias: laalexan

Thanks for your comment, @mgowing. This issue has been assigned to the doc author for review.

Thank you for letting us know about the broken link, @mgowing. The feature is still available and the link has been fixed.


PMTK3 installation failed

Hi, I just tried to install PMTK3. However, I found this error (see below), how can I solve it? Thanks

initPmtk3
initializing pmtk3
Error using evalin
Undefined function or variable 'destnRoot'.
Error in SetDefaultValue (line 24)
isempty(evalin('caller', argName))
Error in downloadAllSupport (line 7)
SetDefaultValue(1, 'destnRoot', fullfile(pmtk3Root(), 'pmtksupportCopy'));
Error in initPmtk3 (line 51)
downloadAllSupport;

in initPmtk3.mat, line 49:
downloadAllSupport(); ---> downloadAllSupport([],[]);
see https://github.com/probml/pmtk3/issues/97

I just pushed a fix for this
On Thu, Dec 24, 2015 at 1:04 AM, sungyongs<EMAIL_ADDRESS>wrote:

in initPmtk3.mat, line 49:
downloadAllSupport(); ---> downloadAllSupport([],[]);
see #97 https://github.com/probml/pmtk3/issues/97
—
Reply to this email directly or view it on GitHub
https://github.com/probml/pmtk3/issues/104#issuecomment-167072432.


Provide option to not fetch name

This would be much more useful to me if you made it optional to extract the name from the url. Unfortunately the name will not be stable and often times is something wack like Sign in to your Microsoft account. Really for my use case I need a stable enum of which provider this is e.g. outlook, yahoo, gmail

In anycase, great work and totally understand this is an enhancement


why i can't get offset coordinate in endDrag

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
I want to return last coordinate when i end drag, so i can do something with it
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I just want to get last coordinate when i end drag, but return null now.

me too,

The API provided by monitor can not be used.

// You can access the coordinates if you need them
const clientOffset = monitor.getClientOffset();
I'm find api.

@guchengjie yes, great! we can't get the offset in end drag's monitor, we should pass it from drop method  in  drop target ,and get it by monitor.getDropResult().
code like below:
in drop target:
drop(props, monitor){     return {       clientOffset: monitor.getClientOffset(),     }   }
in drag source taregt
endDrag(props, monitor) {     const dropTarget = monitor.getDropResult();     let clientOffset = null;     if(dropTarget){       clientOffset = dropTarget.clientOffset;     }   },

@guchengjie
Thank you! I was looking for that kind of solution


prost-build doesn't namespace types from std library

I have a protobuf message type defined like this:
message String {
    option (a_private_extension_namespace.boxed_message).is_presence_box = true;
    optional string value = 1;
}

The Rust code generated by prost-build looks like this:
#[derive(Clone, PartialEq, Message)]
pub struct String {
    #[prost(string, optional, tag="1")]
    pub value: ::std::option::Option<String>,
}

This makes rustc very unhappy, as you might imagine. Perhaps prost-build should be taught to unconditionally prefix all names from std, like so:
#[derive(Clone, PartialEq, Message)]
pub struct String {
    #[prost(string, optional, tag="1")]
    pub value: ::std::option::Option<std::string::String>,
}

Anticipated questions

Why don't you just rename the protobuf message type to not collide with Rust's builtin types?

These protobuf files are used by code in several different languages (Ruby, TypeScript, etc.); I can't bend these protobuf definitions to the needs of any one language-specific code generator.

What in the name of all that is good and holy is that message for?

It's part of a suite of types to work around some limitations of protobufs, particularly when they interact with the needs of other formats. If you haven't run into this problem, you probably don't want to know. 😅

BTW, I'm happy to make a PR to fix this — just trying to make sure I haven't missed something obvious etc. first, and that the maintainers consider this something they want fixed!


Automated cherry pick of #8525: fix(esxi): no callback in uploadHandler

Cherry pick of #8525 on release/3.4.
#8525: fix(esxi): no callback in uploadHandler

/lgtm

/approve


Fix a compiling issue with Edge on Mac

Proposed changes
To fix the bridging from CFType to NSType
Type of change

[ ] Feature work
[x] Bug fix
[ ] Documentation
[ ] Engineering change
[ ] Test
[ ] Logging/Telemetry

Risk

[ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
[ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
[x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)

Additional information

Will create against to release branch


chore: bump version to v2.2.0

Description of changes:
bump for v2.2.0 which includes the following changes:
Features

Placeholders in TrainingStep to set S3 location for InputDataConfig and OutputDataConfig (#142)
EventBridge service integration (#147)

Fixes

supplying hyperparameters to training step constructor drops hyperparameters specified in estimator (#144)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-sEHrOdk7acJc
Commit ID: 3aebd29be54e20307f33dc7ef8a3f6b48510ef66
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-sEHrOdk7acJc
Commit ID: 3aebd29be54e20307f33dc7ef8a3f6b48510ef66
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


SEARCH FOR STRATEGIES - broken - only returns results from the beginning of a token

Expected behavior
I expect the search will return any strategy with the given search term anywhere in the name. For example, if I search for "api" I would expect to see "Passport-LocalAPIKey" in the results.
Actual behavior
The search seems to start at the begging of the token only ie to have "Passport-LocalAPIKey" appear in the search results you have to search for "local" vs "api"
Steps to reproduce
Search for "api"
Search for "local"
Possiable fix
// const data = http://www.passportjs.org/packages/-/all.json
const keys = Object.keys(data)

const search = (val) => keys.reduce((acc, key)=>{
    if (key.includes(val)) acc[key] = data[key]
    return acc
},{})

let tests = ['a', 'ap', 'api']

const test = (val) => {
    console.time(`Test - search: ${val}`)
    let result = search(val)
    console.timeEnd(`Test - search: ${val}`)
    console.log(`Test - search: ${val}  found: ${Object.keys(result).length}`)
}

tests.forEach(test)

/*
Test - search: a: 0.253ms
Test - search: a  found: 500
Test - search: ap: 0.082ms
Test - search: ap  found: 20
Test - search: api: 0.058ms
Test - search: api  found: 4
 */

// with min length of 2
const search = (val) => {
    if (val.length < 2) return data
    return keys.reduce((acc, key)=>{
        if (key.includes(val)) acc[key] = data[key]
        return acc
    },{})
}
/*
Test - search: a: 0.091ms
Test - search: a  found: 502
Test - search: ap: 0.117ms
Test - search: ap  found: 20
Test - search: api: 0.058ms
Test - search: api  found: 4
*/

With a min length of 2, we eliminate the worse case and have effectively no impact on the search results.
Option
Bloodhound is dead and was massive overkill. There are viable forks of Bloodhound but again imo it's overkill. Maybe if there were a few thousand or tens of thousands of items to search then some sort of more efficient search would be needed.

 I made a more efficient version that is 5-15 times faster for search.length > 2. Might have issues with a large data set.
// const DATA = http://www.passportjs.org/packages/-/all.json
const keys = Object.keys(DATA)

const search = (val, data) => {
    if (val.length < 2) return data
    let _val = val.toLowerCase()
    const keys = Object.keys(data)
    return keys.reduce((acc, key) => {
        if (key.toLowerCase().includes(_val)) acc[key] = data[key]
        return acc
    }, {})
}

const filter = (val, index) => index.filter(k => k.toLowerCase().includes(val.toLowerCase()))
const buildResults = (data, index) => {
    return {data: index.reduce((acc, key) => {
        acc[key] = data[key]
        return acc
    }, {}), index}
}
const search2 = (val, {data, index = Object.keys(data)}) => {
    if (val.length < 2) return {data, index}
    return buildResults(data, filter(val, index))
}

let tests = ['a', 'ap', 'api', 'API']
let tests2 =  ['l', 'lo', 'loc', 'loca', 'local', 'locala', 'localap', 'localapi']

const testSearch = (val) => {
    console.time(`Test - search: ${val}`)
    let result = search(val, DATA)
    console.timeEnd(`Test - search: ${val}`)
    console.log(`Test - search: ${val}  found: ${Object.keys(result).length}`)
    return result
}

const testSearch2 = (val, _data) => {
    console.time(`Test2 - search: ${val}`)
    _data = search2(val, _data)
    console.timeEnd(`Test2 - search: ${val}`)
    console.log(`Test2 - search: ${val}  found: ${Object.keys(_data.data).length}`)
    return _data
}
let _data = undefined

console.log('\n*** testSearch - 1 ')
tests.forEach(testSearch)
console.log('\n*** testSearch2 - 1 ')
_data = {data: JSON.parse(JSON.stringify(DATA))}
tests.forEach((val) => _data = testSearch2(val, _data))

console.log('\n*** testSearch - 2 ')
tests2.forEach(testSearch)
console.log('\n*** testSearch2 - 2 ')
_data = {data: JSON.parse(JSON.stringify(DATA))}
tests2.forEach((val) => _data = testSearch2(val, _data))


App Roles for the App Registration should be documented

I had to dig through the python deployment script in order to understand the app roles that needed to be configured on the app registration.
https://github.com/microsoft/onefuzz/blob/54d49a973e4007b3db2ff0d134d368c648183524/src/deployment/deploy.py#L272-L289
Provide a description of requested docs changes
This should more clearly be delineated in markdown documentation in the event that someone is trying to create the app registration by hand. In most secure enterprises, people do not have standing access to create apps / service principals in Azure AD and there is typically a process for getting one created. In this event, in would be helpful to have this documented to save people time from trying to discern all the things the python deployment script is doing.
@shambho
The deployment script is the only supported way to register the application. We do not support the manual creation.
You are welcome to translate the deployment code to manual steps or wait for the audit of the deployment script.
Originally posted by @chkeita in https://github.com/microsoft/onefuzz/issues/813#issuecomment-827229205
A few lines of documentation on how to set up the app registration is a reasonable ask here.

That is good suggestion. We will add description of the azure entities created by the deployment script in the docs.

docs updated

@chkeita thank you so much!


terraform gke error: system already exists

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

setup rancher2 terraform provider with the following terraform file

provider "rancher2" {
  api_url    = "<omitted>"
  access_key = "<omitted>"
  secret_key = "<omitted>"
}

variable "long_key" {
type = "string"
default = <<EOF
{
  "type": "service_account",
  "project_id": "<omitted>",
  "private_key_id": "<omitted>",
  "private_key": "<omitted>",
  "client_email": "<omitted>",
  "client_id": "<omitted>",
  "auth_uri": "<omitted>",
  "token_uri": "<omitted>",
  "auth_provider_x509_cert_url": "<omitted>",
  "client_x509_cert_url": "<omitted>"
}
EOF
}

resource "rancher2_cluster" "patrick-cluster" {
  name        = "patrick-cluster"
  description = "patrick-cluster"
  kind        = "gke"

  gke_config {
    cluster_ipv4_cidr                 = "<IP_ADDRESS>/19"
    credential                        = "${var.long_key}"

    disk_size_gb                      = 100
    enable_alpha_feature              = false
    enable_http_load_balancing        = true
    enable_horizontal_pod_autoscaling = true
    enable_kubernetes_dashboard       = false
    enable_legacy_abac                = false
    enable_network_policy_config      = false
    enable_stackdriver_logging        = true
    enable_stackdriver_monitoring     = true
    image_type                        = "cos"
    locations                         = []
    machine_type                      = "g1-small"
    maintenance_window                = "23:00"
    master_version                    = "latest"
    network                           = "<omitted>"
    node_count                        = 3
    node_version                      = "1.11.7-gke.4"
    project_id                        = "<omitted>"
    sub_network                       = "<omitted>"
    zone                              = "us-central1-a"
  }
}

Insert values in long_key variable from downloading and pasting your Google Cloud private key json between EOF's.

terraform apply

Result:
Cluster gets created successfully but you are left with the following error on your console.
Error: Error applying plan:

1 error(s) occurred:

* rancher2_cluster.patrick-cluster: 1 error(s) occurred:

* rancher2_cluster.patrick-cluster: Bad response statusCode [409]. Status [409 Conflict]. Body: [baseType=error, code=AlreadyExists, message=clusterregistrationtokens.management.cattle.io "system" already exists] from [https://<omitted>/v3/clusterregistrationtokens]

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.1.6
Installation option (single install/HA): Single

Issue resolved with PR rancher/terraform-provider-rancher2#37

Tested and confirmed fixed.

Is the a way of setting the path to this file ?


bug: Audio Cards don't work in new "Open Web Chat" feature

Describe the bug
When using the new/preview "Open Web Chat" feature, audio cards throw an error as soon as the card is rendered.
Note: This worked fine if I tested directly in Emulator.
Version
1.3.1-nightly.219396.61c994a
Browser

[X] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[X] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Get nightly version of Composer
Open RespondingWithCardsSample
Run the bot
use "Open Web Chat"
Use option 7 for the audio card
Receive error message. The card also will not play the audio

Expected behavior
Card to play the audio.
Screenshots

Some findings:
This works in Emulator when run from source, but does not work in a production build.

We think that this might have something to do with the internal Electron build that we use in the production app of both Emulator and Composer.
The internal build we use might be missing codecs used for certain audio / video playback such as .wav files.

For reference https://microsoft.sharepoint.com/teams/ElectronInMicrosoft/Wiki/Electron-11.2.3.aspx. We currently use the electron version with no FFmpeg codecs. Production support for playing audio files/video files inside Webchat can be supported only if we use a media flavor of the Electron in our build pipelines.