SW-2575 Allow toggling open state of nav hiearchy root

we want to allow opening the hierarchy without selecting a menu item

Why is seeds menu not closing on storybook?

Why is seeds menu not closing on storybook?

Oh, I see. It doesn't have to be selected to allow closing, is that the intended behavior?

Why is seeds menu not closing on storybook?

because it has a selected item - keeping current behavior in staging
we want to open other menus without auto selecting

Why is seeds menu not closing on storybook?

Oh, I see. It doesn't have to be selected to allow closing, is that the intended behavior?

behavior: allow opening a menu hierarchy without selecting a child menu. on mobile especially this is helpful
the requirements didn't say anything about existing menus that have a child menu selected so not changing that behavior - also if we close that user may be confused.
if they want changes we can iterate


Outdated cask: arq

Outdated cask: arq.
Info:

version: 5.1.9.
appcast url: https://www.arqbackup.com/download/arq5.xml.

Sorry, was messing with find_outdated_appcasts and didn't realise it would create untagged issues.

Those scripts are for developers only.

Those scripts are for maintainers only. It does not create untagged issues, it tags them. You just can’t do it because you’re not a maintainer (hence have no permissions).

Yeah that's what I realized when I went through the script. I was looking for a method to find updates for the casks I intend to maintain and now that I understand how it works, this will give me a starting basis. Sorry for the noise.

@colindunn, you should check out @victorpopkov's cask-scripts.

Thanks very much for the pointer @reitermarkus


Monthly trend chart

Show a graph of the variation of the number of star, month by month, like what we do on Rising Stars
From @SachaG

It’d be great to have a trend graph of stars added per week or month for the last year for each project.
The daily trend heatmap is good to see if a specific time period had more activity than usual but I find it hard to visualize trends with it

Example of chart seen on Rising Stars project:

First iteration
The monthly chart has been added to the "Trends" section of the Project details page.
https://next--bestofjs.netlify.com/projects/svelte
Example with Svelte framework:

This feature is included in the release 0.20 https://github.com/bestofjs/bestofjs-webui/releases/tag/0.20.0


Important Section

Hi,
This section...
" Important
If xp_cmdshell is executed within a batch and returns an error, the batch will fail. This is a change of behavior. In earlier versions of MicrosoftSQL Server the batch would continue to execute."
... Should include the version number when this was changed, or else the user has to change the version number on the left nav until they figure out which versions don't behave this way.

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

ID: cae5e224-054d-8787-6b4d-5259a9057f9f
Version Independent ID: 7c782643-2e58-de1b-b430-8f3ea38ec4c1
Content: xp_cmdshell (Transact-SQL) - SQL Server
Content Source: docs/relational-databases/system-stored-procedures/xp-cmdshell-transact-sql.md
Product: sql
Technology: system-objects
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@PrometheusRising1 thanks for bringing this to our attention. This note only applied to very old versions - now well out of support. So, I have removed the note.
You will see the updated version of this article later today.


Invalid IdentityPool Configuration Exception

This question is related to CUP, IDPs and IAM roles.
After creating a new CUP and IDP, proceeded with adding them to IAM Trust policy for the assumed I AM Role. I keep getting this error:
Invalid identity pool configuration. Check assigned IAM roles for this pool
I've explored this problem for hours and my understanding is it has to do with the IAM role Trust policy attached to the execution role for this Identity Pool. Any ideas will be greatly appreciated.

Issue fixed

@Ch3ck May i know how you fixed this issue? I'm running into the same issue now.

@gowreswaran Add the Cognito IDP ID as a resource to your IAM role and add it to the IAM trust policy as well, this error should go away.


Add progress indicator

The upload takes too long since we added image compression. I wouldn't want to fix this now, but please add a progress indicator.

the code right now is a nice one-liner fetch(url, options).then(...) using the fetch polyfill. however, it doesn't expose / let the caller access the XMLHttpRequest object which has a progress event that can be used for this (show an indicator, change cursor etc)
this one line would turn into something like this

@lnogol Then leave it out please. When you're done, let me know so I can look at it, and then we should push to production and test again.


fix(cli): kamel uninstall should delete kamelets #2479

Fix #2479

Release Note
`kamel uninstall` now also cleans up all kamelets defined in the same namespace.

@nicolaferraro @tadayosi wonder if we should  delete all the kamelets or only those that have been installed as part of the operator installation as the user may have installed its own set of kamelets that I guess, should not be deleted as part of the uninstall process

@lburgazzoli FYI this pull req also introduces --skip-kamelets option. Maybe we can activate the option by default or introduce another option --skip-user-kamelets with true by default.

Reconsidering it, now I think it's better for kamel uninstall to keep user-defined kamelets untouched whether or not --skip-kamelets is enabled, rather than erasing them altogether as Luca suggests. Users can manage your own set of kamelets with kamel kamelet subcommands.


Is there any gradle dependency url for integrating in my app?

Hi!
I was looking for a chat library and ended here, it looks really good and I wanted to integrate it in my app.
I have all my external libraries on my gradle dependencies list, and as I haven't seen any link in the docs I was wondering if there's any way to install the library like that.
If not, I suppose I'll have to manually download the repo and use compile project on gradle.
Thanks!

+1


npx crawlee create not working in Mainland China?

Which package is this bug report for? If unsure which one to select, leave blank
No response
Issue description
A user in Discord is dealing with this issue when trying to run npx crawlee create in mainland China.

image link
I suggested it's just some great-firewall magic, but @metalwarrior665 said to create an issue.
Code sample
No response
Package version
latest
Node.js version
16
Operating system
No response
Apify platform

[ ] Tick me if you encountered this issue on the Apify platform

Priority this issue should have
Medium (should be fixed soon)
I have tested this on the next release
No response
Other context
No response

I am not following, what is this about? The screenshot is from a successful run?
Even if this would be true, I dont see anything to fix. If user is not able to fetch data from github, we cant really help with that.

This is the correct image

I mentioned that is we prefetch something like manifest or templates, it would be good to improve the error message and maybe suggest installing directly from npm


Up / Down / My buttons now all have same name

I've noticed that a given accessory's Up / Down / My buttons now all have same name.   This wasn't true before -- I am not sure what changed.  Here's what it now looks like (notice how each accessory has three buttons and there's no way to know which is responsible for up/down/my.

Perhaps this problem arose after updating my home app on my phone (which happened when I upgraded to iOS 16).  The problem also arises when viewing the accessories in the Eve Home app.  The screenshot above is from the Eve home app.

Also note that I can work around this by experimenting with each button to see what it does empirically, and then renaming that button in the Home app with an appropriate name.

Probably linked with changes in iOS 16 / macOS 13 according to my own experience and search results on Internet.
A workaround is to go to the Home App, open the device's settings and click (x) next to the device's name. The original name will appear as a suggestion.


Enhancement: "Continue Chat Branch off at this point / UI Self-Selecting Chat Messages to Use"

What features would you like to see added?
Sometimes it seems that a series of conversations leads the LLM very offshore. It would be nice to be able to go back to a previous point in chat. Effectively, on the API, this just involves not sending N messages. Or, this can be implemented as a checklist where the user un-checkboxes the last context-window sized messages they do not want sent.
More details
Sometimes it seems that a series of conversations leads the LLM very offshore. It would be nice to be able to go back to a previous point in chat. Effectively, on the API, this just involves not sending N messages. Or, this can be implemented as a checklist where the user un-checkboxes the last context-window sized messages they do not want sent.
Which components are impacted by your request?
UI, Endpoints
Pictures
No response
Code of Conduct

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

This is mostly possible already:
https://www.librechat.ai/docs/user_guides/fork


Python: overview assignment TDD

https://open-academy.github.io/machine-learning/assignments/prerequisites/python-programming-introduction.html


[Feature Request] Variable fixup

Insomnia Version: 5.16.6
Operating System: Win10 x64

Details
An issue I've just come across - I've been working on creating a bunch of requests for some software and then found someone's already created a chunk more, albeit in Postman format. I've imported them, but obviously they've used different variable names to me, for example they've used SERVER_NAME but I'm using SERVER_ADDRESS. The problem now is I have to visit each request and replace each undeclared variable they've used with my version!
So what I'd like to see is a way to see a list of all (or at least invalid?) variables/tags in the workspace, with an option to swap them for another across all requests. The current way round this is to export, find & replace on the json and then reimport, but this is a PITA :)

This seems like a fairly rare use-case, but I'd be open to someone submitting a PR for this if someone wanted to take it on. I envision a button in the environment dialog to trigger a prompt to rename a variable. It could provide a list of current variable on the left, with a text-box on the right to enter a new value.
Note: Another idea is to implement a more generic find and replace, which could satisfy more use-cases.


Defined Names doesn't seem to work

Hi guys, not sure if I'm doing something wrong - docs don't seem to cover this

doing this through powershell so I can interact with it easily while I'm playing
GetCellRangesByDefinedName for "AllColumns" "PatternName" or "Readme" returns null
what am I missing? Really need to use the Defined Names to find the correct ranges in my spreadsheet so I can access simply

only basic support of defined names is currently implement, you are welcome to implement more advanced usage


Running the tf_connvis_example1.ipynb ，then having a error

hi ,when i running the example,generating a error ：
OSError: [Errno 22] Invalid argument: './Out/AlexNet\conv1\image_2017-12-22_10:16:21\activations\grid_activation.png'

Hi!
It's simply a Windows vs Ubuntu thing. Thanks for bringing this to our notice. You'll need to change it to .\Output\AlexNet for Windows. We'll make the change to make it generic in the notebook and commit soon.
Thanks!

https://github.com/InFoCusp/tf_cnnvis/commit/6593dbc603be3d268fb77f026e722d7c22adf5d1 #


Swift Legacy Problems

Getting the following error. Was wondering if this happens to anybody else too when using xcode 8 and swift 3.
Is there something that needs to be changed inside of cocoapod file to prevent this from happening? Thanks!
“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly.

Also another problem is... Xcode is confused when I do import AlertOnboarding  and AlertOnboarding when creating the class object. Is there a way to resolve this? Thanks!


MAUI XAML without skiasharp

Just wanted to check:
    <math:MathView x:Name="View" HorizontalOptions="FillAndExpand" VerticalOptions="FillAndExpand">
        \frac\sqrt23
    </math:MathView>

Is there a practical way to use this notation in MAUI ?
Many thanks

You could research the relationship between xaml text and classes to see if it is possible to write dotnet code from the markup language (maui is the best repo do discuss that since it controls this markup language), or could create a library to enable what you want.


Broken link for Custom Errors

Uncommenting the following section in Web.Debug.config and Web.Release.config won't work because there is no GenericError.htm or InternalError.htm files in the template.
<customErrors defaultRedirect="GenericError.htm"
  mode="RemoteOnly" xdt:Transform="Replace">
  <error statusCode="500" redirect="InternalError.htm"/>
</customErrors>

That code is commented out and was there in the default web.release.config and web.debug.config files.
<!--
      In the example below, the "Replace" transform will replace the entire
      <customErrors> section of your Web.config file.
      Note that because there is only one customErrors section under the
      <system.web> node, there is no need to use the "xdt:Locator" attribute.

      <customErrors defaultRedirect="GenericError.htm"
        mode="RemoteOnly" xdt:Transform="Replace">
        <error statusCode="500" redirect="InternalError.htm"/>
      </customErrors>
    -->

Sure, we can close this. I just remembered that we use elmah instead of custom errors.


Pokerus glitch

Hello,
Pokerus glitch caused the Hp, speed, attack of my wailmer to jump and has put it in a state of perma-faint. Trying to use a healing machine does nothing, if it revives on its own it will only have 1 hp and will faint upon attempt of healing.

Pokerus has been disabled per next restart pending a fix


Invenio-PIDStore v0.1.0

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

Basically LGTM. Just one comment:

What's the purpose of recordext in the root?

@lnielsen good catch - it can be removed.


add log trick to roots_jacobi an roots_jacobi_sh

Reference issue
closes #12425: roots_sh_jacobi: Error handling for OverflowError
What does this implement/fix?
add option that allows returning of the log values in orthogonal._gen_roots_and_weights when symmetrize=False
Additional information
needed to imitate statmod::gauss.quad.prob function in R

the tests pass now for log_weights=False

@person142 any new with this pr :)?

