Add Firefox Artefact

Add Firefox artefact

Can one of the admins verify this patch?

Hi @mikaelkrief, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

Yes, admins can verify this patch

Firefox would be nice to have.
Please approve soon :smile:

@mithunshanbhag : Ok I'll try with temporary user, like 7-zip

use temporary user for install is commited #62

LGTM. Merging this to master.


Add data plane API swagger for attestation

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

hi @shleiAmy could you pls fix CI failure while waiting for API review board reviewing?

@yungezz @LarryOsterman I have resubmit the pr which should fix the ModelValidation error and LintDiff failed error.
But for the LintDiff error, I don't understand why the data plane APIs need to meet the Arm Specs
R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers//operations'.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:26
R3013 - DeleteMustNotHaveRequestBody
'Delete' operation 'Policy_Delete' must not have a request body.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:222

test

@yungezz @LarryOsterman
I have resubmit the pr which should fix the ModelValidation error and LintDiff failed error.
But for the LintDiff error, I don't understand why the data plane APIs need to meet the Arm Specs:
R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers//operations'.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:26
R3013 - DeleteMustNotHaveRequestBody
'Delete' operation 'Policy_Delete' must not have a request body.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:222

HI @shleiAmy they're all rest api. If you have some exception, can discuss it with reviewing board. To ignore the validation errors.

@yungezz
The pr is marked as WaitingForAzureAPIBoard  for a couple of days.
But I was told by Azure Resource Manager RP API review team that they don't handle data plane reviews. and those data plane reviews are handled by azureapirbcore
I tried to send an email to azureapirbcore, but got rejection from this email address.
Could you please forward this pr to the correct team to next step review?
because We are waiting to finalize the swagger, then publish SDK, and complete powershell/cli cmdlets to meet our public preview deadline.
Thanks.

@yungezz
The pr is marked as WaitingForAzureAPIBoard for a couple of days.
But I was told by Azure Resource Manager RP API review team that they don't handle data plane reviews. and those data plane reviews are handled by azureapirbcore
I tried to send an email to azureapirbcore, but got rejection from this email address.
Could you please forward this pr to the correct team to next step review?
because We are waiting to finalize the swagger, then publish SDK, and complete powershell/cli cmdlets to meet our public preview deadline.
Thanks.

hi @shleiAmy, I've sent email to review board several days ago, you're in the email also, title "pls help to review PR https://github.com/Azure/azure-rest-api-specs/pull/7521". you'll share more in the thread about service schedule for ping for reviewing.

meanwhile, pls fix CI failure to be prepared.

@yungezz
The CI fails for the ARM errors:
R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers//operations'.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:26
R3013 - DeleteMustNotHaveRequestBody
'Delete' operation 'Policy_Delete' must not have a request body.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:218
This is the data plane API, why it need to meet the ARM specs?

hi @shleiAmy are all comments addressed? Is the PR ready for reviewing again?

@yungezz yes, the pr is waiting for review again
Thanks

Hi @shleiAmy  pls fixing LintDiff CI failure.
hi @johanste could you pls review the PR again?

@yungezz As I mentioned on Oct 25
The CI fails for the ARM errors:
R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers//operations'.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:26
R3013 - DeleteMustNotHaveRequestBody
'Delete' operation 'Policy_Delete' must not have a request body.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:218
This is the data plane APIs, why it needs to meet the ARM specs?
Is there any Azure API design guidelines that we should follow?
If I have to fix the CI failure, then the Policy_Delete should not have a request body.
I add @LarryOsterman for this dicussion.

@yungezz The CI fails for two errors:
R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers//operations'.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:26
R3013 - DeleteMustNotHaveRequestBody
'Delete' operation 'Policy_Delete' must not have a request body.
at specification/attestation/data-plane/Microsoft.Attestation/preview/2018-09-01-preview/attestation.json:218
I just change the Route from
"operations/policy/current" ->policy/current"
"operations/policy/updatepolicy"->"policy/updatepolicy"
to get rid of the keywords "operations".
however, the CI still fails for the same error
I don't know why it keeps on complaining Operations API must be implemented for '/providers//operations'.
@johanste we have explained why we need a request body in delete operation. And haven't heard back from you since Nov 4th.

pending on review board comments.

approved in azureapirb

/azp run automation - sdk

@yungezz I have fixed the failure for required CI check. And also I see this or is approved by azure api group. Could you please take some time to review this pr ? I am waiting for the data plane swagger to publish and then work on publishing SDK, poweshell and cli cmdlets.And I am blocked by this pr.  Thanks.

approved in azureapirb

HI @rysweet  could you pls label the PR "AzureAPIBoardSignedOff"? then we'll go ahead to merge this PR. thanks.


Documentation for rds-data usage

Confirm by changing [ ] to [x] below:

[x] I've gone though Developer Guide and API reference
[x] I've searched for previous similar issues and didn't find any solution

Platform/OS/Hardware/Device
What are you running the sdk on?
Docker/ubuntu:latest
Describe the question
Hi, all. I was wondering where I can find documentation or example code for querying an Amazon RDS Postgres database from my C++ application. I couldn't find any through amazon documentation or in Github issues. If I simply want to query this database, is the aws-sdk the best choice, or should I just use SQLAPI++ or some similar API for interfacing with regular PostgreSQL databases?

Hi @justinpchang ,
Yea we don't have that many doc samples for our services... Good news is we do have integration tests on RDS, you could use those to guide you on how to use the service.
Look here.
Let me know if this helps. Or if you have other more specific questions


Units for viscosity?

Hi, thanks for this great simulator. I had a couple of quick questions on the viscosity method, assuming we were to use the 'standard' method:

Does the model take in the dynamic or kinematic viscosity? The docs seem to say kinematic viscosity, but I took a quick look at the source code and it seemed to treat the input as dynamic viscosity. I could be wrong here, so wanted to confirm.

What are the units for the viscosity? In other words - if I wanted to simulate water, what value with what units should I input?

Thanks very much in advance for your help!

Hi,

