TESTNET terraform destroy results in errror

Terraform deployment (k8s) active
/opt/MyTrunk/terraform/my-first-k8s$ terraform show                                                                                130🚫
\# grid_kubernetes.k8s1:
resource "grid_kubernetes" "k8s1" {
    id                 = "22b6756c-ad07-4003-98da-b47265ee789b"
    network_name       = "network12346"
    node_deployment_id = {
        "2"  = 451
        "43" = 452
        "44" = 449
        "49" = 450
    }
    nodes_ip_range     = {
        "1"  = "<IP_ADDRESS>/24"
        "2"  = "<IP_ADDRESS>/24"
        "4"  = "<IP_ADDRESS>/24"
        "42" = "<IP_ADDRESS>/24"
        "43" = "<IP_ADDRESS>/24"
        "44" = "<IP_ADDRESS>/24"
        "45" = "<IP_ADDRESS>/24"
        "46" = "<IP_ADDRESS>/24"
        "47" = "<IP_ADDRESS>/24"
        "49" = "<IP_ADDRESS>/24"
    }
    ssh_key            = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAOP0h6VImNcxnIBRMoMfbMfb0xwGHDlaPxZ+nu0CL8ATJekVDHDLMGEPdvACfHBe0sqIw/l6jqoEMR4Dzhjgm4bVEUBVEnG1FvkeNB59sT2DOxDCZuqJvjx2M1bJlH8AR/JQXxUQ+zvfTbavc4/zfCuJm4PYNUsmEt/IQmRwLznGOkoJbwYLhKCC3ykZd0EGpmCWgUUYn0ihaaYkyrliQi5Ny00x0s6jOIJg0CG2Xh5xcrkhOfCZMxZAB+/LGQpZ3tu+Cy5jRf8V/JZ8XQmtYM2GmBUZ1KGcMcsGzrtuudn13JeYLtWJBw6A7Q3Fb7dQSCMLC9UA0uMSZk67M6DFV john@RescuedMac"
    token              = "12345678910122"

    master {
        computedip = "<IP_ADDRESS>/24"
        cpu        = 2
        disk_size  = 23
        flist      = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
        ip         = "<IP_ADDRESS>"
        memory     = 4096
        name       = "mr"
        node       = 2
        publicip   = true
    }

    workers {
        cpu       = 2
        disk_size = 15
        flist     = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
        ip        = "<IP_ADDRESS>"
        memory    = 4096
        name      = "w0"
        node      = 43
        publicip  = false
    }
    workers {
        cpu       = 2
        disk_size = 14
        flist     = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
        ip        = "<IP_ADDRESS>"
        memory    = 4096
        name      = "w2"
        node      = 44
        publicip  = false
    }
    workers {
        cpu       = 2
        disk_size = 13
        flist     = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
        ip        = "<IP_ADDRESS>"
        memory    = 4096
        name      = "w3"
        node      = 49
        publicip  = false
    }
    workers {
        cpu       = 2
        disk_size = 13
        flist     = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
        ip        = "<IP_ADDRESS>"
        memory    = 4096
        name      = "w4"
        node      = 49
        publicip  = false
    }
}

# grid_network.net1:
resource "grid_network" "net1" {
    access_wg_config   = <<-EOT

        [Interface]
        Address = <IP_ADDRESS>
        PrivateKey = 8GkHO3uF/O3x7TUX0xpHnn67hph2+tO9+NVzOnBl23g=
        [Peer]
        PublicKey = LyryUPen5US+gECByGvCA5mzpLFAoSrtSQNg2fgVTwU=
        AllowedIPs = <IP_ADDRESS>/16, <IP_ADDRESS>/16
        PersistentKeepalive = 25
        Endpoint = <IP_ADDRESS>:2749

    EOT
    add_wg_access      = true
    description        = "newer network"
    external_ip        = "<IP_ADDRESS>/24"
    external_sk        = "8GkHO3uF/O3x7TUX0xpHnn67hph2+tO9+NVzOnBl23g="
    id                 = "ab97364a-0d67-4c69-b3e9-8d96357c36e0"
    ip_range           = "<IP_ADDRESS>/16"
    name               = "network12346"
    node_deployment_id = {
        "1"  = 444
        "2"  = 445
        "4"  = 439
        "42" = 446
        "43" = 447
        "44" = 440
        "45" = 441
        "46" = 448
        "47" = 443
        "49" = 442
    }
    nodes              = [
        2,
        4,
        42,
        43,
        44,
        45,
        46,
        47,
        49,
    ]
    nodes_ip_range     = {
        "1"  = "<IP_ADDRESS>/24"
        "2"  = "<IP_ADDRESS>/24"
        "4"  = "<IP_ADDRESS>/24"
        "42" = "<IP_ADDRESS>/24"
        "43" = "<IP_ADDRESS>/24"
        "44" = "<IP_ADDRESS>/24"
        "45" = "<IP_ADDRESS>/24"
        "46" = "<IP_ADDRESS>/24"
        "47" = "<IP_ADDRESS>/24"
        "49" = "<IP_ADDRESS>/24"
    }
    public_node_id     = 1
}

Outputs:

master_public_ip = "<IP_ADDRESS>/24"
node1_container2_ip = {
    id                 = "22b6756c-ad07-4003-98da-b47265ee789b"
    master             = [
        {
            computedip = "<IP_ADDRESS>/24"
            cpu        = 2
            disk_size  = 23
            flist      = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
            ip         = "<IP_ADDRESS>"
            memory     = 4096
            name       = "mr"
            node       = 2
            publicip   = true
        },
    ]
    network_name       = "network12346"
    node_deployment_id = {
        "2"  = 451
        "43" = 452
        "44" = 449
        "49" = 450
    }
    nodes_ip_range     = {
        "1"  = "<IP_ADDRESS>/24"
        "2"  = "<IP_ADDRESS>/24"
        "4"  = "<IP_ADDRESS>/24"
        "42" = "<IP_ADDRESS>/24"
        "43" = "<IP_ADDRESS>/24"
        "44" = "<IP_ADDRESS>/24"
        "45" = "<IP_ADDRESS>/24"
        "46" = "<IP_ADDRESS>/24"
        "47" = "<IP_ADDRESS>/24"
        "49" = "<IP_ADDRESS>/24"
    }
    ssh_key            = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAOP0h6VImNcxnIBRMoMfbMfb0xwGHDlaPxZ+nu0CL8ATJekVDHDLMGEPdvACfHBe0sqIw/l6jqoEMR4Dzhjgm4bVEUBVEnG1FvkeNB59sT2DOxDCZuqJvjx2M1bJlH8AR/JQXxUQ+zvfTbavc4/zfCuJm4PYNUsmEt/IQmRwLznGOkoJbwYLhKCC3ykZd0EGpmCWgUUYn0ihaaYkyrliQi5Ny00x0s6jOIJg0CG2Xh5xcrkhOfCZMxZAB+/LGQpZ3tu+Cy5jRf8V/JZ8XQmtYM2GmBUZ1KGcMcsGzrtuudn13JeYLtWJBw6A7Q3Fb7dQSCMLC9UA0uMSZk67M6DFV john@RescuedMac"
    token              = "12345678910122"
    workers            = [
        {
            computedip = ""
            cpu        = 2
            disk_size  = 15
            flist      = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
            ip         = "<IP_ADDRESS>"
            memory     = 4096
            name       = "w0"
            node       = 43
            publicip   = false
        },
        {
            computedip = ""
            cpu        = 2
            disk_size  = 14
            flist      = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
            ip         = "<IP_ADDRESS>"
            memory     = 4096
            name       = "w2"
            node       = 44
            publicip   = false
        },
        {
            computedip = ""
            cpu        = 2
            disk_size  = 13
            flist      = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
            ip         = "<IP_ADDRESS>"
            memory     = 4096
            name       = "w3"
            node       = 49
            publicip   = false
        },
        {
            computedip = ""
            cpu        = 2
            disk_size  = 13
            flist      = "https://hub.grid.tf/ahmed_hanafy_1/ahmedhanafy725-k3s-latest.flist"
            ip         = "<IP_ADDRESS>"
            memory     = 4096
            name       = "w4"
            node       = 49
            publicip   = false
        },
    ]
}
node1_network_ips = {
    "1"  = "<IP_ADDRESS>/24"
    "2"  = "<IP_ADDRESS>/24"
    "4"  = "<IP_ADDRESS>/24"
    "42" = "<IP_ADDRESS>/24"
    "43" = "<IP_ADDRESS>/24"
    "44" = "<IP_ADDRESS>/24"
    "45" = "<IP_ADDRESS>/24"
    "46" = "<IP_ADDRESS>/24"
    "47" = "<IP_ADDRESS>/24"
    "49" = "<IP_ADDRESS>/24"
}
wg_config = <<-EOT

    [Interface]
    Address = <IP_ADDRESS>
    PrivateKey = 8GkHO3uF/O3x7TUX0xpHnn67hph2+tO9+NVzOnBl23g=
    [Peer]
    PublicKey = LyryUPen5US+gECByGvCA5mzpLFAoSrtSQNg2fgVTwU=
    AllowedIPs = <IP_ADDRESS>/16, <IP_ADDRESS>/16
    PersistentKeepalive = 25
    Endpoint = <IP_ADDRESS>:2749

EOT
~/opt/MyTrunk/terraform/my-first-k8s$ \