Ach let me try to find some time to review... first thought though is that a flag determining whether we return weights or log weights is non-ideal API-wise; generally outputs of functions shouldn't change completely depending on flags. (Admittedly yes the API already does that, but we can no longer correct that because of back compat. Would be nice to not make the situation worse though.)

@person142 would it be better to open a completely new module with 'roots_log_ ...' functions instead?

would it be better to open a completely new module with 'roots_log_ ...' functions instead?

Yes, new functions would be the way to go I think. It would match well with the rest of the API-e.g. loggamma versus gamma, log_ndtr versus ndtr and so on. But before making you put more effort into this, let me read https://github.com/scipy/scipy/issues/12425 more carefully first... might not have time for that until next week though.


Add transition to the search bar

Is your feature request related to a problem? Please describe.
No its not a problem but it looks good when the placeholder in the search doesn't vanish on click.
Describe the solution you'd like
I feel that the main attraction of the page is the title and the search bar of the page so I would like to add some of transitions to the search bar so that the placeholder doesn't vanishes on click and hence improving the UI of the search bar.
Describe alternatives you've considered
Alternatives includes adding some other type of search bars from some frameworks like Bootstrap or Material UI.
Additional context
No response

Thanks a lot @wasimreja Will get into this asap.

@pooranjoyb best of luck!


can cache ColumnNameMap?

can ColumnNameMap cached for same Entity? Do not call  buildColumnNameMap every time.

can ColumnNameMap cached for same Entity? Do not call buildColumnNameMap every time.

Yes, I will write it when I have time, or you can submit pr if you are interested

see this https://github.com/acmestack/gorm-plus/pull/27


Feat: Add github pre-commit hool to prevent eslint warnings

Describe the feature
In current scenario devs are able to commit their changes even if eslint warnings are present.
By adding a pre-commit hook for eslint devs will only be able to commit there changes when all eslint warnings are addressed.
This will enhance code quality and readability of code.
Add ScreenShots
$ git commit

✔ Preparing lint-staged...
❯ Running tasks for staged files...
  ❯ packages/frontend/.lintstagedrc.json — 1 file
    ↓ *.js — no files [SKIPPED]
    ❯ *.{json,md} — 1 file
      ⠹ prettier --write
  ↓ packages/backend/.lintstagedrc.json — 2 files
    ❯ *.js — 2 files
      ⠼ eslint --fix
    ↓ *.{json,md} — no files [SKIPPED]
◼ Applying modifications from tasks...
◼ Cleaning up temporary files...

Record

[X] I agree to follow this project's Code of Conduct
[X] I have starred the repository
[X] I'm a gssoc-24-extd contributor
[X] I want to work on this issue

good idea @lade6501 assigned


Weird bug at last song (require pressing enter to end this) & Good judgement still MFC

https://user-images.githubusercontent.com/105424534/233835688-d6295710-7c08-4efc-bb77-faa5a0cd4c29.mp4
Here's the bug in Video :(

I realize now MFC = GFC but this is not make sense

i uhhh
i'll see what i can do


Can create a channel that use a CA that is not in the certificates store of windows

I would like to create a gRPC client library that it could be used by windows applications (WPF) and MAUI projects (Android), all in .NET 6 and Grpc.Net.
Then I create my library, that has a class that wrap the grpc client. This is the code.
using Grpc.Core;
using Grpc.Net.Client;
using System.Net.Http;
using System.Numerics;
using System.Security.Cryptography.X509Certificates;
using System.Threading.Channels;

namespace GestorOrdenadores.Service.Client.Grpc
{
    public class ServiceClientGrpc
    {
        #region constructores
        public ServiceClientGrpc(string paramDireccion, int paramPuerto, string paramCA, string paramCertificado, string paramKey)
        {
            X509Certificate2 cert = X509Certificate2.CreateFromPem(paramCertificado, paramKey);

            paramDireccion = @"https://<IP_ADDRESS>";
            paramPuerto = 5001;

            //Esto usa un certificado
            HttpClientHandler miHttpHandler = new HttpClientHandler();
            miHttpHandler.ClientCertificates.Add(cert);
            miHttpHandler.ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator;

            HttpClient httpClient = new(miHttpHandler);

            GrpcChannel channel = GrpcChannel.ForAddress(paramDireccion + ":" + paramPuerto, new GrpcChannelOptions
            {
                HttpClient = httpClient
            });

            _client = new Greeter.GreeterClient(channel);
        }
        #endregion constructores

        private readonly Greeter.GreeterClient _client;

        public async Task<string> SayHelloAsync(string paramNombre)
        {
            HelloRequest miRequest = new HelloRequest()
            {
                Name = paramNombre
            };

            return (await _client.SayHelloAsync(miRequest)).Message;
        }
    }
}

The WPF client:
private async void BtnSaludar_Click(object sender, RoutedEventArgs e)
{
    try
    {
        string miStrCertificado = System.IO.File.ReadAllText(@"Certificados\Client.crt");
        string miStrClave = System.IO.File.ReadAllText(@"Certificados\Client.key");
        string miStrCA = System.IO.File.ReadAllText(@"Certificados\ca.crt");

        ServiceClientGrpc miService = new ServiceClientGrpc("https://<IP_ADDRESS>", 5001, miStrCA, miStrCertificado, miStrClave);

        MessageBox.Show(await miService.SayHelloAsync("Álvaro"));
    }
    catch(Exception ex)
    {
        MessageBox.Show(ex.Message);
    }
}

Mi MAUI client:
private async void OnBtnSaludarClicked(object sender, EventArgs e)
{
    try
    {
        //Get address from XML file.
        string miStrDireccion = Configuracion.GestorConfiguracion.GetDireccionServicio();
        int miStrPuerto = Configuracion.GestorConfiguracion.GetPuertoServicio();

        //Get certificates from the asserts
        using Stream miStmCertificado = await FileSystem.OpenAppPackageFileAsync("certificados/client.crt");
        using StreamReader miSrCertificado = new StreamReader(miStmCertificado);
        string miStrCertificado = await miSrCertificado.ReadToEndAsync();

        using Stream miStmKey = await FileSystem.OpenAppPackageFileAsync("certificados/client.key");
        using StreamReader miSrKey = new StreamReader(miStmKey);
        string miStrKey = await miSrKey.ReadToEndAsync();

        using Stream miStmCa = await FileSystem.OpenAppPackageFileAsync("certificados/ca.crt");
        using StreamReader miSrCa = new StreamReader(miStmKey);
        string miStrCa = await miSrKey.ReadToEndAsync();

        ServiceClientGrpc miServicio = new ServiceClientGrpc("<IP_ADDRESS>", miStrPuerto, miStrCa, miStrCertificado, miStrKey);

        EtrRespuestaPing.Text = await miServicio.SayHelloAsync("Álvaro");
    }
    catch(Exception ex)
    {
        await DisplayAlert("Alert", ex.Message, "OK");
    }
}

With this solution I can connect with the WPF application, because in the library I am using DangerousAcceptAnyServerCertificateValidator, but I get an error in the MAUI project because Android doesn't allow a dangerous channel.
If I comment this line, I can connect with the WPF application, because I am using a self-signed certificate and the CA is not in the certificates store of windows. I would like to avoid t o have to install this CA in every windows client.
The problem here is that I don't know how to create a channel with ForAddress() in which I could indicate the CA, because the X509Certificate2 doesn't allow to indicate the CA.
Then I tried to use Grpc.Core instead of Grpc.Net in the library, so the code would be this:
public ServiceClientGrpc(string paramDireccion, int paramPuerto, string paramCA, string paramCertificado, string paramKey)
{
    var keypair = new KeyCertificatePair(paramCertificado, paramKey);
    var sslCreds = new SslCredentials(paramCA, keypair);

    Channel channel = new Channel(paramDireccion, paramPuerto, sslCreds);
    _client = new Greeter.GreeterClient(channel);

    _client = new Greeter.GreeterClient(channel);
}

