Bricked L515 after 2 hours of usage

Required Info

Camera Model
L515

Firmware Version
can't open camera

Operating System & Version
Linux (Ubuntu 20.04, 22.04), Windows 10, Windows 11

Kernel Version (Linux Only)
multiple

Platform
PCs

SDK Version
2.50

Language
ROS, Realsense.FW.Update, Realsense.Viewer

Segment
others

Issue Description
After using the camera successfully for about 2 hours with ROS1 and RViz on Ubuntu 20.04, it stopped working. Since then we have tested it with another Ubuntu 20.04 ROS1 PC, Windows 11, Windows 10 and finally with Ubuntu 22.04 and ROS2. Nothing worked anymore. What does work though is the camera image with VLC as a Video4Linux device.
With Ubuntu 20.04 and ROS1 noetic we used the packages provided by ROS. With Windows we used the precompiled executables for SDK 2.50.
On Windows with RealSenseView no camera can be found, Realsense.FW.Update finds the camera but crashes:
PS C:\Users\sr4l\Downloads\Realsense L515>
PS C:\Users\sr4l\Downloads\Realsense L515> & '.\Intel.RealSense.FW.Update.exe' --version

C:\Users\sr4l\Downloads\Realsense L515\Intel.RealSense.FW.Update.exe  version: 2.50.0

PS C:\Users\sr4l\Downloads\Realsense L515> & '.\Intel.RealSense.FW.Update.exe'

Nothing to do, run again with -h for help

Connected devices:
 17/06 10:19:18,648 ERROR [17616] (l500-device.cpp:136) Failed to set units age
RealSense error calling rs2_create_device(info_list:000001DBED8250E0, index:0):
    hr returned: HResult 0x8007001f: "Ein an das System angeschlossenes Ger├ñt funktioniert nicht."
PS C:\Users\sr4l\Downloads\Realsense L515>

On Linux Ubuntu 20.04 dmesg output after connecting the device:
mrt@mrt-pc131:~$ dmesg
[  273.750390] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[  273.771280] usb 2-1: New USB device found, idVendor=8086, idProduct=0b64, bcdDevice=10.58
[  273.771300] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  273.771309] usb 2-1: Product: Intel(R) RealSense(TM) 515
[  273.771316] usb 2-1: Manufacturer: Intel(R) RealSense(TM) Camera
[  273.771322] usb 2-1: SerialNumber: FFFFFFFFFFFFFFFF
[  273.776334] usb 2-1: Found UVC 1.50 device Intel(R) RealSense(TM) 515 (8086:0b64)
[  273.777476] uvcvideo 2-1:1.1: Failed to set UVC probe control : -32 (exp. 48).
[  273.779192] uvcvideo 2-1:1.2: Failed to set UVC probe control : -32 (exp. 48).
[  273.780482] uvcvideo 2-1:1.3: Failed to set UVC probe control : -32 (exp. 48).
[  273.780822] input: Intel(R) RealSense(TM) 515: Int as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/input/input34
[  273.781418] usb 2-1: Found UVC 1.50 device Intel(R) RealSense(TM) 515 (8086:0b64)
[  273.784319] hid-generic 0003:8086:0B64.0002: hiddev2,hidraw1: USB HID v1.10 Device [Intel(R) RealSense(TM) Camera Intel(R) RealSense(TM) 515] on usb-0000:00:14.0-1/input7
[  273.986117] hid-sensor-hub 0003:8086:0B64.0002: No report with id 0xffffffff found

On Linux Ubuntu 20.04 ROS1 noetic output after roslaunch, see attached file roslaunch_output.txt.
Summery: We bought the camera, tested it, it worked, it stopped working after 2 hours of use on about 3 different days. We DIDN'T try a firmware update or anything like that, we just use the ROS1 Noetic supplied packages for Intel Realsense. We also used 2 different USB-C cables that work with an OAK-D pro for example.
I think the SerialNumber in dmesg is strange, but I do not know the output from the working state. Also, we have not done anything that should change the serial number, if that is even possible.
Any and all help is appreciated.

Hi @Sr4l  There are two previous cases of the ffffffffffffffff serial number on L515 at https://github.com/IntelRealSense/librealsense/issues/7302 and https://github.com/IntelRealSense/librealsense/issues/7311
This is a hardware issue and will not be fixable.  Please do an RMA return of your camera to the retailer that you purchased it from.  Guidance about doing so can be found at the link below.
https://support.intelrealsense.com/hc/en-us/articles/360051623953-How-to-return-a-faulty-Intel-RealSense-Camera

I am sad to hear that. Thank you for the info.


v1.10 clustermesh followups

We had a discussion with a user on Slack trying out the latest (v1.10-style) clustermesh documentation last week, and these followup items were raised which we should consider addressing before the final release:

[ ] Possible certificate issue for clustermesh where the agents in the same cluster as the local clustermesh etcd can't connect. I'm not sure if we even intend for this connectivity to occur, why would the local cluster need to connect to the local clustermesh etcd?
[x] Network policy across clusters requires --identity-allocation-mode=kvstore to pull the remote identities from remote kvstores. We seem to have just dropped that instruction from the new v1.10 instructions so it's just broken right now.

cc @jrajahalme @tgraf
I think on the first topic, we would expect to only expect someone to access that local clustermesh etcd if they were at a scale whereby distribution via k8s watchers wasn't sufficient and therefore etcd would perform these updates. As tgraf explained it instead of "apiserver -> agents, we would have apiserver -> clustermesh-apiserver -> agents". Do we want to document how you can leverage this if you need to run at this scale ?
On the second point, the docs for external-workloads specifically state that we should use identity-allocation-mode=crd. For v1.9 we explicitly state that kvstore is the preferred store, but in the latest cilium-cli we use crd mode like external-workloads. Is there an expectation that crd should work for cross cluster policy?

Do we want to document how you can leverage this if you need to run at this scale ?

If we have a legitimate reason for this point, I think my main remaining question is whether the Cilium CLI is properly configuring the certificates for access to the local cluster. I didn't try this myself, but a community user on Slack just mentioned that they were getting complaints from etcd. Maybe this is just a matter of doing a minor enhancement to the CLI. Alternatively sure if there's some manual step that the user needs to run, then I'm fine with documenting that but I don't really understand what that will look like.

On the second point, the docs for external-workloads specifically state that we should use identity-allocation-mode=crd. For v1.9 we explicitly state that kvstore is the preferred store, but in the latest cilium-cli we use crd mode like external-workloads. Is there an expectation that crd should work for cross cluster policy?

From my perspective, I think it's OK for the local agent to use CRD for allocating identities etc. However, for remote clusters, we must connect to remote etcds as provisioned by the clustermesh-apiserver feature, and then monitor those etcds for identity updates. My understanding is that today, Cilium-agent configures both of these aspects via only one flag, the identity-allocation-mode. As a consequence, this means that if you don't configure it to etcd then Cilium-agent won't monitor remote clusters for their identities so it can't make policy determinations for the remote identities. We can of course double-check whether this assertion is correct, and if so maybe the answer is to adjust the way that the remote cluster identity monitoring works to ensure that it picks up the remote identities regardless of the identity-allocation-mode setting.

Do we want to document how you can leverage this if you need to run at this scale ?

If we have a legitimate reason for this point, I think my main remaining question is whether the Cilium CLI is properly configuring the certificates for access to the local cluster. I didn't try this myself, but a community user on Slack just mentioned that they were getting complaints from etcd. Maybe this is just a matter of doing a minor enhancement to the CLI. Alternatively sure if there's some manual step that the user needs to run, then I'm fine with documenting that but I don't really understand what that will look like.

On the second point, the docs for external-workloads specifically state that we should use identity-allocation-mode=crd. For v1.9 we explicitly state that kvstore is the preferred store, but in the latest cilium-cli we use crd mode like external-workloads. Is there an expectation that crd should work for cross cluster policy?

From my perspective, I think it's OK for the local agent to use CRD for allocating identities etc. However, for remote clusters, we must connect to remote etcds as provisioned by the clustermesh-apiserver feature, and then monitor those etcds for identity updates. My understanding is that today, Cilium-agent configures both of these aspects via only one flag, the identity-allocation-mode. As a consequence, this means that if you don't configure it to etcd then Cilium-agent won't monitor remote clusters for their identities so it can't make policy determinations for the remote identities. We can of course double-check whether this assertion is correct, and if so maybe the answer is to adjust the way that the remote cluster identity monitoring works to ensure that it picks up the remote identities regardless of the identity-allocation-mode setting.

local agent is also the remote cluster. If local agent is using crd, how does another remote cluster monitor the local agent's identities?  I think the document needs to notify user to set kvstore: etcd, because if we don't explicitly state the kvstore, identity-allocation-mode will force to set to crd
https://github.com/cilium/cilium/blob/31625355bec914998bbf372a0519a87a4a8e1c3f/pkg/option/config.go#L2647-L2651
Further, do we consider that remove entirely kvstore from clustermesh?  is that possible?

local agent is also the remote cluster. If local agent is using crd, how does another remote cluster monitor the local agent's identities? I think the document needs to notify user to set kvstore: etcd, because if we don't explicitly state the kvstore, identity-allocation-mode will force to set to crd

This is the beauty of clustermesh-apiserver: It automatically deploys an etcd instance in the cluster and mirrors the local CRD content into this etcd. Then the remote clusters can be configured to connect to the etcd instance to pull the local cluster's information instead, and we don't have to expose the local cluster's apiserver to other clusters or handle apiserver RBAC configuration for each cluster etc.

Further, do we consider that removing entirely kvstore from clustermesh? is that possible?

I don't know if anyone has thought all the way through the implications yet.

