NRF51822 sometimes hard fault on connect

Describe the bug
I write code https://github.com/korneliuszo/lumiax-controller/
and it sometimes hardfaults on connection
To Reproduce
./scripts/tlay2_server.py  - to connect to my UART protocol
./scripts/aaa.py - for trigger loop
Expected behavior
not crashing
Impact
It makes my device unusable
Logs and console output
It breaks on assert:
https://github.com/zephyrproject-rtos/zephyr/blob/6fe1299c33994329ebfba5c4c94caae57f43b79f/subsys/bluetooth/controller/ll_sw/nordic/lll/lll_scan.c#L1195
Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK=0.14.2
Commit 6fe1299c33994329ebfba5c4c94caae57f43b79f

Tried to run bt code only after bt_ready callback from bt_enable function.
Didn't help.
Stack:
Thread #8 536877040 (Name: main, prio:0,useropts:1) (Suspended : User Request)	 	arch_system_halt() at fatal.c:34 0x1a2d8	 	k_sys_fatal_error_handler() at fatal.c:46 0x1a2e0	 	z_fatal_error() at fatal.c:131 0x1a2fa	 	z_arm_fatal_error() at fatal.c:63 0x172ca	 	z_arm_fault() at fault.c:1,094 0x1f6c	 	z_arm_hard_fault() at fault_s.S:102 0x1fa6	 	<signal handler called>() at 0xfffffff1	 	isr_rx_pdu() at lll_scan.c:1,195 0x107f8	 	isr_rx() at lll_scan.c:766 0x107f8	 	isr_radio() at radio.c:140 0x11344	 	radio_nrf5_isr_body() at lll.c:93 0xf45a	 	radio_nrf5_isr() at lll.c:87 0xf45a	 	<signal handler called>() at 0xfffffffd	 	0xe500e7ea	 	0x80fffe

@korneliuszo can you come up with a simple application that reproduces the problem? Your project is not trivial to set up.

hang.zip
Probably beacuse of this happens.
I use irqlock in fifo.hpp for atomically read 2 pointers.


Cleanup: use idiomatic Go.

Changes
There are no expected functional changes in this PR.
Cleanup: use idiomatic Go.

Use context timeout rather than rolling our own.
Use time.Minute rather than 60*time.Second.
In-lined single-use helper functions.
Added comments with questions around unclear code.
Use t.Cleanup instead of defer where appropriate.
Return after t.Error when it's clear that continuing is pointless.

See:

https://google.github.io/styleguide/go/decisions#matching-braces
https://google.github.io/styleguide/go/decisions#cuddled-braces
https://testing.googleblog.com/2017/06/code-health-reduce-nesting-reduce.html
https://google.github.io/styleguide/go/best-practices#t-fatal
https://pkg.go.dev/testing#T.Cleanup

/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[N/A] Has Docs included if any changes are user facing
[N/A] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[N/A] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[N/A] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

didn't realize this was a chains PR 😅 but you have my approval anyway, haha


move from @renovate/pep440 to @renovatebot/pep440; affects [pypi piwheels python]

At some point this package moved namespace and we didn't notice.
We're already using the right copy of @renovatebot/ruby-semver

This is also a very uncontroversial change. Going to just get this one merged too.


npm run mocha-test fails.

Hello, I am trying to run mocha in my app, but every time it is failing.
I am trying npm run mocha-test command.
I am getting the following error in the command prompt:

When I tried to google with

Error: EPERM: operation not permitted, symlink

I found a solution in this issue in GitHub:
meteor reset
npm install
npm test
However, I received the following error then (on running npm test):

I checked manually in the library and found fibers.node
I also initiated a build in C:\Program Files\nodejs\node.exe C:\Users\Omistaja\Documents\GitHub\platform\node_modules\chimp\node_modules\fibers but that failed as well.
I am not sure what I am doing wrong.
Sorry for the long description.
Node version: v8.11.1
Meteor Version: 1.5.2
npm version: 5.6.0

It looks like meteor's problem, not mocha's.

or meteor-mocha... not sure.  sorry, but we can't help.


Add tnozicka

/cc @deads2k

merging manually to unblock other efforts - in line with what you have approved yesterday for the other repo


version 0.1.4

2016-10-20 0.1.4

Removed depenency on tower-cli #5
Code refactoring

Coverage increased (+0.9%) to 100.0% when pulling 94bc16267b08e5e9a5e596b42df4ccc7eb1c4b48 on 0.1.4 into 5f6b7e49fc9ac2313738168eb59e091b97b82798 on master.

closes #27


Change utt_split type to float

The docs show that utt_split is actually a float value, so I think this type should be changed.
I tested this change by printing out _url in abstract_sync_client.py > _handle_request(), and then making Prerecorded requests with and without this change. For utt_split values of 0.001, 2, and 1.01000, the _url was the same with and without this change.
In other words, this change seems to be a functional no-op and is just documentation.

Yep, that's an oops. Nice catch!


use env variable for script copy location

Since the STI_SCRIPTS_PATH is set to image:///usr/local/sti, which is on a proper PATH this won't work.

@jhadvig see https://github.com/openshift/sti-base/pull/60/files#diff-b0556bed298b3a4fb269eb10d69c91a5R14

STI_SCRIPTS_PATH!=STI_SCRIPTS_URL

LGTM


support old bitcoind versions

fix #2
It was easier than expected. This works with bitcoind 0.16.3. I need someone to confirm that this works with new versions though. I'll be upgrading over the next 2 weeks probably, so I might confirm it myself if no one else beats me to it.

Let me know if it works after you upgrade! Thanks!

It turns out that Account must be set to * or omitted for new versions. I also verified that that works for old versions.

Awesome!


new pod ip cannot ping successfully suddenly

I use calico as my  k8s cluster  network componet  and it run normally last few months.
and suddenly when new pod created, the pod ip o can't ping successfully
Expected Behavior

pod ip cannot ping successfully from host

Current Behavior

here is my pods on one node

the new pod ip <IP_ADDRESS> can't ping successfully but the old pod ip <IP_ADDRESS> still ping successfully

