Using 90%+ CPU on Sonoma

M1 Mac Mini 8Gb, running Sonoma.
I think this might be something with legacy screensavers in general, as I found the same issue with a couple of other old savers...
Not really expecting support on a 10 year old purchase, but in case you are still updating... cheers!

Thank you for taking the time to report this - I would love to fix it. Currently creating a new screensaver from scratch in XCode results in a 'legacy' screensaver. As soon as there is more information available on how to update then I will make the required updates.


Downloader: check if the mod is a .exe and if it is extract it to root and run

Done (only for .fexe files)


Revert "Rename key bot variables"

Reverts SGA-A/c2c#96

Accidentally merged the PR too early without renaming the title, but the subtle difference is not a big issue which was why i tried to revert the merge commit. Closing this PR.


In create_new_teams method, include conditional statement for both MentoredTeam and AssignmentTeam

  if assignment.auto_assign_mentor
    new_team = MentoredTeam.create_team_with_users(assignment.id, user_ids)
  else
    new_team = AssignmentTeam.create_team_with_users(assignment.id, user_ids)
  end


Issue with k8s.io/docs/tasks/administer-cluster/dns-debugging-resolution/

This is a...

[ ] Feature Request
[ X] Bug Report

Problem:
Docs for the DNS cluster addon hyperlink is broken
Proposed Solution:
Add correct link
Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/

/assign


Multiple OCKOutcomes are not sent to MongoDB sequentially

Hi HyperProtect SDK Team,
I'm using a OCKOutcome to store my data to send to the Mongo backend, however, I've been facing a payload too large error. My solution around the problem was to wrap my data in multiple outcomes (it ended up being 8 outcomes with a 50,000 character string each) and to send those. Since CareKit uses a revision record to send the data to Mongo, when I tried adding all my outcomes to an array, I faced the same error. My solution around this was to create my own sequential system for all 8 outcomes. This works without the presence of an error. But when an error occurs in the upload (no internet), the outcome is still saved to CoreData. In this case, all future uploads will fail to work as the revision payload will always be too large (as the CoreData store contains the outcomes that failed to sync with MongoDB). Is there another way around this or is this something the team is working to fix (ideally a fix to the payload limit as I believe this is way lower than Mongo's limit of a 16mb document)?
Thanks,
Shawn

Hello Shawn, can you create a PR with this scenario as a XCTest case please?

Yes, I added the XCTests to my open PR.


52 add reference in readme

Please also add an hyperlink directly to the ArXiV somewhere closer to the top of the README


Background color issue

How we can set background to browser fragment

This sample has been migrated to a new location and updates are happening there (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


Adding repo support for Ubuntu 14 and Debian 7 for HDP <IP_ADDRESS>.

Adding repo support for Ubuntu 14 and Debian 7 for HDP. Support started at version <IP_ADDRESS> and I checked repos exist for these combinations. HDP documentation implies support for both Trusty and Utopic saying just "14". I also converted the debian platform case statement to if/elsif to get around rubocop's 3 level nesting offense.

Yikes, sorry about that. I've moved the hdp_update_version assignment to the rest of the assignments before it gets referenced in the if/else block. Did some additional testing on Ubuntu 14.04 to ensure bothe repos that get set up (HDP and HDP-UTILS) work and they do.

This LGTM... getting approval from management to merge, since this is your first contribution to a Cask-managed project.
@nitinmotgi can you approve this?

Lgtm +1

Can you merge master back to your branch and fix the one conflict? I'll get this merged and a new version of the cookbook released.
Thanks, again.

This is my first time merging changes upstream so hopefully this is correct. Looks like the merge conflict was simple enough to resolve. Just the string in the hdp_apt_repo_path block.

Perfect. Thanks for contributing!


Removed double negative

Issue #11
This is just for easier code review by other people ^^

Thanks.


Push hash to history

I'd like to be able to append a hash parameter to a url on user action without causing a page reload.  Widget rebuild is fine, but nothing that destructs the current widget tree.  Ideally functionality identical to Javascript History.pushState().  Currently the only option that I can find is to use to(), and with or without isReplacement it seems to force a full page navigation w/ widget destruction.

@lulupointu Is there any possibility of getting this functionality? :)

This is because if the url changes than VRouter considers that the VWidget is different.
To prevent this, you can use a key on the VWidget where you have a changing path.
Feel free to reopen this issue if you are having trouble implementing this.


fix: fix runtime error

Kibana could not startup and throw error as below:
[WARN  tini (248)] Tini is not running as PID 1 and isn't registered as a child subreaper.
Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.

 FATAL  Error: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /usr/share/kibana/node_modules/re2/build/Release/re2.node)

this PR will fix this issue

LGTM


Fix problem with metrics test.

The counter_zero_slot test was checking for an assertion that only fires in a debug build. However, upstream rust-lang/rust runs tests in --release mode. This unblocks the upstream update.

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing f3e13226d6d17a2bc5f325303494b43a45f53b7f to master...


Add option to GetStatementOfAccount::create()

If you fix the conflicts, I'll merge :blush:

This is already merged as 5d5cbc8774ebf7044756d4903182fe8342f0e630.


"Generate Support Bundle" Button for Rancher

You can click Generate Support Bundle link at the bottom of the UI to download a zip file contains Longhorn related configuration and logs.

Source: https://longhorn.io/docs/0.8.1/advanced-resources/troubleshooting
It would be great to have this for Rancher.
gz#14291

Yeah it would be great to have this feature enabled for Rancher as well and there should be an config exposed like this on what all logs to collect as part of generating support bundle, so it will be extremely useful for OEM vendors who are packaging their software through Rancher
https://help.replicated.com/api/support-bundle-yaml-specs/kubernetes-logs/

Checking in on this request to add automated bundling for support logs on Rancher. Very manual process at the moment, which can lead to missed logs, which can lead to lost time trying to solve an issue. The functionality already exists for Longhorn, please port this over to Rancher. This request has been open for a year without any feedback at all. I believe it would be of great value for all Rancher users.


Table description and column comments are lost when export table from A db to B db .

Description
export tables from A mysql db to another B mysql db, the tables and the fields comments are lost.
DBeaver Version
23.2.2
Operating System
cnetos7
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Hello, @zghlx. Please provide more details. What do you mean  "the tables and the fields comments are lost"?

Thanks for your report!

Reproducible on any database

Hello @zghlx
For MySQL you can:

Do a copy of your table in the Navigator tree before data transfer. With simple Ctrl+C and Ctrl+V. This case all column comments and table comment will be copied.

Other option - you can specify table comment for a new table during data transfer this way:

Hello @zghlx
For MySQL you can:

Do a copy of your table in the Navigator tree before data transfer. With simple Ctrl+C and Ctrl+V. This case all column comments and table comment will be copied.
Other option - you can specify table comment for a new table during data transfer this way:

thanks! but if mysql db A contains hundred tables and too many fields comments per table, i think you given method is a hard and replate work.  I need transfer A table's coment and fields comments to mysql db B automaticly, just like other db clients tools, like heidisql etc.

I need transfer A table's coment and fields comments to mysql db B automaticly

As I said, you can copy-paste tables first. Just metadata. And after that use data transfer.
Also, you can use backup/restore tools: https://github.com/dbeaver/dbeaver/wiki/Backup-Restore


WIP: Nix code/structure refactoring

Nix code refactoring
this refactoring aims to bettern separate inputs, outputs and "local"
versus external packages or overrides:

default.nix only exposes "deliverables" and receive everything else
nix/default.nix: adds overrides, niv deps and provides pkgs/muslpkgs
nix/pkgs/default.nix: provides all "local" packages/scritps
several lib files moved from nix/ to nix/lib
shell.nix: depends on nix/,nix/pkgs not on default.nix
docker image builds have been moved to ./docker.nix
docker.nix uses the more efficient buildlayeredimage

Both default.nix and shell.nix now receive pkgs and _pkgs:

pkgs -> nix/default.nix:pinned nixpkgs with all niv supplied overlays applied and containing a musl based equivalent under muslpkgs.
_pkgs -> nix/pkgs/default.nix: exposes all local package/scritps living under nix/pkgs/*.

Notes

Dear reviewer: "sorry, sorry, sorry" :heart: : I should have done a better job splitting this up in separate steps
Probably this "separation of concerns" is violated in places but i hope the idea makes sense at least
See Optimising Docker Layers for the use of buildLayeredImage - though this is probably the most obvious unrelated drive-by fix and i'm happy to split if off from this PR
I didn't notice any relevant re-builds so I think/hope this doesn't alter outputs in any relevant ways

TODOS:

[ ] collect some review comments
[ ] fix documentation which has been invalidated by these changes in some places

@michaelpj thanks for the initial review, I’ll address your comments tomorrow.
PS: i guess i don’t like qualified access when the attribute paths gets too long. Mostly i’m happy when i can see an inherent statement at the start of the scope/binding. I do definitely dislike “with” unlike it’s for a tiny scope though as this is much less explicit. Be that as it may, I’m happy to write more qualified statements (i would just prefer lib.whatever over pkgs.lib.whatever unless there is good reason i guess)


[WIP] Show label images

Show label images in the item list.
This is configurable in the plugin.
This is currently very rough and could use css improvements.  It is expected that we'd also expose metadata in some manner, but that hasn't been done yet.

Codecov Report

Merging #173 into master will decrease coverage by 0.25%.
The diff coverage is 70.37%.

@@            Coverage Diff             @@
##           master     #173      +/-   ##
==========================================
- Coverage   82.93%   82.68%   -0.26%
==========================================
  Files          52       52
  Lines        3018     3061      +43
  Branches       64       69       +5
==========================================
+ Hits         2503     2531      +28
- Misses        515      530      +15

Impacted Files
Coverage Δ

server/rest/large_image.py
95.77% <ø> (ø)
:arrow_up:

web_client/views/configView.js
63.26% <0%> (-5.63%)
:arrow_down:

server/constants.py
100% <100%> (ø)
:arrow_up:

web_client/views/itemList.js
76.78% <66.66%> (-11.1%)
:arrow_down:

server/base.py
96.77% <85.71%> (-1.41%)
:arrow_down:

Continue to review full report at Codecov.

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

@jbeezley, could you review this?  I feel it is still a work-in-progress, but there is a desire to have it merged in and then have PRs to change the behavior later.  To have complete tests, we'll need to expose some of the files which have associated images to the client tests, but I'll leave that for a separate PR.

The item list looks a little odd with extra images enabled.  I think either we should remove all of the width's on those elements (so there is no padding) or make all of the item names line up.

With the last change, I think it looks okay.  I'm okay with merging as is.


Doc about changing CNI

Hi,
I would thank you about k3s which seem a pretty cool lightweight k8s implementation.
I seen in the doc the part about changing CNI, but on the server side, it seem it force to use flannel.
It's not possible to disable flannel via the install script.
I wondering use Calico to enable dual-stack (v4/v6) with k3s, any idea how achieve that and stop the use of flannel ?
I've seen some Range are hardcoded in k3s  :
pkg/daemons/control/server.go:          _, clusterIPNet, _ := net.ParseCIDR("<IP_ADDRESS>/16")

Thanks for any road to follow.

https://github.com/rancher/k3s#flannel

@vaibhavsood Trying disabling flannel per the docs and also the cluster cidr can be set with k3s server --cluster-cidr X.X.X.X/X.  Let me know if that works, we really haven't fully tested third party CNI drivers, but we very much need them to work.  So any feedback or issues are appreciated.

@ibuildthecloud Thanks for pointing that,
Now I have :

start from scratch :
Launch the server without agent, and cluster-cidr to <IP_ADDRESS>/16
Launch the agent with good token and no flannel, the pods stay in pending waiting for CNI
I create calico node manifest (crd, cm, daemonset).
The pods are created within default <IP_ADDRESS>/16 (ignoring my 192).
After that, I changed Calico to not use PodCIDR but to use its own IPPool (192.168..).

Now, when I schedule a pod, here the error I get :
  Warning  FailedCreatePodSandBox  3s    kubelet, sh25      Failed create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "daf8a2d1b9eb49d11df0714e43dfdc087b95f47522292402e7bb2513a0ccb087": operation List is not supported on {sh25 6}

Any idea about that ?
It seem k3s doesn't like any other prefix or it's other things ?

@ibuildthecloud specifying --cluster-cidr x.x.x.x/x does not seem to work:
root@k8s-master-dev:~$ /usr/local/bin/k3s server --cluster-cidr <IP_ADDRESS>/16
INFO[2019-03-05T21:56:55.807592266Z] Starting k3s v0.1.0 (91251aa)
INFO[2019-03-05T21:56:55.808984449Z] Running kube-apiserver --watch-cache=false --cert-dir /var/lib/rancher/k3s/server/tls/temporary-certs --allow-privileged=true --authorization-mode Node,RBAC --service-account-signing-key-file /var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range <IP_ADDRESS>/16 --advertise-port 6445 --advertise-address <IP_ADDRESS> --insecure-port 0 --secure-port 6444 --bind-address <IP_ADDRESS> --tls-cert-file /var/lib/rancher/k3s/server/tls/localhost.crt --tls-private-key-file /var/lib/rancher/k3s/server/tls/localhost.key --service-account-key-file /var/lib/rancher/k3s/server/tls/service.key --service-account-issuer k3s --api-audiences unknown --basic-auth-file /var/lib/rancher/k3s/server/cred/passwd --kubelet-client-certificate /var/lib/rancher/k3s/server/tls/token-node.crt --kubelet-client-key /var/lib/rancher/k3s/server/tls/token-node.key
INFO[2019-03-05T21:56:55.972630074Z] Running kube-scheduler --kubeconfig /var/lib/rancher/k3s/server/cred/kubeconfig-system.yaml --port 0 --secure-port 0 --leader-elect=false
INFO[2019-03-05T21:56:55.973624160Z] Running kube-controller-manager --kubeconfig /var/lib/rancher/k3s/server/cred/kubeconfig-system.yaml --service-account-private-key-file /var/lib/rancher/k3s/server/tls/service.key --allocate-node-cidrs --cluster-cidr <IP_ADDRESS>/16 --root-ca-file /var/lib/rancher/k3s/server/tls/token-ca.crt --port 0 --secure-port 0 --leader-elect=false
INFO[2019-03-05T21:56:56.179101139Z] Listening on :6443

I can confirm that --cluster-cidr is working in v0.2.0-rc5.
Also, for what it's worth, if you want to use cilium for networking with k3s, you'll need to change this https://github.com/cilium/cilium/blob/master/examples/kubernetes/1.13/cilium-containerd.yaml#L334 line in official cilium manifest to /run/k3s/containerd/containerd.sock.

@valentin2105 Did you managed to have calico on k3s? Is it works fine ?

@ibuildthecloud I tried disabling flannel and specifying --service-cidr and --cluster-cidr but it seems custom configs in /var/lib/rancher/k3s/agent/etc/cni/net.d/ are not picked up.
I'm trying to use the CNI bridge plugin (https://github.com/containernetworking/plugins/tree/master/plugins/main/bridge)
installing k3s with
INSTALL_K3S_EXEC="server --no-flannel --service-cidr <IP_ADDRESS>/16 --cluster-cidr=<IP_ADDRESS>/16"

and a config like
{
  "name": "kubepods",
  "type": "bridge",
  "bridge": "kubepods",
  "isDefaultGateway": true,
  "forceAddress": false,
  "ipMasq": true,
  "hairpinMode": true,
  "ipam": {
    "type": "host-local",
    "ranges": [
      {
        "subnet": "<IP_ADDRESS>/16",
        "rangeStart": "<IP_ADDRESS>",
        "rangeEnd": "<IP_ADDRESS>",
        "gateway": "<IP_ADDRESS>"
      }
    ],
    "dataDir": "/tmp/container-ipam-state",
    "resolvConf": "/etc/resolv.conf"
  }
}

as /var/lib/rancher/k3s/agent/etc/cni/net.d/11-bridge-kubepods.conf
results in
k3s[26449]: E1015 14:17:50.792650   26449 kubelet.go:2173] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

Are there any other parameter that need to be passed to have k3s pick the CNI configs up from the default config dir?

Looking at containerd.log I found that it is looking in /etc/cni/net.d/ instead of /var/lib/rancher/k3s/agent/etc/cni/net.d/ for configs (although the bundled flannel config is written into the latter). However, if I put my own config in /etc/cni/net.d it seems the binary is expected in /opt/cni/bin, while it is actually in /var/lib/rancher/k3s/data//bin
@ibuildthecloud is this expected behaviour? Is it save to create a symlink from /opt/cni to /var/lib/rancher/k3s/data//? If yes is the id static or where I look it up for automated generation of the symlink?

Hi,
I got the same error as @valentin2105 and @ctr49 when trying to migrate my K3s cluster from flannel to Calico.
In fact it does not seem that error is in calico-kube-controllers. If it complains in the log on not finding calico bin in /opt/cni/bin it is because calico-node did not finish its task properly. In fact this pod use a container for IPAM migration and running the logs here is what I found:
kubectl logs <name of pod type calico-node> -c upgrade-ipam -n kube-system

2019-11-04 23:14:37.760 [INFO][1] migrate.go 72: retrieving node for IPIP tunnel address
2019-11-04 23:14:37.764 [INFO][1] migrate.go 148: checking if host-local IPAM data dir dir is empty...
2019-11-04 23:14:37.764 [INFO][1] migrate.go 171: host-local IPAM data dir is not empty, migrating...
2019-11-04 23:14:37.764 [INFO][1] migrate.go 179: setting datastore readiness to false
2019-11-04 23:14:37.780 [INFO][1] migrate.go 200: successfully set datastore readiness to false
2019-11-04 23:14:37.780 [INFO][1] migrate.go 203: removing cni binaries...
2019-11-04 23:14:37.780 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/calico"
2019-11-04 23:14:37.780 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/host-local"
2019-11-04 23:14:42.781 [INFO][1] migrate.go 215: acquiring lock on host-local IPAM
2019-11-04 23:14:42.781 [INFO][1] migrate.go 223: successfully acquired lock on host-local IPAM
2019-11-04 23:14:42.781 [INFO][1] migrate.go 236: mapping pod ips to pods...
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="helm-install-traefik-4vd5z"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="coredns-66f496764-dn9kn"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="traefik-d869575c8-zscz2"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="calico-kube-controllers-6d85fdfbd8-gvqhb"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="calico-node-mn29n"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="canal-9m2x2"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="sh-5f4cc76d6c-pwm4q"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="test-685ddd4774-gq9tz"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="local-path-provisioner-58fb86bdfd-76btn"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="svclb-traefik-smrmc"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 249: successfully mapped pod ips to pods!
2019-11-04 23:14:42.792 [INFO][1] migrate.go 252: reading files from host-local IPAM data dir...
2019-11-04 23:14:42.792 [INFO][1] migrate.go 261: processing file... file="<IP_ADDRESS>"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 305: assinging pod IP to Calico IPAM... file="<IP_ADDRESS>"
2019-11-04 23:14:42.792 [INFO][1] ipam.go 583: Assigning IP <IP_ADDRESS> to host: localhost.localdomain
2019-11-04 23:14:42.795 [INFO][1] migrate.go 226: releasing lock on host-local backend...
2019-11-04 23:14:42.795 [INFO][1] migrate.go 230: successfully released lock on host-local backend!
2019-11-04 23:14:42.795 [ERROR][1] ipam_plugin.go 95: failed to migrate ipam, retrying... error=failed to assign IP to calico backend: The provided IP address is not in a configured pool
node="localhost.localdomain"
2019-11-04 23:14:43.796 [INFO][1] migrate.go 65: checking host-local IPAM data dir dir existence...
2019-11-04 23:14:43.796 [INFO][1] migrate.go 72: retrieving node for IPIP tunnel address
2019-11-04 23:14:43.800 [INFO][1] migrate.go 148: checking if host-local IPAM data dir dir is empty...
2019-11-04 23:14:43.800 [INFO][1] migrate.go 171: host-local IPAM data dir is not empty, migrating...
2019-11-04 23:14:43.800 [INFO][1] migrate.go 179: setting datastore readiness to false
2019-11-04 23:14:43.817 [INFO][1] migrate.go 200: successfully set datastore readiness to false
2019-11-04 23:14:43.817 [INFO][1] migrate.go 203: removing cni binaries...
2019-11-04 23:14:43.817 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/calico"
2019-11-04 23:14:43.817 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/host-local"
2019-11-04 23:14:48.818 [INFO][1] migrate.go 215: acquiring lock on host-local IPAM

So it seems that it does not succeed in migrating the IP of each pod deployed over flannel to the calico CNI. Delete each pod one by one unlock the situation. But then it is blocking to traefik LB.
At this point, I decide to drop of migrating my cluster and started from a fresh cluster. Here is the procedure for installing calico v0.3.1 over K3s v0.10.2:
install.k3s.sh --write-kubeconfig-mode 644 --docker --no-flannel
curl https://docs.projectcalico.org/v3.10/manifests/calico.yaml -O
POD_CIDR=$(kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}') sed -i -e "s?<IP_ADDRESS>/16?$POD_CIDR?g" calico.yaml

Now before you apply calico, you must activate ip forwarding which is disabled in calico by default. This can be done by adding the container_settings parameter thanks to this doc. You network config should look like:
  cni_network_config: |-
    {
      "name": "k8s-pod-network",
      "cniVersion": "0.3.1",
      "plugins": [
        {
          "type": "calico",
          "log_level": "info",
          "datastore_type": "kubernetes",
          "nodename": "__KUBERNETES_NODE_NAME__",
          "mtu": __CNI_MTU__,
          "ipam": {
              "type": "calico-ipam"
          },
          "container_settings": {
              "allow_ip_forwarding": true
          },
          "policy": {
              "type": "k8s"
          },
          "kubernetes": {
              "kubeconfig": "__KUBECONFIG_FILEPATH__"
          }
        },
        {
          "type": "portmap",
          "snat": true,
          "capabilities": {"portMappings": true}
        }
      ]
    }

Now you can apply it with kubectl apply -f calico.yaml and everything should be running fine.
If IP forwarding is not set properly, you should see error in kubectl logs -n kube-system <svclb-traefik pod name> -c https:
/proc/sys/net/ipv4/ip_forward is read only
+ trap exit TERM INT
+ cat /proc/sys/net/ipv4/ip_forward
+ '[' 0 '!=' 1 ]
+ exit 1

Jeff
PS: this put me on the path of resolution

While trying to install Calico 3.12 with k3s v1.17.2+k3s1 I've run into a couple of problems and I'm not sure what to troubleshoot next. As per the docs I've added the allow_ip_forwarding snippet to the CNI config and changed the pod CIDR to <IP_ADDRESS>/16 to match the k3s defaults. After applying the calico yaml I had to run kubectl taint nodes --all node.kubernetes.io/not-ready:NoSchedule- in order to get the calico-kube-controllers-XXX scheduled (the single node was in a not ready state because of the lack of a network). After removing the taint the pod becomes stuck in ContainerCreating with the error message: network is not ready: runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized. My current theory is that this is all caused by the fact that this cluster is on a single node.
Anyone else about to stand up k3s on a single node with Calico?

As far as I can tell, there is no bug here, but configuring calico on k3s requires some pretty specific configuration that we should consider testing and documenting. I'd like to do this in order to have some known reference implementations on swapping out CNI.

Hi,
I got the same error as @valentin2105 and @ctr49 when trying to migrate my K3s cluster from flannel to Calico.
In fact it does not seem that error is in calico-kube-controllers. If it complains in the log on not finding calico bin in /opt/cni/bin it is because calico-node did not finish its task properly. In fact this pod use a container for IPAM migration and running the logs here is what I found:
kubectl logs <name of pod type calico-node> -c upgrade-ipam -n kube-system

2019-11-04 23:14:37.760 [INFO][1] migrate.go 72: retrieving node for IPIP tunnel address
2019-11-04 23:14:37.764 [INFO][1] migrate.go 148: checking if host-local IPAM data dir dir is empty...
2019-11-04 23:14:37.764 [INFO][1] migrate.go 171: host-local IPAM data dir is not empty, migrating...
2019-11-04 23:14:37.764 [INFO][1] migrate.go 179: setting datastore readiness to false
2019-11-04 23:14:37.780 [INFO][1] migrate.go 200: successfully set datastore readiness to false
2019-11-04 23:14:37.780 [INFO][1] migrate.go 203: removing cni binaries...
2019-11-04 23:14:37.780 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/calico"
2019-11-04 23:14:37.780 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/host-local"
2019-11-04 23:14:42.781 [INFO][1] migrate.go 215: acquiring lock on host-local IPAM
2019-11-04 23:14:42.781 [INFO][1] migrate.go 223: successfully acquired lock on host-local IPAM
2019-11-04 23:14:42.781 [INFO][1] migrate.go 236: mapping pod ips to pods...
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="helm-install-traefik-4vd5z"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="coredns-66f496764-dn9kn"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="traefik-d869575c8-zscz2"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="calico-kube-controllers-6d85fdfbd8-gvqhb"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="calico-node-mn29n"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="canal-9m2x2"
2019-11-04 23:14:42.791 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="sh-5f4cc76d6c-pwm4q"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="test-685ddd4774-gq9tz"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 246: mapping in pod IP="" namespace="kube-system" pod="local-path-provisioner-58fb86bdfd-76btn"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 246: mapping in pod IP="<IP_ADDRESS>" namespace="kube-system" pod="svclb-traefik-smrmc"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 249: successfully mapped pod ips to pods!
2019-11-04 23:14:42.792 [INFO][1] migrate.go 252: reading files from host-local IPAM data dir...
2019-11-04 23:14:42.792 [INFO][1] migrate.go 261: processing file... file="<IP_ADDRESS>"
2019-11-04 23:14:42.792 [INFO][1] migrate.go 305: assinging pod IP to Calico IPAM... file="<IP_ADDRESS>"
2019-11-04 23:14:42.792 [INFO][1] ipam.go 583: Assigning IP <IP_ADDRESS> to host: localhost.localdomain
2019-11-04 23:14:42.795 [INFO][1] migrate.go 226: releasing lock on host-local backend...
2019-11-04 23:14:42.795 [INFO][1] migrate.go 230: successfully released lock on host-local backend!
2019-11-04 23:14:42.795 [ERROR][1] ipam_plugin.go 95: failed to migrate ipam, retrying... error=failed to assign IP to calico backend: The provided IP address is not in a configured pool
node="localhost.localdomain"
2019-11-04 23:14:43.796 [INFO][1] migrate.go 65: checking host-local IPAM data dir dir existence...
2019-11-04 23:14:43.796 [INFO][1] migrate.go 72: retrieving node for IPIP tunnel address
2019-11-04 23:14:43.800 [INFO][1] migrate.go 148: checking if host-local IPAM data dir dir is empty...
2019-11-04 23:14:43.800 [INFO][1] migrate.go 171: host-local IPAM data dir is not empty, migrating...
2019-11-04 23:14:43.800 [INFO][1] migrate.go 179: setting datastore readiness to false
2019-11-04 23:14:43.817 [INFO][1] migrate.go 200: successfully set datastore readiness to false
2019-11-04 23:14:43.817 [INFO][1] migrate.go 203: removing cni binaries...
2019-11-04 23:14:43.817 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/calico"
2019-11-04 23:14:43.817 [INFO][1] migrate.go 208: successfully removed cni binary! binary="/host/opt/cni/bin/host-local"
2019-11-04 23:14:48.818 [INFO][1] migrate.go 215: acquiring lock on host-local IPAM

So it seems that it does not succeed in migrating the IP of each pod deployed over flannel to the calico CNI. Delete each pod one by one unlock the situation. But then it is blocking to traefik LB.
At this point, I decided to drop off migrating my cluster and to start from a fresh cluster. Here is the procedure for installing calico v0.3.1 over K3s v0.10.2:
install.k3s.sh --write-kubeconfig-mode 644 --docker --no-flannel
curl https://docs.projectcalico.org/v3.10/manifests/calico.yaml -O
POD_CIDR=$(kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}') sed -i -e "s?<IP_ADDRESS>/16?$POD_CIDR?g" calico.yaml
export DATASTORE_TYPE=kubernetes
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml

Now before you apply calico, you must activate ip forwarding which is disabled in calico by default. This can be done by adding the container_settings parameter thanks to this doc. You network config should look like:
  cni_network_config: |-
    {
      "name": "k8s-pod-network",
      "cniVersion": "0.3.1",
      "plugins": [
        {
          "type": "calico",
          "log_level": "info",
          "datastore_type": "kubernetes",
          "nodename": "__KUBERNETES_NODE_NAME__",
          "mtu": __CNI_MTU__,
          "ipam": {
              "type": "calico-ipam"
          },
          "container_settings": {
              "allow_ip_forwarding": true
          },
          "policy": {
              "type": "k8s"
          },
          "kubernetes": {
              "kubeconfig": "__KUBECONFIG_FILEPATH__"
          }
        },
        {
          "type": "portmap",
          "snat": true,
          "capabilities": {"portMappings": true}
        }
      ]
    }

Now you can apply it with kubectl apply -f calico.yaml and everything should be running fine.
If IP forwarding is not set properly, you should see error in kubectl logs -n kube-system <svclb-traefik pod name> -c https:
/proc/sys/net/ipv4/ip_forward is read only
+ trap exit TERM INT
+ cat /proc/sys/net/ipv4/ip_forward
+ '[' 0 '!=' 1 ]
+ exit 1

Jeff
PS: this put me on the path of resolution

Hey @identitymonk .
What steps did you follow when trying to migrate from flannel to calico?
I have found this resource
https://docs.projectcalico.org/getting-started/kubernetes/flannel/migration-from-flannel
but the job does not run. Logs from the container are
Daemonset kube-flannel-ds-amd64 not exists, no migration process is needed

@ibuildthecloud How would I uninstall or disable embedded flannel CNI especially for a case where I do not have ssh access to the node. I can only use kubectl.

@jawabuu you need to pass arguments to the k3s server, which would require access to the host.

Hey @brandond I meant a k3s cluster that is already running with flannel as the CNI. How would I change the CNI for such a cluster?
This works for 'stock' k8s
https://docs.projectcalico.org/getting-started/kubernetes/flannel/migration-from-flannel

@jawabuu you would need to add --flannel-backend=none to the k3s arguments, then install an alternative CNI.

Thanks @brandond , this instruction is for an already running k3s cluster?

Yes, although I haven't tested it myself. I would also expect things to be pretty broken after you do that, until you get the new CNI up and running.

This is fine, of the top of your head would there be another way to disable the default flannel?

No?

Alright, I'll teat this out and see if it works

@vaibhavsood Trying disabling flannel per the docs and also the cluster cidr can be set with k3s server --cluster-cidr X.X.X.X/X. Let me know if that works, we really haven't fully tested third party CNI drivers, but we very much need them to work. So any feedback or issues are appreciated.

Hey @ibuildthecloud  I have published a project https://github.com/jawabuu/kloud-3s that uses k3s and have successfully tested with flannel, calico, cilium and weave while managing to preserve source ip whenever needed.
Could this be of help in documenting k3s against 3rd party CNI's?

Currently only the stated cloud providers are supported but the principle is the same and should work for on-prem.
The options to get k3s working with calico are,
            - name: IP_AUTODETECTION_METHOD
              value: "interface=${interface}"
            # Enable IPIP
            - name: CALICO_IPV4POOL_IPIP
              value: "Never"
            # Enable IPIP
            - name: CALICO_IPV4POOL_VXLAN
              value: "Always"
           - name: CALICO_IPV4POOL_CIDR
              value: "${calico_cidr}"

These are envs for calico.yaml
interface is the interface connecting your nodes.
calico_cidr is the k3s cluster cidr

Thanks, I will check it out..


Navbar brand-logo wrong position in small screen

I'm using materialize version 0.95.3 bower package.

your side-nav should not be inside the anv element. It loooks like that is the thing pushing your brand logo down. The button-collapse is absolute-positioned so it doesn't have that issue.

I just do like Materialize Demo Navbar and on demo page nav work well

ill make you a new example when im home, not able to type much on this thing xD

@yowkah Thank you so much for help.

Move the container class to its parent div. We have also update the templates.


why specify --kubeconfig and --master

I appear to have to provide both.
With a valid kubeconfig, I am getting:
$ ./cluster-capacity --kubeconfig=/home/decarr/.kube/config --podspec=examples/pod.yaml
(02:41:03 PM) decarr: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined

I am not in-cluster.

For example, I would expect the master to be pulled from the kubeconfig current cluster.

@derekwaynecarr Right, with --kubeconfig,  it should not ask for --master.

I think lets close it as it is fixed now. Please reopen if the issue still persists.


groupBy object do not provide all object fields

Version: (2.4.2)
Module: (quill-jdbc)
Database: (postgresql)
When using groupBy(object) not all fields are available.
val query: Quoted[Query[(User, Option[LocalDate])]]
query.groupBy(_._1).map { data =>
    data._1 -> data._2.map(_._2).max
}

Expected behavior
Valid sql code should look like this:
SELECT x3.id, x3.fullname, x3.email, MAX(x3._2)
FROM (...) x3
GROUP BY x3.id, x3.fullname, x3.email

Actual behavior
Code above generates invalid sql code:
SELECT x3.id, x3.fullname, x3.email, MAX(x3._2)
FROM (...) x3
GROUP BY x3._1

In this case postgres can't access fields that aren't used in group by statement.
Steps to reproduce the behavior
Fiddle: https://scalafiddle.io/sf/4tyyZR4/2
Workaround
Now I'm executing new query for every user.
@getquill/maintainers

Could be related to #1092

still a valid issue: https://scastie.scala-lang.org/fwbrasil/Z2CeR2qHQJK6EyQWUBhANA


CI: Verify support for Python 3.13

About
What the title says.
Problem
It looks like the llvmlite package does not provide binary wheels for Python 3.13 yet, see CI job run #11652819674.

[!WARNING]
RuntimeError: Could not find a llvm-config binary. There are a number of reasons this could occur,
please see: https://llvmlite.readthedocs.io/en/latest/admin-guide/install.html#using-pip for help.

It could probably be worked around by providing an llvm compiler toolchain, supporting Python that is falling back to build that package before installation.

Support for Python 3.13 is being tracked here on a dependency package.

https://github.com/numba/llvmlite/issues/1084

My evaluation is that we need to leave PyCaret behind.

https://github.com/crate/crate-clients-tools/issues/207


Artifact dependency points to non existing build configuration

Code
project {
   sequence {
      parallel {
         sequence {
            build(Restore) {
               produces("**/*")
            }
            build(Build) {
               requires(Restore, "**/*")
            }
         }
         sequence {
            //...
         }
      }
   }
}

