Fix for issue #746

This fixes issue #746. The only issue i see with this is that it's important you back up the configuration files as there is no way to get the private key outside of just copying the file. The public key may be requested from the sasl module at any time.

May you follow codestyle around?

Would you care to elaborate? I couldn't find a code style document on the wiki, and I've tried to make it as similar as possible to before the DH-BLOWFISH module was removed.

I am not sure if I understand the pr message.

The only issue i see with this is that it's important you back up the configuration files as there is no way to get the private key outside of just copying the file

If I understand correctly, ZNC generates the key and stores it to ~/.znc/configs/znc.conf and these both seem weird to me. Shouldn't the key be generated outside of ZNC and be uploaded with webadmin like *cert and then be stored to similar path which *cert does.
I am not a coder and this is just how I read the quoted section.

Start with squashing the commits (eg. git rebase -i origin/master if origin is the upstream remote) and then:
pick de99fc4 Allows use of ECDSA-NIST256P-CHALLENGE for sasl
f b62350a Added ifdefs so can be built without ssl
f 55677ed Changed to use .pem files instead of fmemopen
f 9c968c9 fixed memory leak, minor whitespace cleanup

to make it a single commit. Once you have a single commit, if you want to make further amendments, you can simply do git commit --amend. Then pass --forcewhen pushing to update the PR.

It actually writes it to ~/.znc/users/[user]/networks/[network]/moddata/sasl/sasl.pem
It used to store it in the .registery file in that same directory, but since fmemopen isn't supported on osx I had to change it to write it out to its own separate file. The point is that there is no command to print the private key (even though it'd not be a very long string either base64 or hex encoded). It's not signed or anything like that so there isn't really a reason to need to use a separate tool to generate the key. The format of the output file is because other ways of getting the key into and out of openssl are very painful.

Also, a descriptive commit title would be nice. "Fix for issue #746" doesn't tell much when browsing the git history. :)

It actually writes it to ~/.znc/users/[user]/networks/[network]/moddata/sasl/sasl.pem

What if there will be another method which uses some kind of certificate file? Maybe the filename should be something like ecdsa.pem or similar.
Can I upload my self-generated key from elsewhere (another client) to ZNC if I don't have access to the OS meaning webadmin?

All the code around uses something like hungarian notation for variables, e.g. bFoo for bool, m_ for member fields.

Has anything changed? There seems to be commit after the comments.

Github does not notify about new comments

@Mikaela And I don't see anything fixed in the new commit anyway.

Github does not notify about new commits

That is why I commented.

@Mikaela And I don't see anything fixed in the new commit anyway.

ok.

And this mechanism isn't needed anymore, see #746 for details.

https://github.com/znc/znc/issues/746#issuecomment-119274435 to be accurate.


import of C++ module 'CoreGraphics' appears within extern "C" language linkage specification

On Xcode15, import of C++ module 'CoreGraphics' appears within extern "C" language linkage specification

This is a duplicate of this issues: https://github.com/adamwulf/ClippingBezier/issues/31
Which is fixed but there hasn't been releases cut for Cocoapods etc... yet I don't think.
@adamwulf Do you think you could create a release containing the fix for the different package delivery mechanisms please? Or is that something we can help with?

I've just pushed up 1.2.4 that includes the necessary version bump in the podspec file, and i've also pushed to cocoapods too, so everything should be good to go. lmk if you run into issues, thanks!

thanks! 🎉


Page hierarchy explorer doesn't always select

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Steps:

build Toolpad yarn && yarn release:build
start Toolpad dev on the basic backend fixture: yarn toolpad dev test/integration/backend-basic/fixture
open the "basic" page
try selecting items in the page hierarchy explorer

Current behavior 😯

It doesn't always select the item (see video)
hovering over page rows doesn't highlight them
the title "components" is very ambiguous. Components for me are like templates, they are blueprints. When they're instantiated on the page I prefer to talk about nodes, or elements.

https://github.com/mui/mui-toolpad/assets/2109932/89208dd8-5a26-43ec-9927-36651b9b380a
Expected behavior 🤔

It always selects the node when I click it
hovering over page rows highlights the node in the canvas
I propose we change the title to "page hierarchy"

Context 🔦
No response
Your environment 🌎
No response

@Janpot Is there any additional information you could share? Context/Browser/error messages in the console? I can't replicate 1. without those.
https://github.com/mui/mui-toolpad/assets/19550456/2b9e58fb-2d79-430f-b40b-7239b293c1b3
Agree, I'll make changes for 2. and 3.

Yes, it seems to happen when I click the text itself, or the vertical center in the whitespace left of the text, basically anything in this area:

I also updated the issue with 4. and 5. that I ran into.

On 3., "Components" makes sense to me given that :

We call the catalog which contains them the "Component Library"

Benchmarking:

Appsmith
Dynaboard
Retool

The title of the section that shows the tree is the same as the entity which you drag on to the page - So "add new widget" translates to a "Widgets" explorer; similar for Retool and Dynaboard

Adding a new term for a component when instantiated on the page seems like an unnecessary complication

Adding a new term for a component when instantiated on the page seems like an unnecessary complication

The distinction between "template" and "instance" is a very natural one for programmers:

a class vs. an object
a React component vs. a jsx element

Adding a new term for a component when instantiated on the page seems like an unnecessary complication