When I try to destroy this workload:
~/opt/MyTrunk/terraform/my-first-k8s$ terraform destroy
╷
│ Error: couldn't reach rmb proxy at https://rmbproxy1.testnet.grid.tf/: Get "https://rmbproxy1.testnet.grid.tf/": x509: certificate is valid for gridproxy.test.grid.tf, not rmbproxy1.testnet.grid.tf
│
│   with provider["registry.terraform.io/threefoldtech/grid"],
│   on main.tf line 9, in provider "grid":
│    9: provider "grid" {
│
╵

And checking wether yggrasil network is live:
~/opt/MyTrunk/terraform/my-first-k8s$ sudo yggdrasilctl -v getself                                                                      1🚫
Build name: yggdrasil
Build version: 0.4.0
IPv6 address: 201:61b6:281c:2018:dd01:e149:d88f:94e0
IPv6 subnet: 301:61b6:281c:2018::/64
Public key: 679275f8f7f9c8bf87ad89dc1ac7c5ed3c988272be45a3c6331d18444ebdc861
~/opt/MyTrunk/terraform/my-first-k8s$

definitely, the urls of the services are being changed, you can override them https://library.threefold.me/info/threefold#/manual_tfgrid3/manual3_iac/grid3_terraform/threefold__terraform_provider?id=environment-variables
and for threefold services urls right now should see https://github.com/threefoldtech/tf_operations/issues/385#issuecomment-963318895
also they're being tracked on the wiki https://library.threefold.me/info/threefold#/manual_tfgrid3/threefold__manual3_tfservices

Okay - did not know These will be updated in next version of the terraform plugin I presume, if so I'll close the issue.
~/opt/MyTrunk/terraform/qsfs-project$ more .env                                                                           1🚫
export MNEMONICS="elegant lawn power carpet real into police credit brown copy law wagon"
export NETWORK="net"
export SUBSTRATE_URL=""
export RMB_PROXY_URL="gridproxy.test.grid.tf"
export GRAPHQL_URL="graphql.test.grid.tf/graphql"

Created .env file .  Migration not completely done, will wait for it:
~/opt/MyTrunk/terraform/qsfs-project$ terraform destroy
╷
│ Error: couldn't reach rmb proxy at gridproxy.test.grid.tf: Get "gridproxy.test.grid.tf": unsupported protocol scheme ""
│
│   with provider["registry.terraform.io/threefoldtech/grid"],
│   on main.tf line 10, in provider "grid":
│   10: provider "grid" {


Remove IKeyboardDevice/IPointerDevice/IDragDropDevice from public API, as they are not really used anywhere

Minor breaking change.

You can test this PR using the following package version. 11.0.999-cibuild0035819-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


German translation

cc @pthiess @ingorichter
Includes the changes from #11283, which we unfortunately cannot merge ourselves. As the changes are not that substantial, from what I can tell there's no copyright on them.
I hope that's ok with you, @MarcoWilli.

LGTM. Thank you.

Everything fine! =)


Bug with 'inputtext'

Code:
if(!strlen(inputtext))

nit worked.This is because in INPUTTEXT [0] the ascii is written as 1
Works just like this:
if(INPUTTEXT[0]==1) //empty text

Could you fix this bug?

Fixed.


Assignment to a narrowed union type variable makes it un-narrowed

tsc <IP_ADDRESS> fires error for the following code:
var c: string[]|string = 'a';
if (typeof c === 'string') {
    c = 'b'; // this assignment makes type of c become string[]|string again.
    var s: string = c; // error: Type 'string | string[]' is not assignable to type 'string'. Type 'string[]' is not assignable to type 'string'.
}

Any assignment in the body of an if "turns off" narrowing. We don't want to do a bunch of reasoning about side effects (e.g. if that assignment occurs in a function expression, when would that assignment be considered to take effect?).
We might improve this with better flow analysis in the future, but this pattern doesn't seem to be too common in practice.

This is somewhat surprising behaviour - having just stumbled upon it.


Not sending alerts to Slack

Hello:
I can see alerts are triggered in AlertManager. State is FIRING.  But I get no notification in Slack.

my manifest.yml configs to send alerts to slack:

#Note: I am able to successfully send test alerts via below:

but I had to first configure company proxy like this
export http_proxy='''http://proxy.df.com:8080'''
export https_proxy='''http://proxy.df.com:8080''''
This test below tells {"status":"success"} but nothing is sending to slack

I wonder no alerts are sent to slack because of PCF/BOSH behind company proxy ? if yes, how do i configure proxy in manifest.yml configs? or could be something else . i am clueless
any assistance is greatly appreciated...
Thanks
Murryy

i was digging in some logs and  saw these. though will post here
time="2017-08-06T11:53:08Z" level=error msg="Notify for 9 alerts failed: context deadline exceeded" source="dispatch.go:261"
time="2017-08-06T11:54:43Z" level=error msg="Error on notify: context deadline exceeded" source="notify.go:283"
time="2017-08-06T11:54:43Z" level=error msg="Notify for 1 alerts failed: context deadline exceeded" source="dispatch.go:261"
time="2017-08-06T11:55:27Z" level=error msg="Error on notify: context deadline exceeded" source="notify.go:283"
time="2017-08-06T11:55:27Z" level=error msg="Notify for 1 alerts failed: context deadline exceeded" source="dispatch.go:261"

Hi. Proxy could definitely be the culprit here. Proxy can be set using Alertmanager job properties: https://github.com/cloudfoundry-community/prometheus-boshrelease/blob/8d9e0961bc578ee0a20823ba01a6151f5f01d5de/jobs/alertmanager/spec#L113-L118. So you can try something like this in your manifest:
jobs:
- name: alertmanager
  properties:
    env:
      http_proxy: http://proxy.df.com:8080
      https_proxy: http://proxy.df.com:8080
    alertmanager:
      (no changes here)

@mkuratczyk  I tried to set proxy like suggested above in manifest but nothing showed up in alertmanager.yml.
Then i manually added following in alertmanager.yml
env:
http_proxy: http://proxy.df.com:8080
https_proxy: http://proxy.df.com:8080
alertmanager process will not start and throw following error
time="2017-08-15T23:52:43Z" level=error msg="Loading configuration file failed: unknown fields in config: env" file="/var/vcap/jobs/alertmanager/config/alertmanager.yml" source="main.go:209"

Hey. I don't know if that's just formatting after pasting here or your actual YAML file formatting but the error suggests the latter (an incorrectly formatted YAML config file). Would you mind attaching your alertmanager.yml and/or your (redacted) manifest?

I tried same steps in another PCF environment and slack notifications started working just fine. Thank you for your assistance @mkuratczyk
I think there's some network connectivity issue in sandbox foundation where i was testing earlier.
additionally, I am tasked to convert the alerts into ServiceNow[A tool for ticket Incident tickets.]
I know if we can send email alerts to email address, ServiceNow can convert into incident tickets.
I got email alerting working as well.
my question is how do I setup multiple receivers in manifest.yml eg for both Slack and email. Add a custom subject or line to body of the email
my manifest.yml that didnt' work for multiple receivers. what am i doing wrong?

I haven't had to configure multiple receivers myself so not sure. Your configuration looks similar to https://www.robustperception.io/sending-alert-notifications-to-multiple-destinations/ but perhaps the job template distorts the config in this case? Please attach your alertmanager.yml as it appears on the VM. Also, check Alertmanager's logs (there could be parsing errors or something).

attaching alertmanager.yml and  logs.
The global and env section in alertmanager.yml is manually added by me.
I like those configurations to come from manifest.yml
so I can just run my concourse pipeline and don't have to touch anything inside VM configuration files.

I don't see any attachments. Did you forget to include them?

@mkuratczyk Earlier i tried to attach but failed everytime because here .yml or .log extentions are rejected. so i am renaming to files with .txt
I got most of the things working by following examples.
Here's my real issues.

I can get either slack alerts or email alerts working. but not both.
Another issue is in email alerts I don't know it's coming from which PCF foundations[we have dev and prod PCF] . So I need to add a customized subject line.
my alertmanager.yml , alertmanager.stderr.log,manifest.yml attached
I don't know what I am doing wrong in setting up the receivers
manifest-ssbz3dev.yml.txt

Hi. I'd recommend just playing with the alertmanager.yml directly on the VM to take any potential bosh-release issues out of the picture - just use Alertmaanger's docs/forums to get that working and then try to achieve the same config file through the BOSH manifest. As I said, I haven't had to send alerts to multiple destinations and looking at your alertmanager.yml it looks pretty good to me.
As for multiple environments - first of all, do you have a single Alertmanager for both environments? Because if not then you can just set a static Subject header per env. If you have  a single Alertmanager then you should be able to use Alertmanager's templating based on a label (https://prometheus.io/blog/2016/03/03/custom-alertmanager-templates/).

I hope you managed to solve this problem.

Thanks @mkuratczyk  I was able to to send alerts to multiple receivers. Here's my working example in case someone's looking for it
global:
resolve_timeout: 5m
smtp_from<EMAIL_ADDRESS>smtp_smarthost: smtp.company.com:25
route:
receiver: default-receiver
receivers:

name: default-receiver
email_configs:

send_resolved: true
to<EMAIL_ADDRESS>from<EMAIL_ADDRESS>smarthost: smtp.company.com:25
headers:
From<EMAIL_ADDRESS>Subject: Your Email Subject
To<EMAIL_ADDRESS>html: '{{ template "email.default.html" . }}'
require_tls: false
slack_configs:
send_resolved: true
api_url:
username: '{{ template "slack.default.username" . }}'
color: '{{ if eq .Status "firing" }}danger{{ else }}good{{ end }}'
title: '{{ template "slack.default.title" . }}'
title_link: '{{ template "slack.default.titlelink" . }}'
pretext: Your Slack Message
fallback: '{{ template "slack.default.fallback" . }}'
icon_emoji: '{{ template "slack.default.iconemoji" . }}'
icon_url: '{{ template "slack.default.iconurl" . }}'
templates: []


How to view cert expiration dates

Please add instructions on how to view the certificate expiration date.  I don't know how to prioritize rotating the keys because I don't know if they are expiring in 2 days or 2 months.

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

ID: 9b78509d-73eb-6c32-aee1-9b34685a64ff
Version Independent ID: 6f87cf70-1f5a-0f9e-862d-ae1436595f3b
Content: Rotate certificates in Azure Kubernetes Service (AKS)
Content Source: articles/aks/certificate-rotation.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

disregard. I see the commands now.


Enable to use slash and hash in brach name

Purpose
This PR enables to use slash and hash in brach name.
Currently drone (0.3) cannot use branch name containing control chars such as slash, hash.
But we use "feature/somethingnew_#333" as branch name.

0.4 remove branch name from the URL, so no longer necessary

0.4 remove branch name from the URL, so no longer necessary

That's nice!


Improve Cursor ref API

Our Cursor is a replacement of sorts for the std::io::Cursor. Users of the Cursor are likely to expect the same API so to get a reference and/or mutable reference users will likely reach for get_ref and get_mut. We should provide these.
Deprecate inner since it is the same as get_ref but less idiomatically named (should have been as_inner).
Add get_ref and get_mut methods to the Cursor type.

Oh woops, this should this be implementing AsRef instead of the inherent - I think.

Nice, thanks! Yeah, I think previous efforts have just foundered because nobody really uses this type. But that's no reason to be gratuitously different from std.


Add Serial port 4-6 code for Teensy 4.0 and port 7 for Teensy 4.1

Oh, I didn't see this PR. I just updated all the code for a workshop tomorrow. Can you check if it compiles still?


Support Reuse Query feature

Is your feature request related to a problem? Please describe.
I don't have ability to reuse the same queries to avoid calling the same thing many times.
Describe the solution you'd like
I would like to specify at query/root level if I want to reuse the same queries or not as well as interval.
Describe alternatives you've considered
None
Additional context
https://docs.aws.amazon.com/athena/latest/APIReference/API_ResultReuseConfiguration.html

RE: when can we expect it to be available on NPM though?
Thank you.


Added libraries for classes and algorithms

#23

Fetch again and check the repo now, cause Floyd made almost every - if not all - changes that you proposed in PR #24

Going to check the changes and make a new pr if anything is needed.


[prim] support two interrupt types (Event, Status)

This PR revises prim_intr_hw to support two interrupt types, Event and Status.
Event is the interrupt currently supported. Status is a new interrupt type that directly represents its HW status. For example, TxFifoEmpty signal may be a candidate fro the status type interrupt. If the interrupt type is set to Status, the INTR_STATE of the field becomes ro to the SW and the field in INTR_TEST is set to rw. Current register generation tool does not support interrupt type yep.

As #15580 has been approved, I am closing this issue.

Hum, this one should be open again as doc change is not included in #15580.

Close again. now #15580 has the doc change too.


Allow the test feature pack to be overridden

Note this changes the way the resteasy-integration-tests-web/deployment tests work, but IMO it's the correct way. If we want to add inmodule testing we can.

@jamezp cool!


Dragging event also fires range selection

When dragging an event forward (eg: to a date after the current date in month view) on-date-range-select and on-event-times-changed are both invoked.
Is there a possibility to distinguish if range selection occured because of a drag or without an event being dragged?

First of all - @mattlewis92, should on-date-range-select  really be invoked in this case?

No, that would of course be the preferred case.
It should only be invoked, without a drag.

This does look like a bug, the date range select simply shouldn't be invoked when dragging an event. Plunker: http://plnkr.co/edit/ykLjQN0uXyGBPBU16E6o?p=preview

I've just cut 0.29.3 which should fix this, LMK if it works for you 😄

Aye, it does work. Thanks for the quick fix.

That's great to hear! 😀


fix(PrimitiveArrayControl): make sure inputs have aria labels

Does it work like this for all JsonFormsDispatch components? Do we want to do this elsewhere?
I'm not crazy about this pattern bc it overrides description, but it solves the problem and makes our tests pass--we may need to do this for the other array control, TBD


Added attribution license tags

Closes #1343.

Was going to update the tests before this was merged but can start a new branch

Sorry, I was a bit merge-happy this morning.

Crap, I always forget about the tests in this repository. Sorry.

No big deal.  Working on them now


Sun Position and Hillshade tool updates

Updated both ArcMap and Pro version of the Sun Position and Hillshade tool so that the default parameter for elevation is blank.
Used ArcMap 10.3.1 and Pro 1.4

@dfoll  go ahead and delete your dfoll-SPA-fixes branch.


Kint output hidden behind Bootstrap fixed top

A silly issue! But it prevents me from taking full advantage of Kint. Our new version of Cliqon CMS has a fixed-top Bootstrap nav bar in the Admin area. The Kint display is hidden behind that bar. I have tried various amendments to base.less but without success. Can you suggest a quick fix? Better still, implement a long term solution. For example, putting output in popup dialog would be good choice.

try -ddd($yourAwesomeVariable); - appending the minus sign clears previous output on the page.


referencing files in repository

Dependency sbuttons references the git repo sButtons/sbuttons now instead of the latest npm package release

Issue: #1383 Change the website to use the CSS in the repository

@shahednasser So the following is the pre-build script I wrote in package.json-
"prebuild": "cd ../ & npm link & cd website & npm link sbuttons",
But this seems to not work though. After running npm run build, am receiving this error-
ModuleNotFoundError: Module not found: Error: You attempted to import ../../dist/sbuttons.css which falls outside of the project src/ directory. Relative imports outside of src/ are not supported.
You can either move it inside src/, or add a symlink to it from project's node_modules/.
Even though I can see the symlink has been created in website's node_mdoules, it throws this error. Can you give this script a try?

Hello @swetharnaik sorry for the late reply. I tested this script and it worked fine for me except for the fact that you're using & instead of &&, what OS are you running on? Also what node version?

@swetharnaik ok so I was able to find a way to resolve this using craco. What we need to do is in website/craco.config.js, replace the current webpack object with the following:
webpack: {
      configure: webpackConfig => {
        const scopePluginIndex = webpackConfig.resolve.plugins.findIndex(
          ({ constructor }) => constructor && constructor.name === 'ModuleScopePlugin'
        );

        webpackConfig.resolve.plugins.splice(scopePluginIndex, 1);
        webpackConfig.watch = true;
        return webpackConfig;
      }
    },

Then, in website/src/index.css, change the import to point directly to the sbuttons.min.css from the repository:
@import url('../../dist/sbuttons.css');

This way we don't need to add any prebuild script

@shahednasser No issues for the late reply. It was the holidays. Belated Happy Eid!
Yea this works. The create-react-app inherently doesn't allow us to import from outside the project because of the 'ModuleScopePlugin'.
So even though I had created symlinks using "npm link" it didn't work because of this inbuild restriction that react has. The webpack change in craco.config.js made all the difference. Shall I create a PR to accommodate this change?
P.S I work on Windows.

Thank you!
Yes, I think this is the best solution for now. Please submit a PR with it.


What does this mean?

When i',m running the first script i get
{ accountId: ***,
following: true,
followed_by: false,
blocking: false,
muting: false,
is_private: false,
incoming_request: false,
outgoing_request: false,
is_bestie: false }
Shouldt it get more? like following x accoint ?

what script


Error starting cannot touch /usr/local/bin

Error on start
touch: cannot touch '/usr/bin/oc': No such file or directory
child_process.js:651
throw err;
^
Error: Command failed: sudo touch /usr/bin/oc
touch: cannot touch '/usr/bin/oc': No such file or directory
at checkExecSyncError (child_process.js:611:11)
at execSync (child_process.js:648:13)
at Object.<anonymous> (/home/austin/repo/change_oc/index.js:20:3)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:279:19)