It is the kinematic viscosity. Maybe the code is a bit confusing due to optimizations but I just checked it again.
The units are the standard units (see also here: https://en.wikipedia.org/wiki/Viscosity): m^2/s

Hope that helps!


Pod to Pod Communcation severely degraded in 4.11 on vSphere

Describe the bug
We run okd in a vSphere environment with the below configuration:
vSphere:
ESXi version: 7.0 U3e
Seperate vDS (on version 6.5) for Front End and iSCSI

Hardware:
UCS B200-M4 Blade
	BIOS - B200M<IP_ADDRESS>a.0.0202211902
	Xeon(R) CPU E5-2667
	2 x 20Gb Cisco UCS VIC 1340 network adapter for front end connectivity (Firmware 4.5(1a))
	2 x 20Gb Cisco UCS VIC 1340 network adapter for iSCSI connectivity (Firmware 4.5(1a))

Storage:
Compellent SC4020 over iSCSI
	2 controller array with dual iSCSI IP connectivity (2 paths per LUN)
All cluster nodes on same Datastore

After upgrading the cluster from a 4.10.x version to anything above 4.11.x pod to pod communication is severely degraded where the nodes that the pods run on are hosted on different esx hosts. We ran a benchmark test on the cluster before the upgrade with the below results:
Benchmark Results

Name : knb-2672
Date : 2023-03-29 15:26:01 UTC
Generator : knb
Version : 1.5.0
Server : k8s-se-internal-01-582st-worker-n2wtp
Client : k8s-se-internal-01-582st-worker-cv7cd
UDP Socket size : auto

Discovered CPU : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz
Discovered Kernel : 5.18.5-100.fc35.x86_64
Discovered k8s version : v1.23.5-rc.0.2076+8cfebb1ce4a59f-dirty
Discovered MTU : 1400
Idle :
bandwidth = 0 Mbit/s
client cpu = total 12.31% (user 9.41%, nice 0.00%, system 2.83%, iowait 0.07%, steal 0.00%)
server cpu = total 9.04% (user 6.28%, nice 0.00%, system 2.74%, iowait 0.02%, steal 0.00%)
client ram = 4440 MB
server ram = 3828 MB
Pod to pod :
TCP :
bandwidth = 6306 Mbit/s
client cpu = total 26.15% (user 5.19%, nice 0.00%, system 20.96%, iowait 0.00%, steal 0.00%)
server cpu = total 29.39% (user 8.13%, nice 0.00%, system 21.26%, iowait 0.00%, steal 0.00%)
client ram = 4460 MB
server ram = 3820 MB
UDP :
bandwidth = 1424 Mbit/s
client cpu = total 26.08% (user 7.21%, nice 0.00%, system 18.82%, iowait 0.05%, steal 0.00%)
server cpu = total 24.82% (user 6.72%, nice 0.00%, system 18.05%, iowait 0.05%, steal 0.00%)
client ram = 4444 MB
server ram = 3824 MB
Pod to Service :
TCP :
bandwidth = 6227 Mbit/s
client cpu = total 27.90% (user 5.12%, nice 0.00%, system 22.73%, iowait 0.05%, steal 0.00%)
server cpu = total 29.85% (user 5.86%, nice 0.00%, system 23.99%, iowait 0.00%, steal 0.00%)
client ram = 4439 MB
server ram = 3811 MB
UDP :
bandwidth = 1576 Mbit/s
client cpu = total 32.31% (user 6.41%, nice 0.00%, system 25.90%, iowait 0.00%, steal 0.00%)
server cpu = total 26.12% (user 5.68%, nice 0.00%, system 20.39%, iowait 0.05%, steal 0.00%)
client ram = 4449 MB
server ram = 3818 MB

After upgrading to version 4.11.0-0.okd-2023-01-14-152430 the latency between the pods is so high the benchmark test, qperf test, and iperf test all timeout and fail to run.  This is the result of curling the network check pod across nodes, it takes close to 30 seconds.
sh-4.4# time curl http://<IP_ADDRESS>:8080
Hello, <IP_ADDRESS>. You have reached <IP_ADDRESS> on k8s-se-internal-01-582st-worker-cv7cd
real    0m26.496s

We have been able to reproduce this issue consistently on multiple different clusters.
Version
4.11.0-0.okd-2023-01-14-152430
IPI on vSphere
How reproducible
Upgrade or install a 4.11.x or higher version of OKD and observe the latency.

What is the VMware hardware version of the VMs?

They are:
ESXi 6.7 U2 and later (VM version 15)

Yes we upgraded a cluster to 4.12 and were able to reproduce it.

Right, so its possibly kernel module or OVN have regressed. Could you check if node-to-node performance has degraded too? If yes, its probably a Fedora / kernel regression

Node to node performance is good, I tested on the nodes themselves using the toolbox
[  1] local <IP_ADDRESS> port 32934 connected with <IP_ADDRESS> port 5001 (icwnd/mss/irtt=14/1448/241)
[ ID] Interval       Transfer     Bandwidth
[  1] 0.00-10.01 sec  8.01 GBytes  6.87 Gbits/sec

In that case its probably OVN. I wonder if we could confirm its OKD specific?

We have a few OCP cluster at 4.11 and I haven't been able to reproduce the problem in them.

When you jump from 4.11 (4.11.0-0.okd-2022-08-20-022919 or so) to 4.12.0-0.okd-2023-02-18-033438 or newer you should see better network performance.

When you jump from 4.11 (4.11.0-0.okd-2022-08-20-022919 or so) to 4.12.0-0.okd-2023-02-18-033438 or newer you should see better network performance.

That is not the case for us, I have upgraded to version 4.12.0-0.okd-2023-04-01-051724 and am still seeing the same issues. I still can't run any test across pods without them timing out.

Do we need to open an issue in the ovn-kubernetes repository?
How do I figure out what release of ovn-kubernetes is in a specific version of okd?

We re-deployed the cluster with version 4.10.0-0.okd-2022-07-09-073606 on the same hardware and the issue went away. There is clearly an issue with 4.11 and above. Benchmark results are below:
=========================================================
 Benchmark Results
=========================================================
 Name            : knb-17886
 Date            : 2023-04-10 19:46:01 UTC
 Generator       : knb
 Version         : 1.5.0
 Server          : k8s-se-platform-01-t4fb6-worker-vw2d9
 Client          : k8s-se-platform-01-t4fb6-worker-jk2wm
 UDP Socket size : auto
=========================================================
  Discovered CPU         : Intel(R) Xeon(R) Gold 6334 CPU @ 3.60GHz
  Discovered Kernel      : 5.18.5-100.fc35.x86_64
  Discovered k8s version : v1.23.5-rc.0.2076+8cfebb1ce4a59f-dirty
  Discovered MTU         : 1400
  Idle :
    bandwidth = 0 Mbit/s
    client cpu = total 4.06% (user 2.17%, nice 0.00%, system 1.82%, iowait 0.07%, steal 0.00%)
    server cpu = total 2.96% (user 1.48%, nice 0.00%, system 1.48%, iowait 0.00%, steal 0.00%)
    client ram = 925 MB
    server ram = 1198 MB
  Pod to pod :
    TCP :
      bandwidth = 8348 Mbit/s
      client cpu = total 26.07% (user 1.78%, nice 0.00%, system 24.27%, iowait 0.02%, steal 0.00%)
      server cpu = total 26.59% (user 1.94%, nice 0.00%, system 24.63%, iowait 0.02%, steal 0.00%)
      client ram = 930 MB
      server ram = 1196 MB
    UDP :
      bandwidth = 1666 Mbit/s
      client cpu = total 19.21% (user 2.14%, nice 0.00%, system 17.02%, iowait 0.05%, steal 0.00%)
      server cpu = total 22.51% (user 2.91%, nice 0.00%, system 19.55%, iowait 0.05%, steal 0.00%)
      client ram = 924 MB
      server ram = 1201 MB
  Pod to Service :
    TCP :
      bandwidth = 8274 Mbit/s
      client cpu = total 26.55% (user 1.78%, nice 0.00%, system 24.77%, iowait 0.00%, steal 0.00%)
      server cpu = total 26.37% (user 2.67%, nice 0.00%, system 23.68%, iowait 0.02%, steal 0.00%)
      client ram = 922 MB
      server ram = 1191 MB
    UDP :
      bandwidth = 1635 Mbit/s
      client cpu = total 20.19% (user 1.60%, nice 0.00%, system 18.54%, iowait 0.05%, steal 0.00%)
      server cpu = total 21.80% (user 2.82%, nice 0.00%, system 18.98%, iowait 0.00%, steal 0.00%)
      client ram = 913 MB
      server ram = 1179 MB
=========================================================

=========================================================
qperf
======================================================

/ # qperf <IP_ADDRESS> tcp_bw tcp_lat
tcp_bw:
    bw  =  907 MB/sec
tcp_lat:
    latency  =  70.6 us
/ # qperf <IP_ADDRESS> tcp_bw tcp_lat
tcp_bw:
    bw  =  1 GB/sec
tcp_lat:
    latency  =  68.2 us

===

I tested this on a cluster using openshiftSDN, deployed version 4.10 upgraded to 4.11 and was able to replicate the issue. So, it's not specific to OVN.

I tested this on a cluster using openshiftSDN, deployed version 4.10 upgraded to 4.11 and was able to replicate the issue. So, it's not specific to OVN.

So, the issue #1564 is reproducible that case.

Version and build numbers of ESXi please
FCOS kernel version
Have you tried a test where all the OKD nodes are on the same physical esxi host?

Yes, for #1563, I checked that all the nodes (except the remote worker nodes)  master, storage and worker  are already on the same esx host (ESXi 6.7 and later (VM version 14))

I will try to reproduce here but it would be good to know if I am replicating to what was already provisioned. Again can I get ESXi version and build numbers, FCOS kernel version - please be specific.
Remember vSphere 6.x is EOL and some older versions have issues with VXLAN w/ESXi and kernel drivers.

I will try to reproduce here but it would be good to know if I am replicating to what was already provisioned. Again can I get ESXi version and build numbers, FCOS kernel version - please be specific.
Remember vSphere 6.x is EOL and some older versions have issues with VXLAN w/ESXi and kernel drivers.

Not really seeing a problem here Each pod in the above test was on different FCOS nodes, residing on different physical esxi hosts.

I can't even get iperf tests to run when the pods are on hosts that are on different esx hosts, it just times out.

In my case I can't even get the console up anymore. I've reproduced it over and over and now it looks like someone else has also. Not sure what to do other than stay at 4.10.

@MattPOlson based on your previous comments this looks to me like MTU or something with VXLAN. Have you checked all the virtual switches, physical device MTU?
And is it correct in stating with all the guests reside together is no performance issue? Is it a specific ESXi host that is ok?

@MattPOlson based on your previous comments this looks to me like MTU or something with VXLAN. Have you checked all the virtual switches, physical device MTU?
And is it correct in stating with all the guests reside together is no performance issue? Is it a specific ESXi host that is ok?

We've tried MTU settings, set them to match the host. But why would that affect 4.11 and not 4.10? I can spin up a cluster on 4.10 and it works perfectly, upgrade it to 4.11 and change nothing else and it breaks.
And yea if all the nodes reside together there is no issue.

And yea if all the nodes reside together there is no issue.

Don't you find that odd? If the problem occurs when packets are leaving the ESXi host then I would suspect something physical. I can't comment to why the version would make a difference but I can't reproduce.

And yea if all the nodes reside together there is no issue.

Don't you find that odd? If the problem occurs when packets are leaving the ESXi host then I would suspect something physical. I can't comment to why the version would make a difference but I can't reproduce.

Agree but I also find it odd that upgrading to 4.11 breaks it and someone else was able to reproduce it. To me that feels like it's not something specific to our environment.

And yea if all the nodes reside together there is no issue.

Don't you find that odd? If the problem occurs when packets are leaving the ESXi host then I would suspect something physical. I can't comment to why the version would make a difference but I can't reproduce.

Agree but I also find it odd that upgrading to 4.11 breaks it and someone else was able to reproduce it. To me that feels like it's not something specific to our environment.

We do test OCP and OKD in multiple different vSphere environments and haven't seen this issue. Maybe you and @imdmahajankanika stumbled into the same problem?
The question is what is the commonality.

And yea if all the nodes reside together there is no issue.

Don't you find that odd? If the problem occurs when packets are leaving the ESXi host then I would suspect something physical. I can't comment to why the version would make a difference but I can't reproduce.

Agree but I also find it odd that upgrading to 4.11 breaks it and someone else was able to reproduce it. To me that feels like it's not something specific to our environment.

We do test OCP and OKD in multiple different vSphere environments and haven't seen this issue. Maybe you and @imdmahajankanika stumbled into the same problem?
The question is what is the commonality.

Right, that is the question.
Interestingly we have a few OCP clusters running at 4.11 on the exact same hardware and don't see the issue there.

After upgrading our clusters from 4.10.0-0.okd-2022-07-09-073606 to 4.11.0-0.okd-2023-01-14-152430 connectivity betwenn kube-apiserver and all other apiservers was lost. Our master nodes all run on VSphere. We could fix the issue by running:
ethtool -K ens192 tx-udp_tnl-segmentation off
ethtool -K ens192 tx-udp_tnl-csum-segmentation off

on the master nodes. I have a feeling that we are looking at the very old bug: https://github.com/openshift/machine-config-operator/pull/2482
Could you check the state of tunnel offloading on your nodes with ethtool -k <your-primary-interface> | grep tx-udp?

That shouldn't be an issue as we haven't removed the workaround
https://github.com/openshift/machine-config-operator/blob/master/templates/common/_base/files/vsphere-disable-vmxnet3v4-features.yaml
And it is in specific older ESXi versions, if you are hitting the VXLAN offloading bug you need to upgrade your hosts.

That shouldn't be an issue as we haven't removed the workaround
https://github.com/openshift/machine-config-operator/blob/master/templates/common/_base/files/vsphere-disable-vmxnet3v4-features.yaml
And it is in specific older ESXi versions, if you are hitting the VXLAN offloading bug you need to upgrade your hosts.

I thnk I figured it out, your workaround isn't working anymore, looks like there is a permission issue and the NetworkManager-dispatcher.service is failing to apply the scripts in the directory /etc/NetworkManager/dispatcher.d/99-vsphere-disable-tx-udp-tnl
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:12 'connectivity-change': find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:13 'up' [ens192]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:14 'up' [br-ex]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:15 'pre-up' [ens192]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d/pre-up.d': Error opening directory “/etc/NetworkManager/dispatcher.d/pre-up.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:16 'up' [ens192]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:17 'dhcp4-change' [br-ex]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:18 'pre-up' [br-ex]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d/pre-up.d': Error opening directory “/etc/NetworkManager/dispatcher.d/pre-up.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:19 'up' [br-ex]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:57:51 k8s-se-internal-01-582st-master-0 nm-dispatcher[1466]: req:20 'connectivity-change': find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
Apr 03 14:58:01 k8s-se-internal-01-582st-master-0 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Disabling tunnel offloading seems to fix the problem. I'm looking into why that script is now getting permission denied errors.

VMware only updated their release notes for 6.7 that resolves this issue. I am unsure what 7.x build fixes it.
We are running the close to the latest versions of 7 and 8.
Certainly need to figure out the permission issue, which is strange. I would figure other dispatch scripts would be breaking too.

It looks like this bug was already reported and fixed, but I'm definitely still seeing the issue in our environment
https://github.com/okd-project/okd/issues/1317

Perhaps its also https://github.com/okd-project/okd/issues/1475?

I think I figured something out, the script the service rhcos-selinux-policy-upgrade.service executes to reload selinux is never running because its looking for RHEL_VERSION in /usr/lib/os-release
That exists in Red Hat Enterprise Linux CoreOS but not in Fedora, therefore it's never hitting the line that calls semodule -B
#!/bin/bash
# Executed by rhcos-selinux-policy-upgrade.service
set -euo pipefail

RHEL_VERSION=$(. /usr/lib/os-release && echo ${RHEL_VERSION:-})
echo -n "RHEL_VERSION=${RHEL_VERSION:-}"
case "${RHEL_VERSION:-}" in
  8.[0-6]) echo "Checking for policy recompilation";;
  *) echo "Assuming we have new enough ostree"; exit 0;;