I just tested clustermesh with two Kind clusters via cilium-cli, which defaults installs to Cilium 1.9.5, CRD allocation mode, and kvstore="". Identity propagation between clusters works fine:
vagrant@runtime:~/go/src/github.com/cilium/cilium-cli$ kubectl --context=$CLUSTER2 logs cilium-94tvw -n kube-system | grep -i -e allocation-mode -e clustermesh -e kvstore
level=info msg="  --clustermesh-config='/var/lib/cilium/clustermesh/'" subsys=daemon
level=info msg="  --identity-allocation-mode='crd'" subsys=daemon
level=info msg="  --kvstore=''" subsys=daemon
level=info msg="  --kvstore-connectivity-timeout='2m0s'" subsys=daemon
level=info msg="  --kvstore-lease-ttl='15m0s'" subsys=daemon
level=info msg="  --kvstore-opt='map[]'" subsys=daemon
level=info msg="  --kvstore-periodic-sync='5m0s'" subsys=daemon
level=info msg="Skipping kvstore configuration" subsys=daemon
level=info msg="Initializing ClusterMesh routing" path=/var/lib/cilium/clustermesh/ subsys=daemon
level=info msg="New remote cluster configuration" clusterName=cluster1 config=/var/lib/cilium/clustermesh/cluster1 kvstoreErr="<nil>" kvstoreStatus= subsys=clustermesh
level=info msg="Connecting to etcd server..." config=/var/lib/cilium/clustermesh/cluster1 endpoints="[https://cluster1.mesh.cilium.io:30567]" subsys=kvstore
level=info msg="Got lease ID 7c0279144db5582c" subsys=kvstore
level=info msg="Got lock lease ID 7c0279144db5582e" subsys=kvstore
level=info msg="Initial etcd session established" config=/var/lib/cilium/clustermesh/cluster1 endpoints="[https://cluster1.mesh.cilium.io:30567]" subsys=kvstore
level=info msg="Successfully verified version of etcd endpoint" config=/var/lib/cilium/clustermesh/cluster1 endpoints="[https://cluster1.mesh.cilium.io:30567]" etcdEndpoint="https://cluster1.mesh.cilium.io:30567" subsys=kvstore version=3.4.13
level=info msg="Connection to remote cluster established" clusterName=cluster1 config=/var/lib/cilium/clustermesh/cluster1 kvstoreErr="<nil>" kvstoreStatus= subsys=clustermesh
level=info msg="Established connection to remote etcd" clusterName=cluster1 config=/var/lib/cilium/clustermesh/cluster1 kvstoreErr="<nil>" kvstoreStatus="Waiting for initial connection to be established" subsys=clustermesh
level=info msg="New endpoint" containerID=591a8d0e85 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=5 identity=133975 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/clustermesh-apiserver-957767d9b-swwk2 subsys=endpoint
level=info msg="Reserved new local key" key="k8s:io.cilium.k8s.policy.cluster=cluster2;k8s:io.cilium.k8s.policy.serviceaccount=clustermesh-apiserver;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=clustermesh-apiserver;" subsys=allocator
level=info msg="Reusing existing global key" key="k8s:io.cilium.k8s.policy.cluster=cluster2;k8s:io.cilium.k8s.policy.serviceaccount=clustermesh-apiserver;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=clustermesh-apiserver;" subsys=allocator
level=info msg="Rewrote endpoint BPF program" containerID=591a8d0e85 datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=5 identity=133975 ipv4=<IP_ADDRESS> ipv6= k8sPodName=kube-system/clustermesh-apiserver-957767d9b-swwk2 subsys=endpoint

vagrant@runtime:~/go/src/github.com/cilium/cilium-cli$ kubectl --context=$CLUSTER2 exec cilium-94tvw -n kube-system -it -- cilium identity list
Defaulted container "cilium-agent" out of: cilium-agent, ebpf-mount (init), clean-cilium-state (init)
ID       LABELS
1        reserved:host
2        reserved:world
3        reserved:unmanaged
4        reserved:health
5        reserved:init
6        reserved:remote-node
70045    k8s:io.cilium.k8s.policy.cluster=cluster1
         k8s:io.cilium.k8s.policy.serviceaccount=coredns
         k8s:io.kubernetes.pod.namespace=kube-system
         k8s:k8s-app=kube-dns
71841    k8s:app=local-path-provisioner
         k8s:io.cilium.k8s.policy.cluster=cluster1
         k8s:io.cilium.k8s.policy.serviceaccount=local-path-provisioner-service-account
         k8s:io.kubernetes.pod.namespace=local-path-storage
129471   k8s:io.cilium.k8s.policy.cluster=cluster1
         k8s:io.cilium.k8s.policy.serviceaccount=clustermesh-apiserver
         k8s:io.kubernetes.pod.namespace=kube-system
         k8s:k8s-app=clustermesh-apiserver
131452   k8s:app=local-path-provisioner
         k8s:io.cilium.k8s.policy.cluster=cluster2
         k8s:io.cilium.k8s.policy.serviceaccount=local-path-provisioner-service-account
         k8s:io.kubernetes.pod.namespace=local-path-storage
133975   k8s:io.cilium.k8s.policy.cluster=cluster2
         k8s:io.cilium.k8s.policy.serviceaccount=clustermesh-apiserver
         k8s:io.kubernetes.pod.namespace=kube-system
         k8s:k8s-app=clustermesh-apiserver
145676   k8s:io.cilium.k8s.policy.cluster=cluster2
         k8s:io.cilium.k8s.policy.serviceaccount=coredns
         k8s:io.kubernetes.pod.namespace=kube-system
         k8s:k8s-app=kube-dns

There should be no reason for a node to connect to the local clustermesh-apiserver. If kvstore is wanted for cluster's identity allocation, the local kvstore should be configured independently of clustermesh. That is, the etcd instance within clustermesh-apiserver is not to be used for cluster's local identity allocation, but only for cross-cluster identity propagation.

From my perspective, I think it's OK for the local agent to use CRD for allocating identities etc. However, for remote clusters, we must connect to remote etcds as provisioned by the clustermesh-apiserver feature, and then monitor those etcds for identity updates. My understanding is that today, Cilium-agent configures both of these aspects via only one flag, the identity-allocation-mode. As a consequence, this means that if you don't configure it to etcd then Cilium-agent won't monitor remote clusters for their identities so it can't make policy determinations for the remote identities. We can of course double-check whether this assertion is correct, and if so maybe the answer is to adjust the way that the remote cluster identity monitoring works to ensure that it picks up the remote identities regardless of the identity-allocation-mode setting.

The test output above shows that this is already done as required at least when identity-allocation-mode = crd.

Thanks for trying it out @jrajahalme , sounds like our answer to the second item in the description is "cannot reproduce". I've checked that box.
For the first item in the description of the issue, we need to decide whether to:
a) Document that etcd will always complain like that with the current release
b) Update cilium-cli to avoid configuring Cilium to connect to the local etcd
c) Update cilium-cli to properly configure the secrets to allow connecting to the local etcd.
It sounds like (c) may be a bigger job that is not worth doing in the v1.10 timeline, so that would leave options (a) or (b). (b) would be my preference but I don't know how complicated it would be to change the way that these settings are configured.

b) Update cilium-cli to avoid configuring Cilium to connect to the local etcd

What does "local etcd" here mean? etcd managed by cilium-etcd-operator or the etcd pod deployed with clustermesh-apiserver? Or something else?

I'll admit I'm a little out of my depth here since I'm not reproducing or observing the errors, but what I hear is that if you configure encryption using the cilium cluster CLI you will see errors like the below in the etcd logs, likely due to a misconfigured cilium-agent:
2021-04-15 04:48:39.013053 I | embed: rejected connection from "<IP_ADDRESS>:42468" (error "EOF", ServerName "")
2021-04-15 04:48:39.014336 I | embed: rejected connection from "<IP_ADDRESS>:40140" (error "EOF", ServerName "")
2021-04-15 04:48:39.034042 I | embed: rejected connection from "<IP_ADDRESS>:15002" (error "tls: first record does not look like a TLS handshake", ServerName "")
2021-04-15 04:48:39.233785 I | embed: rejected connection from "<IP_ADDRESS>:15008" (error "tls: first record does not look like a TLS handshake", ServerName "")
2021-04-15 04:48:39.560465 I | embed: rejected connection from "<IP_ADDRESS>:39610" (error "EOF", ServerName "")
2021-04-15 04:48:39.561120 I | embed: rejected connection from "<IP_ADDRESS>:34945" (error "EOF", ServerName "")

It seems like these are not "real" problems that inhibit connectivity, but noise in the cluster that may make it more difficult to debug the real errors since they suggest there's a problem when there doesn't seem to be a problem. So my suggestion is to investigate and quieten these errors by whatever mechanism we think makes sense.
The corresponding Slack thread is here:
https://cilium.slack.com/archives/C53TG4J4R/p1618461366253900

Couldn't reproduce the issue with errors in the etcds. If you have more information about this, please post in below and we can reopen the issue.

Further, do we consider that removing entirely kvstore from clustermesh? is that possible?

I don't know if anyone has thought all the way through the implications yet.

@joestringer hi, I read and deployed clustermesh(v1.9.6) with multiple clusters, and I found the following points:
ClusterMesh's ETCD only stores the local cluster's resources like "cilium/state/nodes/v1, cilium/state/services/v1, cilium/state/ip/v1", and other clusters' resources is merged in the memory like IPCache/globalServiceCache. So we're not necessary to require ETCD storage if we implement it, but we may modify some structures and interfaces, is that acceptable?


[nrf fromlist]: Nrf wifi mgmt

This is based on pending https://github.com/nrfconnect/sdk-zephyr/pull/871 (will rebase once this is merged) and is a downstream PR of https://github.com/zephyrproject-rtos/zephyr/pull/49049

As Upstream it taking time, for now  I have marked these as nrf noup  sauce tag for CI, once upstream is merged, will change the tag.

As Upstream it taking time, for now I have marked these as nrf noup sauce tag for CI, once upstream is merged, will change the tag.

Feeling a bit confident, as its reviewed to some extent, so, added nrf fromtree we can revisit this before merge.

https://github.com/nrfconnect/sdk-nrf/pull/8540

Looks pretty good already, I've left a minor review in the upstream counterpart.
I wonder if we could incorporate commit from #895 and drop 4981c03 already, so that we have less PRs open (less CI runs and it'll be easier to merge).
Done, remove duplicate commit, merged that in to this PR and closed that PR.

And as for others, we need a sdk-nrf manifest update for this PR as well.

Already linked https://github.com/nrfconnect/sdk-nrf/pull/8540 (there is a separate commit for manifest)


Enable contenteditable for goog.editor.SeamlessField in firefox

It seems these 2 bugs, mentioned here, are now fixed in FF:
/**
 * @define {boolean} Use contentEditable in FF.
 * There are a number of known bugs when the only content in your field is
 * inline (e.g. just text, no block elements):
 * -indent is a noop and then DOMSubtreeModified events stop firing until
 *    the structure of the DOM is changed (e.g. make something bold).
 * -inserting lists inserts just a NBSP, no list!
 * Once those two are fixed, we should have one client guinea pig it and put
 * it through a QA run. If we can file the bugs with Mozilla, there's a chance
 * they'll fix them for a dot release of Firefox 3.
 */