In this case, I can connect from the windows client without using DangerousAcceptAnyServerCertificateValidator, because with Grpc.Core I can set the CA in the credentials.
The problem with this solution is that the MAUI progect give me this error:
{System.DllNotFoundException: grpc_csharp_ext
   at Grpc.Core.Internal.NativeLogRedirector.Redirect(NativeMethods native) in /var/local/git/grpc/src/csharp/Grpc.Core/Internal/NativeLogRedirector.cs:line 49
   at Grpc.Core.Internal.NativeExtension..ctor() in /var/local/git/grpc/src/csharp/Grpc.Core/Internal/NativeExtension.cs:line 46
   at Grpc.Core.Internal.NativeExtension.Get() in /var/local/git/grpc/src/csharp/Grpc.Core/Internal/NativeExtension.cs:line 67
   at Grpc.Core.Internal.NativeMethods.Get() in /var/local/git/grpc/src/csharp/Grpc.Core/Internal/NativeMethods.cs:line 49
   at Grpc.Core.GrpcEnvironment.GrpcNativeInit() in /var/local/git/grpc/src/csharp/Grpc.Core/GrpcEnvironment.cs:line 373
   at Grpc.Core.GrpcEnvironment..ctor() in /var/local/git/grpc/src/csharp/Grpc.Core/GrpcEnvironment.cs:line 302
   at Grpc.Core.GrpcEnvironment.AddRef() in /var/local/git/grpc/src/csharp/Grpc.Core/GrpcEnvironment.cs:line 78
   at Grpc.Core.Channel..ctor(String target, ChannelCredentials credentials, IEnumerable`1 options) in /var/local/git/grpc/src/csharp/Grpc.Core/Channel.cs:line 70
   at Grpc.Core.Channel..ctor(String host, Int32 port, ChannelCredentials credentials, IEnumerable`1 options) in /var/local/git/grpc/src/csharp/Grpc.Core/Channel.cs:line 107
   at Grpc.Core.Channel..ctor(String host, Int32 port, ChannelCredentials credentials) in /var/local/git/grpc/src/csharp/Grpc.Core/Channel.cs:line 95
   at GestorOrdenadores.Service.Client.Grpc.ServiceClientGrpc..ctor(String paramDireccion, Int32 paramPuerto, String paramCA, String paramCertificado, String paramKey) in D:\desarrollo\proyectos\GestorOrdenadores\GestorOrdenadores.Service.Client.Grpc\ServiceClientGrpc.cs:line 74
   at GestorOrdenadores.Client.Maui.MainPage.OnBtnPingClicked(Object sender, EventArgs e) in D:\desarrollo\proyectos\GestorOrdenadores\GestorOrdenadores.Client.Maui\MainPage.xaml.cs:line 51}