here is the calico-node logs when I create the new pod ifae97645333407eb3f312af988e529d-single-0
{"log":"2019-07-15 02:19:05.950 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:05.95034452Z"}
{"log":"2019-07-15 02:19:05.950 [INFO][207] table.go 717: Invalidating dataplane cache ipVersion=0x4 reason=\"refresh timer\" table=\"filter\"\n","stream":"stdout","time":"2019-07-15T02:19:05.950452105Z"}
{"log":"2019-07-15 02:19:05.950 [INFO][207] table.go 438: Loading current iptables state and checking it is correct. ipVersion=0x4 table=\"filter\"\n","stream":"stdout","time":"2019-07-15T02:19:05.9504673Z"}
{"log":"2019-07-15 02:19:05.952 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=2.018841\n","stream":"stdout","time":"2019-07-15T02:19:05.95236442Z"}
{"log":"2019-07-15 02:19:07.744 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:07.744669821Z"}
{"log":"2019-07-15 02:19:11.672 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:11.672773727Z"}
{"log":"2019-07-15 02:19:11.672 [INFO][207] ipsets.go 222: Asked to resync with the dataplane on next update. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:11.672796618Z"}
{"log":"2019-07-15 02:19:11.672 [INFO][207] ipsets.go 253: Resyncing ipsets with dataplane. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:11.672831329Z"}
{"log":"2019-07-15 02:19:11.676 [INFO][207] ipsets.go 295: Finished resync family=\"inet\" numInconsistenciesFound=0 resyncDuration=3.37344ms\n","stream":"stdout","time":"2019-07-15T02:19:11.676205746Z"}
{"log":"2019-07-15 02:19:11.676 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=3.544368\n","stream":"stdout","time":"2019-07-15T02:19:11.676248688Z"}
{"log":"2019-07-15 02:19:13.183 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:13.1838769Z"}
{"log":"2019-07-15 02:19:15.303 [INFO][207] int_dataplane.go 447: Linux interface addrs changed. addrs=set.mapSet{\"fe80::ecee:eeff:feee:eeee\":set.empty{}} ifaceName=\"caliec83ef92d7e\"\n","stream":"stdout","time":"2019-07-15T02:19:15.303427458Z"}
{"log":"2019-07-15 02:19:15.303 [INFO][207] int_dataplane.go 598: Received interface addresses update msg=\u0026intdataplane.ifaceAddrsUpdate{Name:\"caliec83ef92d7e\", Addrs:set.mapSet{\"fe80::ecee:eeff:feee:eeee\":set.empty{}}}\n","stream":"stdout","time":"2019-07-15T02:19:15.303562173Z"}
{"log":"2019-07-15 02:19:15.303 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:15.303578347Z"}
{"log":"2019-07-15 02:19:15.303 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=0.079182\n","stream":"stdout","time":"2019-07-15T02:19:15.303665534Z"}
{"log":"2019-07-15 02:19:15.306 [INFO][207] int_dataplane.go 429: Linux interface state changed. ifaceName=\"caliec83ef92d7e\" state=\"up\"\n","stream":"stdout","time":"2019-07-15T02:19:15.306248984Z"}
{"log":"2019-07-15 02:19:15.306 [INFO][207] int_dataplane.go 588: Received interface update msg=\u0026intdataplane.ifaceUpdate{Name:\"caliec83ef92d7e\", State:\"up\"}\n","stream":"stdout","time":"2019-07-15T02:19:15.306336666Z"}
{"log":"2019-07-15 02:19:15.306 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:15.30667024Z"}
{"log":"2019-07-15 02:19:15.306 [INFO][207] endpoint_mgr.go 239: Workload interface came up, marking for reconfiguration. ifaceName=\"caliec83ef92d7e\"\n","stream":"stdout","time":"2019-07-15T02:19:15.307071174Z"}
{"log":"2019-07-15 02:19:15.306 [INFO][207] endpoint_mgr.go 777: Applying /proc/sys configuration to interface. ifaceName=\"caliec83ef92d7e\"\n","stream":"stdout","time":"2019-07-15T02:19:15.307077778Z"}
{"log":"2019-07-15 02:19:15.307 [INFO][207] route_table.go 442: Syncing routes: found unexpected route; ignoring due to grace period. dest=<IP_ADDRESS>/32 ifaceName=\"caliec83ef92d7e\" ipVersion=0x4\n","stream":"stdout","time":"2019-07-15T02:19:15.307626002Z"}
{"log":"2019-07-15 02:19:15.307 [INFO][207] route_table.go 298: Interface in cleanup grace period, will retry after. ifaceName=\"caliec83ef92d7e\" ipVersion=0x4\n","stream":"stdout","time":"2019-07-15T02:19:15.307642619Z"}
{"log":"2019-07-15 02:19:15.307 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=0.801575\n","stream":"stdout","time":"2019-07-15T02:19:15.307647377Z"}
{"log":"2019-07-15 02:19:16.342 [INFO][207] iface_monitor.go 168: Netlink address update. addr=\"fe80::ecee:eeff:feee:eeee\" exists=true ifIndex=111\n","stream":"stdout","time":"2019-07-15T02:19:16.342398841Z"}
{"log":"2019-07-15 02:19:17.744 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:17.744711458Z"}
{"log":"2019-07-15 02:19:22.513 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:22.513753512Z"}
{"log":"2019-07-15 02:19:22.513 [INFO][207] ipsets.go 222: Asked to resync with the dataplane on next update. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:22.513779073Z"}
{"log":"2019-07-15 02:19:22.513 [INFO][207] ipsets.go 253: Resyncing ipsets with dataplane. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:22.513783399Z"}
{"log":"2019-07-15 02:19:22.513 [INFO][207] route_table.go 442: Syncing routes: found unexpected route; ignoring due to grace period. dest=<IP_ADDRESS>/32 ifaceName=\"caliec83ef92d7e\" ipVersion=0x4\n","stream":"stdout","time":"2019-07-15T02:19:22.514130542Z"}
{"log":"2019-07-15 02:19:22.514 [INFO][207] route_table.go 298: Interface in cleanup grace period, will retry after. ifaceName=\"caliec83ef92d7e\" ipVersion=0x4\n","stream":"stdout","time":"2019-07-15T02:19:22.514152744Z"}
{"log":"2019-07-15 02:19:22.517 [INFO][207] ipsets.go 295: Finished resync family=\"inet\" numInconsistenciesFound=0 resyncDuration=3.418333ms\n","stream":"stdout","time":"2019-07-15T02:19:22.517208267Z"}
{"log":"2019-07-15 02:19:22.517 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=3.641408\n","stream":"stdout","time":"2019-07-15T02:19:22.517258039Z"}
{"log":"2019-07-15 02:19:23.183 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:23.183915499Z"}
{"log":"2019-07-15 02:19:27.744 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:27.744749768Z"}
{"log":"2019-07-15 02:19:29.428 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:29.428711902Z"}
{"log":"2019-07-15 02:19:29.428 [INFO][207] table.go 717: Invalidating dataplane cache ipVersion=0x4 reason=\"refresh timer\" table=\"raw\"\n","stream":"stdout","time":"2019-07-15T02:19:29.428734129Z"}
{"log":"2019-07-15 02:19:29.428 [INFO][207] table.go 438: Loading current iptables state and checking it is correct. ipVersion=0x4 table=\"raw\"\n","stream":"stdout","time":"2019-07-15T02:19:29.428808237Z"}
{"log":"2019-07-15 02:19:29.430 [INFO][207] route_table.go 446: Syncing routes: removing old route. dest=<IP_ADDRESS>/32 ifaceName=\"caliec83ef92d7e\" ipVersion=0x4\n","stream":"stdout","time":"2019-07-15T02:19:29.430418851Z"}
{"log":"2019-07-15 02:19:29.430 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=1.745496\n","stream":"stdout","time":"2019-07-15T02:19:29.430434507Z"}
{"log":"2019-07-15 02:19:29.430 [INFO][207] conntrack.go 78: Removing conntrack flows ip=<IP_ADDRESS>\n","stream":"stdout","time":"2019-07-15T02:19:29.430507295Z"}
{"log":"2019-07-15 02:19:32.966 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:32.966982201Z"}
{"log":"2019-07-15 02:19:32.966 [INFO][207] ipsets.go 222: Asked to resync with the dataplane on next update. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:32.967003077Z"}
{"log":"2019-07-15 02:19:32.966 [INFO][207] ipsets.go 253: Resyncing ipsets with dataplane. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:32.967051298Z"}
{"log":"2019-07-15 02:19:32.970 [INFO][207] ipsets.go 295: Finished resync family=\"inet\" numInconsistenciesFound=0 resyncDuration=3.410025ms\n","stream":"stdout","time":"2019-07-15T02:19:32.970462802Z"}
{"log":"2019-07-15 02:19:32.970 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=3.5811800000000003\n","stream":"stdout","time":"2019-07-15T02:19:32.970495108Z"}
{"log":"2019-07-15 02:19:33.183 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:33.183884038Z"}
{"log":"2019-07-15 02:19:35.335 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:35.336058773Z"}
{"log":"2019-07-15 02:19:35.336 [INFO][207] table.go 717: Invalidating dataplane cache ipVersion=0x4 reason=\"refresh timer\" table=\"nat\"\n","stream":"stdout","time":"2019-07-15T02:19:35.336182711Z"}
{"log":"2019-07-15 02:19:35.336 [INFO][207] table.go 438: Loading current iptables state and checking it is correct. ipVersion=0x4 table=\"nat\"\n","stream":"stdout","time":"2019-07-15T02:19:35.336195203Z"}
{"log":"2019-07-15 02:19:35.337 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=1.550275\n","stream":"stdout","time":"2019-07-15T02:19:35.337604217Z"}
{"log":"2019-07-15 02:19:37.744 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:37.744784291Z"}
{"log":"2019-07-15 02:19:38.452 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:38.452759554Z"}
{"log":"2019-07-15 02:19:38.452 [INFO][207] table.go 717: Invalidating dataplane cache ipVersion=0x4 reason=\"refresh timer\" table=\"mangle\"\n","stream":"stdout","time":"2019-07-15T02:19:38.452781281Z"}
{"log":"2019-07-15 02:19:38.452 [INFO][207] table.go 438: Loading current iptables state and checking it is correct. ipVersion=0x4 table=\"mangle\"\n","stream":"stdout","time":"2019-07-15T02:19:38.452860532Z"}
{"log":"2019-07-15 02:19:38.453 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=1.247249\n","stream":"stdout","time":"2019-07-15T02:19:38.453997902Z"}
{"log":"2019-07-15 02:19:43.184 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:43.184618817Z"}
{"log":"2019-07-15 02:19:43.240 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:43.240480303Z"}
{"log":"2019-07-15 02:19:43.240 [INFO][207] ipsets.go 222: Asked to resync with the dataplane on next update. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:43.240499681Z"}
{"log":"2019-07-15 02:19:43.240 [INFO][207] ipsets.go 253: Resyncing ipsets with dataplane. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:43.24058579Z"}
{"log":"2019-07-15 02:19:43.243 [INFO][207] ipsets.go 295: Finished resync family=\"inet\" numInconsistenciesFound=0 resyncDuration=3.390214ms\n","stream":"stdout","time":"2019-07-15T02:19:43.243932685Z"}
{"log":"2019-07-15 02:19:43.243 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=3.552481\n","stream":"stdout","time":"2019-07-15T02:19:43.243987845Z"}
{"log":"2019-07-15 02:19:47.744 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:47.744745107Z"}
{"log":"2019-07-15 02:19:53.183 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:53.183989353Z"}
{"log":"2019-07-15 02:19:54.235 [INFO][207] int_dataplane.go 690: Applying dataplane updates\n","stream":"stdout","time":"2019-07-15T02:19:54.236099101Z"}
{"log":"2019-07-15 02:19:54.236 [INFO][207] ipsets.go 222: Asked to resync with the dataplane on next update. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:54.236121166Z"}
{"log":"2019-07-15 02:19:54.236 [INFO][207] ipsets.go 253: Resyncing ipsets with dataplane. family=\"inet\"\n","stream":"stdout","time":"2019-07-15T02:19:54.23620437Z"}
{"log":"2019-07-15 02:19:54.239 [INFO][207] ipsets.go 295: Finished resync family=\"inet\" numInconsistenciesFound=0 resyncDuration=3.420777ms\n","stream":"stdout","time":"2019-07-15T02:19:54.239606969Z"}
{"log":"2019-07-15 02:19:54.239 [INFO][207] int_dataplane.go 704: Finished applying updates to dataplane. msecToApply=3.578866\n","stream":"stdout","time":"2019-07-15T02:19:54.239640501Z"}
{"log":"2019-07-15 02:19:57.744 [INFO][207] health.go 150: Overall health summary=\u0026health.HealthReport{Live:true, Ready:true}\n","stream":"stdout","time":"2019-07-15T02:19:57.744789682Z"}

I check the route on this node.

and this happen on all host nodes almost at the same time.

Possible Solution

Steps to Reproduce (for bugs)

Context

network unreachable with new pod

Your Environment

Calico version
image: quay.io/coreos/etcd:v3.1.10
image: quay.io/calico/node:v3.0.4
image: quay.io/calico/cni:v2.0.3
image: quay.io/calico/kube-controllers:v2.0.2

Orchestrator version (e.g. kubernetes, mesos, rkt):
kubernetes

Operating System and version:

Link to your project (optional):

seems I have found out the reason.
the calico-etcd pod have been recreated 3 days ago. And I have check the nodes.
find the node that older calico-etcd pod  running reboot 3 days ago.
so the calico-etcd recreated.

I have 3 Kubernetes masters and I modify the calico-etcd manifest from DaemonSet to Deployment.
becaunse this issue #1902
so is there have calico HA solution?? not just only calico-etcd but also calico-kube-controllers?
here is my yaml
# Calico Version v3.0.4
# https://docs.projectcalico.org/v3.0/releases#v3.0.4
# This manifest includes the following component versions:
#   calico/node:v3.0.4
#   calico/cni:v2.0.3
#   calico/kube-controllers:v2.0.2

# This ConfigMap is used to configure a self-hosted Calico installation.
kind: ConfigMap
apiVersion: v1
metadata:
  name: calico-config
  namespace: kube-system
data:
  # The location of your etcd cluster.  This uses the Service clusterIP
  # defined below.
  etcd_endpoints: "http://<IP_ADDRESS>:6666"

  # Configure the Calico backend to use.
  calico_backend: "bird"

  # The CNI network configuration to install on each node.
  cni_network_config: |-
    {
      "name": "k8s-pod-network",
      "cniVersion": "0.3.0",
      "plugins": [
        {
          "type": "calico",
          "etcd_endpoints": "__ETCD_ENDPOINTS__",
          "log_level": "info",
          "mtu": 1500,
          "ipam": {
              "type": "calico-ipam"
          },
          "policy": {
              "type": "k8s",
               "k8s_api_root": "https://__KUBERNETES_SERVICE_HOST__:__KUBERNETES_SERVICE_PORT__",
               "k8s_auth_token": "__SERVICEACCOUNT_TOKEN__"
          },
          "kubernetes": {
              "kubeconfig": "/etc/cni/net.d/__KUBECONFIG_FILENAME__"
          }
        },
        {
          "type": "portmap",
          "snat": true,
          "capabilities": {"portMappings": true}
        }
      ]
    }