esac

ls -al /{usr/,}etc/selinux/targeted/policy/policy.31
if ! cmp --quiet /{usr/,}etc/selinux/targeted/policy/policy.31; then
    echo "Recompiling policy due to local modifications as workaround for https://bugzilla.redhat.com/2057497"
    semodule -B
fi

 cat . /usr/lib/os-release
cat: .: Is a directory
NAME="Fedora Linux"
VERSION="37.20230303.3.0 (CoreOS)"
ID=fedora
VERSION_ID=37
VERSION_CODENAME=""
PLATFORM_ID="platform:f37"
PRETTY_NAME="Fedora CoreOS 37.20230303.3.0"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:37"
HOME_URL="https://getfedora.org/coreos/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora-coreos/"
SUPPORT_URL="https://github.com/coreos/fedora-coreos-tracker/"
BUG_REPORT_URL="https://github.com/coreos/fedora-coreos-tracker/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=37
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=37
SUPPORT_END=2023-11-14
VARIANT="CoreOS"
VARIANT_ID=coreos
OSTREE_VERSION='37.20230303.3.0'

VMware only updated their release notes for 6.7 that resolves this issue. I am unsure what 7.x build fixes it. We are running the close to the latest versions of 7 and 8.

@jcpowermac  We are running on ESXi 7u3 and this issue should be fixed. Maybe this has come up again in newer versions of vmxnet3?

VMware only updated their release notes for 6.7 that resolves this issue. I am unsure what 7.x build fixes it. We are running the close to the latest versions of 7 and 8.

@jcpowermac We are running on ESXi 7u3 and this issue should be fixed. Maybe this has come up again in newer versions of vmxnet3?

@bo0ts I would suggest opening a support request with vmware. They own both aspects of this, the linux kernel driver [0] and ESXi.
[0] - https://github.com/torvalds/linux/commits/master/drivers/net/vmxnet3

Over in the Slack thread there is also discussion about why and where this occurs. We don't see that problem on our clusters. But perhaps we simply don't do enough intra cluster communications? Can you give us an easy test how I can verify if we indeed do not have the problem or just don't see it?

The easiest way is to deploy an iPerf client on one node and an iPerf server on another node, then run test between them to check performance.

Ok, I guess something like that: https://github.com/InfuseAI/k8s-iperf

I've had good luck with this one:
https://github.com/InfraBuilder/k8s-bench-suite

FROM quay.io/fedora/fedora:38
RUN dnf install -y iperf3 ttcp qperf
ENTRYPOINT trap : TERM INT; sleep infinity & wait # Listen for kill signals and exit quickly.

cat Dockerfile| oc new-build --name perf -D -

then created a deployment for both client and server
just gotta watch which node it lands on and destroy if necessary
then just oc rsh to run the commands
found this on a blog post somewhere ;-)

Hello! In my case, just by executing systemctl restart NetworkManager, it worked.

I also see the failed access in my environment. In my opinion, it is due to SeLinux.
May 25 09:25:11 localhost.localdomain NetworkManager[1088]: <info>  [1685006711.9105] manager: (patch-br-ex_worker1-cl1-dc3.s-ocp.cloud.mycompany.com-to-br-int): new Open vSwitch Port device (/org/freedesktop/NetworkManager/Devices/23)
May 25 09:25:11 localhost.localdomain audit[1099]: AVC avc:  denied  { read } for  pid=1099 comm="nm-dispatcher" name="dispatcher.d" dev="sda4" ino=109431351 scontext=system_u:system_r:NetworkManager_dispatcher_t:s0 tcontext=system_u:object_r:NetworkManager_initrc_exec_t:s0 tclass=dir permissive=0
May 25 09:25:11 localhost.localdomain audit[1099]: SYSCALL arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=56017b2615f0 a2=90800 a3=0 items=0 ppid=1 pid=1099 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="nm-dispatcher" exe="/usr/libexec/nm-dispatcher" subj=system_u:system_r:NetworkManager_dispatcher_t:s0 key=(null)
May 25 09:25:11 localhost.localdomain audit: PROCTITLE proctitle="/usr/libexec/nm-dispatcher"
May 25 09:25:11 localhost.localdomain nm-dispatcher[1099]: req:3 'hostname': find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied

I also see the failed access in my environment. In my opinion, it is due to SeLinux.
May 25 09:25:11 localhost.localdomain NetworkManager[1088]: <info>  [1685006711.9105] manager: (patch-br-ex_worker1-cl1-dc3.s-ocp.cloud.mycompany.com-to-br-int): new Open vSwitch Port device (/org/freedesktop/NetworkManager/Devices/23)
May 25 09:25:11 localhost.localdomain audit[1099]: AVC avc:  denied  { read } for  pid=1099 comm="nm-dispatcher" name="dispatcher.d" dev="sda4" ino=109431351 scontext=system_u:system_r:NetworkManager_dispatcher_t:s0 tcontext=system_u:object_r:NetworkManager_initrc_exec_t:s0 tclass=dir permissive=0
May 25 09:25:11 localhost.localdomain audit[1099]: SYSCALL arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=56017b2615f0 a2=90800 a3=0 items=0 ppid=1 pid=1099 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="nm-dispatcher" exe="/usr/libexec/nm-dispatcher" subj=system_u:system_r:NetworkManager_dispatcher_t:s0 key=(null)
May 25 09:25:11 localhost.localdomain audit: PROCTITLE proctitle="/usr/libexec/nm-dispatcher"
May 25 09:25:11 localhost.localdomain nm-dispatcher[1099]: req:3 'hostname': find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied

Hello, Did you try with  sudo  systemctl restart NetworkManager

I had tried systemctl restart NetworkManager on one node after your message without thinking further. This breaks the SSH connection and kills the command probably because of the missing parent process. I had to reset the node manually. I have not found anything to open any kind of tmux or screen session in FedoraCoreOS.
I can confirm that the offload parameters are also set in my environment.
[root@worker1-cl1-dc3 ~]# ethtool -k ens192 | grep tx-udp
tx-udp_tnl-segmentation: on
tx-udp_tnl-csum-segmentation: on
tx-udp-segmentation: off [fixed]

I ran network performance tests using iperf before and after changing the offload parameters. I used ethtool for changing the offload parameter.
ethtool -K ens192 tx-udp_tnl-segmentation off
ethtool -K ens192 tx-udp_tnl-csum-segmentation off

The difference between the tests is tiny. The network speed between two pods on different nodes and two VM is very large (between two VMs the speed is around 7x faster), but according to my current knowledge this is due to OVN.
I did not notice any network disconnections.


Plugin bumps TypeScript target?

When running nx g @angular-architects/module-federation:init, the following files are updated:

apps/{project}/tsconfig.app.json
tsconfig.base.json

Both files will update the TypeScript target to es2020. Is there a reason why this is done? Would it be possible to preserve the output target?

Unfortunately, we need es2020+. Since v13, the Angular CLI produces EcmaScript modules (instead of plain javascript files) and in this mode, Module Federation uses import.meta which is only available for es2020+.

@manfredsteyer - Thanks for the response. However, I still get the import.meta error with the targets bumped to es2020. My Angular dependencies point to ~14.2.0


Connect frontend to new Hasura3 API

What is it?
It's currently still connected to the Hasura2 deployment via NEXT_PUBLIC_DB_GRAPHQL_URL
This would be relatively easy, except for the fact that Hasura3 CLI camel-cases all of the schema, so our query types don't match anymore.
Another thought, should we just connect directly to Clickhouse for server-side queries, instead of through Hasura? Seems like added complexity / indirection. (Leaving the client-side components alone)

Since this issue tackles server-side queries
https://github.com/opensource-observer/oso/issues/1892
This issue has been downscoped to just fixing event-data-provider to use the new metrics stuff via API

Hasura configs here
https://github.com/opensource-observer/oso/pull/1921

deleting older graphql calls here
https://github.com/opensource-observer/oso/pull/1929

Adding first draft of metricsdataprovider here
https://github.com/opensource-observer/oso/pull/1932
I know this is currently broken because some API calls aren't working in general. Need to go back and find the issues there

Closing this out for now. We have a first draft done, but we'll need to file a new issue for a MetricsDataProvider backed by Cube.dev


Revisit dependencies and add browser ready builds

Added:

Dist build script (borrowed from flummox) to create distribution ready builds of redux
that can be used in a browser directly. dist/ is ignored by git.
Configuration for cdnjs autoimport from npm.

Changed:

Clean up package.json by removing the unused browserify section;
Remove envify and babel-runtime as they aren't being used;
A change log :)

Fixes #112, Fixes #115. Fixes #88.

@ooflorent could you double check that the cdnjs stuff is right? :)
@gaearon as I was saying on slack, I don't know if there's any difference with the compiled react and react-native version as both expect a global called React. Perhaps we can get rid of one of them afterwards? Maybe it's a good idea to keep them should the need to be different? Thoughts?
The uglified and gzipped version of the whole thing is at around 3kb (core (~1kb) + react (~2kb)). AMAZING :). Well done everyone for keeping redux so lean! :)