The distinction between "template" and "instance" is a very natural one for programmers:

a class vs. an object
a React component vs. a jsx element

Updated the title to say "Page Hierarchy"

A code component currently comes without any icon, let's use the icon that we are using in the Component library.


pls release

think we should have a release from master... https://tools.ietf.org/html/rfc5424 support can wait for next release

you should update the release date in CHANGES.md for 0.0.2 (it is "now" atm)

Thanks for the hint. I'll also need to fix the README to play nice with Topkg, when building the description for the OPAM repo.

thx!


Got prusto building with nightly-2021-04-18

It wanted the min_type_alias_impl_trait feature enabled.

@bitemyapp why is this necessary?


Adds customisable CallbackUrl

Solves issue where the library is run within a Docker container.
When inside of a container, it will attempt to (correct) bind to the eth0 interface on the docker0 bridge (<IP_ADDRESS>/16). This will result in a non routable callback url being sent to Marathon. This change gives user the ability to specify a custom endpoint, failing back to the original method.

Updated to meet code style

:+1: ... merging


Add missing paren

Description
Fixes the formatting issue with the link in this comment: https://github.com/conda-forge/jupyter_core-feedstock/pull/99#issuecomment-2389346240

Oops meant to file upstream 🤦♂
Sent in PR: https://github.com/conda-forge/conda-forge-webservices/pull/722


Namespace to Gateway - Gateways list and details are slow to load elements

API Services Portal Issue
User Story
As a API provider on the Portal,
I want page elements to consistently load quickly AND use appropriately sized skeletons during loading
so that I don't need to wait or end up clicking the wrong element when the page jumps.
Slow loads include:

Gateway display names in the My Gateways list

Gateway details

It's possible the slower loads are limited to dev/test, but regardless, appropriately sized skeletons would improve UX when page loads.
Test Case
ENV

[X] DEV
[X] TEST
[ ] PROD

TESTCASE
Open the page (/list or /details)
EXPECTED

First: Skeletons are sized to fill the loading page elements. Page does not shift when elements load.
Secondary: Loading all page elements takes less than X seconds (1 s? 0.5 s?)

ACTUAL

Loading display names (on /list) or the current Gateway details in header (on /details) often has a noticeable delay
Page jumps when these elements load and fill space

I couldn't find the logic for the skeletons in the codebase. Would you like to discuss what the skeletons should look like? I can make some quick mockups if it would be helpful.

<Skeleton> is used throughout the Portal for loading elements and can be seen e.g. on the /detail page:

In that case, it just needs resizing in the props. It comes straight from Chakra - https://v1.chakra-ui.com/docs/components/feedback/skeleton

Thanks, with regard to sizing and to avoid layout shift, I was thinking of using separate Skeletons. Something like this:

Priority: improving UX for our services


add gops dependency and utilize it in Cilium agent

Add support for getting stack traces of the Cilium agent with gops, a profiling tool from Google.
Partially address #1637
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This doesn't build. You seem to have forgotten to vendor gops.


Significantly slower ModMenu processing on 0.18.x betas compared to 0.17.8

MC 1.19.2
Quilt Loader 0.18.x
Not sure exactly which version introduced the slowdown (at least beta 27 and above, but probably earlier), I don't recall noticing it before, but right now, whenever I open mod menu on 0.18.x, I get a 26sec stutter before it opens, as opposed to just 6sec on 0.17.8 (in a modpack, I'm not sure you would notice the difference with just a few mods or no mods at all). I've been investigating this issue for a while, trying all sorts of settings in ModMenu itself, compact mode, hiding unnecessary mods/libraries, etc, but it turned out to be caused by QL 0.18.x, as 0.17.x doesn't have the same issue.
Again, not sure if logs are going to be of any use:
0.17.8: https://gist.github.com/SplendidAlakey/c90e9a25b7dcc72d79440eee314e5be0#file-stable_latest-log (38:06 mark is when I click on mod menu, 38:12 is when it opens)
0.18.1-beta.28: https://gist.github.com/SplendidAlakey/c90e9a25b7dcc72d79440eee314e5be0#file-beta_latest-log (28:15 mark is when I click on mod menu, 28:41 is when it opens)
Edit: just tried practically the same pack on Fabric and it only takes 2sec to open mod menu, so something on Quilt's side is slowing it down in general.

Can you try creating a profiler snapshot in the same way as you did before, but this time only starting the profiler before you click on the "Mods" button and stopping the profiler after the window opens? That way we can see what part of quilt is causing the problem.

There you go: snapshot_beta28_modmenu.zip

Thanks! It looks like it's spending a lot of time converting quilt metadata to fabric metadata, so I'll cache that.

Completely fixed on beta 41, thank you! Now takes only 2sec to open the mod menu, just like on Fabric.


Static files delivered by externalStaticFileLocation are only accessible with 1 service started after 2.5.1

Hello!
This issue affects all versions after 2.5.1 (before the security fix...).
Consider the following code:
        Service server1 = Service.ignite().port(8080);
        Service server2 = Service.ignite().port(8181);

        server1.externalStaticFileLocation(Paths.get("folder1").toAbsolutePath().toString());
        server2.externalStaticFileLocation(Paths.get("folder2").toAbsolutePath().toString());