object Restore : BuildType({
   name = "Restore"
   steps {
      msBuild {
         //...
      }
   }
})

object Build : BuildType({
   name = "Build"
   steps {
      msBuild {
         //...
      }
   }
})

Error

Artifact dependency points to non existing build configuration with external id: <PROJECT_ID>_Restore

It actually prints twice in a row, I don't know why.
Solution attemps
I tried changing the build id:
object Restore : BuildType({
   id = "<PROJECT_ID>"
   name = "Restore"
})

But the error changed to:

Artifact dependency points to non existing build configuration with external id: <PROJECT_ID>_<PROJECT_ID>_Restore

@Logerfo do you have a full source of this configuration somewhere? Which TeamCity version do you use? I couldn't reproduce it with this code sample on 2019.1.x

I don't, it's a private project. I can try to reproduce it to a minimum configuration... I'm currently using TeamCity Professional 2019.1.2 (build 66342).

OK, good, we are on the same TeamCity version. Please, if you can reproduce the issue with the minimal configuration that would help a lot.

Check out https://github.com/Logerfo/pipeline-test

I'm not sure if the build is actually supposed to pass successfully, but either way it should not fail so shortly. The following error must not be thrown:

Artifact dependency points to non existing build configuration with external id: PipelineTest_Restore

Looks exactly like the code that I have created for testing: https://github.com/antonarhipov/myproject
Couldn't reproduce with your example neither.
Maybe teamcity-server.log reveals anything?