I would like to know if with Grpc.Net it is possible to set the CA in some way to create a channel that use a self-signed certificate that needs a CA that is not stored in the certificates store of windows, so in this way, I could use the same library for different kind of clients.
Perhaps implementing the ServerCertificateCustomValidationCallback with a custom implementation? If this could be the way to go, how could I do it?
Thanks.
EDIT: I have implemented the ServerCertificateCustomValidationCallback, returning always true for testing purposes, and then I can connect from the WPF client, but I can't get from the MAUI client because I get the following error:
{Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: The SSL connection could not be established, see inner exception. AuthenticationException: Authentication failed, see inner exception. SslException: Exception of type 'Interop+AndroidCrypto+SslException' was thrown.", DebugException="System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
 ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception.
 ---> Interop+AndroidCrypto+SslException: Exception of type 'Interop+AndroidCrypto+SslException' was thrown.
   --- End of inner exception stack trace ---
   at System.Net.Security.SslStream.<ForceAuthenticationAsync>d__175`1[[System.Net.Security.AsyncReadWriteAdapter, System.Net.Security, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].MoveNext()
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp2ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.<WaitWithCancellationAsync>d__1[[System.Net.Http.Http2Connection, System.Net.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].MoveNext()
   at System.Net.Http.HttpConnectionPool.GetHttp2ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Grpc.Net.Client.Internal.GrpcCall`2.<RunCall>d__73[[GestorOrdenadores.Service.Client.Grpc.HelloRequest, GestorOrdenadores.Service.Client.Grpc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null],[GestorOrdenadores.Service.Client.Grpc.HelloReply, GestorOrdenadores.Service.Client.Grpc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].MoveNext() in /_/src/Grpc.Net.Client/Internal/GrpcCall.cs:line 493")
   at GestorOrdenadores.Service.Client.Grpc.ServiceClientGrpc.SayHelloAsync(String paramNombre) in D:\desarrollo\proyectos\GestorOrdenadores\GestorOrdenadores.Service.Client.Grpc\ServiceClientGrpc.cs:line 148
   at GestorOrdenadores.Client.Maui.MainPage.OnBtnPingClicked(Object sender, EventArgs e) in D:\desarrollo\proyectos\GestorOrdenadores\GestorOrdenadores.Client.Maui\MainPage.xaml.cs:line 53}

So I would like to know how I could implemented a grpc client that could be used for both, MAUI and WPF clients.

For the parts of your issue relating to Grpc.Net please ask in the grpc-dotnet repository: https://github.com/grpc/grpc-dotnet/issues
As for Grpc.Core with Android MAUI project (Xamarin support):

The Grpc.Core implementation is now in maintenance mode and we're only going to focus on critical and security fixes.
Supporting Xamarin simply presents too much maintenance overhead and it's also difficult to test with the test infrastructure available to us
The Xamarin support has always been classified as "experimental"
See the recent update on gRPC C# for more details.

Note that in practice, running Grpc.Core on Android might still be possible (there is nothing in principle that would prevent it from working), but it will be completely at your own risk and it's simply not one of the use cases the grpc team will help you with as Grpc.Core on Xamarin is now considered as "not supported" by us (but you might still be able to get help from the community).


Removal of explicit_interface_ref_definition deviation

-Removal of explicit_interface_ref_definition deviation from following cases metadata.textproto

TE-3.31
TE-3.3
TE-3.1
TE-14.2
TE-14.1

Pull Request Functional Test Report for #3133 / a71650e704f6b94075bd9cbb52aa7da6f3c597e8
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Cisco 8000E

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Cisco XRd

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Juniper ncPTX

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Nokia SR Linux

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Openconfig Lemming

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Cisco 8808

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Juniper PTX10008

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Nokia 7250 IXR-10e

TE-3.1: Base Hierarchical Route InstallationTE-14.2: encap and decap scaleTE-14.1: gRIBI Scaling

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls


Add DMA support to AES module

Also adds a generic DMA module that can be reused by other peripheral APIs.
This pull request is based on #13. I recommend reviewing and merging that pull request before this one.

I forgot some things:

I have additional commits for testing on the Gnat: https://github.com/braun-embedded/stm32l0xx-hal/compare/aes-dma2...braun-embedded:aes-dma-gnat
cc @lthiery

Rebased, ready for review.


adding random uniform initialization

This PR solves #398. It adds :

random_uniform method to all backends. This provides a way to initiate a tensornetwork with values sampled from a uniform distribution.
tests for random_uniform for all backends

Caution : I added a test to validate the behaviour of the random uniform initialization for all backends but tensorflow. Indeed the seed system in tensorflow (graph/op seed) messed with my brain and I could not consistently init a tensornetwork directly as tf object and via the backend method.
As this test is a bit of an overkill, I'm still pushing as is. If you guys have an idea...

@mganahl Ready for review I believe.

That's ok, the TF random module I believe wasn't designed to be deterministic, so not much you can do.

Nit picks done, should be good to go.


MC: Post creation - change text and size of text in my created markets for preliquidity

Current:

Updated:
Figma

Fixed - closing


Support sending "array" types for binary data

Migrated from https://github.com/google/pywebsocket/issues/131:
What steps will reproduce the problem?
1. Construct an array using array.array()
2. Attempt to send it using request.ws_stream.send_message(message, binary=True)

Expected result:

Binary data is sent.

Actual result:

TypeError: web_socket_transfer_data raised exception for /flow-control-test:
cannot concatenate 'str' and 'array.array' objects

Probably a TypeError would be appropriate if binary=False, but when binary=True
this seems a natural way to send large binary objects.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 10 Jul 2014 at 10:18

Since we've managed without this for a long time, and there's an easy workaround in the array.tobytes() method, this is very low priority.


Latest version is not working with sail enabled

Describe the bug
The latest extension version is not working with Laravel Sail setting enabled. It seems to be ignored.
To Reproduce
Steps to reproduce the behavior:

Install Laravel sail
Install latest version of the extension
Set enableDebugLogs: true
Set runInLaravelSail: true
Run format command
Watch the output log and see that is still using the non sail path

Expected behavior
Using the sail path to run pint.
Environment:

Operating system: Ubuntu 22.04 via Windows with WSL2
IDE / version: VSCode / latest
Extension version: 1.1.4
Extension's config: enableDebugLogs: true, runInLaravelSail: true

Additional context
The version 0.7.3 works as expected.

Thanks for raising the issue!
Will take a look at this

+1 on this issue

@d8vjork have you considered something like this?
docker-compose exec -T laravel.test ./vendor/bin/pint
This executes the command inside the default app container that comes with Sail and logs the output to terminal. Should be executable from the shell context of VSCode and its extensions (works fine for me locally anyway.)

@jseitel Problem with that still the same, need to find out where is that docker-compose (or in case of newer versions, docker compose), could be specified on an extension setting tho

@d8vjork I haven't looked into the details but it was working with v0.7.3 and still is? What changed?

@d8vjork I haven't looked into the details but it was working as expected with v0.7.3 and still is? What changed?

You are actually right... after checking 0.7.x I discovered that I was actually wrapping the execution into a VSCode Task, will try if I could achieve the same on this new refactor I did on v1

Laravel pint vscode, still isn't working with docker/sail, is there any development on this ? Is there any workaround?

Laravel pint vscode, still isn't working with docker/sail, is there any development on this ? Is there any workaround?

use 0.7.3

I encountered a similar issue with the latest version of the Laravel Pint VSCode extension not working correctly in a Laravel Sail setup. After some troubleshooting, I found a solution that worked for me, especially if you're working in a .devcontainer environment.
My Solution:
If you're using a .devcontainer environment, add the following snippet to your devcontainer.json settings and rebuild the container:
"settings": {
    "laravel-pint.executablePath": "vendor/laravel/pint/builds/pint",
    "[php]": {
        "editor.defaultFormatter": "open-southeners.laravel-pint",
        "editor.formatOnSave": true
    }
}

The Problem:
It seems that the default path for Laravel Pint (vendor/bin/pint) has been moved in the latest Laravel Sail installation, likely to vendor/laravel/pint/builds/pint.
Alternative Solution:
If you're not using a .devcontainer environment, you could try changing the executablePath in your workspace or extension config to match the new path.
I hope this helps anyone else encountering the same issue!

Just to report, I have same issue! Waiting for new version, but using version 0.7.3 as commented above

Applying the same mapping that better-pest does seems like a good solution to unblock the Sail integration.
Finding the executable is only half of the puzzle, but file paths need to be mapped as well.
E.g., the following doesn't work:
sail bin pint --config /Users/{HOME}/{PATH_TO_PROJECT}/pint.json /Users/{HOME}/{PATH_TO_PROJECT}/some.php

as the project folder is mapped to /var/www/html inside the container.
Potentially, in case the extension runs in "Sail-mode", it would invoke:
sail bin pint --config /var/www/html/pint.json /var/www/html/some.php


feat: v1 audit by Radically Open Security

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
This Pull Request introduces the v1 release audit performed by Radically Open Security and the changes needed to fix the reported vulnerabilities.

well done guys!


Add a python path field to the Omni UI

Added an 'interpreter' property to the core class.
Added an interpreter validation test.
Added a text field to display and edit the path to python.

I looked into also validating the connection to EnSight on the given port, but did not see a quick and easy way to do so.
There might be an existing 'ping' I can do within pyensight, but I still have to get the return value back to the kit extension.


Sqlite3 doen't install into dory-node android app

Hy.
I'm testing a proget with dory node (app into google play from tempage.io).
I've installed into a Samsung Tab A10.1 with android 7.0 and kernel 3.18.14, the gekko project from git hub.
Then i used:
npm install --only=production
But there was error to install sqlite3.
I tryed to install itmanually with
npm install sqlite3
But i have error
I attach this log
npm-debug (npm bugs sqlite3).log
npm-debug (npm install --build-from-source).log
npm-debug (npm install sqlite3 --loglevel=info).log
Before try to root my Tablet, i would like to know if there is an other solution...
Thanks

I'm trying to find different solution for the problem... I tried also to root my tablet but I had issue also with this procedure because my tablet is unsupported yet.
I read carefully the  wiki but I'm not able to understand how to do it. I'm a very newbie with github and npm so I can't understand some things.
I have a package to clone from github (gekko from askmike);
Before putting into terminal npm install --only=production after the cloning, I have understand that I must:

download the package of sqlite3 (I downloaded the zip file from github: node-sqlite3-master.zip);
then, where should I put the sqlite3 unzipped files? Into what directory of the cloned package (there isn't a node-modules directory after the cloning process... the directory is created after the install process)?
After this, I have to open the file node.gyp but info the cloned directory, there isn't any *.gyp file...
only after the install process a node-pre-gyp file exist and isn't a node-gyp file like the wiki.
So I'm very confused!

Would you be able to try on the latest version v5.0.3? 🙂


feat: map Tiled user properties on tiles and objects to Bevy components

Follow-up of the discussion #5
TODO list:

customize colliders using custom properties observers + provide an example / documentation
check if the associated 'macros" crate will not cause an issue during publication
check if we could regroup our custom tiles / objects observers under a single parent entity + name them
add support for multiple callbacks / multiple observers

You don't need my approval so feel free to merge whenever you're ready.

Sure!
But feel free to give your opinion, it's always nice to get a second look :)
Also, I still want to address a few things in this PR.

I've checked out the branch and had a look at the map file and I'm still not quite sure how the derive macros and related structs line up with the map.
For example in the map (colliders_and_user_properties.tmx) you have two shapes with the class set to ColliderComponent. One of them has DamagePerSecond and the other has is_visible and yet in the code, the ColliderComponent struct has both fields. Would the other field be Default::default() if not set? I'm not sure how it is supposed to work.

Yeah, that's the idea: if a field is not explicitely defined by Tiled, we will use its default value from Rust (hence the need for the struct to implement Default trait).
I'll add a little write-up on this.

I guess my larger point is that I found it a bit confusing and overwhelming. I assume you will add more docs so maybe that will help with the learning curve a bit.
You could look at creating an mdbook and hosting it on Github Pages.

Yeah I agree: it definitely needs more documentation.
Indeed, I would like to do a book and host it on Github, as it is done for bevy_ecs_ldtk. It takes some time though and I prefered to focus on the code first. But it's on my TODO list.
In the meantime, I'll try to add more comments in the example and give more explanation.

These are just random opinions and thoughts so feel free to disregard. Overall I agree that it's a good idea to have some kind of hooks either during or after the loading process.

Thanks!
Again, feel free to give your opinion even if you don't have time anymore to contribute.


Hunted down rebar bugs

Turns out that there were a few nasty bugs inside ddate. This PR fixes those. Instead of writing up the changes here, I will comment on them in the code.
Cheers

So, dyalizer was right after all!


[BUG] user-node-remove finalizer not being properly cleaned up.

Rancher Server Setup

Rancher version: v2.6.6

Describe the bug

If a user upgrades from a version of rancher where the user-node-remove controller still existed, there is a period where the node can be deleted before the finalizer is able to be removed from the node. Since an annotation is used to track whether or not the finalizer needs to be removed, it is thus never removed.
https://github.com/rancher/rancher/blob/a86ad02746c0846fedb8fa7436b1d7e6017a73d6/pkg/controllers/management/node/controller.go#L524-L535
To Reproduce

This is difficult to test, since this is effectively a race condition, although it can be done by manually adding the finalizer clusterscoped.controller.cattle.io/user-node-remove_xxxxx (the five x values do not matter, but the prefix is important), and then deleting the node, like so:
# patch.yaml
metadata:
  finalizers:
  - controller.cattle.io/node-controller
  - clusterscoped.controller.cattle.io/user-node-remove_abcde

kubectl patch --patch-file patch.yaml --type=merge -n <CLUSTER_ID (e.g. c-xxxxx)> node.management.cattle.io <NODE> patch.yaml <NODE> && kubectl delete -n <CLUSTER_ID (e.g. c-xxxxx)> node.management.cattle.io <NODE>

Result
The finalizer stays on the object indefinitely, preventing it from being deleted.
Expected Result

The finalizer is removed and the annotation is ignored because the object is already being deleted.
Screenshots

Additional context

SURE-4806

Test Plan:
W.I.P.

Root cause
In Rancher v2.5.2, the user-node-remove cluster scoped lifecycle was removed and merged with the node controller. In the event that a node is already deleted before the annotation can be applied and the finalizer removed, the node will hang indefinitely.
This can be replicated by creating a node provisioned cluster in v2.5.1, stopping rancher and deleting the v3 node object (verifying that the finalizer is present first), and then starting rancher in v2.6.7.
What was fixed, or what changes have occurred
The finalizer is removed on deletion instead.
Areas or cases that should be tested

The finalizer should no longer prevent the object from being deleted in v2.6-head
Upgrading a rancher install from v2.5.2 -> v2.6-head, the finalizer should still be present on the node until it is deleted, at which point it should be removed.

What areas could experience regressions?
N/A
Are the repro steps accurate/minimal?
:heavy_check_mark:

Syncing w/ @jakefhyde w.r.t. behavior seen in Scenario 1; ticket is being re-opened;
Will continue validation when ticket is back in to-test

Ticket #38442 - Test Results
With Docker on a single-node instance:
Reproduced on v2.5.1 => v2.6.6:

Fresh install of rancher v2.5.1
As admin, provision a downstream AWS Node driver cluster w/  k8s v1.19.15 - [ 1 etcd, 1 cp, 1 wkr ]
Once successfully provisioned, delete worker node + immediately stop rancher + upgrade to v2.6.6
Observe cluster go into Unavailable state on v2.6.6, then come up Active
Reproduced - Node stuck in Removing state; Node scheduled for deletion

Screenshots:
Step 7 - Cluster Management

Step 7 - Cluster Management > Cluster Details > Machine Pools

Verified on rancher v2.5.1 => v2.6.6 => v2.6-400e559407d14ad925caf2f56f5edd8645dbdaba-head:
Scenario 1 - Reproduce in v2.6.6 => Upgrade to v2.6-head + verify node deletion - ❌

Fresh install of rancher v2.5.1
As admin, provision a downstream AWS Node driver cluster w/  k8s v1.19.15 - [ 1 etcd, 1 cp, 1 wkr ]
Once Active, upgrade rancher to v2.6.6; Observe cluster go into Unavailable state, then come up Active
Once Active on v2.6.6, add finalizer to a worker node + delete the node
Reproduced - Node in Removing state w/ message: Node scheduled for deletion
Upgrade rancher to v2.6-head
Veri-FAILED - Node stuck in Removing state w/ message: Node scheduled for deletion; expected node to be removed

Scenario 2 - In v2.6-head - add finalizer to node, then delete it => Ensure node successfully deleted

Fresh install of rancher v2.5.1
As admin, provision a downstream AWS Node driver cluster w/  k8s v1.19.15 - [ 1 etcd, 1 cp, 1 wkr ]
Once Active, upgrade rancher to v2.6-head; Observe cluster go into Unavailable state, then come up Active
Once Active on v2.6-head, add finalizer to a worker node + delete the node
<RESULT_HERE> - <NODE_EXPECTED_TO_BE_SUCCESSFULLY_DELETED>

Scenario 3 - Provision cluster in v2.5.1  => Delete node + immediately stop server + upgrade to v2.6-head => verify node successfully deleted upon upgrade

Fresh install of rancher v2.5.1
As admin, provision a downstream AWS Node driver cluster w/  k8s v1.19.15 - [ 1 etcd, 1 cp, 3 wkr ]
Once successfully provisioned, delete worker node + immediately stop rancher + upgrade to v2.6-head
Observe cluster go into Unavailable state on v2.6-head, then come up Active
<RESULT_HERE> - <NODE_EXPECTED_TO_BE_SUCCESSFULLY_DELETED>

/backport v2.6.9

IN PROGRESS - Ticket #378442 - Test Results [pt. 2]
With Docker on a single-node instance:
Verified on rancher v2.7-609db0ad434be0f0f8d4578bf4eb03502a39be6d-head:

Scenario 1 - ❌

Reproduce in v2.6.6 => Upgrade to v2.6-head + verify node deletion

Scenario 2 - NOT YET STARTED

In v2.6-head - add finalizer to node, then delete it => Ensure node successfully deleted

Scenario 3 - NOT YET STARTED

Provision cluster in v2.5.1 => Delete node + immediately stop server + upgrade to v2.6-head => verify node successfully deleted upon upgrade

Scenario 1 - Reproduce in v2.6.6 => Upgrade to v2.6-head + verify node deletion:

Fresh install of rancher v2.6.6
As admin, provision a downstream RKE1 AWS Node driver cluster w/ k8s v1.19.16 - [ 1 etcd, 1 cp, 1 wkr ]
Once successfully provisioned, add finalizer to wkr node, then delete wkr node
Reproduced - Node in Removing state w/ message: Node scheduled for deletion
Upgrade rancher to v2.7-head
Veri-FAILED - Node stuck in Removing state w/ message: Node scheduled for deletion;

cleanup.cattle.io/user-node-remove: "true" annotation is present;
clusterscoped.controller.cattle.io/user-node-remove_abcde finalizer is present;
expected node to be removed; node still present 1 hour after upgrade to v2.7-head

Screenshots:
Step 3 - Add finalizer

Step 3 - Delete wkr node

Step 4 - YAML of wkr node

Step 4 - Cluster Management

Step 4 - Cluster Details > Machine Pools

Step 6 - Never resolves

Scenario 2 - In v2.6-head - add finalizer to node, then delete it => Ensure node successfully deleted:
1.
Screenshots

Scenario 3 - Provision cluster in v2.5.1 => Delete node + immediately stop server + upgrade to v2.6-head => verify node successfully deleted upon upgrade:
1.
Screenshots

Ticket #38442 - Test Results [cont.]
With HA Helm:
Reproduced on rancher v2.5.1 => v2.6.8:

User-node-remove finalizer not being properly cleaned up - ✅

Verified on rancher v2.7-8a2e68267c882a8adf612a29ae2bf3274a4d8572-head:

Scenario 1 - ❌

Reproduce in v2.6.8 => Upgrade to v2.7-head + verify node deletion

Scenario 2 - NOT YET TESTED

Scenario 3 - NOT YET TESTED

Reproduced on rancher v2.5.1 => v2.6.8:

Fresh install of rancher v2.5.1 - [w/ rke v1.2.0]
Provision a downstream RKE1 AWS Node driver cluster w/ k8s v1.19.15-rancher1-1
Scale down rancher deployment to 0:

kubectl scale deployment rancher -n cattle-system --replicas=0

Add finalizer to worker node:

# patch.yaml
metadata:
  finalizers:
  - controller.cattle.io/node-controller
  - clusterscoped.controller.cattle.io/user-node-remove_abcde

kubectl patch --patch-file patch.yaml --type=merge -n <CLUSTER_ID (e.g. c-xxxxx)> node.management.cattle.io <NODE> patch.yaml <NODE>

Delete worker node:

kubectl delete -n <namespace/cluster_id> node.management.cattle.io <NODE>

Upgrade rancher to v2.6.8 - [post-upgrade, rancher will automatically be scaled back to 3 replica sets]
Reproduced - Node in Unavailable state, reporting: Kubelet stopped posting node status;

cleanup.cattle.io/user-node-remove: "true" annotation is not seen
clusterscoped.controller.cattle.io/user-node-remove_abcde finalizer is present

Scenario 1 - Reproduce in v2.6.8 => Upgrade to v2.7-head + verify node deletion:

Reproduce issue, following reproduction steps outlined above
Upgrade rancher to v2.7-8a2e68267c882a8adf612a29ae2bf3274a4d8572-head
Veri-FAILED:

Cluster in Provisioning state;
Node is removed from wkr pool and seen Not in a pool
Node in Unavailable state w/ message: Kubelet stopped posting node status.
controller.cattle.io/node-controller finalizer present on node
cleanup.cattle.io/user-node-remove: "true" annotation is present on node

A previous fix was merged to remove the clusterscoped.controller.cattle.io/user-node-remove_xxxxx finalizer and allow a machine to be deleted, however this would cause new machines to be created for the downstream node. Since the node came from such an old version of rancher, the v3.Node (machine) and the v1.Node (downstream node) could not be correlated, and since the v3.Node was already deleted, there was no way to correlate them. This was causing an orphaned downstream node, which a machine would then be created for. https://github.com/rancher/rancher/pull/39016 solves this by first checking to see if the node is currently being deleted, and if so, do not attempt to reconcile it.

Root cause
In Rancher v2.5.2, the user-node-remove cluster scoped lifecycle was removed and merged with the node controller. In the event that a node is already deleted before the annotation can be applied and the finalizer removed, the node will hang indefinitely.
This can be replicated by creating a node provisioned cluster in v2.5.1, stopping rancher and deleting the v3 node object (colloquially known as the machine object) in the local cluster, in the c-xxxxx namespace (which is the cluster ID of the cluster the machine belongs to)after first verifying that the finalizer is present, and then starting rancher on v2.6-head.
This is also reproducible by creating a node on v2.6.8, stopping rancher, manually adding the following finalizer: clusterscoped.controller.cattle.io/user-node-remove_abcde, and deleting the associated cleanup annotation: cleanup.cattle.io/user-node-remove by setting it to null and then performing the upgrade to v2.6-head.
What was fixed, or what changes have occurred
The finalizer is removed on sync instead, which should happen on startup, when the node is modified, or after an internal interval (I observer this to be ~5 minutes, but YMMV). The "stuck" node should have the finalizer removed, and be deleted.
A previous fix was merged (on release/v2.7) to remove the clusterscoped.controller.cattle.io/user-node-remove_xxxxx finalizer and allow a machine to be deleted, however this would cause new machines to be created for the downstream node. Since the node came from such an old version of rancher, the v3.Node (machine) and the v1.Node (downstream node) could not be correlated, and since the v3.Node was already deleted, there was no way to correlate them. This was causing an orphaned downstream node, which a machine would then be created for, despite the fact that the machine had a deletionTimestamp, and realistically there is not reason to create a machine for a downstream node that is already being deleted, especially when the infstructure no longer exists (i.e. the hardware from e.g. DO has already been destroyed). https://github.com/rancher/rancher/pull/39016 solved this in release/v2.7 by first checking to see if the node is currently being deleted, and if so, do not attempt to reconcile it.
Areas or cases that should be tested
The finalizer should no longer prevent the object from being deleted in v2.6-head
Upgrading a rancher install from v2.5.2 -> v2.6-head, the finalizer should still be present on the node until it is deleted, at which point it should be removed.
What areas could experience regressions?
N/A
Are the repro steps accurate/minimal?
:heavy_check_mark:

Ticket #38442 - Test Results [cont.]
With HA Helm:
Reproduced on rancher v2.5.1 => v2.6.8:

Reproduction - ✅

User-node-remove finalizer not being properly cleaned up

Verified on rancher v2.7-cadad2e8f1285bcfc136484d4dcbf73c7b5e7bb8-head:

Scenario 1 - ❌

Test: Reproduce in v2.6.8 => Upgrade to v2.7-head + verify node deletion
Result: Local cluster terminated; Worker node not removed

Scenario 2 - ❌

Test: In v2.7-head - add finalizer to node, then delete it => Ensure node successfully deleted
Result: Worker node scheduled for deletion hangs

Scenario 3 - ❌

Test: Provision cluster in v2.5.1 => stop rancher, add finalizer, delete node + upgrade to v2.7-head => verify node successfully deleted upon upgrade
Result:  Local cluster is missing; original issue appears to be resolved

Reproduced on rancher v2.5.1 => v2.6.8:

Fresh install of rancher v2.5.1 - [w/ rke v1.2.0]
Provision a downstream RKE1 AWS Node driver cluster w/ k8s v1.19.15-rancher1-1
Scale down rancher deployment to 0:

kubectl scale deployment rancher -n cattle-system --replicas=0

Add finalizer to worker node:

# patch.yaml
metadata:
  finalizers:
  - controller.cattle.io/node-controller
  - clusterscoped.controller.cattle.io/user-node-remove_abcde

kubectl patch --patch-file patch.yaml --type=merge -n <CLUSTER_ID (e.g. c-xxxxx)> node.management.cattle.io <NODE> patch.yaml <NODE>

Delete worker node:

kubectl delete -n <namespace/cluster_id> node.management.cattle.io <NODE>

Upgrade rancher to v2.6.8 - [post-upgrade, rancher will automatically be scaled back to 3 replica sets]
Reproduced - Node in Unavailable state, reporting: Kubelet stopped posting node status;

cleanup.cattle.io/user-node-remove: "true" annotation is not seen
clusterscoped.controller.cattle.io/user-node-remove_abcde finalizer is present

Scenario 1 - Reproduce in v2.6.8 => Upgrade to v2.7-head + verify node deletion:

Reproduce issue, following reproduction steps outlined above
Veri-FAILED: local cluster terminated
Upgrade rancher to v2.7-cadad2e8f1285bcfc136484d4dcbf73c7b5e7bb8-head
Veri-FAILED:

Cluster in Provisioning state;
Node is removed from wkr pool and seen Not in a pool
Node in Unavailable state w/ message: Kubelet stopped posting node status.
controller.cattle.io/node-controller finalizer present on node
cleanup.cattle.io/user-node-remove: "true" annotation is present on node
local cluster is restored and active

Screenshots:
Step 2 - Issue is reproduced - wkr node YAML

Step 2 - Local cluster terminated

Step 4 - Post-upgrade, "Docker machine exists"

Step 4 - Post-upgrade, cluster w/ node hanging "Not in a pool"

Step 4 - Final result, after some time

Scenario 2 - In v2.7-head - add finalizer to node, then delete it => Ensure node successfully deleted

Fresh install of rancher v2.7-head
Provision a downstream RKE1 AWS Node driver cluster w/ k8s v1.19.16-rancher2-1
Once active, stop rancher server, add finalizer to worker node, delete worker node, then start rancher server
Veri-FAILED: Worker node Scheduled for deletion; new worker node provisions and comes up active, Worker node scheduled for deletion hangs

Screenshots:
Step 4 - Cluster Details > Machine Pools

Step 4 - Worker node stuck YAML

Scenario 3 - Provision cluster in v2.5.1 => stop rancher, add finalizer, delete node + upgrade to v2.7-head => verify node successfully deleted upon upgrade:

Fresh install of rancher v2.5.1 - [w/ rke v1.2.0]
Provision a downstream RKE1 AWS Node driver cluster w/ k8s v1.19.15-rancher1-1
Scale down rancher deployment to 0:

kubectl scale deployment rancher -n cattle-system --replicas=0

Add finalizer to worker node:

# patch.yaml
metadata:
  finalizers:
  - controller.cattle.io/node-controller
  - clusterscoped.controller.cattle.io/user-node-remove_abcde

kubectl patch --patch-file patch.yaml --type=merge -n <CLUSTER_ID (e.g. c-xxxxx)> node.management.cattle.io <NODE> patch.yaml <NODE>

Delete worker node:

kubectl delete -n <namespace/cluster_id> node.management.cattle.io <NODE>

Upgrade rancher to v2.7-head
Veri-FAILED:

Post-upgrade, local cluster is no longer seen
Original issue appears to be resolved, but local cluster is affected by fix

Screenshots:
Step 7 - No local cluster, Post-upgrade

Step 7 - No local namespace

Step 7 - Final result, cluster is Active, local is missing

Root cause
When a node is deleted/deleting while rancher is upgraded from a version < v2.6.7, the cluster.Status.ServiceAccountTokenSecret is not yet populated. There was a bug in the internal logic of acquiring a rest config for a downstream cluster, where this would cause a nil rest config to be returned, with a nil error. The only other case for this was when a cluster either hadn't been provisioned yet, or was already being deleted. This caused the Remove function for a v3.Node object to (incorrectly) exit prematurely, and rancher to (correctly) create an unmanaged machine-prefixed v3.Node object for the orphaned v1.Node.
What was fixed, or what changes have occurred
If the ServiceAccountSecretsMigrated condition is not true for the cluster, return an error. The v1.Node removal in the downstream cluster will be re-attempted until this field is populated.
Areas or cases that should be tested

On v2.5.1, provision a 1 etcd, 1 controlplane, 3 worker cluster
Download a kubeconfig for the local cluster
Download a kubeconfig for the downstream cluster
Using the kubeconfig for the local cluster:

Stop rancher with the following command: kubectl scale deploy -n cattle-system --replicas=0 rancher

Run the following command to delete a worker node: kubectl delete node.management.cattle.io -n <CLUSTER_ID (e.x. c-xxxxx)> <MACHINE_ID (e.x. m-xxxxx)> --wait=false
We use --wait=false, since kubectl delete will wait for finalizers by default

Perform a helm upgrade of rancher to the desired version

Example command: helm upgrade --install rancher rancher-latest/rancher --namespace cattle-system --set hostname=<HOSTNAME> --version v2.7-head

Observe that the v3.Node (machine) object was successfully removed in the local cluster: kubectl get node.management.cattle.io -A

Using the kubeconfig for the downstream cluster:

Observe that the v1.Node object was successfully removed in the downstream cluster: kubectl get node

No machine- objects should be created for the v1.Node in the downstream, since it has been deleted

What areas could experience regressions?

This bug was present on rancher versions < v2.6.7, so machine- objects (which are unmanaged i.e. no infrastructure node.management.cattle.io objects in the local cluster created for v1.Node objects in the downstream, could potentially be created in environments where a downstream is provisioned on v2.6.6, the rancher server is paused, and then upgraded to v2.6.7. There is no way to clean up these objects if this happens, however provisioning on v2.6.6, stopping rancher, and then upgrading to v2.7-headshould no longer create thesemachine-objects, and both thev3.Nodein the local cluster and thev1.Node` in the downstream cluster should be deleted successfully.

Are the repro steps accurate/minimal?
:heavy_check_mark:

Test Plan - Revised
Scenario 1:

Reproduce in v2.6.8 => Upgrade to v2.7-head; verify node successfully deletes

Scenario 2:

Provision cluster in v2.6.6 => stop rancher, delete node + upgrade to v2.7-head; verify node successfully deletes

Scenario 3:

Provision cluster in v2.5.1 => stop rancher, delete node + upgrade to v2.7-head => verify node successfully deletes

Ticket #38442 - Test Results [cont.] - IN PROGRESS
With HA Helm + RKE1 local:
Verified on rancher v2.7-1456576dc70b646e8457024e6d44e9691ed517ba-head:
Summary

Scenario
Test Case
Result

1
Reproduce in v2.6.8 => Upgrade to v2.7-head; verify node successfully deletes
✅

2
Provision cluster in v2.5.1 => stop rancher, delete node + upgrade to v2.7-head => verify node successfully deletes
NOT STARTED

3
Provision cluster in v2.5.1 => stop rancher, delete node + upgrade to v2.7-head => verify node successfully deletes
NOT STARTED

Details
Scenario 1:

Fresh install of rancher v2.5.1
Provision a downstream RKE1 AWS Node driver cluster - [3 nodes, individual roles]
Once Active, download kubeconfig of downstream cluster - [save for later use]
Using kubeconfig of local cluster, stop rancher by scaling deployment to 0:

kubectl scale deployment rancher -n cattle-system --replicas=0

Delete worker node using the following command:

kubectl delete node.management.cattle.io -n <CLUSTER_ID> <MACHINE_ID> --wait=false

Upgrade rancher to v2.6.8
Observe worker node stuck in deletion; Observe new worker node successfully provisions
Once new worker node is Active, upgrade rancher to v2.7-head
Verified - Node successfully deletes; cluster comes up Active
Verified - v3 node object removed from local cluster

kubectl get node.management.cattle.io -A

Verified - v1 node object removed from downstream cluster [verify w/ kubeconfig from step 3]

kubectl get nodes

Scenario 2:
1.

Scenario 3:
1.


refactor: Rename consensus tasks and split storage (BFT-476)

What ❔

Renames FetcherTask to ExternalNodeTask
Moves run_main_node to mn::run_main_node to match en::run_external_node
Splits consensus::storage into consensus::storage::connection and consensus::storage::store

Why ❔
I'm working on https://github.com/matter-labs/zksync-era/pull/2340 where I made these changes either because the naming was confusing or the module was getting very long and I thought it would make it easier to have it in two before adding more trait implementations to it. The PR was getting huge even before I did any actual work, so I decided to make a pure refactoring PR to make the other one easier to review later.
Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[x] Tests for the changes have been added / updated.
[x] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.

Is it expected that the contracts submodule was updated?

@popzxc no, I don't know why it did that. Could it be a side effect of zk init? Sorry, I missed that. It would explain why one of the tests failed with this:
x  Failed to parse config file "/usr/src/zksync/contracts/l1-contracts/script-out/output-deploy-erc20.toml".
|
!    0: TOML parse error at line 5, column 8
|    |
|  5 | mint =<PHONE_NUMBER>24506600000000000.0
|    |        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|  invalid type: floating point `17[408](https://github.com/matter-labs/zksync-era/actions/runs/9744720297/job/26904060256#step:7:409)5318024506600000000000.0`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 32] bytes
|
—  Failed to run command

@aakoshh I think it happened during the merge, e.g. you updated main (which had updated submodule revision) but didn't update it via git submodule update --recursive, and then you committed the (old) revision checked out locally.
@brunoffranca please check the PR for suspicious things; if something doesn't seem to belong to the PR, it's generally better to ask about it.


WIP: helm: fix YAML indentation for helm-job-image

fixes #10

Since the error originates in the dependency https://github.com/rancher/helm-project-operator/ i'll try to fix it there and update the dependency here.

waiting for merge of https://github.com/rancher/helm-project-operator/pull/17

already fixed in #15


ChatOpenAI.with_structured_output(..., , method="json_schema")  does not support pydantic.v1.

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
from dotenv import load_dotenv
from langchain_openai import ChatOpenAI
from pydantic import BaseModel
from pydantic.v1 import BaseModel as BaseModelV1

load_dotenv()

class AddV1(BaseModelV1):
    """add two numbers"""

    a: int
    b: int

class AddV2(BaseModel):
    """add two numbers"""

    a: int
    b: int

model = ChatOpenAI(model="gpt-4o-2024-08-06")
v2_tool = model.with_structured_output(AddV2)  # work
v1_tool = model.with_structured_output(AddV1)  # work
v2_schema = model.with_structured_output(AddV2, method="json_schema")  # work
v1_schema = model.with_structured_output(AddV1, method="json_schema")  # not work

for m in [v2_tool, v1_tool, v2_schema, v1_schema]:
    print(m.invoke("What is 42 + 87?"))

Error Message and Stack Trace (if applicable)
TypeError: Unsupported response_format type - <class '__main__.AddV1'>

Description
function_calling supports pydantic.v1, but json_schema does not support pydantic.v1.
System Info
langchain==0.2.13
langchain-core==0.2.30
langchain-openai==0.1.21
platform==linux
python-version==3.10.12

ah this is a limitation of the openai python sdk, it only accepts pydantic v2 in the new parse method
will think about best way to solve this. may just raise a warning and convert pydantic v1 objects to json schema


fix can't use chinese or somethin else char

After debugging,
When  open(             f"{temp_dir}/{generated_uuid_file}.ps1", "w", encoding="utf-8") writing PS1 files with Chinese or Emoji characters,
it will be garbled
and codecs.open () is written with the original character
ms7m/notify-py#22

Thanks for the PR!
I'll try to format this and merge this into dev branch.


Regenerate Google.Cloud.Talent.V4Beta1

This PR was generated using Autosynth. :rainbow:
Log from Synthtool
{synth_log}

The breaking change here is known and expected. I'll close this PR and send one that regenerates and then fixes up manual code.


Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:fasterxml:jackson-databind:2.13.2:::::::* and cpe:2.3:a:fasterxml:jackson-modules-java8:2.13.2:::::::*)
CVE
CVE-2020-36518
ODC Integration
No response
ODC Version
7.0.1
Description
From https://nvd.nist.gov/vuln/detail/CVE-2020-36518:

jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.

When reporting this CVE for jackson-databind 2.13.2 it seems like a false positive.

Hello, :wave:
This does not looks like a false positive to me. The vulnerability has been acknowledged by the jackson-databind contributors and they are actively working on it. A fix has been integrated in version <IP_ADDRESS>, 2.13.2 is considered to be impacted. Please see https://github.com/FasterXML/jackson-databind/issues/2816.

@nhumblot Aha, thanks for catching this!

Hi all 👋 please note that one more patch, <IP_ADDRESS>, has appeared.


Add TLS Value to mDNS TXT Record

The mDNS responses should include a TLS key/value pair if the connection supports it. This is less necessary for HTTP/WS service records as the server should perform a 301 redirect if TLS is configured. However, for future lower-level transports (e.g. directly over UDP/TCP or a PUB/SUB protocol like NATS or MQTT), it will be useful for the client to know that it should initiate the connection with TLS (or upgrade via a mechanism like STARTLS).

We discussed in Slack adding the version of the TLS supported. That may turn out to be not much value added, unless there is a standard way to represent the current & future versions. Node tlsSocket will report something like version: 'TLSv1/SSLv3'.
However do we really need this? In the APIs and conventions doc we specify that

A Signal K server should advertise its services over mDNS/Bonjour. The server must use the service types - _signalk-http._tcp for http API - _signalk-ws._tcp for WebSocket - _signalk-https._tcp for HTTPS API - _signalk-wss._tcp for secure WebSocket

I think that should be enough, client code needs to have logic to handle the different service types.
If a server has available and advertises standard and secure protocols there should be a way for a client to figure that they are from the same server identity and it should choose which it prefers. For this purpose at least node server includes self identity in the TXT record.

Well, then we just need to fix the bug in signalk-server-node not behaving according to the specification - it always reports only _signalk-ws._tcp / _signalk-http._tcp, regardless of ssl setting....

Definitely!

I have completely missed that part of the specification, BTW.

It will also mean that the client, at least the implementation I'm using in OpenCPN will have to query the DNS twice, but it is certainly doable.

FYI node binding to Bonjour/Avahi implementation is event based: you start to listen to a service type and you receive events as advertisements appear/repeat.

So the solution that is acceptable and correct for you is
diff --git a/lib/interfaces/rest.js b/lib/interfaces/rest.js
index bf02504..d016006 100644
--- a/lib/interfaces/rest.js
+++ b/lib/interfaces/rest.js
@@ -75,7 +75,7 @@ module.exports = function(app) {
     },

     mdns: {
-      name: "_signalk-http",
+      name: app.config.ssl ? "_signalk-http" : "_signalk-https",
       type: "tcp",
       port: app.config.port
     }
diff --git a/lib/interfaces/ws.js b/lib/interfaces/ws.js
index 6ef7f35..5e287b1 100644
--- a/lib/interfaces/ws.js
+++ b/lib/interfaces/ws.js
@@ -26,7 +26,7 @@ module.exports = function(app) {
     primus;

   api.mdns = {
-    name: "_signalk-ws",
+    name: app.config.ssl ? "_signalk-ws" : "_signalk-wss",
     type: "tcp",
     port: app.config.port
   };
diff --git a/lib/mdns.js b/lib/mdns.js
index a0e7c67..a3293ca 100644
--- a/lib/mdns.js
+++ b/lib/mdns.js
@@ -54,7 +54,7 @@ module.exports = function mdns(app) {
   }

   types.push({
-    type: mdns['tcp']('http'),
+    type: app.config.ssl ? mdns['tcp']('http') : mdns['tcp']('https'),
     port: app.config.port
   });

?

Yes.

OK, will update the PR.
BTW, _https.tcp seems not to be recognized by Bonjour Browser, while _http.tcp is. I don't think it matters much, just an observation

Yeah, I think I've seen comments about that.  I think zero conf discovery could be a lot more useful in IoT, seems like a solution finding a problem, but too bad there is no generic browser support.

I believe that's because HTTPS isn't actually a different protocol. It's just HTTP wrapped in TLS. If http were being developed today, IANA and the IETF would insist that HTTPS version use the same port as HTTP and use something like STARTTLS to negotiate encryption.
So, mDNS treats them as the same thing and expects implementors (us) to do what we're doing with including a flag indicating TLS support.
-Tim

On Apr 20, 2016, at 12:25 PM, Pavel Kalian<EMAIL_ADDRESS>wrote:
OK, will update the PR.
BTW, _https.tcp seems not to be recognized by Bonjour Browser, while _http.tcp is. I don't think it matters much, just an observation
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Well, this solution was just refused :) Anyway, I have redone the PR to follow the specification.

I finally found something relevant in the HTTP section of http://dns-sd.org/ServiceTypes.html
It does not look like people take the advice too seriously though- for example Konqueror seems to support _https.tcp according to https://web.archive.org/web/20150922075901/http://www.avahi.org/wiki/AdministrativeAvahiApplication (avahi.org site currently defunct)

Signalk-js-client discovery does not support tls services with the double lookup method yet as nohal pointed out in https://github.com/SignalK/signalk-js-client/commit/907dd20247171d633994136a84d8cd931de0fa43


ng-disabled is working

i need to disable the autocompleter but ng-disabled is not working.
is there any other way to disable the autocompleter?

Hi Kerem,
what exactly is not working when you disable the input field? It still pops up when the user clicks on it? If that is the case please set the manage-externally to true, as then you are not able to click  on it anymore. See https://github.com/guylabs/ion-autocomplete#manage-externally for more details.
If that did not help, can you please elaborate more on this issue with a codepen such that I can right away have a look at it?
Thanks and regards,
Guy

Hey Guy,
I am sorry about my question. Because i found an another bug in my app.
I checked it again: http://codepen.io/anon/pen/meNddo?editors=101
ion-autocomplete is working very well with ng-disabled option :+1:
please ignore my question
Thanks

Hi Karem,
ok nice that it worked. So I will close the issue.
Thanks and regards,
Guy

Hi @guylabs,
I'm currently experiencing the same issue but I have figured out why. I am currently using the plugin on my AngularJS/Ionic Type 1 application.
When doing my development I use ionic serve --lab or ionic serve to debug, etc. When running ionic serve, it runs on the browser but I use the device toolbar under Chrome DevTools to simulate mobile devices. I found that when doing this, even though I have ng-disabled="true" or <input disabled> it still triggers the autocomplete. However, if I remove the mobile simulation and just run it as is on the browser it does not trigger it as it should since the field is disabled.
I have also tried this with ionic serve --lab which also opens/runs on the browser but the application is in it's contained emulator, rather than me forcing it to simulate to a mobile device via Chrome DevTools. In this environment it works as it should and does not open the autocomplete modal.
Finally, I also tried this on my mobile device (Android, S9+) and it doesn't work. It still opens the autocomplete even though the field is disabled. Strange. I was wondering what I was doing wrong when I was inspecting @keremtiryaki's codepen as his browser version is working as it should but mine isn't.
As you've linked there, it seems that I can fix it by using manage-externally but is there any way around this where ng-disabled works in all environments?
Thanks
Allan

Hi @aecvargas
Thanks for the detailed explanations of your issue. I did not work on the autocomplete for a long time now and it looks like there are several new major versions of Ionic and I guess it would be best to check if this also happens on those versions first.
Currently I just know of the manage-externally option to fix this issue. Any other issues with the different browser/dev tools setup I am not familiar with and could as well happen with a default input field from Ionic. (Did you try that once?)
I hope I could help you with that answer.
Thanks and regards
Guy


TCP port 5000 blocked by corporate firewalls

Using TCP/5000 as the default port for flask may be a bad choice. I just had to debug a problem where I wasn't able to reach my service from outside of my network because the firewall (and I assume many firewalls do this) blocks incoming requests on port 5000.
This port is used for universal plug-and-play (UPNP) and it's considered a security problem if it's reachable from the internet says source1 and source2.
I therefore suggest to change the default port or mention this possible problem in the documentation so others don't have to search for this problem as long as I did.

The dev server is only for development, usually on localhost - so no corporate firewall will be between you and the app.
If you use Flask in production you should use a real WSGI server behind a real webserver (running in port 80/443).


feat(pixel):Add my new pixel (33,3)

The pixel value of (33,3) has coloured with attractive color

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Pixel (33,3)has updated with a colour successfully


BUILD-297: Bump Kubernetes to v1.22

/test all

/test e2e-aws

/retest
infrastructure issue
 level=info msg=Creating infrastructure resources...
level=error
level=error msg=Error: Error retrieving Target Group Attributes: TargetGroupNotFound: Target groups 'arn:aws:elasticloadbalancing:us-east-1:460538899914:targetgroup/ci-op-hnblpriv-f242d-6lbct-aext/e60484d43df1dee3' not found
level=error msg=	status code: 400, request id: 009de565-1fd9-4bd4-a38f-900cef790770
level=error
level=error msg=  on ../tmp/openshift-install-cluster-034962729/vpc/master-elb.tf line 71, in resource "aws_lb_target_group" "api_external":
level=error msg=  71: resource "aws_lb_target_group" "api_external" {
level=error
level=error
level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change

/retest
unrelated test failure/flake

/retest
infrastructure issues
level=error
level=error msg=Error: Error retrieving Target Group Attributes: TargetGroupNotFound: Target groups 'arn:aws:elasticloadbalancing:us-east-1:460538899914:targetgroup/ci-op-hnblpriv-f242d-6lbct-aext/e60484d43df1dee3' not found
level=error msg=	status code: 400, request id: 009de565-1fd9-4bd4-a38f-900cef790770
level=error
level=error msg=  on ../tmp/openshift-install-cluster-034962729/vpc/master-elb.tf line 71, in resource "aws_lb_target_group" "api_external":
level=error msg=  71: resource "aws_lb_target_group" "api_external" {
level=error
level=error
level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change

/retest

/retest

/retest

/assign @adambkaplan @gabemontero

/retest

well the most recent e2e-aws-image-ecosystem failure turned up an issue with the recent fix to shorten the connection timeout ... broke the retry mechanism
that fix merged 9 days ago, so it must not be frequent (I saw evidence of networking pain in various logs) but I'll be opening a new BZ for this in a few minutes and have a PR up shortly after
the cgroupsv2 e2e needs my BUILD-278 PR in this repo ... that optional job should be skipped
but I won't issue the skip yet so we can
/test e2e-aws-image-ecosystem
/lgtm

https://github.com/openshift/cluster-samples-operator/pull/386 up for fixing retry on tbr check

the image eco suite failed, but if you look at the results, the actual tests passed, but an error occurred during must gather
/test e2e-aws-image-ecosystem

/test e2e-aws-image-ecosystem

/retest

yeah that cgroupv2 won't pass until BUILD-278 merges @coreydaley
I just wanted to see a clean image eco (that latest failures have been non samples flakes) before officially invoking a skip to clear out the cgroupv2 e2e

ok we have a green image eco
going to
/skip
to clear out the cgroupv2 test .... it will be covered by BUILD-278 which should cover cgroupv2 and k8s v1.22 after this PR merges.

Thanks @gabemontero
Looks like i still need an approval from @adambkaplan

/label docs-approved
No documentation required for this

/label px-approved
No PX materials required for this

/assign @jitendar-singh
I think the CI test for this PR is sufficient. If you agree you can label this "qe-approved" and this can merge.

/retitle Bug 1986003: Rebase to Kubernetes 1.22

/bugzilla refresh

/bugzilla refresh

/qe-approved


Missing requirements?

On running python setup.py install the following appear to be missing:
IPython
jupyter_client

Well I figure I depend upon the notebook server and you're not supposed to put sub dependencies within the setup.py. I don't directly depend upon IPython or jupyter_client. jupyter_client comes through depending on notebook:
https://github.com/jupyter/notebook/blob/master/setup.py#L79-L91
And IPython comes through ipykernel which notebook depends upon:
https://github.com/ipython/ipykernel/blob/master/setup.py#L83-L88
So, strictly I should not need to, nor should I be putting those dependencies within my own setup.py.

It is odd that those dependencies were missing.

Is it okay to close this issue now?


Equivalent continuous query not working on v0.11.0 but working on  0.10.3, CQ on v0.11 appears to be broken

Hi, I have the same query on two different versions, and the query should be supported by both versions.
This works on v0.10.3:
when I do SHOW CONTINUOUS QUERIES... on both versions i get:
name: testdb
name            query
down_sample     CREATE CONTINUOUS QUERY down_sample ON testdb BEGIN SELECT mean(value) INTO "testdb_down"."default".:MEASUREMENT FROM "testdb"."default"./testsim*/ GROUP BY time(1m) END
But the very same query on v0.11 (stable) does not work.
No CQ query that I can form works for with v0.11.
By "not working" i mean the CQ on v0.11 is NOT running, although it appears in SHOW CONTINUOUS QUERIES

the same issue to #6096

@ianlutzeigen please upgrade to 1.1 and let us know if there is an issue.


[msid] [content freshness]Make docs PR demo #12345

Minor doc update on authorization article
@OwenRichards1

@Dickson-Mwendia : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#assign-reviewer @OwenRichards1

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @rwike77

#hold-off

@rwike77
Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thank you @Jak-MS for checking this.  I should have left the PR as draft since I was doing a demo on "how to contribute". No need to review as I will be closing it.
Cc: @rwike77


Retry Seed Download

Related to #23326

/azp python - core - ci

/azp run python - core - ci

This failure is due to an eng/sync-common PR merging. Analyze failing is not related to this PR. Overriding and merging.

/check-enforcer override


[various] mostly tradehistory improvements

Also addresses https://github.com/knowm/XChange/issues/2558


Add iui-* prefix to all component names

In the Vue world, this is a good practice that would prevent component name clashes. For example, if a person installs the library from the CDN and connects it as a plugin, the <Button> would be mis-interpreted. And since no default HTML tag has two words in the name, iui-* prefix is perfect.

Respectively, it is better to change names in all the exports and imports

Implemented in #28


Practitioner identifiers

Practioner ID Slices

Practitioner.identifier:Terhikki

Ok. We store this ID in Apotti and can support this today.

Practitioner.identifier:SSN

Is this just HETU?

Practitioner.identifier:SV

Can you give more info on this identifier? I want to make sure we support this today in Apotti's system

Actually there is a minor issue regarding SSN abbreviation. That refers to "Social Security Number" which is not the correct definition for HETU. PIC (like in Patient profile) should be used in here and it stands for "Personal Identifier Code". https://dvv.fi/en/personal-identity-code
We have already acknowledged this error and decided to fix it soon.
Here you can find a definition for SV-number. Unfortunately the page is in Finnish but the identifier is explained under Yksilöintitunnus heading.
https://www.valvira.fi/valvira/rekisterit/terveydenhuollon_ammattihenkilot

Ah yes - we call this SV number the "Valvira ID" in Apotti. All 3 identifiers are stored and supported by Apotti then.
Yeah SSN is a very US concept, broadly meaning "national identifier".

Nothing else to track here once you address the "SSN" thing you mentioned.


feat: create launcher for core services

Description
Provide a launching mechanism for Core Services. Should work both on Windows and Linux
Issue linked
Closes #1578
Checklist

[x] I have tested my changes locally.
[ ] I have added necessary documentation or updated existing documentation.
[x] I have followed the coding style guidelines of this project.
[ ] I have added appropriate unit tests.
[x] I have reviewed my changes before submitting this pull request.
[x] I have linked the issue or issues that are solved to the PR if any.
[x] I have assigned this PR to myself.
[x] I have added the minimum version decorator to any new backend method implemented.
[x] I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

IMPORTANT NOTE - when using ansys-tools-path on Linux, it is important that the Geometry Core Service is located in one of the following directories:

/usr/ansys_inc/vXXX/CoreGeometryService
/install/ansys_inc/vXXX/CoreGeometryService
/ansys_inc/vXXX/CoreGeometryService

Feel free to use symbolic links to try this out.

Let's merge this one as is. Testing for launching local products is not in yet anyway (our VMs rely on Docker). We can come back to fix things.


*: fix web UI build failure

Signed-off-by: hundundm<EMAIL_ADDRESS>
What problem does this PR solve?
fix web UI build failure
PD_WEB=1 make

What is changed and how it works?
fix bugs in scripts and add compilation tags.
Check List

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

Codecov Report

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

@@            Coverage Diff             @@
##           master    #2047      +/-   ##
==========================================
- Coverage   76.79%   76.72%   -0.07%
==========================================
  Files         184      184
  Lines       18631    18631
==========================================
- Hits        14307    14294      -13
- Misses       3234     3241       +7
- Partials     1090     1096       +6

Impacted Files
Coverage Δ

server/kv/etcd_kv.go
75.32% <0%> (-6.5%)
:arrow_down:

server/schedule/placement/rule.go
87.87% <0%> (-6.07%)
:arrow_down:

pkg/etcdutil/etcdutil.go
82.6% <0%> (-5.8%)
:arrow_down:

server/tso/tso.go
77.37% <0%> (-3.65%)
:arrow_down:

server/schedulers/random_merge.go
60.71% <0%> (-3.58%)
:arrow_down:

server/member/leader.go
75.51% <0%> (-3.07%)
:arrow_down:

server/grpc_service.go
57.23% <0%> (-1.73%)
:arrow_down:

client/client.go
72.23% <0%> (-1.21%)
:arrow_down:

server/server.go
83.04% <0%> (+0.38%)
:arrow_up:

pkg/btree/btree.go
87.65% <0%> (+0.8%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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

@winkyao Please approve.

PTAL @nolouch @disksing @winkyao

/merge


Option to auto-remove/clean formData properties not found in Schema?

Prerequisites

[x] I have read the documentation;
[x] In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.
[x] Ideally, I'm providing a sample JSFiddle or a shared playground link demonstrating the issue.

Description
We currently use rjsf to enable users to load a Schema and a formData file for each of our electronics device firmwares. When we release new firmwares, we'd like the users to be able to load a new Schema - and their old formData (in order to quickly update their formData to the structure of the new Schema).
This works for the most part. However, if an update removes a property in the Schema, which was still present in the formData, this property is not removed upon submitting the updated formData using the new Schema and the old config.
We can partially "solve" this by enforcing requirements on additionalProperties and minimum properties - but then the user is unable to directly edit their old formData in the editor as the validation will block the submission due to "outdated" fields still present in his formData. To fix it, the user has to manually remove the redundant fields to get past the validation issues.
Ideally, instead, the form could have an option to clean the formData of any properties that are not part of the Schema file. This would work similar to setting additionalPropertes: false and minProperties: X - but with the advantage that the form is able to process the removal of redundant properties on behalf of the user, minimizing errors.
Steps to Reproduce
I've added  a playground link to illustrate the issue. In this, the formData input contains firstName, yet this property is not part of the Schema. Regardless, firstName is still included in the submitted formData - here we'd ideally want to have it excluded.
Playground link
Expected behavior
Property fields in the loaded formData that are not part of the Schema should be removed from the submitted formData.
Actual behavior
The property fields remain included in the submitted formData
Version
Release 1.6.1

See #1283


Add missing RLMRealm#addOrUpdateObjectsFromArray: test

Add a test for RLMRealm#addOrUpdateObjectsFromArray:.
RLMRealm#addOrUpdateObjectsFromArray: methods are not covered by the unit tests.
Could you please review? @jpsim @segiddins

:+1:

:+1:


Chapter 2 - Feature_importances versus the pipeline

When making a select and predict pipeline, the feature importance's are supposedly calculated beforehand.
But how can it do so considering we create new features from scratch in the pipeline itself?
Or is the feature_importances var updated after the creation of said new features?
prepare_select_and_predict_pipeline = Pipeline([
('preparation', full_pipeline),
('feature_selection', TopFeatureSelector(feature_importances, k)),
('svm_reg', SVR(**rnd_search.best_params_))
])

Thanks for your question. Indeed, in this example we assume that the feature importances were computed ahead of time: in other words, we ran the preparation pipeline once already, we ran some analysis and we figured out which features were most important. Then the purpose of this new pipeline is to add the feature selection step which keeps only the top k features. Since we don't know what the best value of k is, this new pipeline could be used to try different values of k and find which one gives the best results on the validation set.
It would probably be better to compute the feature importances as part of the pipeline itself (between the preparation step and the feature selection step).
Hope this helps.

Hi Mr Ageron,
Yes this answers my question completely.
Thank you for making this book, the exhaustive exercises+solutions and githubguidance.
It is of a tremendous help!