with inside folder1 and folder2 a file "image.jpg".
If you visit http://localhost:8080/image.jpg (server1) => 404
If you visit http://localhost:8181/image.jpg (server2) => 200
If you put in comment the server2, the image from server1 is now accessible!
If you want something to quickly test it, I made a Github repository with my examples:
https://github.com/sandronm/sparkjava_example
What's wrong?

#727

Hello guy's,
I found the origin of the bug in your code: the class StaticFilesFolder
public class StaticFilesFolder {
    private static final Logger LOG = LoggerFactory.getLogger(StaticFilesFolder.class);

    private **static** volatile String local;
    private **static** volatile String external;

    public **static** final void localConfiguredTo(String folder) {

        local = removeLeadingAndTrailingSlashesFrom(folder);
    }

    public **static** final void externalConfiguredTo(String folder) {

        String unixLikeFolder = Paths.get(folder).toAbsolutePath().toString().replace("\\", "/");
        LOG.warn("Registering external static files folder [{}] as [{}].", folder, unixLikeFolder);
        external = removeLeadingAndTrailingSlashesFrom(unixLikeFolder);
    }

    public **static** final String local() {
        return local;
    }

    public **static** final String external() {
        return external;
    }

}

The class should not use static variables and methods because if you do that, you can only define 1 external static files path by JVM and not by Service as expected.
You should instead create a single instance of StaticFileFolder by Service (Singleton pattern).

I'm taking a look at this, but I'm not quite getting what's the deal with all the statics - seems like running from servlet, stuff is supposed to be static and otherwise not. This seems to be the case with routes as well. @perwendel | @tipsy am I on the right track here, is this by design?

am I on the right track here, is this by design?
Spark used to be entirely static (no instance api), so it might just be legacy code.

this is still the case at 2.7.1
    Service s1 = Service.ignite().port(4568).staticFileLocation("/s1");
    Service s2 = Service.ignite().port(4569).staticFileLocation("/s2");

    s1.init();
    s2.init();

curl -v http://localhost:4568/s1.txt ends up being 400 bad request


how to use COMClassInfo with c++?

I ran remote hook using EasyHook (hook Beep() in Tutorials )with C++ successful.
Then I want to hook a com interface. But when i create a COMClassInfo object : COMClassInfo cci1 = new COMClassInfo(typeof(CLSID_DirectInputDevice8), typeof(IID_IDirectInputDevice8W), "GetCapabilities");
It failed : undeclared identifier COMClassInfo . I have already included "easyhook.h"
environment： easyhook v2.7.6270.0 , vs2017 ,win10 64

COMClassInfo is only available in the managed library. If you want to use that you will need to implement within C#


Lecture 8: Single-use property of streams

Description
I would like to understand why Java Streams are single-use by design (once the elements are iterated, they cannot be used again).
Is there a way to 'clone' an unused stream to avoid duplication of code?

Of course, just like slide 9 of this week's lecture, you can put them inside a function!

To "copy" or "clone" a stream, you can try storing it as a List and then convert it back to stream when you want to use it. Not sure if this is a good design but if you really want to copy or clone, this is a way to do it.
For example, using .toList() to convert an int stream to list.
List list = stream.collect(Collectors.toList());
then use flatMapToInt() to convert list of integers back to IntStream.
list.stream().flatMapToInt(IntStream::of);

Ok thanks, I got it now.


Make HAL enums DRYer

Rename variants in HALUsageReporting::tResourceType to not have a kResourceType_ prefix.  This drops the concat_idents requirement for resource_type!.
Rename variants in a couple of HAL enums to drop the enum name prefix.
Re-export the usage reporting modules in wpilib_sys::usage with friendlier names.

Wonder whether it'd be better to directly generate the usage reporting constants. Would have even more flexibility there.