Here's what happened:

The repository was created with only a readme file.
The teamcity project was created.
Versioned settings was enabled.
Teamcity commited the settings file.
The settings file was edited in order to retrace the reproduction steps.
The build was triggered automatically when the changes were pushed.
The build failed, QED.
I changed the log to debug, since the current log wasn't helpful.
I don't know if I needed to restart teamcity in order to change the log verbosity, so I tried without restarting.
A single push was not enough to trigger the build.
Running the build manually could not reproduce the error.

I don't think this has anything to do with the log verbosity, but perhaps this is happening in my private project because it's triggered by a github pull request and both base and target branches are NOT master.
My master settings has only one build with a lot of steps. What I'm trying to do is make some steps parallel in order to make the build faster. Do you think that would be possible without messing with master?

Ok, I probably understand now why it fails. So you have a master and a branch. And the configuration that fails is the one that you have in branch?
Unfortunately, I think there's no easy way for you to avoid touching the master. The build chain structure is taken from master. So if your master has one build configuration and you want to have two configurations in the branch - it is not going to work. You can read about branch specific settings and the limitations in this blog post: https://blog.jetbrains.com/teamcity/2018/01/branch-specific-settings-in-teamcity/

Just to clarify about the configuration that you have created:  surrounding sequence with "parallel" block doesn't make the build configurations that are declared in the nested sequence block to run in parallel. See,
project {
sequence {
parallel {
sequence {
build(A)
build(B)
}
}
}
}
In this example, parallel block does nothing. The builds A and B are sequential.
What actually is produced here is a project with A & B build configurations where B depends on A.
However, this
project {
sequence {
parallel {
sequence {
build(A)
build(B)
}
sequence {
build(C)
build(D)
}
}
}
}
would produce 2 build chins, A->B and C->D.

Yes, thanks, I'm aware of that. I have more than 10 steps, but restoring packages and building cannot be parallel. I just used the problematic part to reproduce the error.
Alright then, I'll try to do this again when I manage to have the time to stop master commits and dedicate exclusively to this. It's a shame that Teamcity has such limitations... Anyway, thank you very much!


Add guide explaining how to use Pangeo Docker Images with Jupyter Notebook on HPC Systems using Singularity

I'm going to go ahead and merge this so that it's more easily discoverable by anyone interested. Would be great to add to the read-the-docs page since that is now up. But that can happen in a separate PR


Update links in README

As the master branch has been renamed to main, update appropriate links in the readme document.

ty!


Additional metadata information needed regarding ATBD Reviewers

###Description
We need to collect reviewer information for each ATBD. If an ATBD has already been reviewed and is being uploaded, we need to be able to verify this review.
The reviewer information does not need to be included in ATBD search.
My thinking is that this would be very similar to adding contacts (see below). However, we would only need the following:
First Name
Last Name
Email
Affiliations

This will also solve our issue of informing the curator of who to contact about reviewing ATBDs created within APT. The curator could reach out to the potential reviewers via email with instructions on how to create an account.
Acceptance Criteria:

[ ] New step in APT (similar to Contacts) that requests above information about reviewers or potential reviewers

@wrynearson This is just my thinking out loud. If it's too complicated/time consuming to make this an additional step in APT, we can just request this information somehow on the Identifying Information step.