goog.define('goog.editor.defines.USE_CONTENTEDITABLE_IN_FIREFOX_3', false);

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


Fixed typos

Description
Fixed some typos in the source code. Note that I also touched some files in macos folders. I understand that that may be off limits. I could revert those changes.

@lzandman in this specific case macOS submission is ok, thanks for getting all these fixed!


Add support for time_box time domain items

These are needed to be able to represent discretized time, like how it is done in PCRaster. A time_box is similar to a space_box. Along the 1D time dimension, we need two bounding coordinates.

Depends on #29


Error ELIFECYCLE

When trying to run this on a mac, I get:
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "run" "webpack"
npm ERR! node v7.4.0
npm ERR! npm  v4.1.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>webpack: `cross-env NODE_ENV=development webpack --progress --hide-modules`
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>webpack script 'cross-env NODE_ENV=development webpack --progress --hide-modules'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the 2017.sucks package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=development webpack --progress --hide-modules
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs 2017.sucks
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls 2017.sucks
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/alex/Development/2017.sucks/npm-debug.log

log file:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/7.4.0/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'webpack' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prewebpack', 'webpack', 'postwebpack' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prewebpack, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/alex/Development/2017.sucks/node_modules/.bin:/Users/alex/.cargo/bin:/Users/alex/Development/spark-installer:/Users/alex/.composer/vendor/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/alex/.yarn/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/alex/Development/2017.sucks
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',
11 silly lifecycle   'cross-env NODE_ENV=development webpack --progress --hide-modules' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 255  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec webpack script
14 verbose stack Error<EMAIL_ADDRESS>webpack: `cross-env NODE_ENV=development webpack --progress --hide-modules`
14 verbose stack Exit status 255
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:885:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /Users/alex/Development/2017.sucks
17 error Darwin 16.3.0
18 error argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "run" "webpack"
19 error node v7.4.0
20 error npm  v4.1.1
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>webpack: `cross-env NODE_ENV=development webpack --progress --hide-modules`
22 error Exit status 255
23 error Failed at the<EMAIL_ADDRESS>webpack script 'cross-env NODE_ENV=development webpack --progress --hide-modules'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the 2017.sucks package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     cross-env NODE_ENV=development webpack --progress --hide-modules
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs 2017.sucks
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls 2017.sucks
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Reproduction:
laravel-mix-test.zip

The issue appears to be the lack of the config file. I copied directly from: https://github.com/JeffreyWay/laravel-mix/blob/master/docs/installation.md
Might be worth including it in here.

The instructions tell you to copy the webpack.config.js file to your project root. So it's not necessary to specify the full config path in that case.


feat(add angular)

closes #38
Add export template for Angular Material theming based off of the CSS var exports (similar to the Web CSS option).
Thanks @rodydavis!