---

# This manifest installs the Calico etcd on the kubeadm master.  This uses a DaemonSet
# to force it to run on the master even when the master isn't schedulable, and uses
# nodeSelector to ensure it only runs on the master.
apiVersion: extensions/v1beta1
#kind: DaemonSet
kind: Deployment
metadata:
  name: calico-etcd
  namespace: kube-system
  labels:
    k8s-app: calico-etcd
spec:
  replicas: 1
  template:
    metadata:
      labels:
        k8s-app: calico-etcd
      annotations:
        # Mark this pod as a critical add-on; when enabled, the critical add-on scheduler
        # reserves resources for critical add-on pods so that they can be rescheduled after
        # a failure.  This annotation works in tandem with the toleration below.
        scheduler.alpha.kubernetes.io/critical-pod: ''
    spec:
      tolerations:
      # This taint is set by all kubelets running `--cloud-provider=external`
      # so we should tolerate it to schedule the calico pods
      - key: node.cloudprovider.kubernetes.io/uninitialized
        value: "true"
        effect: NoSchedule
      # Allow this pod to run on the master.
      - key: node-role.kubernetes.io/master
        effect: NoSchedule
      # Allow this pod to be rescheduled while the node is in "critical add-ons only" mode.
      # This, along with the annotation above marks this pod as a critical add-on.
      - key: CriticalAddonsOnly
        operator: Exists
      # Only run this pod on the master.
      nodeSelector:
        node-role.kubernetes.io/master: ""
      hostNetwork: true
      containers:
        - name: calico-etcd
          image: quay.io/coreos/etcd:v3.1.10
          env:
            - name: CALICO_ETCD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
          command:
          - /usr/local/bin/etcd
          args:
          - --name=calico
          - --data-dir=/var/etcd/calico-data
          - --advertise-client-urls=http://$CALICO_ETCD_IP:6666
          - --listen-client-urls=http://<IP_ADDRESS>:6666
          - --listen-peer-urls=http://<IP_ADDRESS>:6667
          - --auto-compaction-retention=1
          volumeMounts:
            - name: var-etcd
              mountPath: /var/etcd
      volumes:
        - name: var-etcd
          hostPath:
            path: /var/etcd

---

# This manifest installs the Service which gets traffic to the Calico
# etcd.
apiVersion: v1
kind: Service
metadata:
  labels:
    k8s-app: calico-etcd
  name: calico-etcd
  namespace: kube-system
spec:
  # Select the calico-etcd pod running on the master.
  selector:
    k8s-app: calico-etcd
  # This ClusterIP needs to be known in advance, since we cannot rely
  # on DNS to get access to etcd.
  clusterIP: <IP_ADDRESS>
  ports:
    - port: 6666

---

# This manifest installs the calico/node container, as well
# as the Calico CNI plugins and network config on
# each master and worker node in a Kubernetes cluster.
kind: DaemonSet
apiVersion: extensions/v1beta1
metadata:
  name: calico-node
  namespace: kube-system
  labels:
    k8s-app: calico-node
spec:
  selector:
    matchLabels:
      k8s-app: calico-node
  updateStrategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
  template:
    metadata:
      labels:
        k8s-app: calico-node
      annotations:
        # Mark this pod as a critical add-on; when enabled, the critical add-on scheduler
        # reserves resources for critical add-on pods so that they can be rescheduled after
        # a failure.  This annotation works in tandem with the toleration below.
        scheduler.alpha.kubernetes.io/critical-pod: ''
    spec:
      hostNetwork: true
      tolerations:
      # This taint is set by all kubelets running `--cloud-provider=external`
      # so we should tolerate it to schedule the calico pods
      - key: node.cloudprovider.kubernetes.io/uninitialized
        value: "true"
        effect: NoSchedule
      - key: node-role.kubernetes.io/master
        effect: NoSchedule
      # Allow this pod to be rescheduled while the node is in "critical add-ons only" mode.
      # This, along with the annotation above marks this pod as a critical add-on.
      - key: CriticalAddonsOnly
        operator: Exists
      serviceAccountName: calico-cni-plugin
      # Minimize downtime during a rolling upgrade or deletion; tell Kubernetes to do a "force
      # deletion": https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods.
      terminationGracePeriodSeconds: 0
      containers:
        # Runs calico/node container on each Kubernetes node.  This
        # container programs network policy and routes on each
        # host.
        - name: calico-node
          image: quay.io/calico/node:v3.0.4
          env:
            # The location of the Calico etcd cluster.
            - name: ETCD_ENDPOINTS
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: etcd_endpoints
            # Enable BGP.  Disable to enforce policy only.
            - name: CALICO_NETWORKING_BACKEND
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: calico_backend
            # Cluster type to identify the deployment type
            - name: CLUSTER_TYPE
              value: "kubeadm,bgp"
            # Disable file logging so `kubectl logs` works.
            - name: CALICO_DISABLE_FILE_LOGGING
              value: "true"
            # Set noderef for node controller.
            - name: CALICO_K8S_NODE_REF
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            # Set Felix endpoint to host default action to ACCEPT.
            - name: FELIX_DEFAULTENDPOINTTOHOSTACTION
              value: "ACCEPT"
            # The default IPv4 pool to create on startup if none exists. Pod IPs will be
            # chosen from this range. Changing this value after installation will have
            # no effect. This should fall within `--cluster-cidr`.
            - name: CALICO_IPV4POOL_CIDR
              value: "K8S_HA_CIDR"
            - name: CALICO_IPV4POOL_IPIP
              value: "Always"
            # Disable IPv6 on Kubernetes.
            - name: FELIX_IPV6SUPPORT
              value: "false"
            # Set MTU for tunnel device used if ipip is enabled
            - name: FELIX_IPINIPMTU
              value: "1440"
            # Set Felix logging to "info"
            - name: FELIX_LOGSEVERITYSCREEN
              value: "info"
            # Auto-detect the BGP IP address.
            - name: IP
              value: "autodetect"
            - name: IP_AUTODETECTION_METHOD
              value: "can-reach=K8SHA_CALICO_REACHABLE_IP"
            - name: FELIX_HEALTHENABLED
              value: "true"
          securityContext:
            privileged: true
          resources:
            requests:
              cpu: 250m
          livenessProbe:
            httpGet:
              path: /liveness
              port: 9099
            periodSeconds: 10
            initialDelaySeconds: 10
            failureThreshold: 6
          readinessProbe:
            httpGet:
              path: /readiness
              port: 9099
            periodSeconds: 10
          volumeMounts:
            - mountPath: /lib/modules
              name: lib-modules
              readOnly: true
            - mountPath: /var/run/calico
              name: var-run-calico
              readOnly: false
        # This container installs the Calico CNI binaries
        # and CNI network config file on each node.
        - name: install-cni
          image: quay.io/calico/cni:v2.0.3
          command: ["/install-cni.sh"]
          env:
            # Name of the CNI config file to create.
            - name: CNI_CONF_NAME
              value: "10-calico.conflist"
            # The location of the Calico etcd cluster.
            - name: ETCD_ENDPOINTS
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: etcd_endpoints
            # The CNI network config to install on each node.
            - name: CNI_NETWORK_CONFIG
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: cni_network_config
          volumeMounts:
            - mountPath: /host/opt/cni/bin
              name: cni-bin-dir
            - mountPath: /host/etc/cni/net.d
              name: cni-net-dir
      volumes:
        # Used by calico/node.
        - name: lib-modules
          hostPath:
            path: /lib/modules
        - name: var-run-calico
          hostPath:
            path: /var/run/calico
        # Used to install CNI.
        - name: cni-bin-dir
          hostPath:
            path: /opt/cni/bin
        - name: cni-net-dir
          hostPath:
            path: /etc/cni/net.d

---

# This manifest deploys the Calico Kubernetes controllers.
# See https://github.com/projectcalico/kube-controllers
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: calico-kube-controllers
  namespace: kube-system
  labels:
    k8s-app: calico-kube-controllers
spec:
  # The controllers can only have a single active instance.
  replicas: 1
  strategy:
    type: Recreate
  template:
    metadata:
      name: calico-kube-controllers
      namespace: kube-system
      labels:
        k8s-app: calico-kube-controllers
      annotations:
        # Mark this pod as a critical add-on; when enabled, the critical add-on scheduler
        # reserves resources for critical add-on pods so that they can be rescheduled after
        # a failure.  This annotation works in tandem with the toleration below.
        scheduler.alpha.kubernetes.io/critical-pod: ''
    spec:
      # The controllers must run in the host network namespace so that
      # it isn't governed by policy that would prevent it from working.
      hostNetwork: true
      tolerations:
      # This taint is set by all kubelets running `--cloud-provider=external`
      # so we should tolerate it to schedule the calico pods
      - key: node.cloudprovider.kubernetes.io/uninitialized
        value: "true"
        effect: NoSchedule
      - key: node-role.kubernetes.io/master
        effect: NoSchedule
      # Allow this pod to be rescheduled while the node is in "critical add-ons only" mode.
      # This, along with the annotation above marks this pod as a critical add-on.
      - key: CriticalAddonsOnly
        operator: Exists
      # Only run this pod on the master.
      nodeSelector:
         node-role.kubernetes.io/master: ""
      serviceAccountName: calico-kube-controllers
      containers:
        - name: calico-kube-controllers
          image: quay.io/calico/kube-controllers:v2.0.2
          env:
            # The location of the Calico etcd cluster.
            - name: ETCD_ENDPOINTS
              valueFrom:
                configMapKeyRef:
                  name: calico-config
                  key: etcd_endpoints
            # Choose which controllers to run.
            - name: ENABLED_CONTROLLERS
              value: policy,profile,workloadendpoint,node

---

apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: calico-cni-plugin
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: calico-cni-plugin
subjects:
- kind: ServiceAccount
  name: calico-cni-plugin
  namespace: kube-system

---

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: calico-cni-plugin
rules:
  - apiGroups: [""]
    resources:
      - pods
      - nodes
    verbs:
      - get

---

apiVersion: v1
kind: ServiceAccount
metadata:
  name: calico-cni-plugin
  namespace: kube-system

---

apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: calico-kube-controllers
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: calico-kube-controllers
subjects:
- kind: ServiceAccount
  name: calico-kube-controllers
  namespace: kube-system