Thanks @bwbaker1 for scoping this out. Do you see this being added only to the PDF-upload workflow, or also to the standard APT-created ATBD workflow?
Is there any way that you think we could incorporate this into the existing review process by encouraging external ATBD review to be done within the tool? Maybe that wouldn't make sense for historical ATBDs...
@thenav56 (or @sunu), could you chime in on the LOE of adding this, either as a dedicated step or as an additional field?

@wrynearson I see this for both workflows because we need reviewer information both ways.
We still need this information even if the ATBD was reviewed externally (verification that it was actually reviewed). This includes historical ATBDs as well.

@bwbaker1 @wrynearson I have some questions to understand the intended workflow a little better:

Do we collect this information only for ATBDs that were externally reviewed already or for all ATBDs?

If we collect this information for all ATBDs, will the curators use this information to assign reviewers for ATBDs that are yet to be reviewed? Should we also record whether an ATBD has already been reviewed externally or it needs review during ATBD creation?

Is this information visible to the authors and curators only or to all viewers?
For ATBDs that have been externally reviewed already, how does the verification process work for verifying that the ATBD was actually reviewed? Does it happen offline through email or inside APT?

Does APT need a way to track this verification status somehow? eg: mark the reviewer information on an ATBD as verified or unverified?

@wrynearson @sunu

We are collecting this information for all ATBDs.
i. Yes, curators will use this information to assign reviewers.
ii. Yes, it would be good to record whether the ATBD has been reviewed externally or needs review after creation/upload.
Yes, only the authors and curators need to know who the reviewers are.
The curator will simply email the reviewers to confirm/verify that it has been reviewed and is ready to be made public within APT.
i. No, the curator will simply publish ATBDs that have been verified. We don't need this information on the ATBD.

A couple of other points.

Just for clarification, none of the reviewer information needs to be generated on the PDFs. This is just for our own internal workflows.
It would be good to ask the user if the ATBD has already been: 1) submitted to a journal 2) published in a journal 3) or if they plan to submit to a journal.
This is a little redundant for users completing their ATBDs within the APT interface (i.e., journal details section), but I think it is ok.

@kamicut @frozenhelium I'll break this down into several tickets

I added a few sub-tickets in the tasks list at the top of this ticket

@bwbaker1 this is ready for testing on staging (in about 15 min)

@wrynearson

This looks good in view mode. Meaning I can see the reviewer info.
This looks good in PDF mode. Meaning the reviewer info is not displayed.
The only issue is that I can only add one reviewer. In theory, users should be able to add as many reviewers as they want. When I tested this before (a few sprints ago), I was able to add multiple reviewers. So something changed somewhere.

@bwbaker1 @wrynearson after reviewing @frozenhelium's code and the ticket, I don’t think there was ever a case where there were “multiple reviewers” in that section. We merged in a PR where it was always the case where there was a single reviewer https://github.com/NASA-IMPACT/nasa-apt-frontend/pull/528
Adding multiple reviewers will be a new UI/data component, and would require some work. I suggest that we re-use the existing "Contacts" form in this section to add reviewers. This would add less complexity to the code as the application wouldn't be managing and creating a list of contact information not tied to the existing "Contacts" backend.
To implement, we could re-use the "Roles related to this document" field that to mark the contact as a reviewer, for example ticking the Writing - review & editing checkbox. We could also use an explicit "Mark this contact as a reviewer" checkbox alongside the contact if that's more suitable.
Before implementing, we would need to answer the following questions related to the workflow:

Are "roles related to this document" used for the document presentation in any way? (view mode, journal, document PDF)?
What determines a contact show up in the "contact" section in the presentation? Should it be the simple fact of adding a contact that makes them show up? Or should it be required to select a role for this contact?
If we mark a contact as a reviewer should they also show up in the "Contacts" section in the view mode? If not, then is there a scenario where a contact shows up in the "Contacts" and "Reviewers" sections?

Waiting for your feedback to implement the fix.

The section 9 "Reviewer Information" still shows up on the PDFs. It only needs to be on HTML.

Thanks @bwbaker1. This is in review with https://github.com/NASA-IMPACT/nasa-apt-frontend/pull/569

This is ready for your review @bwbaker1

@wrynearson I am still seeing the reviewer info for both the journal and document PDFs.

We think this was a caching issue. I just checked after updating a document and both the Journal and Document PDFs don't have the Reviewer Information section, but the HTML does

@wrynearson I just checked a document as well....and it worked as expected after making small update to the document. Thanks! I think this ticket is now complete, so feel free to close.


PARQUET-1701: [C++] Stream API: Add support for optional fields

StreamReader and StreamWriter classes can now support schemata with
optional fields.
Additional input/output operators are available using the
arrow::util::optional class in order to indicate whether optional data
was present when reading, or is present when writing.

@wesm

will try to take a look at this within a week if nobody gets to it sooner.

Seems reasonable except for the documentation and 1 style (using an alias for optional).  So I think a committer should take a look @wesm @xhochy @majetideepak

Will look. Are the CI failure legitimate?

The macOS failure is probably https://issues.apache.org/jira/browse/ARROW-7551 (I say clicking on it)

The appveyor failure looks unrelated, trying to rebuild.

@wesm : I do not plan on making any other changes to this pull request unless required.
All the functionality required to support optional fields is in place and I would very much like this functionality to be available in the next release of Arrow.

thanks @gawain-bolton!


protoc-gen-es: 2.0.0 -> 2.2.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for protoc-gen-es is: Protobuf plugin for generating ECMAScript code
meta.homepage for protoc-gen-es is: https://github.com/bufbuild/protobuf-es
meta.changelog for protoc-gen-es is: https://github.com/bufbuild/protobuf-es/releases/tag/v2.2.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.2.2 with grep in /nix/store/bhsjbnhhbx8ig9xwii88av4qvv84m67c-protoc-gen-es-2.2.2
found 2.2.2 in filename of file in /nix/store/bhsjbnhhbx8ig9xwii88av4qvv84m67c-protoc-gen-es-2.2.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

protoc-gen-es

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bhsjbnhhbx8ig9xwii88av4qvv84m67c-protoc-gen-es-2.2.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A protoc-gen-es https://github.com/r-ryantm/nixpkgs/archive/c48160a9a217c4c3333feda9dcaabb625f708529.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c48160a9a217c4c3333feda9dcaabb625f708529#protoc-gen-es

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bhsjbnhhbx8ig9xwii88av4qvv84m67c-protoc-gen-es-2.2.2
ls -la /nix/store/bhsjbnhhbx8ig9xwii88av4qvv84m67c-protoc-gen-es-2.2.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

protoc-gen-es

Maintainer pings
cc @felschr @jtszalay for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 355994 run on x86_64-linux 1

1 package built:

protoc-gen-es

@ofborg build protoc-gen-es


tf error

getting this error.. i suppose something to do with the recent changes in tensorflow ...i am using 1.1.0
ValueError: Attempt to reuse RNNCell <tensorflow.contrib.rnn.python.ops.core_rnn_cell_impl.GRUCell object at 0x7f69f4de3850> with a different variable scope than its first use.  First use of cell was with scope 'DMN/question/rnn/gru_cell', this attempt is with scope 'DMN/input/bidirectional_rnn/fw/gru_cell'.  Please create a new instance of the cell if you would like it to use a different set of weights.  If before you were using: MultiRNNCell([GRUCell(...)] * num_layers), change to: MultiRNNCell([GRUCell(...) for _ in range(num_layers)]).  If before you were using the same cell instance as both the forward and reverse cell of a bidirectional RNN, simply create two instances (one for forward, one for reverse).  In May 2017, we will start transitioning this cell's behavior to use existing stored weights, if any, when it is called with scope=None (which can lead to silent model degradation, so this error will remain until then.)

Just updated the repository to support TF 1.1 and Python 3 so that should fix your error. Let me know if you still have problems.

Thanks


RHODS Operator Hub Listing Rewrite

The RHODS listing in Operator Hub is outdated and inaccurate for the latest version. @erwangranger and I have written a more relevant and engaging listing for the current RHODS, which will be linked.  Suggestions and comments for the listing rewrite are appreciated!
https://docs.google.com/document/d/1pgXExt7LQBPhsANBaMh2sXe0Ay5FyDvAncszCeq7ZMQ/edit?usp=sharing

Moving this to the common location (as this is not a dashboard item) -- I think this is something we can look at from the ODH perspective; not sure how much is actually shared with the RHODS Operator though.
cc @VaishnaviHire

is this something for https://github.com/red-hat-data-services/rhods-operator/blob/main/bundle/manifests/opendatahub-operator.clusterserviceversion.yaml#L221 ?

The above looks like the description for ODH Operator. So, I would say, no.
The proposed text is to update the text seen by people in Operator Hub when they see RHODS.
See this thread for more information: https://redhat-internal.slack.com/archives/C03UA0RLSQM/p1691629637372989

can we transfer this issue to "operator" repo for tracking? I need permission to add "rhods-1.33" label to include it in the verification process....

@zdtsw since you're staying in ODH GitHub org -- I believe you can just use the /transfer command. Harshad has had success.
/transfer opendatahub-operator

Ah would not appear to work in this repo 😞 (ref) -- needs the bot to operate in this repo.
@LaVLaS can we add the bot?

Closing this issue, as we have implemented the changes for RHODS 1.33 https://github.com/red-hat-data-services/rhods-operator/pull/42

/close


Stuck at allocating files

Describe the bug
The launcher hangs at allocating files. It's not frozen, but just won't move to the next stage.
Screenshots

System Information (please complete the following information):

macOS: 13.4 Ventura
Device: Macbook Air M1 2020
CPU: M1
RAM: 8G

Additional context
Add any other context about the problem here.
I'm not sure if SIP needs to be disabled because mine is enabled. Also I installed a bunch of brew packages and I don't know if that affects the launcher.
Logs (if any)
neutralinojs.log

Solved. The server was blocked by my network and using a VPN fixes it.

I was always using VPN but when I finally turned it off it start downloading


initial support for RP2040 (R2 variant)