Hi @twerske,
I was giving a try to the template (I'm using @angular/material 16.0.1) and I think I found 2 issues (if not mistaken) :

you can remove line 413, mat-core does not allow any parameters on v15 and so it's throwing an error. Maybe it is worth adding @include mat.typography-hierarchy($core-theme) instead ?

I have another issue with the define-typography-config: I had first to add the mat prefix to the define-typography-level but got another compile error to finally find out that the correct list should be the following (found @angular\material\core\typography_all-typography.scss) :

$font-family
$headline-1
$headline-2
$headline-3
$headline-4
$headline-5
$headline-6
$subtitle-1
$subtitle-2
$body-1
$body-2
$caption
$button
$overline
Really not sure of myself but wanted to let you know.
Would be cool also if the theme could be generated also via @material/material-color-utilities

Hello any update on this? The issue #38 was closed but the PR was never merge.


feat(choices): add null option support

Needed this feature so decided to implement it. I toyed with a few different solutions and boiled it down to this (doesn't look like much, but it took me quite a while to get to this).
This solution requires that the "null" option is a typical item present in the array so that we have flexibility in filtering and displaying it without having to write a bunch of conditional statements. We then use the "null-option" directive on the "ui-select-choices" element to mark our null option. When the option is selected, the model is set to null (and vice versa).
An additional helper option is included - "loose-null" - which tells ui-select to treat undefined and null as the same. In this case, if the model value is undefined, the null option will still be displayed. Just add
"loose-null" on the "ui-select-choices" element.
See http://plnkr.co/edit/7nmBRicsmH33E55sSomz?p=preview.
Happy to discuss implementation specifics, thought I'd open this PR to get the ball rolling. Yet to write unit tests... Could anyone help with this?

Mm, may not have been as relevant to #302 as I thought after having another read. May take another look at this at some point. If we want to include the null-option in the filtering things might be tough since the filtering happens outside of ui-select itself.

If nullOption is used, then placeholder won't work or when will it be shown?

The placeholder would be shown if "loose-null" isn't used and the value is undefined. I agree that this relationship between placeholder/null-option should probably be thought about further.

Gonna close this for now to make sure it's not accidentally merged before it's ready. A discussion is still on going in #302 on this


Handle .html vs no .html

Current link to articles in content, especially in promotions, featured / recommended articles contains .html. But requesting an article with a .html returns a 404.
While there is some thing that needs to happen globally, while we import the content, we can certainly remove the .html.
Also, we could add client side logic to remove it.

@stefan-guggisberg will you be able to take care of this ?

@kptdobe as mentioned above, the redirect should be generic rather than per URL.

@stefan-guggisberg will you be able to take care of this ?

@kptdobe yes, I can configure a generic /*.html -> /* redirect. when should the generic redirect be active?

Related: we'll need to resubmit a sitemap with the new extensionless canonicals...

Who's in charge for this?

I can configure a generic /.html -> / redirect. when should the generic redirect be active?
I assume that as soon as we go-live, there will be tons of requests coming-in with the extension. I think it should be there when we change the backend url to adobe/blog.

Related: we'll need to resubmit a sitemap with the new extensionless canonicals...
Who's in charge for this?
I have created https://github.com/adobe/blog/issues/52 to track this.

I have prepared a generic /x.html -> /x redirect in draft version 146, together with other changes for the hlx3 switch.

Brilliantly handled by @stefan-guggisberg. Closing now.


When displays are (un)plugged under Windows, parts of the terminal might become invisible

Which operating system does the issue occur on?
Windows 10 1809
Went from from dock to laptop screen to (crappy, slow) StarLink USB2.0 external graphics card, and afterwards I noticed that the top my vim and bash were hidden out of sight behind and below the window titlebar and buttons.
Basically the OpenGL buffer was displayed offset, so the top was not visible inside the window (or anywhere for that matter).

This happens when you change your display DPI also, though I admit, this might be a less common scenario.


Fixed tools/build_release.py to allow ports to be moved easily between repos.

Not yet, gotta check to see if i fixed it.


save button does not go away

Most likely I have redirect problems with redux-forms or with crudUpdate / crudSaga but this part of the code is a bit complex for my limited abilities.
I finally was able to match my rest database components with the jsonServer "rest"calls and have confirmed that the correct data is being updated on the server but somehow the flag for being finished is not being set before Redux-Form  takes over and Redux-form keeps spinning waiting for that flag to be set.
My question where and how isthat  save is finished go back to the previous component flag  set?
This is also related to another problem I am having when a new feature (being able to limit table columns dynamically.) The component works but in order to do so I have to re-select from the left side menu lists. What i would really  like to do is trigger a redraw of the entire component without any other user interaction.  Is this a crudRoute issue or somewhere else?
Any help would be appreciated this redux-form / saga stuff really spins me in circles.

Accidental close.
I am thinking that redux should be renamed rubix as in the cube!.  Very small changes have very big consequences.

Save goes back to the previous state in crudResponse. This happens only if no exception is thrown by your restClient (cf https://github.com/marmelab/admin-on-rest/blob/master/src/sideEffect/saga/crudFetch.js#L21-L26).

thanks
I noticed that you changed crudfetch between release 7 and release 8 to
remove the successSideEffects and failureSideEffects and replaced them with
a crudResponse.
in order to figure out my last bug I ended up consolidating 7.2 version of
success, failure, referenceFetch and index.js into one method but I cannot
seem to get the newer version with meta carrying the  response routing to
work.
My question is whether this change was brought about by a bug in 7.x or are
there other parts of the code that were also affected by it in order to
make it work?
On Tue, Mar 7, 2017 at 3:06 AM, Francois Zaninotto<EMAIL_ADDRESS>
wrote:

Save goes back to the previous state in crudResponse
https://github.com/marmelab/admin-on-rest/blob/master/src/sideEffect/saga/crudResponse.js.
This happens only if no exception is thrown by your restClient (cf
https://github.com/marmelab/admin-on-rest/blob/master/src/
sideEffect/saga/crudFetch.js#L21-L26).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/marmelab/admin-on-rest/issues/376#issuecomment-284691469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI7J7RPIEiBF7-_cSeVudJouiG7Rca_dks5rjTowgaJpZM4MQZaP
.

I advise you to use git blame to get the answer.
As for overriding side effects in 0.7, it wasn't documented nor supported. I'm sorry that it doesn't work anymore, but you weren't supposed to do that in the first place.


Added 'events' property to options

Done :)
I did it the other way so if we add new events we wouldn't have to update this as well, but it's updated so more explicit now like you suggested

Thanks @tjenkinson it's a great feature :beers:


Change Text("") to EmptyView()

Note: I have not tested this, and made the change directly in github

Thank you for your contribution!


RLMSyncLogLevel is deprecated

Problem
Im still getting these deprecation warnings come up, (RLMSyncLogLevel is not used in any of my code so much be internal to the packages) so is there a way a future release can address these to get rid of these warnings?
Solution
Resolve deprecations internal to package
Alternatives
No response
How important is this improvement for you?
Would be a major improvement
Feature would mainly be used with
Local Database only

Hi @krissbennett this APIs are gonna be deprecated in the near future, but on the meantime this warnings may appear for some release. I'll take a look and check if I can remove them completely.

@dianaafanador3 Thanks for looking into this--I reached out to MongoDB Support with basically the same issue. As krissbennett said, there is probably something wrong within the realm-swift package that is leading to this deprecation warning. Deprecation warnings should only appear if you actually try to use the deprecated code in your codebase; a package shouldn't just warn you about any deprecated code you could theoretically use from the package.

Same for Xcode 15 beta.


webapi only return 1 record

I don't know what's wrong.  I did the  http get method:
var chks = _context.CheckListForUsers.Include(c => c.CheckList).ToList();
return chks.
I can see there're 3 records, but only shows 1 if I open it with browser or on my client app.
but if I remove Include(c => c.CheckList), I can get 3 records.
what's wrong?
Thanks,

If you turn on logging to you see any exceptions logged? This issue may be related: https://github.com/aspnet/Mvc/issues/5413

@Tratcher, thanks, but could you tell me how to turn on logging?

Add the console logger: https://docs.asp.net/en/latest/fundamentals/logging.html
Also, if you're using IIS/Express you'll need to enable stdoutLogEnabled in the web.config.
https://docs.asp.net/en/latest/hosting/aspnet-core-module.html


fix: minor glitches in Preview screen implementation

Look and feel:

when screen estate is smaller then styling is not consistent e.g.:

Composition:

it is a bit counter-intuitive to navigate between preview components implementation in order to understand/provide more functionality, maybe there is already existing tree-view structure that could be used instead?

The 'look and feel' part was easy: #220
Composition part:
A lot of work has been put into the custom tree-view functionality.
Unfortunately, the already existing MUI's React Tree View hasz not been used here and therefore out version is not as well documented and may seem complicated.
I see 2 solutions here:

Document the current tree-view implementation
Use MUI's React Tree View - parse the JSON coming from server in a similar way as here: MUI's demo and style the tree accordingly.

If, from the maintenance point of view (considering the documentation and the fact that existing components don't have to be tested, etc...) it would be cheaper to rely on MUI's Tree View I would favour the solution 2....


Update alert-policies.md

Removed description of "HVE A potentially malicious URL click was detected" alert which was built for one specific customer

Learn Build status updates of commit 484335c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/alert-policies.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Ensure that the iptables masquerade rule is always installed

We ran into an issue where sometimes the iptables masquerade rules that flannel creates get deleted. Obviously ideally this wouldn't happen, but if it does happen it's really bad -- containers can't send packets to any hosts outside the cluster.
This PR makes flannel automatically recover from this situation by recreating the iptables rules, so that the cluster will remain healthy:

added a goroutine that automatically recreates the masquerade rules every second
added an alternate version of AppendUnique which returns whether or not the rule was appended. This allows flannel to only log when a rule was actually successfully added, instead of always logging (which, now that we're retrying every second, would add too much noise to the logs)

We're running this in our production cluster now

Hi @julia-stripe, thanks for another well put together PR!
I see one key problem with this PR and then a couple of minor concerns (below) - the main concern is that if a single rule (of the four that flannel installs) is removed, then flannel just restores the one missing rule, which means it might end up being out of order! Since the ordering of the rules matters, I think this defeats the purpose of this PR a bit.
e.g. if I remove the first flannel rules iptables -D postrouting -t nat -A POSTROUTING -s <IP_ADDRESS>/8 -d <IP_ADDRESS>/8 -j RETURN then I can see your code restores it, but it restores it last in the list which means it won't get hit.
I'd be interested to hear if you have any thoughts on automated testing in this area? I know there aren't any existing tests but it would be great to have some.
Otherwise, the code looks good to me, though I'd like to leave it up for at least a few days before merging to give others a chance to comment.
The slight areas of concern I'd have about this are

The additional IPTables churn that this could create. But I'm not too concerned since this should just be 4 attempted appends (one for each rule) per second.
The potential for multiple processes to "fight" over keeping these rules updated. If there is another process which is making changes to the NAT table then potentially that could cause additional churn.

@fasaxc I'd love to hear your thoughts on this.

On (1), looks like the code checks for the existence of the rule first, so it's 4 reads per second.  That  could be moderately expensive if there are a lot of rules (since most iptables operations do a full table load from the kernel to userspace, even to check one rule).
On (2), as long as the other process isn't deleting these rules actively then we should be OK (and if it was actively trying to delete those rules then there's not much we can do.
Longer term, you may want to migrate to having only a single rule inserted into the root chain and then jumping fro there to a flannel-owned chain.  That's the approach that we have in Calico; it reduces cloberring since there's only one rule and it avoids reordering issues.

I see one key problem with this PR and then a couple of minor concerns (below) - the main concern is that if a single rule (of the four that flannel installs) is removed, then flannel just restores the one missing rule, which means it might end up being out of order! Since the ordering of the rules matters, I think this defeats the purpose of this PR a bit.

this is a great point. Changed the PR so that it instead:

checks if any rules are missing
if so, deletes all the rules and recreates them in order.

I also added a mock IPTables struct & some tests to give us a little more confidence that this code actually works as intended.

@fasaxc thanks for the comments. I agree that longer term, a single jump to a flannel owned chain would be better.
@julia-stripe That's looking much better thanks. Could you squash the two commits then I can merge it?

Squashed.

I also think it's desirable that the rules aren't cleaned up (so the dataplane keeps working during an upgrade).

This makes sense to me.


Add default timeout for Dedicated Apps to prevent runaway functions

I think we should add a relaxed default timeout back to Dedicated apps in a future breaking release.
Had a customer issue where their python function would timeout every 20 hours or so, requiring a site restart (he did not know about the configurable function timeout setting).
As it's now configurable (it was not in the time of #657), users can remove it if it negatively affects their scenario, but it should save some apps from being completely stalled.

@mamaso can you clarify scenario? Do you have Always-On enabled?

I finally have finished my Python function that monitors an Azure subscription for modifications but there seems to be an issue with it hanging.  What I have noticed is that after about 20 hours of executing the function every N seconds it the script hangs and never finishes.  The next morning I will come in and restart the service and it works great for another 20 hours.
Customer had Always On enabled, no default timeout set.
I think we should enable a default timeout on dedicated to prevent situations like this requiring manual restarts.  If someone wants to run a function that long they can remove the timeout setting.

I agree. Having a sensible limit by default is likely the desired behavior here.
@lindydonna @christopheranderson thoughts?

Agreed. @christopheranderson probably has a better sense of what the value should be. 10 minutes?  15 minutes?

Please allow azure functions on Consumption plan to run with timeout greater than 5min. This is too restrictive for certain applications.

Shouldn't change the host behavior, should instead add an entry in host.json

Created https://github.com/Azure/azure-webjobs-sdk-script/issues/1232 to track adding the setting in host.json.


Remove existing Asset Manager asset files from NFS

Note that we need to implement a solution for new assets before doing this.
Once we have enabled proxying to S3 via Nginx for staging & integration, we should be able to delete all Asset Manager asset files from NFS on all environments and rely entirely on the assets being in the relevant S3 bucket.

If the nightly off-site backup job has not been removed, we should be aware that any changes we make to the production NFS mount will be synced to staging & integration overnight.
We should be careful not to delete any files which are currently being processed by Sidekiq jobs (e.g. awaiting/undergoing virus scan or S3 upload). We can probably achieve this by iterating over the assets in the Asset Manager database and checking the state of each asset before actually deleting the underlying file from NFS.
We should be careful not to delete any Whitehall assets from NFS, i.e. files under /mnt/uploads/whitehall as opposed to /mnt/uploads/asset-manager.
We should not remove the /mnt/uploads/asset-manager directory, because the Asset Manager app will still need to store files there until they have been virus scanned and uploaded to S3.

Note: We should stop the nightly Duplicity backup of the Asset Manager assets before doing this.


OCI runtime create failed ( OS Ubuntu 20.04)

when running the docker-compose build && docker-compose up I get an OCI runtime creage failed ( posted below):
Sending build context to Docker daemon  1.724MB
Step 1/7 : FROM python:3
 ---> 6beb0d435def
Step 2/7 : ENV PYTHONUNBUFFERED=1
 ---> Using cache
 ---> 2aab34bae599
Step 3/7 : WORKDIR /clifs
 ---> Using cache
 ---> 7c6854350226
Step 4/7 : COPY requirements.txt /clifs
 ---> Using cache
 ---> df31f0e3f4ff
Step 5/7 : RUN pip install -r requirements.txt
 ---> Running in 8eca7fd2853d
OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:722: waiting for init preliminary setup caused: EOF: unknown
ERROR: Service 'web' failed to build : Build failed ```

**any ideas I have tried running the command as sudo and user. Upon my digging I found the error might contain to setup of Dockerfile but not sure.**

Not seen this issue before. I would check that docker has enough drive space available and that the docker version is relatively new. I guess you could also try DOCKER_BUILDKIT=1 just ahead of your build command.

Ran with that appended to the command with some other minor changes and new error message is this:
Attaching to clifs-web-1, search-engine
clifs-web-1    | standard_init_linux.go:228: exec user process caused: no such file or directory
Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request: unknown```

any other advice would be appreciated thanks, still debugging on my end as well.

Alright, so it seems to build. If you're trying to run the GPU-enabled docker-compose file, make sure you've got the nvidia-container-toolkit installed as well as a NVIDIA driver that works for CUDA 10.1.
You could check just your NVIDIA setup by running e.g., the image used in this app (pytorch/pytorch:1.6.0-cuda10.1-cudnn7-devel) and test that the GPU is available to it.

new error: ```Successfully built 236e84e61a41
Successfully tagged clifs_search-engine:latest
Removing search-engine
Starting clifs_web_1                  ... done
Recreating d1d9af7a0e6c_search-engine ... error
ERROR: for d1d9af7a0e6c_search-engine  container d1d9af7a0e6c5a0777f34b2e7820530a32f7312df8d7fed89741e2b43a294778: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/c718c1688e0285f1f24db1dba3fa0c7274c87c157eef6a6b802e6ff77ca64b0d/merged: device or resource busy
ERROR: for search-engine  container d1d9af7a0e6c5a0777f34b2e7820530a32f7312df8d7fed89741e2b43a294778: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/c718c1688e0285f1f24db1dba3fa0c7274c87c157eef6a6b802e6ff77ca64b0d/merged: device or resource busy
ERROR: Encountered errors while bringing up the project.

Still looks like I am having trouble finding the correct NVIDIA driver. Do you have link or more information on which on you used, and where you downloaded it from. This is the last error I am encountering:
Successfully tagged clifs_search-engine:latest
Starting clifs_web_1   ... done
Starting search-engine ... done
Attaching to search-engine, clifs_web_1
web_1            | standard_init_linux.go:228: exec user process caused: no such file or directory
clifs_web_1 exited with code 1
search-engine    |  * Serving Flask app 'server' (lazy loading)
search-engine    |  * Environment: production
search-engine    |    WARNING: This is a development server. Do not use it in a production deployment.
search-engine    |    Use a production WSGI server instead.
search-engine    |  * Debug mode: off
search-engine    | /opt/conda/lib/python3.7/site-packages/torch/cuda/__init__.py:52: UserWarning: CUDA initialization: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx (Triggered internally at  /pytorch/c10/cuda/CUDAFunctions.cpp:100.)
search-engine    |   return torch._C._cuda_getDeviceCount() > 0
search-engine    | 2021-10-04 13:51:48,526 -  * Running on all addresses.
search-engine    |    WARNING: This is a development server. Do not use it in a production deployment.
search-engine    | 2021-10-04 13:51:48,526 -  * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
^CGracefully stopping... (press Ctrl+C again to force)```

I already have NVIDIA driver on my machine but torch still not finding it. Thanks

Make sure you are using the GPU docker-compose file (as stated in instructions) and make sure you have the correct nvidia drivers and cuda container toolkit. For the latter two items, I think googling is the easiest solution as it can be a few steps to setup.

I have checked and resolved these issues for now, am now running into the same issue posted by
hoel-bagard: OpenCV error when opening the video #6

Great. That's not an error I've seen earlier either, but I will look into it. Closing this issue as it is now covered by #6


SPI library not found

Hello,
I have a library that uses the Arduino SPI library.
After realising #include<SPI.h> doesn't work i tried adding it maually by adding
find_arduino_library(spi_lib SPI ${board_id})
link_arduino_library(main spi_lib ${board_id})
but I just got the error:
CMake Error at cmake/Platform/Libraries/LibrariesFinder.cmake:38 (message):
Couldn't find library named Spi
So how do i use the SPI library located at:
C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SPI

@Tyrrx Hi there, please add some info regarding your environment as stated here.

I've hit this issue as well.  I was trying to convert from arduino-cmake to this version, but, I seem to have hit 2 issues as listed here.

It doesn't appear to find libraries that are listed in ArduinoSDK/hardware/arduino/avr/libraries
It converts SPI to Spi

/home/seans/.local/share/JetBrains/Toolbox/apps/CLion/ch-0/183.4886.39/bin/cmake/linux/bin/cmake -DCMAKE_BUILD_TYPE=Debug -G "CodeBlocks - Unix Makefiles" /home/seans/git/trillium/trillium-holt-arduino
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Arduino SDK version 1.8.5: /home/seans/apps/ArduinoSDK
-- Determined Platform Header: /home/seans/apps/ArduinoSDK/hardware/arduino/avr/cores/arduino/Arduino.h
-- Arduino SDK version 1.8.5: /home/seans/apps/ArduinoSDK
-- Determined Platform Header: /home/seans/apps/ArduinoSDK/hardware/arduino/avr/cores/arduino/Arduino.h
-- Check for working C compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-gcc
-- Check for working C compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Arduino SDK version 1.8.5: /home/seans/apps/ArduinoSDK
-- Determined Platform Header: /home/seans/apps/ArduinoSDK/hardware/arduino/avr/cores/arduino/Arduino.h
-- Check for working CXX compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-g++
-- Check for working CXX compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at cmake/Platform/Libraries/LibrariesFinder.cmake:38 (message):
  Couldn't find library named Spi
Call Stack (most recent call first):
  CMakeLists.txt:50 (find_arduino_library)

CMake Error at cmake/Platform/Targets/ArduinoLibraryTarget.cmake:70 (message):
  Target doesn't exist - It must be created first!
Call Stack (most recent call first):
  CMakeLists.txt:51 (link_arduino_library)

-- Configuring incomplete, errors occurred!
See also "/home/seans/git/trillium/trillium-holt-arduino/cmake-build-debug/CMakeFiles/CMakeOutput.log".

[Finished]

if I hack LibrariesFinder.cpp and change the find_file PATH and add my ArduinoSDK/hardware/arduino/avr/libraries and then comment out the code that converts to pascal case... it finds the library... but then fails on issue #56.
My LibrariesFinder.cpp hacks are basically this..
#    if (NOT parsed_args_3RD_PARTY)
#        convert_string_to_pascal_case(${_library_name} _library_name)
#    endif ()

    find_file(library_path
            NAMES ${_library_name}
            PATHS ${ARDUINO_SDK_LIBRARIES_PATH} ${ARDUINO_CMAKE_SKETCHBOOK_PATH} /home/seans/apps/ArduinoSDK/hardware/arduino/avr/libraries
            ${CMAKE_CURRENT_SOURCE_DIR} ${PROJECT_SOURCE_DIR}
            PATH_SUFFIXES libraries dependencies
            NO_DEFAULT_PATH
            NO_CMAKE_FIND_ROOT_PATH)

/home/seans/.local/share/JetBrains/Toolbox/apps/CLion/ch-0/183.4886.39/bin/cmake/linux/bin/cmake -DCMAKE_BUILD_TYPE=Debug -G "CodeBlocks - Unix Makefiles" /home/seans/git/trillium/trillium-holt-arduino
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Arduino SDK version 1.8.5: /home/seans/apps/ArduinoSDK
-- Determined Platform Header: /home/seans/apps/ArduinoSDK/hardware/arduino/avr/cores/arduino/Arduino.h
-- Arduino SDK version 1.8.5: /home/seans/apps/ArduinoSDK
-- Determined Platform Header: /home/seans/apps/ArduinoSDK/hardware/arduino/avr/cores/arduino/Arduino.h
-- Check for working C compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-gcc
-- Check for working C compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Arduino SDK version 1.8.5: /home/seans/apps/ArduinoSDK
-- Determined Platform Header: /home/seans/apps/ArduinoSDK/hardware/arduino/avr/cores/arduino/Arduino.h
-- Check for working CXX compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-g++
-- Check for working CXX compiler: /home/seans/apps/ArduinoSDK/hardware/tools/avr/bin/avr-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at cmake/Platform/Targets/ArduinoLibraryTarget.cmake:70 (message):
  Target doesn't exist - It must be created first!
Call Stack (most recent call first):
  CMakeLists.txt:51 (link_arduino_library)

OS: Linux
Distribution Ubuntu
OS Version: 18.10
Platform: Arduino
Platform SDK Version: 1.8.5
My CMakeLists.txt file is...
cmake_minimum_required(VERSION 3.8.2)

set(ARDUINO_SDK_PATH /home/seans/apps/ArduinoSDK/)
set(ARDUNIO_PORT /dev/ttyACM0)

set(CMAKE_TOOLCHAIN_FILE ${CMAKE_SOURCE_DIR}/cmake/Arduino-Toolchain.cmake)

set(PROJECT_NAME trillium_holt_arduino)
project(${PROJECT_NAME})

set(CMAKE_CXX_STANDARD 11)

get_board_id(board_id uno)

file(GLOB API_HDRS api/*.h)
file(GLOB API_SRCS api/*.cpp)

file(GLOB ARINC_HDRS arinc429/holt/*.h)
file(GLOB ARINC_SRCS arinc429/holt/*.cpp)

file(GLOB DIO_HDRS dio/holt/*.h)
file(GLOB DIO_SRCS dio/holt/*.cpp)

file(GLOB RUNTIME_HDRS runtime/arduino/*.h)
file(GLOB RUNTIME_SRCS runtime/arduino/*.cpp)

file(GLOB PROG_HDRS programs/*.h)
file(GLOB PROG_SRCS programs/*.cpp)

file(GLOB MAIN_HDRS *.h)
file(GLOB MAIN_SRCS *.cpp)

set(${CMAKE_PROJECT_NAME}_SRCS  ${API_SRCS} ${ARINC_SRCS} ${DIO_SRCS} ${RUNTIME_SRCS} ${PROG_SRCS} ${MAIN_SRCS})
set(${CMAKE_PROJECT_NAME}_HDRS  ${API_HDRS} ${ARINC_HDRS} ${DIO_HDRS} ${RUNTIME_HDRS} ${PROG_HDRS} ${MAIN_HDRS})

add_arduino_executable(${CMAKE_PROJECT_NAME} ${board_id} ${${CMAKE_PROJECT_NAME}_SRCS})

find_arduino_library(spi_lib SPI ${board_id})
link_arduino_library(Arduino_Library spi_lib ${board_id})

@stuckless Your problem is wrong usage of API, unfortunately...
Take a minute to read this - I've added this just a few days ago (although the API has been consistent all this time)
Besides, are you using the latest version of this framework? i.e. The top-listed in the releases page.

@MrPointer - thx for the quick response.
So, in changing my CMakeLists.txt to be the following...
add_arduino_executable(${CMAKE_PROJECT_NAME} ${board_id} ${${CMAKE_PROJECT_NAME}_SRCS})
link_arduino_library(${CMAKE_PROJECT_NAME} SPI ${board_id})

I still get the following issue :(
CMake Error at cmake/Platform/Targets/ArduinoLibraryTarget.cmake:72 (message):
  Library target doesn't exist - It must be created first!
Call Stack (most recent call first):
  CMakeLists.txt:48 (link_arduino_library)

Clearly, I'm still missing something.

@stuckless Actually, your'e not missing anything at all. I've just checked this on my end and found out it's clearly a bug, and moreover, a serious lack of API, which relates to #66 .
About the clone source - I'd rather not depend on the master branch as this is the main development branch in this repo, where release-unready code might exist, as opposed to a tagged release.

@MrPointer thx, I switched to the released version.  And thanks for you work this.

@stuckless I just remembered that there's a dedicated function for linking platform libraries - It's called link_platform_library and its' API is the same as for link_arduino_library.
Nonetheless, it doesn't mean that this API isn't flawed and shouldn't be fixed.

@MrPointer thx.   I can confirm that does does work.
My CMakeLists.txt now includes the following directives, and they build and upload in a similar way as the older Arduino-CMake project.
add_arduino_executable(${PROJECT_NAME} "${board_id}" ${${PROJECT_NAME}_sources} ${${PROJECT_NAME}_headers})
link_platform_library(${PROJECT_NAME} SPI "${board_id}")
upload_arduino_target(${PROJECT_NAME} "${board_id}" ${ARDUNIO_SERIAL_PORT})

Thanks again for you help with this.  I do think that it would be beneficial to make the library handling more automatic (as I'm guessing you are planning with #66 ).  I personally had no idea that SPI was a platform library vs an arduino library.  The older Arduino-CMake figured this out, somehow, since I didn't add anything to my project's CMakeLists.txt to directly reference it.  I do appreciate the work you've done on this.

@stuckless Great to hear that, thanks.
About the API - I've known this project for a long time now, having worked on it's most popular and attractive fork prior to this "NG" project, so I know exactly how messy stuff was back in the days. Some parts were good, especially regarding usability, bad had been awful design and implementation-wise.
This project tries to address many of those issues, but I don't always get it right of course - That's what community is for 😃


ACX Grants proposal submission period expired

thx for flagging! moved to the "inactive" list via #61.


Request: add a title component/hovertext to the EasyButton

reference: https://community.plotly.com/t/show-and-tell-dash-leaflet/34924/212?u=taliebram
The EasyButton works perfectly, however it currently dus not allow for a hovertext. The EasyButton plugin that it is based on has a title component which adds this.
It is also not possible by adding a dl.Tooltip or dbc.Tooltip as a child or as a parent.
I don't know if it is hard to add, also it is not very important, but I'll add it as a feature request anyway.
Thanks in advance!

I think it should be fairly easy to add. I'll consider it next time I am coding.


openamp_rsc_table example with MBOX: bus fault on TI SK-AM62 M4

I'm using a TI SK-AM62 board running Linux on the main A53 and Zephyr on the M4 core. The Linux image is the stock image provided by TI.
I've been trying to adapt the openamp_rsc_table example for using the newer MBOX subsystem.
The MBOX driver is provided by https://github.com/zephyrproject-rtos/zephyr/pull/71241.
Here's the implementation I'm working on: https://github.com/aleeraser/zephyr/tree/feat/ti-mailbox, in particular this commit contains the changes for the example.
According to TI's documentation, the resource table is correctly loaded at the beginning of the M4 external memory section at 0x9cc00000, while the IPC virtio and vring buffers must be located at 0x9cb00000.
I have therefore created the following device tree overlay:
 / {
	chosen {
		zephyr,ipc_shm = &ipc_shm;
	};

	ipc_shm: memory@9cb00000 {
		compatible = "mmio-sram";
		reg = <0x9cb00000 DT_SIZE_M(1)>;
	};

	mbox-consumer {
		compatible = "vnd,mbox-consumer";
		mboxes = <&mbox0 0>, <&mbox0 1>;
		mbox-names = "tx", "rx";
	};
};

When running the example, I have the following Bus Fault / Precise data bus error:
[00:00:00.000,000] <err> os: ***** BUS FAULT *****
[00:00:00.000,000] <err> os:   Precise data bus error
[00:00:00.000,000] <err> os:   BFAR Address: 0x9cc0002d
[00:00:00.000,000] <err> os: r0/a1:  0x00000048  r1/a2:  0x000000ff  r2/a3:  0x9cc00014
[00:00:00.000,000] <err> os: r3/a4:  0x000077b8 r12/ip:  0x00000000 r14/lr:  0x000006e3
[00:00:00.000,000] <err> os:  xpsr:  0x01000000
[00:00:00.000,000] <err> os: Faulting instruction address (r15/pc): 0x00002bde
[00:00:00.000,000] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:00:00.000,000] <err> os: Current thread: 0x75c0 (main)
[00:00:00.000,000] <err> os: Halting system

The BFAR address (0x9cc0002d) should be within the resource table, and in fact addr2line 0x00002bde blames this as the faulting instruction.

@vaishnavachath any idea or suggestion to share?

@glneo I believe you have got this working, do you have any pointers regarding the issue?

Yes, here is my working branch with openamp_rsc_table example running on M4 with Vaishnav's MBOX driver: https://github.com/glneo/zephyr/tree/openamp-am62x-sk-m4
The change you need to fix your data fault is this one: 4a04044

Thank you very much!

The default RAT configuration is a bit of a mess right now, I'll send this patch upstream after a couple other bug fixes I've sent get through the pipeline.

I've seen your other patches. I agree this is definitely needed as well.

Our solutions seem similar, we should be able to work together to find a clean way to update the current IPM based examples to the newer MBOX (maybe have it selected based on what is found in DT).

Unfortunately I'll be unavailable until the end of the month. Depending on the status of this when I'll be back, I'll be happy to join you if needed.


Enable Scala 2.13.0 in the linker and all the other artifacts.

This is the equivalent of #3702 for the master branch.

Updated to match recent changes in #3702.

Ping @gzm0. If possible I'd like to merge this before the open source spree of Scala Matsuri, happening on Thursday.

Thanks :)


Add /Schemas endpoint

Moved from https://github.com/osiam/resource-server/issues/47
@thomasdarimont wrote:

The section about Service Provider Configuration Endpoints of the SCIM Specification describes a /Schemas endpoint that enables clients to discover the list of supported Schemas.

Are there any plans to add the endpoint /Schemas?

Hi @namoona1,
the /Schemas endpoint was initially planned for the next release, 3.1. It had been dropped from 3.1, because no one seemed to really need it and other features were more important. Nevertheless, it's still planned to add the endpoint in some 3.x release. If you want to see the /Schemas endpoint in the next release, we can certainly add it back to 3.1.
@dacrome @wallner Do you think there are any objections to adding the /Schemas endpoint in 3.1?

No,
I think if there is a demand for it we should add it.

Could you please add it to 3.1, I am seeing more and more provisioning vendors like Sailpoint starting to leverage standard SCIM endpoints such as /Schemas
Thanks
On Thu, Jan 5, 2017 at 8:08 AM -0500, "Thomas Krille"<EMAIL_ADDRESS>wrote:
Hi @namoona1,
the /Schemas endpoint was initially planned for the next release, 3.1. It had been dropped from 3.1, because no one seemed to really need it and other features were more important. Nevertheless, it's still planned to add the endpoint in some 3.x release. If you want to see the /Schemas endpoint in the next release, we can certainly add it back to 3.1.
@dacrome @wallner Do you think there are any objections to adding the /Schemas endpoint in 3.1?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

No, add it

Alright, this is scheduled for 3.1 again.


Events documentation

Would be great to have some quick reference about what events are emitted by the angularPlayer.
E.g: track:progress,  music:isPlaying

@Gargol that's great idea, I was thinking to write proper API documentation already, seems like you pushing me for it now ;)

@perminder-klair no pressure :wink:  just a suggestion. would love to help out if needed.

thanks @Gargol I am going to setup and new branch called documentation using Jekyll. I will let you know once it's pushed, will be great if you can help in writing documentation!

great! cheers buddy.

@Gargol here is is: https://github.com/perminder-klair/angular-soundmanager2/tree/documentation

All sorted with documentation setup http://perminder-klair.github.io/angular-soundmanager2/, just need to write them now!

List of available events are now at documentation, happy to close this issue? as by time we can improve documentation.

@perminder-klair cool to see such fast progress :+1:


Planned adapters

These are the adapters that we should support.

[ ] redis
[x] memcached
[ ] memcache
[ ] mongo
[ ] apc
[ ] apcu
[x] array https://github.com/php-cache/array-adapter
[ ] predis
[ ] sqlite
[ ] file
[ ] filesystem (flysystem)
[ ] zendata
[x] void https://github.com/php-cache/void-adapter
[ ] chain
[x] doctrine

Im starting with void adapter now

Im starting with the array adapter

Im starting with apc

Im starting with apcu

Starting with the filesystem adapter

Im starting with mongo

Staring with PHPredis

Starting with the Chain

Well done mate :) congrats


graylog: 3.3.3 -> 3.3.4

Bumps Graylog and integration plugins to version 3.3.4

Motivation for this change
New version with bugfixes in the integration plugins.
/cc @Ma27
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Ported to stable as d84d3632abb628ce768cec6809fb1c2c915d96d7.


Implement natural language processing for add command

Here are the acceptable format(s):
add  - adds a task which can be done anytime.
add  by  - adds a task which have to be done by the specified deadline. Note the keyword by.
add  from  to  - adds a event which will take place between start time and end time. Note the keyword from and to.
Remember not to delete the previous version of the add command update with start time
Eg. format:  add /p /s /e /d /t

Split into smaller tasks in issue #65


scenario 3 - protect and call web api on azure ad b2c - infinite loop

Issue

Please provide us with the following information:

This issue is for the sample

    - [ ] 1-1) Sign-in with Azure AD
    - [ ] 1-2) Sign-in with Azure AD B2C
    - [ ] 2-1) Acquire a Token and call Microsoft Graph
    - [ ] 3-1) Protect and call a web API on Azure AD
    - [x] 3-2) Protect and call a web API on Azure AD B2C
    - [ ]   4) Deploy to Azure Storage and App Service
    - [ ] 5-1) Call a web API using App Roles
    - [ ] 5-2) Call a web API using Security Groups
    - [ ] 6-1) Call a multi-tenant web API
    - [ ] 7-1) Call Microsoft Graph using on-behalf-of flow
    - [ ] 7-2) Call a web API using Proof of Possession tokens

This issue is for a

    - [x] bug report -> please search issues before submitting
    - [ ] question
    - [ ] feature request
    - [ ] documentation issue or request

Minimal steps to reproduce

Follow the sample tutorial step by step

Any log messages given by the failure

Expected/desired behavior

I should be able to access the web-api / edit my profile

Library version

Browser and version

Safari?

Mention any other details that might be useful
I can login fine (I had to go to the portal first and configure the sign in policy to allow the user to self reset his password) but then when i click the TodoList button it goes to an infinite loop (looks like login/logout)
https://user-images.githubusercontent.com/2547646/120226164-f5aa2580-c246-11eb-9565-9e3f29b98bd7.mov
here is my repo https://github.com/jeromechrist/repro-step-b2c

Thanks! We'll be in touch soon.

@jeromechrist thank you very much for the details and the repro link, I was able to reproduce the issue. I'll get back to you as soon as I figure this out.

I just clicked that grant permission button and I can access the APIs feature fine.
But there is still a loop when I click on "Edit Profile"
https://user-images.githubusercontent.com/2547646/120396169-611ef080-c336-11eb-90d1-7491f3ca7699.mov

@jeromechrist strange, I can reproduce this with the edit user-flow you've set up, but not with my edit user-flow. I'm suspecting this is to do with your configuration. Have you configured any user attributes and/or application claims? It might be that there is no attribute/claim to edit, which might cause the edit screen not showing at all.

@derisen yep that was the case, I did selected claims in "Application claims" but no in "User attributes". After setting a few it works !

Thank you for helping troubleshoot the issue

@jeromechrist awesome! I'll update the sample README with the missing admin consent step and add some remarks about setting up user claims. Really appreciate all the details you provided in the issue -makes our lives easier : )

@derisen heyyyyy sorry, it did resolve the edit profile part but the loop is back on the API :confused:
https://user-images.githubusercontent.com/2547646/120495382-f1077d80-c3bc-11eb-847c-7484a5ae0739.mov

@jeromechrist hmm, I'll check this with B2C team and get back to you. In the meantime, can you send me a network trace using Fiddler. My email is on my GitHub profile.

hey @derisen, sorry for the delay, just for the heck of it I tried another browser and it looks like this bug is happening on Safari only, no issues on Edge (dev channel)
on Safari the bug repro is 100%
https://user-images.githubusercontent.com/2547646/120699728-12e22c80-c4b1-11eb-9cb4-635d08c897bc.mov

@jeromechrist Ok, I've just tested this on a Mac with Safari and I can reproduce it as well.
At this point, it would be best to raise this issue in the main MSAL.js repo, as this is likely to do with the msal-angular itself rather than the sample. I can't seem to transfer it, can you please create a bug report there?

Yep, created there https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/3713


df.std() doesn't display anything

Issue:
since pd.std() returns the standard deviation of both quantitative and temporal columns the data type is object which is ignored in column_group.py

Potential fix:
Either ignore the temporal attribute or come up with different visual encoding that will support quantitate column along with temporal
See https://github.com/willeppy/lux/blob/d38294775ca5930b439c65282b233cc092b12e46/lux/action/column_group.py#L92

Fixed in #10


[SLACK] new SlackBotWorker() Error

** DO NOT ERASE THESE INSTRUCTIONS WITHOUT READING THEM FIRST **
Please read this entire template before posting any issue to get faster response.
Open an issue on this repository with your topic or question, providing as much detail as possible. The more we know, the better we can help.
Before posting, search the repository to see if there's already an issue opened to avoid duplicates.
Are you sure this is an issue with the Botkit core module?
Yes - botbuilder-adapter-slack
For all other questions, requests or help, please feel free to join the discussion slack : https://community.botkit.ai
What are you trying to achieve or the steps to reproduce?
Describe your issue here, include as much detail as necessary to reproduce the issue or implement a missing functionality.
// Wrap code in markdown source tags
        // controller is the Botkit instance
        const slackbot = new SlackBotWorker(controller, message.incoming_message.conversation['team']);
        const user = userId;
        await bot.startPrivateConversation(user.id);
        await bot.say('Howdy, Mike');

What was the result you received?
(node:45547) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'im' of undefined
at SlackBotWorker. (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botbuilder-adapter-slack/1.0.1/node_modules/botbuilder-adapter-slack/src/botworker.ts:87:45)
at Generator.next ()
at /Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botbuilder-adapter-slack/1.0.1/node_modules/botbuilder-adapter-slack/lib/botworker.js:10:71
at new Promise ()
at __awaiter (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botbuilder-adapter-slack/1.0.1/node_modules/botbuilder-adapter-slack/lib/botworker.js:6:12)
at SlackBotWorker.startPrivateConversation (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botbuilder-adapter-slack/1.0.1/node_modules/botbuilder-adapter-slack/lib/botworker.js:86:16)
at Object. (/Users/roger.king/development/joebot/src/events/onboarding.ts:13:18)
at Generator.next ()
at fulfilled (/Users/roger.king/development/joebot/src/events/onboarding.ts:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:45547) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:45547) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:45547) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sendActivity' of undefined
at SlackBotWorker. (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/src/botworker.ts:107:56)
at Generator.next ()
at /Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/lib/botworker.js:7:71
at new Promise ()
at __awaiter (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/lib/botworker.js:3:12)
at _controller.middleware.send.run (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/src/botworker.ts:103:95)
at next (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/ware/1.3.0/node_modules/ware/lib/index.js:82:27)
at Ware.run (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/ware/1.3.0/node_modules/ware/lib/index.js:88:3)
at Promise (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/src/botworker.ts:103:46)
at new Promise ()
at SlackBotWorker. (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/src/botworker.ts:100:16)
at Generator.next ()
at /Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/lib/botworker.js:7:71
at new Promise ()
at __awaiter (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/lib/botworker.js:3:12)
at SlackBotWorker.say (/Users/roger.king/development/joebot/node_modules/.registry.npmjs.org/botkit/4.0.1/node_modules/botkit/lib/botworker.js:93:16)
What did you expect?
Bot starting private conversation with a different user and sending a message.
Screenshots and animated GIFs
Context:

Botkit version: 4.0.1
Messaging Platform: Slack
Node version:
Os:
Any other relevant information:

You definitely do not want to create workers directly like that.  Only use controller.spawn() to do this.

@benbrown Thanks for that. I could have sworn I tried with controller.spawn(). I got it working! I think I may have been forgetting the await


Merge in SP23 Main

TODO: Let's get this PR up to spec!

Couldn't resolve codeclimate issues because codeclimate use Ruby version up tp 2.7.

Nice, thank you! :D


Not able to pull latest rust sns-sdk library

I'm using sns-sdk = "1.2.0" inside my project and getting this error when trying to import sns-sdk
Log:
rust-analyzer failed to load workspace: Failed to load the project at /GitHub/api/Cargo.toml: Failed to read Cargo metadata from Cargo.toml file /GitHub/api/Cargo.toml, Some(Version { major: 1, minor: 71, patch: 0 }): Failed to run `cd "/GitHub/api" && "cargo" "metadata" "--format-version" "1" "--manifest-path" "/GitHub/api/Cargo.toml" "--filter-platform" "aarch64-apple-darwin"`: `cargo metadata` exited with an error:     Updating crates.io index
error: failed to select a version for `curve25519-dalek`.
    ... required by package `solana-program v1.14.18`
    ... which satisfies dependency `solana-program = "=1.14.18"` of package `solana-address-lookup-table-program v1.14.18`
    ... which satisfies dependency `solana-address-lookup-table-program = "=1.14.18"` of package `solana-account-decoder v1.14.18`
    ... which satisfies dependency `solana-account-decoder = "=1.14.18"` of package `solana-client v1.14.18`
    ... which satisfies dependency `solana-client = "^1.14.18"` of package `sns-sdk v1.2.0`
    ... which satisfies dependency `sns-sdk = "^1.2.0"` of package `name_resolver v1.0.0 (/GitHub/api/name_resolver)`
    ... which satisfies path dependency `name_resolver` (locked to 1.0.0) of package `client v1.0.0 (/GitHub/api/client)`
versions that meet the requirements `^3.2.1` are: 3.2.1

all possible versions conflict with previously selected packages.

  previously selected package `curve25519-dalek v3.0.0`
    ... which satisfies dependency `curve25519-dalek = "^3"` of package `ed25519-dalek v1.0.1`
    ... which satisfies dependency `ed25519-dalek = "^1.0.1"` of package `sns-sdk v1.2.0`
    ... which satisfies dependency `sns-sdk = "^1.2.0"` of package `name_resolver v1.0.0 (/GitHub/api/name_resolver)`
    ... which satisfies path dependency `name_resolver` (locked to 1.0.0) of package `client v1.0.0 (/GitHub/api/client)`

failed to select a version for `curve25519-dalek` which could resolve this conflict

Hi @timdegen, could your provide you Cargo.toml as well? This would help us reproduce the issue

Hey @timdegen, sorry for the late reply! Basically ethers and the solana library do not play well, and this is related to an outdated upstream dependency for the crate zeroize. You can track the relevant issues here :

https://github.com/solana-labs/solana/issues/26688
In the meantime, we have dealt with it by splitting our libraries into Solana and Ethereum ones, with a common crate for shared functionality. That's not really satisfying but it might take months for this issue to be completely resolved.


Missing helpers

Also note sodium_free hack in leu of ArrayBuffer.transfer

much cleaner like this. looks good to me

I think my ci fix worked but travis is being unstable now ... Otherwise feel free just to undo my "fix"


fix: mobile logo alignment

Signed-off-by: Shivansh-yadav13<EMAIL_ADDRESS>BEFORE

AFTER

@Selflocking plz review


Error processing request

Im not sure why but i want to get the raspberry pi's i tried the Download FFU but when i click confirm on the last one asking for what device it just says error processing request if you could help that be great :)

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

ID: 257dc32b-f302-db2a-2571-8f217007d893
Version Independent ID: 92b2f238-f621-3feb-5b5b-07aed095b115
Content: Suggested Prototype Boards - Windows IoT
Content Source: windows-iotcore/tutorials/quickstarter/PrototypeBoards.md
Product: windows-iot
GitHub Login: @saraclay
Microsoft Alias: saclayt

@Colink02 please download the image from Windows 10 IoT Downloads
@saraclay the download FFU links are pointing to Insider and not to Release, that's not a good idea...

you are welcome


Fixes 13249: Added ingestion support - Presto tbl/col comments

Describe your changes:
Fixes #13249

I worked on ... because ...

Type of change:

[ ] Bug fix
[ ] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Thanks @mitchellmann for the contribution.
 I still see some tests failing, but I do not believe they are related.


https://raw.githubusercontent.com/MicrosoftLearning/MS-4010-Build-Plugins-Connectors-Microsoft-Copilot-M365/main/Instructions/Labs/LAB_01/6-summary.md

Module: 00
Lab/Demo: 01
Task: 00
Step: 00
Description of issue
-'More Resources':  The links for the additional resources are invalid.

Thank you for raising this issue. We are reviewing this issue and will update on this soon

Closing - new labs have been released, no need for fix now.  Thx.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4378

Questions ?
Please refer to the Backport tool documentation


Add dfrs

Add dfrs (https://github.com/GaviTSRA/dfrs) to the list

I didn't get a notification from this, my bad for not merging


Maven support

Bring across Maven support from Spoon based lsif-java (aka from Spoon itself) as that appeared to work pretty well for the majority of cases

Fixed in #100


Style precedence incorrect when using :not selector

Describe the bug
If a style has a :not(...) selector setting a property, that property cannot be overridden by a selector closer to the control without also specifying the same :not(...) selector.
To Reproduce
Create the following window:
Steps to reproduce the behavior:
<Window ...>
    <Window.Styles>
        <!-- every button should stretch content -->
        <Style Selector="Button">
            <Setter Property="VerticalContentAlignment" Value="Stretch"/>
        </Style>

        <!-- if its not in the stretch buttons stack panel make it center -->
        <Style Selector="Button:not(.StretchButtons Button)">
            <Setter Property="VerticalContentAlignment" Value="Center"/>
        </Style>
    </Window.Styles>

    <Grid ColumnDefinitions="* *">
        <StackPanel Classes="StretchButtons">
            <Button Height="100">
                <Border BorderBrush="Red" BorderThickness="5">
                    <TextBlock Text="Should stretch"/>
                </Border>
            </Button>
            <Button Height="100">
                <Border BorderBrush="Red" BorderThickness="5">
                    <TextBlock Text="Should also stretch"/>
                </Border>
            </Button>
        </StackPanel>

        <StackPanel Grid.Column="1">
            <StackPanel.Styles>
                <!-- Override the center style so the button is stretched -->
                <Style Selector="Button">
                    <Setter Property="VerticalContentAlignment" Value="Stretch" />
                </Style>
            </StackPanel.Styles>
            <Button Height="100">
                <Border BorderBrush="Red" BorderThickness="5">
                    <TextBlock Text="should stretch since the style is closer"/>
                </Border>
            </Button>
        </StackPanel>
    </Grid>
</Window>

Expected behavior
The second stack panels button should be Stretch'd content alignment because the style is closer
Screenshots

Desktop (please complete the following information):

OS: Windows
Version 11.0.0-rc1.1

Additional context
It's possible to work around this by changing the selector for the style in the stack panel to also be Button:not(.StretchButtons Button) but in my use case that's a very difficult workaround to manage

It is by design, as selectors with pseudoclasses are trigger selectors and are higher in priority.
But I suppose ":not" shouldn't necessary count as a trigger selector.
cc @grokys

That makes sense now I know it uses the same system as the pseudo classes, I just tried the stack panel style with the selector Button:not(.SomeNonExistingClass) and that also works, but does seem very un intuitive.
I'd like to suggest that all the selectors on the docs (:is, :not and :nth-*) should also not count as trigger selectors. Or at least the docs should explain the edge case by using them.


Fix code scanning alert - Use of password hash with insufficient computational effort

Tracking issue for:

[x] https://github.com/KaygusuzAbdal/juice-shop/security/code-scanning/80

Fixed by replacing export const hash = (data: string) => crypto.createHash('md5').update(data).digest('hex') code fragment with:
const bcrypt = require("bcrypt")
export const hash = (data: string) => bcrypt.hashSync(password, salt).digest('hex')

Fixed by replacing export const hash = (data: string) => crypto.createHash('md5').update(data).digest('hex') code fragment with:
const bcrypt = require("bcrypt")
export const hash = (data: string) => bcrypt.hashSync(password, salt).digest('hex')


WebVTT position setting not working

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
v4.2.1 (from demo page)
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Didn't test
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
N/A
What browser and OS are you using?
Chrome 105.0.5195.102 on Windows 10
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
What are the manifest and license server URIs?

https://www.kaltura.com/p/0/playManifest/entryId/0_z79l0t8f/format/mpegdash/protocol/https/x.mpd
(Choose the "Spanish" subtitles)
What configuration are you using?  What is the output of player.getConfiguration()?

Using the demo page default
What did you do?

Play the stream & choose the "Spanish" subtitles
What did you expect to happen?
The cue "Left alignment" is expected to appear on the left, it has these WebVTT settings:
00:00:25.000 --> 00:00:30.000 position:10%,line-left align:left size:35%
Left alignment

Same for "Right alignment":
00:00:30.000 --> 00:00:35.000 position:90% align:right size:35%
Right alignment

What actually happened?

All cues seem to be centered horizontally.
I think that we're missing + '%' here -
https://github.com/shaka-project/shaka-player/blob/main/lib/text/ui_text_displayer.js#L620
Since position is only the number -
https://github.com/shaka-project/shaka-player/blob/main/lib/text/vtt_text_parser.js#L666
However, even after manually adding the % in Chrome dev tools, the line did not show in the correct position.
Thank you!
Eran

I encountered a related positioning bug with my subtitles.
Adding % where you suggest is only part of the solution since the specs are incorrectly implemented.
For instance, if you read the specs here, you'll see that if no alignment is given for position (i.e. same as auto), it should follow the text alignment.
So if you have 00:04:07.360 --> 00:04:10.080 align:end position:90%, it means that:

the text is right-aligned inside the cue box,
and the cue box itself is positioned at 10% from the right side of the viewport.

But have a look at the following code:
  static setPositionAlign_(cue, align) {
    const Cue = shaka.text.Cue;
    if (align == 'line-left' || align == 'start') {
      cue.positionAlign = Cue.positionAlign.LEFT;
    } else if (align == 'line-right' || align == 'end') {
      cue.positionAlign = Cue.positionAlign.RIGHT;
    } else {
      cue.positionAlign = Cue.positionAlign.CENTER;
    }
  }

It says that if no position alignment is given, center is used.
I'll try to fix that and make a PR.

Well... After reading the specs for the 1000th time, some things are not as clear as I thought they were.
For instance, it says here:

the default value of the WebVTT cue position alignment is center

But it says here:

By default, the position alignment is set to auto.

I started a PR but I'm gonna investigate a little bit more, and commit fixes if needed.

I commited changes to my PR and I think it's ready.

Awesome, thanks @Robloche!


[minor] Use teamsfx-cli to sideload xml manifest

Change Description:
Changing the sideloading of xml manifests to match that of json manifests.  They will both be loaded through the service using teamsfx-cli

Do these changes impact command syntax of any of the packages? (e.g., add/remove command, add/remove a command parameter, or update required parameters)
No.

Do these changes impact documentation? (e.g., a tutorial on https://learn.microsoft.com/office/dev/add-ins/overview/office-add-ins)
No.

If you answered yes to any of these please do the following:
> Include 'Rick-Kirkham' in the review
> Make sure the README file is correct
Validation/testing performed:
Ran automated tests.  Tried sideloading a test project using the script changes targeting current versions of Outlook as well as older ones that don't support json manifests.

Can I get a review?


Code highlighting

Probably needs some updating. A bit of a hack with some of the CSS.

Hey @JacobAnavisca,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 8e2e3ed0-d384-11e9-9a2a-b93990a2c4d9

Hey @JacobAnavisca,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 7fbedf20-d448-11e9-847a-07722ef8bbdd

I stumbled upon a bug in which repeated requests response body are not updated in textarea.
To reproduce:
0. Send a request

Send another request
Response body is not updated
Preview HTML is also kinda broken

@liyasthomas Sorry for merging! I thought the OK meant good to merge. Do you have an API that returns HTML so I can test and get a fix in?

All 404 returns HTML response.

@liyasthomas Just committed a fix for the response issue. I didn't notice an issue with the Preview HTML unless I'm missing something.

@JacobAnavisca Thanks for the quick response


Feature: Error feedback in case of missing query parts

In case of partial query results, i.e. some sites couldn't be reached, display a corresponding error info in order for users to know they have only partial data.

dedicated info/erro box if one or more sites are offline
dedicated info page (sites status + _issues)


Touchscreen doesn't work if keyboard or mouse plugged on on start up

Description
We are building for Yocto Zeus, raspberry pi4.
The touchscreen works properly unless a mouse or keyboard is plugged in on boot. The touch screen continues to work properly idfa mouse or keyboard is plugged in after the system is up and running.

Connect touchscreen
boot system, touchscreen works
Connect Keyboard
reboot system, no touchscreen

Describe the results you expected:
We would like to be able to use the touchscreen even if a keyboard or mouse is plugged in when the system boots.
Additional details (revisions used, host distro, etc.):
Yocto Poky version 3.0.4, Zeus, compiled on Ubuntu 18.04

Zeus is not a version that we maintain anymore. Have you tried honister or master?

Hello Andrei,
We are using the QT boot2qt version of the Yocto system, so I am stuck on zeus for now. The next version of boot2qt will be using Hardknot.
Do you know if there are any changes between zeus and the current master that might affect this?
Regards,
Greg
From: Andrei Gherzan @.>
Sent: Thursday, December 9, 2021 10:20 AM
To: agherzan/meta-raspberrypi @.>
Cc: Greg Wilson-Lindberg @.>; Author @.>
Subject: Re: [agherzan/meta-raspberrypi] Touchscreen doesn't work if keyboard or mouse plugged on on start up (Issue #970)
Zeus is not a version that we maintain anymore. Have you tried honister or master?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/agherzan/meta-raspberrypi/issues/970#issuecomment-990105552, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE7XRTYJJV3625EQY2OE4BLUQDXMXANCNFSM5JSONI7Q.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

It's very hard to say given how old zeus is. What is the graphical stack you are using?

The top level is EGL. I don't know what the pieces in the middle are, boot2qt does not run a window manager, just the application.
Is there a way to figure what is loaded for that?

@GWLindberg Indeed, the bottom level is EGL. The interface between Qt and the EGL is the QPA_PLUGIN, I guess in your case is eglfs. Qt has its own way of handling the touch/mouse events. It's the tslib that does the magic. I suggest starting investigating from there.

Hi Aurelian,
Thank you for the insight, I will contact Qt support to try to figure out what is going on there.
Regards,
Greg

I'm going to close this issue as zeus is not a branch we maintain anymore. Nevertheless, I'm happy to pull in changes that would fix this on zeus as long as you manage to figure out the issue.


enable empty security definition

This allows to use optional authentication and provide different
responses to authenticated users via the same API-Endpoint.
Fixes #1036
Changes proposed in this pull request:

Enable optimal authentication
Provide different information to logged in customers via the same API endpoint

Thanks for fixing my typos. I squashed them into my commit.
An empty security definition is not explicitly defined within the OpenAPI specification. But according to a comment in the OpenAPI-Secification Repo it should be possible.
i also found support within the go server library as of this discussion.
It would be great to see this feature within connexion, because there are a lot of use cases for optional auth. E.g. providing demo data for unauthenticated users or provide publicly available data (e.g. OpenData) without authorization and protected data via the same API endpoint.

Hello,
I just wanted to add my support for this. This would be incredibly helpful for us.

:+1:


Please invite me to the GitHub Community Organization

Name
Avneesh Agarwal
Discord Username (if applicable)
Avneesh#5806
Additional Context
Hey there, I got to know about Eddie from Francesco. I am loving that this community is helping so many people to improve their profiles, OSS projects and their portfolios! I would love to help others too :D

Welcome to the community!

Thank you!