---

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: calico-kube-controllers
rules:
  - apiGroups:
    - ""
    - extensions
    resources:
      - pods
      - namespaces
      - networkpolicies
      - nodes
    verbs:
      - watch
      - list

---

apiVersion: v1
kind: ServiceAccount
metadata:
  name: calico-kube-controllers
  namespace: kube-system

The manifest that included the etcd pod is not production ready, we expect the user to setup their own HA etcd cluster in that configuration.

@rafaelvanoni how about calico-kube-controllers HA cluster?


PDF preview shows the wrong version of the document

Gitea version (or commit ref): 1.15.0+dev-21-gf4e677edb @ gitea.com
Git version: 2.31.0
Operating system: Linux Manjaro (5.11.6-1-MANJARO)

Description
I committed different versions of a LyX and PDF file on the public repository gitea.com/christiankral/Ipe_Anleitung
If I click on the PDF document Ipe_Anleitung.pdf

the URL becomes https://gitea.com/christiankral/Ipe_Anleitung/src/branch/master/Ipe_Anleitung.pdf and old document version is previewed, which consists of only two pages:

However, the PDF file in the repository holds the actual version of the document, consisting of five pages. One can double check this by cloning the repository by git clone https://gitea.com/christiankral/Ipe_Anleitung.git.
Additionally, when changing the URL to https://gitea.com/christiankral/Ipe_Anleitung/raw/branch/master/Ipe_Anleitung.pdf (change src to raw), the previewed document is the correct version, consisting of five pages.
Note. Possibly this issue is related with #10913

It should be a browser cache problem. Both urls returned 5 pages from me.

Good point. After clearing the cache, it loads five pages. I guess this issue can be closed then.


Permissions

Hello Volkan,
Please with reference to the issue #3240, this is the code inside UserPermissionRepository.cs
  if (!Authorization.HasPermission(PermissionKeys.Tenants))
  {
       result.Remove(Administration.PermissionKeys.Tenants);
  }
            result.Remove("*");
            result.Remove("?");

I added the if condition so that if I want to create users who will have same permissions as the default user admin, I can grant them the tenants permission. So I want to be able to hide or show the tenant permission in the permission tree inside the Edit Permission Dialog depending on whether the user has tenant permissions or not.
Regards,
George

I said no that needs to be hidden, now you are opening another issue, this is not a place for your custom how-to's. This is only for issues. You've opened many issues regarding Multi Tenant tutorial in last weeks. First you need to read the guide carefully, and if you have a custom request for that, sorry but this place is not for custom requests.


Search

You'll need something like lunr integration to provide offline search.
https://www.npmjs.com/package/lunr


InterbrandsOrbico - The message "•Bistrita is not a city in Romania" is displayed instead of the job locations

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the URL in the browser
Search for "interbrandsorbico" Company
Click on "Run Scraper" button
Check the job locations

EXPECTED RESULTS:
Job locations are the same in Scrapers-UI as on the company website
ACTUAL RESULTS:
The message "•Bistrita is not a city in Romania" is displayed instead of the job locations
Attachments:

fixed can you retest?

Retested ✅


Wish: Remote reboot

Sometimes the only way to get everything runing again is a reboot.

Hey!
Thanks for your patience, my apologies for the delayed response. Couldn't agree with you more here and luckily this will be very simple to implement. I'll provide an update once I have a pull request containing this feature.
Thanks!

Hey!
Thanks for your patience, my apologies for the delayed response. Couldn't agree with you more here and luckily this will be very simple to implement. I'll provide an update once I have a pull request containing this feature.
Thanks!


Remove recharts dependency

Hello,
I was successfully using this library to download charts, one at a time. However, now I need to download a single PNG with multiple charts on it. The charts are rendered inside a <div> container and I just need to create a PNG out of this div.
I've noticed that the only dependency to the recharts library is this line of code where you expect ref.current.container to have a container attribute
return await html2canvas(ref.current.container as HTMLElement, {
        logging: false,
        ...options,
})

Other than this, it looks like the useCurrentPng could be made generic and used to render any element to png. Am I right?
If yes, do you think it would be worth it to remove the dependency?

@dan-corneanu Thanks for your suggestion. I created useGenerateImage to work with any HTMLElement. Can you try version 2.3.0-rc.0 and see if it works for you?
You can see examples of how to use it here:
https://github.com/brammitch/recharts-to-png/blob/42efb600f34f95dcba50fef1ef431ccd308ddfad/examples/next-pages/pages/index.tsx#L56-L74

@brammitch yes it does work as expected.

@dan-corneanu Thanks for the feedback! I'll work on getting a proper release out as soon.


Prepare documentation with description of messages consumed from ccx-XXX-insights-operator-archive-features topic

Messages consumed from ccx-XXX-insights-operator-archive-features topic

Pages with description:
https://redhatinsights.github.io/insights-data-schemas/internal-pipeline/parquet_features.html
Source code with documentation:
https://github.com/RedHatInsights/insights-data-schemas/blob/master/docs/internal-pipeline/parquet_features.md


Bound map size in kMap

This is done in the fast paths already.

this PR has broken github

this PR has broken github

this PR has broken github

Diff looks fine now, I assume it worked for you since you approved!


CEO-359 Numerous small text changes and style clean ups.

Purpose
Numerous small text-based changes have been made:

The terms of service link when creating a new institution is fixed.
The terms of service link when creating a new project is fixed.
The Planet Daily and Monthly "click here for help" links (when creating new imagery) is fixed.
Added a useful message to the institution dashboard when there are no projects.
Reverted a dev_data.sql change.
Changed the unicode carets for an Institution to SVGs.
Capitalized the word "membership" in the "Request Membership" button.
Changed "Create New Institution" to be "Edit Institution" when editing an existing institution.
Changed the text under the Projects tab when there are no projects from "There are no projects" to "There are no projects yet. If you are an Admin click "Create New Project" to get started."
Fixed the spacing on the message that pops up when User-Drawn samples are enabled for the quality control tab.
Fixed the spacing between "circleplot" and "squareplot" in the Collection Map Preview.

Related Issues
Closes CEO-359
Submission Checklist