Sorry for being late, I was on vacation for a while.
For the record, here's a diff of the bindings output.
diff --git a/src/hal_bindings.rs b/HAL_BINDINGS_NEW.rs
index 06cf8b0..3c64f82 100644
--- a/src/hal_bindings.rs
+++ b/HAL_BINDINGS_NEW.rs
@@ -124,9 +124,9 @@ pub type HAL_Bool = i32;
 pub mod HAL_AccelerometerRange {
     /// The acceptable accelerometer ranges.
     pub type Type = i32;
-    pub const HAL_AccelerometerRange_k2G: Type = 0;
-    pub const HAL_AccelerometerRange_k4G: Type = 1;
-    pub const HAL_AccelerometerRange_k8G: Type = 2;
+    pub const k2G: Type = 0;
+    pub const k4G: Type = 1;
+    pub const k8G: Type = 2;
 }
 extern "C" {
     /// Sets the accelerometer to active or standby mode.
@@ -1515,12 +1515,12 @@ impl HAL_ControlWord {
 }
 pub mod HAL_AllianceStationID {
     pub type Type = i32;
-    pub const HAL_AllianceStationID_kRed1: Type = 0;
-    pub const HAL_AllianceStationID_kRed2: Type = 1;
-    pub const HAL_AllianceStationID_kRed3: Type = 2;
-    pub const HAL_AllianceStationID_kBlue1: Type = 3;
-    pub const HAL_AllianceStationID_kBlue2: Type = 4;
-    pub const HAL_AllianceStationID_kBlue3: Type = 5;
+    pub const kRed1: Type = 0;
+    pub const kRed2: Type = 1;
+    pub const kRed3: Type = 2;
+    pub const kBlue1: Type = 3;
+    pub const kBlue2: Type = 4;
+    pub const kBlue3: Type = 5;
 }
 pub mod HAL_MatchType {
     pub type Type = i32;
@@ -3104,10 +3104,10 @@ pub mod HAL_SerialPort {
     /// @ingroup hal_capi
     /// @{
     pub type Type = i32;
-    pub const HAL_SerialPort_Onboard: Type = 0;
-    pub const HAL_SerialPort_MXP: Type = 1;
-    pub const HAL_SerialPort_USB1: Type = 2;
-    pub const HAL_SerialPort_USB2: Type = 3;
+    pub const Onboard: Type = 0;
+    pub const MXP: Type = 1;
+    pub const USB1: Type = 2;
+    pub const USB2: Type = 3;
 }
 extern "C" {
     /// Initializes a serial port.
@@ -3405,88 +3405,88 @@ extern "C" {
 }
 pub mod HALUsageReporting_tResourceType {
     pub type Type = u32;
-    pub const kResourceType_Controller: Type = 0;
-    pub const kResourceType_Module: Type = 1;
-    pub const kResourceType_Language: Type = 2;
-    pub const kResourceType_CANPlugin: Type = 3;
-    pub const kResourceType_Accelerometer: Type = 4;
-    pub const kResourceType_ADXL345: Type = 5;
-    pub const kResourceType_AnalogChannel: Type = 6;
-    pub const kResourceType_AnalogTrigger: Type = 7;
-    pub const kResourceType_AnalogTriggerOutput: Type = 8;
-    pub const kResourceType_CANJaguar: Type = 9;
-    pub const kResourceType_Compressor: Type = 10;
...
+    pub const Controller: Type = 0;
+    pub const Module: Type = 1;
+    pub const Language: Type = 2;
+    pub const CANPlugin: Type = 3;
+    pub const Accelerometer: Type = 4;
+    pub const ADXL345: Type = 5;
+    pub const AnalogChannel: Type = 6;
+    pub const AnalogTrigger: Type = 7;
+    pub const AnalogTriggerOutput: Type = 8;
+    pub const CANJaguar: Type = 9;
+    pub const Compressor: Type = 10;
...
 }
 pub mod HALUsageReporting_tInstances {
     pub type Type = u32;

I'm on board with that. I'll merge this real quick.


Network mode Exposed Ports

While in network mode, it's moot to append the ports to use as well in the docker command/compose since it's already in host mode. It runs fine as is, but it gives the misconception of what host mode is and that those port variables are required.

Fixed README.md, thank you!


Make effective against all U.S. government employees, not just agencies

The language would not have included federal employees other than those of the executive branch due to use of the word "agency."  That is, an assistant to a member of Congress or the court clerk of a federal judge do not work for an "agency," but do work for the federal government.  The changes expand the definition of who is covered.
Jonathan Corbett
<EMAIL_ADDRESS>

LOL.  How many "United States federal governments" are there anyway?
Line 10 says "on behalf of a United States federal government".  Probably intended "on behalf of the United States federal government".  The "a" got missed when "agency" was removed.

@mMerlin Adjusted to address your feedback.

I feel like this could be too extensive, since this could include a group that has received a grant from the U.S. government.

What about state/federal university employees? I am new to the subject matter. Can someone please break-down in lamens terms why there exists two different documents?

@mancoast, I believe that the relevant piece is the unchanged line 16.  The specified people have additional constraints on what they can and must do.  I (just me, no background) would expect that those additional clauses would apply whether they were explicitly included or not.  This is just a reminder that they are not playing in their own sandbox.  Standard verbiage that basically says follow the rules that are already in place.  That using the system does not excuse them from existing agreements.

There are legislative agencies and judicial agencies. The use of "agency" doesn't exclude non-executive branch agencies.

The service is being adopted widely, and any inconvenience due to confusion may limit contributions to public domain.  Please be careful to prevent interference with students that kindly offer their work on github.

Thanks, @jcorbett-tandent and everyone else who made suggestions here!
We agree, and we're revising this language. We should have an updated PR up shortly. I'm going to go on and close this PR — again, thank you for calling our attention to it!


Parsing fails on multiline string with comments and newlines

I can't put my finger on this exactly, but it seems that the parser gets confused by certain combinations of multiline strings with comments.
For example:
toml.loads('a = """#\n"""#')

returns {}
while it should return {"a": "#\n"}
May be related to #152.

Thank you for the bug report!
Your example appears to be equivalent to the following toml document:
a = """#
"""#

Is this correct?
This appears to be an issue of combining # and newlines in the same multiline string.

Yes I agree. That is the TOML document I'm talking about.
Indeed it looks like certain combinations do not work well inside the multiline string.
Note however that the second comment (immediately after the multiline string) is also necessary to trigger the problem. That puzzles me.

This issues is due to '# ' or any chracter (e.g. space )just after """. The check for """ is done on the non stripped version of the line.
is replace by a space during a preprocessing and later the space is not removed when operating on multistring.


clean up some stdlib unittest warnings

Thanks for these, @brettkoonce!
@swift-ci Please smoke test

Can one of the admins verify this patch?

@swift-ci smoke test and merge

⛵


Merge 11-14 (2) to live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/add-cut-paste-methods-page-object-multipage-control-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/addcontrol-event-add-method-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/alignment-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/autosize-multiline-wordwrap-scrollbars-properties-textbox-control-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/backcolor-backstyle-bordercolor-borderstyle-forecolor-specialeffect-properties-e.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/canundo-canredo-properties-undoaction-redoaction-methods-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/checkbox-control-enabled-locked-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/click-event-commandbutton-control-accelerator-caption-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/combobox-control-additem-method-picture-pictureposition-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/copy-getfromclipboard-gettext-methods-dataobject-object-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/count-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/cut-paste-methods-textbox-control-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/cycle-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/dblclick-event-canpaste-property-paste-copy-methods-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/dragbehavior-enterfieldbehavior-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/dropdown-method-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/enabled-enterfieldbehavior-sellength-selstart-seltext-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/enter-exit-events-activecontrol-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/enterkeybehavior-multiline-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/font-object-bold-italic-size-strikethrough-underline-weight-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/getformat-gettext-settext-methods-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/groupname-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/height-width-left-top-clientheight-clientwidth-clientleft-clienttop-properties-t.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/index-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/insideheight-insidewidth-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/item-method-optionbutton-control-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/keydown-event-textbox-control-curline-curtargetx-curx-text-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/keypress-event-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/largechange-smallchange-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/layout-event-layouteffect-property-move-method-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/layout-event-oldleft-oldtop-oldheight-oldwidth-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-additem-removeitem-methods-listindex-listcount-properties-exampl.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-boundcolumn-controlsource-rowsource-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-boundcolumn-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-column-columncount-list-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-columncount-columnwidths-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-dataobject-object-mousemove-event-startdrag-settext-methods-exam.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listbox-control-list-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listrows-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/liststyle-multiselect-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/listwidth-property-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/locked-dropbuttonstyle-showdropbuttonwhen-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/matchentry-property-optionbutton-control-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/matchfound-matchrequired-properties-change-event-checkbox-control-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/max-min-maxlength-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/max-min-zoom-properties-frame-scrollbar-controls-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/mouseicon-mousepointer-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/move-method-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/multiselect-selected-properties-example.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/page-object-commandbutton-multipage-controls-controltiptext-property-example.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


List.of and similar methods should be specialized based on the context

There is an expectation that these two methods:
@pragma('vm:prefer-inline')
@pragma('dart2js:tryInline')
List<Object?> _copy1(List<Object?> array) {
  final List<Object?> clone = List<Object?>.filled(array.length, null);
  for (int j = 0; j < array.length; j++) {
    clone[j] = array[j];
  }
  return clone;
}

@pragma('vm:prefer-inline')
@pragma('dart2js:tryInline')
List<Object?> _copy2(List<Object?> array) {
  return List<Object?>.of(array, growable: false);
}

should have similar performance. Unfortunately this is not the case - List.of remains a call and resulting code is 20-50% slower even if TFA infers that array is always a fixed length list.
We should be able to specialise List.of into a fast (inlined) list copy if we know the type of the argument.
It might be good to figure out generic framework for such optimisations.
/cc @alexmarkov

looks like a typo in line 8   return clone; List<Object?>.of(array, growable: false);

@aam fixed thanks.

When I was working on making list splices smaller and faster, I noticed that AOT compiler gives up trying to inline too easily.
What would likely be best is if _copy was inlined several levels and then left as a call to _List._ofArray.
The inliner clones and simplifies List.of because it is called with one of the arguments bound to a constant.
  factory List.of(Iterable<E> elements, {bool growable: true}) {
    if (growable) {
      return _GrowableList.of(elements);
    } else {
      return _List.of(elements);
    }
  }

This simplifies to a single call, one with fewer arguments, but IsSmallLeaf rejects any result that has a static call that is not marked as 'prefer-inline'. What it should do is accept a simple reduction of one call to another provided the number of arguments does not increase.
I tried two ways of fixing this, but neither was successful.
The first way was to make IsSmallLeaf more accepting of inlining calls-to-calls.
The call to List.of was replaced with a call to _List.of.
But _List.of was never inlined at the next level.
I suspect that the propagation of facts into the inlined code was inadequate as other passes do not run between levels of the 'inlining tree'. TFA results for the call sites inside the inlinee are too imprecise, so there needs to be some non-feedback way of refining the results.
The second way was to add a transform to replace List.of with _List.of with _List.of or _GrowableList.of, like the other List constructors .
(I dislike these transforms since they change the call stack that the programmer sees - List.of, what they called, is nowhere to be seen. I think all the constructors should be written in the style of List.of and inlined. Then these transforms should be removed (after possibly fixing TFA to be aware of the growable: arguments.))
The transform did not work out well, since replacing List.of with _List.of removed one call, but not the expensive one.
AOT refused to inline _List.of because of https://github.com/dart-lang/sdk/issues/48207.
It learned that sometimes there is no benefit, so it disabled inlining permanently.
While impact analysis could be helpful, cases like this where the function dispatches to other functions could be handled by not making a permanent decision below a higher threshold. The threshold could be a function of the shape of the CFG - many similar sized functions have no chance of getting smaller and that is 'obvious'.
Occasionally the first few calls to _List.of were beneficial and were inlined before inlining was disabled permanently.
The result then was disappointing code size, since the call to _List._ofArray was also inlined because the body of _List._ofArray has no calls.
I think this could be prevented by marking static calls as the result of size-conscious inlining - the inlining heuristic (IsSmallLeaf) should be very strict for marked calls.

Based on conversation with @alexmarkov: one possible path forward with this would be to introduce another pragma (vm:prefer-inline-if-concrete-types-known?) along the lines of vm:prefer-inline/vm:never-inline so it can drive more aggressive inlining in presence of known concrete types for method parameters. Then use that pragma on _List.of and others that specialize based on argument type(_List.setRange ?)


Error: Trimap did not contain foreground values

failing out while removing background image
uname -a
5.8.0-3-amd64 #1 SMP Debian 5.8.14-1~mx19+2 (2020-10-25) x86_64 GNU/Linux

backgroundremover -i ./final_sign.jpeg -a  -ae 15 -o final_sig4.png

final_sig4.png
[W NNPACK.cpp:80] Could not initialize NNPACK! Reason: Unsupported hardware.
Traceback (most recent call last):
  File "/home/xyz/.asdf/installs/python/3.8.0/bin/backgroundremover", line 8, in <module>
    sys.exit(main())
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/backgroundremover/cmd/cli.py", line 241, in main
    remove(
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/backgroundremover/bg.py", line 187, in remove
    cutout = alpha_matting_cutout(
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/backgroundremover/bg.py", line 147, in alpha_matting_cutout
    alpha = estimate_alpha_cf(img_normalized, trimap_normalized)
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/pymatting/alpha/estimate_alpha_cf.py", line 51, in estimate_alpha_cf
    is_fg, is_bg, is_known, is_unknown = trimap_split(trimap)
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/pymatting/util/util.py", line 495, in trimap_split
    raise ValueError(
ValueError: Trimap did not contain foreground values (values >= 0.900000)

Does this work without pymatting? Did you install python3.8-dev?

I'm unable to get right python3.8-dev for mxlinux? Also how about delivering nadermx / backgroundremover in  Dockerfile.
https://pkgs.org/search/?q=python3.8-dev

Does this work without the -a -ae 15, so backgroundremover -i ./final_sign.jpeg -o final_sig4.png  Did you install python3.8-dev?

backgroundremover -i ./final_sign.jpeg -o final_sig4.png

RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd
Failed to import ahead-of-time-compiled modules.
This is expected on first import.
Compiling modules and trying again.
This might take a minute.
Traceback (most recent call last):
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/pymatting_aot/cc.py", line 36, in <module>
    import pymatting_aot.aot
ImportError: numpy.core.multiarray failed to import

During handling of the above exception, another exception occurred:

RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd
Traceback (most recent call last):
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/pymatting_aot/cc.py", line 36, in <module>
    import pymatting_aot.aot
ImportError: numpy.core.multiarray failed to import

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/xyz/.asdf/installs/python/3.8.0/bin/backgroundremover", line 5, in <module>
    from backgroundremover.cmd.cli import main
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/backgroundremover/cmd/cli.py", line 5, in <module>
    from .. import utilities
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/backgroundremover/utilities.py", line 10, in <module>
    from .bg import DEVICE, Net, iter_frames, remove_many
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/backgroundremover/bg.py", line 6, in <module>
    from pymatting.alpha.estimate_alpha_cf import estimate_alpha_cf
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/pymatting/__init__.py", line 2, in <module>
    import pymatting_aot.cc
  File "/home/xyz/.asdf/installs/python/3.8.0/lib/python3.8/site-packages/pymatting_aot/cc.py", line 56, in <module>
    import pymatting_aot.aot
ImportError: numpy.core.multiarray failed to import

I haven't thought about docker as I don't use it, but over some time I could try and figure it out.  I'm seeing this stackoverflow question, https://stackoverflow.com/questions/20518632/importerror-numpy-core-multiarray-failed-to-import
one of the soltuions says
pip install --upgrade pip
pip install -U numpy

It seems it might be a version of either pip or numpy, perhaps try some of those solutions? I've only had the time to test this on ubunutu.

I think its python virtualenv might reduce the dependency errors.
backgroundremover -i ./final_sign.jpeg -o final_sig4.png  << this works now.

but when these attributes -a -ae 15 are added it's throwing error.

The same error?

Please note I had installed rembg and other similar tools, Maybe it had some conflicting libraries. Now it works fine.
$ backgroundremover -i ./tm1.png -a -ae 15 -o oyt.png
oyt.png
[W NNPACK.cpp:80] Could not initialize NNPACK! Reason: Unsupported hardware.
PERFORMANCE WARNING:
Thresholded incomplete Cholesky decomposition failed due to insufficient positive-definiteness of matrix A with parameters:
    discard_threshold = 1.000000e-04
    shift = 0.000000e+00
Try decreasing discard_threshold or start with a larger shift

$ backgroundremover -i ./final_sign.jpeg  -ae 15 -o final_sign_out.png
final_sign_out.png
[W NNPACK.cpp:80] Could not initialize NNPACK! Reason: Unsupported hardware.

Awesome, glad to hear.  Yeah virtual enviroment is key for most python projects.  I may update the readme to install it in it's own virtual env, just incase.  I'll consider this issue closed.


UI list pods from multiple statefulset if they share the same label

Internal reference: SURE-5576
Reported in 2.6.9
If there are two StatefulSets with the same label. The UI will list the pods from both StatefulSet.
As you can see in the screenshots below, when selecting StatefulSet busybox-1, the user can list the pods of both busybox-1 and busybox-2 because they share the same label (app: busybox). (This is from 2.6.9)

And when selecting any of the two StatefulSets, the user can see pods from both StatefulSets

It seems even kubectl doesn’t have the ability to list pods for specific StatefulSet. We can only use labels. Any guidance here will be appreciated.
Issue also affects old version 2.5
Business impact:
UI list pods from multiple StatefulSet if they share the same label
Troubleshooting steps:
Repro steps:

Create a Rancher cluster
Deploy two Statefulset with the same label
Go to the Statefulset page in the UI, and it will list pods from both StatefulSets

No workaround
Expected behavior:
UI should not list pods from multiple StatefulSets if they share the same label

Part of this may be permissible by Kubernetes. If that's the case, we need to document what that part is but we still have to sort out what's going on with the lack of uniqueness in labels is.

I believe this is as indented k8s behaviour

@aalves08 I would try creating a statefulset as per the example here: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/ and then just modify the name of the statefulset and create it again.

QA TEST PLAN
Scenarios

Scenario
Test Case

1
As an admin user, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only

2
As a standard user, provision a downstream RKE1 node driver cluster, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only

3
As a standard user, provision a downstream RKE2 node driver cluster, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only

4
As a standard user, provision a downstream K3S node driver cluster, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only

Reproduced this bug on v2.7.0. See details below:
ENVIRONMENT DETAILS

Rancher install: Docker
Rancher version: v2.7.0
Browser: Chrome

TEST RESULT

Scenario
Test Case
Result

1
As an admin user, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only
:x:

VALIDATION STEPS
Scenario 1

As an admin user,  navigated to the top-left menu > local cluster > Workload > StatefulSets.
Created two StatefulSets, namely test1 and test2, using the following YAML:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: test1
  namespace: default
spec:
  selector:
    matchLabels:
      app: nginx # has to match .spec.template.metadata.labels
  serviceName: "nginx"
  replicas: 3 # by default is 1
  minReadySeconds: 10 # by default is 0
  template:
    metadata:
      labels:
        app: nginx # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: nginx
        image: registry.k8s.io/nginx-slim:0.8
        ports:
        - containerPort: 80
          name: web
  volumes:
    - name: test1
      persistentVolumeClaim:
      claimName: test1

Reproduced the behavior as shown below:

I will attempt to validate that this is resolved on the latest v2.7-head.

Validated that this is addressed on v2.7-head https://github.com/rancher/rancher/commit/95edd0203b7c5f0159d09e368e6897a06c48ba77. See details below:
ENVIRONMENT DETAILS

Rancher install: Docker
Rancher version: https://github.com/rancher/rancher/commit/95edd0203b7c5f0159d09e368e6897a06c48ba77
Browser: Chrome

TEST RESULT

Scenario
Test Case
Result

1
As an admin user, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only
:white_check_mark:

2
As a standard user, provision a downstream RKE1 node driver cluster, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only
:white_check_mark:

3
As a standard user, provision a downstream RKE2 node driver cluster, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only
:white_check_mark:

4
As a standard user, provision a downstream K3S node driver cluster, deploy two StatefulSets with matching labels, validate that each StatefulSets displays their respective pods only
:white_check_mark:

VALIDATION STEPS
Scenario 1

As an admin user,  navigated to the top-left menu > local cluster > Workload > StatefulSets.
Created two StatefulSets, namely test1 and test2, using the following YAML:

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: test1
  namespace: default
spec:
  selector:
    matchLabels:
      app: nginx # has to match .spec.template.metadata.labels
  serviceName: "nginx"
  replicas: 3 # by default is 1
  minReadySeconds: 10 # by default is 0
  template:
    metadata:
      labels:
        app: nginx # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: nginx
        image: registry.k8s.io/nginx-slim:0.8
        ports:
        - containerPort: 80
          name: web
  volumes:
    - name: test1
      persistentVolumeClaim:
      claimName: test1

Viewed the StatefulSets and noted the following:

Scenario 2

As a standard user, provisioned a downstream RKE1 node driver v1.26.4-rancher2-1 cluster.
Repeated scenario 1 steps 2-3, which yielded the same successful results.

Scenario 3

As a standard user, provisioned a downstream RKE2 node driver v1.26.4+rke2r1 cluster.
Repeated scenario 1 steps 2-3, which yielded the same successful results.

Scenario 4

As a standard user, provisioned a downstream K3S node driver v1.26.4+k3s1 cluster.
Repeated scenario 1 steps 2-3, which yielded the same successful results.


[AST] Mark two more dump() methods as LLVM_ATTRIBUTE_USED

...so that they don't get dead-code-stripped and become unusable from the debugger.

@swift-ci Please smoke test


Error: tcp lookup no such host - when no location specified

What happened?
When I run the following command to create an agent:
$ cxcli agent create TesterBot --credentials ~/.config/gcloud/service-account-key.json

It returns the following error:
ERRO[2023-04-18T21:20:07-05:00] Post "https://-dialogflow.googleapis.com:443/v3beta1/projects//locations//agents?%!a(MISSING)lt=json%!B(MISSING)enum-encoding%!D(MISSING)int": dial tcp: lookup -dialogflow.googleapis.com: no such host

How can we reproduce this?

Install cxcli
Create a service account and a JSON key
Create an agent with cxcli agent create [name] --credentials [path-to-json-key]

cxcli version
INFO[2023-04-18T21:22:18-05:00] Current version: 1.43.1
INFO[2023-04-18T21:22:19-05:00] You have installed the latest version!

Search

[X] I did search for other open and closed issues before opening this.

Code of Conduct

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

Additional context
Does cxcli pull a default location from the gcloud config? If not, then the --location-id should be a required parameter.
Also, you might want to catch errors when cxcli tries to reach out to https://-dialogflow.googleapis.com (when the location is not specified) and/or allow users to use the https://dialogflow.googleapis.com service endpoint. Otherwise users might get confused by the tcp error and not know to specify a location.
Finally, thanks for the great tool! 😎

As a related note, if the region is not specified, should cxcli default to the global region similar to the Dialogflow CX API?
https://cloud.google.com/dialogflow/cx/docs/concept/region

As a related note, if the region is not specified, should cxcli default to the global region similar to the Dialogflow CX API?
https://cloud.google.com/dialogflow/cx/docs/concept/region

that is a great idea @koverholt ! we can use global as the default one

I am gonna close this issue in favour of this one: https://github.com/xavidop/dialogflow-cx-cli/issues/59 since the issue under the hood is the same: don't specify the required flags

Sounds good to me, I'll add some more specific bullet points and proposed solutions to #59 rather than duping in this issue.


[FEAT] Add hacktoberfest example

⚠ WIP
Depends on #58
While the PR is opened, new example is available at https://cdn.statically.io/gh/process-analytics/bpmn-visualization-examples/add_hacktoberfest_example/examples/hacktoberfest-diagram/index.html

@csouchet the home index.html and the home README are currently missing to reference the new example.
I suggest to reference this example close to the custom color examples as it show how to have cutom color for icons of BPMN elements.

@csouchet the home index.html and the home README are currently missing to reference the new example.
I suggest to reference this example close to the custom color examples as it show how to have cutom color for icons of BPMN elements.

I didn't finish 😉
I did it before seeing your comment ^^

Latest review with info
with eb0686f

alternative proposal


fix(core): fix ngx.balancer.recreate_request does not refresh body bu…

…ffer issue when ngx.req.set_body_data is used in balancer phase
backport Openresty upstream fix: https://github.com/openresty/lua-nginx-module/pull/2334
issues context: https://github.com/openresty/lua-nginx-module/issues/2333

Summary

Checklist

[x] The Pull Request has tests
[ ] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

AG-12

Need a change log entry?

hold merge after 3.8 is released for safety of summit

converting this to draft because there's no do not merge label anymore.


ext: initial alembic support

Related PRs:

https://github.com/inveniosoftware/invenio-accounts/pull/172
https://github.com/inveniosoftware/invenio-records/pull/158
https://github.com/inveniosoftware/invenio-communities/pull/89
https://github.com/inveniosoftware/invenio-pidstore/pull/93

self LGTM - Travis is green, no comments for 3 days


[Block] Prevent multiple actions call

Actual behaviour
Action bar is not blocked when a request is sent to the server.
So, when a user double click on confirm in the block bar, data is sent multiple times to the server.
Expected behaviour
Prevent the block to sent another request until completion of the first request.
Versions
Focus-core: 0.12.0
Focus-components: 0.7.9-rc2

A block is blocked with data loading attribute and prevents click to other button. You action should set loading to true.

@durandx does @pierr 's answers solved your issue ?

We use a standard action (build with actionBuilder), standard block, and standard service call...

linked to #618 and #779


Shouldn't it be CZOpenWeatherMapRequest in your example

Hi,
shouldn't
CZOpenWeatherMap *request = [CZOpenWeatherMap newCurrentRequest];
request.location = [CZWeatherLocation locationForCity:@"Seattle" state:@"WA"];
[request sendWithCompletion:^(CZWeatherData *data, NSError *error) {
CZWeatherCurrentCondition *condition = date.current;
// dreams come true here
}];
look like this?
CZOpenWeatherMapRequest *request = [CZOpenWeatherMapRequest newCurrentRequest];
request.location = [CZWeatherLocation locationForCity:@"Seattle" state:@"WA"];
[request sendWithCompletion:^(CZWeatherData *data, NSError *error) {
CZWeatherCurrentCondition *condition = date.current;
// dreams come true here
}];
and "date.current", should be "data.current" I guess..
Sascha

Yeah you're right, fixing...


Display value and variables in run results

Display the account value and the final values of all the user variables in the run results.

Delivered to master.
I added another ListView and added all the user vars from the context to it. I also added another text block for the current account value.
Commit
commit 90bfac4a449c7e82f07469085205769f237cb22e
Author: Alex Hunt<EMAIL_ADDRESS>Date:   Thu Apr 28 22:42:44 2022 -0400
Issue62: Account value and user variables are now displayed in the results view.

Testing

Ran a strategy and checked that the variables are displayed with their ending values.
Checked that the new account value is displayed and is correct.