Can't dismiss bubble by clicking on background dim or bubble

When using:
                override fun onTargetClick(bubbleShowCase: BubbleShowCase) =
                    bubbleShowCase.dismiss()

                override fun onClose(bubbleShowCase: BubbleShowCase) = Unit
            })`

Bubble won't dismiss when clicked.

Hi wezley98,
It is only possible to close the Bubble clicking the targetView or the closeActionImage.

would it be possible to add another listener method for the bubble?

@wezley98 I have been facing the same problem. Still waiting for an answer on that!

Hi wezley98 and abel2901,
A new library version has been published:
implementation 'com.elconfidencial.bubbleshowcase:bubbleshowcase:1.3.0'

Now, you can know when the user clicks on the bubble or the background dim.
BubbleShowCaseBuilder(this) //Activity instance
                .title("foo") //Any title for the bubble view
                .listener(listener(object : BubbleShowCaseListener{ //Listener for user actions
                    override fun onTargetClick(bubbleShowCase: BubbleShowCase) {
                        //Called when the user clicks the target
                    }
                    override fun onCloseActionImageClick(bubbleShowCase: BubbleShowCase) {
                        //Called when the user clicks the close button
                    }
                    override fun onBubbleClick(bubbleShowCase: BubbleShowCase) {
                        //Called when the user clicks on the bubble
                        bubbleShowCase.dismiss() //If you want to close the bubble when the user clicks on it.
                    }

                    override fun onBackgroundDimClick(bubbleShowCase: BubbleShowCase) {
                        //Called when the user clicks on the background dim
                        bubbleShowCase.finishSequence() //If you want to close all the sequence when the user clicks on background dim.
                    }
                })
                .targetView(view) //View to point out
                .show() //Display the ShowCase

I hope it will be useful for your requirements. Sorry for the delay. :)

Thank You Very Much !! it helped a lot !

How to hide BubbleShowCase automatically after 5 seconds?


Add Download Button to Pins

Hello, I want to work on this problem

Hi @LPkkjHD I have made the download button in the marker pins and added a functionality that it downloads the description of the city of which the pin is open .

@LPkkjHD I have made a pull request please review it
Thanks.

@arpitjha867 Thank you for your PR! I'll review it later as I'm currently not home.


Using existing midi?

Would it be possible to use the ai jam demo on an existing midi file instead of a midi device?
For example sake, would/could you be able to generate a midi through use of magenta/models/melody_rnn/, and then use the ai jam to create a drum track based on that input?
Or is this a question for the drums_rnn model?
Also, the link for the for the simplified js version is pointing to the wrong place. I believe it should be https://github.com/tensorflow/magenta-demos/tree/master/ai-jam-js instead of https://github.com/tensorflow/magenta-demos/blob/master/demos/ai-jam-js

asked and answered in the main branch. The error was between the keyboard and chair. Closing.


[Bug]: Responsive Search bar

Give a brief about the bug ✍
Description:
In this project below 766px width the search bar doesn't display properly when click on search icon
https://github.com/GameSphere-MultiPlayer/Community-Page/assets/127814497/fd78bbe1-1dac-45b9-b2ee-eb43c4883e93
@Durgesh4993 please assign this issue to me
What is the expected behavior? 🤔
Description: Create a Responsive search bar suitable in all devices
Provide step by step information reproduce the bug 📄
steps : Create a responsive search bar when click  on search icon
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

please assign it to me. I can fix it.

If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

@ayushrskiaa Please raise any other issue, i'll assign you

hii ,
I'm GSSoC'24 contributor , I have experienced in HTML, CSS, JS, and react.js , so I want to work on this issue,
so, kindly requested to you to assign me the issue.


Added Footer #59

Hello! @surajondev Please check my pr.

Hi there! Could you just space the icons a little bit, it's a bit too close, besides that, it's perfect.

Is it okay now? Kindly check @xMrAfonso

Yes, thanks a lot!

Kindly add "hacktoberfest2022" and "hacktoberfest-accepted" tags @xMrAfonso @surajondev so that this contribution gets counted


fix: access tsi active log file with READ lock

Closes #16383

@e-dard can you add 1.x label?

@dgnorton can you take care of this, and check if it needs to hit 1.8?

@dgnorton @e-dard can you get it merged into 1.7?


Device state incomplete/insufficient

https://github.com/jbouwh/lib-elro-connects/blob/2eed7bbf606c30ad63eea12cb90ff8fcb77ac49d/elro/device.py#L84
After a false alarm of a fire alarm, I noticed nothing really triggered. So i took a deep dive into the code and noticed that the original code of dib0 was incomplete, and the "splat" that happened in the referenced line was less fortunate. I came to this conclusion after i took a look at the original code from the android app and it is different from what was used originally:
https://github.com/Skons/familywell-lidl-android/blob/6218fdd314a031c4745e71f101061065cc27bbfc/branch/lidl/app/src/main/java/me/hekr/sthome/equipment/detail/CxSmDetailActivity.java#L269
In the original dib0, i created this list to get the correct status
#FIRE_ALARM specific status
        if self.device_type == DeviceType.FIRE_ALARM:
            logger.debug(f"AlarmSensor with id '{self.id}' is a FIRE_ALARM, state is '{state}'")

            if state == "17":
                state_name = "Test alarm" #Operation: Test alarm
            elif state == "18":
                state_name = "Temperature alarm" #Operation: Silence
            elif state == "19":
                state_name = "Fire alarm" #Operation: Silence
            elif state == "11":
                state_name = "Error" #Operation: Do not disturb
            elif state == "12":
                state_name = "Error" #Operation: Do not disturb
            elif state == "13":
                state_name = "Low battery" #Operation: Do not disturb
            elif state == "15":
                state_name = "Do not disturb" #Operation: Do not disturb
            elif state == "18":
                state_name = "Silence" #Operation: Do not disturb
            elif state == "AA":
                state_name = "Normal"
            else:
                state_name = "Offline"

To get to this, i used jadx to open up the elro connects downloaded from APKPure. The doStatusShow from the  CxSmDetailActivity has got something like this:
            if ("17".equals(substring3)) {
                this.root.setBackgroundColor(getResources().getColor(R.color.device_error));
                this.showStatus.setTextColor(getResources().getColor(R.color.device_error));
                this.showStatus.setText(getResources().getString(R.string.cxalert7));
                this.operation.setText(getResources().getString(R.string.cxalert7));
                this.operation.setEnabled(true);
            }

It has a showStatus.setText with a reference to R.string.cxalert7. In Resources/resources.arsc/res/values/string.xml this list is available:
    <string name="cxalert11">Silence</string>
    <string name="cxalert2">Fault</string>
    <string name="cxalert5">Silence</string>
    <string name="cxalert6">Silence</string>
    <string name="cxalert7">Test alarm</string>
    <string name="cxalert8">Temp Alarm</string>
    <string name="cxalert9">Fire alarm</string>

This is the way equipment statuses can be related to a text string. Another thing available in the [device]DetailActivity code, is  this.operation.setText(getResources().getString(R.string.cxalert7). It show that a state can have an operation. Not every type of equipment has got this, but some have. Others also have state changes associated, but they are implemented differently. Most, maybe even all, of the operations that are allowed on the FireAlarm (CXSM_ALARM) are collected in the following function
    public void sendSlienceSign(String str) {
        try {
            int parseInt = Integer.parseInt(this.device.getEquipmentDesc().substring(this.device.getEquipmentDesc().length() - 2), 16);
            if (getResources().getString(R.string.cxalert7).equals(str)) {
                if (isDebugMode() && parseInt >= 14) {
                    openTestModeAlert();
                } else {
                    SendCommand.Command = 1;
                    this.sd.sendEquipmentCommand(this.device.getEqid(), "17000000");
                }
            } else if (getResources().getString(R.string.cxalert11).equals(str)) {
                SendCommand.Command = 1;
                this.sd.sendEquipmentCommand(this.device.getEqid(), "1B000000");
            } else if (getResources().getString(R.string.cxalert5).equals(str)) {
                SendCommand.Command = 1;
                this.sd.sendEquipmentCommand(this.device.getEqid(), "15000000");
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

It shows that the state of the device, and the operations allowed on the device are closely related. The current code has made the device.py very generic, The commands defined in the command.py now contain every command, but shouldn't the device commands be regulated by de device.py? I don't know if you agree, besides i am not a very good object oriented programmer in python. I would love to create that code, but the implications of that are quite significant and i cannot oversee that all right now. Please let me know what you think and if you want my help implementing a solution.
This is the way the socket is implemented:
    private void newAction() {
        this.operation_img.setOnClickListener(new View.OnClickListener() { // from class: me.hekr.sthome.equipment.detail.SocketDetailActivity.5
            @Override // android.view.View.OnClickListener
            public void onClick(View view) {
                SocketDetailActivity.this.chuli();
            }
        });
    }
    public void chuli() {
        if (this.device.getState() == null || "".equals(this.device.getState()) || this.device.getState().length() != 8) {
            this.sd.sendEquipmentCommand(this.eqid, "0101ffff");
            return;
        }
        String substring = this.device.getState().substring(6, 8);
        String str = "00";
        if ("00".equals(substring)) {
            str = "01";
        } else {
            "01".equals(substring);
        }
        this.sd.sendEquipmentCommand(this.eqid, "01" + str + "ffff");
    }

    private void doStatusShow(String str) {
        try {
            String substring = str.substring(0, 2);
            String substring2 = str.substring(6, 8);
            this.signal.setImageResource(ShowBascInfor.choseSPic(substring));
            if ("01".equals(substring2)) {
                this.root.setBackgroundColor(getResources().getColor(R.color.device_error));
                this.showStatus.setTextColor(getResources().getColor(R.color.device_error));
                this.operation_img.setImageResource(R.drawable.detail_switch_on);
                this.showStatus.setText(getResources().getStringArray(R.array.socket_actions)[0]);
            } else if ("00".equals(substring2)) {
                this.root.setBackgroundColor(getResources().getColor(R.color.device_normal));
                this.showStatus.setTextColor(getResources().getColor(R.color.device_normal));
                this.operation_img.setImageResource(R.drawable.detail_switch_off);
                this.showStatus.setText(getResources().getStringArray(R.array.socket_actions)[1]);
            } else {
                this.root.setBackgroundColor(getResources().getColor(R.color.device_offine));
                this.showStatus.setTextColor(getResources().getColor(R.color.device_offine));
                this.operation_img.setImageResource(R.drawable.detail_switch_off);
                this.showStatus.setText(getResources().getString(R.string.offline));
            }
        } catch (Exception unused) {
            this.root.setBackgroundColor(getResources().getColor(R.color.device_offine));
            this.showStatus.setTextColor(getResources().getColor(R.color.device_offine));
            this.operation_img.setImageResource(R.drawable.detail_switch_off);
            this.showStatus.setText(getResources().getString(R.string.off_line));
            this.signal.setImageResource(ShowBascInfor.choseSPic("04"));
        }
    }

Interesting, I'll take steps to add to add the missing states. The current implementation just shows the hex number instead,.With this, that is not needed anymore.

@Skons The current code is very generic indeed, to allow debugging and testing with it. Through some user feedback I was able to reverse engineer some states and commands. It was already clear to me that command are only accepted for specific device types and under specific conditions. I use the library for ha-elro-connects to enable the entities under Home Assistant through hacs. With this, I can improve the state reporting. Not sure what commands would be helpful to have added though?

Can you check the linked PR? If this is merged, ha_elro_connects also needs an update to add the new states.

Your code now implements the statuses, but not the operation that can be associated. If you look at this
public void sendSlienceSign(String str) {
        try {
            int parseInt = Integer.parseInt(this.device.getEquipmentDesc().substring(this.device.getEquipmentDesc().length() - 2), 16);
            if (getResources().getString(R.string.cxalert7).equals(str)) {
                if (isDebugMode() && parseInt >= 14) {
                    openTestModeAlert();
                } else {
                    SendCommand.Command = 1;
                    this.sd.sendEquipmentCommand(this.device.getEqid(), "17000000");
                }
            } else if (getResources().getString(R.string.cxalert11).equals(str)) {
                SendCommand.Command = 1;
                this.sd.sendEquipmentCommand(this.device.getEqid(), "1B000000");
            } else if (getResources().getString(R.string.cxalert5).equals(str)) {
                SendCommand.Command = 1;
                this.sd.sendEquipmentCommand(this.device.getEqid(), "15000000");
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

you can see that cxalert5 is associated with command 15000000
In this piece i already commented the possible operations that are allowed
if self.device_type == DeviceType.FIRE_ALARM:
            logger.debug(f"AlarmSensor with id '{self.id}' is a FIRE_ALARM, state is '{state}'")

            if state == "17":
                state_name = "Test alarm" #Operation: Test alarm
            elif state == "18":
                state_name = "Temperature alarm" #Operation: Silence
            elif state == "19":
                state_name = "Fire alarm" #Operation: Silence
            elif state == "11":
                state_name = "Error" #Operation: Do not disturb
            elif state == "12":
                state_name = "Error" #Operation: Do not disturb
            elif state == "13":
                state_name = "Low battery" #Operation: Do not disturb
            elif state == "15":
                state_name = "Do not disturb" #Operation: Do not disturb
            elif state == "18":
                state_name = "Silence" #Operation: Do not disturb
            elif state == "AA":
                state_name = "Normal"
            else:
                state_name = "Offline"

And that is what is missing with the generic implementation that has been created. As said, i do not know enough about it all to create a good implementation. But there should be something, i think, that allows for peeking into the possibilities of a device. In this way you can create an object that becomes its own entity in HA with it's own properties and methods. But again, i do not know how to do that properly. If it's done smart enough, it should become quite easy to implement other devices that communicate with the k1.

The operation is linked to the device type in ha_elro_connects, not in this library. This keeps the code base flexible. Are you missing any commands?

If i'm not mistaken, the silence alarm in ha_elro_connects is this: self._description.silence_alarm, device_ID=self._device_id
silence_alarm seems to be from here
https://github.com/jbouwh/lib-elro-connects/blob/2eed7bbf606c30ad63eea12cb90ff8fcb77ac49d/elro/command.py#L148
and that sends this to the hub (like the way i implemented it in the dib0 repo...)
additional_attributes={"device_ID": 0, "device_status": "00000000"},

But, if i take a look at this from the android app
    public void sendSlienceSign(String str) {
        try {
            int parseInt = Integer.parseInt(this.device.getEquipmentDesc().substring(this.device.getEquipmentDesc().length() - 2), 16);
            if (getResources().getString(R.string.cxalert7).equals(str)) {
                if (isDebugMode() && parseInt >= 14) {
                    openTestModeAlert();
                } else {
                    SendCommand.Command = 1;
                    this.sd.sendEquipmentCommand(this.device.getEqid(), "17000000");
                }
            } else if (getResources().getString(R.string.cxalert11).equals(str)) {
                SendCommand.Command = 1;
                this.sd.sendEquipmentCommand(this.device.getEqid(), "1B000000");
            } else if (getResources().getString(R.string.cxalert5).equals(str)) {
                SendCommand.Command = 1;
                this.sd.sendEquipmentCommand(this.device.getEqid(), "15000000");
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

Then you can see that the app sends different commands based on the current state, to the device that has an alarm state, i.e. this.sd.sendEquipmentCommand(this.device.getEqid(), "15000000");. Take a look at this in regards to the state cxalert5=Silence
    <string name="cxalert11">Silence</string>
    <string name="cxalert2">Fault</string>
    <string name="cxalert5">Silence</string>
    <string name="cxalert6">Silence</string>
    <string name="cxalert7">Test alarm</string>
    <string name="cxalert8">Temp Alarm</string>
    <string name="cxalert9">Fire alarm</string>

Sidenote
I really think english has not been properly translated, i also think the app creates bugs by using descriptions instead of the technical state. This is the dutch translation:
    <string name="cxalert11">Stil</string>
    <string name="cxalert2">Fout</string>
    <string name="cxalert5">Niet storen</string>
    <string name="cxalert6">Niet storen</string>
    <string name="cxalert7">Test alarm</string>
    <string name="cxalert8">temperatuuralarm</string>
    <string name="cxalert9">Brandalarm</string>
    <string name="cxsmalarm">Rookmelder</string>

/Sidenote
The code translates to this table

Current state
name
Command to send

Test alarm
ctxalert7
17000000

Silence
ctxalert11
1B000000

Do not disturb
ctxalert5
15000000

this.device.getEqid() is the device_id of this device, and not from the hub. This is because this.device.getEqid() is used, and not the ConnectionPojo object. Here you can see how that command leads to the json that will be send to the hub.
/* SendEquipmentData class */
    public void sendEquipmentCommand(String str, String str2) {
        sendAction(this.sc.equipControl(str, str2));
    }

/* SendCommand class */
   public String equipControl(String str, String str2) {
        if (ConnectionPojo.getInstance().msgid < 65536) {
            ConnectionPojo.getInstance().msgid++;
        } else {
            ConnectionPojo.getInstance().msgid = 0;
        }
        return jsonToString("{     \"msgId\": " + ConnectionPojo.getInstance().msgid + ",      \"action\": \"appSend\",      \"params\": {         \"devTid\": \"" + ConnectionPojo.getInstance().deviceTid + "\",         \"ctrlKey\": \"" + ConnectionPojo.getInstance().ctrlKey + "\",          \"data\": {\n            \"cmdId\": 1,              \"device_ID\": " + str + ",            \"device_status\": \"" + str2 + "\"        }     } }");
    }

Right, the android app seems to so som trial and error to silence a device. But the commands may be could be corrected.
To issue a test alarm the code knows what command to choose.

This is not about issuing the test alarm, that seems to be the same. This is about silencing an alarm. This could be done to the hub, but the app does it to the device itself

This is not about issuing the test alarm, that seems to be the same. This is about silencing an alarm. This could be done to the hub, but the app does it to the device itself

So what you suggest is to update the silence command codes?

So it is clear the Android app silences based on the state. But is the silencing depending on the device type as well?

That seems to be the case. The gas and the co both use BB000000 to enable and disable a test alarm.

@Skons Can you help to make an overview for the commands to test and silence per device type/state. Then I'll try to implement this. The cases based on state should be included.


New discussion

Hi I'm not able to generate the message content of the new discussion by passing a straightforward string. I manage to get the subject but the field "message" stays empty.
Moreover I did not manage to have the correct format to pass the recipients' list (do I have to specify the email address or just id, name and _type ?

Hi, you should get recipients from Client.get_recipients. I couldn't recreate your issue with the message content.
import pronotepy
from pronotepy import Util

client = pronotepy.Client(...)

assert client.logged_in

recip = client.get_recipients()
client.new_discussion("New discussion subject", "A message", Util.get(recip, name="Mme BROWN J."))


print(..., file=wspm) is redundant

Consider creating a helper method to avoid having to write print(..., file=wspm) over and over again. For example instead of
    print('',file=wspm)
    print("Please select your country below to see our supported payment methods for Wix Stores:

",file=wspm)
    #generates the dropdown menu of all the countries we support
    print('<select id="selectedcountry" onchange="optionCheck()">',file=wspm)
    for z in range(0,len(country)):
            print('<option value="',z,'">',country[z],'</option>',file=wspm)

Write a helper method (say "p()") to simplify the code to:
    p('')
    p("Please select your country below to see our supported payment methods for Wix Stores:

")
    #generates the dropdown menu of all the countries we support
    p('<select id="selectedcountry" onchange="optionCheck()">')
    for z in range(0,len(country)):
            p('<option value="',z,'">',country[z],'</option>')

Again, great point. I should break a lot of this up into functions
On Wed, Sep 7, 2016, 20:05 Eric Chiang<EMAIL_ADDRESS>wrote:

Consider creating a helper method to avoid having to write print(...,
file=wspm) over and over again. For example instead of
print('',file=wspm)
print("Please select your country below to see our supported payment methods for Wix Stores:

",file=wspm)
#generates the dropdown menu of all the countries we support
print('<select id="selectedcountry" onchange="optionCheck()">',file=wspm)
for z in range(0,len(country)):
        print('<option value="',z,'">',country[z],'</option>',file=wspm)

Write a helper method (say "p()") to simplify the code to:
p('')
p("Please select your country below to see our supported payment methods for Wix Stores:

")
#generates the dropdown menu of all the countries we support
p('<select id="selectedcountry" onchange="optionCheck()">')
for z in range(0,len(country)):
        p('<option value="',z,'">',country[z],'</option>')

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/barakplasma/wixStoresPaymentMethodsByCountry/issues/1,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD12QM5Fjp8xXhrWVKjVucBa9dv7zIEks5qnu64gaJpZM4J3JYX
.


#435: Add metadata support (read/write) to pinecone embedded store

Context
Fixes #435
Change
I have added support for storing custom metadata and retreiving it.
I have added some comments to the PR describing more important changes for verification

Hey, is there anything I can do to help this along? I don't want to step on any toes/I'm new to this project and this is someone else's work- but I need this for something I'm currently working on and would rather put my effort towards getting this merged vs. having a one off fork.
I'm happy to rebase to main, write/fix unit tests, whatever needs to get finished. Let me know.

@sfotex feel free to finish it, I ended up with using my own fork and PR got attention after couple weeks and I did not have time to look at it yet.
Btw if this gets merged I have another one where I refactored the code to use pinecone client v. 1.0.0, will create the PR once this gets merged. Just letting you know in case you need it as well.

@sfotex thank you, feel free to address the comments

Hi @sfotex, any updates? Please let me know if you plan to address this PR/comments.

Has been implemented in https://github.com/langchain4j/langchain4j/pull/1400


Added a failing test for issue #449.

An optional dependency shouldn't treat its own required dependencies as optional.
The failing test is currently disabled.

Hmm, not sure why the build is failing on the CI.
Locally it builds just fine and the failing test is commented out...


be more declarative

if we deploy a function that already exists kubeless fails.
kubeless function create foo ...
kubeless function create foo ...

We should be a bit more declarative like kubectl apply, for example I would like to see:
kubeless function update foo

Create the function and not fail if the function already exists.
This will help with continuous delivery.
And yes, I am aware that we can be declarative with kubectl apply if we stick the function in a k8s manifest.
cc/ @murali-reddy do you think you could hot fix kubeless update to also create a function if if does not already exists ?

Same thing with kubeless trigger create/update

Lets also be more declarative regarding the issue title - I would suggest

Make "kubeless function update" create the function and not fail if the function already exists to improve CI


fix: Support unsafeSsl and enable ssl verification as default

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>Checklist

[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes https://github.com/kedacore/keda/issues/4005

/run-e2e redis*

if you agree, I'd merge this ignoring the suggestions about the min TLS version, because I'd like to address all of the at once

/run-e2e redis*


Add circuitbreaker

Add go-kit circuitbreaker using handy breaker

Fixes #21

Coverage increased (+0.3%) to 71.905% when pulling 03b35f891af2a19589b68d85e2d70461b9c49dbe on add-circuitbreaker into 982de775ed1b04d55898bf34b0f72c5c241d7d4c on master.


Can palm_detection distinguish between right and left hand?

I am wondering if it is possible to use palm_detection (or hand_landmark...) for detecting which hand is rising, right or left?
Don't need this feature right now. Just curious.

quick and dirty
bool rigthHand = (landmarks[5].x()>landmarks[17].x());

It's not true. What if user show the back of hand to camera?

1 your welcome
2 still working on it

I am wondering if it is possible to use palm_detection (or hand_landmark...) for detecting which hand is rising, right or left?
Don't need this feature right now. Just curious.

This is a very good question! You are absolutely correct that basically there's no sense of right/left hand depending on which camera you are using. For example, right hand in front-facing looks exactly the same as left hand in back-facing camera. We are adding a feature to the model that it can predict it's the back or front of a hand, then you can tell left/right hand based on which camera you are using.

@fanzhanggoogle thank you for your reply, so glad to hear that!!
We will keep waiting for this amazing feature!

@fanzhanggoogle any updates on the feature? Would love to test it out.

You can determine handedness using hand_landmark in 3D. Here's my approach in python which I used in my python implementation of the Multi-hand Tracking pipeline:
def is_right_hand(kp):

    '''
    Returns True if kp is right hand and False if left hand.
    '''

    digitgroups = [
        (17,18,19,20),
        (13,14,15,16),
        (9,10,11,12),
        (5,6,7,8),
        (2,3,4) # Thumb
    ]

    palm_dir_vec = np.array([0,0,0], dtype=np.float64)
    for digit in digitgroups:
        for idx in digit[1:]:
            palm_dir_vec += kp[idx] - kp[digit[0]]

    palm_pos_vec = np.array([0,0,0], dtype=np.float64)
    for digit in digitgroups:
        palm_pos_vec += kp[digit[0]]
    palm_pos_vec /= len(digitgroups)

    top_palm_pos_vec = kp[9]

    val = np.dot(np.cross(kp[2] - palm_pos_vec, palm_dir_vec), top_palm_pos_vec - palm_pos_vec)

    if val < 0: return True

    return False

Here kp is a list of 3D coordinates representing the keypoints.

Have you researched a feasible way to distinguish between left and right hand ？I can't find a solution ~

You can determine handedness using hand_landmark in 3D. Here's my approach in python which I used in my python implementation of the Multi-hand Tracking pipeline:
def is_right_hand(kp):

    '''
    Returns True if kp is right hand and False if left hand.
    '''

    digitgroups = [
        (17,18,19,20),
        (13,14,15,16),
        (9,10,11,12),
        (5,6,7,8),
        (2,3,4) # Thumb
    ]

    palm_dir_vec = np.array([0,0,0], dtype=np.float64)
    for digit in digitgroups:
        for idx in digit[1:]:
            palm_dir_vec += kp[idx] - kp[digit[0]]

    palm_pos_vec = np.array([0,0,0], dtype=np.float64)
    for digit in digitgroups:
        palm_pos_vec += kp[digit[0]]
    palm_pos_vec /= len(digitgroups)

    top_palm_pos_vec = kp[9]

    val = np.dot(np.cross(kp[2] - palm_pos_vec, palm_dir_vec), top_palm_pos_vec - palm_pos_vec)

    if val < 0: return True

    return False

Here kp is a list of 3D coordinates representing the keypoints.
this approach for 2d coordinates  is ok？thanks

The above is more of a hack for back when mediapipe did not support handedness. It works by finding if the fingers are behind or in front of the palm, so it would not work for 2D coordinates. Mediapipe now supports handedness so I don't recommend you to use my code.


[performance testing] Ensure scaling behaviour is observed with horizontal scaling

Describe the issue:

Currently the scaling behaviour (reduction in response time) is not observed in high concurrencies due to bottlenecks outside Identity Server (Ex Database configuration)
These bottlenecks need to be identified and removed to observe proper horizontal scaling before publishing the performance results

Fix for IOPS bottleneck:
https://github.com/wso2/performance-is/pull/181

Use new instances:
https://github.com/wso2/performance-is/pull/186


Remaining work on add-analysis modal

Postponed stuff from #6886, that were considered nice-to-have at the moment. Most of them have impediments that needs to be discussed and resolved

[x] Options groups in UI; "data transformation", "relationship analysis", etc. #7626
[x] Collapse/expand option groups in UI #7628
[x] Search #7629

Closing since the things originally listed here were either resolved, or have separate issues created to be done later (considered "easy")


feat(TabBar): support TabBar

Summary
Support Tab and TabBar components.
Handling the border at TabBar level to ensure correct UI when the border color has different opacities.
Checklist before requesting a review

[x] Working on iOS
[x] Working on Android
[x] Integration tests added
[x] Visual regressions screenshots are up to date
[ ] Design validated

Screenshots

iOS
Android

Looks good to me! Thanks :) For the demo, can we please make sure the TabBar spans the entire width of the screen?

You mean an example where the Tabs overflow the width of the devices right?

Looks good to me! Thanks :) For the demo, can we please make sure the TabBar spans the entire width of the screen?

@ianrobertlambert You mean an example where the Tabs overflow the width of the devices right?

Yes please! And, can we please make the TabBar is aligned left edge to right edge of screen? Like this:

@ianrobertlambert  Updated with the minor fix and adding the example!


runtime: refactor into separate subpackages

Now that the runtime is Go code, we should be able to break it apart into multiple packages.
Among other things we should consider putting locking, the gc, and special symbols in separate packages.

Why, exactly?

Now that the runtime is written in Go, it's worth taking the time to consider whether it could be better organized if it were split into packages. I think it could. Splitting the runtime into packages could also help improve the readability, in the style sense, of the code. That would make the runtime more accessible to new contributors.
It was also suggested by crawshaw that putting certain parts of the runtime into their own packages would make it easier to stub out or replace parts of the runtime. That would be helpful when bootstrapping a new architecture or os, where all of the runtime is not available, or in creating a modified runtime that would run without an os.

I'm in favor of splitting up the runtime, at least insofar as it is mostly just movement of existing code. This has the following advantages:

Makes the structure and components of the runtime more obvious. There really are several basically standalone pieces.
Faster to run runtime tests when making modifications. (This is a pain point; the runtime tests are slow.)
Easier to do safe refactoring and experimentation.
Having a runtime/internal/magic package will make it more obvious where the runtime touches the compiler.

CL https://golang.org/cl/15045 updates this issue.

We got a couple subpackages in for Go 1.6. More work in Go 1.7.

Another advantage to this: More of the runtime could be build concurrently. It's not super slow to build, but it always runs first, and linearly, since everything else depends on it. See the graph at #15734.

Bumping this to Go 1.9. Not sure anything happened in Go 1.8 but it seems too late now.

At the very least, if there are parts of runtime that are not tightly coupled to the implementation details of the compiler, it would probably help maintainers of other compliers (such as TinyGo) to split those parts into separate subpackages. (See #31330.)

Another advantage to doing this: Any parts of the runtime not involved in scheduling can have their race/msan instrumentation done by the compiler rather than manually.


Disallow capital letter at the beginning in CamelCasePropertyName rule

Type: bugfix
Issue: Resolves #276
Breaking change: yes, capital letter at the beggining of property name is not allowed anymore in the CamelCasePropertyName rule

I miss read the BC part and pressed merge to fast, so I created a revert PR. Sorry for that.


[BUG] placeholder text showing for Qwik libraries section

Describe the bug
This is what is currently listed under the Qwik libraries section

I understand that we are currently in the process of adding real content for this section, but I think for now it would be best to remove the "test" text and add at least one real entry.  The logo and link lead to Flux so maybe we should change the title and description to be that.
To Reproduce
Steps to reproduce the behavior:

Go to https://www.framework.dev/
Click on Qwik resources
Click on libraries
See the entry

Expected behavior
The libraries entry should show real title and description
Screenshots

I am going to close this issue because this framework is not meant to be live yet on the production site


Support Jest 24.9.0

Describe the bug
Unable to run react-scripts start with jest 24.9.0
Did you try recovering your dependencies?
Yes
Which terms did you search for in User Guide?
jest 24.9.0
Environment
    "react-scripts": "3.1.1"
    "jest": "24.9.0",
Steps to reproduce
$ react-scripts start

There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

  "jest": "24.8.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of jest was detected higher up in the tree:

  /Users/bob/active/dev/react-native/react-native-web-typescript/node_modules/jest (version: 24.9.0)

Expected behavior
react-scripts start works
Actual behavior
react-scripts start breaks
Reproducible demo
n/a

It sounds like you've installed jest as a dependency of your application? If so this is expected behavior. We control the jest dependency as part of react-scripts.

Thank you.


nginx: use stick sessions

In our production deployment we'll have two servers running, which means we need to ensure websocket connections remain on the same host for the duration of the session.

Preview is available here:http://stellar-anchor-tests-pr20.previews.kube001.services.stellar-ops.com/

I'm closing this PR because I just realized that this solution won't work -- kubernetes will deploy two instances of the nginx proxy, one for each server instance, so there is no reason to have ip_hash.


Update: Lock down navi dependency versions

Resolves #

Description
Lock down navi dependency versions
Proposed Changes

Set versions to 0.2.0 as that is what we are currently publishing
Change navi dependencies from floating the minor to a static version

Screenshots
License
I confirm that this contribution is made under an MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

why

why

@cythrawll can you expand on your question :)

talked offline


SIGSEGV crashes, known issue?

We're evaluating the potential benefits of deploying Fatcache and I've run into a problem I haven't been able to resolve.  The code compiles cleanly on the platform we're using, Ubuntu 16/Trusty, and the server process start just fine.  But if I run performance tests with "memtier_benchmark" the server process crashes with a segmentation fault for any non-trivial test configuration.
I've tried running minimal configurations that use all defaults, I've compiled the v0.1.1 tag and the lastest code from the GitHub repo.  And I've compiled with full debugging enabled and optimization (O0 flag) disabled.  The process crashes each time no matter which configuration I use.
I'm hoping it's a known issue or something dumb I'm doing to setup/configure Fatcache.  But since I haven't found anything by searching public documents related to Fatcache I wanted to post here to look for clues.
Here's the stack trace from "gdb" in case it helps.
Program received signal SIGSEGV, Segmentation fault.
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
36	../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.
(gdb) where
#0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
#1  0x000000000040ccfc in mbuf_copy (mbuf=0x5889f60, pos=0x7ffff6ff0cf0 "", size=8144) at fc_mbuf.c:233
#2  0x000000000040ce1c in mbuf_copy_from (mhdr=0x737b68, pos=0x7ffff6ff0cf0 "", size=2347828697) at fc_mbuf.c:267
#3  0x000000000040c46f in rsp_send_value (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30, it=0x7ffff1ef104c, cas=423) at fc_response.c:338
#4  0x000000000040aaae in req_process_get (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30) at fc_request.c:212
#5  0x000000000040b8ae in req_process (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30) at fc_request.c:548
#6  0x000000000040b9f6 in req_recv_done (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30, nmsg=0x0) at fc_request.c:610
#7  0x0000000000409898 in msg_parsed (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30) at fc_message.c:168
#8  0x0000000000409c99 in msg_parse (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30) at fc_message.c:317
#9  0x0000000000409e85 in msg_recv_chain (ctx=0x7fffffffea00, conn=0x634ab0, msg=0x735a30) at fc_message.c:383
#10 0x0000000000409f30 in msg_recv (ctx=0x7fffffffea00, conn=0x634ab0) at fc_message.c:417
#11 0x000000000040415f in core_recv (ctx=0x7fffffffea00, conn=0x634ab0) at fc_core.c:77
#12 0x000000000040454f in core_core (ctx=0x7fffffffea00, conn=0x634ab0, events=1) at fc_core.c:157
#13 0x00000000004046f2 in core_loop (ctx=0x7fffffffea00) at fc_core.c:215
#14 0x000000000041396d in main (argc=13, argv=0x7fffffffeb08) at fc.c:746

I am having the same problem, very easy to reproduce

Hi,
I can confirm this is still an issue.
[Tue Apr 20 10:16:04 2021] fc_util.c:694 [0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7f4dd927c3c0] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [1] fatcache(+0x667c) [0x55f42073967c] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [2] fatcache(slab_get_item+0x14d) [0x55f420739c6d] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [3] fatcache(item_get+0x3d) [0x55f42073a47d] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [4] fatcache(+0x93f5) [0x55f42073c3f5] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [5] fatcache(req_recv_done+0x286) [0x55f42073c926] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [6] fatcache(msg_recv+0x1de) [0x55f42073c02e] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [7] fatcache(core_loop+0x56) [0x55f420738906] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [8] fatcache(main+0x758) [0x55f420738028] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [9] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f4dd909c0b3] [Tue Apr 20 10:16:04 2021] fc_util.c:694 [10] fatcache(_start+0x2e) [0x55f42073868e] Segmentation fault
I've tried compiling from the repository and from the tarball. No joy.  Is there any chance of this being fixed?

fatcache seems no maintenance for many years, you can have a try at https://github.com/bitleak/kvrocks which supports Redis protocol.

Amazing! Thanks for the link - I will definitely try it out.

Is fatcache no longer used/maintained as stated above?
cc: @manjuraj


Add Platforms Card List Page, update Platform list page

New page for All Platforms

Each Platform page with service Offerings:

@lgalis Looks good.  Merging to get in this sprint, we can address any follow items in a separate PR.


Missing a step to setup Environment variable DJANGO_SETTINGS_MODULE

[Enter feedback here]
In section "Prepare app for App Service", reader is asked to update manage.py and azuresite/wsgi.py. It's going to set environment variable DJANGO_SETTINGS_MODULE based on the value of another env variable DJANGO_ENV.
Here is the thing that Web App is required to configure environment variables in Application Settings. So I think we should also include this variable in Deploy the App Service app/Configure environment variables.

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

ID: 791bd216-532f-7f28-fa51-d95798397310
Version Independent ID: 4f7ff676-e4a5-cc41-6a43-ecb8fa1095fb
Content: Tutorial: Deploy Python (Django) with Postgres - Azure App Service
Content Source: articles/app-service/containers/tutorial-python-postgresql-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@kzkz221 Thank you for your feedback! We will review and update as appropriate.

@kzkz221 the DJANGO_ENV variable is set in Configure Environment Variables and is highlighted in Prepare app for App Service with the following note.

You'll set the environment variable DJANGO_ENV later when you configure your App Service app.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Build Newsboat on FreeBSD 11.2 and 12.0 with Cirrus CI

CI builds Newsboat, and runs Rust tests. Some C++ tests for ConfigPaths fail, and since we're rewriting this component at the moment, I'm not fixing them. This will be done later, when ConfigPaths is moved to Rust completely (see #413, #561).

Coverage increased (+0.005%) to 40.892% when pulling 65e345cc724f8202db96b1b5974a0bff1ca4b6c1 on feature/407-freebsd-with-cirrus-ci into 909e664d9b109289c3d50961b99aa49eb93e20e1 on master.


Add -ListAvailable param to Get-PlasterTemplate

On the heels of #336, provide additional clarification and a parameter for "classic" operation due to slightly breaking change.

@JustinGrote Thanks again!!


GeoLocation Library not present in most recent version

React Native version: 0.60.0
Steps To Reproduce

react-native init test
edit pods to include geolocation
atempt pod install
observe error due to inability to find Geolocation node_module
check '../node_modules/react-native/Geolocation
The library is not present

Describe what you expected to happen:

react-native init test
edit pods to include geolocation
atempt pod install
4.pod installs correctly
navigator.geolocation.getCurrentPosition should not error

This module has been extracted out to here as part of Lean Core. This was due to an issue where Apple was rejecting apps which declared privacy requirement strings (like for location), but didn't actually use them.
Follow the instructions in the project linked above to migrate to the new library. All of the API and the code is identical.


SC-Cord

alright just to be clear I wanted a little customization. was not gonna "sell" or act Like I made it.

What in the world...

@BussinessImposter do you understand what PRs do?

@3nt3 Not really honestly I just wanted to see what I could do with the code


Question about parameters and database storage

Hello, I was wondering about what these parameters meant
const Parameters kParameters{
    .db_rows = 8,
    .db_cols = 8,
    .db_record_bit_size = 16,
    .lwe_secret_dim = 1400,
    .lwe_modulus_bit_size = 32,
    .lwe_plaintext_bit_size = 8,
    .lwe_error_variance = 8,
    .linpir_params =
        linpir::RlweParameters<RlweInteger>{
            .log_n = 12,
            .qs = {35184371884033ULL,<PHONE_NUMBER>3809ULL},  // 90 bits
            .ts = {2056193, 1990657},                      // 42 bits
            .gadget_log_bs = {16, 16},
            .error_variance = 8,
            .prng_type = rlwe::PRNG_TYPE_HKDF,
            .rows_per_block = 1024,
        },
    .prng_type = rlwe::PRNG_TYPE_HKDF,
};

Does the  lwe_plaintext_bit_size have to be half the size of db_record_bit_size? Also wanted to know how the matrix that is assigned here related to the database index. Is it column-major ordering?

also wondering how large records are stored. If I want to store 32KB per record and if lwe_plaintext_bit_size is still 8, can I only store 0-256?

@b5li do you have any suggestions for how I can store and retrieve large record sizes?


chore: vulnerability fix CVE-2023-32681

PR summary
requests library was vulnerable
Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

closing as Fix is given in another PR - https://github.com/IBM/event-notifications-python-admin-sdk/pull/43/files#


uv publish package for the first time, "error: failed to query check URL"

I am trying to use uv publish to publish a new python package to a private registry.
I believe the private registry is a nexus repository.
pyproject.toml configuration
[project]
name = "my-example-package"
...

[[tool.uv.index]]
name = "pypi-publish-private"
url = "https:/mirrors.my-company.com/pypi/simple/"
publish-url = "https://pypi-publish.my-company.com/"
default = true

Command I am running:
uv publish -v --index pypi-publish-private

Output:
DEBUG uv 0.5.10
warning: `uv publish` is experimental and may change without warning
DEBUG Publishing with index pypi-publish-private
DEBUG Not a distribution filename: `.gitignore`
Publishing 2 files https://pypi-publish.my-company.com/
DEBUG Using request timeout of 900s
DEBUG Checking for my-example-package-0.1.0-py3-none-any.whl in the registry
DEBUG No cache entry for: https:/mirrors.my-company.com/pypi/simple/my-example-package/
DEBUG No netrc file found
error: Failed to query check URL
  Caused by: Package `my-example-package` was not found in the registry

I am a bit confused.

Is there something I am suppose to do before publishing the very first time?
Since the package has never been published before isn't it expected that the package is not found in the the registry?
Is my private registry not behaving as expected?

I was able to work around this by using twine to upload the package the very first time. Once the package has been uploaded once then uv publish appears to work as expected.

This might be a real problem -- tagging @konstin for when they're back from vacation.

Just tried the fix. Worked great! Thanks!


Add Testing to doc builds

I have a few ideas that I will need to go over, but I am reasonably sure we can come up with a meaningful test suite with the existing infrastructure.

Note to self: OpenShift documentation uses AsciiBinder

Note to self: We only want to build all our books the standard way, see if xmllint passes. Previewing builds is an extra.

Apparently, the rest of the team uses ci.centos.org. Investigation needed.


C.NOP/C.ADDI HINT documentation

There is an inconsistency in the way that the C.NOP/C.ADDI HINTs are documented that IMO is confusing. Here's an example of the typical way that compressed HINT instructions are documented:

C.LI is only valid when rd != x0; the code points with rd = x0 encode HINTs.

Contrast this with C.NOP/C.ADDI:

C.ADDI is only valid when rd != x0. The code point with both rd=x0 and nzimm=0 encodes the C.NOP instruction; the remaining code points with either rd=x0 or nzimm=0 encode HINTs.

Given that that paragraph is encountered in a section that documents C.ADDI* instructions, that kind of sounds like rd=0 and nzimm=0 encodes a single C.NOP while rd=x0 or nzimm=0 encode C.ADDI HINTS. The section should probably be more explicit about which are C.NOP hints and which are C.ADDI hints, IMO.

There is an related unresolved binutils question about this, as it isn't clear on the binutils side what exactly in an instruction and what exactly is an alias here.
https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/18ObEKnn4mE

I've changed the text to make it clear which hints are ADDI hints and which are NOP hints.


DVS-2827 dvs checks for ncn reboots 1.4

Description
Ports work for DVS-2827 currently in the main branch to release/1.4:  Adds a before-each hook to ensure that at least two other NCNs have DVS loaded and a running CPS pod before restarting a target NCN.  Handles a fresh install case where COS is not yet present by first checking whether the target is contributing to DVS HA before performing other checks.
Checklist Before Merging

[] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

Note on failed checks:

Links, Spelling and Style are the same pre-existing issues we saw on the PR to main
This one additionally has a failing check on licenses.  I am happy to make a ticket for this if anyone can tell me the correct JIRA proj, but I do not believe it is related to my code change.  See https://cray.slack.com/archives/C01F7HW8LBX/p1674065903217829 for more details.


Release 0.2.1 version

Also install instructions should be updated to using 0.2.1 version.

@softprops Please release new version.

@softprops ping

@softprops any update?

I've created a release from my fork: https://github.com/Philippus/base64
I'd recommend to just migrate to the Java 8 encoder available in java.util.Base64 though.


Fix StructuredBuffer usage in Metal backend

Previously, the Metal backend was treating structured buffers the same as uniform buffers - containers of a single element, rather than pointers to an array. The SimpleCompute test happened to pass because of Metal's implicit conversion from float to float4.

You're right, that was obviously broken before. The fix looks good to me; thanks!


Fix empty ECDS with Delta XDS

This was caused by only sending the Resource, and ignoring the other
fields (Name, version, etc).
Fixes https://github.com/istio/istio/issues/47227

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
ab0c6d999d1fa4522d13204bf514f27bb8cedb05
link
true
/test lint

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/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
ab0c6d999d1fa4522d13204bf514f27bb8cedb05
link
true
/test lint

gencheck_istio
ab0c6d999d1fa4522d13204bf514f27bb8cedb05
link
true
/test gencheck

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/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
ab0c6d999d1fa4522d13204bf514f27bb8cedb05
link
true
/test lint

gencheck_istio
06140459bcc6bca9f7ee0f6e530425c711aceb79
link
true
/test gencheck

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/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
06140459bcc6bca9f7ee0f6e530425c711aceb79
link
true
/test gencheck

lint_istio
06140459bcc6bca9f7ee0f6e530425c711aceb79
link
true
/test lint

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/test-infra repository. I understand the commands that are listed here.


rgbringcoder: Initial implementation.

Signed-off-by: Jon Trulson<EMAIL_ADDRESS>

Merged, thanks!


View graph for ORP value

Under ressource->Sensors details for ORP sensors (Redox) it will be fine to have a graph (ORP in mV). Same for PH

@fab33 ok, I will update. For now you can change it as double metric type. You will get this option when you edit sensorVariable.


All the work from the IOOS code sprint

Sorry for a bunch of stuff all in one PR -- if you don't want all (or most) or it, I can split it up, but this is what's here:

Set up a pixi config -- it can optionally be used for development, etc, but it is used for the CI testing -- which really makes things easy. -- I did add some notes on how to use it to the README.

Set up gitHub workflows to test -- a matrix of Windows, Linux, and Mac (not ARM Mac, but I think that can be added fairly easily) and Python 3.9 -- 3.12 (3.9 is failing, but I think there's a change in main that will fix that -- and maybe we can drop it anyway)

Added some point in polygon performance testing -- kept it there for posterity

Refactored the existing (few) tests to use pytest parametrize

Added a couple more tests for the UGRID stuff.

I think that's it :-)

All in favor getting rid of the 3.9 tests and cutting that version from support? That seems to be the only failure currently

I think they would pass for 3.9 if we brought in the latest changes @omkar-334  made.
But yes, I think we should dump 3.9 I'll do that in the CI soon.

Thanks!


Provide example data on definition properties

By decorating a definition property with an  xml comment, you will get proper 'live' sample data in the example section of a response.
Hope this is okay, not done many PRs before :-)

Looks good, I like the idea!
And the <example> is not a new tag:
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/xmldoc/recommended-tags-for-documentation-comments

Yeah thats why i did it that way, as i saw it being emitted into the XMLComments; i was originally doing a custom attribute in my own OperationFilter and thought there may be a more native way to do this.

+1 For getting this merged

+1 from me as well on this. Not only will this make it easier to get more rich information in the UI, but also improve documentation a lot for many. At least will it help the team im on here tremendously.
This might also help on the issue reported on #1137, which we also are experiencing on many of our apis, by doing this correctly natively.

+1 for this


fix secure_mnemonic for 160, 192, 224 and 256 bits

This fixes #34

LGTM! I just submitted this PR to you Jimmy with minor tweaks (merge them both?):
https://github.com/buidl-bitcoin/buidl-python/pull/36/


Tabgroups are lost if computer crashes or reboots - Now Permanently!

Tabgroups are lost after some crashes/reboots. I can reproduce this by powering off my PC (Win 10).  I then have to recreate them from the bookmarks so lose anything new I haven't specifically bookmarked before the crash.
My PC is a Ryzen build, and does crash regularly when trying to OC ram, but it can also happen from power loss.
I'm now in a position where I can't create groups at all and it's not creating them automatically when I open a new window, so I've lost ALL functionality.

This is what it looks like after I create a new group and give it a name.
I should add that I have tried removing the add-on and re-installing but still doesn't work. Also disable and re-enable, same result. Something does appear to be in the export file which I'm happy to fwd to you, but it does NOT contain all my group names or URLs.
The file storage is now called storage.js-xx.corrupt, there are many of these up to xx=13.  All of these files contain nothing but NUL chars.

9 groups, so far no problems!

Many thanks - all seems to be working really well. I think this was at least in part caused by some problems with FF57.


Add Ruby/rvm version plugin

Similar to #57 create a plugin for ruby/rvm version information prompt.
Use rvm/rbenv if available. Display in the following format:
 ◆ 2.3.3 (1.27.0)

Cache version information in the setup phrase.
This is a great opportunity for anyone interested in contributing.

Hi, I'd like to give this a shot. Can I take this issue?

It will probably be useful if the current rvm gemset is also displayed. What do you think?

@reuben453 I'd have it under a configuration variable, something like:
GEOMETRY_RUBY_RVM_SHOW_GEMSET=[true|false]

Good work so far in #93

Should this be closed now?

@reuben453 you're right, closing.


Parsing string to integer accepting '0x' + hexadecimal

In many cases, it is useful for a program that parses integers (e.g. from the command line) to accept both decimal and hexadecimal constants, by letting the user prefix the latter with 0x.  Currently, FromStr::from_str (also the destination of str::parse) only accepts base 10; from_str_radix allows an arbitrary base to be specified, but doesn't have any special magic to parse prefixes.
If I were writing from_str from scratch, I would suggest having it accept 0x, perhaps along with 0o and 0b like Rust source, because even if many applications don't have any particular reason to expect hexadecimal, there's very little advantage to rejecting it*.  At this point, I guess that would be something of a breaking change, so a new method would be needed; still, I claim such a method belongs in the standard library for the same reason.  Alternatively, from_str_radix could accept radix 0 like some other languages' equivalents, although this seems like a hack.
Other languages' behavior:

C atoi only accepts base 10.
The C strtol family has a mandatory base parameter; base=0 is decimal by default but allows 0x and 0755 (octal); base=16 accepts 0x
Python int() is base 10 only by default, but has a base parameter; same behavior as C except 0b and 0o are also accepted
Ruby: '0x123'.to_i is 0, but Integer('0x123') is 291.  I have no idea.  The latter seems to accept the same as Python.
JavaScript: parseInt by default accepts 0x and, in some browsers, 0-for-octal, which ES5 says not to.

(I certainly don't propose interpreting leading zeroes as octal.)

One possible reason to reject alternate forms would be to give each integer a unique input representation, but of course -0 and 0, and 008 and 8 parse to the same value.

I think we should expose some mechanism to parse these prefixes. I'm not convinced that FromStr::from_str() is that mechanism, but I don't have a particularly strong opinion about that. I'm concerned that automatically parsing prefixes might be surprising to some people, because those prefixes really only make sense to developers and aren't so familiar to other users (and this function may be used to parse user input, or to parse integral values in data formats that don't allow for prefixes). But I'm not sure that parsing prefixes like that would necessarily be a problem for anybody either. And of course anyone that wants to guarantee that they don't parse the prefixes can use from_str_radix() instead (which will of course not parse prefixes).

An alternative to consider is an extension to FromStr that adds an associated type Config and a method from_str_config(&str, Config) (tentative name) that allows types to provide a generic mechanism to configure parsing. The integral types could vend a struct for Config that has a field parse_prefix that enables prefix parsing (and perhaps a radix field of type Option<bool> as well). Then from_str(s) could be considered equivalent to from_str_config(s, <Config as Default>::default()) (although it can't literally be that since it's already stabilized). I can't decide if this is  a good idea or just overly complicated. It depends on whether there are any other types that want to have options for string parsing (and whether there's any actual benefit to doing this in a standardized way in this trait, instead of just adding ad-hoc methods to each type that wants to be custom).

Incidentally, we don't currently support hexadecimal float literals, but if we wanted to add support for those, that would have the same concerns that parsing prefixes on integral literals does (and may want a way to enable/disable the prefix handling when parsing strings).

I’d prefer the "default" FromStr impl for integer types not to do this. This can be useful, but it should be explicit / opt-in.
When this kind of thing is default/implicit, we end up with headaches like 0x7f.0.0.1 being accidentally a valid IPv4 address, but only on some systems. https://github.com/w3c/web-platform-tests/issues/1104

Hah, nice example. That's a really good point. I'm now in full agreement that it should be opt-in behavior.
The simplest change here would be to follow C's lead and allow a 0 value given to from_str_radix() to mean autodetect, but I agree with @comex that it's kind of an ugly hack. We could make the radix an optional value, but that makes the common case (of providing a radix value) more awkward, and it's not clear if this actually has any benefit over just using 0.
I am still a bit partial to my "alternative" idea from before, of having a from_str_config() method. This would allow us to provide a way to control not only integral prefix parsing, but whether a leading 0 should be treated as octal or whether that should require 0o, and similarly whether we should accept a binary prefix of 0b. But I am a bit worried that this is straying to far towards behavior that should be done with a "real" parser.

So,what's the decision?

I think it would be a breaking change to do this now in existing APIs. But new APIs could be added.

BTW with Ruby:
2.3.3 :001 > '0x123'.to_i
 => 0
2.3.3 :002 > '0x123'.to_i(16)
 => 291

The default parser should be simple and generic. Having special cases for radix 2, 8 or 16 is terrible when we don't need it.
Adding this feature is simple while removing it is not.
If required, implementing another parse_with_prefix() is better. Though I think it should not be a part of std.

For future reference: use from_str_radix

For future reference: use from_str_radix

Why?

Because you can use this example for example.
Cheers :smiley:

Right, that misses the point of this issue.  The ask was that there would be one function that will handle common prefixes.

Ah, I see more something along the lines of parse_int::parse()

I think this is probably what most people want:
fn parse_int(s: &str) -> std::result::Result<u64, std::num::ParseIntError> {
    if let Some(s) = s.strip_prefix("0x") {
        u64::from_str_radix(s, 16)
    } else if let Some(s) = s.strip_prefix("0o") {
        u64::from_str_radix(s, 8)
    } else if let Some(s) = s.strip_prefix("0b") {
        u64::from_str_radix(s, 2)
    } else {
        u64::from_str_radix(s, 10)
    }
}

Playground
I had a look at the parse_int() crate and it seems ok too. It also supports stripping _, and it uses num_traits to make it generic. Also it can optionally support 0777 style octals 🤮.

I am the author of parse_int where you can enable the "implicit-octal" feature if needed, but it is not enabled by default. Feel free to open an issue if needed on the repo:
https://gitlab.com/dns2utf8/parse_int


Support for multi-labeled datasets?

Hello,
does datumaro have the possibilities (also by writing custom plugins) to support multi-labeled datasets?
For example using datasets like Fashionpedia which are using a custom coco version with one category_id and multiple attribute_ids per image?
Would it also be possible to write custom plugins to allow a label remapping from a single-labeled dataset (only one category_id per image) to a multi-labeled dataset and ideally allow the merging of multiple multi-labeled datasets afterwards?
As I'm very new to datumaro and the concept looks very promising, I would be interested to know if datumaro could support datasets like this, even though I would have to write custom plugins for that. But if not I'm just scared of wasting my time.
Thanks!

Hi. Unfortunately no, multiple label sets are not supported. A DatasetItem can have multiple labels, but they must be related to a single set of labels. However, there is support for annotation attributes that can be used instead. They are just string or number values attached to an annotation - a bbox or a label. For the dataset you mentioned you'll need to write a custom plugin, take a look at COCO format implementation.


Cannot find FileSaver.js with in-repo-engine

I have an in-repo-engine that is trying to load ember-cli-file-saver but am seeing:
no such file or directory, open '/somerepo/tmp/source_map_concat-input_base_path-yZSiVeUk.tmp/undefined/FileSaver/FileSaver.js'

Looking around it seems that switching from loading FileSaver via bower to npm is the right course of action.

Should be fixed with 1.0.0 !

Thank you!


Update roadmap.md

cc @markgrover @philippemizrahi

we should include all our upcoming planned features to provide the transparency for the external communities.

Looks like what's stated in these few slides I just shamelessly clipped from the new presentation you just linked to in the README - might be a good beginning: 😄
https://www.slideshare.net/JrnAHansen/clipboards/my-clips

thanks @jornh  :) cc @markgrover @philippemizrahi

I guess with https://github.com/lyft/amundsenfrontendlibrary/pull/235 (and it’s 🐑 clone in the umbrella repo) this is resolved?

Yep. https://github.com/lyft/amundsen/pull/20


Feature/python3 refactored

Offering up this port to python3 with a few items cleaned up.
Specifically:

Update dome9ApiV2Py.py to python3 compatibility with Futurize
Update runSyncAssessment.py to python3 compatibility with Futurize
Include .gitignore file, excluding compiled python files
Remove pervious complied python files
Make mild PEP8 revisions (spaces vs tabs and a few other things)
Update dome9ApiV2Py.py to use private naming for private defs.
Create requirements.txt to make deployment easier for consumers
Update README.md to reflect requirements.txt

No tests to run but it looks sane in both 2.7 and 3.7 in my world.

@cfir ; don't know if you saw this PR.

@nomadicj ty , soon we'll ship a py3 supported version


ECO-987: Update Global State Documentation

REF: https://casperlabs.atlassian.net/browse/ECO-987
CHANGELOG:

Moved the Keys section from Global State to Serialization Standard
Updated Keys to the current model
Updated Block Structure to reflect recent changes
Created a new page dedicated to the explanation of URefs

@darthsiroftardis @EdHastingsCasperLabs I added 5 commits to clean up spelling, grammar and links (mostly outside of Karan's changes):

execution-semantics.rst dce140f922f2aecb27a432c9bf72779f1cd11912
block-structure.rst 6c2c35e2a29a4b238259551fb13885a01cf7591e
uref.rst 19fbda58c6bd506864fbb916ceee423d8c60871d
global-state.rst 52b47b83f8dacbc1a700da57a37480f0001488c2
serialization-standard.rst c75a74cf9f1c08a53ea910bbd23472bc2015dc51
Please double check the git links in execution-semantics. Thank you!

@ipopescu : yes, protobuf isn't a thing anymore in our platform, so any reference to it can either be repointed to the newer logic / docu, or just removed.

@ipopescu : yes, protobuf isn't a thing anymore in our platform, so any reference to it can either be repointed to the newer logic / docu, or just removed.

Thanks Ed! I'll prepare a different PR to remove all mentions of the protobuf.


Show speed in km/h

I don't have the confidence in Objective C to add an option for this, so here's a little guide to change the mph to kmph in the code. I added a decimal point to it too.

Open GPSLogger.xcworkspace in Xcode and navigate to GPSLogger/FirstViewController.m
Change on line 124 int to float (2 times), remove round() and change 2.23694 to 3.6.

from int speed = (int)(round(location.speed*2.23694));
to float speed = (float)(location.speed*3.6);

Change on line 126 @"%d" to  @"%0.1f".

from self.locationSpeedLabel.text = [NSString stringWithFormat:@"%d", speed];
to self.locationSpeedLabel.text = [NSString<EMAIL_ADDRESS>speed];

Change the labels containing mph to km/h on lines 134 to 144.

from self.motionTypeLabel.text = @"mph, walking";
to self.motionTypeLabel.text = @"km/h, walking";

Change on line 222 MetersToMiles to 0.001

from self.tripDistanceLabel.text = [NSString<EMAIL_ADDRESS>[GLManager sharedManager].currentTripDistance * MetersToMiles];
to self.tripDistanceLabel.text = [NSString<EMAIL_ADDRESS>[GLManager sharedManager].currentTripDistance * 0.001];

Navigate to GPSLogger/Main.storyboard, and in the graphic interface, look for the main view, and click a few times on 'miles' in the trip area, to change it to 'km/h'. (This changes that file on various places, according to Git, but I guess that's ok.)
Rebuild app.

note This is only changing the display of the speed in the app, not what the app stores.

There is a way to use the system setting to determine the units shown, NSLocaleUsesMetricSystem. The app should read that value and show the appropriate units.


Run-now with additional artifacts.

/cc @ssalinas

This got folded into https://github.com/HubSpot/Singularity/pull/1650 , closing in favor of that one


add README.md

Improve README.md

Add a description from your project here.
reason why we dont use zammad.org integrations/ldap/

Mapping / Synchronizing organizations is not possible
Nested groups are not supported.
When a user originates from an LDAP server, Zammad will try to verify the login credentials against LDAP first --> no SSO

@rowe42 : Please update documentation as far as possible in branch :  https://github.com/it-at-m/zammad-ldap-sync/tree/documentation


Files Not Found on CentOS

We have a the configuration below which works fine on OS X using karma-remap-istanbul 0.1.0:
    remapIstanbulReporter: {
      src: 'reports/coverage.json',
      reports: {
        lcovonly: 'reports/ts-ut.lcov',
        html: 'reports/html'
      },
      timeoutNotCreated: 5000,
      timeoutNoMoreFiles: 1000
    },

But on CentOS it fails with 'Could not find any specified files, exiting without doing anything'. I have tried CentOS 7 and 6.5. Same result.
I put in an issue with chokidar:
https://github.com/paulmillr/chokidar/issues/514#issuecomment-235973032
But the owner thinks that the settings being used by karma-remap-istanbul might be the issue.

I just tried on an Ubuntu 16 box and got the same result.

Should be fixed in 0.2.1.


[TIR][Transform] Clear buffer_map during MakeUnpackedAPI

This mimics the behavior in MakePackedAPI, and is assumed to be the case for some codegens.

@Lunderberg I think we make use of this in following passes and I'm unsure why make packed API decides to clear it?

@Mousius Can you check the latest commit on this PR?  I didn't try to re-order the passes, but reading from the BufferStore/BufferLoad objects instead of the buffer_map resolved the test cases I ran locally.

To me, the buffer_map is an indicator for how a function should later be lowered, and what buffers should be defined as part of the lowered function. Once it has been used, then it makes sense for the resulting function to have an empty buffer_map, because no further lowering is required. After #9727, the buffer shape/size could still be accessed by later passes find finding the BufferLoad or BufferStore object that makes use of a parameter, rather than searching in the buffer_map itself, or the passes could be moved to an earlier stage of lowering.

Aha! Makes perfect sense, thanks for the explanation! I figured that was why it was in draft, being a bit nosey as I remember wondering about it when I was writing MakePackedAPI 😸

The fix makes sense to me, can we either make use of get_loads and get_stores or move the collect_buffer_map function to utils.py?

Certainly.  It is now pulled out and documented, with defined behavior for buffers that share a backing Var.

I figured that was why it was in draft, being a bit nosey as I remember wondering about it when I was writing MakeUnpackedAPI :smile_cat:

No worries at all, and I wouldn't consider it nosey, either.  It's the exact type of comment I was hoping for, as there wasn't an immediately obvious reason for the asymmetry between packed and unpacked.

Also can we add to the documentation of the Pass the intention behind clearing it?

Good call, and will do.

Thanks for making the API that little bit more consistent @Lunderberg 😸


"Stand Alone" containers

I am trying to build containers that sit on the network like "regular machines", looking at /usr/lib/x86_64-linux-gnu/lxc/lxc-net there always seems to be some nat magic involved but I am not sure this script is used to build new containers.
To achieve my goal I created a new bridge (/etc/network/interface dump below) and assignated it to a container with
lxc config set containerName raw.lxc 'lxc.network.link = br0'
the container starts but can't seem to get an address from the dnsmaq dhcp server :
the dnsmasq log output shows a DHCPDISCOVER(br0) but the DHCPOFFER(br0) is never received by the container.
Am I on the wrong path and are iptable rules always needed ?
Some context :
The goal would be to create containers with a network configuration that put them as first class citizen of the network they are in while assigning their IP in a reserved range with dnsmaq to also get name resolution from dnsmasq.
Bridge configuration :
# The primary network interface
auto eth0
iface eth0 inet manual

auto br0
iface br0 inet static
        address <IP_ADDRESS>
        netmask <IP_ADDRESS>
        network <IP_ADDRESS>
        broadcast <IP_ADDRESS>
        gateway <IP_ADDRESS>
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers <IP_ADDRESS>
        dns-search mondomaine.com
        bridge_ports eth0
        bridge_stp off

Thanks a lot for your time

Join us on IRC Freenode #linuxcontainers for support.

But to answer your question, use "lxc config edit "
And paste something like that

Thanks a lot for you answer, I went to theIRC  channel before posting but nobody was available to answer at that time, I'll do my homework with your clues and come back to the IRC after that.
I did not know the nictype : bridged since I based my knowledge of the various type of connection on the otherwise excellent blog post http://containerops.org/2013/11/19/lxc-networking/ that did not mention it ;)

You can't really configure LXD by following LXC documentation :)
For LXD, what @pcdummy told you is right, you want to edit the device definition of the container or of the default profile.
Obviously if you're creating your own bridge, then there won't be a DHCP daemon running on it unless you manually set on up.
Closing this as there's no evidence of an actual LXD issue there.


groupingContainer and groupBox were both exporting functions called G…

groupingContainer and groupBox were both exporting functions called GroupingContainer, they were both registering with the same name as well. The names both widgets register with and the name of the exported functions have been changed.

https://github.com/dls-controls/cs-web-proto/wiki/How-to-make-a-Widget
Have a read, I suspect it is a little out of date. I think you will be making a few widgets.

https://github.com/dls-controls/cs-web-proto/wiki/How-to-make-a-Widget
Have a read, I suspect it is a little out of date. I think you will be making a few widgets.

Will do, will finish the documentation for the current widgets first thing tomorrow morning, then start on that.


[Feature Request]: Electron compatibility

I'm using Carbone with Electron, if I run the app from command line everything go well, if i wrap the app with electron packager to get an .exe, Carbone don't work anymore. There's something I can do? thank you

Hi @Rick9595, thank you for using Carbone!
I have never tried an Electron app with Carbone, do you have any logs?
Are you using Carbone on the server side?
If you are exporting PDF, did you install Python and OpenOffice?

Hi, thank you for reply, I don't get any error or callback from "carbone.render", i'm using openoffice for the conversion, it not work only if I wrap the app with electron packager, otherwise everything go well
thank you

Can you share with me a sample project reproducing the issue?
My email is available on my Github profile.

The problem was probably coming from the "asar" option which creates an archive of the source code.
By disabling it, Carbone is working well.


New README badges

This PR replaces the README badges with ones from www.shields.io. Those badges have style options that have a more modern look and fit our logo better.

These look nice! 🚀


Punct spacing is not preserved

During testing custom punctuation in syn, i have found that it is impossible to write tests using quote.
Debugging lead me to the minimal test:
#[cfg(test)]
mod test {
    use quote::quote;
    use proc_macro2::{TokenTree, Spacing};

    #[test]
    fn it_works() {
        let mut tts = quote!(<>).into_iter();
        let TokenTree::Punct(c) = tts.next().unwrap() else { panic!() };
        assert_eq!(c.spacing(), Spacing::Joint)
    }
}

Output:
thread 'test::it_works' panicked at 'assertion failed: `(left == right)`
  left: `Alone`,
 right: `Joint`', src/lib.rs:10:9

If i understand correctly, Rustc will produce Spacing::Joint for similar token stream.

I don't know any other way to implement this, but I would be prepared to consider a PR if someone else has a way.

Thanks, for fast response.
Maybe implementation on procedural macro can solve this?
Is there any reason to keep quote declarative?
I have found few issues https://github.com/dtolnay/quote/issues/82 https://github.com/dtolnay/quote/issues/113 that mention, that the main purpose is the speed.
Do you have some repo for benchmarks(or guide how one can measure perfomance of its own macro)? (very interested to apply it for my project)


Bound parameters is back under certain conditions in QuantumCircuit.

Environment

Qiskit Terra version: qiskit-terra': '0.20.0'
Python version: 3.8
Operating system: macOS

What is happening?
If you decompose the parameterized quantum circuit with control and inverse, the parameters will be back.
How can we reproduce the issue?
Code
from qiskit.circuit import Parameter
from qiskit import QuantumCircuit

qc = QuantumCircuit(1)
param = Parameter("old")
qc.p(param, 0)
controlled = qc.control()
new_param = Parameter("new")
qc = QuantumCircuit(2)
qc.append(controlled.assign_parameters({param: new_param}).inverse(), qc.qubits)

print(qc)
print(qc.decompose().decompose())

Output
     ┌─────────────────────────┐
q_0: ┤0                        ├
     │  c_circuit-0-11_dg(new) │
q_1: ┤1                        ├
     └─────────────────────────┘

q_0: ─■────────────
      │P(-1.0*old)
q_1: ─■────────────

What should happen?
The parameters of both circuits should be new.
Any suggestions?

I think the problem is that the ControlledGate object inside controlled uses the ControlledGate.base_gate to reconstruct the inverse, but we don't propagate the parameter update down to ControlledGate.base_gate.
from qiskit.circuit import Parameter
from qiskit import QuantumCircuit

qc = QuantumCircuit(1)
param = Parameter("old")
qc.p(param, 0)
controlled = qc.control()
new_param = Parameter("new")
assigned = controlled.assign_parameters({param: new_param})

cgate = assigned.data[0][0]
print(cgate)
# prints: Instruction(name='ccircuit-0', num_qubits=2, num_clbits=0, params=[Parameter(new)])
# meaning that ControlledGate.params is updated to the new parameters

print(cgate.base_gate.definition.parameters)
# prints: ParameterView([Parameter(old)])
# to construct the inverse, the ControlledGate.base_gate is used which still contains the old parameter.

print(cgate.base_gate.definition.draw())
#    ┌────────┐
# q: ┤ P(old) ├
#    └────────┘

Hence to fix this, we would have to bind parameters also in the base_gate if we hit a ControlledGate in the QuantumCircuit._assign_parameter method.

Coincidentally I have been working with someone this week who had come across, what I think is the same issue, when using the machine learning SVC and QuantumKernel. They had created a controlled ZZfeatureMap and used that as the feature map for the kernel. That fails when running the SVC with a message about "par_y" not being found when binding. These happen to be the parameters of the inverse part of the circuit the kernel uses, which it creates from the given feature map and re-assigned the parameters to par_y.
Now printing the circuit and its parameters, after it was created, it had par_x and par_y as expected. It was after transpilation in the case of the QuantumKernel that the circuit 'lost' the par_y and then failed when binding; and printing the parameters showed par_x and x, rather than par_x and par_y.
I had been going to create an issue after I created a smaller working sample. But it seems this describes the same issue and the person I was working with on their problem noticed this a few mins ago. Hence for now I think this is good and we can check with the QuantumKernel when a solution is found.


style: improve tabs and breadcrumb icon style

Types

[x] 💄 Style Changes

Background or solution
before:

after:

Changelog

improve tabs and breadcrumb icon style

/publish

dark:

light:


Ramen - Tab Switch Stuck

When switching to the Data and Code Tabs and then switching back to the Ramen Tab the graph focus appears to be stuck for numbers.

this pull requests fixes this issue
https://github.com/louisVottero/vtool/tree/ramen_fixes


slopeclockpp: avoid reusing background colour for clkinfo

@eyecreate @myxor @hughbarney what do you think of this? I feel like there might be a better way to ensure the clock info is always visible

Improved the fix, much better. Will merge after a few to do a bit of testing and to give you chance to take a look

Been working great, merging


[SR-4231] Add diagnostic (& fix-it) for mixed syntax availability attribute

This adds a specific diagnostic when both shorthand and non-shorthand specifications are mixed in the same availability attribute. For example: @available(OSX 10.0, deprecated: 10.12).
Current error:
@available(OSX 10.0, deprecated: 10.12)
//                             ^
// error: expected version number
// error: expected declaration

New error:
@available(OSX 10.0, deprecated: 10.12)
//                   ^
// error: 'deprecated' can't be combined with shorthand specification 'OSX 10.0'
// error: expected declaration

If (and only if) there is only a single platform version constraint, that is followed by ‘deprecated’, ‘renamed’, etc. but not ‘introduced’, then it also offers a fix-it to insert , introduced: in the platform version constraint, turning:
@available(OSX 10.0, deprecated: 10.12)

into:
@available(OSX, introduced: 10.0, deprecated: 10.12)
// insert:    ^-----------^

Resolves SR-4231.

I've tried to keep the comments focused on why something is done, but I'm not sure if I ended up
with a good comment to code ratio or if it's too much.

@swift-ci please smoke tes

@swift-ci please smoke test

@swift-ci please smoke test

Thanks @d-ronnqvist!  Don't worry yourself with the recovery thing for now.  I've got one last request then I think this can be put in.

@swift-ci please smoke test

@swift-ci please smoke test

Thanks @d-ronnqvist!
⛵


[ez] Minor code sample updates

#92  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Disabling/configuring loading spinner

Is your feature request related to a problem? Please describe.
I want to disable loading spinner, especially in production. This is especially important to me because this spinners usually is shown on language change. In my case language is part of url, so language change actually changes route. I don't want to show loading spinner, especially on language change.
Describe the solution you'd like
We could add a way to disable spinner, maybe a flag to static.config.js? I would be also nice to allow to configure spinner. Right now it is an blue spinner on a blank page. Not only it should be possible to provide own spinner implementation, but also I guess it should be possible to inject in anywhere, so it doesn't override the whole page
Describe alternatives you've considered
I tried to use  minLoadTime: 0 in static.config.js, but it would be kind of cheating which doesn't work anyway.
Additional context
n/a

In v6 you can configure the spinner on Routes, SiteData and RouteData with the Loader prop. Unfortunately this is undocumented and will be removed next version on favor of suspense. So proceed with caution.
Tanner Linsley
On Mar 21, 2019, 3:31 PM -0600, Konrad Lisiczyński<EMAIL_ADDRESS>wrote:

Is your feature request related to a problem? Please describe.
I want to disable loading spinner, especially in production. This is especially important to me because this spinners usually is shown on language change. In my case language is part of url, so language change actually changes route. I don't want to show loading spinner, especially on language change.
Describe the solution you'd like
We could add a way to disable spinner, maybe a flag to static.config.js? I would be also nice to allow to configure spinner. Right now it is an blue spinner on a blank page. Not only it should be possible to provide own spinner implementation, but also I guess it should be possible to inject in anywhere, so it doesn't override the whole page
Describe alternatives you've considered
I tried to use minLoadTime: 0 in static.config.js, but it would be kind of cheating which doesn't work anyway.
Additional context
n/a
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@tannerlinsley thx, I did the following: const Loader = () => null; It works, but ideally what I would like to have is not to show loader at all in some cases. So lets say I am on route /en/about-us and I switch language so I push new route /pl/about-us . Is it or will it be possible to just keep /en/about-us visible and switch /pl/about-us when it is available? Or to rephrase, to disable loader, not to make it blank.

What you’re describing is suspense 😉. Back in v4, we did routing in a similar way. We monkey patched and delayed actual page navigation until the data and template were resolved. While this looked like suspense, it was far from it and produced a TON of bugs. This is why we moved to the new fallback/loader strategy.
So, even if you were to disable or render a blank loader, react will still attempt to load the new page and you’ll see a splash of white until the data/template resolve. There isn’t much we can do here until async react and true suspense ship.
HOWEVER, there is another remedy to your problem. React Static will not show a loader if the data has already been preloaded. If you can detect early which language they are switching to, you might be able to call await prefetch('/lang/page’). When that promise resolves, it means any navigation to it will be immediate and not show a loader.
I hope this is making more sense.
Tanner Linsley
On Mar 22, 2019, 3:48 AM -0600, Konrad Lisiczyński<EMAIL_ADDRESS>wrote:

@tannerlinsley thx, I did the following: const Loader = () => null; It works, but ideally what I would like to have is not to show loader at all in some cases. So lets say I am on route /en/about-us and I switch language so I push new route /pl/about-us . Is it or will it be possible to just keep /en/about-us visible and switch /pl/about-us when it is available? Or to rephrase, to disable loader, not to make it blank.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@tannerlinsley thx for detailed answer. I cannot wait for true async React, especially on server side.
In the meantime I will do the following. The problem is that I pass language to data to every component, like in #475 . Maybe I could use createSharedData because actually each component  will have exactly the same data apart from language, because I use i18next for translations. So this would solve all data props apart from language. And I was just enlightened that I don't really need to have language passed as data, because I can read it from path with React router. So then I won't have spinner because no new data will need to be fetched on lang switch :)

Perfect :) That’s a much better solution for now.
Hopefully in v7 we can figure out the right plugin points for this and just make it plug and play.
Tanner Linsley
On Mar 22, 2019, 7:13 AM -0600, Konrad Lisiczyński<EMAIL_ADDRESS>wrote:

@tannerlinsley thx for detailed answer. I cannot wait for true async React, especially on server side.
In the meantime I will do the following. The problem is that I pass language to data to every component, like in #475 . Maybe I could use createSharedData because actually each component will have exactly the same data apart from language, because I use i18next for translations. So this would solve all data props apart from language. And I was just enlightened that I don't really need to have language passed as data, because I can read it from path with React router. So then I won't have spinner because no new data will need to be fetched on lang switch :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

:+1:  thx again and I am sure this library is gonna be even more awesome than it is now. I also considered Gatsby but I don't really wanna use graphql for not remote stuff. I am sure that with future react with the possibility to pause and stop rendering will allow us to make such a flexible and simple plugin API which could be used for anything, including plug and play i18next.

@tannerlinsley apologies for asking here as it seems already closed, but I have a weird issue where the loader div just wraps around the first div element on the page (that happens after building and on page refresh). Its a bit annoying because it breaks mostly the page layout, so my question would be how I can disable the Loader and if it's possible to configure it (you mentioned above that is configurable but not documented).
Thanks in advance.


Redshift - external table cannot be queried

Description
Hi,
Here is an example of a very simple select statement on an external table that does not complete.
Works fine on the command line.
select id from "oneflow"."staging_external"."core_api_account_billing" limit 1;

DBeaver Version
Version <IP_ADDRESS>405191503 Community version
Operating System
macOS 14.2 (23C64)
Database and driver
Redshift
Not sure how to look up the driver.
Steps to reproduce
Create an external table, for instance via a parquet file and do a simple select query on the table.
Additional context
No response

Hello @Auric-Manteo, please provide the error and log details.

Hi serjiokov,
I truncated the logs and only executed the relevant statement which I cancelled manually after it ran for 40 min.
dbeaver-diagnostic-info-1718779279414.zip

Just to clarify, this query returns in seconds if I run it via psql on the command line.

@serjiokov I can't remove the wait for response label myself I think.
Is this enough information or do you need anything else?

I have a possibly related issue where the query takes forever and the status says "Discover owner entity...".
I followed the setting recommended here and now the query returns in less than a second:
https://github.com/dbeaver/dbeaver/issues/4193

It seems like that is also a workaround for the original issue described in this ticket.

Sorry for the late response.
unfortunately, I cannot reproduce it against 24.2.5. Is the issue still actual for you?

It's been a while since there has been an update here. If the issue is still present, please let me know.


second demo issue

@JuliaRegistrator register

Error while trying to register: "Pre-release version not allowed"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/80145
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.1 -m "<description of version>" 60c5f273d1a840ab054a57fdc21c69d5f6f5b0d5
git push origin v0.0.1


Add "agile testing vs waterfall appraoch"

link to wordpress website where differences are clearly shown

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

hacktober T-shirt

@PatiPavanSai Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality >standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


Button text overflows with "larger text" accessibility settings on iOS

On iOS if a user is using larger accessibility sizes, the text on the buttons overflows.

same

same