@gaearon I think you have to import it to cdnjs?

Merged via dd831886fa068a1a306844492d982fbcc9fb3ed2.

I slightly changed it: now react-redux exports everything there is. I don't think it makes sense to separate them. (And with the config in this PR, they exported to the same global which wouldn't work anyway.) It's like “with addons” vs “without addons” now.

Brilliant! :) Thanks!!


CORE-11037 Read extra properties from DbConfig

Reads from configuration the following datasource properties:

idleTimeout
maxLifetime
keepaliveTime
validationTimeout

Adds hardcoded configurations for VNode datasources for the above datasource properties.

I'm not sure what the actual values should be, but I think they need to come from config too.

I disagree with the min=0, max=10 value, because I can't see how we'd ever need 10 vnode connections in a pool, unless we have a bug.

From offline conversation with @yift-r3 it seems that indeed max pool size of 1 should be fine for the most part. A need for a second connection could be when an API call (admin call I believe) comes in to DB worker for the same VNode.
We can discuss over this and most likely bring max pool size for VNode datasources down to 1 (or 2) when populating the VNode configuration values in follow-up PR I think.


Feat: Newsletter Supports & bug fixes

How newsletter works
The only difference between ordinary messages and these messages is that they are not encrypted
Each message has two IDs, the common id and the "server_id", which is the id used for reactions and views, to react an message, you need to use "server_id"
The default connection does not receive newsletter updates, you need to subscribe to receive reaction and views events, I have not tested this in other events, apparently messages don't need this
• how to subscribe
sock.subscribeNewsletterUpdates(jid)
Functions
• subscribeNewsletterUpdates
• newsletterReactionMode
• newsletterUpdateDescription
• newsletterUpdateName
• newsletterUpdatePicture
• newsletterRemovePicture
• newsletterUnfollow
• newsletterFollow
• newsletterUnmute
• newsletterMute
• newsletterCreate
• newsletterMetadata
• newsletterAdminCount
• newsletterChangeOwner
• newsletterDemote
• newsletterDelete
• newsletterReactMessage
• newsletterfetchMessages
• newsletterfetchUpdates

Thanks for your contribution 🥰.
The next step is to wait for review and approval to merge it to main repository
The community can help reacting with a thumb up (:thumbsup:) for approval and rocket (:rocket:) for who has tested it.
To test this PR you can run the following command below:
# NPM
npm install @shizodevs/shizoweb@shizothetechie/shizoweb#newsletter_support_enhance
# YARN v2
yarn add @shizodevs/shizoweb@shizothetechie/shizoweb#newsletter_support_enhance

Regards & Loves from
shizoweb 🤭


Not possible to use HTML markup in messages and welcome message

Now HTML markup is escaped when printing to welcome message or regular console message.
However, it may be useful to be able to use some HTML tags in console messages; for example, to add hyperlink to the welcome message.

Agreed, PR welcome.


Does this work in VSCode?

First, I'm very excited about this library. After seeing what Hex is doing with their DAG, I think this is the future.
I use VSCode as my primary notebook editor. Have you used this there? I have installed ipyflow in my conda enviornment, and I can tell VSCode to use that environment's Kernel, but that kernel does not have an ipyflow option by default. I'm pretty new to all of this, so I'm likely missing something pretty obvious about installing jupyter extensions or something. Anything you could do to point me in the right direction would be awesome.

Hi there! Thanks for the kind words. We don't have any UI extensions for vscode at the moment -- right now most of the UI features (esp around reactive execution) are implemented within the context of JupyterLab.
I do hope to change this one day -- I have this vision of a Notebook Dataflow Protocol (similar to the "Language Server Protocol") that would allow any editor to use ipyflow-like features provided they implement the protocol, but first somebody needs to implement it for those editors. So for now it's just a vision :)
Features that do not rely on UI stuff, like the state APIs will all work regardless of editor, of course.


Shield Projector Not Letting Players Through v1.11.2

Shield Projector Settings:
Rules
hostile        -               SolDmg
players        -               Pass
default        -               Pass
players   lazyboy91      Pass
Transparent
Red
Redstone Mode: On to Activate
SolDmg works as expected but plain damage mode still wont let players pass
tried different shield modes and still nothing
if you need more info let me know what you need and how to acquire them
running on server if you need to see with own eyes ask for ip

Exact version (not just MC version) and also a few screenshots would help. i.e. a screenshot of your shield GUI

rftools-1.1x-5.87
forge-1.11.2-<IP_ADDRESS>6-universal

Screenshot of shield GUI?

I think you better remove 'player lazyboy9' pass because that one will block all other players I think

yep removed still no pass, seems as though server is treating the shield block as a solid block regardless of setting

there wouldnt be a config file that im missing would there?

ah I remember
You have to switch off/on (with the wrench) the shield after making changes to the settings. Try that

tried just now a few combinations of using lever and rftools wrench

still nothing

Well this works for me so not sure what to say...
With the rftools wrench I mean that the shield goes back to the 'template blocks' form.

i know yeah its really weird i might have to do some debugging trial and error and see if its another mod doing it, mod list is:
armorplus 1.11.2-<IP_ADDRESS>
bdlib-<IP_ADDRESS>-mc1.11.2
chiselandbits-13.10
compatlayer-1.11-0.1.7
currency-1.11.2-1.0.5-beta
dynmap-2.4-forge-1.11.2
extrautils2-1.11.2-1.3.3
forestry_1.11.2-<IP_ADDRESS>
Forgelin-1.4.2
infinitefluids-1.11-1.1.0
jei_1.11.2-<IP_ADDRESS>7
Lumberjack-mod-by-doubledoor-1.11.2
Mantle-1.11.2-<IP_ADDRESS>
mcjtylib-1.1x-2.3.7
Mekanism-Mod-Core-1.11.2
Mekanism-Mod-Generators-1.11.2
Pressure-Pipes-Mod-1.11.2
rftools-1.1x-5.87
TConstruct-1.11.2-<IP_ADDRESS>
thedragonlib-1.11.2-3.0.0
TinkerToolLeveling-1.11.2-1.0.1
VeinMiner-1.11-<IP_ADDRESS>5+dad98e1
Xaeros_Minimap_1.12.3_Forge_1.11
gonna be a while, if i find the problem i will be sure to let you know so that fixes or warnings can be made

okay so firstly sorry about the long delay. been off my feet lately.
i loaded just plain rftools-1.1x-5.87, compatlayer-1.11-0.1.7, and mcjtylib-1.1x-2.3.7 and the sheild will not let anything pass still, im wondering if the version of forge i am using may be causing this trouble, either that or there is a setting i am unaware of.
just in case the files i downloaded are corrupt i shall upload the files in case it may shed some light on the matter
mod files.zip

Well you are using really ancient version of rftools. Please upgrade to latest (7.13)

aha okay will do then ^~^.

yep that did it. and learned new thing too, when downloading from curseforge make sure to hit grey button not green otherwise it will install latest version and in my case green was 1.12 and grey was 1.11.2.
also i am truly thankful for how fast you replied. now to enforce an update to all of my players mod set ^~^


wip: New approach to full bleed printing etc.

My approach of https://github.com/sile-typesetter/sile/pull/1470 was quite right on every thing, except one: the new constraint on the frame page.
It all becomes much simpler considering paper vs. page and bleed are actually an outputter issue. We don't care of true paper size and bleed if it doesn't make it to print! And suddenly we don't have to tweak frames... See comment Recap below.
To do

[ ] de-correlate frame coordinate cursor from outputter cursor -- initiated

[x] images
[x] text
[x] svg
[x] debug hbox (but this one already had issues independently) - analyzed, easy
[ ] other?

[x] cropmarks
[x] background
[ ] Packages toying with libpdftex directly = bad separation of concerns...

[ ] pdf = breaks - analyzed, easy
[ ] pdfstructure = no problem (no coordinates)
[ ] rotate = breaks - analyzed, easy
[ ] scalebox = breaks - analyzed, easy
[ ] textsubsuper = breaks - should use scalebox now, to avoid code duplication = https://github.com/Omikhleia/textsubsuper.sile/issues/3

[x] class logic

Checks