Config (CF2)
RP2040 port uses a similar mechanism for configuration as the existing STM32 and SAMD51 ports - there is a special designated area in the flash that has a binary with information about pinout and on-board peripherals. However, the area in this case is not in the bootloader, since the bootlaoder is in ROM. Instead, it's at 4k before 1 megabyte, and also at 4k before 2MB, 4MB, etc. That should be relatively resilient against accidental overwrite, however manufacturers should provide a "factory reset" UF2 which contains all these config sections, and possibly a test game. This file can be used to recover after the flash has been overwritten (eg by large files in MicroPython filesystem).
Sample config file is in this branch (in future on master) and you can edit it (and also view) with CF2 patcher
The sample config is using 74HC165 chips for buttons to save pins like in the micro:bit Arcade Shield. However, one can also just use regular pins for buttons.
Testing
Here's a test build for RP2040 Arcade
Go to "Settings -> About -> Experiments" and enable Experimental Hardware. Then "R2" variant should pop up at the bottom of hardware selection list.
Status
What's supported:

SPI screen (no parallel screen, anyway not yet)
sound (using DMA for PWM)
regular and 74HC165 buttons
Jacdac

What's not supported:

WebUSB flashing

Is there any update to this pullrequest? Thanks

@sabas1080 it should be close to finished now! check out the updated description


Firebase Cloud Messaging on iOS not calling onMessage, onResume

Steps to Reproduce
I followed the steps of installing FCM for Android an iOS and i can receive notifications on both, however only on Android i get triggered onMessage, onResume and onLaunch while on iOS i just receive the onLaunch callback.
I'm using Cloud functions to send the notifications and the structure of the message is the following:
{
        notification: {
            title: header,
            body: text
        },
        data: {
            type: '2',
            tag: tag,
            click_action: 'FLUTTER_NOTIFICATION_CLICK',
	   content: questions
        },
        android: {
            notification: {
                icon: "ic_notification"
            }
        }
}

Logs
Flutter Doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v0.4.4, on Mac OS X 10.13.4 17E202, locale es-MX)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4)
[✓] Android Studio (version 3.1)
[✓] VS Code (version 1.24.0)
[✓] Connected devices (1 available)

• No issues found!

@Hixie

I did more testing and found out that on iOS it triggers onLaunch when the app is killed but onResume and onMessage are not being called

There was a conflict between firebase messaging and flutter local notifications plugin, so i had to remove flutter local notifications to make it work as intended

still same here. any progress?

+1, our team stumbled upon this as well

+1 here too - iOS onMessage not firing - everything else working as expected including Android. No other notifications packages are being used in my case.

we're facing the same issue as well, onMessage and onLaunch not firing whereas the onResume fires successfully (no other packages used apart from firebase_messaging), I am not really sure what the problem. Do we need to reopen this issue so that the flutter team will have a look into this one? Is this something to do with recent Xcode and iOS updates or something we're missing in the API's?

+1, our team stumbled upon this as well

hi @werdlv have you resolved the issue or have you got any workaround so that we can resolve this?

I have exactly the same issue. Everything works as expected on Android but iOS only receives notifications but not the data part. onMessage fires on Android but not on iOS.
Any new light on this?

Any news on this?
I have the same Problem, I'm using firebase_messaging 3.0.0 and flutter_local_notifications 0.5.0 and don't get the onMessage, onResume calls on IOS.
When I uninstall the local_notification package, firebase_messaging get the calls again. On Android this works just fine, but on IOS not.

Could you please report on https://github.com/mitchhymel/local_notifications/issues to change the conflicting method name?

Thats not the plugin I'm using, sorry for lack of clearity!
Thats the plugin I mean with the already open Issue: https://github.com/MaikuB/flutter_local_notifications/issues/111.
And that issue leads to an open flutter issue, which is opened by the author of the flutter_local_notifications plugin: https://github.com/flutter/flutter/issues/22099

In my case onResume is getting called, but onLaunch and onMessage are not getting called. Pretty random behavior, this? Has anyone found a solution?

PHEW!!! After a couple of hours of debugging I figured out that all three, viz., onLaunch, onResume and onMessage are getting called. So there's no fundamental issue.
The issue is that on iOS, the message body is present in msg['aps']['alert'] where msg is the Map passed to the above three functions.
On Android, the message body is present in msg['notification']['body'].
Since this isn't clearly documented (certainly not in the firebase_messaging plugin's README), I had just used the Android version. On iOS, looks like it used to result in an exception which wasn't getting logged anywhere in the debug console.
Now this is how I grab the message body, and all the three functions are working fine:
if (Theme.of(context).platform == TargetPlatform.iOS)
    _message = msg['aps']['alert'];
else
    _message = msg['notification']['body'];

Note: I'm just testing my app right now, so I'm sending notifications from the Firebase console. Hopefully things won't break when I move stuff to a cloud function :-)
Suggestion to Flutter/Firebase team: please improve the documentation for the firebase_messaging plugin.

@kbrmimbyl might be #23148

@zoechi #23148 appears different: the inability to write a single parse function for onMessage and onResume.

@kbrmimbyl If you think it's different, please create a new issue with all the information that allows to reproduce. A minimal reproduction project and how you send the message and what it looks like when you send it and when you receive it on iOS or Android.

I wish @kbrmimbyls solution worked for me. I have every hook firing on Android, but none firing on iOS. This is painful

@zoechi Just created #28196

@nayanbhana Checkout #28196

Has someone fixed this? I also need to show local notifications when the app is in foreground but when I use both firebase_messaging and local_notificatins, the iOS remote notificatins stops working.

onMessage is not working, I'm just printing the message to console, but nothing is getting printed out.

event onMessage is not working!

I am using firebase_messages 5.0.3 and
1- onMessage(), onLaunch(), onResume are working as intended on Android
2- onMessage() is working on iOS simulator iphoneX running iOS but fails on iphone 6
3- onLaunch and onResume are not working on the simulator (I assume because a physical device is required)
4- onMessage(), onLaunch(), onResume not working on physical device - iphone 6 running iOS 12.2
I am assuming since onMessage is firing on the simulator then my iOS related setup - APNs and keys and all of that is correct.
Please do let me know if there are anything that I need to do in order to get this working

onMessage() is not working on iOS.
I am not using flutter local notification.
Any update?

A quick update - just to make sure I didn't mislead anyone with my comment above.
Now everything is working fine, I had a discrepancy  in my package name and my bundle id.

I had same problem, I using the real device to test.
[✓] Flutter (Channel master, v1.8.2-pre.42, on Mac OS X 10.14.5 18F132, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.3)
[✓] VS Code (version 1.36.1)
[✓] Connected device (2 available)
• No issues found!
And my plugin is
firebase_messaging: ^5.1.1
flutter_local_notifications: ^0.7.1+3
And I using the firebase cloud messaging to test.
Android Pixel 3 XL
onMessage Working
onResume Working
onLaunch Working
iOS iPhone 6 +
onMessage Fail
onResume Working
onLaunch Working
iOS start the app can't get onMessage.

I had same problem, I using the real device to test.
[✓] Flutter (Channel master, v1.8.2-pre.42, on Mac OS X 10.14.5 18F132, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.3)
[✓] VS Code (version 1.36.1)
[✓] Connected device (2 available)
• No issues found!
And my plugin is
firebase_messaging: ^5.1.1
flutter_local_notifications: ^0.7.1+3
And I using the firebase cloud messaging to test.
Android Pixel 3 XL
onMessage Working
onResume Working
onLaunch Working
iOS iPhone 6 +
onMessage Fail
onResume Working
onLaunch Working
iOS start the app can't get onMessage.

At least for me, onMessage on iOS is now working fine.
Guide I used : https://medium.com/flutterpub/enabling-firebase-cloud-messaging-push-notifications-with-flutter-39b08f2ed723.

@rekubot
OK so my issue was that I had the incorrect bundle Id written on XCode and it didnt match my Firbase Project.
My advice would be to double check all of these values everywhere on the xcode, app store connect  firebase and so to make sure the bundle ID is correct everywhere.. mine was changed for some reason when I changed a team or due to finger clicking by mistake.
Now if you are receiving the notifications and nothing is happening from your callbacks I would suspect that this might be more related to your callbacks code and not the notification service itself.
Try to print the data from your onMessage and see if anything is happening .. I know that the data model for the message is different between Android and iOS .. is everything working on Android?

Guys I'm also having this issue even using the latest firebase messaging  (5.1.6) and flutter master channel (1.10.7-pre.79). Any news or fix on that?

if (Theme.of(context).platform == TargetPlatform.iOS)
    _message = msg['aps']['alert'];
else
    _message = msg['notification']['body'];

It should be _message = msg['aps']['alert']['body'] on iOS

Same issue on iOS. On the simulator all the events are being fired. On the device the push notification is received but no event is received so we cannot receive simple data for things like new instant messages.

Same issue on iOS. Using last stable channel and fcm 6.0.9

I also ran 'pod install' command in  cd /users/user/dev/flutter/myapp/ios

removing this line in AppDelegate fixed it for me per #1056
//    if #available(iOS 10.0, *) {
//      UNUserNotificationCenter.current().delegate = self as UNUserNotificationCenterDelegate
//    }

barees63 - can you show your complete AppDelegate class?  I removed that line, and I'm still not getting callbacks.

My issue was specifically, onMessage not called on physical device when app in foreground, onResume and onLaunch were working.
@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
override func application(
_ application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
GMSServices.provideAPIKey("xxxx")
//    https://github.com/FirebaseExtended/flutterfire/issues/1056
//    if #available(iOS 10.0, *) {
//      UNUserNotificationCenter.current().delegate = self as UNUserNotificationCenterDelegate
//    }
GeneratedPluginRegistrant.register(with: self)
return super.application(application, didFinishLaunchingWithOptions: launchOptions)

}
}

@barees63 if you remove those 3 lines, ios 10 and above will not receive notification in foreground


Fix UnicodeDecodeError permanently

https://docs.python.org/3/library/codecs.html#error-handlers
This detects a multibyte UTF8 character, and doesn't return if its incomplete.
If there otherwise wasn't enough tokens or the model somehow returns invalid bytes, we use errors="ignore" to remove invalid characters.
Ascii example:

'German ß, ♬'.encode(encoding='ascii', errors="ignore")
b'German , '

But there will never be thrown a decode or encode error.
Fixes:
https://github.com/abetlen/llama-cpp-python/issues/36
https://github.com/abetlen/llama-cpp-python/issues/57
https://github.com/abetlen/llama-cpp-python/issues/100
https://github.com/abetlen/llama-cpp-python/issues/116

Thanks @SagsMug, I'll take a look at this and weigh against #55 I think this better preserves streaming functionality.
So is this bug just due to the fact that the Llama vocabulary includes token which are not valid utf-8 strings?

Thanks @SagsMug, I'll take a look at this and weigh against #55 I think this better preserves streaming functionality.
So is this bug just due to the fact that the Llama vocabulary includes token which are not valid utf-8 strings?

According to this:
https://github.com/ggerganov/llama.cpp/pull/73#issuecomment-1465469224
It does indeed stem from some characters needing multiple tokens.
They supposedly fixed this by changing the model converter in https://github.com/ggerganov/llama.cpp/pull/79
But given we still encounter this issue, maybe not.
> import llama_cpp
> lparams = llama_cpp.llama_context_default_params()
> ctx = llama_cpp.llama_init_from_file("./models/7B/ggml-model-q4_0.bin", lparams)
> def _tokenize(prompt, bos=True):
 _arr = (llama_cpp.llama_token * (len(prompt) + 1))()
 _n = llama_cpp.llama_tokenize(ctx, prompt.encode("utf8"), _arr, len(_arr), bos)
 return _arr[:_n]
> _tokenize("😀", False)
llama_tokenize: too many tokens
[]

I would speculate that the only real solution is to save invalid tokens until a valid output occurs.
But this works alright until that happens.

Thanks @SagsMug, I'll take a look at this and weigh against #55 I think this better preserves streaming functionality.
So is this bug just due to the fact that the Llama vocabulary includes token which are not valid utf-8 strings?

I have added a check that detects a multi-byte UTF8, and waits accordingly.
It

Thanks @SagsMug, I'll take a look at this and weigh against #55 I think this better preserves streaming functionality.
So is this bug just due to the fact that the Llama vocabulary includes token which are not valid utf-8 strings?

I have tried to address UTF8 properly by detecting multibytes and waiting for their completion.
Please check that it's satisfactory.
I have also kept the errors = "ignore" as a precaution.

@SagsMug can we reduce the use of errors="ignore" to just bare minimum to catch detokenize issues, ie. we probably don't need it for prompts and such.

@SagsMug can we reduce the use of errors="ignore" to just bare minimum to catch detokenize issues, ie. we probably don't need it for prompts and such.

I have removed a bunch of cases and add a test for this.
Im pretty sure the rest are necessary, but please check

Because of errors from Llama.generate() and low level api, I use below code snippet.
How about to integrate it?
                if not input_noecho:
                    for id in tokens:
                        detoken = llama_cpp.Llama.detokenize(self=self,tokens=[id])
                        byte_list.append(detoken)
                        gen_tokens += 1
                        try:
                            combine = b''.join(byte_list)
                            letter = combine.decode("utf-8")
                            # print(letter, end="",flush=True)
                            # yield print(letter, end="",flush=True)
                            yield letter
                            if gen_tokens > n_predict:
                                gen_tokens = 0
                                # llama_cpp.llama_free()
                                break
                            byte_list = []

                        except:
                            pass


Update dependencies to latest versions / Add Jest / Use prepare instead of prepublish

This PR includes the following changes

Update all dependencies to latest versions, including @types
Add Jest as test runner
Use enzyme instead of react-dom/test-utils
Use expect(jest assertions) instead of assert
Fix some test cases
Use prepare instead of prepublish. prepublish was deprecated in new npm version

Sorry for delaying here.  We've been discussing the best way to deal with the react 16 componentWillMount issue for the last few days and wanted to close on that before taking your submission.  Thanks for the patience. :)  We will check this out in the morning.

@deregtd I've merged last updates here. Above I described what this PR contains. If these changes make sense, you can review them. Thanks

After a quick pass on this:

What is the advantage of changing to jest for test running?  We didn't have any complaints with mocha.
We need to have a way to run tests through the web in test.html.  Debugging issues in Chrome is far better than printf().

@deregtd

What is the advantage of changing to jest for test running? We didn't have any complaints with mocha.
We need to have a way to run tests through the web in test.html. Debugging issues in Chrome is far better than printf().

Ok, I understood, I'll remove this PR. When I was updating dependencies, I thought that would be great to have test runner in order to avoid making every time build to run tests and check it in browser., Jest is a great tool which almost covers all cases which need to write and run tests, Mocha also it good tool, however, Jest more natural for React world. Also, enzyme has great API  to mount components and get/set state/props. Also, I thought that would be better to add such work to CI which will run tests, make build and publish a new version, and avoid to do it by hand. I think, to debug library we can add Webpack dev server and use it for development purposes.

We can do both -- in the Skype repository, we migrated from mocha to jasmine for our unit tests, and utilize phantomjs for in-console tests through CI, and a webpack build for browser tests through a test.html file (similar structure to here.)  So, if you're just looking for a way to build the tests through CI, I think both can be accommodated.  I'm not attached to jasmine vs jest or anything -- they both look like they have similar syntax.  We just want to make sure that tests are still runnable via web as well as console.  So if you can take this structure and re-add the ability to do the web build for in-browser testing, then that's fine by us as well.

@deregtd
There is the branch where were added there following tools:

Jasmine,
Karma + Chrome
Travis CI


Cannot see TSI Environment

Describe the bug
I have deployed the IIoT Platform, and have enabled some OPC UA endpoints to send data.  I see the data coming into the IoT Hub.  When I go to TSI I get a message that says "There are no environments available".
To Reproduce
Steps to reproduce the behavior:

Install the Industrial IoT Platform
Enable some OPC UA variables through the UI
Go to TSI in the portal
Click on "Go to TSI Explorer"
Get message "There are no environments available" (see attached)

Expected behavior
Ability to view OPC data in TSI
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: chrome

I think you've missed assigning yourself data access rights. Please have a look here: https://github.com/Azure/Industrial-IoT/blob/master/docs/tutorials/tut-timeseriesinsights.md

Thanks @cristipogacean !  I missed that in the documentation.


Add option to block Osram Lightify individual lights

Added option to block Osram Lightify individual lights in the same way that groups can be
Description:
Currently the Osram Lightify platform can be configured to block the importing of groups. This PR allows one to configure the platform so that individual lights can be blocked (and thus only groups imported).
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#5368
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

Hi @austinlg96,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Thanks. Glad to contribute.


PromptGPT - AI assistant for refining user prompts to maximize GPT-4 interaction.

https://chat.openai.com/g/g-p0jlP3Tcq-promptgpt

Merged


lazyLoad triggers multiple image downloads on Safari

When using lazyLoad in current Safari (Version 11.1 (136<IP_ADDRESS>.2)) I see that images are loaded multiple times.
In the Codebox Example below I see them being loaded twice or three times. But in another example in my application I see up to 11 simultaneous loads.
CodeSandBox Example

Did just see, that this is a duplicate of #1170. Closing this one.


Do not recompile/reboot projects that were not changed

No more needed as we don't compile the projects on this machine.


Adding test for line wrap.

This test ensures we can enable and disable line wrap.

Look good; thanks!


Add support for log files

Some features, like alert, benefit from a log file.

Fixed in https://github.com/nozel-org/freebsd-serverbot/commit/881c318e0aeac671a045b2701ac40d86dd807d49.


realsense2_camera building error

Have followed the tutorial in order to get this working but have run into some issues. Have followed this tutorial for the SDK - https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
Then attempted to get the realsense2_camera package working but when executing catkin_make there are errors that come up (as shown below).
What can I do to fix this?

CMake Warning at realsense2_camera/CMakeLists.txt:29 (find_package):
By not providing "Findrealsense2.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"realsense2", but CMake did not find one.
Could not find a package configuration file provided by "realsense2" with
any of the following names:
realsense2Config.cmake
realsense2-config.cmake

Add the installation prefix of "realsense2" to CMAKE_PREFIX_PATH or set
"realsense2_DIR" to a directory containing one of the above files.  If
"realsense2" provides a separate development package or SDK, be sure it has
been installed.
CMake Error at realsense2_camera/CMakeLists.txt:31 (message):
Intel RealSense SDK 2.0 is missing, please install it from https://github.com/IntelRealSense/librealsense/releases

Hi @FYPBois ,
Can you describe how did you try to make the realsense2_camera package working, so that I'll try to reconstruct the errors? Did you follow the installation guide at https://github.com/intel-ros/realsense ?
What OS do you use? Can you provide the list of commands you used? log?


feat(feature-toggle-jsx): add new withoutFeature HoC

closes #15

Pull Request Test Coverage Report for Build 209

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 208:
0.0%

Covered Lines:
96

Relevant Lines:
96

💛  - Coveralls

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Steam release support