[x] Included Jira issue in the PR title (e.g. CEO-### <title>)
[x] Code passes linter rules (npm run eslint/clj-kondo --lint src)

Screenshots
Institution toggle button before (unicode):

Institution toggle button after (svg):

Fixed the spacing on "circleplot":

Changed "Create New Institution" to be "Edit Institution" when editing an existing institution:

Added a useful message to the institution dashboard when there are no projects:

Fixed the spacing on the message that pops up when User-Drawn samples are enabled for the quality control tab:

src/js/home.js
532, this needs to be a div.   should only be used for text with alternate styling.  span should not have any children.
534, use flex if possible for the alignment
553, use padding / margin instead of the space char for edge spacing.
src/js/institutionDashboard.js
90, use padding / margin instead of the space char for edge spacing.
92, Unfortunately its not enough to check for an empty project list.  If the user is not a member, and there are no public projects, they will also see no projects.
src/js/reviewInstitution.js
1071, use padding / margin instead of the space char for edge spacing.
92, Unfortunately its not enough to check for an empty project list.  If the user is not a member, and there are no public projects, they will also see no projects.
1444, use padding / margin instead of the space char for edge spacing.
With both of your empty project messages, you may be able to make the message generic enough not to need new logic.

src/js/reviewInstitution.js
1047, This structure leads to a more nesting that you need.
1048, No lets allowed form our team. Aside from that, there is no reason for a variable here, as you are not really mutating anything.
1049, Un nest this.
1058 This is not really the use case for switch. Use if / else here.
1058-1078, this can stay as a function.  Use ES6 arrow function for consistency.


Add subscript and subscript markdown tokens

Uses ^^ for superscript and ^^^ subscript as wrappers in the same
pattern as italics and bold ( * and **, respectively)
Adds editor hot-keys and syntax highlighting. (CTRL-6/CTRL-7)
Exact values may not be ideal. Short of the suggested overloading of ~,
I didn't see a better option for the delimiter.
Solves Issue #2171

There's probably room for discussion, but I would vote for single ^ and double ^^ rather than double and triple.
Otherwise I agree this is probably the cleanest approach without overriding things.

One concern is that maybe single pairs would break some brews, if they are using the symbols? I think it’s fairly low chance of that.

One concern is that maybe single pairs would break some brews, if they are using the symbols? I think it’s fairly low chance of that.

Probably low chance, but we can also be specific with our syntax that you can't allow blank spaces on the end or start, which I think would account for most cases:
i.e.:
^some text^ is valid, but ^ some text^  and ^some text ^ are not.

Also, should we account for Long strings of ^^^^^^^^^^^Some text^^^^^^^^^^^? Is that multiple supers or multiple subs?

One concern is that maybe single pairs would break some brews, if they are using the symbols? I think it’s fairly low chance of that.

That was the assumption I made, that it was plausible for there to be a line that contained two unrelated carets and could trigger a false match.

One concern is that maybe single pairs would break some brews, if they are using the symbols? I think it’s fairly low chance of that.

One possible use case is where someone is using ^ as a footnote marker for cells in a table, like this:
...
|**Text**| More text^| Would you believe it^ | And Again* | ... |
...
`^` special note numero uno
`*` another special note

One possible use case is where someone is using ^ as a footnote marker for cells in a table, like this:

Fortunately, the contents of each table cell is evaluated individually, so there is no risk of "cross-cell" problems like this. (The syntax highlighting is still there, but the tables are not an issue in the output:

That was the assumption I made, that it was plausible for there to be a line that contained two unrelated carets and could trigger a false match.

I think we are pretty safe that this won't happen. Maybe in a couple of very rare cases.

I'm finally getting around to merging this! Just did a small bit of cleanup and I think it's ready. 👍
Thanks @dbolack-ab ! 💯 🎉 ⭐


Deeplink failed to pass the Query Params

We are invoking the task module via Adaptive Card's task/fetch as well as via deep_link.
In the case of task/fetch, things are working as expected, but for the deep-link, we are not able to get the query params:
Url which we are passing:
https://c5d3-2405-201-5c0a-a025-3507-9541-abcd-1234.ngrok.io//card-links/1431/web_view.html?sample_data=123&agent_id=8
Here is the part of JSON which we are building for deep link:
...
 {

 "type": "Action.OpenUrl",
 "url":  "https://teams.microsoft.com/l/task/4c4bc977-07b2-4f26-bf74-de6dcfece674?url=https://c5d3-2405-201-5c0a-a025-3507-9541-abcd-1234.ngrok.io/card-links/1431/web_view.html?sample_data=123&agent_id=8&height=500&width=500&title=wer-view-html&agent_id=8"

 }
 ...

On clicking that button, the task module opens up, but we are not able to see any content, and this is what we got on the server:
Started GET "//card-links/1429/web_view.html?sample_data" for 2405:201:5c0a:a025:91f6:a0ae:a25b:c41a at 2021-11-18 14:23:02 +0530

I had tried to bind the URL part with the single quotes as well, but that also didn't worked.
sample JSON:
...
 {

 "type": "Action.OpenUrl",
 "url":  "https://teams.microsoft.com/l/task/4c4bc977-07b2-4f26-bf74-de6dcfece674?url=`https://c5d3-2405-201-5c0a-a025-3507-9541-abcd-1234.ngrok.io/card-links/1431/web_view.html?sample_data=123&agent_id=8`&height=500&width=500&title=wer-view-html&agent_id=8"

 }
 ...

You can see that after sample_data rest of the things got vanished. Just wanted to know Is there any way we can pass query params with a deep link?

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

ID: 55c5e4a1-6116-ec92-36e9-b94097bd83c7
Version Independent ID: fd843eef-73e2-7a7e-9ac4-5c20fcf1fa2f
Content: Invoke and dismiss task modules - Teams
Content Source: msteams-platform/task-modules-and-cards/task-modules/invoking-task-modules.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: lajanuar

@Chang025 - We are looking into this I will get back to you soon.

@Chang025 - Please have a look at this doc - https://adaptivecards.io/explorer/Action.OpenUrl.html .
https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/task-modules/invoking-task-modules#task-module-deep-link-syntax
Let us know if you have any query.

hey @sayali-MSFT - Thank you for the quick response.
I have gone through the docs, the first doc is more of a general Action.OpenUrl thing and in the second doc, there is no place where it is written that the TaskInfo.url property does not support query params for deep_link.
reference from docs: https://teams.microsoft.com/l/task/APP_ID?url=<TaskInfo.url>&height=<TaskInfo.height>&width=<TaskInfo.width>&title=<TaskInfo.title>&completionBotId=BOT_APP_ID
I need to send TaskInfo.url along with the query parameters, something like:
TaskInfo.url:  https://adaptivecards.io?my_custom_param1=abcd&my_custom_param2=123
Can you please confirm that deep_link's url attribute does not support query params?
or just bring my attention to how we can pass the query params which will require later on our server.

@Chang025 - Deeplink  url attribute is support query params. I tryouts with above syntax. it's working on our end.
Sample Link:-
https://teams.microsoft.com/l/task/bc6fb7f5-5824-44c6-9a08-38c3a211XXXX?url=https://adaptivecards.io?my_custom_param1=abcd&my_custom_param2=123&height=500&width=500&title=wer-view-html&completionBotId=bc6fb7f5-5824-44c6-9a08-38c3a211XXXX

@sayali-MSFT - Thanks for the sample URL, I'll check that again at our side and if needed then I'll re-open this issue again.


No spec for EDM:Action

There doesn't seem to be any defintion for OData Actions listed here. Is this an oversight or intended?

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

ID: 8b86196e-11c3-ee18-2019-81de165f7892
Version Independent ID: 449aab8b-497c-8cdc-3bb0-1a549c7340dc
Content: CSDL Specification - EF6
Content Source: entity-framework/ef6/modeling/designer/advanced/edmx/csdl-spec.md
Product: entity-framework
Technology: entity-framework-6
GitHub Login: @ajcvickers
Microsoft Alias: avickers

Thank you for requesting a change to the EF6 documentation. We are prioritizing improvements to the EF Core documentation and at this time we are not making changes to the EF6 documentation.
However, we will consider well-written community pull requests to improve the EF6 documentation. The documentation source is located in the EntityFramework.Docs repository on GitHub. To submit a pull request:

Find the file to update and click on it to open

Click on the edit button (✏) to edit in your web browser

When done, add a title and description, then use the "Create a new branch and start a pull request." option.

(Note that you can also clone the docs repo and do a GitHub PR in the normal way.)


HAWQ-1591 Common tuple batch structure for VecExe

Define TupleBatchData struct to hold a batch of tuples through vectorized execution process.

LGTM


Greetings

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Greetings such like in Lawnchairs V2's at a glance native widget.
EG: "Good morning!" in morning
"Have a good day!" in afternoon
"Charge your phone" when low battery
"Sleep well" at night
"Don't go to bed too late" at very late night
Things like this :)
Describe alternatives you've considered
Going back to Lawnchair
Additional context
https://i.imgur.com/lbmvw14.jpg
https://i.imgur.com/taE498v.jpg

It would be nice. And it would also be nice to have new providers to show other types of informations. :)

Hi there, this could be a really good idea but I think that it'll be very hard to support with partial language support.

Hi there, this could be a really good idea but I think that it'll be very hard to support with partial language support.

Maybe you can make it change during the day (morning, noon, evening, night) like on Apple lockscreens.
For each period, you can make a random greeting that display one of the few messages that you already wrote.
Example for Morning:

Good morning!
Did you sleep well?
Have a nice day!
Rise and shine! Today is a sunny day. (related to weather)
Do you want to build a snowman? (related to weather)

I've just added the Greetings as a Glance provider in the latest beta.
Everyone could add some string resources in each language file and they will be shown randomly.


bool.Equals() function fails

This one is really easy to work around but worth reporting anyways.  Normally nobody would do this, but I saw this when converting an Nunit test.  Somebody used AreEquals(false, func(xxxx)) which wound up calling an overload that takes 2 objects in my replacement function (which then used .Equals()).
Reproduction boils down to these lines:
        bool a = true;
        bool b = false;
        Console.WriteLine("Got here 1");
        bool c = a.Equals(b);   // Script error
        Console.WriteLine("Got here 2");

Actually it looks like the problem is with any var type and with object assigned to null.

Duplicate of #241 it appears.

Really here case a little bit different from #241, as we have here have problem with method of IEquatable<bool> interface.
When fixing it, IComparable interface should also be checked. This issue is still open, but simple fix for it will be just add bool proxy:
    [JSProxy(typeof(Boolean))]
    public abstract class BooleanProxy
    {
        [JSReplacement("JSIL.ObjectEquals($this, $obj)")]
        public abstract bool Equals(bool other);
    }

But before resolving it will be a good idea to test executing method through interface reference on it.


Return expected keys from database summary

Coverage remained the same at 100.0% when pulling c2ce808bd5b61d6bc174ef503fa6218aecd39ae0 on summary-features into 848aaa7e982c33993c48f671f37290f9b56fbcb2 on master.


python3Packages.pydeconz: 86 -> 87

Motivation for this change
https://github.com/Kane610/deconz/releases/tag/v87
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Picked into my home-assistant branch.


Mouse wheel zoom zooms from center

In my opinion, using the mouse wheel should scroll relative to the cursor position instead of in the center.

Hey @allanburleson - thanks for checking in. Completely agree on this expected behaviour!
Workaround for now:
the map centers on click, so click & mouse wheel will bring you where you'd like to zoom.
Cheers!


vim and tag not found…

Hi, VIm support tags → good, but something is missing

my tags file

> grep self_test tags
self_test       backend/backendConnector.cpp    /^bool BackendConnector::self_test()$/;"        f       class:xmrstak::BackendConnector signature:()
self_test       backend/nvidia/minethd.cpp      /^bool minethd::self_test()$/;" f       class:xmrstak::nvidia::minethd  signature:()
xmrstak::BackendConnector::self_test    backend/backendConnector.cpp    /^bool BackendConnector::self_test()$/;"        f       class:xmrstak::BackendConnector signature:()
xmrstak::nvidia::minethd::self_test     backend/nvidia/minethd.cpp      /^bool minethd::self_test()$/;" f       class:xmrstak::nvidia::minethd  signature:()

my code

bool BackendConnector::self_test()
{
    bool    ret;
    ret =   cpu::minethd::self_test();
#   ifndef CONF_NO_CUDA
    ret &=  nvidia::minethd::self_test();
#   endif
    return ret;
}

as you see, self_test has multiple definitions… and as you see the definition nvidia::minethd::self_test is valid but vim seems NOt be able to match the substring nvidia::minethd::self_test with the entry xmrstak::nvidia::minethd::self_test from the ctags file
I find ALL ctags entries if I search for self_test or NO ctags entries if I search for nvidia::minethd::self_test
my simple question is… why ?

If I understand correctly this can be solved by using a pattern :tag /nvidia::minethd::self_test

@EgZvor I have the same problem.
It works perfectly when I use pattern search, but it doesn't when I use ^] keybinding under the cursor.

@korney4eg ^] is using the word under cursor if your settings of iskeyword is default you only search self_test, so I'm not sure what exact problem you're having. The reason for different results when matching self_test vs nvidia::minethd::self_test is in the former case Vim is using name field and in the latter pattern field. In both cases it is matched strictly, that's why you don't get anything in the latter case, you'd need to use xmrstak::nvidia::minethd::self_test instead. And if you want your search to be not strict you have to use / in any of the :tag commands.

Thanks for the answer @EgZvor  now I found where I can get an issue.
I needed to fix my ctags configuration.


Add browser load monitoring servlet

Add GridStatistics servlet to monitor browser load
Add maximum instances of every browser type in response
Add number of requests waiting on queue per browser type in response
Add support for JSON responses
Add supporting classes BrowserInformationCache and BrowserStatisticsCollection
Include GridStatistics servlet in hubConfig.json

The response body seems to always be surrounded by quotes "..
For example;
"[]"

"[{\"browserName\":\"chrome\",\"statistics\":{\"waitingRequests\":0,\"maxBrowserInstances\":10}},{\"browserName\":\"firefox\",\"statistics\":{\"waitingRequests\":0,\"maxBrowserInstances\":15}}]"

This should not be the case

This PR needs some @Test code for it.

@kumaravel-jayakumar Thanks for this! I made a few minor changes and I think the code looks good now. I will squash and merge this soon, assuming the Travis CI and Codacy checks come back green


Remove hub code

Description

This PR removes any dependency on the hub api in napari.  While working on #5198, it was decided to go ahead and remove this code.

Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

@ppwadhwa I agree with Draga. Could you please also clean pointed places?

As Draga's request has been made, I will merge tomorrow if there are no objections.


Make for target 'build-patcher-spike' failed

After meeting prerequisites, I execute make -j40. However, I got the error message as follows：

I check the related files and find that the function cfg_t::cfg is called in pspike/psike.cc with 12 arguments provided:

But the candidate function in my pre-built Spike expects 13  arguments:

It seems that the call for cfg_t::cfg in pspike/psike.cc missing the const char * default_priv argument. Could you please help me solve the problem?

We're using some unstable API, so it changes from time to time, please check build-and-test.yml file to use a specific version of spike.

We're using some unstable API, so it changes from time to time, please check build-and-test.yml file to use a specific version of spike.

Thanks, it works.
However, When I change the mode to ‘user’, I get stuck in the tests_patch step, such as
LD_LIBRARY_PATH=/riscv_toolchains/lib build/pspike --isa=rv64gcv --varch=vlen:256,elen:64 /riscv_toolchains/riscv64-unknown-elf/bin/pk out/v256x64user/bin/stage1/vaadd.vv-0 > out/v256x64user/patches/stage2/vaadd.vv-0.patch
I get the error message:
*** FAILED *** (tohost = -1073707433)
*** FAILED *** (tohost = -1073707433)

That's strange. out/v256x64user/bin/stage1/vaadd.vv-0 is not supposed to have this many test cases. The last few lines on my side are:
  TEST_CASE(2111, t0, 0xffffffffffffc000, ld t0, 0(a0); addi a0, a0, 8)
  TEST_CASE(2112, t0, 0xa989e5f32751c914, ld t0, 0(a0); addi a0, a0, 8)
  TEST_CASE(2113, t0, 0xffffffffbfffc000, ld t0, 0(a0); addi a0, a0, 8)
---

Are you sure you're using the latest main without any changes?

Then I don't know why, the "patch" stage works fine on my side. Spike with pk is indeed a bit unstable for reasons I don't know, but the errors only happen at the later "merger" stage on my side, retrying a few times will get a successful build.

Closed for long periods of inactivity.


Failed to decode downloaded font

After updating Ember CLI to 2.4.0
DEBUG: -------------------------------
DEBUG: Ember      : 2.4.1
DEBUG: Ember Data : 2.4.0+9f8c40927a
DEBUG: jQuery     : 2.2.1
DEBUG: ------------------------------
In Chrome Inspector's console I am getting (edit: same in Firefox):

Failed to decode downloaded font: http://localhost:4200/fonts/fontawesome-webfont.woff2?v=4.5.0
OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
Failed to decode downloaded font: http://localhost:4200/fonts/fontawesome-webfont.woff?v=4.5.0
OTS parsing error: incorrect file size in WOFF header
Failed to decode downloaded font: http://localhost:4200/fonts/fontawesome-webfont.ttf?v=4.5.0
OTS parsing error: incorrect entrySelector for table directory

And the icons do not appear.

This is an issue with Ember CLI: https://github.com/ember-cli/ember-cli/issues/5538

thanks!


Cannot find module 'kinvey-nativescript-sdk/push'

Hey all,
A problem came up on the NativeScript forum that I was able to verify. Seems like the push module that the Kinvey push documentation says to use is not published with the plugin.
Steps to Reproduce

Start a new NativeScript app and install the Kinvey {N} SDK.
Add the following import to any file.

import { Push } from 'kinvey-nativescript-sdk/push';

Expected Result
No TypeScript errors.
Actual Result
The following TypeScript error.
Cannot find module 'kinvey-nativescript-sdk/push'.

Version of Kinvey NativeScript SDK
3.9.3
NodeJS version
6.11.4

@tjvantoll thanks for the bug report. I am seeing the problem as well. We'll have an update soon.

This has been fixed in https://github.com/Kinvey/js-sdk/pull/171 and will be available in the next release. I will update this issue when the new release is available.

@nikola6789 @tjvantoll This was fixed with the release of version 3.9.4.

I'm still seeing this in 3.11.1

Ok. We are fixing some other issues related to Push this sprint. We will take a look while we are fixing these issues. Expect a fix at the end of next week. I will update here when this fix is released.

Hi @thomasconner any update on this? :)

The Push module is available an can be accessed with
import { Push } from 'kinvey-nativescript-sdk/push';

but there is another issue that is causing push to not work and will need to be fixed. Right now I don't have a time estimate for that fix but it is something that is priority for us to fix.

I do have
import * as Kinvey from 'kinvey-nativescript-sdk';
import { Push } from 'kinvey-nativescript-sdk/push';

and I still get:
error TS2307: Cannot find module 'kinvey-nativescript-sdk/push'.

with version (from package.json): "kinvey-nativescript-sdk": "^3.11.1"

+1

Hey @thomasconner with 3.11.1 isn't the Push class just exposed in the kinvey-nativescript-sdk itself and not via the sub directory? I looked into the module and the push files (android & ios) are just in the root of the module. So for now I'm trying import * as Kinvey from ... and using Kinvey.Push... to access the methods in the Push. I have not confirmed that this works yet, having some local build/device issues with my android device at the moment.

Hey @bradmartin. 3.11.1 should have the Push class exposed as a separate module accessed by kinvey-nativescript-sdk/push and not at kinvey-nativescript-sdk. It looks like there might be an issue where it is available but the TypeScript definitions file has not been updated which is causing the error error TS2307: Cannot find module 'kinvey-nativescript-sdk/push'. I will try and fix the TypeScript definition file to see if that resolves the issue.
cc: @finger563 @nikym23

@thomasconner - yep you're right, was finally able to test that and while the typings pass, it's not valid like you mentioned 👍
Wouldn't just putting the push files into a sub directory /push along with a typings file fix this issue?

Also, I'm referring to the NS SDK having this done here https://github.com/Kinvey/nativescript-sdk and not the monorepo for all the kinvey-js projects 👍

Has any fix for this been pushed? specifically related to .register failing?

No there has not been a fix pushed at the moment. It is scheduled to be fixed in this sprint.

This has been fixed with 3.11.5 release.


Full set of attributes for Lovelace Card

@mykhailog might need to check I've used all the right units of measurements, and there might be some icon tweaking needed, but providing this as a starting point if anyone wants to add the sensor attributes to their overview dashboard or similar.
I added the following to my configuration.yaml:
sensor:
  - platform: waveshare_ups_hat

binary_sensor:
  - platform: waveshare_ups_hat`

template:
    - sensor:
        - name: UPS Capacity
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'capacity' )}}"
          unit_of_measurement: '%'
          icon: mdi:battery-unknown
        - name: UPS PSU Voltage
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'psu_voltage' )}}"
          unit_of_measurement: 'v'
          icon: mdi:lightning-bolt
        - name: UPS Load Voltage
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'load_voltage' )}}"
          unit_of_measurement: 'v'
          icon: mdi:lightning-bolt
        - name: UPS Shunt Voltage
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'shunt_voltage' )}}"
          unit_of_measurement: 'v'
          icon: mdi:lightning-bolt
        - name: UPS Current
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'current' )}}"
          unit_of_measurement: 'mA'
          icon: mdi:current-dc
        - name: UPS Power
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'power' )}}"
          unit_of_measurement: 'W'
          icon: mdi:power-plug
        - name: UPS Power Calculated
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'power_calculated' )}}"
          unit_of_measurement: 'W'
          icon: mdi:power-plug
        - name: UPS Charging
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'charging' )}}"
          unit_of_measurement: ''
          icon: mdi:battery-charging
        - name: UPS Online
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'online' )}}"
          unit_of_measurement: ''
          icon: mdi:battery-charging-100
        - name: UPS Low Battery
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'low_battery' )}}"
          unit_of_measurement: ''
          icon: mdi:battery-low

yes, it looks good. The only one fix is to change 'v' to 'V'

Good spot, fixed

@mykhailog might need to check I've used all the right units of measurements, and there might be some icon tweaking needed, but providing this as a starting point if anyone wants to add the sensor attributes to their overview dashboard or similar.
I added the following to my configuration.yaml:
sensor:
  - platform: waveshare_ups_hat

binary_sensor:
  - platform: waveshare_ups_hat`

template:
    - sensor:
        - name: UPS Capacity
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'capacity' )}}"
          unit_of_measurement: '%'
          icon: mdi:battery-unknown
        - name: UPS PSU Voltage
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'psu_voltage' )}}"
          unit_of_measurement: 'V'
          icon: mdi:lightning-bolt
        - name: UPS Load Voltage
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'load_voltage' )}}"
          unit_of_measurement: 'V'
          icon: mdi:lightning-bolt
        - name: UPS Shunt Voltage
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'shunt_voltage' )}}"
          unit_of_measurement: 'V'
          icon: mdi:lightning-bolt
        - name: UPS Current
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'current' )}}"
          unit_of_measurement: 'mA'
          icon: mdi:current-dc
        - name: UPS Power
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'power' )}}"
          unit_of_measurement: 'W'
          icon: mdi:power-plug
        - name: UPS Power Calculated
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'power_calculated' )}}"
          unit_of_measurement: 'W'
          icon: mdi:power-plug
        - name: UPS Charging
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'charging' )}}"
          unit_of_measurement: ''
          icon: mdi:battery-charging
        - name: UPS Online
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'online' )}}"
          unit_of_measurement: ''
          icon: mdi:battery-charging-100
        - name: UPS Low Battery
          state: "{{ state_attr('sensor.waveshare_ups_hat', 'low_battery' )}}"
          unit_of_measurement: ''
          icon: mdi:battery-low

I added template sensor to HA configuration.yaml but I sensors are still as unknown.
Could you help to solve this?
thx


Can I hide specific majorTicks on a gauge, so that only a few are visible?

