Allow for configuration of LDAP referral following

These changes allow for the configuration of the LDAP referral response behavior. Behavior can be set by modifying the plugins.security.FOLLOW_REFERRALS field of the opensearch.yml file. By default, referrals are followed in exactly the same way as previous releases.

Resolves #195

Testing
Integration testing was manually conducted as further details on reproducing the undesired behavior would be necessary for unit tests or function tests. The changes were tested by following the developer guide for manual set up and integration of the security plugin with the new setting configured to both true and false. Because the developer guide's predicted results were met in both cases, it was determined that the configuration change was at least integrated into the code base properly.
Further suggestions for testing would be welcome.
Check List

[ ] ~New functionality includes testing~ (See above)
[X] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This is kind of cool, I don't see any changes in this pull request.  Unforunately, I think this means that the updates you wanted to make aren't here in a way that can be reviewed, please try pushing your changes to scrawfor99:main and they will automatically appear in this pull request.


Improve the Windows OneCore target support

Add New Targets

VC-WIN32-UWP
VC-WIN64A-UWP
VC-WIN32-ARM-UWP
VC-WIN64-ARM-UWP

How to compile OpenSSL libraries for an Universal Windows Platform (UWP) App

perl Configure --release no-asm no-hw no-dso no-tests no-stdio no-async VC-WIN64A-UWP
nmake build_libs

It is my first time to make a pull request to OpenSSL. So I need some help.
Thanks.
Mouri_Naruto

https://github.com/openssl/openssl/issues/4853
https://github.com/openssl/openssl/issues/4156

@dot-asm I need your help.

@dot-asm I need your help.

This is misdirected question, address the project.

@dot-asm I have renamed the pull request.

@dot-asm  I have renamed the name of pull request because you say it is a misdirected question. Or I created a wrong pull request? How to do in the next?

What @dot-asm means it that he doesn't want to be addressed directly, that you should address the project, i.e. @openssl.
I've decided to take this on, but then I need your help to understand what you're trying to achieve.  I have no idea what WindowsApp.lib, and trying to search for it gets me to pages talking about OneCore libs...  It would be great if the comments, either in commit messages or in the conf file you've added to, expanded a bit on what's going on, and what that covers that isn't already covered by the current onecore targets we already have.