Opening an issue for the newly released Steam update for the game, which added a tour mode but possibly didn't do anything to fix the framerate caps, FOV limitations etc.
Update: I checked out the Steam release, and true enough the fps cap is still there, with cutscenes animating at a, uh, cinematic update rate.
The fix seems to still work, as framerate appeared to no longer be capped at 62, but instead it went up over 100. I tried the tour mode, for example, and it seemed to settle at 120fps (I'm playing at 4K). Huh.

I have been using it with the Steam release as well, and so far have not ran into any issues. I am playing at 1440p and manually locked the game to 144hz in case to try and prevent additional jank. Seems to be running great so far.


parquet: "not yet implemented" error when codec is actually implemented but disabled

Describe the bug
When a codec is disabled (with parquet = { version = ..., default-features = false }) and such a codec is requested, the error message is incorrect
To Reproduce
"The codec type XXX is not supported yet"
Expected behavior
"The codec type XXX is disabled" or "feature YYY is disabled"

label_issue.py automatically added labels {'parquet'} from #5521


Update clap to 3.1

@markmandel This needs to be merged first as it is blocking other PRs from passing CI.


Execution messages and results printed out of order in messages window

Azure Data Studio Version:

Version: 1.16.1 (user setup)
Commit: 16801c522df68e63218b39ccb5b4a7431f9bf667
Date: 2020-03-23T22:08:06.892Z
VS Code: 1.42.0
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:
Execute the following in any query window against a SQL server instance
drop schema if exists temp_should_not_exist
go

create schema temp_should_not_exist
go

drop schema if exists temp_should_not_exist
go

The expected output is:
7:56:12 PM Started executing query at Line 1
Commands completed successfully.

7:56:12 PM Started executing query at Line 3
Commands completed successfully.

7:56:12 PM Started executing query at Line 6
Commands completed successfully.

Total execution time: 00:00:00.130

Actual output is
7:56:12 PM Started executing query at Line 1
7:56:12 PM Started executing query at Line 3
7:56:12 PM Started executing query at Line 6
Commands completed successfully.
Commands completed successfully.
Commands completed successfully.
Total execution time: 00:00:00.130

Notes:
Originally reported:
https://twitter.com/casperOne/status/1243992443076427779

Ported fix to release/1.18


Pyramid view configuration could not register the view route

When I try the pets swagger specification with simple pyramid application. I could not get view configuration working. I keep get the following error:
pyramid.exceptions.ConfigurationExecutionError: <class 'pyramid.exceptions.ConfigurationError'>: No route named api.pets.get found for view registration
Here are the pyramid configuration, view configuration and swagger example I used.
init.py:
from pyramid.config import Configurator

def main(global_config, **settings):
    """ This function returns a Pyramid WSGI application.
    """
    settings['pyramid_swagger.swagger_versions'] = ['2.0']
    config = Configurator(settings=settings)
    config.include('pyramid_chameleon')
    config.include('pyramid_swagger')
    config.add_static_view('static', 'static', cache_max_age=3600)
    config.add_route('home', '/')
    config.scan()
    return config.make_wsgi_app()

views.py:
from pyramid.view import view_config

@view_config(route_name='home', renderer='templates/mytemplate.pt')
def my_view(request):
    return {'project': 'mypramid'}

@view_config(route_name='api.pets.get')
def get_pets(request):
    # Returns thing_id as an int (assuming the swagger type is integer)
    pets_id = request.swagger_data['id']
    return {'project': 'mypramid'}

api_docs/swagger.json:
{
    "swagger": "2.0",
    "info": {
        "version": "1.0.0",
        "title": "Swagger Petstore (Simple)",
        "description": "A sample API that uses a petstore as an example to demonstrate features in the swagger-2.0 specification",
        "termsOfService": "http://helloreverb.com/terms/",
        "contact": {
            "name": "Swagger API team",
            "email"<EMAIL_ADDRESS>            "url": "http://swagger.io"
        },
        "license": {
            "name": "MIT",
            "url": "http://opensource.org/licenses/MIT"
        }
    },
    "host": "localhost:6543",
    "basePath": "/api",
    "schemes": [
        "http"
    ],
    "consumes": [
        "application/json"
    ],
    "produces": [
        "application/json"
    ],
    "paths": {
        "/pets": {
            "get": {
                "description": "Returns all pets from the system that the user has access to",
                "operationId": "findPets",
                "produces": [
                    "application/json",
                    "application/xml",
                    "text/xml",
                    "text/html"
                ],
                "parameters": [
                    {
                        "name": "tags",
                        "in": "query",
                        "description": "tags to filter by",
                        "required": false,
                        "type": "array",
                        "items": {
                            "type": "string"
                        },
                        "collectionFormat": "csv"
                    },
                    {
                        "name": "limit",
                        "in": "query",
                        "description": "maximum number of results to return",
                        "required": false,
                        "type": "integer",
                        "format": "int32"
                    }
                ],
                "responses": {
                    "200": {
                        "description": "pet response",
                        "schema": {
                            "type": "array",
                            "items": {
                                "$ref": "#/definitions/pet"
                            }
                        }
                    },
                    "default": {
                        "description": "unexpected error",
                        "schema": {
                            "$ref": "#/definitions/errorModel"
                        }
                    }
                }
            },
            "post": {
                "description": "Creates a new pet in the store.  Duplicates are allowed",
                "operationId": "addPet",
                "produces": [
                    "application/json"
                ],
                "parameters": [
                    {
                        "name": "pet",
                        "in": "body",
                        "description": "Pet to add to the store",
                        "required": true,
                        "schema": {
                            "$ref": "#/definitions/newPet"
                        }
                    }
                ],
                "responses": {
                    "200": {
                        "description": "pet response",
                        "schema": {
                            "$ref": "#/definitions/pet"
                        }
                    },
                    "default": {
                        "description": "unexpected error",
                        "schema": {
                            "$ref": "#/definitions/errorModel"
                        }
                    }
                }
            }
        },
        "/pets/{id}": {
            "get": {
                "description": "Returns a user based on a single ID, if the user does not have access to the pet",
                "operationId": "findPetById",
                "produces": [
                    "application/json",
                    "application/xml",
                    "text/xml",
                    "text/html"
                ],
                "parameters": [
                    {
                        "name": "id",
                        "in": "path",
                        "description": "ID of pet to fetch",
                        "required": true,
                        "type": "integer",
                        "format": "int64"
                    }
                ],
                "responses": {
                    "200": {
                        "description": "pet response",
                        "schema": {
                            "$ref": "#/definitions/pet"
                        }
                    },
                    "default": {
                        "description": "unexpected error",
                        "schema": {
                            "$ref": "#/definitions/errorModel"
                        }
                    }
                }
            },
            "delete": {
                "description": "deletes a single pet based on the ID supplied",
                "operationId": "deletePet",
                "parameters": [
                    {
                        "name": "id",
                        "in": "path",
                        "description": "ID of pet to delete",
                        "required": true,
                        "type": "integer",
                        "format": "int64"
                    }
                ],
                "responses": {
                    "204": {
                        "description": "pet deleted"
                    },
                    "default": {
                        "description": "unexpected error",
                        "schema": {
                            "$ref": "#/definitions/errorModel"
                        }
                    }
                }
            }
        }
    },
    "definitions": {
        "pet": {
            "required": [
                "id",
                "name"
            ],
            "properties": {
                "id": {
                    "type": "integer",
                    "format": "int64"
                },
                "name": {
                    "type": "string"
                },
                "tag": {
                    "type": "string"
                }
            }
        },
        "newPet": {
            "required": [
                "name"
            ],
            "properties": {
                "id": {
                    "type": "integer",
                    "format": "int64"
                },
                "name": {
                    "type": "string"
                },
                "tag": {
                    "type": "string"
                }
            }
        },
        "errorModel": {
            "required": [
                "code",
                "message"
            ],
            "properties": {
                "code": {
                    "type": "integer",
                    "format": "int32"
                },
                "message": {
                    "type": "string"
                }
            }
        }
    }
}

You have not declared any route with the name api.pets.get so pyramid doesn't know what route to associate with the view. You need a line similar to config.add_route('home', '/') in your main.
http://docs.pylonsproject.org/projects/pyramid/en/latest/narr/urldispatch.html is some good reading. There are some examples at the bottom of the page.

Closing as solved, thanks for the detailed report :)

@striglia @johnschultz
Just following up on this bug and my chats yesterday in Gitter.
I think the Quickstart doc is somewhat misleading insofar as the view_config(route_name='api.things.get') statement in this section seems to suggest that pyramid_swagger is populating the routes automagically. I just spent three or four hours messing with the code just to discover that -- oh shit! -- I still have to set the routes up myself. The docs probably need to clearly state that, no, pyramid_swagger doesn't set the routes up for you.


Have the converter show a popup window when there are issues that couldn't automatically be fixed

Is your feature request related to a problem? Please describe.
There are rare cases where things have to be changed - like with PlaySound() -, but the changes are too difficult to automatically fix.
Describe the solution you'd like
Show a popup window when there are issues that couldn't automatically be fixed.
Use popup_scrolled from PySimpleGUI for this.

Done: d832e75


Missing '(' after 'if' in if statement.

desc
run sh to release package to npm registry in window in github workflows.
exp
run bash script done
act
Missing '(' after 'if' in if statement.

why
it may not use bash default in window .
fix
set 'shell: bash' in relative step in github workflow


remove incorrect error check when sending a packet

There's no need for a check if more than protocol.MaxTrackedSentPackets packets were sent. There are certain situations where we allow (via SendingAllowed()) sending of more packets, and we shouldn't throw an error when the session then actually sends these packets.

Codecov Report

Merging #1219 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1219      +/-   ##
==========================================
+ Coverage   91.11%   91.13%   +0.02%
==========================================
  Files         114      114
  Lines        7828     7823       -5
==========================================
- Hits         7132     7129       -3
+ Misses        465      464       -1
+ Partials      231      230       -1

Impacted Files
Coverage Δ

internal/ackhandler/sent_packet_handler.go
96.33% <100%> (-0.04%)
:arrow_down:

session.go
80.72% <100%> (+0.27%)
:arrow_up:

Continue to review full report at Codecov.

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


fort-agent publish doesn't work

I get this:
> forta-agent publish

building agent image...
ERROR: Error: error building agent image: unknown flag: --load
See 'docker --help'.
...
...

From cursory scan, this PR looks like a cause of the issue: https://github.com/forta-network/forta-bot-sdk/pull/193

@abhimanyusinghgaur When possible, could you also run this command?
> docker buildx version

> docker buildx version
docker: 'buildx' is not a docker command.
See 'docker --help'

hey @abhimanyusinghgaur :) buildx comes bundled with Docker Desktop. from your console output, it seems like you do not have it installed. please see the docs here to install buildx: https://docs.docker.com/build/buildx/install/

@abhimanyusinghgaur please let us know if you need any help with that process ^