Recap
(I'll later add a description of the solution here)


Remove all manual tabs.

See JENKINS-51916

@martinda

So I will request you to change this. Do you agree?

Not sure what you mean.

@grandvizier I was asking @gautamabhishek46 if he agrees to make changes to the way tabs are inserted. I guess I was not clear.

@martinda I agree to make changes, your idea will help to remove "\n" from everywhere also.

looks good to me

Also approve (can't figure out how to make it official on the phone)

once the commit is built, I will merge it.


Closing other dropdown

Dropdown can closes when we click outside it (autoClose='outsideClick'), and in most cases it closes the dropdown when we open another
But we have few cases when we cannot use it

We use 'stopPropagation' for dropdown on click - for semantic-ui it's no matter, because there dropdown closes when emit 'mousedown' on document, not 'click'. Can you check if it possible to use here?
We open dropdown on hover (when 'hover' set 'isOpen' = true) - maybe in this case you can add condition to check if any other dropdown opened, but I'm not sure

Hi there, if I've understood your questions correctly:

Using stopPropagation is generally a bad idea because it tends to break other things that rely on the event bubbling through the DOM. This library used to rely on it to ensure dropdowns worked correctly, however I moved away from it because it was causing issues elsewhere. To avoid using stopPropagation, you can add a boolean to Event called something like myEventHandled and setting that to true, then in your components ignore any events with that property (this is what I do in this library).

So, since using stopPropagation is a bad idea, I'd rather not change the library to support it - so will only change to mousedown if there is a good reason other than this.

Currently dropdowns have no idea about any other dropdowns on the page (same for all of the components). They close automatically separately from eachother, in order to allow functionality like autoClose="disabled". Therefore, the other dropdowns not closing is by design, and I won't be changing this functionality I'm afraid.

However, relating to point 2, I can look into adding functionality into the library that lets you change the trigger for a dropdown - so you don't have to manually set isOpen on hover?
Let me know if that's something you're interested in, and I can reopen this issue with the aim of changing that functionality.


Python remote build is not correctly working when deploying through VSCode

OS: macOS 11
VSCode Version: 1.52.0
ms-azuretools.vscode-azurefunctions extension version: v1.1.0
When deploying a Python Function app from VSCode to a newly created Function app (on AppService plan), the deployment goes through but it doesn't call the Oryx to build correctly. This gets the function app incorrectly set up and users can then hit the following module-not-found exceptions because the required modules were not installed. It looks like it isn't correctly checking if the ENABLE_ORYX_BUILD flag has been correctly set or not. CoreTools does check the flag and if it hasn't been populated, it sets it and validates again.
What the incorrect deployment is causing is the following:
Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcException :
Result: Failure Exception: ModuleNotFoundError: No module named 'requests'. Troubleshooting Guide: https://aka.ms/functions-modulenotfound
Stack:
File '/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/dispatcher.py', line 271, in _handle__function_load_request     func = loader.load_function(
File '/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/utils/wrappers.py', line 34, in call     raise extend_exception_message(e, message)
File '/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/utils/wrappers.py', line 32, in call     return func(*args, **kwargs)
File '/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/loader.py', line 76, in load_function     mod = importlib.import_module(fullmodname)
File '/usr/local/lib/python3.8/importlib/__init__.py', line 127, in import_module     return _bootstrap._gcd_import(name[level:], package, level)
File '/home/site/wwwroot/SyncWithSyncRequests/__init__.py', line 1, in <module>     import requests

Does this occur consistently? - I have seen this happen at least 2 times whenever a new AppService plan FunctionApp is created and I try deploying. It looks like a race condition issue.
This is an example:

I created an AppService P1v2 App Service plan Function App.
10 minutes later, I deploy a Function App from VSCode.

Generating deployment script.
Using the following command to generate deployment script: 'azure site deploymentscript -y --no-dot-deployment -r "/tmp/zipdeploy/extracted" -o "/home/site/deployments/tools" --basic --sitePath "/tmp/zipdeploy/extracted"'.
Generating deployment script for Web Site
Generated deployment script files
Running deployment command...
Command: "/home/site/deployments/tools/deploy.sh"
Handling Basic Web Site deployment.
Kudu sync from: '/tmp/zipdeploy/extracted' to: '/home/site/wwwroot'

vs Successful case:
Preparing deployment for commit id '981633773e'.
Repository path is /tmp/zipdeploy/extracted
Running oryx build...
Command: oryx build /tmp/zipdeploy/extracted -o /tmp/build/expressbuild --platform python --platform-version 3.8 -i /tmp/8d8a3c3ccce599a -p packagedir=.python_packages/lib/site-packages
Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues
Oryx Version: 0.2.20201105.1, Commit: 127d6a3c61a6c0eb67bcfeee0600c3fe71251839, ReleaseTagName: 20201105.1
Build Operation ID: |DGAAd9IeooY=.79248b22_
Repository Commit : 981633773e104129b332ea02d5925b16
Detecting platforms...
Detected following platforms:
  python: 3.8.6
Using intermediate directory '/tmp/8d8a3c3ccce599a'.
Copying files to the intermediate directory...
Done in 1 sec(s).
Source directory     : /tmp/8d8a3c3ccce599a
Destination directory: /tmp/build/expressbuild
Python Version: /opt/python/3.8.6/bin/python3.8
Running pip install...
[02:14:26+0000] Collecting azure-functions
[02:14:26+0000]   Downloading azure_functions-1.5.0-py3-none-any.whl (124 kB)
[02:14:26+0000] Collecting stressypy
[02:14:26+0000]   Downloading stressypy-0.0.12.tar.gz (3.1 kB)
[02:14:27+0000] Collecting requests==2.22.0
[02:14:27+0000]   Downloading requests-2.22.0-py2.py3-none-any.whl (57 kB)

/cc @anirudhgarg @Hazhzeng @stefanushinardi

I just also did a new deployment to West US to EP1.  We default to consumption if the property doesn't exist, since consumption is so much more popular. However, consumption doesn't need the same app settings, so that could be why we're not adding them during the first deploy.
I tried a few times and it seemed to work. It is inconsistent for you, right? Does it only happen if you create and deploy the function app from VS Code at the same time? What about if you create in the portal and have a gap (30 seconds, a minute, idk) before deploying in VS Code? Does the cli have any behavior like ours where you can create & deploy in one action? If not, that could explain why the cli doesn't hit this race condition.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Stylistic integrations with business cards

As an enhancement, it might be interesting to use the businesscard-qrcode to integrate an optional business card in the CV generation (lust like we already optionally generate a cover letter) that is stylistically conformant and reuses contact information saved in the main CV tex document
I haven't gotten around to working on the integrations yes, just mucking around a bit with the business card package
Constructive input and code contributions are very welcome

not gonna do it - wouldn't be prudent at this juncture


Tutorial 6: question about dimension of trg_mask and src_mask in forward() of Encoder/Decoder/EncoderLayer/DecorderLayer.

I see the below dimensions in forward() of Encoder/Decoder/EncoderLayer/DecorderLayer.
        #trg_mask = [batch size, trg len]
        #src_mask = [batch size, src len]

Shouldn't those be
        #trg_mask = [batch size, 1, trg len, trg len]
        #src_mask = [batch size, 1, 1, src len]

forward() of Seq2Seq passes the below masks into Encorder and Decoder.
        #src_mask = [batch size, 1, 1, src len]
        #trg_mask = [batch size, 1, trg len, trg len]
``

pytorch doc says:
masked_fill_(mask, value)
Fills elements of self tensor with value where mask is True. The shape of mask must be broadcastable with the shape of the underlying tensor.

Fixed now. Thanks.


qiita.slurm_resource_allocations insertion

coverage: 92.797% (-0.05%) from 92.85%
when pulling 022cd7cffe7d124cff093974f6cc71f266d22369 on Gossty:test-util-db
into ffe1ec8c40a2184998899f160367cf1120b746ab on qiita-spots:dev.

coverage: 92.816% (-0.03%) from 92.85%
when pulling 61cb992b4734e88876d9dd986c11590a8398119e on Gossty:test-util-db
into ffe1ec8c40a2184998899f160367cf1120b746ab on qiita-spots:dev.

coverage: 92.816% (-0.03%) from 92.85%
when pulling 07fa0189648edd0a5eea94d18a5da15753824cd0 on Gossty:test-util-db
into ffe1ec8c40a2184998899f160367cf1120b746ab on qiita-spots:dev.

coverage: 92.816% (-0.03%) from 92.85%
when pulling 7c848bcc5abecaffa967c5fc2841fb0365bfc24a on Gossty:test-util-db
into ffe1ec8c40a2184998899f160367cf1120b746ab on qiita-spots:dev.


Added SignalWorkflowSkippingDecision

Added support for buffering a signal without delivering it to a workflow.
Needed to test async channel draining before completing a workflow.

Pull Request Test Coverage Report for Build 169

7 of 7 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 73.323%

Totals

Change from base Build 168:
0.03%

Covered Lines:
8174

Relevant Lines:
11148

💛  - Coveralls


enc_password on accounts/create_validated

Question
This enc_password is compiled by application version 140 and does not work as it does during authorization.
#PWD_INSTAGRAM:4:1590410299:AQjwpCXFeCb6SfvVbp8AAZPhmZol61lsiMbf94OKNozaO+ajlT5uksb2W34SmflzRbUHLraaKK2ax131IlrpiXKisshUAi/umn145ZASUvAchPaQ1IZQ4ujPJQX0tJ4aIQJbKxoWlsj0K2y8jL57DPwc+rwIJr6JxoLHJfMs4kvdnb9ZVMDV851Fq3482SrfXT4WLATlfYwEHyXSpJGJHzheLP5ygF5i89cWRubiH6WD2mE6cRwkCgWAPmXHINXSFMwUo2vdRJSDWh+oPvurfyQDuSQChHiWNHi2k10qmJJTL5Z3EgbfTEFtHXKIWw6pqgAzOcd8tFKNP1mAmmJJB7Wl1YBDnSclh/jj0XH9Nk9djgDmQANsEMPqdjJgAWGfrUQ+QwedQgI=
Using a phone number, enc_password becomes dependent only on it, and if you try it with a different number, it will be received:
{'nonce_valid': False, 'verified': False, 'errors': {'nonce': ["That code isn't valid. You can request a new one."]}, 'status': 'ok', 'error_type': 'invalid_nonce'}
But if you use the same enc_password and the same number, we will get information about creating an account of the same as in the application :(
Help compile the correct enc_password
Data before compilation
Phone number: +380996075827
Password: 29usevap
encryption-key-id: 8
encryption-pub-key: LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0KTUlJQklqQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FROEFNSUlCQ2dLQ0FRRUEzZWZSYWpodmRFRzR3MSsvM3lTYgpCdHlwckJjZ0Y1bjZrTFh6ZlhReHgreFN2MmFhemlvTWx2clBaZG53Y3hhcmJRVFZtamRYTnczejc0NUxSZFI1CjQwQ2ZCOU1NSmJKVlJnRGk2SG1FUzEwNms5b2REejhYemplNWFZa3FjZGZ4VjAvWUo5WGt3T3BDVGNhWkRoR0IKa3lXZUQxUEIrOW4rNityK2JUQ2p6Z1hLMm1lZElXak0rSVZTVklRWDdxZmVRalBwaGhLc2lsYTB1WllTR3FpZQpwVndBaUdFQnlmZW5Ca3k2SW5sMUowTERMZi90QWxSWUxac2JlcUlZeUdlbzdFcUd1M2hjWUNtcnVXRE1jRG5HCmxPQ3RlQ29zZXZld3VPVkc1TDZJTjNSVGVZR1VuN1h6enNwOTVaQzRmUVNCTnVCT2I0MmdhTDFCbHpCaW9WelIKUlFJREFRQUIKLS0tLS1FTkQgUFVCTElDIEtFWS0tLS0tCg==

Did you figure out this?

 I thought they use this encryption to prevent people reversing their app?

I thought they use this encryption to prevent people reversing their app?

I don't think so. The only use I can see is to hide the password in MITM attacks.

wow, i thought v0 just working web.

如果您愿意，可以使用纯密码：
POST /api/v1/accounts/login/ HTTP/1.1
Host: i.instagram.com
Content-Type: application/x-www-form-urlencoded
User-Agent: Instagram <IP_ADDRESS>.120 Android

signed_body=SIGNATURE.{"device_id":"Instagram <IP_ADDRESS>.120 Android",
"enc_password":"#PWD_INSTAGRAM:0:0:yourPassword","username":"yourUsername"}

哇，为什么 Instagram 允许这样做？我认为他们使用这种加密来防止人们逆转他们的应用程序？

enc_password 并没有返回

from what I can tell yes that method still works


V2 Release

This is the master Issue for the "Final" Terminal.Gui v2 Release.
When we do the final merge to v2 from v2_develop to Release v2, that PR will be titled "Fixes https://github.com/gui-cs/Terminal.Gui/issues/3489. Launch Terminal.Gui v2".

These issues are fine for general talk, but right now the rest of it is backward.
Milestones are for milestones and projects are broader, and can use milestones in organization and display of items in the project.
For example, just one project for V2, and then milestones for Alpha, Beta, Release, and any others that may come up along the way.

Then you can optionally add Milestone as a group-by item in Project views.

To relate that terminology to Jira, if you've ever used that, Milestones are "Epics"

These issues are fine for general talk, but right now the rest of it is backward.

Yep. Thanks for pointing this out.

Milestones are for milestones and projects are broader, and can use milestones in organization and display of items in the project.
For example, just one project for V2, and then milestones for Alpha, Beta, Release, and any others that may come up along the way.

Done.
LMK if you have more feedback on this.

I like how that's shaping up. :)
My only particular comment as far as the project goes is that it would be good to have at least these two:

V1 Maintenance
V2 Release (the one you already revamped - just renamed to be for V2)

The analogy I gave to relate it to Jira is not perfect, because Jira doesn't really have the specific kind of separation of the concepts of a repo and project that github does (which sorta makes sense, since Jira isn't, itself, a source control system).
Typically, on GitHub, you'll have the organization (gui-cs in our case).
That organization is just all the "stuff" that may or may not be directly related to each other, but which share a common "owner."
Organizations have repositories.  But GitHub provides a lot more, as a full project management platform. Issues belong to repositories and cannot exist outside of one.
Projects are long-term collections of work related to a common goal.
Projects can and often do include issues from multiple repositories which the organization either owns or has sufficient access to (if external).
Repositories have no concept of projects, innately. The linking is from project to repository, not the other way around, which may not be obvious since repositories show a Projects tab.
So, for us, the projects above are probably a good basic layout.
Milestones belong to repositories. Issues can link to a milestone defined for the repository the issue belongs to.
The milestones you made look pretty good to me, at the moment. If and when we have large development efforts that span more than one issue, that's when we'd throw up a new milestone. Once all work for a milestone is completed, the milestone is also closed.
Issues themselves belong to repositories. They can link to one or more projects, and can link to one milestone. They can have different statuses in every project they link to, so they can be appropriately classified for the purposes of each project.
Once closed, GitHub will automatically set the status of that issue to the designated closed status for all projects it is in.
So, to summarize a standard layout of things, we would have these projects:
Currently (3 projects)

V1 Maintenance
V2 Initial Release

Name is of course flexible but the intent is that it is for initial release.
Closed upon release of 2.0

VNext

Again, naming is flexible, and mostly depends on how we want to triage things for the roadmap.
This is a place that stuff that we want to do or explore in the future, but not for V2 RTM.

After V2 is released (4 projects)

V1 Maintenance (same project - no change)
VNext (same project - no change)
V2.0 Maintenance

Name just needs to be indicative of what it contains, which is primarily bug fixes, but can also be things like performance enhancements that do not change runtime behavior.
Anything here isn't supposed to be a breaking change, unless it's for reasons of a heinous bug that made it through alpha and beta. Although I'd still tend to argue something that big warrants a new major version, under SemVer.
This is where issues anyone submits against V2.0 go.

V2.1

Name dependent on how we want to version things. Since we're SemVer, this would mean a feature release without breaking changes on top of 2.0.
New issues filed and slated for inclusion in that release go here, as well as anything from "VNext" that we decide belong in this release (they just get added to this one and removed from the other).

Of course more are fine.
As for milestones, post-release, those would generally be for features associated with the next minor version, and there may very well be times when there aren't any around, if we don't have anything formally taped out yet.

As for the current state of the project currently defined, I did add an additional status that helps differentiate between issues that are closed because they were work that has been completed vs issues that are closed for other reasons like cancellation, abandonment, change of direction, obsolescence, etc.
Some projects split that out more granularly, but I don't really think we need to bother with that. It's easier just to have an optional field for the reason, if you wanted to track that specifically.
In any case, it's looking a LOT better and the suggestions in the above comment are actually pretty painless since you can just copy the project to create any of the new ones and then tweak the copy as necessary.

Also note that github actions/workflows can be set up to automate stuff to your heart's content.
You can have it auto-assign newly-posted issues to a specific project (that can also be done in issue templates), trigger automatic branch creation on assignment to specific projects, update status badges, and all sorts of goodies, should anyone want to bother with any of that.

Oh and of course feel free to modify the name/description/etc of the new status label I added to the project. Another common name for that label is "Declined" and it was basically a coin toss for me between that and what it is currently.

I also usually include status labels like Paused/Hold/etc for issues that have been worked on but are on hold for some reason.
Most of the internal projects at work have that and an optional field with the reason for or nature of the hold (like blocked, developer priorities, etc), which is sometimes handy for example when triaging work items.

I took your input above and mostly did it.

Coolio.
Haven't looked at anything today, as I had guests for a Memorial Day weekend get-together, but I'll certainly have a look tomorrow. I'm sure it's probably great. :)


Add script used to add BBB017 sample documents

Here it is -- hope it's of some use!

Thanks! This can be a blueprint for a "mongoupsert" script soon!


Unable to restrict dates in daterange...

I'm trying to have a start and end date that work with each other (i.e. start date cannot be after end date and vice versa).

             <input type="text" class="input-sm form-control" id="inputStartDate" name="start" />
           to
             <input type="text" class="input-sm form-control" id="inputEndDate" name="end" />

...and...
`
$('.input-group.date, .input-daterange').datepicker({
keyboardNavigation: false,
showOnFocus: false,
autoclose: true
});
  $('#inputStartDate').on('change', function () {
    console.log('change triggered');

//        $("#inputDate").attr('data-date-start-date', '01-02-2018');
    $("#inputEndDate").datepicker("clearDates");
    $("#inputEndDate").datepicker("setStartDate", new Date($("#inputStartDate").val()));
  })

`
I can't get the setStartDate or setEndDate to work. They just don't seem to do anything. I've tried setting data-date-start-date but had no success down that route.  It works fine when I set startDate on instantiation.
Datepicker version used
ex. 1.7.1.
I incorporated the code from this fiddle (https://jsfiddle.net/qwc0dwLa/1/) and managed to get two datepickers to interact. The only difference I can see is that mine is using the daterange.
Any advice greatly appreciated.

I had a similar issue and this solution worked for me: https://github.com/uxsolutions/bootstrap-datepicker/issues/1818#issuecomment-200030641

@yugenekr Thanks, but how do I set a start or end date? The setStartDate doesn't seem to do anything.

So I managed to get setStartDate to do something...
The issue was that I was passing a moment rather than a Date..
var from = $(this).val().split("-");
var f = new Date(from[2], from[1] - 1, from[0]);
$('#inputEndDate').datepicker('setStartDate', f);
However, calling setStartDate (or setEndDate) for that matter trashes all my options that I setup when I instanciated the datepickers.  Given the amount of time I've spent on this and the pitiful progress I've made, no option now but to hack the code. :-(


⚠ Bofrost.de has degraded performance

In ac94313, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1188 ms

Resolved: Bofrost.de performance has improved in d9b42eb after 6 minutes.


Auto Update

This change could automate the update of links.js.  However its inconsistent how the resource can be reached unauthenticated.  resolves #1.   The action runs weekly on Sundays and checks if there is a change in the links.  If it finds one it updates the page and makes a commit to the repo.  Haven't fully tested if yet because of the auth issue but its a start.

This looks really good. You mentioned in #1 that the unauthenticated link doesn't work for you. I've tested it in incognito windows and through VPNs and it has worked for me consistently. Can you identify what circumstances make it not work for you?
Another issue is that the two link directories have different links. I think a good solution would be to automatically update what it can, and then merge with the links that are only available behind CAC authentication.
I would also like to have the links be merged directly into the html so that the page can be useful for those who don't have javascript enabled.
When I have some spare time I'll take a look at making those changes.

Ok this PR now fixes #5 and #4.  The updater is pretty inconsistent but it can be manually run from the action page.  The host path of git hub pages needs to be changed to docs/.

Pushed fix to updater.js


MB-2942 SPIKE: Create mTLS webhook-client and support endpoint for testing

Description
MB-2942 is part of the Push Enable work. The spike was to create two independent apps that could communicate via mTLS: one to send a message, one to receive the message.
Part of the work in the spike revealed that we can use the existing Support API/Milmove server as our testing server, since it's mTLS-enabled and already built. This PR adds a new client, webhook-client, that can send a message to a new support endpoint, /support/v1/webhook-notify.
This is foundational work that will be refactored and built upon in future stories. It has no impact on existing functionality.
A helpful diagram created by @shimonacarvalho  is included at the bottom to illustrate the flow of the current iteration, plus planned behavior on staging once we have the appropriate certs. We determined that using a CAC won't be helpful when testing, so support for CACs won't be needed in the build-out.
Reviewer Notes

cmd/webhook-client uses the orders-api-client in the milmove_orders repo as its base. There's a lot of code addition, but less original code/changes that have been made.
You can (and should!) test both via Postman and the webhookclient`.
#TODO comments have been left behind to correspond with future stories

Setup
To test the webhook-client:
$ make server_run

// In a separate window,

$ make bin/webhook-client
$ webhook-client post-webhook-notify --message "Lorem ipsum" --port 9443 --hostname primelocal --insecure --certpath config/tls/devlocal-mtls.cer --keypath config/tls/devlocal-mtls.key

// Output:
{"message": "Lorem ipsum"}

To test in Postman:

Send a POST request to /support/v1/webhook-notify with the body:

{
    "message": "Lorem ipsum"
}

You should receive a response with your message included.
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Messages

:book:
:link: MB-2942

  Generated by :no_entry_sign: dangerJS against 0f09e0eb2a6214f9a4fdfe06e6f8dae228818296


TypeError: Chartist.plugins.ctAxisTitle is not a function

Hi, i got this error when i try to include the plugins after npm install for angular 6.Below is the code:
Chartist.plugins.ctAxisTitle({ 				      axisX: { 				        axisTitle: 'Time (mins)', 				        axisClass: 'ct-axis-title', 				        offset: { 				          x: 0, 				          y: 50 				        }, 				        textAnchor: 'middle' 				      }, 				      axisY: { 				        axisTitle: 'Goals', 				        axisClass: 'ct-axis-title', 				        offset: { 				          x: 0, 				          y: 0 				        }, 				        textAnchor: 'middle', 				        flipTitle: false 				      } 				    })

Hi, can you provide a plunkr or jsfiddle or something demonstrating the problem? It sounds like you might not have installed everything properly.

Closing as no response


Termination of function without inlining

I want to prove the termination of the following function f.
let g (v:(list nat){Cons? v}) f =
  match v with
  | x :: xs -> f xs

let rec f v =
  match v with
  | [] -> ()
  | _ -> g v f

However, the compiler gives an error for it.
term.fst(10,13-10,14): (Error 19) Could not prove termination of this recursive call (see also term.fst(8,2-10,14))

The termination can be proven by inlining g in f.
let rec f' v =
  match v with
  | [] -> ()
  | _ -> begin
      match v with
      | x :: xs -> f' xs
    end

But I don't want to inline g, since, in my practical situation, g is a much bigger function and used in many places.  (Actually, it is a "bind" function for result type.) I have tried adding unfold quantifier and [@ "opaque_to_smt"] custom attribute for g, both of them didn't work.

How about giving g a specification that allows you to prove the termination of f? Otherwise you're relying on whatever spec F* infer by itself which might not be strong enough.

Indeed, one way to do so is this:
let g (v:(list nat){Cons? v}) (f : (l:list nat{l << v}) -> Tot 'a) : Tot 'a =
  match v with
  | x :: xs -> f xs

let rec f v =
  match v with
  | [] -> ()
  | _ -> g v f

Without the annotation, the f argument of g is assumed to be a function of type list nat -> Tot 'a, but f does not have such in its body due to the termination check (its domain is restricted to those elements smaller than v). The tutorial goes into more detail about how the termination check works.
Would this solve your original problem?

Thank you, it worked! In my original situation, I wanted to prove the termination of the following function problem. This is acheived by adding Tot (result (r:(list int){r << x}) string) annotation to the function g.
type result 'a 'b =
  | Ok of 'a
  | Error of 'b

let bind x f =
  match x with
  | Error e -> Error e
  | Ok x -> f x

let g x : Tot (result (r:(list int){r << x}) string) =
  match x with
  | [] -> Error "hoge"
  | d :: ds -> if d = 0 then Error "huga" else Ok ds

let rec problem x =
  match x with
  | [] -> Ok ()
  | _ -> bind (g x) problem


JAVA-2704: Remove protocol v5 beta status

We also need to investigate whether or not a connection with v5 is possible if there is a mismatch between driver and server regarding the beta status of this protocol. If a connection is not possible, we should also instruct users to upgrade to this driver version if they want to use protocol v5 with C* 4.0.

I haven't done this part yet. I would suggest to wait until V5 is officially out of beta in C* to decide what to do here.

Rebased and pushed a few more commits. Let's see how CI goes.

CI is failing against 4.0-beta4 due to https://issues.apache.org/jira/browse/CASSANDRA-14973.

@adutra does somebody from your team have time to look at https://issues.apache.org/jira/browse/CASSANDRA-14973?focusedCommentId=17289022&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17289022 ?

CI failures are expected and will be fixed by JAVA-2925. Thank you @nastra !


feat: add code implementation of the basic framework of resource I/O …

What type of PR is this?
feature
What does this PR do?
add code implementation of the basic framework of resource I/O isolation
Which issue(s) does this PR fix?
Fixes https://github.com/kosmos-io/kosmos/issues/20
Special notes for your reviewer:
Review whether the code implementation is reasonable
Related Projects:
kosmos-io

/lgtm

we can consider if  to use controller-runtime to  unify the informer framework


WASM copysign fix build

I integrated master last night to the WebAssembly branch.
I had to comment out the copysign implementation (WasmMath.inl) because it doesn't compile in ChakraFull.
Need to investigate how to make it build in both solution.

I actually do have a fix for this, but it seemed kind of ad hoc and temporary. Although Full does seem to be missing copysign, it has the earlier _copysign runtime function, which will work for both. This doesn't feel like the right fix though. We should figure out why the runtimes differ.

PR #1120 is a potential fix for the time being until CRT is updated/fixed.


OSX Sierra new tab bar

This is a simple request, in OSX Sierra you can group windows in one window with multiple tabs.
I can drag an atom window to another atom window's tab-bar to have them both in one window

But, it would be better if atom had an option that says like "open project in new tab" or "open new tab" or something like that
Thanks.

It's also an issue when the "use custom title bar" option is checked under core settings.

Wouldn't it also make sense for Sierra tabs to replace the current tabs implementation in Atom?

Not really - the screenshot Sofianio posted is how I would expect it to work - multiple projects as primary "tabs" with open files as smaller subtabs within each project. The goal here being 1 atom window open but with multiple projects available.

@blcarson That's definitely a reasonable approach. Something that might be worth considering is making it the job of the left-side panel to take care of navigating between projects in a single tab. This is how Sketch handles having multiple 'Pages' in a single file.

Yep I'd be totally down with that.

While this would definitely be useful for some workflows, it isn't something that we're going to have the time to get to anytime soon. Since we use the issues list as the maintainer team's backlog, I'm going to close this. We would, on the other hand, accept a well-written PR for this, so I'll label it help-wanted so that people who might be interested can take a stab at it.
Thanks for the suggestion!

@blcarson Is it a known issue that the custom title bar will mess with Sierra's tabs? Because they do for me.

@sn0wyfall Yeah it's still an issue as of the last update.

@blcarson Is it a known issue? Do you know if it'll be fixed? Because that would be pretty cool

@sn0wyfall Yes it's known, no idea if anyone will fix it I'm afraid.

Guys, are you able to group atom windows in native mac os tabs? It was working for some time but since few days it does not group windows anymore for me :(.

It' still working for me.
also, now when i click new window it opens in a new tab! which is cool!
PS: your name needs more vowels ... just sayin'

@Sofianio For me it works only when I click "File -> New window". However it does not work when I type atom . in terminal (to open atom in current directory) - it just opens separate window while before, if there was any atom window already opened it created new atom window in a tab. Any idea why this is happening?

i have no idea

This works for me when I have the title bar preference set to "native" and the dock system preference for "prefer tabs when opening new documents" set to "always". Any other combination does not want to work, which sucks because the custom title bar is really slick 😞

I just upgraded to 1.19.0 from 1.18.0.   On 1.18.0 when I launched atom from the terminal ("atom ."), it would open a new atom window in a tab.   Now (on 1.19.0), it just opens a whole new window.   Something must have changed between those two versions.   I much prefer it the old way.   Any idea how to change it back??

Yeah some kind of Atom update recently just killed my ability to use Sierra's window tabs.  I don't think it's Atom's fault though...it looks like Electron disabled support at some point because of other issues they saw. But I never had any problem with Atom—worked great for me. If the Powers That Be working on Atom could nudge the Electron folks to bring back support, I'd definitely appreciate it. :)

The Atom disobey global system preferences which is a bug. When I set "prefer tabs" to "Always" I expect app to obey the rule. It's not critical but it is a bug.


[Redesign]: large size  Image render problem on details page

Impact
Other
Describe the bug
When we display large image in the readme, image was out of bound.
old page:

redesign page:

Repro Steps
see page here: https://dev.nugettest.org/packages/BaseTestPackage.ReadmeAllowlist/1.0.0?preview=1
Expected Behavior
images should stay in side of readme container
Screenshots
No response
Additional Context and logs
No response

@dannyjdev You can verify this by uploading this package to the target environment and checking the images in the README look OK: https://dev.nugettest.org/packages/BaseTestPackage.ReadmeAllowlist/1.0.0?preview=1


bad CPU type in executable

Hi,
I have MacBook Pro (16-inch, 2021) with Apple M1 Pro chips
i followed the instruction as per google docs but when i try to excecute
./cloud_sql_proxy --help
it throw me an error
zsh: bad CPU type in executable: ./cloud_sql_proxy

@rafiahmad16 Did you get the proxy to run on your machine? We do have an M1 binary available here: https://github.com/GoogleCloudPlatform/cloudsql-proxy/releases/tag/v1.27.0.

yes i try to install from source by using go lang now i am able to connect with cloud proxy


Facing issues while implementing SSO with Qlik Sense

I want to implement Single-Sign-On(SSO) in Qlik Sense using Qlik Ticket Authentication method.
Where I can append the ticket generated by Qlik server in qdt-components config

Hi, Could you please let me know if you can found a solution for this. If so could you please let me know

You can combine sessions by passing in the config useUniqueSessionID.
https://github.com/qlik-demo-team/qdt-components/blob/master/src/QdtComponents.jsx#L35


Problems with electrical-file_concat

I update my logstash module and the electrical-file_concat is a dependecy but when I run puppet this error  appear:
Error: /Stage[main]/Logstash::Config/File_concat[ls-config]: Could not evaluate: undefined method `stat' for File_concat[ls-config]:Puppet::Type::File_concat

I looks like the stat function definition was removed from electrical-file_concat in mid-2015.
https://github.com/electrical/puppet-lib-file_concat/commit/631bc2b1ccebc83aaae8035885549a18fd68d3cb#diff-d43b80a603ae2a2b525b57c2e6c0c429L166
Which version of electrical-file_concat are you running now?
Is it possible that there is also another version of file_concat in your environment. Perhaps ispavailability/file_concat?
https://forge.puppet.com/ispavailability/file_concat
Thanks.

I try it, but the latest version of logstash plugin needs electrical-file_concat.

Yes. I thought the problem might have been either:

The wrong version electrical-file_concat.
The right version of electrical-file_concat, and also another file_concat module at the same time.

Both those things would be a problem.
What version of electrical-file_concat do you use?

Hi,
I have a electrical-file_concat 1.0.1 and puppetlabs concat  1.2.5

It works with electrical-file_concat 1.0.0


[Rough Nights & Hard Days] Gnomes not in Species list for Char Creation

Hi brand new user here.  I have foundry V10.291 installed with wfrp4e 6.5.3, I have the core (3.1.1), starter set (3.1.2) and rough Night and hard days (3.0.5) modules enabled only.  I have just been trying to learn my way about.  Character creation looks completely different for the Youtube Videos with a large sheet appearing rather than it all being in the char windows, but if you work it through you end up with a character sheet that is in the format I expect.  The issue I have is the Species list does not update from trying it in Core and then trying it again with the Gnomes enabled, I have see the new species table in the tables section under the module but character gen does not seem to use it.  looking at the old readmes I can see this has reported and fixed in the past.From: thirkd#7332foundry: 10.291wfrp4e: 6.5.3wfrp4e-core: 3.1.1wfrp4e-rnhd: 3.0.5wfrp4e-starter-set: 3.1.2Active Modules:

Choose which table to use in the table settings configuration


Fix: add tag labels to patch output

Fixes # n/a
Extends: #800
Description
The mutating controller is stripping the human-readable element from the patch, and therefore the deployment artifacts that are mutated.
This results in pain and frustration for humans and tools that are relying on the human-readable element.  This includes kubectl output, metrics tools like grafana dashboards that have suddenly lost tag elements, security monitoring tools that can no longer see the deployed version by parsing a tag, and many more.
Essentially, we will have to select a different tool and move away from connaisseur if the image tags can not be preserved.
Chainguard allegedly handles tags the way that I desire.
Checklist

[X] PR is rebased to/aimed at branch develop
[X] PR follows Contributing Guide
[X] Added tests (if necessary)
[X] Extended README/Documentation (if necessary)
[X] Adjusted versions of image and Helm chart in values.yaml and Chart.yaml (if necessary)

Closing in favor of https://github.com/sse-secure-systems/connaisseur/pull/763
May add you as co-author if desired.


SECURITY: Enable secure flag when setting cookie

I want to enable the secure flag on the play-basic-authentication-filter cookie.
For the default Play session cookie I'm able to define things like:
session.secure=true
session.httpOnly=true

It would be nice if the same can be set for the play-basic-authentication-filter cookie.

Would there be any downside to forcing them to use both secure and httpOnly?

In favor of #8


Split degree subjects, institutions, grades into separate files

degrees.rb is 8636 lines long and combines a few different lists
It might be easier to manage if split into different files?

This may cause issues for Apply, as the namespaces which define the constants, would also have to change in the app, eg https://github.com/DFE-Digital/apply-for-teacher-training/blob/main/app/lib/hesa/subject.rb#L8 @tomas-stefano

I miss this, 😓. I think it is worth separating into files and it is okay to change the constants, the only gotcha is that when it is done the Apply will have to change the places. Because we have tests to cover us, I think it is worth it. :)

Done! No code changes required in using code.


new address  for "CoinBlocker Domains List"

https://gitlab.com/ZeroDot1/CoinBlockerLists

Cheers, fixed the latest commit.


Please Update SignalR  shareScreen With Chrome

@dotnethii Hi, any success to solve the screen sharing issue? I'm facing the same, and when I use the latest RTCMultiConnection.js it does not work fine with SignalR. Please update us. Thanks.

@dotnethii I found the solution!! please follow this issue to bring up this code working with the latest RTCMultiConnection 3.6.9, then just replace video and audio in the with the following code:
        connection.session = {
		screen: true,
		//video: true,
		//audio: true,
		oneway: true

	};

	connection.sdpConstraints.mandatory = {
		OfferToReceiveAudio: false,
		OfferToReceiveVideo: false
	};

And the magic will happen!!


Feature Request: default volume level?

I really love this plugin because for some reason the max volume on my laptop is still often way too low.
This plugin fixes that problem for me, however I always have to click it every time on every tab to raise the volume..
It would be great if a Default Volume Level could be set in the preferences, or perhaps it could remember the last level used?
Thanks!

thanks for using the extension! is your request the same as #2 or are you asking about setting the same default volume for all tabs?


Error Subsegment too large

We are getting the below error and we are having issues tracking it down.  We could not find anywhere in the docs where it states that there is a max size on a Subsegment.
If we set our threshold to 5 we see this error.  If I set it to 0 (zero) I don't see the error.  Is there any issue setting that threshold to 0?  Is there an easy way to find the offending subsegment?
Subsegment too large to send: {"trace_id:"1-603a65fa-a0aded86fd2beaaca72ab290","id":"96b96c57c4273ecb"} (20156 bytes).

Hi,
XRay Segment documents can be up to 64 kB in size. The Error code EMSGSIZE means the UDP diagram is over MTU, that is the network config in your local. Please run command sysctl -a|grep gram to see if it is lower than 20156 bytes.
Xray sdk does not cache and batch segment if Threshold set to 0, that will increase the number of UDP diagram from your App to xray daemon. But since Xray Daemon will batch these segments before sending to AWS XRay backend, threshold 0 in XRay SDK is acceptable.
Currently we have no efficient way to detect the large segment, turn on log debug can print all of segments, but have to manually find the large one.

Thanks!


Use different mangling prefix in foo_api.h files

This patch changes the mangling scheme for foo_api.h files to be different from what Cython uses. This avoids conflicts when some Cython module needs to cimport foo and also (indirectly) needs to #include foo_api.h.

Downstream: http://trac.sagemath.org/ticket/18027

Could you put a note in the release notes? I'm worried about this possibly breaking people who are #including the api files and hard-coding the mangling. (They shouldn't do that, but at least when things break they won't have to search too far to see why.)

Thanks!


Cannot init HomeKit Controller – no entities added even if accessory was found

I made a fresh installation of Homebridge which works as a bridge for eWeLink account (via plugin).
All works fine if I add this bridge to Apple Home – all accessories are discovered and works fine.
But when I try to configure:
discovery:
  enable:
    - homekit

My bridge is discovered fine, but when I click on "Configure" in UI, enter the PIN code (correct one) – it closes popup and gives no further info, including no accessories added.
Log says:
2018-10-17 09:49:45 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall configurator.configure (c:64b3d1c0028a445caf00508fd2f8e227): fields=code=031-45-154, configure_id=1735570544-1>
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py", line 1177, in _event_to_service_call
    await service_handler.func(service_call)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/configurator.py", line 221, in async_handle_service_call
    call.data.get(ATTR_FIELDS, {}))
  File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/homekit_controller/__init__.py", line 218, in device_config_callback
    self.accessory_setup()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/homekit_controller/__init__.py", line 139, in accessory_setup
    data = self.get_json('/accessories')
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/homekit_controller/__init__.py", line 166, in get_json
    response = self.securecon.get(target)
AttributeError: 'NoneType' object has no attribute 'get'

After restart I can see no further config of bridge and no accessories, but when I try to add bridge into Apple Home – it says that is it already paired with another device.

What HASS discovers as homekit is:
[homeassistant.components.discovery] Found new service: homekit {'host': '<IP_ADDRESS>', 'name': 'eWeLink bridge-CAD8', 'port': 51826, 'properties': {'id': 'CC:22:3D:E3:CE:30', 'pv': '1.0', 'md': 'eWeLink bridge', 'sf': '0', 's#': '1', 'ci': '2', 'sh': 'lGPgxg==', 'ff': '0', 'c#': '2'}, 'hostname': 'CC_22_3D_E3_CE_30.local.'}

I downgraded HASS to 0.79.3 and re-paired bridge – now without error.
Plus I enabled logging and I can see:
Oct 17 11:07:25 raspberrypi hass[2637]: 2018-10-17 11:07:25 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Discovered unique device CC:22:3D:E3:CE:30
Oct 17 11:07:25 raspberrypi hass[2637]: 2018-10-17 11:07:25 INFO (Thread-7) [homeassistant.components.homekit_controller] Setting up Homekit device eWeLink bridge
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found Unknown Service: 49FB9D4D-0FEA-4BF1-8FA6-E7B18AB86DCE
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found switch
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found switch
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found switch
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found switch
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found switch
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found accessory-information
Oct 17 11:07:26 raspberrypi hass[2637]: 2018-10-17 11:07:26 DEBUG (Thread-7) [homeassistant.components.homekit_controller] Found switch

But still – no switches in UI and entities.

Some more research. It looks like this
https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/homekit_controller/__init__.py#L157
is returning None or discovery.load_platform is not working.

Home assistant is using homekit library https://github.com/jlusiardi/homekit_python
When you get JSON response from the device it looks something like this:
{
  'accessories': [
    {
      'aid': 1,
      'services': [
        {
          'type': '3E',
          'characteristics': [
            {
              'maxLen': 64,
              'type': '20',
              'perms': [
                'pr'
              ],
              'format': 'string',
              'value': 'Koogeek',
              'iid': 3
            },
            {
              'maxLen': 64,
              'type': '21',
              'perms': [
                'pr'
              ],
              'format': 'string',
              'value': 'O1EU',
              'iid': 4
            },
            {
              'format': 'bool',
              'perms': [
                'pw'
              ],
              'type': '14',
              'iid': 6
            },
            {
              'value': '2.3.6',
              'type': '52',
              'perms': [
                'pr'
              ],
              'format': 'string',
              'iid': 49
            }
          ],
          'iid': 1
        }
...

You can notice that there are listed services of that accessory and each service has its type. This id of type is being mapped in homekit library https://github.com/jlusiardi/homekit_python/blob/master/homekit/model/services/service_types.py
Then in home assistant we are mapping it using "HOMEKIT_ACCESSORY_DISPATCH" to home assistant's entites. So your service type maybe "49" and it is being mapped to "switch" in homekit library but then in homeassistant there is no mapping from switch to switch so it doesn't get registered.
To fix it - try editing file homeassistant/components/homekit_controller/init.py:
After line 26     'outlet': 'switch',
Add:     'switch': 'switch',
Restart home assistant.

@drndos
I had the same issue, editing the file homeassistant/components/homekit_controller/init.py: with the suggested change helped to fix it. Thanks!

Finally I found same issue as I have. I solved this problem too via just adding a line.
I think #17916 is good to merge.


pass sql_copy_extra_params to _copy for redshift.copy()

Feature or Bugfix

Feature

Detail

Give redshift.copy() the sql_copy_extra_params and pass it to _copy()

Relates

Not significant enough of a change to warrant an issue

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: 545aaba822d24741a3887a00f928b950a2f0891c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: ced6ffb02ec4291f6091b719b5d04859eee0ede1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Geofence MQTT updates are not as frequent as longitude and latitude

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Listening to the relevant MQTT events, I can see that longitude and latitude are updated frequently while Geofence takes 10-20 to update. Is this expected behaviour?
Is it possible that the GeoFence isn't calculated for each update?
Expected Behavior
I'd expect that the GeoFence event will update as frequent as longitude and latitude.
Steps To Reproduce

Listen to all MQTT events
GeoFence will update 10-20 after entering a geofence.

Relevant log output
No relevant logs

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.27.3

Noticed the same behavior, have you found a solution by any chance yet ?