@levitte Thanks, I want to say sorry to @dot-asm after I read your reply. (I don't know what he said before because I am not good at English. I am really sorry. 😓)

what you're trying to achieve

I want to make the OpenSSL can build the static and dynamic libraries which the UWP store app can use it. In OpenSSL 1.0.2 era, I commit the similar thing to Microsoft's OpenSSL repo before. But when I found many people have done something in the offical OpenSSL repo, I want to add them to the offical instead of the Microsoft's because it can help more UWP app developers.

what WindowsApp.lib
The WindowsApp.lib is the contains all Win32 APIs which the UWP app can use. If you want to build an UWP app which can upload to the Microsoft Store, you only can link to this lib and the ucrt.

Based on the Microsoft's branch, I only add some configurations to Configurations/50-win-onecore.conf and ms/uwp_applink.h.
I add the ms/uwp_applink.h because we can't use GetModuleHandle API in the store app, I use the macro to hack it like the Microsoft's way.
The Microsoft's way is:
https://github.com/Microsoft/openssl/blob/a033d72bdb8cc465594a8061eea369cacc6b7027/ms/winrt.cpp#L153
https://github.com/Microsoft/openssl/blob/a033d72bdb8cc465594a8061eea369cacc6b7027/ms/winrtdef.h#L49
More questions are welcome. Thank for everyone.
Mouri

The WindowsApp.lib is the contains all Win32 APIs which the UWP store app can use. If you want to build an UWP app which can upload to the Microsoft Store, you only can use the Win32 APIs defined in this lib.

But...  OneCore.lib is an umbrella library as well, and the already existing config targets already do link with that without issue last time I looked (I'm perfectly willing to check again).  So I would like to know what WindowsApp.lib provides that OneCore.lib does not.
Mind you, I do understand that other apps that link with OpenSSL libraries may need WindowsApp.lib for purposes that OpenSSL itself doesn't, and I do understand that other apps may need the /APPCONTAINER flag.  But does the openssl app need it?  And most of all, do the OpenSSL DLLs need it?  I can understand a desire to run openssl on devices other than the desktop...
I hope I'm not babbling helplessly.  OneCore and UWP are new to me, and I'm trying to learn as I go.

@openssl Any news?

@levitte Any news?

Sorry, been distracted by other stuff...  I'll run some tests now

So I got quite a bit, but here's a showstopper I can't figure out:
        link /nologo /debug /dll /NODEFAULTLIB:kernel32.lib /APPCONTAINER /nologo /debug  /implib:libcrypto.lib /out:libcrypto-1_1-x64.dll /def:libcrypto.def @C:\Users\Richard\AppData\Local\Temp\nm90E.tmp || (DEL /Q libcrypto-1_1-x64.* libcrypto.lib && EXIT 1)
   Creating library libcrypto.lib and object libcrypto.exp
MSVCRT.lib(gs_report.obj) : error LNK2019: unresolved external symbol __imp_RtlCaptureContext referenced in function capture_current_context
MSVCRT.lib(utility_desktop.obj) : error LNK2001: unresolved external symbol __imp_RtlCaptureContext
MSVCRT.lib(gs_report.obj) : error LNK2019: unresolved external symbol __imp_RtlVirtualUnwind referenced in function capture_current_context
MSVCRT.lib(utility_desktop.obj) : error LNK2001: unresolved external symbol __imp_RtlVirtualUnwind
MSVCRT.lib(gs_report.obj) : error LNK2019: unresolved external symbol __imp_UnhandledExceptionFilter referenced in function __raise_securityfailure
MSVCRT.lib(utility_desktop.obj) : error LNK2001: unresolved external symbol __imp_UnhandledExceptionFilter
MSVCRT.lib(utility_desktop.obj) : error LNK2019: unresolved external symbol __imp_GetStartupInfoW referenced in function __scrt_get_show_window_mode
MSVCRT.lib(utility_desktop.obj) : error LNK2019: unresolved external symbol __imp_GetModuleHandleW referenced in function __scrt_is_managed_app
libcrypto-1_1-x64.dll : fatal error LNK1120: 5 unresolved externals
NMAKE : fatal error U1077: 'link' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'
Stop.

BTW, I did a few changes in addition to your stuff:
diff --git a/Configurations/10-main.conf b/Configurations/10-main.conf
index 5cf345da0..e98ea6f92 100644
--- a/Configurations/10-main.conf
+++ b/Configurations/10-main.conf
@@ -1290,7 +1290,7 @@ my %targets = (
     },
     "VC-WIN64I" => {
         inherit_from     => [ "VC-WIN64-common", asm("ia64_asm"),
-                              sub { $disabled{shared} ? () : "ia64_uplink" } ],+                              sub { $disabled{uplink} ? () : "ia64_uplink" } ],         AS               => "ias",
         ASFLAGS          => "-d debug",
         asoutflag        => "-o ",
@@ -1302,7 +1302,7 @@ my %targets = (
     },
     "VC-WIN64A" => {
         inherit_from     => [ "VC-WIN64-common", asm("x86_64_asm"),
-                              sub { $disabled{shared} ? () : "x86_64_uplink" } ],
+                              sub { $disabled{uplink} ? () : "x86_64_uplink" } ],
         AS               => sub { vc_win64a_info()->{AS} },
         ASFLAGS          => sub { vc_win64a_info()->{ASFLAGS} },
         asoutflag        => sub { vc_win64a_info()->{asoutflag} },
@@ -1315,7 +1315,7 @@ my %targets = (
     },
     "VC-WIN32" => {
         inherit_from     => [ "VC-noCE-common", asm("x86_asm"),
-                              sub { $disabled{shared} ? () : "uplink_common" } ],
+                              sub { $disabled{uplink} ? () : "uplink_common" } ],
         CFLAGS           => add("/WX"),
         AS               => sub { vc_win32_info()->{AS} },
         ASFLAGS          => sub { vc_win32_info()->{ASFLAGS} },
@@ -1378,7 +1378,7 @@ my %targets = (
 #### MinGW
     "mingw" => {
         inherit_from     => [ "BASE_unix", asm("x86_asm"),
-                              sub { $disabled{shared} ? () : "x86_uplink" } ],
+                              sub { $disabled{uplink} ? () : "x86_uplink" } ],
         CC               => "gcc",
         CFLAGS           => picker(default => "-Wall",
                                    debug   => "-g -O0",
diff --git a/Configurations/50-win-onecore.conf b/Configurations/50-win-onecore.conf
index b6291a558..606be55db 100644
--- a/Configurations/50-win-onecore.conf
+++ b/Configurations/50-win-onecore.conf
@@ -71,6 +71,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
      "VC-WIN64A-UWP" => {
@@ -80,6 +81,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
     "VC-WIN32-ARM-UWP" => {
@@ -89,6 +91,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
      "VC-WIN64-ARM-UWP" => {
@@ -98,6 +101,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
 );
d+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
      "VC-WIN64A-UWP" => {
@@ -80,6 +81,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
     "VC-WIN32-ARM-UWP" => {
@@ -89,6 +91,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
      "VC-WIN64-ARM-UWP" => {
@@ -98,6 +101,7 @@ my %targets = (
         lflags          => add("/APPCONTAINER"),
         defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
                                "_WIN32_WINNT=0x0A00"),
+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
         ex_libs         => "WindowsApp.lib",
     },
 );
diff --git a/Configure b/Configure
index d5dc36c28..f9cf4f524 100755
--- a/Configure
+++ b/Configure
@@ -409,6 +409,7 @@ my @disablables = (
     "ubsan",
     "ui-console",
     "unit-test",
+    "uplink",
     "whirlpool",
     "weak-ssl-ciphers",
     "zlib",
@@ -482,7 +483,7 @@ my @disable_cascades = (

     # Without position independent code, there can be no shared libraries or DSOs
     "pic"               => [ "shared" ],
-    "shared"            => [ "dynamic-engine" ],
+    "shared"            => [ "dynamic-engine", "uplink" ],
     "engine"            => [ "afalgeng", "devcryptoeng" ],

     # no-autoalginit is only useful when building non-shared

With that change, I configured like this:
perl Configure VC-WIN64A-UWP no-asm no-uplink

I'm not sure no-hw is necessary
uplink implements the library side of what's described in https://www.openssl.org/docs/manmaster/man3/OPENSSL_Applink.html
If you look at my patch above, you'll notice that I added "uplink" among things the can be disabled.  That's how I avoid the macro hack.
The toolchain can handle it, but it seems that some assembler modules depend on stuff that isn't available with WindowsApp.lib, so it seems they need to be turned off, at least until we figure out how they can be used.

Note btw that I'm on vacation starting tomorrow and will be away for two weeks.  In all likelyhood, this won't be done today, so we will just have to continue after I get back

@levitte Got it. Have a nice vocation!

I'm not sure no-hw is necessary

It may be necessary.
I read the "https://wiki.openssl.org/index.php/Compilation_and_Installation" and have found "no-hw | Disables hardware support (useful on mobile devices)". You may know the developer can make their UWP apps running on the mobile phones. And I also read the compile scripts in the Microsoft's OpenSSL branch and I found they have used the "no-hw" options. (https://github.com/Microsoft/openssl/blob/a033d72bdb8cc465594a8061eea369cacc6b7027/ms/do_vsprojects15.bat#L53)
Mouri

Adding no-hw to my configuration line changes nothing at all

@levitte How's it going?

no-hw isn't really of much value today, and terribly misunderstood...  it was originally conceived to disable building of any ENGINE module that supported HSMs (the first ENGINE module was to support the nCipher device, which needs support files, such as nCipher specific header files, libraries, ...).  Now that there are a number of ENGINE modules that are not about supporting specific hardware, no-hw has become a bit of an oddity.

Could it be that with no-hw, you really want to disable all ENGINE module building (as well as the ENGINE API)?  In that case, no-engine would make more sense, wouldn't you think?

@levitte Yes, I don't want to disable all ENGINE modules. But can this project compile successfully without this option? I don‘t know.
In short, it will be fine if it compiles successfully.
Finally, I would like to know if OpenSSL will determine the hardware instruction support at run time.
Thank you.
Mouri

Finally, I would like to know if OpenSSL will determine the hardware instruction support at run time.

Yup, and that's completely unrelated to no-hw, I might add.  There's the internal function OPENSSL_cpuid_setup that deals with that kind of thing.

@levitte Got it. It's your turn to do now. (Thank you very much.)
Mouri.

I forgot to ask, which thing I should do next? Thanks.
@levitte

Any news?

I close the PR because it is not responding. If someone want to merge them, tell me to reopen. Thanks.

I reopen the PR because I still want to make this PR to be merged.
But the process of OpenSSL Team is too slow to wait. (sad)
Mouri

BTW, I did a few changes in addition to your stuff:
diff --git a/Configurations/10-main.conf b/Configurations/10-main.conf
index 5cf345da0..e98ea6f92 100644
--- a/Configurations/10-main.conf
+++ b/Configurations/10-main.conf
@@ -1290,7 +1290,7 @@ my %targets = (
},
"VC-WIN64I" => {
inherit_from     => [ "VC-WIN64-common", asm("ia64_asm"),

                         sub { $disabled{shared} ? () : "ia64_uplink" } ],+                              sub { $disabled{uplink} ? () : "ia64_uplink" } ],         AS               => "ias",
   ASFLAGS          => "-d debug",
   asoutflag        => "-o ",

@@ -1302,7 +1302,7 @@ my %targets = (
},
"VC-WIN64A" => {
inherit_from     => [ "VC-WIN64-common", asm("x86_64_asm"),

                         sub { $disabled{shared} ? () : "x86_64_uplink" } ],

                         sub { $disabled{uplink} ? () : "x86_64_uplink" } ],
   AS               => sub { vc_win64a_info()->{AS} },
   ASFLAGS          => sub { vc_win64a_info()->{ASFLAGS} },
   asoutflag        => sub { vc_win64a_info()->{asoutflag} },

@@ -1315,7 +1315,7 @@ my %targets = (
},
"VC-WIN32" => {
inherit_from     => [ "VC-noCE-common", asm("x86_asm"),

                         sub { $disabled{shared} ? () : "uplink_common" } ],

                         sub { $disabled{uplink} ? () : "uplink_common" } ],
   CFLAGS           => add("/WX"),
   AS               => sub { vc_win32_info()->{AS} },
   ASFLAGS          => sub { vc_win32_info()->{ASFLAGS} },

@@ -1378,7 +1378,7 @@ my %targets = (
MinGW
 "mingw" => {
     inherit_from     => [ "BASE_unix", asm("x86_asm"),

                         sub { $disabled{shared} ? () : "x86_uplink" } ],

                         sub { $disabled{uplink} ? () : "x86_uplink" } ],
   CC               => "gcc",
   CFLAGS           => picker(default => "-Wall",
                              debug   => "-g -O0",

diff --git a/Configurations/50-win-onecore.conf b/Configurations/50-win-onecore.conf
index b6291a558..606be55db 100644
--- a/Configurations/50-win-onecore.conf
+++ b/Configurations/50-win-onecore.conf
@@ -71,6 +71,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
"VC-WIN64A-UWP" => {
@@ -80,6 +81,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
"VC-WIN32-ARM-UWP" => {
@@ -89,6 +91,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
"VC-WIN64-ARM-UWP" => {
@@ -98,6 +101,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
);
d+        disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
ex_libs         => "WindowsApp.lib",
},
"VC-WIN64A-UWP" => {
@@ -80,6 +81,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
"VC-WIN32-ARM-UWP" => {
@@ -89,6 +91,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
"VC-WIN64-ARM-UWP" => {
@@ -98,6 +101,7 @@ my %targets = (
lflags          => add("/APPCONTAINER"),
defines         => add("WINAPI_FAMILY=WINAPI_FAMILY_APP",
"_WIN32_WINNT=0x0A00"),

   disable         => [ 'dso', 'ui-console', 'stdio', 'async' ],
   ex_libs         => "WindowsApp.lib",

},
);
diff --git a/Configure b/Configure
index d5dc36c28..f9cf4f524 100755
--- a/Configure
+++ b/Configure
@@ -409,6 +409,7 @@ my @disablables = (
"ubsan",
"ui-console",
"unit-test",

"uplink",
"whirlpool",
"weak-ssl-ciphers",
"zlib",
@@ -482,7 +483,7 @@ my @disable_cascades = (
Without position independent code, there can be no shared libraries or DSOs
"pic"               => [ "shared" ],

"shared"            => [ "dynamic-engine" ],

"shared"            => [ "dynamic-engine", "uplink" ],
"engine"            => [ "afalgeng", "devcryptoeng" ],
no-autoalginit is only useful when building non-shared

Where I can find your modify branch? @levitte

Pardon, I've been distracted by a gazillion other OpenSSL stuff...

Hi @levitte how is this going? Fixing this is blocking fixing https://github.com/Microsoft/vcpkg/issues/4267.
I would appreciate your help.
thank you in advance

@levitte sorry to bother you again about this. Do you have plans to work on this?

Closed because of https://github.com/openssl/openssl/pull/8917.


Im not able to see the toolbar on the test server (AWS Elastic Beanstalk) but its available on the local server !!!

Hi,
I have installed and configured for the DJDT , but im not able to see the tool bar in my test server !!!???
is there anything else i need to do for it , to make it work on the test / production server???

As described in the documentation, there are additional controls to avoid accidentally exposing the debug info on the Internet. Look at SHOW_TOOLBAR_CALLBACK.


IE11: Potential Rounding Error when using .card inside .block-group

When a border is on a child of .block-group, the flex-basis and width values need the border-width added to the calc() statement.
Might be fixable with box-sizing: border-box.

https://github.com/ArcGIS/arcgis-for-developers/issues/4644
Fixed in https://github.com/ArcGIS/arcgis-for-developers/commit/bc4c16702a4d67b0529f639f78beb7043efe945f

I'm going to close this as there is now apparently no border on cards? And it already has box-sizing: border-box which it inherits from the block class.


pipelines page- show pipeline details

go to pipelines page, click on the + (plus) sign near one of the pipelines.
it still open the description and json tabs
get an error-"ENOENT: no such file or directory, open '/hkubedata/test-hkube-store/readme/pipeline/simple.json'"

Fixed on PR #37


add pktinfo consts and structs for linux and apple

The constants and structs are from /usr/include/linux/in.h, /usr/include/linux/in6.h for Linux (+ Android) and /usr/include/netinet/in.h, /usr/include/netinet6/in6.h for Apple.
With Apple it's important to mention that I'm choosing the RFC 3542 versions of the constants in alignment with other critical pieces of software like nginx, and Linux also defaults to this RFC version.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+

:pushpin: Commit 0e3cf47 has been approved by alexcrichton

:hourglass: Testing commit 0e3cf4737bff35b252736cb2888c20c5a89fa5bb with merge 297fc414c3225631e879ff87006ce4a53146bf1f...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 297fc414c3225631e879ff87006ce4a53146bf1f to master...


[SUGGESTION] Install AAS WorldWide Telescope JupyterLab components

Is your feature request related to a problem? Please describe.
I want to explore whether the AAS WorldWide Telescope (WWT) software package can deliver a compelling solution for exploratory visualization of Rubin imagery on the RSP.
Describe the solution you'd like
In order to test out the WWT visualization framework for this use case, a few software components need to be added to the RSP JupyterLab stack (see below).
Describe alternatives you've considered
Most of the WWT components can installed at the user level if needed, but there are a couple of server extensions required in order to pass data from the kernel backend(s) to the browser frontend. I don't believe that those are user-installable with the RSP setup, although I'm not 100% sure about that.
Additional context
The key server extensions are:

pywwt
wwt_kernel_data_relay

The ideal setup would also include the WWT JupyterLab extension, installable either as:

@wwtelescope/jupyterlab "source" form
wwt_jupyterlab_extension "prebuilt" form

There are also kernel-side Python packages to complete the framework (most importantly pywwt) but those can be user-installed if needed.

Hi — is there any extra information that I can provide that would help move this ticket forward? Thanks!

Apologies for the delay. The short answer is that we are not prepared to support the WWT on the Rubin Science Platform at this time. We have removed it from our notebook aspect interface.
The long answer is that there are a lot of challenges in supporting a compute environment for thousands of users, and testing that everything works (and stays working) is an effort-consuming process. We therefore look for "common denominator" packages that are requested by a sizeable fraction of the community as well as our own internal science users, so that we can be certain that they are extensively used and that they have active users as internal champions. At this (pre-operations) stage of the project we have not been able to find any compelling interest in using WWT in the RSP nor any current WWT users among our product owners. Moreover, graphical user interfaces are a worst-case scenario, as they are not tractable to our current automated testing and have an even higher bar for being made available than numeric packages.
In the long run, during Rubin Operations we will develop a process for adding capabilities to the RSP in consultation with our User Committee. I anticipate that at that time, we might be able to add capabilities without internal project advocates under circumstances where third-party support can be provided by another institution. That will be a good time to revisit the WWT issue. Sorry to be the bearer of bad news.

Congratulations and best wishes @pkgw!
Rubin Observatory will have a booth in the AAS 240 Exhibit Hall, and I'll be there a lot of the time. Looking forward to chatting.


Can you please provide any documentation for Slim 4 Graphqlite Implementation.

Can you please provide any documentation for Slim 4 Graphqlite Implementation.

You might reference the following two repositories for implementation into frameworks.  This repo and lib is framework agnostic.  I don't have any specific implementation details for Slim.
https://github.com/thecodingmachine/graphqlite-bundle
https://github.com/thecodingmachine/graphqlite-laravel
You can also follow the instructions for installing without a framework, which will give you an idea of how you might implement it within your Slim app.
https://graphqlite.thecodingmachine.io/docs/other-frameworks


CMPivot status message queries / auditing?

Just installed 1806, CMPivot is amazing - I saw in the document for CMPivot the log files, but what about auditing use / status message queries for it?
Apologies if this is not the correct venue or method for such an inquiry.

Thanks @tstolswo for the feedback. Good question, I don't know, but will check. If yes, it's good addition to add to the article (especially regarding auditing). If no, I'll redirect you to the correct venue to file product feedback. :)

The audit message for CMPivot is the same as when running a script: user A has initiated the client operation type 135 on collection B.
That's some interesting detail I can add to this article.
If you're interested in the product doing more along these lines, then see Product feedback.

Thanks for the prompt responses, @aczechowski; exactly what I was looking for.

Oops, lets keep the issue open. My tracking item to update the doc! :)

Meghan took care of this a while back when she created the troubleshooting article for CMPivot


Add Zemismart Zm02 Curtian Motor

Check all that apply
Type of Change

[ ] WWST Certification Request

If this is your first time contributing code:

[ ] I have reviewed the README.md file
[ ] I have reviewed the CODE_OF_CONDUCT.md file
[ ] I have signed the CLA

[ ] I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com

[ ] Bug fix
[ ] New feature
[ ] Refactor

Checklist

[ ] I have performed a self-review of my code
[ ] I have commented my code in hard-to-understand areas
[ ] I have verified my changes by testing with a device or have communicated a plan for testing
[ ] I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change
Summary of Completed Tests

@iris-wy PLease provide changes to the translation file as well. Thank you.


Testimonial for Dunsin

Name
Dun-sin
Title
A Guiding Light in the Open Source Community
Description
Dunsin is an outstanding open-source contributor. She truly represents the spirit of open source with her genuine tips and dedication. She empowers and guides developers, making her a genuine inspiration in the tech community. Her influence is significant, and she's truly authentic.

Thanks @sojijr


Add dockerfile for liboqs-go

This is a multistage dockerfile which builds liboqs in a build container and then exports the build artifacts to a second container to keep the image as small as possible. After that, it installs liboqs-go and makes it available for Go modules.

I made a new sub directory and added a little documentation :)

It would be great if this container is hosted at docker hub. I changed the Dockerfile so that it builds the tests per default instead of the kem example.  As next step, I will add the .circleci file.

@JannisFengler The image is now accessible at https://hub.docker.com/repository/docker/openquantumsafe/go. Would you agree that now an update (simplification) to https://github.com/open-quantum-safe/liboqs-go#quick-and-dirty-execution-of-examples-with-disposable-docker-containers is sensible? If so, would you want to do another PR for that in the README (and possibly add yourself as a contributor there) or shall we add some suitable language?

I will update the readme in another PR. Maybe it also makes sense to update the use of the docker container so it mounts the directory of the user.

Maybe it also makes sense to update the use of the docker container so it mounts the directory of the user.

Quite possibly. My approach for the docker README is to consider people only reading the documentation at docker hub and not being versed in PQC. That then gives me contents for a self-contained README that is simply copied as-is to docker-hub. For now I put links at docker hub as I (currently) think that both, docker and project, READMEs are required to understand the contents of the docker image.


Bugfix of subtensor validation

Shape of parent tensor should be compared with shape of subtensor, not
with itself.
Signed-off-by: llFreetimell<EMAIL_ADDRESS>

Cherry picked. Will be part of the next release.

This change is now part of the v18.08 release. Thanks for your contribution.


Added FileManager extension method "decode"

This method allows to decode an object that was previously save to a file.
Checklist

[+] I checked the Contributing Guidelines before creating this request.
[+] New extensions are written in Swift 4.
[+] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
[+] I have added tests for new extensions, and they passed.
[+] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[+] All extensions are declared as public.
[+] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 535 tests, with 0 failures (0 unexpected) in 13.091 (17.310) seconds

:book:
tvOS: Executed 504 tests, with 0 failures (0 unexpected) in 5.547 (7.530) seconds

:book:
macOS: Executed 369 tests, with 0 failures (0 unexpected) in 1.722 (2.440) seconds

SwiftLint found issues
Warnings

File
Line
Reason

FileManagerExtensions.swift
67
Colons should be next to the identifier when specifying a type and next to the key in dictionary literals.

FileManagerExtensionsTests.swift
85
Lines should not have trailing whitespace.

  Generated by :no_entry_sign: Danger

Not sure what exactly failed here.

@omaralbeik @LucianoPAlmeida can you please check?

Sorry, I just notice that we missed that one 😅, not remember why we didn't merge it
@AlexeiGitH Closing this one due to inactivity, feel free to reopen :))


add secret

@AsfaMumtaz Image is available for testing. docker pull stakater/workshop-excercise:SNAPSHOT-PR-27-289566b3


Fox at-a-glance dashboard shows merged nodes

In the at-a-glance dashboard there should be no merged nodes, but there are:

This silver lining is that this bug is what allowed us to see the broken node name merging in #630.
This is likely a problem in naicreport, it must ask sonalyze not to merge nodes when it computes jobs for the main dashboard display.  I'm guessing that this code was correct once upon a time, then changes elsewhere made it incorrect.

OK, what happened here was that prior to #614 landing, sonalyze jobs would be run without a config-file (by accident or design, I don't know) and so node merging could not take place because information in that file determines eligibility for merging.  But with naicreport running sonalyze remotely, this is not an option: the config information will always be supplied by the server (and this is the right thing).  The correct fix is to add an argument, eg -no-merge or something like that, and pass it from naicreport.  This switch will complement -batch, which basically means all nodes are eligible for merging (not what we usually want but useful for testing).  Maybe -batch should be renamed or at least have a more intelligible alias while we're in here.  Maybe -merge-all and -merge-none.


Scrolling up & down in the in-editor Documentation is not smooth

Tested versions

Reproducible in 4.3.beta1, but I think it's actually in all Godot 4.x versions

System information
Godot v4.3.beta1 - TUXEDO OS 3 22.04.4 - Wayland - Vulkan (Forward+) - integrated Intel(R) Graphics (RPL-P) () - 13th Gen Intel(R) Core(TM) i7-13700H (20 Threads)
Issue description
The code editor and documentation screens have different scroll smoothing.
The code editor is very smooth and feels nice.
Scrolling in a builtin documentation page however feels heavier, and jumps by around 4 lines at each mouse scroll.
Steps to reproduce

Open a .gd script big enough to scroll, and then scroll up & down using the mouse. It's smooth.
Press F1, and open any documentation big enough, then scroll up & down using the mouse. It feel a bit more sluggish, and jumpy. There is no smoothness.

In isolation, it might have not been noticeable, but those 2 types of screens (code editor and documentation pages), share the same spot in the window, and usually you have to jump from one to the other quickly when typing some code. This makes the lack of smoothness in the documentation quite noticeable
Minimal reproduction project (MRP)
No need. This is related to the built-in documentation editor.

Thanks for the report! Consolidating in https://github.com/godotengine/godot-proposals/issues/5386.

related https://github.com/godotengine/godot-proposals/issues/5386


Transparent background (not blurred)

Description of the new feature/enhancement
A transparent background, acrylic is a blurred background not a transparent background
 it will provide users to see info they need to see behind the terminal
Proposed technical implementation details (optional)
 Add an option for transparent background just like acrylic, just not blurred.

Please search for existing duplicates before filing new issues.
/dup #603


Add regression test for generated package data

This adds a regression test for generated pacakge data. The test folder now has a data folder inside it which contains a reference copy of the generated package. This is then compared at test time to a newly generated package. Any differences are shown after the failing test with a diff that looks like:
E           RuntimeError: Non-zero diff between generated files and expected files.
E           Generated files can be found in /Users/dstansby/software/python-tooling/pytest_output/test_package_generation0/cookiecutter-test.
E
E           --- /Users/dstansby/software/python-tooling/pytest_output/test_package_generation0/cookiecutter-test/README.md
E           +++ /Users/dstansby/software/python-tooling/tests/data/test_package_generation/README.md
E           @@ -119,7 +119,7 @@
E            tox -e docs
E            ```
E
E           -from the root of the repository. The built docs will be written to
E           +from the root of the repository. The built documentation will be written to
E            `site`.
E
E            Alternatively to build and preview the documentation locally, in a Python

tests/test_package_generation.py:79: RuntimeError

To update the test files with an intentional change, when the test fails the test data is updated with the changes that can then be easily comitted (if desired).
Fixes https://github.com/UCL-ARC/python-tooling/issues/329

Are we sure we want this? Every time there's a new change, this test will have to be updated.

Are we sure we want this? Every time there's a new change, this test will have to be updated.

See https://github.com/UCL-ARC/python-tooling/issues/329 for context and motivation.
Definitely appreciate that this adds a bit more work when changing anything in the template, but I think it's worth it to catch potential errors such as in https://github.com/UCL-ARC/python-tooling/pull/309 which slipped through the PR author and reviewer.
I've tried to make the loop here as simple as possible:

Run tests
If this test fails, it modifies the test data in place
Review if the test data is modified as expected. If it is, commit and push the changes.

See #329 for context and motivation.
Definitely appreciate that this adds a bit more work when changing anything in the template, but I think it's worth it to catch potential errors such as in #309 which slipped through the PR author and reviewer.

Consider me won over, I'd forgotten about #329

The tests are failing again @dstansby. main had updated.


Support for Angular Material v15

Hello
Today, I have finished updating the project from Angular v14 to v15, along with Angular Material to v15.
Once I try to run the application, I get the following error for cdk-table-exporter
Error: node_modules/cdk-table-exporter/lib/services/exporters/file-exporter.d.ts:3:67 - error TS2344: Type 'T' does not satisfy the constraint 'Options'.

3 export declare abstract class FileExporter<T> implements Exporter<T> {
                                                                    ~

  node_modules/cdk-table-exporter/lib/services/exporters/file-exporter.d.ts:3:44
    3 export declare abstract class FileExporter<T> implements Exporter<T> {
                                                 ~
    This type parameter might need an `extends Options` constraint.

I managed to compile the project using "skipLibCheck": true into tsconfig.json but once I'm about to export as a CSV file, I run into this error

Experiencing the same Issue. Commenting to help visibility.

same issue here.

So I was able to get my application running locally by adding this import
import { Options } from '../../options';
and then editing the class declaration to say:
export declare abstract class FileExporter<T extends Options> implements Exporter<T> {
But this is changing the node_modules and not sure how viable that is.

So I was able to get my application running locally by adding this to file-exporter.d.ts
import { Options } from '../../options';
and then editing the class declaration to say:
export declare abstract class FileExporter<T extends Options> implements Exporter<T> {
But this is changing the node_modules and not sure how viable that is.

Can you fork it with the code changes?
In this way it will be possible for everybody to install that version via npm i

So I was able to get my application running locally by adding this to file-exporter.d.ts
import { Options } from '../../options';
and then editing the class declaration to say:
export declare abstract class FileExporter<T extends Options> implements Exporter<T> {
But this is changing the node_modules and not sure how viable that is.

Can you fork it with the code changes? In this way it will be possible for everybody to install that version via npm i
EDIT: Seeing old in comments the author saying "pull requests" are kindly welcome

I made the changes and submitted a pull request.

So I was able to get my application running locally by adding this to file-exporter.d.ts
import { Options } from '../../options';
and then editing the class declaration to say:
export declare abstract class FileExporter<T extends Options> implements Exporter<T> {
But this is changing the node_modules and not sure how viable that is.

Can you fork it with the code changes? In this way it will be possible for everybody to install that version via npm i
EDIT: Seeing old in comments the author saying "pull requests" are kindly welcome

seems like someone has already made a pull request here. https://github.com/HalitTalha/ng-material-extensions/pull/158/commits

We run into the same problems using Angular 15.
Is there any update/progress on this issue?

We are also facing the same issue... is there any solution?

Hi there,
Since this would require a full rebuild of the Angular workspace with newer versions, it's taking time. But I hope I'll be able to handle it soon. If anyone could have done it before (upgraded the workspace and projects into v15) that would be great to have this as a PR.


Give public transportation recommendation

Current plan for location: Employer puts it into a box, and based on the address we generate text to insert into the posting about how to get there via transit (or if a car is required).

Original:
At the very basic level, we have a permanent message that encourages job posters to include info about public transportation from major metro areas.
A slight iteration would be to scan for instances of 'bus' or 'train' and only show the warning if those words are not present.
There are more complicated versions that would take location info and generate directions for the poster, but those are beyond the scope of the tool for time being.
This issue originally created by @pacarole as codeforamerica/joblint#4.

ORIGINAL COMMENT BY @pacarole (here)
Sample text forthcoming.

Going to do some feasibility research into API options for figuring out the closest transit routes


Creating native compiler fails (x86-64 RHEL 9.2, x86-64 Alpine)

(GCC version set to 11.2.0)
I can create a cross compiler for x86_64 using CFLAGS="-fPIE" make install TARGET=x86_64-linux-musl -j. I then move the output folder to /usr/local/musl and export PATH=/usr/local/musl/bin:$PATH". Attempting to compile a native compiler with CFLAGS="-fPIE" make install TARGET=x86_64-linux-musl NATIVE=y -j` fails however, with various errors.
I just want a gcc/g++ toolchain targeting musl libraries. I do not plan on cross-compiling. I would use the pre-compiled ones on https://musl.cc, but when compiling php with intl, it causes a segmentation fault somewhere in the musl libraries. This problem does not exist when building this repo myself.

Did you ever figure it out?

Yes, after it fails you can find error messages in a gcc config.log. Something about calloc being poisoned. Removing that from gcc source makes compilation run through.
Wasn't an issue when using GCC 13 anymore, by the way, but you'll have to patch the repo with the new checksum.

Oh wait, this was the runtime issue after it successfully built: no, never figured it out. Rebuilding with newer versions and installing musl libraries fixed that.


Remove Appointment duplication

What does this pull request do?
Removes duplication in Appointment data structures, by removing the AppointmentDetails class that was introduced as a shared interface that could represent both original Appointment (used by for Initial Assessment)  and ActionPlanAppointment classes.
There's a lot of file changes required due to the number of classes that relied on these fields, so to break the important changes, we now have the following structure:

AppointmentSchedulingDetails - scheduling details about an
appointment e.g. time, appointment type, duration. This also replaces
the AppointmentUpdate interface that we sent to the
Interventions Service as it contained the same fields.
Base Appointment - extends AppointmentSchedulingDetails and adds
additional SessionFeedback which felt like it didn't belong on the
SchedulingDetails model.
InitialAssessmentAppointment - extends Appointment and adds an
id.
ActionPlanAppointment - extends Appointment and adds a
SessionNumber.

It's worth noting that AppointmentSchedulingDetails has nullable fields, where there weren't necessarily nullable fields on the duplicate interfaces that this new interface replaces. This shouldn't be an issue, as we seem to have null checks for this behaviour.
What is the intent behind these changes?
This change was motivated by the need to add a SessionType e.g. "Group" or "1:1" field, as I didn't want to add this to all the duplicate classes, and now felt like a good time to re-use the shared interfaces. It's been a bit difficult adding behaviour to these classes when there are a lot of different types of appointment, so I'm hoping it should be easier going forward.

@lawrence-forooghian good points above, and you're right about the session vs appointment being a bit muddied at the moment.
I don't think there are any big plans to refactor Appointments on the API at the moment. It would definitely make sense to do, but with a lot of people being away now / over the next few weeks it might not be considered a high priority. Either way, I think this feels a bit clearer for representing how things are now.
I'm gonna tag @andrewburrowsmoj and @tomsmyers as other people I "consulted" when making this change to see if they've got any thoughts on the above.

Yeah, I think my main worry was the introduction of nullability to the date / time etc fields. Because it means that if we add new appointment-related pages, they'll all have to have nullability checks in them even though the nullability is just a side-effect of one particular appointment type that isn't really an appointment.

To clarify on the above, I see the existing Appointment as being the correct way to do appointments for all future things that have appointments, and ActionPlanAppointment as being a special case that should have no influence on future appointment-related things (in particular, nullability).


Scrollbar showing for scrollable Tabs in Legacy Edge

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When you have scrollable Tabs, they do not show a native scrollbar for Firefox / Chrome / macOS. However, I do get a native scrollbar for Legacy Edge and it looks quite odd.
Expected Behavior 🤔
I would like to get rid of that scrollbar. Should be quite easily doable by adding an extra style to Tabs.js / scrollable style. With #15762 the style "scrollbarWidth:none" was added and the style "msOverflowStyle:none" was removed from ScrollbarSize.js If we could also add "msOverflowStyle:none" to Tabs.js / scrollable style, the scrollbar will disappear.
Steps to Reproduce 🕹
Open https://material-ui.com/components/tabs/ in Legacy Edge and have a look at the vertical Tabs example there. I personally do also get it for horizontal tabs, while this is not happening here. To be honest, I have not been able to find out, what is the difference in my setup. However, also there, when adding the property "msOverflowStyle:none" to MuiTabs / scrollable, it will disappear.
Your Environment 🌎
| Tech             |  Version |
| Material-UI  |  v.4.9.5   |
| React           |  v.16.3.0 |
| Browser       |  Microsoft Edge 44.17763.831.0 (Legacy)  |
| TypeScript   |  v.3.7.5   |

@caroe233 Something is definitely off. Did. you have the time to investigate?

I'm closing, we have no time to solve this problem.


Update fi.json

Translated new lines
:recycle: Current situation
Describe the current situation. Explain current problems, if there are any. Be as descriptive as possible (e.g., including examples or code snippets).
:bulb: Proposed solution
Describe the proposed solution and changes. How does it affect the project? How does it affect the internal structure (e.g., refactorings)?
:gear: Release Notes
Provide a summary of the changes or features from a user's point of view. If there are breaking changes, provide migration guides using code examples of the affected features.
:heavy_plus_sign: Additional Information
If applicable, provide additional context in this section.
Testing
Which tests were added? Which existing tests were adapted/changed? Which situations are covered, and what edge cases are missing?
Reviewer Nudging
Where should the reviewer start? what is a good entry point?

Merged into beta-5.0.0 branch:

https://github.com/homebridge/homebridge-config-ui-x/commits/beta-5.0.0/

Thanks!


Pigeon: add lifecycle / ability to close down pigeon channels

This is a mix of feature request and a question for pigeon:
Let's say I have a screen in Flutter that requires some data from native code. Data comes over time, so I'm using @FlutterApi. When screen opens, I create Pigeon instance in Flutter and start receiving data.
However, what happens when user closes said screen? From what I can see, Pigeon instances are singletons that never die, potentially causing memory leaks since they reference the UI classes that are not displayed anymore.
Ideally, there would be a way for me to close/dispose the pigeon instance after screen closes. Or is there another pattern that is supposed to be used?
Thanks.
@gaaclarke

I think what you are looking for is Api.setup(binaryMessenger, null);, right?

Would this work? From what I can see, new message channel is created every time setup is called. Do those channels share single message handler?

Also, from what I see, this does not work on the dart side. Setup method does not check for the null value anywhere.

Yea, they are confusing.  Channels aren't the things that store the connections.  It's all saved on the binary messenger.  That's why it is a parameter to creating channels and setting up pigeon.
This would clear things out:
{
  Channel channel = Channel(binaryMessenger, "foobar");
  channel.setHandler(() { print('hello'); });
}
{
  Channel channel = Channel(binaryMessenger, "foobar");
  channel.setHandler(null);
}

Thanks for the explanation. However, from what I see, pigeons generated on the dart side do not handle null well (they call the listener even it if it null, spewing errors into the console).

Thanks @matejdro, it would be helpful if you can supply some code where you are seeing the problem.  The code using Pigeon and the code generated by Pigeon is helpful.  That will make it easier for me to get started when looking into it.  I appreciate your help.

Here is an example:
ScanCallbacks interface (https://github.com/pebble-dev/mobile-app/blob/42c81f4e559d777cd2c9367839add86ae65f9d2d/pigeons/pigeons.dart#L18) generates into this:
https://github.com/pebble-dev/mobile-app/blob/42c81f4e559d777cd2c9367839add86ae65f9d2d/lib/infrastructure/pigeons/pigeons.dart#L142
Note that nullability of the api variable is never checked, methods are just called blindly. So I can't put null there.


Configure Talon pod to not rollout on configmap changes, allow user to input rules.yaml directly, configure Talon to rollout on secret change

What type of PR is this?
/kind feature
/kind chart-release
Any specific area of the project related to this PR?
/area falco-talon
What this PR does / why we need it:
Which issue(s) this PR fixes:
There's no issue open for this fix.
Special notes for your reviewer:
Checklist

[ x ] Chart Version bumped
[ x ] Variables are documented in the README.md
[ x ] CHANGELOG.md updated

@IgorEulalio: The label(s) area/falco-talon cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?
/kind feature
/kind chart-release
Any specific area of the project related to this PR?
/area falco-talon
What this PR does / why we need it:
Which issue(s) this PR fixes:
There's no issue open for this fix.
Special notes for your reviewer:
Checklist

[ x ] Chart Version bumped
[ x ] Variables are documented in the README.md
[ x ] CHANGELOG.md updated

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: IgorEulalio
Once this PR has been reviewed and has the lgtm label, please assign alacuku for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

6abed4a feat: remove helm-generated labels and timestamp so that pod isn't recycled with a new update
5785832 feat: trigger rollout based on secret change
7e39ab7 feat: remove rules_override.yaml file, add field so users can specify custom rules directly via values
63a3f93 chore: bump chart version, update CHANGELOG.md and make docs

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: IgorEulalio
Once this PR has been reviewed and has the lgtm label, please ask for approval from issif. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: IgorEulalio, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 16a97dd04eccd051e27e37d3d89d21c6e1ef6e43


[docs] better 512 px tile size documenation

Including specifying 512 and zoom 14 max to fix #156.
Vector tile changes are over in https://github.com/tilezen/vector-datasource/pull/1399.
Like that other PR: This is off the v1.0.0-docs11 branch that happens for docs to be the same as master. This PR should be merged to master before the v2 PR, and then we can just tag master as
v1.0.0-docs12 and releasing as latest will trigger Mapzen docs update.

@meetar can you take a look at the buffered is better because section?

Thanks all! I've merged Peter's PR and addressed Ian's comment. Merging.


feat(node): add missing Brotli APIs to the zlib module

https://nodejs.org/api/zlib.html
Also, narrow the type of the second argument to the asyncFn's
callbacks from any to Buffer, and expand the type of the first
argument to all functions to include more Buffer-like types, as
specified in the node documentation.

The docs aren't actually specific that the callback param is a Buffer, but typescript says it is, so.

@mroch or @nmote can you take a look?

@Brianzchen any idea how to get this moving? 🙏

@isker I've messaged them on Discord and haven't heard back, if it's really blocking you, maybe jump on and express it's importance to you

Thanks for checking.

@jobrk I can rebase this branch and resolve conflicts if it'd help you.

@isker that would be perfect, thank you very much for this contribution, and sorry we took that long to look into it

Okay, there it is.


Fix importRoot

currently this fixes #64
however, there's still ambiguity with the CLI flag importRoot and root coming from config files.
importRoot takes precedence now, but I guess both should just be named root.
also, we might consider output to be resolved around the same root. having thought about that a little more, I think we actually should not - most of the time the output will go into some arbitrarily located dist folder, I guess.
thoughts?

should we also fix this part?

@giuseppeg Do you mean normalising it so it always refers to root?

@simonsmith we said that CLI flags should always override config file options, in this case --importRoot won't because we check for program['root'], we should add importRoot to the array.

Maybe get this merged and we can address the other issue separately.

Do we just need to make those test case changes?

Yeah.
I can fix the other part in a follow-up branch if you prefer.

Might be easier as it can be done in parallel. Then I think we're set to release a patch

hey guys! sorry, have been a bit busy & thus silent. please ping me if you'd like me to add more changes or squash the prev commits.

@casio Not a problem, we're all busy at times :)
I think if you could address the feedback about grouping the tests in a single describe then we're good to go

so I just put the importRoot related test in its own nested describe block, as @giuseppeg suggested.
also I only checked for errors here(as @simonsmith did in his current pr).
it might be a good idea to, in one of the next steps, switch tests unrelated to importRoot to not make use if -i at all, but I thought that'd be better to do in another pr.

@casio Yes, agreed. We can just give the full path to the fixtures which hilariously it seems like I had done even with -i which hid this bug in the first place :D

@simonsmith haha : )
fyi seeing appveyor bark, I just pushed an update. strangely the local lint task didnt catch that(done in describe call & a missing semicolon).

I think this looks good to merge. @giuseppeg ?

@casio where the other tests failing after your changes? I think that importRoot shouldn't affect the input file path  @simonsmith correct me if I am wrong.

@giuseppeg yes, they were. actually with how this is currently implemented, the name inputRoot would better mimic the behaviour.
and you're right, I guess: basically these are two different things - a root for the input(=entry) file and another one to resolve @import statements.
maybe it'd even be beneficial to revisit the concept/scope of how these things should work: ie. should it be rather import roots(plural), do we need a separate base path to resolve input and output, etc.
however I feel that'd go beyond the scope of this pr?

I don't see any failing tests?

I think @giuseppeg meant tests that read like
... -i path/to/fixtures path/to/fixtures/input.css
Theses were failing with the new behavior since the cli tried to read
path/to/fixtures/path/to/fixtures/input.css then.

Yea imporRoot is about @imports not input files.
We should fix this, please also revert the changes to the old tests.
I can take a look at the issue again and the PR, I am just hopping on and off and I haven't been able to read it carefully because I am busy – sorry about that :)

Interesting, I see what you guys mean.
Yeah it should relate directly to the postcss import root option.

Took a quick look, this is a non-issue because --import-root wasn't meant for this purpose i.e. pass input files without basepath. We should only fix #70 I suppose.

So are we saying the issue in #64 is expected?

It has always been like that. Ideally the root can be different than the input file's folder.

I see. I guess that does correctly mimic how it would with postcss-import directly. You'd pass a full path to an input file and also be able to set a separate import root if needed. It is somewhat confusing but I think in most cases you rarely need to set -i.

So it looks like this is PR is not worth merging then? I fear we may have led you down a wrong path @casio. My apologies if so D:

@simonsmith haha, no worries. was worth the ride : )

thank you for your time @casio! Sorry for the inconvenience.


Moving lines in the ER diagram

Discussed in https://github.com/orgs/dbeaver/discussions/34139

Originally posted by paoloholzl May 24, 2024
Example

In the ER diagram, lines usually originate from the fields where a relationship is set (but this does not happen in DBeaver). For example, in figure 1, this is what I need. Since the schema connects the tables but not the related fields, row-by-row adjustments are required.
It is possible to move the line, but due to the set mechanism, it is almost impossible to get from field to field without creating broken lines (see figure 2).
Sometimes reducing the number of breaks is almost impossible.
Ideally, each line should start from the fields in referential integrity (if any), and be movable if needed.
Then, a marker would be needed for each angle of the broken line (with the possibility of removing it with a right-click), as shown in example 3. Additionally, a way to move the line from its beginning (example 3, a marker that moves the start directly from its origin) would be helpful.
I use ER diagram programs for SQL Server, Oracle, and even MS Access, and none of them have these problems (they have other issues). I am providing an example of one of my diagrams to show that complex results can be achieved. I am also posting an image of the poor result of connecting all lines to the same origin with great difficulty.
The tool is splendid, but this is a significant shortcoming.
Try to connect to the same filed (orrible)

Er example

See https://github.com/orgs/dbeaver/discussions/34139#discussioncomment-9957453 with steps to reproduce


[5.4][SourceKit] Verify the stdlib is loaded before creating an AST

Cherry-picks https://github.com/apple/swift/pull/36797 to release/5.4.

Explanation: When sourcekitd is unable to load the stdlib, report an error and fail early instead of trying to compile and crashing somewhere in the type checker because required types from the standard library cannot be found.
Scope: sourcektid requests that are unable to load the standard library
Risk: Very low
Testing: None, the fix was synthesized from a set of crash reports
Issue: rdar://78035923
Reviewer: Argyrios Kyrtzidis (@akyrtzi)

@swift-ci Please test

@swift-ci Please nominate

@swift-ci Please nominate


Fixes #624

Supports condensed DistanceMatrixes, adds a test, and updates pw_distances.

@Kleptobismol You'll need to update the docstring of the DistanceMatrix class.

I closed it because I accidentally deleted the branch it was on, I'll create a new branch and put all changes on it.


Does this project also support the socket.io client?

Recently, I was trying to use import { io } from "https://cdn.socket.io/4.6.1/socket.io.esm.min.js";  in a deno project, but it didn't seem to work. Nothing was emitted. 🤔 Maybe this project implements a fixed version of the socket.io client? I couldn't find it in the repo, but I hope it's somewhere in here. Thanks much!

Hi! No, the JavaScript client is not compatible with Deno, but if there is enough interest we could totally implement it.

So, how connect from client with server?

I'm worried about that too...

people, it can be done with deno using the socket.io client
This code works:
import { io } from "https://cdn.socket.io/4.6.1/socket.io.esm.min.js";

const socket = io("http://localhost:8080/", {
  transports: ["websocket"],
});

socket.on("connect", () => {
  console.log(socket.id); // x8WIv7-mJelg7on_ALbx
});

@RomanFama592 does it work from a web browser?

This is what is holding me back from using Deno.


Find a way to support corner radius on blurred views inside popovers

I tried to play with layer, corner & image masks, clipsToBounds property, container views, but couldn't find a way to achieve the desired behavior. Maybe together we can find how to make it work 🙂
Upd: everything works fine in default windows, but blur-in-blur doesn't work.

let visualEffectView = NSVisualEffectView(frame: NSMakeRect(100, 100, 300, 300))
visualEffectView.material = .dark
visualEffectView.blendingMode = .behindWindow
visualEffectView.wantsLayer = true
visualEffectView.layer?.cornerRadius = 15.0
self.view.addSubview(visualEffectView)

let visualEffectView2 = NSVisualEffectView(frame: NSMakeRect(100, 100, 100, 100))
visualEffectView2.material = .light
visualEffectView2.blendingMode = .behindWindow
visualEffectView2.wantsLayer = true
visualEffectView2.layer?.cornerRadius = 15.0
visualEffectView.addSubview(visualEffectView2)

Some solutions I found:

Default behaviour:

Insert non-blurring NSVisualEffectView (with .headerView material for example) under the blurred one. But it should cover all the background or you'll get the second picture.

Play with opacity and different non-blurring materials (they actually blur the background if their opacity is low, but it may be hard to notice)

Use separate windows (here  you can find some great examples of window styles)


Not working 1.16.5

Title is as it says, it is not working for 1.16.5
Could you update for 1.16.5?

Can confirm, not working in 1.16.5

I fixed it.
I opened the reach-out-1.0.0-1.16.4.jar file in WinRAR
Then I double-clicked on the file named fabric.mod.json
Then I edited this part:
"depends": {
"fabricloader": "\u003e\u003d0.10.8",
"fabric": "*",
"minecraft": "\u003e\u003d1.16.1"
},
to this
"depends": {
"fabricloader": "\u003e\u003d0.11.6",
"fabric": "*",
"minecraft": "\u003e\u003d1.16.5"
},
Saved the file and let WinRAR update the jar file.
I also renamed the jar file to reach-out-1.0.0-1.16.5.jar
Now it works in Minecraft 1.16.5

I also got the mod working with Minecraft 1.17.1 by doing the same thing as above.


Omni for Notepad++

Add a new theme to the organization
If you have already created a theme, make sure you check the following requirements:

[x] The theme follows the template;
[x] The theme follows the Omni Color Palette;
[x] The branch name is main (we will keep this name pattern from now on);
[x] The theme has correct instructions on how to install it;
[x] The repository name is lowercase and contains just the application name. E.g. visual-studio-code.

Application: Notepad++
Application URL https://notepad-plus-plus.org/
GitHub URL: https://github.com/AllanCapistrano/notepad-plus-plus

Hey @AllanCapistrano, I have reviewed the theme, and we can include it in the organization. 🎉
I'll be sending an invite for you to join the organization.
Before transferring the repo, make sure to change all URLs to match the new repository link.
Also, open a PR and include the theme on the main repository 👊🏻

Thanks, @AllanCapistrano!


Can not build on iPhone 5 / armv7 devices

The app builds fine using the new Firebase pods on iPhone 5s, 6, 6s but I get this using the same code on an iPhone 5 with the latest iOS version:
Segmentation fault 11

While loading members for 'ViewController' at
While deserializing decl #101 (PATTERN_BINDING_DECL)
While deserializing decl #7 (VAR_DECL)

Thanks for your input.

I was able to fix by not storing a snapshot as class variable explicitly but as AnyObject? then casting it when using it.


SelectBox Custom, List: Low contrast for foreground, hover colors in Light themes

Light themes have relatively low contrast for foreground and hover colors.
ideally we do not need to create a new color.  Either we can tweak the default list colors
which are used for quick pick , SelectBox, Explorer et cetera.
Light Default:

Bad Hover contrast:

I suggest we increase the contrast for the default listHoverBackground applicable to all users.
For the foreground color we could make this slightly darker again for the default.
I don't see why we would create new colors either, I think whatever is good for selectBox should be the same and good for the quick pick
Tagging this "under discussion" hopefully that is correct.

@weinand
@bpasero
I finally figured out the listFocusForeground has no default, it's inherited from Monaco-shell.
If we define it and listFocusHover in light-defaults we won't create any other colors.
Below light+ with foreground, hover darkened:
foreground  ===  #454545 originally #6c6c6c
hover  ===  #e8e8e8

@cleidigh can you make a PR for me to try out your suggested color change?


Site multi-instrument multi-inlet selection

Should we be able to select between instruments and inlets?

I think I'll add the inlet selection to the popup when the site is clicked on for now.

Yea I think selecting between inlets at least would be helpful for this.

This was done with #2 .


Fix login error

https://github.com/carpedm20/fbchat/issues/446

I agree with @kapi2289, so I'll close this for now


Updates to use ACR mgmt SDK

Removed SDK from CLI module.
Minor updates to match new SDK.

To address issue https://github.com/Azure/azure-cli/issues/1107

/cc @SajayAntony @skkestrel @DavidObando


Fc 2127 doc examples of tailwind

What
This introduce a guide to setup tailwind in a front-commerce project
Preview
https://deploy-preview-894--heuristic-almeida-1a1f35.netlify.app/docs/3.x/guides/extend-vite-configuration/tailwind

@mGGk-fr this should have targeted main. Can you port it to main please? (I don't think we have 3.5 specific doc on next already, so it could be only merging next into main.


how to use broadcastTXT... in esp-fs-webserver

how to use broadcastTXT... in esp-fs-webserver

Have you checked the example?
https://github.com/cotestatnt/esp-fs-webserver/blob/master/examples/withWebSocket/withWebSocket.ino


Update segmented buttons to support Material 3

As part of the Material 3 specification there are updates to the Segmented Button visuals:

The Flutter Material library currently has a ToggleButtons class that we should either update to support Material 3 or build a new widget if they are not close enough in functionality.

It would be nice if the API aligned with the Cupertino segmented control, it looks probably more similar than ToggleButtons.

Probably better to build a new widget, can then also improve its API and features, plus name align it with the M3 name too.
ToggleButtons have some limitations, like does not implement VisualDensity and it is based on RawMaterialButton. Then add oddities like the border is drawn outside its content height/width constraints. It can be themed fairly close the SegmentedButtons look, but not quite.

cc: @rydmike
Thanks for the feedback!

ToggleButtons have some limitations, like does not implement VisualDensity

This looks to be true.

and it is based on RawMaterialButton.

ToggleButtons no longer contain RawMaterialButton. (I've replaced it in https://github.com/flutter/flutter/pull/101760)

Then add oddities like the border is drawn outside its content height/width constraints. It can be themed fairly close the SegmentedButtons look, but not quite.

Investigating into this.

cc: @rydmike @darrenaustin @HansMuller
After reading Segmented buttons sepcs and some native Android testing.

In terms of functionality, there is no change. The single and multi-select functionality exist in both M2 and M3 versions
(there is a check to toggle between single and multi-select on Android, we can easily introduce this toggle if needed)
There is a new optional check icon to indicate the selected state.
Layout height is a little taller.
Slight default Shape change and minor typography changes.

Aside from minor improvements stated in https://github.com/flutter/flutter/issues/103529#issuecomment-1151700201 which are already required addressing in M2 ToggleButtons, there is no significant difference.
I will defer to other team members for the widget name update. (In my testing I noticed even Android API doesn't have an updated name for SegementedButtons, it simply refers to MaterialButtonToggleGroup with different style attributes for M2 and M3).
We also didn't introduce newly named widgets for regular buttons, for instance Filled or Filled Tonal, see Material 3 button types

Yes, there is FilledButton now. https://github.com/flutter/flutter/pull/107382

After looking more closely at this, I think we should create a new SegmentedButton API that combines the best of the ToggleButton and CupertinoSegmentedControl APIs. It would of course be driven by M3 tokens by default, but would hopefully be configurable enough to be able to pull off Cupertino styles with just theme data. I have already started work on this, so if you don't mind @TahaTesser, I will assign this to myself.

Thanks @darrenaustin, I also think that is a good call. Looking forward to seeing the results! 👍🏻

It sounds. Definitely a bigger project, thanks for taking this.


[Bug] Could not load type 'Microsoft.AspNetCore.Builder.IISServerOptions' from assembly  KernelMemory service with Ollama

Context / Scenario
Run MemoryKernel Service from source using .NET and Ollama endpoint for text (phi3:medium-128k) and embedding (nomic-embed-text) model.
What happened?
Hi there, I am running into an error when trying to run a KernelMemory service with Ollama endpoint from appsettings.Development.json config file.
Unhandled exception. System.TypeLoadException: Could not load type 'Microsoft.AspNetCore.Builder.IISServerOptions' from assembly 'Microsoft.AspNetCore.Server.IIS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.```
Thank you in advance!

### Importance

edge case

### Platform, Language, Versions

.net 8.0
Ubuntu 22.04

### Relevant log output

```shell

by any chance, does the project have a Properties/launchSettings.json file with an IIS profile?


Test code intermittently fails when using JavaxValidationPlugin

Describe the bug
Test code intermittently fails when using JavaxValidationPlugin
Your environment

version of Fixture Monkey: 0.4.11
version of Java/Kotlin: Kotlin 1.7.22

Steps to reproduce
Repository that reproduced the problem
I wrote 2 test codes. This test code does the same logic. Only the presence or absence of LabMonkey's JavaxValidationPlugin that creates fixtures is different.
@Test
fun getSavedQuestionnaire() {
    val uri = "/test"
    val sut: LabMonkey = LabMonkey.labMonkeyBuilder()
        .defaultNullInjectGenerator { DefaultNullInjectGenerator.NOT_NULL_INJECT }
        .plugin(KotlinPlugin())
        .plugin(JacksonPlugin())
        .build()
    val fixture = sut.giveMeOne<TestDataClass>()
    println(fixture.toString())
    every { testService.test() } returns fixture

    mockMvc
        .perform(MockMvcRequestBuilders.get(uri))
        .andExpect(MockMvcResultMatchers.status().isOk)
        .andExpect(MockMvcResultMatchers.jsonPath("$.id").value(fixture.id))
        .andExpect(MockMvcResultMatchers.jsonPath("$.name").value(fixture.name))
        .andExpect(MockMvcResultMatchers.jsonPath("$.name2").value(fixture.name2))
        .andExpect(MockMvcResultMatchers.jsonPath("$.name3").value(fixture.name3))
        .andDo(MockMvcResultHandlers.print())
}

// Fails intermittently
@Test
fun getSavedQuestionnaireWithJavaxPlugin() {
    val uri = "/test"
    val sut: LabMonkey = LabMonkey.labMonkeyBuilder()
        .defaultNullInjectGenerator { DefaultNullInjectGenerator.NOT_NULL_INJECT }
        .plugin(KotlinPlugin())
        .plugin(JacksonPlugin())
        .plugin(JavaxValidationPlugin())
        .build()
    val fixture = sut.giveMeOne<TestDataClass>()
    println(fixture.toString())
    every { testService.test() } returns fixture

    mockMvc
        .perform(MockMvcRequestBuilders.get(uri))
        .andExpect(MockMvcResultMatchers.status().isOk)
        .andExpect(MockMvcResultMatchers.jsonPath("$.id").value(fixture.id))
        .andExpect(MockMvcResultMatchers.jsonPath("$.name").value(fixture.name))
        .andExpect(MockMvcResultMatchers.jsonPath("$.name2").value(fixture.name2))
        .andExpect(MockMvcResultMatchers.jsonPath("$.name3").value(fixture.name3))
        .andDo(MockMvcResultHandlers.print())
}

Expected behaviour
JavaxValidation plug-in was added, but there is no part where javax.validation-related logic is used in fixture.
Therefore, I expect the same result, i.e. pass both test cases.
Actual behaviour
Test cases using JavaxValidationPlugin fail intermittently.
Additional info
It could be a bug in Spring and related tools, or my lack of proficiency in using it
Not exactly accurate, but the output of the path seems to be a Unicode-related issue.

@doljae
Yes it is a bug. Thank you for finding a bug.
If use JavaxValidationPlugin,  StringArbitrary generates only ascii codes.
String rarely be ascii control character, then test fails.
It would be fixed in 0.4.12

@seongahjo
Thanks for the quick reply 🚀
May I try to fix this part?
It's my expectation, but I think I can fix only a small part, so if you're okay, and if the related work isn't in progress yet, I'd like to get your guide and raise a PR 🙂

@doljae
Yes, it is appreciated if you fix this part! Thank you

@seongahjo
Could you please let me know which class of javax-validation module I should check in focus?
Also please let me know if you have a direction for revision that you thought about when you were trying to fix it 🙂

@doljae
Check out this
https://github.com/naver/fixture-monkey/blob/c7ed595a7943abe3eec24a3d9bb425517cc1eb23/fixture-monkey-javax-validation/src/main/java/com/navercorp/fixturemonkey/javax/validation/introspector/JavaxValidationJavaArbitraryResolver.java
jakrata-validation module also needs to fix

@seongahjo
Thanks. I will make PR ASAP 🙂


v1.15 Backports 2024-03-06

[x] #30928 (@giorio94)
[x] #30916 (@giorio94)

:information_source: Skipped the renovate-related commit, as not relevant in stable branches.

[ ] #31198 (@giorio94)

The last commit additionally switches the k8s version used for Ginkgo tests from quay.io/cilium/kindest-node:v1.29.0-rc.1 to kindest/node:v1.29.2.
Once this PR is merged, a GitHub action will update the labels of these PRs:
 30928 30916 31198

/test-backport-1.15

Conformance K8s Kind and Conformance K8s Upstream Network failures are expected, because they use the set-env-variables checked out from the target branch, which doesn't contain the additional variables. This will be fixed after merging this PR.

Marking as blocked to avoid merging while releases are in progress.

Releases are out, unblocking.


Fix infinite recursion bug when func raises AttributeError.

Please merge to master. I spent one day for finding the problem in python3.

Is the project dead?


QueueDeleteOptions

Could change to this
  pub struct QueueDeleteOptions {
        #[serde(default)]
        pub if_unused: Boolean,
        #[serde(default)]
        pub if_empty: Boolean,
        #[serde(default)]
        pub nowait: Boolean,
    }

I don't think this works, deleting the queue is not possible since the state of other consumers is unknown and there is no "if_not_empty". The only way to get a "queue" struct is by either declaring a new queue or deleting one.


All your hints are belong to us

In https://github.com/googlefonts/fontmake-rs/issues/33#issuecomment-1346920324 concerns about hints came up. It then became unclear what the existing fontmake tooling actually supports. Based on #33 and IM conversation I current believe that:

Glyphs can embed hinting information but fontmake wouldn't read or compile it
Tools exist to stick hints directly into the binary (or ttx), any outline edit would presumably invalidate the hints

@davelab6 noted "the hint byte code is turned into assembly in .TTX files, and can be read in a text editor; and fontforge provides a step debugger for TT assembly via FreeType."

People aspire to stick hint information into UFOs but fontmake might (TODO clarify) not read or compile it

See https://unifiedfontobject.org/versions/ufo3/lib.plist/#publictruetypeinstructions, https://unifiedfontobject.org/versions/ufo3/glyphs/glif/#publictruetypeinstructions.
https://github.com/googlefonts/ufo2ft/pull/654 aims to add fontmake support for ^

(will update as I learn more)

Glyphs can embed hinting information but fontmake wouldn't read or compile it

that's right, fontmake can not yet read nor compile Glyphs.app hinting, as glyhpsLib even crashes on them: https://github.com/googlefonts/glyphsLib/issues/817

People aspire to stick hint information into UFOs but fontmake might not read or compile it

correct, until ttps://github.com/googlefonts/ufo2ft/pull/654

Additional context courtesy of Adam:

The FontLab compiler from visual commands to binary is proprietary to FontLab. This works well for environments without subpixel rendering & VF.
The Glyphs compiler from visual commands to binary is proprietary to Glyphs. It's relatively lightweight set of visual commands that I think work with VF.
The VTT compiler was opemsourced by MS not so long ago, and that's the first (and good) piece of code that does the compilation.
But there isn't really any established way to store VTT visual commands in source formats (should be)
And there isn't any code to convert from the Glyphs visual commands or from the FontLab visual commands to VTT commands, but since both G & FL commands are kind of a subset of VTT, such converters could be made

Marc adds

gftools builder uses vttLib. We don't store the hinting info in the ufos since we also build glyphs files. Instead, the user provides a mapping which maps fonts to ttx files e.g https://github.com/wix/wixmadefor/blob/main/sources/config_text.yaml#L20-L36


DRAFT: Adapt konflux policy

Draft PR to check konflux pipeline execution.
This PR should only be merged once all Konflux checks pass.
Changes so far

Changed container base image to RH approved source (registry.access.redhat.com / ubi9).
Add container labels. Content can be finalized in follow up PRs.

/ok-to-test

/ok-to-test

/ok-to-test


FIxed issue #94

commit 62c4fcd4b5a446835333ebfc019ce89994036004
Author: Julian Krumow<EMAIL_ADDRESS>Date:   Fri Jul 24 22:53:34 2015 +0200
Changed usage of cocoapods plugin API which has changed in version 0.38.x

commit 0fc3de4bfc776a8e976ef8030b8adad0f7bd66a2
Author: Julian Krumow<EMAIL_ADDRESS>Date:   Fri Jul 24 22:29:00 2015 +0200
Revert.

commit e898a665f9bdf02a864f23410d00dfe5a89f0d5f
Author: Julian Krumow<EMAIL_ADDRESS>Date:   Fri Jul 24 22:28:24 2015 +0200
Push.

commit 2ea7b6a82d4ae56ab54d0083d3ba3a6d72e2d236
Author: Julian Krumow<EMAIL_ADDRESS>Date:   Fri Jul 24 22:23:33 2015 +0200
Update dependencies cocoapods and xcodeproj.

is anybody alive?

Good question. Not much happening here lately.

Works fine for me :+1: @eliperkins could you take a look and merge?

:ship: :ship: :ship:

Hello? Is anybody maintaining this repo?

I'm currently running into this too...

I really need this update. Should we consider using the fork, instead?

Can we merge this fix soon ?

:+1:

Cleaned up the commit message for clarity in #109. Thanks @tarbrain !


Update wskadmin with namespace related commands

wskadmin has user creation and deletion commands. With #1107 in place, we should also support namespace creation and deletion commands.

Is this feature available ?If yes, which build ?

Do you mean is wskadmin available already? If so yes it's in master/head in the bin directory.

No i meant the feature to create namespace to the wskadmin options

is it now possible to add multiple users in a namespace ? any documentation already available for using it ?

not yet - could be done after this pr #1681.


MDS graph isn't generated!

We are almost there! Its working now and looks good. But the MDS graph isn't generated. Could you please look into that?
Another issue is the the *.mds file should be saved as well, the race2 file and the merged mds race file. Thanks.
Also, please fill out the timesheet for all these hours you're working! I hope the internship is going well.

Gotcha! Will do 😊 these should be fixed now


Firestore uses the File timestamp APIs but has not provided a reason in the privacy manifest.

Description
I found that Firestore uses the stat function in the File timestamp APIs, please add reason for use in privacy manifest.
Reproducing the issue
No response
Firebase SDK Version
10.24.0
Xcode Version
15.2
Installation Method
Swift Package Manager
Firebase Product(s)
Firestore
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Hi @edisonlin77, Firestore does not directly use that API, but does depend on dependencies that do. Those dependencies have privacy manifests to justify the usage of the API, but the privacy manifests are not being evaluated by the App Store Connect validator. Let's continue the conversation in #12557.


Expose metadata field in add service and edit service pages

Related issue 2243
Before,

After focus out,

Loading ace and this is far more involved than I was thinking (and hundreds of KB) for a tiny feature...

@vincent99  agree!
Now it is a input-multiline

This looks pretty good but should default to empty, or empty object ({}), not null.  And the validation should check that the top-level value is an object, an array or literal ([1,2,3], false, etc) are not allowed because the field is map of string->json.

updated.
thanks a lot for your review!


Redirect to /linodes on delete

Closes #2120

Coverage increased (+0.01%) to 78.876% when pulling 82f60ce18ac76309b9557f76dfb802cb9e95a4b4 on eatonphil:redirect-on-linode-delete into 0d049c4499775015ff84ce1e9ef7d5111ffd0273 on linode:develop.

Still have to fix some weirdness going on here, sorry.

Coverage increased (+0.1%) to 78.393% when pulling 83d2d7f2c0ea0515d8362fa0e33dda11007b49c5 on eatonphil:redirect-on-linode-delete into e4f8c4d028f0f965c3711bb26dfa2ed4c32c5a9c on linode:develop.

thanks!


build: bundle extension (>40 MB -> 26 MB)

resolves microsoft's warnings that it spits out when you vsce pack an unbundled extension:
https://aka.ms/vscode-bundle-extension

Hi,
I missed this, I will need to test it. Although one of the reasons I do not bundle it is so anyone can inspect the code. Thoughts? @llllvvuu

Ah good point! I always worry about any type of MITM attack.


CA issue to reach files.pythonhosted.org

Hi,
Stumbled on this when trying to install "requests" with pip 18.0.
It retries 5 times with failing certificate and ending with:
pip._vendor.requests.exceptions.SSLError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Max retries exceeded with url: /packages/65/47/7e02164a2a3db50ed6d8a6ab1d6d60b69c4c3fdf57a284257925dfc12bda/requests-2.19.1-py2.py3-none-any.whl (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833)'),))

This is indeed CA certificate error as my system does not have any CISCO umbrella Root CA...
My system does not have this CA and even with firefox on https://files.pythonhosted.org/ I get blocked with "SEC_ERROR_UNKNOWN_ISSUER".
Is this me or is this hosting issue ?
* TCP_NODELAY set
* Connected to files.pythonhosted.org (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* stopped the pause stream!
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

TLS Debug
IPv4
echo -n | openssl s_client -4 -connect files.pythonhosted.org:443
depth=2 CN = Cisco Umbrella Primary SubCA, O = Cisco
verify error:num=20:unable to get local issuer certificate
CONNECTED(00000003)
---
Certificate chain
 0 s:/C=US/ST=California/L=San Francisco/O=OpenDNS, Inc./CN=*.opendns.com
   i:/CN=Cisco Umbrella Secondary SubCA lon-SG/O=Cisco
 1 s:/CN=Cisco Umbrella Secondary SubCA lon-SG/O=Cisco
   i:/CN=Cisco Umbrella Primary SubCA/O=Cisco
 2 s:/CN=Cisco Umbrella Primary SubCA/O=Cisco
   i:/O=Cisco/CN=Cisco Umbrella Root CA
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIDRDCCAiygAwIBAgIEA6AkGzANBgkqhkiG9w0BAQsFADBAMS4wLAYDVQQDDCVD
aXNjbyBVbWJyZWxsYSBTZWNvbmRhcnkgU3ViQ0EgbG9uLVNHMQ4wDAYDVQQKDAVD
aXNjbzAeFw0xODA4MTMyMTU0MjFaFw0xODA4MTgyMTU0MjFaMGoxCzAJBgNVBAYT
AlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1TYW4gRnJhbmNpc2Nv
MRYwFAYDVQQKDA1PcGVuRE5TLCBJbmMuMRYwFAYDVQQDDA0qLm9wZW5kbnMuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAow68Z4xuZS8kmrH9bnco
p4K2lpz3P2RuVuvTXWmjGx+bIVZtEHqoi3jxMEUEoeBdPWzgKctUZWWZue14hfaY
0P4zO0L0r/IL4I2oAmX6hegd5mhmiEqi3quzk9zkc9CYCInQUEys8WQn5USNpr+N
Tt9584aJnIVOTgeg5uEp7anJyrMk/EhtxmA/YYaYWoFYewpkVEKx2y1DjqONqHGP
98L4aC2jGbTgP7q0Ugj73o5/wcVAdshNvT210gFfW+NRZVW2ll8zyyPQB8kLvNrZ
1udEL/xjZrihi7Sp4sdhjuGgp64VDWXTl/FBk/adhY8y085Tb0w3O7jpyzcllPfZ
cwIDAQABoxwwGjAYBgNVHREEETAPgg0qLm9wZW5kbnMuY29tMA0GCSqGSIb3DQEB
CwUAA4IBAQBS8I8wP4JrAncDch5/KadQYG3FIbG1b0nalS/ijOINEPw8zkraHuve
jZaiRIM8lnPXKeOl9R2lXAj2bQqY3nvnexFTJ8FQ6q+1wvKbr5diaOzvzDsIMsIG
zlxtXLq13YQdJrU67VhayXOI05aJ+7F6VmIzSLRpfA0rgx+ZSkxZc5CcVTtTgmiE
AlQLkte6SpM1yVAhqgsOLV8FEANqoGZaM/Rrb9W7daG6DPc0Miw5/Eb7FzsWA2+0
aUXgz28moru/Iq14snH/5JC8Ie++F+Caow3ts/BIXxxUvr2A9qdijjOUMGnWKi0x
X+sU+uwuw4XnKEyd3i9ZmgPpv8vC9h7E
-----END CERTIFICATE-----
subject=/C=US/ST=California/L=San Francisco/O=OpenDNS, Inc./CN=*.opendns.com
issuer=/CN=Cisco Umbrella Secondary SubCA lon-SG/O=Cisco
---
No client certificate CA names sent
---
SSL handshake has read 3303 bytes and written 494 bytes
Verification error: unable to get local issuer certificate
---
New, TLSv1.2, Cipher is AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : AES256-GCM-SHA384
    Session-ID: AED70343CE251C645E91BB481E0B06D17171B6907E1DDCB6B5F8C23E9C91E0CD
    Session-ID-ctx:
    Master-Key: 0ADF814185D4AFB53666E9C90C595FCD6DDF553CD8BC867D2577666DEBAEA49ABF634D4A262F2CC3DB6942FF22F36D33
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - 4b b8 51 09 95 9b e5 a0-e0 bc c0 a8 8c 5b 9c b2   K.Q..........[..
    0010 - 34 5d 8e 10 38 ab 6f b0-2f 7e 16 cd 3e d3 29 0a   4]..8.o./~..>.).
    0020 - ad d7 21 6c f2 96 1f 02-82 34 77 11 33 2b 83 7d   ..!l.....4w.3+.}
    0030 - 82 d8 f8 13 16 a9 dc 96-d4 57 9c 6c be e8 76 03   .........W.l..v.
    0040 - fb f3 6a 55 3d 07 75 9b-2a 9c 6e 0a 41 aa 8a ff   ..jU=.u.*.n.A...
    0050 - e8 2d 05 4f 64 99 57 54-d2 07 2e f0 b8 be 46 66   .-.Od.WT......Ff
    0060 - 66 60 d4 15 42 13 b1 69-12 97 3e ba cc ed b0 ce   f`..B..i..>.....
    0070 - a6 da fb a3 f8 5b 01 1a-6e 83 ab 3f dc 35 3e 91   .....[..n..?.5>.
    0080 - 2e c5 2a b4 f9 a3 35 44-d4 7e 6a 08 7e b5 3c 62   ..*...5D.~j.~.<b
    0090 - cc 11 61 37 a2 91 cb e4-d9 73 3a 67 2e 28 a4 8a   ..a7.....s:g.(..

    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 20 (unable to get local issuer certificate)
    Extended master secret: no
---
DONE

This appears to be a Corporate Firewall or Proxy, pypi.org's certificate is issued from the DigiCert root CA and files.pythonhosted.org's certificate is issued from the. GlobalSign Root CA.
You should work with your ISP or Corporate IT department to determine what is intercepting this request.

Additionally, it appears your DNS is being intercepted as files.pythonhosted.org is a CNAME to dualstack.r.ssl.global.fastly.net

I see, thanks a lot.
So it is indeed me...


Unspecific error message after branch name change

Forge CLI Version: 1.1.0
PHP Version: 7.4.20

Description:
An unexpected error occured. Please report this issue here:
  https://github.com/laravel/forge-cli/issues/new/choose

  - Forge CLI Version: 1.1.0
  - PHP Version: 7.4.20
  - Operating System: Darwin
  - Error Message: Failed to deploy. Please refresh the tokens in your Forge profile..

Steps To Reproduce:
Change the branch name on Github without updating the branch name at Forge, then try to deploy. The error message could if possible be more specific rather than Please refresh the tokens in your Forge profile...

You are right. We are going to address this on the Forge API side.


python3Packages.quadprog: init at 0.1.11

Description of changes
Quadratic Programming Solver.
https://github.com/quadprog/quadprog
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build python3Packages.quadprog

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1651


netcoreapp vs netstandard story

Can I check what happens with netstandard assemblies with tests that are used in an entrypoint netcoreapp?
It looks like you are running tests using the adapters app?
If you look at the story here for xunit it gets complicated:
https://twitter.com/ExpectoIO/status/953194299872735233

Deleting my previous comment with a test repo, as I now realize the repo is not properly configured to test this issue.


refactor: remove redundant falsy provider check from Contract

Closes #769
Test coverage is not required here as getBalance() gets covered in #760

Closing as will cherry-pick single commit and will recreate PR


Twenty-sixth Community Call

Next call will be on Tue May 18th at 6pm CET (1600 UTC, 12pm EDT, 9am PDT). We will aim to include more projects from America this time. From 2021, we will have monthly community calls, every 3rd Tuesday of the month, alternating times. (Jan/Mar/May/Jul/Sep/ Nov at a more America-friendly time - 6pm CET and Feb/Apr/Jun/Aug/Oct/Dec at 10am CET)
Agenda:

1.0 RFC release (wasmd 0.16 / cosmwasm 0.14)
CosmJS 0.25
CosmWasm testnet
Open Q&A

Zoom link: https://zoom.us/j/361222561?pwd=ZmpIQUppYks2MDVtSjRGQVpTaVlKUT09
(This is same for all meetings at America-friendly times)

The video recording is now online: https://vimeo.com/552027920


MIECD UAT Issues #1

Logface View

[x] For pregnancy registration (DKY) messages, when the risk category is NOT SET, simply leave it as GREY text without any box/border.  It should be greyed out, to show that it is not a categorization.

[x] Risk categorization should be clickable and should take the user to the patient view.On click of the risk category, there should be a link to open the patient view.

[x] In the logface remove SMS ID column

[x] The Back in Compartment takes the user back to the very first compartment page . This should take you back to the previous page.

Compartments View

[x] Within the compartments, change the category risk colors from orange to yellow

[x] At the end of the locations disaggregation(All the way to the commune), if there is no patient to show in the log the village level, display there is no patient in this record instead of leaving it empty.

[x] Within the compartment, the total should be clickable , and should follow similar actions to the risk categorizations. This means the total column should be highlighted and on click, the locations show according to the hierarchy

[x] In the compartment table, the area for clicking should be bigger as people are not always specific with clicking just the name of the location.  This means the whole row should be clickable.

[x] In Compartments, have the card that contains delivery due in one week to come before the deliveries due in 2 weeks. Preferred changes are to have the card with the 1 week first, then the 2 weeks, and then totals. Make the font bigger, and circles bigger. The circles should be clickable. Logface and compartments are both hard to see due to the size. Make the font size bigger. Consider having compartments (Total, 1 week, 2 weeks) broken down into 2 rows.

@hmakandi, I'm going to split this issue into smaller issues in order to be able to more easily  make smaller PRs.

This is ok. Thanks @FrankApiyo

Closed the main issue and the child issues.