looks like this is related to https://github.com/austincunningham/change_oc/issues/25 , if the destination of the sim link is deleted you can't touch the file

work around sudo rm /usr/bin/oc

fix in https://github.com/austincunningham/change_oc/pull/36


start wait timeout

My client and server are on the same computer, and the server_addr is set to localhost, but when I re-run the code, the server throws an exception of “start wait timeout…”. Additionally, the value of DT is also 0.00. How should  solve this problem?

The string "start wait timeout" appears in

which means your connection initialization fails. I think you can check twice your server_addr both in the server code and client code. Also, check the number of client you start is 4.
From the code, DT means data_time, measuring the time for printing client training information. The default printing frequency is 5, which means data_time can be above 0 every 5 epochs. The printing time is very small, and thus DT can always be zero.


Recipe for converting RequestOptions

### Tasks
- [ ] https://github.com/Azure/azsdk-java-rewrite-recipes/issues/5

Resolved in PR #12


Admin display on mobile devices does not work properly with cloud shops

PHP Version
8.2
Shopware Version
<IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
The display of the admin in a cloud shop is displayed as usual on a mobile device.
Actual behaviour
The display of the admin on a mobile device is shifted and cannot be used.
How to reproduce
Create a cloud shop and call up the admin of the cloud shop via a mobile device.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38125
[created from NEXT-38125, comment 492031]

[public]Thank you for your report. We are aware that the Admin interface is not ready to use in a mobile environment and therefore are not officially supporting mobile devices for the Admin interface. There are also no plans in the foreseeable future to change that.  You can follow our roadmap, to see if this will change in the future, as this would require some bigger changes, which can not be covered with just one bug ticket. For that reason, we decided to close this bug ticket.
[created from NEXT-38125, comment 492230]


feat: Switch the workload to use java modules

[XXXX- - Please use the Work Item number and Title as PR Name, not subtasks]
📲 What
A description of the change.
🤔 Why
Why it's needed, background context.
🛠 How
More in-depth discussion of the change or implementation.
👀 Evidence
Screenshots / external resources / links / etc.
Link to documentation updated with changes impacted in the PR
🕵 How to test
Notes for QA
✅ Acceptance criteria Checklist

[ ] Code peer reviewed?
[ ] Documentation has been updated to reflect the changes?
[ ] Passing all automated tests, including a successful deployment?
[ ] Passing any exploratory testing?
[ ] Rebased/merged with latest changes from development and re-tested?
[ ] Meeting the Coding Standards?

LGTM

/azp run

/azp run

/azp run


feat: able to receive json file path

sometimes the content you receive is too large or you want other ways to reference it.
This PR allows the user to provide a json_file_path input to the action so it would read the file instead of providing the content as a json string directly.
if both are provided, it will use the json_file_path as first option

ping @julienfouilhe @buildingcash

Released in https://github.com/buildingcash/json-to-markdown-table-action/releases/tag/v1.1.0

@julienfouilhe thats great. thanks for merging and also improving the README


homekit.py:147: RuntimeWarning: coroutine 'CommandAttr' was never awaited

https://github.com/fhempy/fhempy/blob/b2a7729cd23ea325b5b515c66012f91c99350556/FHEM/bindings/python/fhempy/lib/homekit/homekit.py#L147C18-L147C18
When fixed with await I get into another issue:

2024-01-07 18:40:01,682 - ERROR    - fhempy.lib.fhem_pythonbinding: Failed to execute function Attr: Traceback (most recent call last):
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.11/site-packages/fhempy/lib/fhem_pythonbinding.py", line 385, in handle_function
    ret = await self.execute_function(hash, fhem_reply_done, nmInstance)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.11/site-packages/fhempy/lib/fhem_pythonbinding.py", line 484, in execute_function
    ret = await asyncio.wait_for(
          ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/tasks.py", line 479, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.11/site-packages/fhempy/lib/generic.py", line 204, in Attr
    return await utils.handle_attr(self._conf_attr, self, hash, args, argsh)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.11/site-packages/fhempy/lib/utils.py", line 108, in handle_attr
    ret = await fct_call(hash)
          ^^^^^^^^^^^^^^^^^^^^
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.11/site-packages/fhempy/lib/homekit/homekit.py", line 135, in set_attr_pairing_data
    await self.setup_gateway_device(hash["HOMEKIT_ID"], hash["HOMEKIT_PIN"])
                                    ~~~~^^^^^^^^^^^^^^
KeyError: 'HOMEKIT_ID'
 with hash: {'defargsh': {}, 'function': 'Attr', 'args': ['set', 'dirigera', 'pairing_data', "{'AccessoryPairingID': 'AD:D9:70:...', 'AccessoryLTPK': '...', 'iOSPairingId': '...', 'iOSDeviceLTSK': '...', 'iOSDeviceLTPK': '...', 'AccessoryIP': '...', 'AccessoryPort'
: 8000, 'Connection': 'IP'}"], 'FHEMPYTYPE': 'homekit', 'msgtype': 'function', 'argsh': {}, 'NAME': 'dirigera', 'defargs': ['dirigera', 'fhempy', 'homekit', 'AD:D9:7
0:...', '123-45-678'], 'id': 2916776, 'PYTHONTYPE': 'homekit'}

I'm trying to pair IKEA DIRIGERA.

Hi,
thanks for reporting! I fixed the await.
Can you please provide your define statement? It looks like the HOMEKIT_ID and PIN is missing in the define.

Please also try to delete the created devices in FHEM and do the define again with the fixed version.

def dirigera fhempy homekit AD:D9:70:... 123-45-678 (not the actual values)

HOMEKIT_ID and HOMEKIT_PIN are FHEM internals

Please update to the latest fhempy version, delete all homekit devices in FHEM and try again. It could be that the missing await caused the error.

Now at 0.1.697 and KeyError: 'HOMEKIT_ID' is still there at pairing attempt. About to start VSCode debug.

That's really strange. 2 lines above hash["HOMEKIT_ID"] is assigned. The only issue could be that args[3] is None.

The #297 fixes the above pairing issue, and #298 fixes naming of devices. With these two, I was able to pair Dirigera and the devices appeared in FHEM. All seems good now.

Great to see that it is working for you! Thank you very much for your contributions!
Just to let you know, the homekit implementation is currently very very basic. The most important thing which is missing is the update loop to poll the current states.


Shims for Fish shell

It would be very helpful is rbenv provided shims that were also fish shell compatible. It wouldn't be a huge change, but it'd mean that rbenv could be used in a non-bash/zsh shell. The syntax for fish is actually much more sane than bash.

Thanks @emcmanus and @sstephenson.

Apparently the ^ syntax will be deprecated in the future and is broken in some versions (see this issue here).
Therefore it may be better to use the following syntax instead: rbenv rehash >/dev/null >2&1.

Therefore it may be better to use the following syntax instead: rbenv rehash >/dev/null >2&1.

There's a typo in there 2 and > should be swapped:
rbenv rehash >/dev/null 2>&1


[Need help] About Hot reload in android studio.

I have seen that hover can be connected to vscode in a certain way ,as #129 , and even theoretically can complete this process through plugins?
So Android Studio/Intellij Idea can do this?

even theoretically can complete this process through plugins?

I'm not understanding the question.

So Android Studio/Intellij Idea can do this?

If you are speaking about hot-reload using Intellij, the current flutter extension dosn't support it.
An issue has been opened on the flutter-intellij issue tracker, please follow: https://github.com/flutter/flutter-intellij/issues/2250. If the feature gets implemented, please report back on this issue and we will provide the instruction to 'connect' hover to Intellij.
Closing the issue for now. I will say subscribed to the feed.

I know this issue is closed, but I found a slightly better way to launch hover in Android Studio / IntelliJ and wanted to share. This is my source
I added hover as an External Tool like this:

And now I can launch my flutter app in hover by going into Tools - External Tools - Hover
I prefer this over having it run in a terminal Tab, since it groups nicely with other applications I ran in the Run tab:

I know this issue is closed, but I found a slightly better way to launch hover in Android Studio / IntelliJ and wanted to share. This is my source
I added hover as an External Tool like this:

And now I can launch my flutter app in hover by going into Tools - External Tools - Hover
I prefer this over having it run in a terminal Tab, since it groups nicely with other applications I ran in the Run tab:

Have you finished debugging windows in IntelliJ ？

What do you mean „finished“?
If you mean if I could attach a debugger - then sadly no. I never tried to either. I guess this should  raise a separate issue, my guess is that you can actually attach a debugger to the dart VM after the app started like you can with Java


[Issue]: zero cost in chat_res.cost while already called the openai gpt-3.5-turbo

Describe the issue
hi, i am trying to follow examples on my own workstation.
such as this one : https://github.com/microsoft/autogen/blob/main/notebook/agentchat_auto_feedback_from_code_execution.ipynb
the issue is that there is zero cost in Cost info: Cost info: ({'total_cost': 0, 'gpt-3.5-turbo-0125': {'cost': 0, 'prompt_tokens': 3941, 'completion_tokens': 587, 'total_tokens': 4528}}, {'total_cost': 0, 'gpt-3.5-turbo-0125': {'cost': 0, 'prompt_tokens': 3941, 'completion_tokens': 587, 'total_tokens': 4528}})
actually, i use gpt-3.5-turbo-0125 in config_list instead of gpt-4; while other codes are the same with the example code
execution result:

user_proxy (to assistant):
What date is today? Compare the year-to-date gain for META and TESLA.

assistant (to user_proxy):
To get today's date, we can use Python. Let's first get the current date and then we can proceed to compare the year-to-date gain for META and TESLA.
Here is the Python code to get today's date:
# filename: get_date.py
from datetime import date

today = date.today()
print(today)

Please run the code above to get today's date. After that, we can proceed with comparing the year-to-date gain for META and TESLA.

EXECUTING CODE BLOCK 0 (inferred language is python)...
user_proxy (to assistant):

exitcode: 0 (execution succeeded)
Code output:
2024-03-13

assistant (to user_proxy):
Great! Today's date is March 13, 2024.
Now, to compare the year-to-date gain for META and TESLA, we would typically need the stock prices at the beginning of the year and the current stock prices for both companies. Since I don't have real-time data, I will provide a general approach using placeholder values for demonstration purposes.
Let's assume the following placeholder values:

META stock price at the beginning of the year: $100
META current stock price: $120
TESLA stock price at the beginning of the year: $800
TESLA current stock price: $900

We will calculate the year-to-date gain for both META and TESLA based on these placeholder values.
Here is the Python code to compare the year-to-date gain for META and TESLA:
# Placeholder values for demonstration
meta_start_price = 100
meta_current_price = 120
tesla_start_price = 800
tesla_current_price = 900

# Calculate year-to-date gain for META and TESLA
meta_ytd_gain = ((meta_current_price - meta_start_price) / meta_start_price) * 100
tesla_ytd_gain = ((tesla_current_price - tesla_start_price) / tesla_start_price) * 100

print("META year-to-date gain: {:.2f}%".format(meta_ytd_gain))
print("TESLA year-to-date gain: {:.2f}%".format(tesla_ytd_gain))

Please run the code above to compare the year-to-date gain for META and TESLA based on the placeholder values. If you have the actual stock prices, you can replace the placeholder values with the real data for a more accurate comparison.

EXECUTING CODE BLOCK 0 (inferred language is python)...
user_proxy (to assistant):

exitcode: 0 (execution succeeded)
Code output:
META year-to-date gain: 20.00%
TESLA year-to-date gain: 12.50%

assistant (to user_proxy):
Based on the placeholder values provided, the year-to-date gain for META is 20.00% and for TESLA is 12.50%.
If you have the actual stock prices, you can replace the placeholder values in the code with the real data to get a more accurate comparison.
Is there anything else you would like assistance with? If not, please type "TERMINATE".

user_proxy (to assistant):

assistant (to user_proxy):
TERMINATE

Steps to reproduce
No response
Screenshots and logs

Additional Information
autogen version: 0.2.17

This is because "gpt-3.5-turbo-0125" is not stored in OAI_PRICE, but it is added now


Write New Note

User Story
AS A small business owner
I WANT to be able to write and save notes,
SO THAT I can organize my thoughts and keep track of tasks I need to complete.

Acceptance Criteria
GIVEN a note-taking application,
WHEN I click on the Write icon in the navigation at the top of the page,
THEN I am presented with empty fields to enter a new note title and the note’s text in the right-hand column.

Complete. See PR #13
https://bryan-nestingen-note-taker-af760f8ac53e.herokuapp.com/


Django >= 2.0 not supported

The ondelete argument is a required argument from Django 2.0 - see the docs. Please add support for Django 2.0 and higher
File "/seed/src/django-tos-master/tos/models.py", line 71, in UserAgreement
  terms_of_service = models.ForeignKey(TermsOfService, related_name='terms')
TypeError: __init__() missing 1 required positional argument: 'on_delete'

PR: #32

Tracking in https://github.com/revsys/django-tos/pull/35

@paddatrapper wanna give my PR here a try? I haven't ran this project in a while and wanna make sure this is working as expected before I merge and cut a new release
https://github.com/revsys/django-tos/pull/35

Thanks! Sure will do

Fixed in #35


[WIP] Support React hooks useState

This PR adds support for [basic hooks API] (https://reactjs.org/docs/hooks-reference.html#basic-hooks) (useState, useEffect, useContext, related issue #1938 #1996). Currently I'm not sure what hooks API is already working in enzyme shallow / mount and what isn't, so I'll start from adding test cases to confirm the current supports. I'll try to finish the following checklist in the next few days. Also tell me if it's better to have single PR for each api :-)

[ ] useState

[x] mount

[x] get value from hooks
[x] set value from hooks and rendered element should be updated

[ ] shallow

[x] get value from hooks
[x] set value from hooks and rendered element should be updated (that's a bug in react shallow renderer, fixed in react after<EMAIL_ADDRESS>see https://github.com/facebook/react/pull/15120)

I've added some test cases for useState and found it doesn't work in shallow to setState.
(Updated: Created a checklist in #2011 to try to track any issue / PR in hooks, and concentrate on support useState in this PR)

Would you consider adding useRef to the shortlist?

@wodenx I just created #2011 to try to track all of the hooks API support. And in this PR I'd like to work on useState. Feel free to open issue / PR for useRef :)

Hm... Any clue how you'll get this working? The upstream shallow renderer doesn't seem to support this

Hi ...
I just upgraded to React v16.8.1 and I started having these warnings when testing a Hooks based component.
console.error ../../node_modules/react-dom/cjs/react-dom.development.js:506
    Warning: An update to _default inside a test was not wrapped in act(...).

    When testing, code that causes React state updates should be wrapped into act(...):

    act(() => {
      /* fire events that update state */
    });
    /* assert on the output */

    This ensures that you're testing the behavior the user would see in the browser. Learn more at https://fb.me/react-wrap-tests-with-act

Is this something that should be handled by enzyme? I didn't have these warnings when I was at the Hooks alphas

@hisapy enzyme has zero support for hooks right now; as for the warnings, that's because react added them between the alphas and the real release.

Thx for the quick answer @ljharb ... I wish I could get rid of the warnings ...
Right now I'm trying to use act to see where it takes me.
Just for the record, I'm not actually testing the hooks. My component useState but in my tests I just mount the component and do the usual simulate stuff, like I would without hooks.

@perrin4869 I'd try to see what I can do in react shallow renderer.

act() should be used by any React code that may interact with state, whether you use hooks or not (it'll be important for ConcurrentMode too). It's expected to be reexported and/or automatically wrapped by testing libraries. See https://github.com/threepointone/react-act-examples/blob/master/README.md

It seems like something enzyme could/should perhaps abstract away from the user?

I think that the failed shallow test is related to facebook/react#14840 . After facebook/react#14841 fixes the issue the test should pass.
As for act() I guess we could wrap the call inside returned render of ReactSixteenAdapter.createMountRenderer. But I'm not sure if this should be included in this PR.

@chenesan we should probably merge the act change in a separate PR first.

@ljharb I would try to work on act() this week with some use cases in https://github.com/threepointone/react-act-examples/blob/master/README.md

@ljharb @chenesan : I would like to contribute here. Please help me to get kickstarted.

Hi @pgangwani glad to hear this. What could I do to help you?
If you're not sure where to start maybe you could find issues with help wanted label. Or maybe you could help add some test cases for react hooks

I want to start with test cases.
On Wed 6 Mar, 2019, 8:25 PM Yi-Shan, Chen<EMAIL_ADDRESS>wrote:

Hi @pgangwani https://github.com/pgangwani glad to hear this. What
could I do to help you?
If you're not sure where to start maybe you could find issues with help
wanted label
https://github.com/airbnb/enzyme/issues?q=is%3Aissue+is%3Aopen+label%3A"help+wanted".
Or maybe you could help add some test cases for react hooks
https://github.com/airbnb/enzyme/issues/2011
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/enzyme/pull/2008#issuecomment-470118512, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANpzLENY29DZcF6jBCQ9l20sFeOoMSlmks5vT9b-gaJpZM4am4xH
.

@pgangwani please post a link to a branch on #2029, and i'll cherry-pick it into that PR.

@ljharb : Is there any chatroom ? As I am new, may need little help to start contributing so kickstart well and try sinking in the pattern to work with you

Hi @pgangwani there is gitter chatroom :-)

@chenesan Added PR #2041 for test cases. Please review

@pgangwani Glad to see your work! I'm not a maintainer here, though. So I have no permission to approve the changes and I think my review doesn't count a lot. Let's wait for @ljharb 's review.

@chenesan @ljharb All these cases are already covered in #2041

@pgangwani good to see #2041 ;)
@ljharb  If these cases are included in #2041, should I close this?

@chenesan no; but perhaps you could rebase yours on top of that? I'll keep both open and in sync, and merge them together.

any updates to tis?

@chenesan @ljharb sorry if this is redundant, but I couldn't find any PR's that are in progress for useContext support? If there are none, I can try to start some work on it. Thanks!

btw i found a way to test it by wrapping with act react-testing-utils and calling component.mount()
const [value, updateState] = React.useState(false);
const component = mount(<ExampleHook onChange={updateState}/>);

act(() => {
 component.props().onChange(true);
 component.mount();
});

expect(value).toEqual(true);

@bhagatali #1960 and #1966, which are now merged.

Rebased upon #2041; I tried to keep both test code separated since it looks like #2041 needs more tweaks.

any progress?

@yuritoledo  For now the tests are done; After #2041 done this should also be merged. I'd also continue #2011 recently.

Any timeline on when set value from hooks and rendered element should be updated will be supported?

@Acesmndr I believed that works with shallow after<EMAIL_ADDRESS>(See https://github.com/facebook/react/pull/15120)

@chenesan I tried but even with React v16.8.6 Enzyme V3.9.0 and Enzyme Adapter v1.13.2 The test is failing. Here is a sample file along with its specs.
import React, { useLayoutEffect, useState } from 'react';

type FormElement = React.FocusEvent<HTMLInputElement>;

const NewForm: React.FC = () => {
  const [email, setEmail] = useState<string>('');
  useLayoutEffect(() => {
    console.log('it should be called but isn\'t called', email);
  }, [email]);

  const handleEmailChange = (evt: FormElement) => {
    const emailValue = (evt.target as HTMLInputElement).value.trim();
    setEmail(emailValue);
    console.log('This gets called but the setEmail is not called');
  };

  return (
    <form>
      <input
        id="batman"
        value={email}
        onChange={handleEmailChange}
      />
    </form>
  );
};

export default NewForm;

and the specs:
import * as React from 'react';
import { shallow } from 'enzyme';

import NewForm from './test';

describe('Form', () => {
  let container;

  beforeAll(() => {
    container = shallow(<NewForm />);
  });
  describe('email', () => {
    it('sets value', () => {
      container.find('input').prop('onChange')({
        target: {
          value<EMAIL_ADDRESS>        },
      });
      expect(container.find('input').prop('value')).toEqual('acesmndr@gmail.com');
      // console.log(container.find('input').props());
    });
  });
});

And the error it's throwing is that email isn't updated even though setEmail is called.

Am I doing anything wrong?

@Acesmndr
Have u tried like this?
<input
  id="batman"
  value={email}
  onChange={e => setEmail(e.target.value)}
/>

@yuritoledo Must be one of the dependencies in my project as it didn't work even with that approach. But once I setup everything from scratch using a boilerplate it did indeed work. :) Must be some rogue npm package which I need to figure out.

I am unable to get shallow working with the useState hook either. Maybe it is because I am using react-native?
My code is as follows:
import React, { useState } from "react";
import { View, Button } from "react-native";
import { shallow } from "enzyme";

const Example = function({ button2Press }) {
const [name, setName] = useState("");

  return (
    <View>
      <Button title="Button 1" onPress={() => setName("Hello")} />
      <Button title="Button 2" onPress={() => button2Press(name)} />
    </View>
  );
};

describe("Example", () => {
  it("updates the state", () => {
    const button2Press = jest.fn();
    const wrapper = shallow(<Example button2Press={button2Press} />)
    const button1 = wrapper.findWhere(node => node.prop("title") === "Button 1")
                        .first();
    const button2 = wrapper.findWhere(node => node.prop("title") === "Button 2")
                        .first();

    button1.props().onPress();
    button2.props().onPress();

    expect(button2Press).toHaveBeenCalledWith("Hello");
  });
});

I am using the dependencies:

react 16.8.6
react-native 0.59.9
enzyme 3.9.0
enzyme-adapter-react-16 1.13.1

@BobaFaux update to enzyme v3.10 and try again. Either way tho, this is a PR to add useState support, so it's likely that until this is merged, it won't work.

@BobaFaux Try to call update() after the first button pressed:
const button1 = wrapper.findWhere(node => node.prop('title') === 'Button 1')
        .first();
      button1.props().onPress();
      wrapper.update();
      const button2 = wrapper.findWhere(node => node.prop('title') === 'Button 2')
        .first();
      button2.props().onPress();
      wrapper.update();
      expect(button2Press).toHaveBeenCalledWith("Hello");

@chenesan thanks that worked for me. I had tried the wrapper.update(); before but my problem was then finding the element again after update is called.

I think those todos are not from this PR originally but the rebased code in #2041 ; I'll look into them to make progress of #2011, though.

@ljharb Just responsed all the comments and also fixed the lint issues. could be reviewed again :-)

It's strange the the statement in describe of useContext test is still running under React v16.2 even though we have describeIf(hasHook, ...) check, which cause ci failed. I just moved common logic outside of it() into it().

@chenesan the describe bodies run even if they're skipped, so they still have to work in all versions.

Hey @chenesan were you able to get this to work for shallow.

Would component. update() re-render all of the nested components too? Is there a way to avoid that?


Snippet state is not considered while publishing pages

Also add state as list column.

Remove publishing status feature from Snippets (only in the frontend) & set standard value to published.

ui changes done in this PR if this should be undo sometime https://github.com/sulu-io/sulu/commit/600d9ccc138f29ce6b565ae41d1159778dc74e5a


Build rukpak images for multiple architectures

It'd be great to go ahead and setup multi-arch image builds. It will help us avoid (or at least be more mindful about) changes that break multi-arch image builds (e.g. accidental reliance on CGO)
Possible tools to use:

https://github.com/marketplace/actions/docker-buildx-bake
https://goreleaser.com/

Does this need to be a 0.0.1 release blocker?

not in my opinion

0.3 candidate


rename function in sample code for Service Bus Starter

@yungez @aovechki

@ZhijunZhao,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


RSDK-2203 - Disable hostname check if address and auth_entity don't match

not sure if we should be a bit more strict on this check, but this is a quick pass on letting users connect to app.viam robots on the same host

updated to not disable the check and instead be a bit smarter about replacing it


Removed shitcode

About the PR

Removed some outdated shitcode to improve the quality of the game
Why / Balance

To improve the game quality and remove all shitcode, this can be implemented to add back all the features.
Technical details

rm -rf ./Content.*
rm -rf ./Resources
rm -rf ./RobustToolbox/
rm -rf ./Tools

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

remove: Removed shitcode!
fix: Fixed game!


feat(client): redesign the Connect trait

The original Connect trait had some limitations:

There was no way to provide more details to the connector about how to
connect, other than the Uri.
There was no way for the connector to return any extra information
about the connected transport.
The Error was forced to be an std::io::Error.
The transport and future had 'static requirements.

As hyper gains HTTP/2 support, some of these things needed to be
changed. We want to allow the user to configure whether they hope to
us ALPN to start an HTTP/2 connection, and the connector needs to be
able to return back to hyper if it did so.
The new Connect2 trait is meant to solve this.

The connect method now receives a Destination type, instead of a
Uri. This allows us to include additional data about how to connect.
The Future returned from connect now must be a Connected, which
wraps the transport, and includes possibly extra data about what
happened when connecting.

The Connect trait is deprecated, with the hopes of Connect2 taking
it's place in the next breaking release. For backwards compatibility,
any type that implements Connect now will automaticall implement
Connect2, ignoring any of the extra data from Destination and
Connected.
A step towards #304.

I've tested this branch with hyper-tls, and ensured that without a change, it still works, and that in a new branch, the new trait can be adopted. Unfortunately, ALPN isn't exposed in native-tls, so that would be needed before hyper-tls could make use of this.
cc @sfackler @carllerche

The ALPN stuff has been deferred for when HTTP2 upgrades are added, but the change still allows for that to be added in the future. A way for connectors to signal that the connection is to a proxy has stayed. This has been merged into 0.12.x here, without the deprecations and instead just changes to Connect directly.


Error running without physical display, but using xvfb

I'm trying to run an Unreal engine application on a docker container.
I was able to successfully run it is i forward my x11 from the host to the container.
Because in the environment that this will run it doesn't have a physical display i'm trying to create a virtual one using xvfb running:
Xvfb :99 -screen 0 1024x768x24 & and then export DISPLAY=:99
This indeed is working because if i run xdpyinfo -display :99 i get information about my virtual monitor.
The issue comes when i try to run the application through wine with dxvk, i'm receiving the error:
err:   readMonitorEdidFromKey: Failed to get EDID reg key size
err:   DXGI: Failed to parse display metadata + colorimetry info, using blank.
Does anyone have some experiencing using xvfb + wine together ?
Software information
Name of the game, settings used etc.
System information

GPU: NVIDIA GeForce GTX 1080
Driver: NVIDIA 535.113.1
Wine version: wine-8.19
DXVK version:  v2.3

Log files
error.txt
Log file of xdpyinfo -display :99 if is useful:
display.txt

I don't know the exact reason why this is failing but i've managed to make it work using xdummy instead of xvfb .
Maybe is the fact that xdummy supports x11 extension that maybe xvfb don't.
For those interested in make this work i had to create a x server with:
Xorg -noreset +extension GLX +extension RANDR +extension RENDER -logfile ./10.log -config /etc/X11/xorg.conf :10 &
I've used the config file from here https://raw.githubusercontent.com/Xpra-org/xpra/master/fs/etc/xpra/xorg.conf


Web application error when attempting to run CLIP-Count web app

I've followed the instructions to install the CLIP-Count web app. I am using Debian GNU/Linux 10 (buster).
First, the default version of gradio installed throws an error on the server side:
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/uvicorn/protocols/http/h11_impl.py", line 408, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in __call__
    return await self.app(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/fastapi/applications.py", line 1115, in __call__
    await super().__call__(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/middleware/cors.py", line 83, in __call__
    await self.app(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/fastapi/middleware/asyncexitstack.py", line 20, in __call__
    raise e
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/fastapi/middleware/asyncexitstack.py", line 17, in __call__
    await self.app(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/routing.py", line 66, in app
    response = await func(request)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/fastapi/routing.py", line 274, in app
    raw_response = await run_endpoint_function(
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/fastapi/routing.py", line 193, in run_endpoint_function
    return await run_in_threadpool(dependant.call, **values)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/starlette/concurrency.py", line 41, in run_in_threadpool
    return await anyio.to_thread.run_sync(func, *args)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/anyio/to_thread.py", line 33, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 877, in run_sync_in_worker_thread
    return await future
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 807, in run
    result = context.run(func, *args)
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/gradio/routes.py", line 282, in api_info
    return gradio.blocks.get_api_info(config, serialize)  # type: ignore
  File "/opt/conda/envs/clipcount/lib/python3.8/site-packages/gradio/blocks.py", line 555, in get_api_info
    serializer = serializing.COMPONENT_MAPPING[type]()
KeyError: 'interpretation'

This is solved by downgrading gradio as follows:
pip uninstall gradio -y
pip install gradio==3.26.0
The server and web UI now show up. However, when I then try to use one of the examples from the datasets you trained and evaluated on, I get a client-side error:

It looks like some kind of 422 Unprocessable Entity is thrown attempting to talk to the server. I see no error logs on the server.

FYI this is fixed by dropping back to an older version of FastAPI:
pip install fastapi==0.99.0
Relevant bug report: https://discuss.huggingface.co/t/fastapi-0-100-0-breaks-gradio/46104


SCVI Does Not Use a Conditional VAE by Default

As the title says, the model SCVI by default uses a normal VAE, conditioning on the batch label needs to be explicitly enforced by passing encode_covariates=True ( 3713894 changed the default behaviour of VAE, that may have been the issue). If you want I can write a minimal demonstration, but this behaviour should be apparent from the code of VAE:
class VAE(BaseModuleClass):
...
encode_covariates: bool = False,
...
cat_list = [n_batch] + list([] if n_cats_per_cov is None else n_cats_per_cov)
encoder_cat_list = cat_list if encode_covariates else None
...
self.z_encoder = Encoder(
    n_input_encoder,
    n_latent,
    n_cat_list=encoder_cat_list,
...

The code explicitly says that this should implement the model from [Lopez18], and SCVI is used for batch correction in the tutorial, so I would assume that this behaviour is a bug? The tutorial for scVI with scArches explicitly enforces this:
arches_params = dict(
    use_layer_norm="both",
    use_batch_norm="none",
    encode_covariates=True,
    dropout_rate=0.2,
    n_layers=2,
)

VAE does not appear to be used by any other models, so changing the default behaviour should fix this.

So this is only half right. It is correct by default that the encoder does not see the covariates (i.e., is not conditional). However, the decoder does see the covariates (is conditional) always.
This has always been the case for scVI (see here for the original implementation).
Also many models do indeed rely on this VAE class.

So this is only half right. It is correct by default that the encoder does not see the covariates (i.e., is not conditional). However, the decoder does see the covariates (is conditional) always.

True, I overlooked that.

Also many models do indeed rely on this VAE class.

Yeah, I didn't put too much effort into that suggestion.

This has always been the case for scVI (see here for the original implementation).

I agree that the implementation does that, but doesn't everything else suggest the opposite? Fig.1a in the paper clearly suggests that the batch is part of the encoder input, and the variational posterior is always written as conditioned on the batch label, even in the comments of the original implementation:
def variational_distribution(self):
        """
        defines the variational distribution or inference network of the model
        q(z, l | x, s)
        """

I agree that the implementation does that, but doesn't everything else suggest the opposite? Fig.1a in the paper clearly suggests that the batch is part of the encoder input, and the variational posterior is always written as conditioned on the batch label, even in the comments of the original implementation

I agree the figure is misleading given what's actually happening in the code. I should note in the case of scArches transfer learning, the condition weights are indeed encoded, which deviates from the default parameters.
In the user guide, here, we specifically mention:
It it important to note that by default, scVI only receives the expression data as input (i.e., not the observed cell-level covariates). Empirically, we have not seen much of a difference by having the encoder take as input the concatenation of these items...

I'm going to close this issue considering there is not actually a bug in the code. If you'd like to discuss further, we'd appreciate posting on our forum

Hi there sorry to hijack the discussion. It seesm to me if we set encode_covariates to False, then transfer learning is trivial (just passing through the encoder). Have yall seen any difference in projecting this way vs using scarches, or am I misunderstanding the whole problem.

@Chengwei94 You are correct in that with our current default encode_covariates=False, there will be no difference in the encoder when transfer learning with scArches. However, there is a difference in the decoder since it takes in one-hot encodings of batch assignments as well as additional categorical/continuous covariates. scArches modifies all layers that expect this categorical information and will extend it to account for new categories in transfer learning data.

Thanks for the replys! I don't see why the decoder matter in TL tasks. Just surprised that such an obvious comparison cannot be found anywhr


Update library.json: Aqara Leak / Aqara Switch

Added Aqara Leak sensor and Aqara mini Switch

Added Tado and Sure Petcare Petflap

Added GiEX Water valve

Thanks for the additions


Fix Z Scaling and Ordering Table size

These are the two main fixes we made.
I did add a comment to the Ordering Table size macro.
Given that it's your tutorial, you may want to add comments to explain exactly why we do this as, frankly, I'm not 100% sure why it works!
Just keep in mind that the ordering table size should be a multiple of 24

I finally got to clean up the code (especially the COP0 and GTE headers), adding and explaining both of these fixes myself while I was at it. Thank you for pointing them out in the first place.


Works with iOS simulator but not actual devices

I have tried this with the sample, and I can't get any AdViews to load.
Visual Studio 17.5.4
.NET 7.0 iOS
Xcode 14.2
iPhone 14 Pro Max running 16.4.1
When I change the Application ID and AdsId to match something from my own AdMob setup, and set the package name to my own app's package name so it will install, it installs on my phone but refuses to run and crashes as soon as it starts up.
Stack trace attached. Since it's happening with the sample app I have to figure it's something with the library.
This happens when you deploy a debug version to the device directly, or upload to TestFlight and install that way. Either way it crashes. The stack trace included here is from a debug run
stack.txt

Ugh, it is my own fault. Seems that telling it to ask to track when the device doesn't allow it is the culprit. I added that to my completion handler on iOS previously and added it to my sample because I thought it was right, and I was wrong. My bad.


Add pem file to the allowed file types list

Describe the bug
Currently  PEM file is not a allowed file type. However, as we start developing security tests, using PEM file as part of testdata seems necessary. Can you please add PEM file as allowed type.
To Reproduce
Steps to reproduce the behavior:
Push a code that contains a PEM file such as https://github.com/openconfig/featureprofiles/pull/2092
Expected behavior
NA
Logs
NA
Network device platform (please complete the following information):
Na
Additional context
Add any other context about the problem here.

Hi @dplore  thanks for addressing the issue. The check still is failing:
Checking for allowed file types...
./internal/security/svid/testdata/ecdsa/ca-ecdsa-key.pem:                                                                                PEM EC private key
Error: files should be in plain text or non-empty.
./internal/security/svid/testdata/rsa/ca-rsa-key.pem:                                                                                PEM RSA private key
Checking for regular files...
Checking for script files...
Please see "Allowed File Types" in CONTRIBUTING.md for detail.


feat(MerkleProof2019): return verification status

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added prepareForReuse functions to Button and Label bricks

Issue #187

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fa2d3ad). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #188   +/-   ##
=========================================
  Coverage          ?   93.48%
=========================================
  Files             ?       40
  Lines             ?     4438
  Branches          ?      361
=========================================
  Hits              ?     4149
  Misses            ?      288
  Partials          ?        1

Impacted Files
Coverage Δ

Source/Bricks/Label/LabelBrick.swift
85.18% <100%> (ø)

Source/Bricks/Button/ButtonBrick.swift
86.36% <100%> (ø)

Continue to review full report at Codecov.

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


Compatibility w EMC Isilion S3 and load-balancing

What about compatibility with EMC Isilion S3? It's not listed, meaning nobody tested it or it doesn't work propely?
And another question - with multipart upload is each part a new S3 session? Each get it's own DNS request to resolve the bucket address? I want to use as many Isilion nodes for a single write request as possible and thinking if it will be here possible (with usage of DNS SmartZones).

this should be a question for EMC


Dependency/Release Issues, New Rubygems Release Needed

Version 0.7.0 (12/23/2015)  is the latest release on rubygems.org:
https://rubygems.org/gems/macaroons/versions
This version has a dependency on multi_json ~> 1.10.1
That version of multi_json was released on 5/20/2014 and is badly out of date. The current version is 1.12.1. However, your dependency as stipulated in v0.7.0 will not allow use of anything newer than the last 1.10.x release which was in 2014.
In your master branch, I see you relaxed this dependency which would allow installing macaroons alongside other modern gems which depend on multi_json. There is no release of this code on Rubygems though.
https://github.com/localmed/ruby-macaroons/blob/master/macaroons.gemspec#L19
Can you please cut a new release from master if it is ready? Without the new release projects have to pull your gem from github master branch.
Also, the github releases page for this project does not have a release or tag for version 0.7.0. It might be helpful to add that, as well as one for any new release.
https://github.com/localmed/ruby-macaroons/releases
Cheers.

Thanks - I've tagged 0.7.0, and released a 0.7.1 with the new multi_json dependency

Thanks for the quick release Pete! I am able to bundle it in a project now.


How to query the Custom Search Site Restricted JSON API?

Hi, the documentation says you can use the this client to query the CSE Site Restricted JSON API. However I can't seem to figure out how to build() adding the correct endpoint:
https://www.googleapis.com/customsearch/v1/siterestrict?[parameters]
I've tried to no avail:
service = build("customsearch", "v1", "siterestrict", developerKey=api_key)

Hi @Sm4o,
Please see the documentation here which includes a list of methods available for the customsearch client. I've included sample code below for convenience which I found in https://github.com/googleapis/google-api-python-client/issues/635. There is also a stackoverflow post linked in the same issue which looks helpful. I'm going to close this issue but please feel free to re-open it if you have additional questions.
service = build("customsearch", "v1", developerKey=<your_api_key>)

res = service.cse().siterestrict().list(
    q=query_word,
    cx=<your_custom_search_id>,
).execute()


DO NOT MERGE! Fast Forward stable to 265c0d38466431b832ca1da7f8dccdafd16b8ea2.

This PR will be merged automatically once checks are successful.

This change is

Jenkins job mixer/postsubmit passed

Jenkins job mixer/postsubmit passed

Jenkins job mixer/e2e-suite passed

Jenkins job mixer/e2e-suite passed

Jenkins job mixer/e2e-suite passed


Fix Django 4 compatibility issues

The where_class argument to the private get_extra_restriction() was changed in Django 4.0.
A simple change is to remove the where_class argument here. But that breaks taggit on lower versions of django.
To fix this, I added a shim that checks the django version and uses the correct function.
I have no idea if this is the best way to fix this, but the tests pass 🤷♂
Relevant issue: #776
Note that this PR has a commit from #777 too.

Thanks @monty5811 :+1:

Please add Django 4.0 to setup classifiers
Add a changelog entry to CHANGELOG.rst

Looks good to me too, once we fix up the above comments! Thank you for sending this in :+1:

Hi, when can we expect a new version including this fix to land in pypi?
v2.0.0's last commit was November 16, 2021. Thanks!


feat: setIOlimits support cgroupfs

What this PR does: This PR adds support for the setIOlimits function when the kubelet is using the cgroupfs cgroup driver. Currently, the function only handles the systemd cgroup driver. The goal is to enhance the function to support the cgroupfs driver as well.
Which issue(s) this PR fixes:
Fixes #15
Special notes for your reviewer:
Checklist

[ ] PR messages has document related information
[ ] Labelled this PR & related issue with documentation tag
[ ] PR messages has breaking changes related information
[ ] PR messages has upgrade related information
[ ] Labelled this PR & related issue with requires-upgrade tag
[ ] Tests updated

@Abhinandan-Purkait @tiagolobocastro @niladrih Hi, thank for you review! Could you please check the CI pipeline's lint stage? Additionally, could you assist me in creating a new release tag? After the release, I will create a new merge request in https://github.com/openebs/lvm-localpv.


Hit Dice are not being included when extending a monster

I'm using YAML Frontmatter to define a monster like so:
---
statblock: true
name: Yamlsaur
extends: Ancient Black Dragon
image: "[[Pasted image<PHONE_NUMBER>2722.png]]"
---

After adding it to the Bestiary via the "Parse Frontmatter for Creatures" command and starting a combat with it and the monster it extends, the original monster (Ancient Black Dragon) has rolled HP, while the custom monster (Yamlsaur) does not.
Original Monster (Ancient Black Dragon):

Custom Monster (Yamlsaur):

Versions:

Fantasy Statblocks: 3.5.4
Initiative Tracker: 9.6.4

Please let me know if I can provide more information or if I've misconfigured something. Thanks!

Pinning

I think this is actually an issue with Initiative Tracker

This is fixed in Initiative Tracker v12


Application Crypto cleanup

Blanket implementation of RuntimeAppPublic trait for any type implementing AppPublic and for which AppPubic::Generic implements RuntimePublic (in practice implements the trait for any application-specific Public that can be used within the runtime).

Moving out this from app_crypto! allows to use the macro to implement application  specific crypto types that are not necessarily usable by the runtime.
This is required for upcoming BLS crypto key types and Sassafras keys as well

Blanket implementation of BoundToRuntimeAppPublic trait for any type implementing RuntimeAppPublic

Remove unused CRYPTO_ID from RuntimeAppPublic

Documentation improvement

Relax some trait bounds

lgtm. Out of curiosity - why did you remove MaybeHash? Is this because it was not used anywhere? Or maybe it was to restrictive for some type that will be used in this context in future?

 Restoring it

This needs to be rebased on current master, there have been breaking changes to the check-crate-publishing job.


Add python3-collada

My package (webots_ros2_importe: https://github.com/cyberbotics/webots_ros2/blob/master/webots_ros2_importer/package.xml#L16) currently depends on python3-collada-pip but I would prefer to avoid adding pip dependencies.
debian: https://packages.debian.org/sid/main/python3-collada
fedora: https://fedora.pkgs.org/31/fedora-aarch64/python3-collada-0.6-3.fc31.noarch.rpm.html
ubuntu: https://packages.ubuntu.com/focal/python3-collada

Thank you @clalancette for your pertinent comments, it should be fixed now.

Any news about the merge of this PR?

@clalancette: when can we expect to see this PR merged?


Update index.html

added universal paperclips
https://www.decisionproblem.com/paperclips/index2.html

merging with some changes. might move the link later.


Release the logger image

What this PR does / why we need it:
I saw the logger is already in the configmap, but checked it's not released so we cannot use the image yet.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

This change is

/assign @yuzisun @cliveseldon

Great. Not sure how I missed this. Thanks for adding.

/approve /lgtm

/lgtm

Why is this not auto merged? Seems all checks have passed...

Try to retest? That's strange...
/retest

/lgtm


remove wi_locness dataset due to licensing issues

It was brought to my attention that this dataset's license is not only missing, but also prohibits redistribution. I contacted the original author to apologize for this oversight and asked if we could still use it, but unfortunately we can't and the author kindly asked to take down this dataset.

Hi ! I'm sorry to hear that.
Though we are not redistributing the dataset, we just provide a python script that downloads and process the dataset from its original source hosted at https://www.cl.cam.ac.uk
Therefore I'm not sure what's the issue with licensing. What do you mean exactly ?

I think that the main issue is that the licesenses of the data are not made clear in the huggingface hub – other people wrongly assumed that the data was license-free, which resulted in commercial use, which is against the licenses.
Is it possible to add the licenses from the original download to huggingface? that would help clear any confusion (licenses can be found here: https://www.cl.cam.ac.uk/research/nl/bea2019st/data/wi+locness_v2.1.bea19.tar.gz)

Thanks for the clarification @SimonHFL
You're completely right, we need to show the licenses.
I just added the them here: https://huggingface.co/datasets/wi_locness#licensing-information

Hi guys, I'm one of the authors of this dataset.
To clarify, we're happy for you to keep the data in the repo on 2 conditions:

You don't host the data yourself.
You make it clear that anyone who downloads the data via HuggingFace should read and abide by the license.

I think you've now met these conditions, so we're all good, but I just wanted to make it clear in case there are any issues in the future. Thanks again to @aseifert for bringing this to our attention! :)

Thanks for your message @chrisjbryant :)
I'm closing this PR then.
And thanks for reporting @aseifert


bump version to node 20 and vscode 1.91.0

This PR bumps the esbuild target to node20 and sets the minimum vscode engine version to 1.91.0. This recent update to vscode bricked my direnv extension (it gets stuck on always loading in my project).
Building and installing with this patch seems to have resolved it. Sorry, I am not sure why the tests are failing. Hope this helps!
Version: 1.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286
Date: 2024-07-01T18:53:23.353Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0

direnv --version
2.34.0

Thanks for your contribution!Could you explain the upside of doing this?In the past I've updated the required vscode version when I had to to use a new feature.On 8. Jul 2024, at 16:11, Big Boss @.***> wrote:
You can view, comment on, or merge this pull request online at:
  https://github.com/direnv/direnv-vscode/pull/801
Commit Summary
6246e2c  bump version to node 20 and vscode 1.91.0
File Changes  (2 files)
M
package-lock.json
(20)

M
package.json
(8)

Patch Links:
https://github.com/direnv/direnv-vscode/pull/801.patch
https://github.com/direnv/direnv-vscode/pull/801.diff
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Sorry, I don't have much context on how vscode versioning works with respect to extensions. I upgraded it since this vscode version upgrade electron and the nodejs version. https://code.visualstudio.com/updates/v1_90#_electron-29-update
Though, I guess I should have perhaps opened this up as an issue. The direnv vscode extension stuck on loading is what prompted me to investigate and ultimately try this patch.
Funny enough, no idea what's actually happening though since I reinstalled v0.17.0 today and everything works again. 🤷 Going to close.


Use cytoscapejs APIs everywhere + inheritance model for Node and Edge

Building on https://github.com/QuantStack/ipycytoscape/pull/106 (so all the changes from there are in these diffs) I used the viewLists to use the cytoscapejs api to update the graph when any individual element's attributes change as well as for adding new elements to the graph. With this I think almost every update to the graph will be smooth (no re-rendering of the whole graph)!

split the widget.ts file into two files, one for the widget and one for all the graph elements
Node and Edge both inherit from Element which provides methods for all the shared attributes

reduced duplication of code

Edge actually had several properties that were only for nodes. I removed these
The pannable property was missing so I added this to Element
Used the viewLists to handle adding of elements to the graph and eliminated the array of elements previously held by the graph object

This also made it easier to add and keep track of new elements that get added to the graph after creation

Added a method that allows user to force a a relayout

Should be easy to add more methods like center using the same framework

Used the types from types/cytoscape in more places
added __all__ to python to reduce the number of items exported

Two design notes:

For the qualities like locked or pannable cytoscapejs actually provides three functions. One to query the value and then one each for turning it on or off. Instead of expose all of these I just exposed the boolean value on the python side and then do some checking on the typescript side to call the appropriate cytoscapejs function.
I wasn't sure whether the graph should re-layout when a user adds another element after the initial creation. I ended up making it behave this way, but it could easily be changed. Or even just the new elements could be made to layout again. I left a comment about this.

Finally:

I took the forEachView function from ipycanvas. I'm not sure how is best to acknowledge this. A comment next to the function?
There's still no easy way to remove an element from the graph.

@marimeireles no rush but can you look at this sometime? I think this will extend the performance enhancements of using cytoscapejs api to pretty much everywhere that is possible. It will also make it much easier to keep views in sync which will help with things like saving images as well as enabling methods like: https://js.cytoscape.org/#eles.flashClass

Thanks for the many comments! I'll look at them a bit later. But real quick maybe something is weird with your traitlets install? I can import CaselessStrEnum with the latest version on conda forge:

Thanks for that @ianhi. Will try in a clean environment :)

I'm not sure about the use of async.

What are you referring to?

That's so true.
Thanks! Sorry I missed that.

I just rebased and did some trimming, if you have nothing else to add, we can merge :)

bump of this @marimeireles @MridulS

Gonna review it again and test it now @ianhi sorry for taking such a long time!

Thanks a lot Ian! 🌸

Got really carried away trying to get the node positions to:

sync back to python
sync between views

I made some progress:

but sometimes it can very buggy, like all the edges disconnect from the nodes. Or a node will dissappear or they just won't sync:

So maybe it's best to leave that syncing for another PR? Chasing after that prevented me from finishing responding to your other comments.

rebased on master to pick up the tests so that I could fix them for this branch. Still need to address https://github.com/QuantStack/ipycytoscape/pull/109#discussion_r480360045 and do a thorough local test to make sure everything still renders correctly

Sweeet Ian. I'll have a look tonite :)
thank you very much

Okay, a lot to take in here :)
I won't be able to finish this today, sorry!
First thing on my list tomorrow. Thanks again.

Okay, a lot to take in here :)

yes definitely a lot. No pressure timing wise! As you say it is kind of a big change so it's better to get it right than to get it done

So while your changes allows to some great things like this:

It's also causing some weird behavior, I guess:

My initial opinion is that we don't do this syncing in this PR, as you already proposed. I wanna dive in further though, maybe I can give some useful input on this.

Ack! That weird behavior is definitely no good. Though I don't really know what might be causing that. Does it only happen when you display the same graph more than once?

Soorryyy for taking so long!

Soorryyy for taking so long!

no i think this is on me. There was that bug you found and then I got very distracted wiht work so I never properly resolved it.
I'm a little worried about the last issue you brought up, but otherwise this is an improvement.
Probs deserves more than a patch version bump bc several parts of api to the user change with this

Which one? Sorry, the one about being async await?

The "weird behavior" from https://github.com/QuantStack/ipycytoscape/pull/109#issuecomment-702803882

aw yeah
but I reproduced it on master, so
not a problem of ur pr specifically :)

oh really? I guess we just never noticed that being a problem. Maybe a new issue for that, bc thats clearly a bug


Prevent animation from reoccurring after every progress

Hey, I was wondering how to prevent the button from animating after every time you record. Would love it if the button did the animation and stayed in it's recording state and every subsequent press and release it did not keep doing the animation. Thanks!

Hi @dlush315,
Cool that your using the RecordButton, what are you using it for?
It's not possible in the current version, so you can do two things: 1. Copy the code from RecordButton.swift to your own project and modifying the code a little or 2. fork this repo, make the same changes, and submit a PR. I'm fine with both, but the seconds one would be better as other people can also use your new implementation.
Anyways, the code you need  to change:
Remove the else statement in the didTouchUp-fucntion. This makes sure the recordButton doesn't return to it's idle state. Result looks like this:
    public func didTouchUp() {
        if(closeWhenFinished) {
            self.setProgress(1)

            UIView.animateWithDuration(0.3, animations: {
                self.buttonState = .Hidden
                }, completion: { completion in
                    self.setProgress(0)
                    self.currentProgress = 0
            })
        }
    }

(make sure you have closeWhenFinished set to false on your button)
Then in  didTouchDown make sure it doesn't set the Recording state everytime you press the button. Like this:
    public func didTouchDown(){
        if self.buttonState != .Recording {
            self.buttonState = .Recording

        }
    }

Now, if you want the button to return to the Idle mode (the blue mode) when the circle is full. I'm not sure if you want this, but if you do, modify the setProgress function so that it returns back to the idle state after it's 100%, like this:
    public func setProgress(newProgress: CGFloat) {
        if newProgress > 1 {
            self.buttonState = .Idle
        } else {
            progressLayer.strokeEnd = newProgress
        }
    }

I hope it works out, and if so: it'd be great if you submitted a PR, so that this becomes a mode that other people can use too. I would put all this functionality under a boolean named allowContinuousRecording or something similar.
Let me know if you need more help.

Thanks, I ended up modifying the code to do what I wanted and this helped!


fix: add keystone sync user debug info

这个 PR 实现什么功能/修复什么问题:
修正：LDAP配置加载时候引入了额外的冗余字段

是否需要 backport 到之前的 release 分支:
NONE

/cc @zexi
/area keystone

Codecov Report

Merging #7633 into master will increase coverage by 2.77%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #7633      +/-   ##
=========================================
+ Coverage    6.22%   9.00%   +2.77%
=========================================
  Files         563     457     -106
  Lines      103248   65915   -37333
=========================================
- Hits         6431    5938     -493
+ Misses      96345   59476   -36869
- Partials      472     501      +29

Flag
Coverage Δ

#aFlag
9.00% <ø> (+2.77%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/loadbalancerawscachedlbb.go

pkg/monitor/tsdb/request.go

pkg/compute/models/groupjoints.go

pkg/compute/models/loadbalanceraclresource.go

pkg/compute/models/loadbalancers.go

pkg/hostman/system_service/ntpd.go

pkg/appsrv/stats.go

pkg/compute/models/loadbalancercachedacls.go

pkg/compute/models/snapshotpolicyresource.go

pkg/compute/models/purge.go

... and 392 more

Continue to review full report at Codecov.

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

/lgtm
/approve


Unknown class for modules without any parameter

When i want to create a module with no parameters i get an unknown class. For example PointToPoint- and PointToPointSimilarityErrorMinimizer or the RemoveNaNDataPointsFilter. I created the module just like explained in the examples.The ICP seems to work anyhow, is this behaviour wanted?

I already solved the problem, i just needed the classname to write the module to a yaml file. I will close the "issue" ;)


Buffer with uint8_t type invalid encoding

Version of Beast
Latest develop
Steps necessary to reproduce the problem
void sendResponse(websocket::stream<tcp::socket>& ws)
 {
  std::array<uint8_t, 1> err_buff{{ static_cast<uint8_t>(140) }};
  ws.binary();
  ws.write(std::array<boost::asio::const_buffer, 1>{{
    { err_buff.data(), err_buff.size() }
  }});
}

clang 4.0.1
Calling it via the browser like this:
const socket = new WebSocket('ws://localhost:3003');
socket.addEventListener('message', (event) => {
  console.log("Server sent: ", event.data);
});
socket.addEventListener('open', (event) => { socket.send("hello"); });

Results in: failed: Could not decode a text frame as UTF-8
Changing the number from 140 to something below 128 avoids this error.
Which makes me think it has something to do with interpreting the buffer in a certain way.
It'b be great to have a fast response, as this is somewhat of a roadblock.

140 is not a value character for the first byte of a UTF-8 code point.  If you want to send binary data, set the message type to binary before sending the message data, like this:
socket.binaryt(true);

Ok thanks, looking at binary() I misread the == for and =.

Btw, any reason you use std::bind over lambdas? The latter is both cleaner and produces better assembly.

The generated assembly should be no different. Can you give me an example of a piece of existing example code, and how you think it should look? Keep in mind, it has to be C++11 only (so no auto parameters in lambdas, or capture expressions).

Ok, so std::bind is not as bad as I had in memory. Given C++11 as requirement Some reason for using it.
However lambdas are cleaner as they are a direct compiler construct and are aloud to have no size. Also if called improperly can lead to loss of performance.

So I should stick with the std::bind? Do you want to provide an example of a lambda at a call site from one of the beast example programs?

Wherever possible use lambdas, as it also avoids the the <functional> dependency.
Small self contained example
Try replacing ret_a with a constant.
From the websocket_async_server example:
void run()
{
  ws_.async_accept(
    strand_.wrap(
      std::bind(
        &session::on_accept,
        shared_from_this(),
        std::placeholders::_1
      )
    )
  );
}

Improved version
void run()
{
  ws_async_accept(
    strand_.wrap(
      [this](boost::system::error_code ec) { on_accept(ec); }
    )
  );
}

Completely unrelated, how would you suggest to do a websocket broadcast? Should I keep track of all the sessions myself?

[this](boost::system::error_code ec) { on_accept(ec); }

That looks very nice! There's just one problem, this will cause the socket to close prematurely. The original code binds a copy of shared_from_this() into the call wrapper, while the new version does not.

how would you suggest to do a websocket broadcast? Should I keep track of all the sessions myself?

Yes. And you probably will need to implement an outgoing message queue, to handle the case where you want to broadcast while there is already an asynchronous write in progress on a stream. Also, remember that websocket streams (like asio sockets) are not thread safe. You can't call async_write from foreign threads. You need to call async_write from the same implicit or explicit strand.
In practice, this means that when you want to send a message on a stream from a foreign thread, you need to call io_service::post with a completion handler that does the actual send.

Okay, are you all squared up now? Is there still something that needs attention?

All good. However I'd like to hijack this thread and give you the opportunity to stop me from showcasing anything blatantly wrong. Same as you, I'm presenting a talk at this years cppcon. It focuses heavily on websockets, so one of the libraries I'll compare is beast. You can find my current example implementation here. Ignore the poll_data_.result.ref() related UB, It'll be fixed.
If you are busy or don't want to take a look. That's totally fine.
Thanks for the great help so far!

I had a look at the repository. I could do a code review if you want, you just need to open up a pull request against your own branch so that I can comment. With respect to your presentation, I have to remind you that Beast is a low-level library. It does not try to implement a client or server in a few lines of code. Instead, it is a thin protocol layering on top of Boost.Asio. It is the library that someone might use to write a higher-level library which DOES implement a simple interface to produce a server or web service. This goes for the HTTP interfaces as well as the WebSocket interfaces. As you noted, Beast does not have WebSocket broadcast facilities built-in to it and likely never will, since the management of individual connections is beyond the scope of the library. But hopefully someone will write a higher level library on top of it.

I'll try my best to convey that beast is not a high level abstraction, much rather a toolkit to implement such, and by that, tries to achieve a different goal and should be compared accordingly.
A code review would be great. The 2 best ways I found to create a review of a single file. Is to either create a pull from the earliest non related commit like this. Note there is a lot of clutter this way, as every other change is also included. Or you could comment on the individual commits found via the blame overview.

It is a goal of beast to be proposed for standardization in C++. i.e. std::http::message, std::websocket::stream. The design of the library is based on this outcome.

Nothing bad jumped out from looking over your code

Great! Thanks for your time. I'll close this now, see you at cppcon.


Redis in queue

Do It is necessary to use REDIS for the jobs to work?

Yes it does @jos3duardo . This package depends on bee-queue which utilizes REDIS by default. We are working on incorporating other drivers like rabbitmq. If you have suggestions: please let us know.

Closing out now.... Since no further activity here


HTTP Error codes

Need to return proper HTTP error codes when exceptions are being thrown on purpose or by mistake.

Focusing on 404 for this ticket, but going to create a separate ticket for 400.