I have a gauge that I am working on and my client wants to only show a few of the majorTicks on the gauge. I know that I will need entries x10 to 100 to make a gauge that functions appropriately. can I use something like a CSS call to hide the specific majorTick? ie. '10'{this.css('visibility, 'transparent')}? Any hint would be nice!

Hi. Gauge is drown on a canvas, so it's a bitmap and does not have any relation to CSS. As a result there is no way to hide specific ticks unless changing drawing algorithm itself. So within core implementation it is currently not possible.

Hi Mikhus, thanks for the reply. I probably used CSS when I did not need to. I looked more deeply in your code and I found that the config changes all of the Major ticks and not just one. I understand that it would be difficult to extend the config on the "strokeStyle" of the majorTicks (ctx.strokeStyle = config.colors.majorTicks;). What if I wanted to do something like the following:
majorTicks: [{tick:'0', color:'#000000'}, '10', '20', '30', '40', '50', '60', '70', '80', '90', '100'],
Could I extend your library to change the configuration? I would prefer not to change the code in gauge.js, however maybe I could create a "plugin" of sorts that could extend it and apply what I am describing?
I think you have done an excellent job of making these gauges possible using html5 canvas! Very very cool stuff, keep up the great work!

It is opensource under MIT license, so, please, feel free to do any modifications. There is no limits, so you can fork, modify and pull your changes. All that is highly appreciated!

This feature will be added in upcoming release 2.0.4. It will be possible to specify specific colors for major ticks and tick numbers separately as arrays of colors instead of a single color value. For example:
<canvas data-type="radial-gauge"
               data-major-ticks="0,50,100,150,200"
               data-color-numbers="transparent,red,green,blue,black"
               data-color-major-ticks="black,red,green,blue,black"
></canvas>


Split testing steps into functions

Summary

Split testing steps into functions so they can be callable as wanted.
Changes

Moved testing steps in seperate files with functions under libs
Testing

Manually tested.
Possible Regressions

Checklist

[x] Read the contributions page.
[x] Submitted the CLA form, if you are a first time contributor.
[x] The introduced changes are covered by unit and/or integration tests.

Notes

Thank you for this PR @berkayoz could we have a way to call each test on its own from test-distro.sh? The end goal was/is to have each test in its own jenkins stage.

Thank you for this PR @berkayoz could we have a way to call each test on its own from test-distro.sh? The end goal was/is to have each test in its own jenkins stage.

Thanks for the review @ktsakalozos
You are correct, the end goal is to have each test suite in its own stage. However for better visibility, we can also put each part of the suite for example setup_test_addons, test_core_addons, post_test_addons into separate jenkins steps and call them like
sh '''
  #!/usr/bin/env bash
  source tests/libs/addons.sh
  post_test_addons
'''

sh '''
  #!/usr/bin/env bash
  source tests/libs/addons.sh
  test_core_addons
'''

sh '''
  #!/usr/bin/env bash
  source tests/libs/addons.sh
  post_test_addons
'''

This will help with identifying which step has failed in a testing suite without requiring us to do digging through logs since the jenkins ui will highlight it directly. We probably can parse this data easier to view our performance/standing in tests.
There is some additional work required for this, which is parameterizing the functions instead of environment variables since steps don't share environments. Once a step is done, the environment is cleared. But we can use Jenkins variables to share and manage things like lxd container names we use.


Feature request: autocomplete for import

When typing inside import, there should be autocomplete containing all libraries that have been installed.

I'm gonna take a stab at implementing this.

Good luck, I would start from here: https://github.com/nsf/gocode/blob/master/cursorcontext.go#L272
You need to figure out somehow that the cursor is on the import clause. Maybe do some sort of reverse parsing. This function above actually does tokenize code, but you should take care about a common case when string literal isn't valid, e.g.:
package main
import (
  "io/
)

In this case tokenizer may actually fail. But there are hacks to avoid that, you can try detecting if amount of quotes before the cursor is odd (be careful about possible quotes in comments) and insert a quote after the cursor. All sorts of hacks may work. It's definitely possible to do a solid context detection here, but may take some time.

@nsf thanks.


Add PyroRL

Insert URLs to the project here: https://github.com/sisl/PyroRL

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All new projects listed will be posted on our Mastodon channel.

@cpondoc @joey-obrien


Move from Sidekiq to solid_queue

We don't need fast processing of jobs. solid_queue works fine for our usecase.
This will also help us drop the upstash/redis requirement that we currently have

@apoorv1316 is this all done, if yes, please close cc @keshavbiswa


e2e: rmsched -> schedrst

Tests that restart the scheduler actually remove the scheduler pod but not the scheduler, and tests that remove the scheduler CR and recover are restarting the scheduler.
Both versions delete the scheduler logs which are essential for troubleshooting if needed.
Replace the rmsched tag with a tag that better reflects the effect of tests under this go file.

/approve
/lgtm


Cannot see route which blocks deleting service

I have added some service, and route associated with this service.
I wanted to delete service but I obtain the following error

{
"fields": {
"@referenced_by": "routes"
},
"name": "foreign key violation",
"code": 4,
"message": "an existing 'routes' entity references this 'services' entity"
}

I cannot find route which blocks this operation. I cannot see it using admin API GET command neither via Admin GUI (I am using kong enterprise edition).
How can I delete this service  and "ghost" route?

@mirkoszy You can list the routes associated with a service using GET /services/{service_name_or_id}/routes. Do you see any routes listed on that endpoint?
Also, which version of Kong Enterprise are you using?

I think i have same issue. I'm using 0.34-1-enterprise-edition by Docker and can't see all the routes in GUI. I'm checking logs from docker. This is the logs.
2019/05/07 06:29:19 [error] 55#0: *18623224 lua coroutine: runtime error: /usr/local/share/lua/5.1/kong/core/handler.lua:139: attempt to compare number with userdata
stack traceback:
coroutine 0:
        [C]: in function 'sort'
        /usr/local/share/lua/5.1/kong/core/handler.lua:134: in function 'build_router'
        /usr/local/share/lua/5.1/kong/api/routes/routes.lua:86: in function 'rebuild_routes'
        /usr/local/share/lua/5.1/kong/api/routes/routes.lua:102: in function </usr/local/share/lua/5.1/kong/api/routes/routes.lua:101>
<IP_ADDRESS> - - [07/May/2019:06:29:19 +0000] "GET /default/routes?size=100 HTTP/1.1" 500 54 "http://<IP_ADDRESS>:8002/default/routes" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36"
coroutine 1:
        [C]: in function 'resume'
        /usr/local/share/lua/5.1/lapis/application.lua:393: in function 'handler'
        /usr/local/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
        /usr/local/share/lua/5.1/lapis/application.lua:161: in function </usr/local/share/lua/5.1/lapis/application.lua:159>
        [C]: in function 'xpcall'
        /usr/local/share/lua/5.1/lapis/application.lua:159: in function 'dispatch'
        /usr/local/share/lua/5.1/lapis/nginx.lua:215: in function 'serve_admin_api'
        content_by_lua(nginx-kong.conf:304):2: in function <content_by_lua(nginx-kong.conf:304):1>, client: <IP_ADDRESS>, server: kong_admin, request: "GET /default/routes?size=100 HTTP/1.1", host: "<IP_ADDRESS>:8001", referrer: "http://<IP_ADDRESS>:8002/default/routes"
2019/05/07 06:29:19 [error] 55#0: *18623224 [lua] init.lua:146: handle_error(): /usr/local/share/lua/5.1/lapis/application.lua:397: /usr/local/share/lua/5.1/kong/core/handler.lua:139: attempt to compare number with userdata
stack traceback:
        [C]: in function 'sort'
        /usr/local/share/lua/5.1/kong/core/handler.lua:134: in function 'build_router'
        /usr/local/share/lua/5.1/kong/api/routes/routes.lua:86: in function 'rebuild_routes'
        /usr/local/share/lua/5.1/kong/api/routes/routes.lua:102: in function </usr/local/share/lua/5.1/kong/api/routes/routes.lua:101>

stack traceback:
        [C]: in function 'error'
        /usr/local/share/lua/5.1/lapis/application.lua:397: in function 'handler'
        /usr/local/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
        /usr/local/share/lua/5.1/lapis/application.lua:161: in function </usr/local/share/lua/5.1/lapis/application.lua:159>
        [C]: in function 'xpcall'
        /usr/local/share/lua/5.1/lapis/application.lua:159: in function 'dispatch'
        /usr/local/share/lua/5.1/lapis/nginx.lua:215: in function 'serve_admin_api'
        content_by_lua(nginx-kong.conf:304):2: in function <content_by_lua(nginx-kong.conf:304):1>, client: <IP_ADDRESS>, server: kong_admin, request: "GET /default/routes?size=100 HTTP/1.1", host: "<IP_ADDRESS>:8001", referrer: "http://<IP_ADDRESS>:8002/default/routes"

I am using version 0.34. I tried to list the routes associated with that service and there is no route.

In my case, after i create a second new route with GUI, routes just gone. I re-installed the server because of this issue and same problem occurred again.

I cannot delete deployment, especially cassandra DB. Do you have any idea how to solve this issue?

In 0.34 there is the concept of workspaces, and there is a workspace_entities table that contains references to the entities and their workspaces. Since kong does not use transactions, there is the possibility that a record in this table was orphaned. There is a row created in the workspace_entities table for each unique field an entity contains.
You can check the contents of the table with the following Admin API endpoint (assuming you did not specify some other workspace):
:8001/workspaces/default/entities
If you compare the uuid's for the routes in this table with what is found in your routes table, you can clean up the orphans with a DELETE request like:
:8001/workspaces/default/entities/<UUID>
Hopefully this helps.

It sounds like you may have the opposite problem from the one I described. The consumer or route entity got left behind when the workspace entities entry was deleted. This would prevent you from seeing the route in the admin api. You will have to go into your database and find the consumer where username='foo' or routes where service_id =  and remove them from the consumers and routes table.

As this seems to be relating to Kong Enterpise, I will close this. If you can provide a way we can reproduce it on Kong, please reopen.


az functionapp config container set fails

Describe the bug
I am unable to set a container image to function apps using Azure CLI. The function app is under "Container Apps Environment". I am able to do the same using portal, just that it won't work in CLI. The error is  "Internal Server Error", doesn't provide much information as well.
Related command
az functionapp config container set --docker-custom-image-name .azurecr.io/:4338e0ec91f0bb3216e4 --docker-registry-server-password  --docker-registry-server-url https://.azurecr.io --docker-registry-server-user  --name  --resource-group
Errors
Operation returned an invalid status 'Internal Server Error'
Content: {"Message":"An error has occurred."}
Issue script & Debug output
urllib3.connectionpool: https://management.azure.com:443 "PUT /subscriptions//resourceGroups//providers/Microsoft.Web/sites//config/appsettings?api-version=2022-03-01 HTTP/1.1" 500 36
cli.azure.cli.core.sdk.policies: Response status: 500
cli.azure.cli.core.sdk.policies: Response headers:
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Length': '36'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'Server': 'Microsoft-IIS/10.0'
cli.azure.cli.core.sdk.policies:     'X-AspNet-Version': '4.0.30319'
cli.azure.cli.core.sdk.policies:     'X-Powered-By': 'ASP.NET'
cli.azure.cli.core.sdk.policies:     'x-ms-failure-cause': 'service'
cli.azure.cli.core.sdk.policies:     'x-ms-ratelimit-remaining-subscription-writes': '1199'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': '7d1eeaf6-1d3d-4aa8-ab54-143b6422f61c'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': '7d1eeaf6-1d3d-4aa8-ab54-143b6422f61c'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'WESTUS:20240107T210608Z:7d1eeaf6-1d3d-4aa8-ab54-143b6422f61c'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'Date': 'Sun, 07 Jan 2024 21:06:08 GMT'
cli.azure.cli.core.sdk.policies:     'Connection': 'close'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"Message":"An error has occurred."}
cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 464, in update_application_settings_polling
_generic_settings_operation(cmd.cli_ctx, resource_group_name, name,
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/appservice/_appservice_utils.py", line 33, in _generic_settings_operation
return operation(resource_group_name, name, setting_properties)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/core/tracing/decorator.py", line 78, in wrapper_use_tracer
return func(*args, **kwargs)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/mgmt/web/v2022_03_01/operations/_web_apps_operations.py", line 18341, in update_application_settings
raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)
azure.core.exceptions.HttpResponseError: Operation returned an invalid status 'Internal Server Error'
Content: {"Message":"An error has occurred."}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 663, in execute
raise ex
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 726, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 697, in _run_job
result = cmd_copy(params)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 333, in call
return self.handler(*args, **kwargs)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
return op(**command_args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 1783, in update_container_settings_functionapp
return update_container_settings(cmd, resource_group_name, name, registry_server,
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 1761, in update_container_settings
update_app_settings(cmd, resource_group_name, name, settings, slot)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 438, in update_app_settings
update_application_settings_polling(cmd, resource_group_name, name, app_settings, slot, client)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 477, in update_application_settings_polling
raise CLIError(ex)
knack.util.CLIError: Operation returned an invalid status 'Internal Server Error'
Content: {"Message":"An error has occurred."}
cli.azure.cli.core.azclierror: Operation returned an invalid status 'Internal Server Error'
Content: {"Message":"An error has occurred."}
az_command_data_logger: Operation returned an invalid status 'Internal Server Error'
Content: {"Message":"An error has occurred."}
Expected behavior
Sets a container image to the function app
Environment Summary
azure-cli                         2.55.0
core                              2.55.0
telemetry                          1.1.0
Extensions:
ai-examples                        0.2.5
ml                                2.22.0
ssh                                2.0.2
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location '/usr/bin/python3.9'
Extensions directory '/home/sridharan/.azure/cliextensions'
Extensions system directory '/usr/lib/python3.9/site-packages/azure-cli-extensions'
Python (Linux) 3.9.14 (main, Oct 12 2023, 19:48:32)
[GCC 11.2.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response

Thank you for opening this issue, we will look into it.

Any update on this?

Hi @sridharvenkat We are currently investigating this issue and we will get back to you on this. Thank you for your patience.

Hi @sridharvenkat you need to use below parameters such as --image, --registry-password, --registry-username to update the image in cli . (refer this doc link -https://github.com/Azure/azure-functions-on-container-apps?tab=readme-ov-file#update-function-container-image)
az functionapp config container set --image /<image_name>: --registry-password   --registry-username  --name  --resource-group
The current parameters used in your cmdlet are deprecated (https://learn.microsoft.com/en-us/cli/azure/functionapp/config/container?view=azure-cli-latest#az-functionapp-config-container-set)

@sridharvenkat  - can you please look into the acr image name as well , it seems incorrect. https://.azurecr.io  https:// is not required. Can you try below format highlighted

Hi @sridharvenkat Just wanted to check in and see if the suggestions above resolved the issue you were experiencing?

@raorugan, image name parameter did not contain https, only the register server URL had it. I guess while posting this bug, GitHub also removed some text from my command text. Also, I tried the commands with and without deprecated parameter names.

Hi @sridharvenkat  can you share the error messages you are currently seeing?

@sridharvenkat - can you please look into the acr image name as well , it seems incorrect. https://.azurecr.io https:// is not required. Can you try below format highlighted
<your_acr_name>.azurecr.io/<image_name>:

I was getting the same "Internal Server Error" and the above resolved the issue for me


Add Widevine asset that does not require proprietary codecs

What version of Shaka Player are you using?

Current demo version at http://shaka-player-demo.appspot.com/demo/

What did you do?

Build a Chromium-derived product with Widevine support but without proprietary codecs support. This is a common configuration used by projects such as Chromium Embedded Framework (CEF): https://bitbucket.org/chromiumembedded/cef. There are a number of companies using CEF which are also Widevine licensees. Having a pre-existing option for Widevine playback without requiring proprietary codecs would make testing of Widevine support in CEF easier.

What did you expect to happen?

There should be an asset for testing Widevine playback that does not also require proprietary codecs.

What actually happened?

All Widevine assets are grayed out in the "Asset" select menu when Chromium is built without proprietary codecs support.

@magreenblatt, proprietary codecs refers to MP4, as opposed to WebM.  Chromium or CEF built without proprietary codec support should still be able to play WebM or multicodec (MP4 + WebM) content.  We have many such assets in the demo app already.
The first asset in the list, "Angel One (multicodec, multilingual)" should be playable for you in CEF.  Please confirm.
The second asset in the list, "Angel One (multicodec, multilingual, Widevine)" should be playable if you have a Widevine CDM, which you may not, depending on your Chromium build config.  This is completely different from having support for proprietary codecs.
The third asset in the list, "Angel One (multicodec, multilingual, ClearKey server)" should be playable as long as you have ClearKey support.  This is usually built into Chromium and should be available to you.  Please confirm.
Finally, you should use https://shaka-player-demo.appspot.com/support.html to get a complete report of what is and isn't supported by your build of CEF.  This breaks out support for various containers, codecs, and DRM systems.  If you are having trouble getting playback in Shaka Player, a copy of this report is very valuable information for us and will help us direct you to the right fix in your CEF build.
Does this help?

I'm testing using a local build of M53 on Windows (32-bit). In my local build with proprietary codecs  enabled (GN settings of "proprietary_codecs=true ffmpeg_branding=Chrome") and Widevine disabled the "Angel One (multicodec, multilingual)" and "Angel One (multicodec, multilingual, ClearKey server)" assets play. In the same build when I enable loading of Widevine version <IP_ADDRESS>3 the "Angel One (multicodec, multilingual, Widevine)" asset also plays.
If I create the same build without proprietary codecs then only the "Angel One (multicodec, multilingual)" option is enabled irrespective of whether Widevine is loaded. You can see the same behavior with the binaries here: http://opensource.spotify.com/cefbuilds/index.html (download the "Sample Application"). The support.html page reports the following:
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
v2.0.0

{
  "manifest": {
    "application/dash+xml": true,
    "application/x-offline-manifest": true,
    "mpd": true,
    "application/x-mpegurl": false,
    "application/vnd.apple.mpegurl": false,
    "application/vnd.ms-sstr+xml": false,
    "m3u8": false,
    "ism": false
  },
  "media": {
    "video/mp4; codecs=\"avc1.42E01E\"": false,
    "video/mp4": false,
    "audio/mp4; codecs=\"mp4a.40.2\"": false,
    "audio/mp4": false,
    "video/webm; codecs=\"vp8\"": true,
    "video/webm": true,
    "video/webm; codecs=\"vp9\"": true,
    "audio/webm; codecs=\"vorbis\"": true,
    "audio/webm": true,
    "audio/webm; codecs=\"opus\"": true,
    "video/mp2t; codecs=\"avc1.42E01E\"": false,
    "video/mp2t": false,
    "video/mp2t; codecs=\"mp4a.40.2\"": false,
    "text/vtt": true,
    "application/mp4; codecs=\"wvtt\"": true,
    "application/mp4": true,
    "application/ttml+xml": true,
    "application/mp4; codecs=\"stpp\"": true
  },
  "drm": {
    "org.w3.clearkey": null,
    "com.widevine.alpha": null,
    "com.microsoft.playready": null,
    "com.apple.fps.2_0": null,
    "com.apple.fps.1_0": null,
    "com.apple.fps": null,
    "com.adobe.primetime": null
  },
  "offline": true
}

How is Shaka player detecting the "drm" state? It's possible that this is a bug in Chromium -- some portion of the CDM detection logic being incorrectly gated on proprietary codec support.

We're filling out the "drm" section of the support page by using EME APIs such as navigator.requestMediaKeySystemAccess.  The code is here, if you are curious:
https://github.com/google/shaka-player/blob/addece60/lib/media/drm_engine.js#L1187
Perhaps Chromium intends to enable DRM only with MP4 support, perhaps not.  I wish I could say for certain, but I honestly don't know.  If you think it's a bug, please file it at crbug.com so the Chromium team can give you an authoritative answer.
If you do file a chromium bug, please post a link to the bug report so that we can track it as well.

The Angel One option appears to support VP9 and Vorbis, presumably in WebM, so it should work without proprietary codecs.
However, looking at the referenced probing code, basicVideoCapabilities only specifies 'video/mp4; codecs="avc1.42E01E"'. Thus, only implementations that support MP4 and H.264 will report that success. Adding { contentType: 'video/webm; codecs="vp9"' } to the sequence should fix this.

@ddorwin: Thanks for the suggestion. After making your suggested change clearkey now shows up in the drm list:
"drm": {
    "com.microsoft.playready": null,
    "com.apple.fps.2_0": null,
    "com.apple.fps.1_0": null,
    "com.apple.fps": null,
    "com.adobe.primetime": null,
    "org.w3.clearkey": {
      "persistentState": false
    },
    "com.widevine.alpha": null
  },

However, Widevine is still not detected.

Looks like we forgot to probe WebM in DrmEngine!  We'll get that fixed soon.
If Widevine is still not showing up as supported, perhaps something is set up incorrectly in your CEF build or its runtime environment.  I think the CEF and Chromium issue trackers are your best bet for further assistance getting the Widevine CDM working correctly in CEF3.  Shaka Player ends at JavaScript, so we can't really do much more for you here.

Agreed, thanks for looking into this. I'll debug further in the native code and report back with my findings.

After resolving an error in my code both Widevine and Clearkey support are now reporting correctly with the above change (adding { contentType: 'video/webm; codecs="vp9"' } in DrmEngine.probeSupport). I've also verified that a local build of Shaka Player successfully plays "Angel One (multicodec, multilingual, Widevine)" with this change (I get a 6006 error and CDM playback stops after 10 seconds, but I believe that's expected since my test server isn't licensed to play the sample videos).

Great, glad to hear it!  We've fixed the probe code to add webm, so if there are no objections, I'll consider this resolved.


Add Gnome 3 to popular distribution (line41)

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

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

@romeos25 Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Add support for proxying in RStudio Workbench

This PR adds the ability for the ui editor to be proxied properly through RStudio Workbench.

This will fix https://github.com/rstudio/shinyuieditor/issues/69.