Add networking-daemonsets feature

Deploy Calico and Flannel networking as a daemonset with kubernetes API as backing store. Removes the need for nodes connecting to etcd and frees up node podCIDR leases faster -addressing cluster role issue: coreos/flannel#954.
Experimental feature, disabled by default.
Kubernetes Controllers become responsible for allocating node cidrs.
Switch between calico+flannel (canal) or flannel.
Fast roll out into existing clusters with minimal disruption.
Optional calico typha service for easing load on apiservers in large clusters.

I need to update the tests with the expectation of the NetworkingDaemonSets type which gets set up with default values.

Codecov Report

Merging #1195 into master will increase coverage by 0.14%.
The diff coverage is 90%.

@@            Coverage Diff             @@
##           master    #1195      +/-   ##
==========================================
+ Coverage    36.2%   36.34%   +0.14%
==========================================
  Files          63       63
  Lines        3823     3833      +10
==========================================
+ Hits         1384     1393       +9
- Misses       2224     2225       +1
  Partials      215      215

Impacted Files
Coverage Δ

model/userdata.go
60% <0%> (-1.02%)
:arrow_down:

core/controlplane/config/config.go
62.39% <100%> (+0.4%)
: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 7195c04...d0b6895. Read the comment docs.

Or create it just for this settings?

This is what I meant!
I'll create separate issues for migrating others.

Hi, I've updated the settings to kubernetes.networking.selfhosting, squashed a couple of bugs, and merged the latest changes.  I have new versions of the template files and these seem to be conflicting and not sure how to clear them.
Is their a way to select my versions?  Can you do that?

Awesome! I would heart this PR more if I could. I believe this will resolve https://github.com/kubernetes-incubator/kube-aws/issues/704 as well which I would need to work on soon. Might be worth commented it as experimental in cluster.yaml?

@davidmccormick Thank you so much for all the your awesome works. I've reviewed this again, and am happy to get this merged 👍

Did someone test this?

I did lots of testing of it - are you having a particular issue?

We're having issues creating a cluster from master and looks related with canal. I'll try to collect as much logs as possible and post it here asap

Hey i am a colleague from @jorge07 . Yesterday we were doing some testing with the master branch and we have found that the cluster was not  able to run containers correctly. We are running the cluster without self-hosting the network .We have been looking logs around, and the problem was that kubelet was not able to locate cni binaries.
Apr 11 10:42:10 ip-10-0-2-59.us-east-2.compute.internal kubelet-wrapper[1410]: E0411 10:42:10.546050    1410 cni.go:259] Error adding network: failed to find plugin "loopback" in path [/opt/loopback/bin /opt/cni/bin]
Apr 11 10:42:10 ip-10-0-2-59.us-east-2.compute.internal kubelet-wrapper[1410]: E0411 10:42:10.546706    1410 cni.go:220] Error while adding to cni lo network: failed to find plugin "loopback" in path [/opt/loopback/bin /opt/cni/bin]
Apr 11 10:42:10 ip-10-0-2-59.us-east-2.compute.internal kubelet-wrapper[1410]: E0411 10:42:10.547302    1410 cni.go:259] Error adding network: failed to find plugin "loopback" in path [/opt/loopback/bin /opt/cni/bin]
Apr 11 10:42:10 ip-10-0-2-59.us-east-2.compute.internal kubelet-wrapper[1410]: E0411 10:42:10.551897    1410 cni.go:220] Error while adding to cni lo network: failed to find plugin "loopback" in path [/opt/loopback/bin /opt/cni/bin]

After taking a look basically i have found that the kubelet system unit basically is mounting the host path /opt/cni/bin inside the kubelet container, this is causing that the path of the container is override with the host path and the kubelet is not able to found the cni binaries.
https://github.com/kubernetes-incubator/kube-aws/blob/3f116956373f6fa817618b257b4479a8cb464b45/core/controlplane/config/templates/cloud-config-worker#L329-L330
This is the output of one of the nodes that currently are not working correctly:
core@ip-10-0-2-59 /opt/cni/bin $ rkt list
UUID		APP		IMAGE NAME				STATE		CREATED		STARTED		NETWORKS
9d5945e6	awscli		quay.io/coreos/awscli:master		exited garbage	1 hour ago	1 hour ago
9f0dfd23	flannel		quay.io/coreos/flannel:v0.10.0		exited		1 hour ago	1 hour ago
eadd1353	flannel		quay.io/coreos/flannel:v0.10.0		running		1 hour ago	1 hour ago
f1dcc1fc	hyperkube-amd64	k8s.gcr.io/hyperkube-amd64:v1.9.1	running		59 minutes ago	59 minutes ago
core@ip-10-0-2-59 /opt/cni/bin $ sudo rkt enter f1dcc1fc
enter: no command specified, assuming "/bin/bash"
root@ip-10-0-2-59:/# ls /opt/cni/bin
root@ip-10-0-2-59:/#

If we delete the argument from the unit then the containers began to run correctly and on the kubelet container we can see the binaries:
core@ip-10-0-1-182 /usr/lib64/systemd $ sudo rkt enter 4cd0af93
enter: no command specified, assuming "/bin/bash"
root@ip-10-0-1-182:/# ls /opt/cni/bin
bridge	dhcp  flannel  host-local  ipvlan  loopback  macvlan  portmap  ptp  sample  tuning  vlan
root@ip-10-0-1-182:/#

Hi thanks for the info - I will have a look at making the mount dependent on the networking selected.  I'm guessing that you are not running with calico?  as this would have installed the cni binaries as part of its bootstrap.

Hi all,
I've opened an issue #1232 without noticing this discussion.   (Thanks @kevtaylor for notifying me)
I'll keep #1232 open for users who search issues with ContainerCreating, so please include Close #1232 in your commit message when you create a fix commit for this problem in the future.
I'll also keep investigating it.

Yep not using calico. I have just try some changes, modifying the template, but then i am getting and error in relation but then i am getting some strange failure. If i go through the templates and i modify the mount, then i am getting an error in relation  to the signature verification of the image.
Apr 11 13:05:52 ip-10-0-2-229.us-east-2.compute.internal kubelet-wrapper[2258]: run: signature verification for docker images is not supported (try --insecure-options=image)

Yep not using calico. I have just try some changes, modifying the template, but then i am getting and error in relation but then i am getting some strange failure. If i go through the templates and i modify the mount, then i am getting an error in relation  to the signature verification of the image.
Apr 11 13:05:52 ip-10-0-2-229.us-east-2.compute.internal kubelet-wrapper[2258]: run: signature verification for docker images is not supported (try --insecure-options=image)

Thanks, it looks like I introduced this bug with cni after my flannel testing.  I'm testing an update to the cloud-config that copies the binaries into the host /opt/cni/bin directory.  I need to keep this mounted so that users can switch from legacy flannel/calico mode to the self-hosting daemonsets with minimal cluster disruption.


Add retries to outbound traffic test

Occasionally the tests are getting 503s, which I suspect is due to just
not waiting long enough. This adds the standard retry we use in other
tests to attempt to deflake it a bit.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/integration/pilot/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/integration/pilot/OWNERS [howardjohn,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test e2e-simpleTests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simpleTests-master

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-framework-local-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-local-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-framework-local-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-local-presubmit-tests-master

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-framework-local-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-local-presubmit-tests-master

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

prow/e2e-mixer-no_auth.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test e2e-mixer-no_auth-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-framework-local-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-local-presubmit-tests-master

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

prow/e2e-mixer-no_auth.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test e2e-mixer-no_auth-master

prow/integ-framework-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

prow/integ-framework-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test e2e-mixer-no_auth-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

prow/integ-framework-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test e2e-mixer-no_auth-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

prow/integ-framework-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-framework-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test e2e-mixer-no_auth-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test istio-unit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
c5404765fe6f96a613e29203af3418dc5f79d6fc
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all


adding QueryGranularity to segment metadata

and optionally expose same from segmentMetadata query via "query_granularity" analysis type

👍

@himanshug mostly looks good but I think the result return format can be more useful

👍

@himanshug merge conflicts

👍 , after https://github.com/druid-io/druid/pull/2873#discussion_r61920354 & travis


Bug Report: Game crashes whenever you try to load an old chart

I tried to play some old mods like ronald mc donald's mod or Scarlet police on Ghetto patrol (https://gamebanana.com/mods/46238) but the game crashes everytime i try to play those mods
Version 1.6 (most stable recent)

issue with the audio. also what the notes doing

they don't fit the size for the skin, same happens with other skins

I have no idea here lol

I just realized that the main problem was because Kade Engine uses OGG files, and the audio files from these mods uses another type of file, basically just export as OGG with Audacity
The problem with the arrows is due to the change of place, not a big deal


side menu not working in scadnano.org/dev

Although the side menu works on local host, this error shows up on the console when loading into scadnano.org/dev.

The code seems to run correctly if you webdev serve the dev branch as a local host


Ctrl-T broken: Quotation marks around result for fish shell

Category

[X] fzf binary
[ ] fzf-tmux script
[X] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[ ] Linux
[X] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[ ] bash
[ ] zsh
[X] fish

All the bindings work as expected apart from Ctrl-T for file search which wraps the result in quotation marks.
I tried to add the "-e" flag to __fzfcmd.fish in .config/fish/functions but this did not help. Any ideas? Because the wrapping quotations are breaking the whole key bindings for me.
I installed fzf via homebrew and the fish fzf plugin using fisherman.

As far as I know, it only wraps when the selected entry contains spaces or characters that need to be escaped. Are you saying that it wraps unconditionally?


Abbreve forms

What issue are you facing? Missing Abbreviation
Which slang/feature/bug? :wydm
Bug description: What do you mean

wdym already exists in our records. Closing this.


Unable to see the result:

Hello,
When I try the DETIC model. I do not see any result : It seems labelled images are zero.
person
Loading pretrained CLIP
/media/csverma/M2Disk/Projects/CompVis/ObjectDetection/AutoDistill/autodistillenv/lib/python3.11/site-packages/torch/functional.py:504: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at ../aten/src/ATen/native/TensorShape.cpp:3526.)
return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]
[10/07 11:40:22 fvcore.common.checkpoint]: [Checkpointer] Loading from models/Detic_LCOCOI21k_CLIP_SwinB_896b32_4x_ft4x_max-size.pth ...
Labeling images: 0it [00:00, ?it/s]
Labeled dataset created - ready for distillation.

Thank you for leaving this Issue. What file extension are the images in the folder that contains the images you want to label?

Same here, jpeg and png - same result.

I see the possible issue: you should provide an absolute path for the directories.

I gave the complete path. Stil there were issues.

@shersoni610 Can you provide a complete code snippet and, if possible, an example image so that we can take a look?


Can nodeselector schedule based on in / not in option selection enable affinity / anti - affinity

Can nodeselector schedule based on in / not in options?
It seems like this might enable affinity / anti - affinity?
Currently it looks like labelSelector allows set based rules and more than one predicate
from : docs/user-guide/labels.md
LIST and WATCH operations may specify label selectors to filter the sets of objects returned using a query parameter. Both requirements are permitted:

equality-based requirements: ?labelSelector=key1%3Dvalue1,key2%3Dvalue2
set-based requirements: ?labelSelector=key+in+%28value1%2Cvalue2%29%2Ckey2+notin+%28value3%29

If nodeselector had the same functionality it would enable anti-affinity/affinity placement.
If the scheduler attempted to schedule 2 instances of the application wouldn't be scheduled to the same node, because of fault tolerance or resource constraints.
apiVersion: v1
kind: Pod
metadata:
name: big-app
labels:
env: test
spec:
containers:

name: big-app
image: big-app
imagePullPolicy: IfNotPresent
nodeSelector:
disktype: ssd
pods: not in [ cpu-app, big-app ]?

cc @bprashanth

The master tracking issue we're using for these kinds of suggestions is #367.

If the scheduler attempted to schedule 2 instances of the application wouldn't be scheduled to the same node, because of fault tolerance or resource constraints.

the scheduler should do this if you create your name:big-app service before the pods (other resource utilization node metrics staying the same).

Oh, I was assuming @davidwalter0 wanted hard constraints. If best-effort is acceptable then I agree with what @bprashanth said

There is work underway to extend nodeSelector, but the others are correct that anti-affinity must be addressed via other means

Just to clarify, in case my merging the two use cases caused confusion, I was thinking of hard affinity / anti affinity constraints.
[Apologies for the additional confusion of overloading the term node here for k8s node and numa node ]
For example, 2 instances of the same application we may want to that want numa node binding [ as we've seen some cases of > 20% perf improvment ] let's call them numa0 and numa1, Optionally they could be scheduled on the same k8s node, but 2 instances of numa0 shouldn't be scheduled to the same node.  In this case the affinity rule is an ok to schedule numa0-rc with numa1-rc, but if these consume all compute / memory on one numa-node, then 2 instances of numa0-rc shouldn't be colocated on the same k8s minion/node.
If the application isn't visibly consuming sufficient resource during a startup phase, then resource constraints couldn't know based on the memory or cpu resource requirements, unless NUMA affinity were a resource constraint.
Similarly, but for fault tolerant reasons, to guarantee that 2 instances of a persistence engine don't schedule to the same k8s node, an anti affinity option would be helpful.

See #9560


Tomcat: 7.0.70 -> 7.0.72 for CVE (HTTPoxy)

Please backport to 16.09
Motivation for this change
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Re: #18856


Geo DNS based load balancing policy

What
We currently only support Round Robin / Even weighted load balancing. We want to support GEO based load balancing. The idea here is that the DNS for a given listener will be setup based on geo metadata added to the managedcluster resource.
Initially we will focus on supporting continents but we should also consider what it means to support more fine grained options such as countries.
Example EU (Europe) NA (North America)
We will also need to support defining a default for when a request falls outside of a defined geo region
Use Cases
As a gateway administrator setting up multiple instances of a gateway that are deployed to clusters in different geographic regions, I want to be able to specify that traffic coming into these gateways should be load balanced based on where the request originated. Additionally I want to be able to specify  default / fall back location to cover the case where a request falls outside a specified geo location

Proposal
This work should build on top of what was done with GLBC in the past to support this. Work originally done by @mnairn
One option is to support a set of attributes on the ManagedCluster resource
kuadrant.io/attribute-geo-contienent: EU
kuadrant.io/attribute-geo-default: True

kind: DNSPolicy
spec:
  targetRef:
     ....  Gateway
   routing:
     strategy: GEO # default even weighting

In a future iteration, we may also look to support "overriding" the gateway policy with a policy that directly targets a DNSRecord resource

https://github.com/kcp-dev/kcp-glbc/pull/504

Dropped this out of the iteration for now since we really want the policy stuff to land before taking this on. https://github.com/Kuadrant/multicluster-gateway-controller/issues/221


-march=native breaks portability of KaHIP within docker containers

KaHIP is crashing with illegal hardware instruction errors on some docker images.
This is mainly because -march=native  is enabled by default, however, the docker images are not generally built in the same machine as the containers.
In my specific case, the docker image is built on a server using docker hub and then used for CI with GitHub actions.
A possible solution is to enable optimizations and -march=native only on Release mode.
If you feel that it's a sensible solution, I can make a PR.
Alternatively,  I'd suggest to remove all aggressive compile flags in the cmake file, and instruct the users in the README.md about ‘recommended settings’ (via -DCMAKE_CXX_FLAGS=).

Hi Igor,
would it help you if we add a flag to disable native optimizations? This would be better as most people dont have to think about optimization flags...
Best
Christian

Hi Christian,
Sure, that would definitely help.

Ok, i will try to integrate such a flag tomorrow.
Best
Christian
On Thu, Dec 17, 2020, 19:00 Igor Baratta<EMAIL_ADDRESS>wrote:

Hi Christian,
Sure, that would definitely help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KaHIP/KaHIP/issues/69#issuecomment-747601947, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLP7SSAKP5OTT2P3YPQJG3SVJBLDANCNFSM4U6Y4KXQ
.

Thanks. I really appreciate it.

Absolutely no problem :)
On Thu, Dec 17, 2020, 19:03 Igor Baratta<EMAIL_ADDRESS>wrote:

Thanks. I really appreciate it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KaHIP/KaHIP/issues/69#issuecomment-747603622, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLP7SRVXJXS235HJQK3SO3SVJBVRANCNFSM4U6Y4KXQ
.

Hi Igor,
you should be able to use the flag -DNONATIVEOPTIMIZATIONS=On now.
Best
Christian


Installing with Homebrew: undefined method `path' for nil:NilClass

This error popped up when installing via Homebrew. Putting it here just in case that's helpful, as it looks like it could be a minor typing error:
▶ brew install gather-cli

==> Cloning https://github.com/ttscoff/gather-cli.git
Cloning into '/Users/ce/Library/Caches/Homebrew/gather-cli--git'...
==> Checking out tag 2.0.25
HEAD is now at a7843ba Preparing for 2.0.25 release
==> Installing gather-cli from ttscoff/thelab
Error: An exception occurred within a child process:
  NoMethodError: undefined method `path' for nil:NilClass
Did you mean?  paths

apparently redundant on #2 #3


tiffutil error

This relates to #45
When I had either a blank background key or a non existing file I get a tiffutil error.
This was fixed by adding a background.

Hey.
Please provide more information and follow https://github.com/loopline-systems/electron-builder/blob/master/CONTRIBUTING.md.

Error below
- Running electron-builder 2.1.1
- Starting creation of installer for ´osx
Writing temporary ´appdmg.json´
Wrote temporary ´appdmg.json´
Kicking off ´appdmg´
appdmg: [1] Looking for target
appdmg: [2] Reading JSON Specification
appdmg: [3] Parsing JSON Specification
appdmg: [4] Validating JSON Specification
appdmg: [5] Looking for files
appdmg: [6] Calculating size of image
appdmg: [7] Creating temporary image
appdmg: [8] Mounting temporary image
appdmg: [9] Making hidden background folder
appdmg: [10] Copying background
appdmg: [11] Unmounting temporary image
appdmg: [12] Removing temporary image
/projects/docker-indicator/node_modules/electron-builder/cli.js:30
    throw error;
    ^

Error: Error running `tiffutil`! Exit code was 5
    at ChildProcess.<anonymous> (/projects/docker-indicator/node_modules/electron-builder/node_modules/appdmg/lib/util.js:30:17)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

The files I'm using are available. If one changes the background value to a blank string in the packager.json the above error is produced. I'm using node 4.2.2 and npm 2.14.7 on OS X.
This may not be an issue since it can be worked around by using a background image. I chose a 1x1 blank image. The fact that a background image is require can be implied by the examples in the readme. However, it may be helpful to make it more clear if this is the desired behavior. If the absence of a background should not break the build then this is an issue.

Thanks. This is actually not on the side of electron-builder. Will ask at appdmg about that.

I will update the documentation here when this question is resolved over at appdmg.
Thanks.

In the 2.8+ API we require background image, but according to https://github.com/LinusU/node-appdmg/issues/76#issuecomment-158080026 we should not. If background is not explicitly specified, we must not substitute default value if file doesn't exist.


Add raw city data and a binary to refine them

The purpose of the binary is to:

Reduce the size of city data (~1.7 MB to <0.3 MB).
Convert the format from CSV to JSON.

Is that the correct way to include the CC4.0 database into our repository under the Apache license? I am not an expert in law but I want to be careful about these license things.
I think src/assets/cities.json can be considered as a modified version and redistribution of the database, which should also follow the terms of attribution. I would suggest putting information on README indicating the use of this database if needed.

Is that the correct way to include the CC4.0 database into our repository under the Apache license? I am not an expert in law but I want to be careful about these license things.
I think src/assets/cities.json can be considered as a modified version and redistribution of the database, which should also follow the terms of attribution. I would suggest putting information on README indicating the use of this database if needed.

The license.txt says "this [https://simplemaps.com/data/us-cities] backlink must come from a public webpage where the Customer is using the data," and CC BY 4.0 states that "you must give appropriate credit, provide a link to the license, and indicate if changes were made."
So I am planning to include the attribution on the UI by the time I mark this PR as ready for review, but not on the README.


Use transparent Arrow icon

@MehdiMahdloo
Now uses a lighter (400KB -> 4KB) arrow icon that is transparent.

Tthat’s great! A much needed fix! Thank you!


QT SPIKE: Review the steps to initiate the QT

There are a lot of buttons hanging on the Dashboard.
This ticket is to review the workflow of the creation/initialization/activation / etc ... for a test/
There are some buttons that should go together
There are some buttons that need to be disabled when some others are enabled
There are some button that should be hidden when some others are enabled / visible

One suggestion was to have a task list with done

@Rebecca-mcknight1991 look at when this can be done.


[Feature Request] Array fields

I will be working on this array fields very soon.
at the moment the api in my head will be like the below:
[1,2,3].map((i) => <input name={`test[$i]`} key={i} ref={register} />);

https://github.com/bluebill1049/react-hook-form/releases/tag/v2.1.0


bug: Empty area when "spinner='none'" for ion-refresher

Type: bug
Platform: all
Hi,
i am implementing my own loading overlay, so i want no spinner displayed at all for pull-to-refresh. When i now use "spinner='none'" as attribute of the ion-refresher, no spinner is displayed (good), but the area where the spinner used to be is still there as empty area (bad), as long as the refreshing takes.
In my opinion, for "spinner='none'", also the area should not be displayed.
Maybe related to #2926

Greetings @sikron!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Well, the wrapping element needs to exist to contain the pulling icons, but are you saying it shouldn't pause at 50 or so px until the complete event fires?

Hi, thx for answering!
You are right. I made a picture, though, to be absolutely clear:
The green arrow points to my loading animation (because of which i don't want the pull-to-refresh spinner). The read rectangle is, where the empty spinner area is. After pulling, the area stays until the 'scroll.refreshComplete' event is broadcasted. Afterwards it goes aways and my content begins at the very top of the page.

@sikron, thanks for pointing out this issue. I have the same problem. Moreover, @perrygovier, this issue is also related to this category of problems.

+1

Hello all! Is this still an issue with the latest version of ionic? Thanks!

+1

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


Add support for consumer version selectors for deployed and released versions

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:
{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "deployed": true }

{ "released": true }

These keys can be used in various combinations ( eg. { "environment": "prod", released: true, consumer: "Foo" } ). Please allow any combination of keys, and do not validate them locally, as the validation rules can change over time as support is added for new selectors - just ensure that any errors returned from the API are displayed clearly to the user.
See https://github.com/pact-foundation/pact_broker/blob/master/lib/pact_broker/doc/views/provider-pacts-for-verification.markdown for the usage docs of each selector.
As more selectors will be added over time, it's my preference that the consumer version selectors are not strongly typed, and are just passed through straight from the configuration object to the API, so that we don't have to make code changes to the Pact clients each time we add new selectors. (eg. there will be new selectors coming for branch support very soon). I understand that this is not compatible with the idioms of every Pact client language however, so do whatever you need to do to make the new selectors work elegantly within your language.
Please update https://docs.pact.io/pact_broker/advanced_topics/consumer_version_selectors/ for your language once the selectors have been released.

duplicate of #45 , but will keep this one with more details 😄

think now doable due to https://github.com/pact-foundation/pact-jvm/pull/1471

added in v0.2.0


Following your example adding --interactive doesn't allow interactive mode

^ like what title says.
I'm trying to enter interactive mode, but whatever I do, i can't. Am I missing something here?
i saved the file like so in test.js

const yargsInteractive = require("yargs-interactive");
const options = {
  interactive: { default: true },
  name: { type: "input", default: "A robot", describe: "Enter your name" },
  likesPizza: {
    type: "confirm",
    default: false,
    describe: "Do you like pizza?",
  },
};

yargsInteractive()
  .usage("$0 <command> [args]")
  .interactive(options)
  .then((result) => {
    // Your business logic goes here.
    // Get the arguments from the result
    // e.g. myCli(result.name);
    console.log(
      `\nResult is:\n` +
        `- Name: ${result.name}\n` +
        `- Likes pizza: ${result.likesPizza}\n`
    );
  });

then i run
node test.js --interactive
outputs immediately without prompts:

Result is:
- Name: A robot
- Likes pizza: false

Thanks for reporting! There is something weird indeed, I'm not sure if the bug was always there or something changed in the yargs API. Just in case, I've added a patch in the code to make sure Interactive mode is triggered if you explicitly asked for it via arguments.
BTW, we are working on a complete refactor and cleanup, using TypeScript, and a better testing strategy, this is why you don't see any test in the commit that fixes the issue (will be included in the next major). Stay tuned!

me too, it seems there is no new tag for this version. @nanovazquez


add [Sonar] badges for various test metrics

Refs #3236 and #3189

Adds first class badge support for the various test result/count/etc. metrics that Sonar supports
Refactors transform function in the base class to make it easier in the child service classes that work with multiple metrics

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 99d18515cfa6ee2ac671bdb3269de142619cdf0b


Nlmgs containing Tcmsg fails serialization

Version of neli
0.5.3
Does the documentation specify that neil's behavior is correct?
Not related.
Does there appear to be a mistake in the netlink documentation based on the kernel code?
Not related.
Describe the bug
Serialization of Tcmsgs seems to be bugged.
It's reporting The number of bytes written to the buffer did not fill the given space for very simple messages.
In an example, I have noticed that the buffer is expecting 40 bytes to be written as it's aligned to 4 bytes.
The message however is reporting 39 bytes, perhaps it's missing some padding?
To Reproduce
        let msg = Tcmsg {
            tcm_family: 0,
            tcm_ifindex: 0,
            tcm_handle: 0,
            tcm_parent: 0,
            tcm_info: 0,
            rtattrs: RtBuffer::new(),
            padding_char: 0,
            padding_short: 0,
        };

    let mut socket = NlSocketHandle::connect(socket::NlFamily::Route, None, &[])?;
    let nlhdr = {
        let nl_type = Rtm::Newtfilter;
        let nl_flags = nl::NlmFFlags::new(&[nl::NlmF::Request, nl::NlmF::Ack, nl::NlmF::Excl, nl::NlmF::Create]);
        let payload = NlPayload::Payload(msg);
        Nlmsghdr::new(None, nl_type, nl_flags, None, None, payload)
    };

    println!("{:?}", nlhdr);

    socket.send(nlhdr)?;

Additional context
I modified the library to expose the padding fields so I could build the Tcmsg payload.
See https://github.com/jbaublitz/neli/issues/151.

@tammela Can you please take a look and see if this is still a problem in v0.6.0? I've heavily improved the serialization code. If it hasn't, I'll fix it and add some tests.

Considering this closed by 16854b52d52fefed8e3ce3337b58499d23723934


Updating Dataflow API version to revision 235.

r: @tgroh

Jenkins retest this please

@lukecwik PTAL : )

Closing for now.


Color schemes

Would it be a good idea to have different color pallets for coloring nodes, edges, and clusters? For example, there is a good standard for choosing colors, that is developed even with consideration of picking colors for color blind people: https://personal.sron.nl/~pault/data/colourschemes.pdf
Some good ideas for choosing colors and gradient can come from this picture: https://pbs.twimg.com/media/Eks6mCFU0AAV0uI?format=png&name=4096x4096

I toyed with the idea, but ultimately never pursued it because I didn't feel like building a compelling widget to select between predefined color schemes was a high-impact goal, relative to the other things in the backlog. That said, I never documented the thought! So, what I'm really trying to say is thanks @Sergey-Knyazev for writing this ticket :)


[Bug]: nanolayer: HTTP Error 403: rate limit exceeded

Feature id and version
ghcr.io/devcontainers-contrib/features/actionlint:1
Devcontainer base Image
mcr.microsoft.com/devcontainers/base:jammy
What happened?
During installation of nanolayer, it crashed during install_gh_release_binary installation (nanolayer.cli.install).
Relevant log output
2024-08-14 14:30:35.450Z: #15 6.609 urllib.error.HTTPError: HTTP Error 403: rate limit exceeded

c20fe8ec-f97d-4e6d-ac53-d58c25efcc6e.pdf

https://homh1.co/DMkwSo8

This project is not associated with the devcontainer project and appears to have been abandoned #628 . The official project has removed all devcontainer-contrib features from their listing. https://github.com/devcontainers/devcontainers.github.io/issues/451


Added a filterQuality parameter to images.

I've added the possibility to set the filterQuality on Images. This was hardcoded.
The previously hardcoded value is set as default parameter.
Some images look better when scaled with no filter quality (like pixelart). That's why I added the parameter.

Can you update the documetation to explain the newly exposed parameter and why you might want to not use the default?

I'll update the documentation for all the files I've changed in this pull request. I expect to do it tomorrow morning.

Thanks!

Looks like a couple of my suggestions messed up the spacing too - the assert( is spaced in one from the others.  Can you fix those while you do the docs?  Sorry about that!

I'm not too great when it comes to documentation. I hope this is what you mean!
I've also fixed the spacing on the asserts.
Also CLA is no again. The bot is being strict today ;)

LGTM!  Thanks for the contribution!  Will land on green.

Great! Thank you!


Synapse COPY INTO AUTO CREATE TABLE options

The option AUTO CREATE TABLE documented on https://docs.microsoft.com/en-us/sql/t-sql/statements/copy-into-transact-sql?view=azure-sqldw-latest uses some options to create the table but these are not documented. E.g. I want to have HEAP tables with distribution ROUND ROBIN, but apparently the option creates CCI tables.

@sdebruyn -- Sam, thank you again for your feedback.
@MikeRayMSFT -- Mike, please look into this issue.


Add some documentation of resources and changes

This is in preparation of releasing a version 8.3.5 just before other changes are added to master.  In general, the resources we're storing in Artifactory aren't well documented and the procedures to get them there won't be repeatable as soon as my laptop breaks.  However, improving that situation is a separate task which shouldn't slow this down.

Thank you @kwalcock!


In Swagger 2.0, what should “default” within an array parameter actually mean?

Not an issue, but a question on the swagger in the repo:
In the well-known petstore swagger document, the findByStatus endpoint takes a status:
"parameters": [
    {
        "name": "status",
        "in": "query",
        "description": "Status values that need to be considered for filter",
        "required": true,
        "type": "array",
        "items": {
            "type": "string",
            "enum": [
                "available",
                "pending",
                "sold"
            ],
            "default": "available"
        },
        "collectionFormat": "multi"
    }
]

While the default value could be implied from this, from a programmatic perspective what should be expected as the value for "status" (and for other parameters in a similar case)?
The value is of type array, it doesn't have a default.
Each item is a string, one of available, pending or sold, and the default if not supplied is "available"
How would you use "default" for an array of arbitrary length? The default supplied is for the string, not the array so:
Does this imply that the array has no default value?
Does it imply that the array has a default value of an array with one item that is the default value for the array items?
Does it imply an array of arbitrary length where all the values are the default value for the array items?
Or is it just for UI representation of the default selected value when adding a new item to the array?

I believe that the example is just wrong. It should rather read
"parameters": [
    {
        "name": "status",
        "in": "query",
        "description": "Status values that need to be considered for filter",
        "required": true,
        "type": "array",
        "items": {
            "type": "string",
            "enum": [
                "available",
                "pending",
                "sold"
            ]
        },
        "default": ["available"]
        "collectionFormat": "multi"
    }
]

We should probably fix that example. @alasdairhurst , I cannot seem to find it in this repo. Can you point us to the source file?

@tedepstein I'd also like to know where to find the up-to-date one that has this example.
http://petstore.swagger.io/
https://petstore.swagger.io/v2/swagger.json
These both have the issue - I don't know where this is stored. It's slightly different from the ones in the repo here which i originally thought it was at:
https://github.com/OAI/OpenAPI-Specification/tree/master/examples/v2.0/json
Looks like this may be the source - which is see is an extension of your examples.  I assumed you were the same team on this, and it looks like you're not?
https://github.com/swagger-api/swagger-codegen/blob/master/modules/swagger-codegen/src/test/resources/2_0/petstore.yaml
Although the question was aimed mostly at to what was expected from the spec. I'll open an issue there.

Thanks, @alasdairhurst .  The OpenAPI specification is no longer part of Swagger, so yes, these are different projects. (See background here.)

Looks like the example in question is not part of this project, and no more work is being done on OAS 2 anyway, so I'm going to close this.


Logs not being written to remote storage (GCS)

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Chart Version
8.6.1
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.6", GitCommit:"ad3338546da947756e8a88aa6822e9c11e7eac22", GitTreeState:"clean", BuildDate:"2022-04-14T08:49:13Z", GoVersion:"go1.17.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.12-gke.2200", GitCommit:"6c11aec6ce32cf0d66a2631eed2eb49dd65c89f8", GitTreeState:"clean", BuildDate:"2022-05-20T09:29:14Z", GoVersion:"go1.16.15b7", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.23) and server (1.21) exceeds the supported minor version skew of +/-1

Helm Version
version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}

Description
I'm using Remote Logging to store logs in a GCS bucket, but the logs don't seem to be uploaded. This is what I see inside tasks:
*** Unable to read remote log from gs://airflow-logs-store/staging/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-01T09:35:44+00:00/task_id=list_batch_packs/attempt=1.log
*** 404 GET https://storage.googleapis.com/download/storage/v1/b/airflow-logs-store/o/staging%2Fdag_id%3Ddo_labeled_pack_data_etl%2Frun_id%3Dmanual__2022-08-01T09%3A35%3A44%2B00%3A00%2Ftask_id%3Dlist_batch_packs%2Fattempt%3D1.log?alt=media: No such object: airflow-logs-store/staging/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-01T09:35:44+00:00/task_id=list_batch_packs/attempt=1.log: ('Request failed with status code', 404, 'Expected one of', <HTTPStatus.OK: 200>, <HTTPStatus.PARTIAL_CONTENT: 206>)

*** Log file does not exist: /opt/airflow/logs/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-01T09:35:44+00:00/task_id=list_batch_packs/attempt=1.log
*** Fetching from: http://airflow-worker-0.airflow-worker.airflow.svc.cluster.local:8793/log/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-01T09:35:44+00:00/task_id=list_batch_packs/attempt=1.log

This seems to happen with all DAGs.
I have a connection to GCP already set and working, and the Service Account has the right permissions  (in fact this DAG moves some data to a GCS bucket using a Hook with that connection, assuring that the connection works), and the DAGs all end successfully (no crashes, final status is either success or fail, local logs are also available).
This is the current configuration for Logging:
$ airflow config list
[logging]
base_log_folder = /opt/airflow/logs
remote_logging = True
remote_log_conn_id = google_cloud_default
google_key_path =
remote_base_log_folder = gs://airflow-logs-store/staging
encrypt_s3_logs = False
logging_level = INFO
celery_logging_level =
fab_logging_level = WARNING
logging_config_class =
colored_console_log = True
colored_log_format = [%(blue)s%(asctime)s%(reset)s] {%(blue)s%(filename)s:%(reset)s%(lineno)d} %(log_color)s%(levelname)s%(reset)s - %(log_color)s%(message)s%(reset)s
colored_formatter_class = airflow.utils.log.colored_log.CustomTTYColoredFormatter
log_format = [%(asctime)s] {%(filename)s:%(lineno)d} %(levelname)s - %(message)s
simple_log_format = %(asctime)s %(levelname)s - %(message)s
task_log_prefix_template =
log_filename_template = dag_id={{ ti.dag_id }}/run_id={{ ti.run_id }}/task_id={{ ti.task_id }}/{% if ti.map_index >= 0 %}map_index={{ ti.map_index }}/{% endif %}attempt={{ try_number }}.log
log_processor_filename_template = {{ filename }}.log
dag_processor_manager_log_location = /opt/airflow/logs/dag_processor_manager/dag_processor_manager.log
task_log_reader = task
extra_logger_names =
worker_log_server_port = 8793

I have also tried adding a custom google_key_path (the same that I'm using for the default connection) but the logs still weren't updated. What can I do to troubleshoot it?
Relevant Logs
No response
Custom Helm Values
airflow:
  executor: CeleryExecutor
  defaultSecurityContext: {}
  usersUpdate: false
  config:
    AIRFLOW__SCHEDULER__DAG_DIR_LIST_INTERVAL: "60"
    AIRFLOW__CORE__ENABLE_XCOM_PICKLING: "True"
    AIRFLOW__API__AUTH_BACKENDS: "airflow.api.auth.backend.basic_auth, airflow.api.auth.backend.session"

    AIRFLOW__LOGGING__REMOTE_LOGGING: "true"
    AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER: "" # This is set by helm --set
    AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID: "google_cloud_default"
    AIRFLOW__LOGGING__COLORED_CONSOLE_LOG: "true"

    GOOGLE_APPLICATION_CREDENTIALS: "xxx/airflow-sa.json"
    PYTHONPATH: "/opt/airflow/dags/repo"

  connectionsUpdate: true
  connections:
    - id: google_cloud_default
      type: google_cloud_platform
      description: Vector GCP

      ## see the official "google_cloud_platform" connection docs for valid extra configs
      extra: |-
        {"extra__google_cloud_platform__key_path": "xxx/airflow-sa.json", "extra__google_cloud_platform__key_secret_name": "", "extra__google_cloud_platform__keyfile_dict": "", "extra__google_cloud_platform__num_retries": 5, "extra__google_cloud_platform__project": "", "extra__google_cloud_platform__scope": ""}

  extraVolumeMounts:
    ## spec for VolumeMount: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#volumemount-v1-core
    - name: google-service-account
      mountPath: xxx
      readOnly: true

  extraVolumes:
    ## spec for Volume: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#volume-v1-core
    - name: google-service-account
      secret:
        secretName: gcloud-key-airflow
dags:
  gitSync:
    enabled: true
    repo: "xxx"
    branch: "master"
    revision: "HEAD"
    syncWait: 60
    sshSecret: "xxx"
    sshSecretKey: "xxx"
    repoSubPath: "dags"

ingress:
  enabled: false
  web:
    annotations:
      kubernetes.io/ingress.class: nginx
      cert-manager.io/cluster-issuer: letsencrypt-prod
      nginx.ingress.kubernetes.io/rewrite-target: /$1
    path: ""
    host: ""

@nhabbash a few questions:

What version of airflow are you running (if its 1.10 you will need to review the older docs
When you look into your GCS bucket, do you see any log files being created?
Are you seeing logs in GCS for tasks that succeed? (airflow only uploads the logs at the end of a task, so if the pod crashes none will be uploaded)
Are you 100% sure that Secret/gcloud-key-airflow contains a key called airflow-sa.json which is correctly formatted? (use kubectl get secret -o yaml to figure out)
Why are you setting extra__google_cloud_platform__key_secret_name and extra__google_cloud_platform__keyfile_dict as "", I imagine that might overwrite extra__google_cloud_platform__key_path

What version of airflow are you running (if its 1.10 you will need to review the older docs
Airflow 2.3.3, mistakenly removed it from OP

When you look into your GCS bucket, do you see any log files being created?
I've actually noticed that for some DAGs the logs are being written to GCS. I have this DAG here that reports the following:

*** Reading remote log from gs://airflow-logs-store/local/dag_id=common_create_organization_config/run_id=manual__2022-08-02T07:38:30.880016+00:00/task_id=create_org_config_file/attempt=1.log.
*** Previous log discarded: 404 GET https://storage.googleapis.com/download/storage/v1/b/airflow-logs-store/o/local%2Fdag_id%3Dcommon_create_organization_config%2Frun_id%3Dmanual__2022-08-02T07%3A38%3A30.880016%2B00%3A00%2Ftask_id%3Dcreate_org_config_file%2Fattempt%3D1.log?alt=media: No such object: airflow-logs-store/local/dag_id=common_create_organization_config/run_id=manual__2022-08-02T07:38:30.880016+00:00/task_id=create_org_config_file/attempt=1.log: ('Request failed with status code', 404, 'Expected one of', <HTTPStatus.OK: 200>, <HTTPStatus.PARTIAL_CONTENT: 206>)

On GCS, I see the files also being created. I also rerun some of the other DAGs but I still get the following:
*** Unable to read remote log from gs://airflow-logs-store/local/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-02T09:40:13+02:00/task_id=list_batch_packs/attempt=2.log
*** 404 GET https://storage.googleapis.com/download/storage/v1/b/airflow-logs-store/o/local%2Fdag_id%3Ddo_labeled_pack_data_etl%2Frun_id%3Dmanual__2022-08-02T09%3A40%3A13%2B02%3A00%2Ftask_id%3Dlist_batch_packs%2Fattempt%3D2.log?alt=media: No such object: airflow-logs-store/local/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-02T09:40:13+02:00/task_id=list_batch_packs/attempt=2.log: ('Request failed with status code', 404, 'Expected one of', <HTTPStatus.OK: 200>, <HTTPStatus.PARTIAL_CONTENT: 206>)

If for some DAGs it's uploading the logs I believe the issue might not be the connection, but something with the the DAG definitions? I can share the code or definition if that's the case.

Are you seeing logs in GCS for tasks that succeed? (airflow only uploads the logs at the end of a task, so if the pod crashes none will be uploaded)
Tasks always succeed or fail, I have no crashes happening (in fact Airflow is always reading the local logs). In GCS I don't see logs for the DAGs that report Unable to read remote log from ... 404 GET, as they aren't uploaded altogether. But as I discovered there are a couple of DAGs for which logs are uploaded to GCS, and I can see them both there and in Airflow, as they're read.

Are you 100% sure that Secret/gcloud-key-airflow contains a key called airflow-sa.json which is correctly formatted? (use kubectl get secret -o yaml to figure out)
Yes, the key is there and it's mounted correctly by K8s in the PODs.

Why are you setting extra__google_cloud_platform__key_secret_name and extra__google_cloud_platform__keyfile_dict as "", I imagine that might overwrite extra__google_cloud_platform__key_path
I tried just setting extra__google_cloud_platform__key_path, but the extra JSON field wouldn't parse in Airflow (I would get an error when using the connection). This solved it, I did found this solution either on some Issue in the official Airflow repo or on StackOverflow but I can't find it again. Anyway, the connection works when using it for Hooks (I can list/upload/create buckets and blobs on GCS), and it seems like it is working sometimes for uploading logs, but most of the times it isn't.

@nhabbash if you are seeing logs in GCS for some DAGs but not others, you should compare what is happening between those dags.
I almost guarantee that something is crashing in the DAGs which are failing to upload, as this is incredibly common (because airflow only uploads logs to GCS after the task is finished).

@thesuperzapper the DAGs and their tasks are succeeding in both cases and not crashing - if they are crashing somewhere I'm not really seeing it. Here are some screenshots and logs (just the log loading and task succeeding message):
DAG w/ remote logging not working (first task example):

Screenshots

Log
*** Unable to read remote log from gs://airflow-logs-store/local/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-04T08:59:12+00:00/task_id=list_batch_packs/attempt=1.log
*** 404 GET https://storage.googleapis.com/download/storage/v1/b/airflow-logs-store/o/local%2Fdag_id%3Ddo_labeled_pack_data_etl%2Frun_id%3Dmanual__2022-08-04T08%3A59%3A12%2B00%3A00%2Ftask_id%3Dlist_batch_packs%2Fattempt%3D1.log?alt=media: No such object: airflow-logs-store/local/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-04T08:59:12+00:00/task_id=list_batch_packs/attempt=1.log: ('Request failed with status code', 404, 'Expected one of', <HTTPStatus.OK: 200>, <HTTPStatus.PARTIAL_CONTENT: 206>)
*** Reading local file: /opt/airflow/logs/dag_id=do_labeled_pack_data_etl/run_id=manual__2022-08-04T08:59:12+00:00/task_id=list_batch_packs/attempt=1.log
...
...
[2022-08-04, 08:59:26 UTC] {python.py:173} INFO - Done. Returned value was: <REDACTED (it's a dict)>
[2022-08-04, 08:59:26 UTC] {taskinstance.py:1415} INFO - Marking task as SUCCESS. dag_id=do_labeled_pack_data_etl, task_id=list_batch_packs, execution_date=20220804T085912, start_date=20220804T085919, end_date=20220804T085926
[2022-08-04, 08:59:26 UTC] {local_task_job.py:156} INFO - Task exited with return code 0
[2022-08-04, 08:59:26 UTC] {local_task_job.py:273} INFO - 0 downstream tasks scheduled from follow-on schedule check

DAG w/ remote logging working:

Screenshots

Log
*** Reading remote log from gs://airflow-logs-store/local/dag_id=common_create_organization_config/run_id=manual__2022-08-04T08:57:54.498373+00:00/task_id=create_org_config_file/attempt=1.log.
*** Previous log discarded: 404 GET https://storage.googleapis.com/download/storage/v1/b/airflow-logs-store/o/local%2Fdag_id%3Dcommon_create_organization_config%2Frun_id%3Dmanual__2022-08-04T08%3A57%3A54.498373%2B00%3A00%2Ftask_id%3Dcreate_org_config_file%2Fattempt%3D1.log?alt=media: No such object: airflow-logs-store/local/dag_id=common_create_organization_config/run_id=manual__2022-08-04T08:57:54.498373+00:00/task_id=create_org_config_file/attempt=1.log: ('Request failed with status code', 404, 'Expected one of', <HTTPStatus.OK: 200>, <HTTPStatus.PARTIAL_CONTENT: 206>)
...
...
[2022-08-04, 08:57:56 UTC] {python.py:173} INFO - Done. Returned value was: None
[2022-08-04, 08:57:56 UTC] {taskinstance.py:1415} INFO - Marking task as SUCCESS. dag_id=common_create_organization_config, task_id=create_org_config_file, execution_date=20220804T085754, start_date=20220804T085755, end_date=20220804T085756
[2022-08-04, 08:57:56 UTC] {local_task_job.py:156} INFO - Task exited with return code 0
[2022-08-04, 08:57:56 UTC] {local_task_job.py:273} INFO - 0 downstream tasks scheduled from follow-on schedule check

@nhabbash I think the docs forgot to say that you MUST set AIRFLOW__LOGGING__GOOGLE_KEY_PATH if not using "GKE Workload Identity".
Can you confirm that everything works when you set values like this:
airflow:
  config:
    AIRFLOW__LOGGING__REMOTE_LOGGING: "True"
    AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER: "gs://<<MY-BUCKET-NAME>>/airflow/logs"
    AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID: "my_gcp"

    ## this is the new part \/
    AIRFLOW__LOGGING__GOOGLE_KEY_PATH: "/opt/airflow/secrets/gcp-keyfile/keyfile.json"
    ## this is the new part /\

  connections:
    - id: my_gcp
      type: google_cloud_platform
      description: my GCP connection
      extra: |
        {
          "extra__google_cloud_platform__key_path": "/opt/airflow/secrets/gcp-keyfile/keyfile.json",
          "extra__google_cloud_platform__num_retries: "5"
        }

  extraVolumeMounts:
    - name: gcp-keyfile
      mountPath: /opt/airflow/secrets/gcp-keyfile
      readOnly: true

  extraVolumes:
    - name: gcp-keyfile
      secret:
        ## assumes that `Secret/my-gcp-keyfile` contains a key called `keyfile.json`
        secretName: my-gcp-keyfile

Also, can you confirm 100% if only setting extra__google_cloud_platform__key_path and extra__google_cloud_platform__num_retries works, or if you need to specify the other ones?

@thesuperzapper I did try setting AIRFLOW__LOGGING__GOOGLE_KEY_PATH previously, but it did not work. I tried again with these values:
airflow:
  config:
    AIRFLOW__LOGGING__REMOTE_LOGGING: "True"
    AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER: "" # Set through helm --set
    AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID: "google_cloud_default"
    AIRFLOW__LOGGING__GOOGLE_KEY_PATH: "/opt/airflow/secrets/google-service-account/airflow-sa.json"

    GOOGLE_APPLICATION_CREDENTIALS: "/opt/airflow/secrets/google-service-account/airflow-sa.json"

  connectionsUpdate: true
  connections:
    - id: google_cloud_default
      type: google_cloud_platform
      description: GCP Connection

      extra: |-
        {"extra__google_cloud_platform__key_path": "/opt/airflow/secrets/google-service-account/airflow-sa.json", "extra__google_cloud_platform__num_retries": 5}

  extraVolumeMounts:
    - name: google-service-account
      mountPath: /opt/airflow/secrets/google-service-account
      readOnly: true

  extraVolumes:
    - name: google-service-account
      secret:
        secretName: gcloud-key-airflow

Unfortunately for remote logging I'm getting still the exact same output as my last post, that is the DAG that previously had remote logging still has it, the other does not, and the situation is identical (same logs and status).
This is the config:
[logging]
base_log_folder = /opt/airflow/logs
remote_logging = True
remote_log_conn_id = google_cloud_default
google_key_path = /opt/airflow/secrets/google-service-account/airflow-sa.json
remote_base_log_folder = gs://airflow-logs-store/staging

One thing is good though, which is that the connection is set correctly even without defining all the extra fields (previously I was getting something similar to this, but maybe this chart does things differently, although I wouldn't be able to explain why I wasn't able to use the field with just key_path set previously.

@naturalett can you try restarting all your worker pods (so they pick up new secret values)?
Also, where are you copying the [logging] configs you believe are in your cluster from?

@thesuperzapper this was a fresh branch deployment, so the pods were newly created ones and the secrets were mounted anew. the logging config I got from running a shell in an Airflow worker pod and running airflow config list, just to check whether everything has been set correctly

@nhabbash did you end up solving this logging issue?

I am not sure why the bot closed this, as there was clearly activity in the last 60 days.
Either way, do you have any updates @nhabbash?

I am not sure why the bot closed this, as there was clearly activity in the last 60 days.
Either way, do you have any updates @nhabbash?

Hey @thesuperzapper, sorry for the late reply. Unfortunately haven't found a solution for this, as I moved onto working on other stuff I haven't had the chance to revisit the issue. I tried checking again just now, and I'm still left with some DAGs that are able to write logs to GCS, and others that do not write them and hence lose the logs once the pods are restarted.


Entity unavailable after HAOS 2022.3.0 udpate

Seems the plugin stopped working after HAOS 2022.3.0 udpate. The entity becomes unavailable and cannot pass configuration check: "Platform error media_player.kef_connector - Requirements for kef_connector not found: ['pykefcontrol==0.5']."

Thanks @tjxism, I just release version 0.5.5 which resolves the issue.
Update to the last version and you should be good. Feel free to reopen the issue if it is not the case !

You're the best!


Converting stop_fold exception breaks vnode worker

This fixes a problem where, occasionally, paginated 2i queries would be missing values.  The fix is very short, but the explanation is very long:
2i queries eventually execute folds, which run in one of the the riak_kv vnode pool workers.  The request to run work in a pool worker has a fold function with an accumulator, and a finish function that runs on the result of the fold function (riak_kv_worker:handle_work). See how a stop_fold exception is handled by skipping the finish function.  In the case of paginated 2i queries, the fold sends back results to the index FSM using riak_kv_vnode:result_fun_ack (see 2i handler), which waits for an ack from the index FSM and may throw stop_fold if the FSM signals it does not need any more results.
Results are collected in batches before being sent in a riak_kv_fold_buffer, which is used as the accumulator in the fold.  Adding to this buffer and reaching the batch limit is what triggers the sending.  A finish function is provided so that any remaining items in the buffer by the end of the fold are also sent.  That's the key of the problem right there: the folder adds an item, the buffer gets full, the folder sends the batch to the FSM and receives a stop command, then throws stop_fold.  The intention is to stop the fold right there and not send any more items, so the finish function should be skipped. The stoppable_fold wrapper was catching that stop_fold and converting it to a {break, Acc} exception, where the accumulator was the value before the last items were sent, still containing most of those items.  The riak_kv_fold_worker never gets the exception, and simply processes that last buffer minus last item by calling the finish function on it, re-sending those items. An example:

Last batch, after adding last item 9: [7,8,9]
FSM receives [7,8,9]. Then, if it stays around long enough, it receives an extra [7,8] due to the finish function being called on the stale accumulator and ends up with [7,8,9,7,8].  This is the bit that is timing sensitive and makes it non-deterministic.
The merge sort algorithm expects items in order. The result is undefined otherwise. So occasionally it will output items out of order. For example [7,8,7,9,8].  It also truncates to page size, so the [9,8] is dropped and the 7 dropped due to de-duplication.

/cc @jonmeredith @JeetKunDoug
The code around the fold functions is pretty hairy. Let me know if you need more clarification (you will).

I'm going to try to "TODONE" the todo to remove stoppable_fold - there are only 5 usages, all in riak_kv_eleveldb_backend, so unless I'm missing something it should be pretty painless to remove it completely and be done with it.

I incorporated Doug's cleanup and added a fix for the memory backend, then squashed the branch to a single commit.

This problem can be observed and verified with this new EQC based 2i test: https://github.com/basho/riak_test/pull/822
This is a pure EQC test, without PULSE. Ideally you could use PULSE in a cluster, but the tech is not there yet. Still, running that test for the eleveldb or memory backend with a single node using 32 vnodes shows the pagination problem immediately.

+1 9b82812
Mentally walked through the code.
Ran the EQC riak_test (at commit 2.0.0-234-gfa49385)
Ran the 'repro.erl' script that replicated the original problem and was resolved.

Forgot to mention also ran existing 2I r_t's

@borshop merge


rubocop: require braces for Sorbet sig

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

I think this is more readable
(Should we have a vote of 👍 or 👎?)

Review period will end on 2021-01-19 at 06:49:41 UTC.

Review period will end on 2021-01-19 at 06:49:41 UTC.

Review period ended.

Review period ended.


[FEA] Support JITting and Linking LTOIR from cuda source inputs

Is your feature request related to a problem? Please describe.
After Pynvjitlink is introduced into Numba-CUDA, I would like to be able to jit cuda source files into LTOIR and link it with nvjitlink. This basically requires the linker lto flag to be respected by the jit and linker machinery.
Describe the solution you'd like
Add lto flag to nvrtc.compile, and add -dlto flag to compile option when set. In the Linker class, use add_ltoir in add_cu when self.lto is set.

As a follow up to this PR - it would be helpful to support -ptx flag for nvjitlink to emit the PTX under LTOIR linkage, given NUMBA_DUMP_ASSEMBLY is set. This makes sure that Numba-CUDA shows the LTO-ed PTX and is more useful in debugging optimization related issues.

I think this was fixed by #62 - is that correct, @isVoid?


Adding new plugin yml file

Description
JIRA - https://issues.jenkins-ci.org/projects/HOSTING/issues/HOSTING-965
Github - https://github.com/jenkinsci/gcr-scanner-plugin
Add new plugin gcr-scanner yaml file for hosting.
Submitter checklist for changing permissions
Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

Changed the file name to plugin-gcr-scanner.yml


auto-assign to oncall

Today PR pick someone from our normal rotation which is a bit interuptive. What do you think about having an alias that gets assigned all ticket? This will force us to internally pick the round-robin assigner by hand which I don't love but I don't see another way.
I used the word oncall since that is more publicly known than onrun.
Motivation

Test plan

See included automated tests.

Is this just for PRs from non-members, or all PRs that have no reviewer assigned?

This commit is for everyone. I'd love if we could bifricate but I don't see how in CODEOWNERS

I've added automation to this via https://pullreminders.com/installs/46383129/assigner/teams/1340
👍

@DarkDimius do we then want the rotation that it points at to be empty and have it proxy to a real one so that if we internally already pick a reviewer it won't do anything? (like you do with the other team)?

I updated https://pullreminders.com/installs/46383129/assigner/teams/1340 to use a proxy team so hopefully it won't assign someone if someone else is already assigned


Update trackerforce/switcher-management public image with latest updates

The issue can be closed as the CI pipeline is now creating and pushing new versions to Docker Hub.


InfiniteScroll inside a container is not working if that container has ng-scrollbars atached

Hi, so I have a page that has div (in the code below that's the one with grid class) that has attached ngscrollbars, and infinite scrolls works in the container as it should only if the container div bottom is below or really close to the bottom border of the window. When I scroll the window down completely, and the bottom of the container is higher than bottom of the window, the loading function isn't called anymore (getNextNews()).

          ....

So I tried the obvious one, disabling the ng-scrollbars, and then it works like it should, but I have to use that awful default scrollbar inside the container, which is kinda bad.
I'm probably missing something obvious, but I can't for the life of me figure it out right now.

I´m having a similar issue.. did you ever find a solution?

Hey, I'm not sure since it was months ago, but I think I resolved it by not using scrollbars, since that was the reason it didn't work.


Events

Alrighty, this component is ready for merge.
Important changes

Moved events archive to its own page events/archives
Need to add moment.js (waiting on #84)
@adekunleoduye, events modules are ready for styling (will open a separate ticket)


[JS] Render Action.OpenUrl with role=link (#3914)

Related Issue
Fixes #3914 in release/1.2 (direct cherry-pick)
Description
Render Action.OpenUrl buttons with role="link"
How Verified

local build and inspection

Microsoft Reviewers: Open in CodeFlow

/azp run

going to re-do this from the unified approach (see #4080)


docs: Small typo on best practice: is should have been us

Thanks @WyriHaximus
Out of interest, have you enabled the controller liveness probe in production? Found any circumstances where the controller has become stuck?

No problem @wallrj, I was actually surprised to read the liveness prob isn't enabled by default. Just enabled it on my personal clusters. Will discuss it with my team at work tonight, and report any issues we run into.


Publish Button Visibility and Permissions Issue

Link to reproduction
No response
Payload Version
beta v37
Node Version
21
Next.js Version
15
Describe the Bug
I've been experimenting with the solution from the Payload CMS discussion[ #1009 in v3.
The goal is to have permissions that restrict publish access in create/update operations for a collection. The suggested solution initially hides the publish button, allowing only draft saving. However, there are two issues observed:
After saving a draft, the publish button reappears. Clicking on it results in an error.
Despite the absence of publish permissions, users can still publish documents from the list view.
Expected Behavior:

The publish button should remain hidden for users without publish permissions after saving a draft.
Users without publish permissions should not be able to publish documents from the list view.

Actual Behavior:

The publish button reappears after saving a draft and results in an error when clicked.
Users without publish permissions can publish documents from the list view.

Reproduction Steps

Implement access control for create/update operations in a collection to check if _status is 'published' and restrict publish permissions accordingly.
Save a draft of a document.
Observe that the publish button reappears.
Attempt to click the publish button and note the error.
Navigate to the collection list view and observe that publishing the document is possible without having publish permissions.

Adapters and Plugins
No response

@Bobeta can you give an example of your update/create access functions so I can recreate?

Closing as I could not reproduce. We can reopen this if a reproduction is provided!

@JarrodMFlesch I think, I can reproduce the issue in v3 and the issue should be reopened.
This is my access function
export const cannotPublish: Access = ({ req, data }) => {
  if (!req.user) {
    return false;
  }

  if (data?._status === "published") {
    return false;
  }

  return true;
};

This is the collection's access config:
access: {
    read: () => true,
    create: () => true,
    update: cannotPublish,
    delete: () => false,
}

Observation

On load => "Publish changes" is hidden, "Save Draft" is disabled
When editing a field => "Publish changes" is hidden, "Save Draft" is enabled
After "Save Draft" => "Publish changes" appears ⚠
When clicking "Publish changes" => "You are not allowed to perform this action."


chore: add duplicate render repro to vanilla demo (DO NOT MERGE)

both @cjpillsbury and I could reproduce it on commit https://github.com/muxinc/elements/pull/520/commits/364e3ea83b84a65092f18c44a1add101b48fae20
but not on the latest Mux player version before the tagged template cache key fix
https://github.com/muxinc/elements/pull/520/commits/d6817d46f342b322ce42b5e2faf7cc36fe94836b
conclusion is that potentially it's a bug in the template parts implementation https://github.com/github/template-parts or that code being used in there has an influence on the frozen array of the tagged template (like the generators)
the latest Mux player uses the template parts implementation of https://github.com/dy/template-parts
and it's also using the new Media Chrome theme system which could make a difference too.
closing for now because the cache key by array string value will fix this bug for sure


Feature request: add padding option to components

As the title says, we should add a padding option to our components. But how is it gonna be useful?
We will be able to set our padding between components in a more comfy way, without having to manually add whitespaces. This option will extend how separators works and could look like this
padding = { left = 1, right = 2 },

But there's a separator option that would allow us to set padding by using whitespaces as the value

Yes, you're right but this looks ugly af in my opinion. Also I discovered that galaxyline has a "hidden" (non-documented) feature to set the separator direction (left or right) called position, I thought hey this is really cool, however this will not allow us to say "So I want to have left and right padding on this component".
This feature aims to fix this, by allowing us to set padding in both directions.

But if we implement this, what would happen with separator and the hidden feature that you said?

They will be still here, because there is people using special characters as their components separators and this looks really cool. The new option has a specific use case that separator can cover but in a limited way, so we will have more freedom with it because it is intended only for adding whitespaces (padding) between our components.
Note for myself (and also to you if you want to contribute with this feature): there will be also a precedence order, because we don't want to add padding after our separators, e.g.
separator padding component ----- BAD
padding separator component ----- GOOD

Hey @NTBBloodbath when this feature will be implemented?


Unable to run release build

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Run react-native info in your terminal and paste its contents here.
React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
      Memory: 26.61 MB / 8.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 11.0.0 - /usr/local/bin/node
      Yarn: 1.10.1 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        API Levels: 23, 25, 26, 27, 28
        Build Tools: 23.0.1, 25.0.0, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.1, 28.0.2
        System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>14246
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.1 => 16.6.1
      react-native: 0.57.5 => 0.57.5
    npmGlobalPackages:
      react-native-git-upgrade: 0.2.7

Description
Running the below command to build and hit exception:
xcodebuild clean build -project UdemyFastlaneXX.xcodeproj -configuration Release -scheme UdemyFastlaneXX

EXCEPTIONS
SHA-1 for file /Users/isaac/code/reactnative/UdemyFastlaneXX/index.js is not computed

ReferenceError: SHA-1 for file /Users/isaac/code/reactnative/UdemyFastlaneXX/index.js is not computed
    at DependencyGraph.getSha1 (/Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/node-haste/DependencyGraph.js:201:13)
    at /Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/DeltaBundler/Transformer.js:164:26
    at Generator.next (<anonymous>)
    at step (/Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/DeltaBundler/Transformer.js:31:30)
    at /Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/DeltaBundler/Transformer.js:50:14
    at new Promise (<anonymous>)
    at /Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/DeltaBundler/Transformer.js:28:12
    at Transformer.transformFile (/Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/DeltaBundler/Transformer.js:188:7)
    at /Users/isaac/code/reactnative/UdemyFastlaneXX/node_modules/metro/src/Bundler.js:78:34
    at Generator.next (<anonymous>)

+ [[ false != true ]]
+ [[ ! -f /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app/main.jsbundle ]]
+ echo 'error: File /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app/main.jsbundle does not exist. This must be a bug with'
error: File /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app/main.jsbundle does not exist. This must be a bug with
+ echo 'React Native, please report it here: https://github.com/facebook/react-native/issues'
React Native, please report it here: https://github.com/facebook/react-native/issues
+ exit 2

GenerateDSYMFile /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app.dSYM /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app/UdemyFastlaneXX (in target: UdemyFastlaneXX)
    cd /Users/isaac/Code/ReactNative/UdemyFastlaneXX/ios
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app/UdemyFastlaneXX -o /Users/isaac/Library/Developer/Xcode/DerivedData/UdemyFastlaneXX-eltuekpfuqqbnmboxhdjzwuzjcis/Build/Products/Release-iphoneos/UdemyFastlaneXX.app.dSYM

I can't even build development on Windows unless I remove watchman from the picture. When I do that though, the build seems to time out when I include my node_modules folder.

https://github.com/facebook/react-native/issues/18313  may help you

@CarGuo, thanks for your response. I'm confused though, what in particular might be of help here? I'm using Expo, so it seems not applicable, but maybe I'm mistaken?
Thanks again.

Sorry，My mistake，this may help to this issue with @isaaclem  main.jsbundle does not exist


iPXE for v1.3.0-rc1

I tried to create, but it kept failing.
`FlexBoot v3.6.403 (PCI 02:00.1) starting execution...ok                         e established.
FlexBoot initialising devices...
Initialising completed.
                                                                            nown hosts.

FlexBoot v3.6.403
Features: DNS HTTP HTTPS iSCSI TFTP VLAN ELF MBOOT PXE bzImage COMBOOT Menu PXEX
T
net0: b8:ce:f6:04:90:11
Using ConnectX-4Lx on 0000:02:00.1 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 b8:ce:f6:04:90:11)............................................
................ No configuration methods succeeded (http://ipxe.org/040ee119)
No more ports. Exiting FlexBoot...
Intel(R) Boot Agent GE v1.4.04
Copyright (C) 1997-2012, Intel Corporation
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel Boot Agent.
Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key      `

@rajeshkio What value did you set for ipxe_script in your terraform.tfvars?

@rajeshkio What value did you set for ipxe_script in your terraform.tfvars?

We don't set it in terraform.tfvars now, right?
harvester_version = "v1.3.0-rc1" hostname_prefix   = "rajesh-harvester" node_count        = "2" project_name      = "Harvester Labs" plan              = "c3.small.x86" max_bid_price     = "0.17" metro = "SV" spot_instance     = true ssh_key           = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC4ScCbHjmbnSJmAMVlbRP2552uFncwdGCVFHKIx5tSjMK84e8aibUcX5fdDfLdvvQcOpwL837MQEq9L60vqiS5cPlSg+P4gJ/39v3xL4TVzTWFSehDywM0ifDCTepqQIOZIneHJkdX9PxijYHFc3J0T19WeHWW5M+MIegfSJF5qVjaL1XCGPfHlBnvV5oyhsVnunFFS/kz22BCiPDv9KRLcjJVF9jKOP4U7dH3Ym2SH3KxhOlFcY6bzhJ0+fyfyYRXzeA4QDWIvrP+tr8tEdsKftUI04FtuROgIJgcSGN0cBEqt5W4dNf4Pvv9M1lBi8fQ8VjE8CXBT2VFW9VkuDSfbQb2Ki0Tz7A+e1c+wM9C/DQ5vCv8ImMePVFVTiHWA1/zIg2T1XLx4wBGFyzYCHQWhVxNuxBotqWPOh4x5Z8G+QyhAuiuOtAxfe//5In59wrs0+OraqQ1AsuYcBfN4R1GNvUKvaBnmWeYuiOh5OfxZqDyzBkfCmgXVQbiUIuvKjc= rajesh@rajesh-infracloud" #ipxe_script       = "https://raw.githubusercontent.com/rajeshkio/test-harvester-ipxe/main/ipxe-" num_of_vlans = 2

You going to have to set it there. Until the PR is merged, the script is not there for you to test. Setting it to https://raw.githubusercontent.com/rancherlabs/harvester-equinix-terraform/9e9f20036143cd434dba6c5ae0de3a628a65c699/ipxe/ipxe- should work.

You going to have to set it there. Until the PR is merged, the script is not there for you to test. Setting it to https://raw.githubusercontent.com/rancherlabs/harvester-equinix-terraform/9e9f20036143cd434dba6c5ae0de3a628a65c699/ipxe/ipxe- should work.

 I was testing in the branch, so I thought I don't need to. I forgot that the variable.tf points to the main branch.


CharacterBody3D will not slide on slopes when stop on slopes is disabled.

Godot version
4.1.2 stable
System information
Fedora Linux
Issue description
While adding a velocity against the floor direction, the body will not slide correctly even with stop on slope disabled. The result is a jittery, slow movement.  In this simple example i'm applying gravity to a sphere, which i expect to slide along the floor, but it does not work:

Expected behavior, using a max angle of 0 so it does not treat it like a floor:

Steps to reproduce

Create a CharacterBody3D
Disable stop on slopes
Disable stop on walls (Just to be sure)
Add some gravity to the character body
Call move and slide
The body does not slide.

Minimal reproduction project
CharacterBody3DBug.zip

Thank you for the explanation!  No pressure, just curious if this was seen by the team in first place or it was "lost", knowing it will be eventually fixed allow me to focus on the other parts of the character instead of building workarounds. Thank you again!


Change configuration options to CLI arguments for get_tournaments.py and get_commanders.py

get_tournaments now has a variable overwrite_tourneys and similarly, get_commanders has ignore_unknown. These should be CLI arguments so we can set up cron jobs to trigger updates with the costlier version on a less frequent basis.

Done in https://github.com/JasonQiu21/cedhtop16/pull/32


Artemis should get pixels_per_micron itself

Currently pixels_per_micron is passed in to Artemis, with the work done in https://github.com/DiamondLightSource/python-artemis/pull/334 we should be able to remove this and instead get the value from the zoom level and parameters file

done in #554


After remove & reinstall "node_modules" & "package-lock.json" get "TypeError: vite_ssr_import_2.default is not a function"

What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
Latest version
What version of Remix are you using?
No response
Steps to Reproduce
on Localhost running

Expected Behavior
After remove & reinstall then run localhost "node_modules" & "package-lock.json" get "TypeError: vite_ssr_import_2.default is not a function" error message
Actual Behavior
TypeError: vite_ssr_import_2.default is not a function

I had exactly the same issue.
Just delete your remix.d.ts

Closed. Not enough information to reproduce problem.

Closed. Not enough information to reproduce problem.

Sure... Next time I will upload to github and share its link to everyone to examine and advice on the errors.
I just learnt how to using github now.


pts.js, pts.min.js added to .npmignore and are not served by cdns any longer

It seems that this commit omits files in the dist folder which would expose functions needed to use Pts as an included script. You reference the instruction here and in your readme using links to unpkg, but the resource is missing.
Any chance you can restore these resources or expose the quickStart function and the Pts namespace some other way? I prefer to include it as a script in my use case as I'd rather not maintain a copy of Pts or have build steps for my static page.
For now I've just updated my reference to pull the 0.10.10 resource specifically, just before this change.

Thanks for reporting this. I was updating the (old!) build system for v0.11 but missed this CDN use case. This has been fixed in 0.11.2.

Should be working now. Give it a try and thank you again!
<EMAIL_ADDRESS>


Product only added to SQL-table offer_rangeproduct if removed and added again

Issue Summary
I use django-graphene (GraphQL) together with Oscar so I don't know how this behaves with the Oscar frontend.
I have added a range called LandingPage so that I can add products to my front-page.
query LandingPage {
  viewer {
    landingPage {
      edges {
        node {
          name
            includedProducts {
	      edges {
	        node {
		      title
		      images {
		      edges {
		         node {
		              original
		          }
		      }
		    }
		  }
	       }
	     }
	    }
          }

       }
   }
}

If I add and save the range "LandingPage", also checking that the products are in the range, the products are not added to the SQL-table offer_rangeproduct. But if I remove and add them again they get added to the table. Is it suppose to be like this?
I added a picture to show which section I mean.

As a side comment: I think Oscar works quite good together with a GraphQL-schema. Data gets extracted quite easily.
Technical details

Python version: 3.7.
Django version: 2.08.
Oscar version: 1.64.

I believe the issue is not related directly with the Oscar itself, since Oscar does not have any raw SQL queries or etc.

As noted above this seems to be happening at the database abstraction layer. If you can narrow this down to an issue with Oscar itself, as opposed to with django-graphene, please reopen this with additional details of how to reproduce this directly in Oscar.


Replicator authentication breaks if password contains @

Description
It looks like CouchDB 3.0 does not correctly handle replication urls with credentials containing an @ char. Other preserved characters does not seem to cause any problems, though.
The correct way for basic auth urls is to percent encode (e.g. using encodeURIComponent()) the credential part, see chapter 2 of the URI RFC. For example, consider a username<EMAIL_ADDRESS>and a password secure, a basic auth url would look like this<EMAIL_ADDRESS>There are different ways to trigger replications, but I have only tested the issue with the classic _replicate endpoint. Here we post a JSON specifying the replication, eg:
{
  "source": "https://couch.example.com/my-db",
  "target": "https://anothercouch.example.com/another-db"
}

If the databases are protected, we can use basic authentication:
{
  "source"<EMAIL_ADDRESS>  "target"<EMAIL_ADDRESS>}

And this is where we were hit. Now our password contained an @ char, for example p@ssword. The correct way to supply the password would be:
{
  "source"<EMAIL_ADDRESS>  "target"<EMAIL_ADDRESS>}

We can circumvent this problem by using the object syntax for replication source and target:
{
  "source": {
    "url": "https://couch.example.com/my-db",
    "headers": {
      "Authorization": "Basic YWxpY2U6cGFzc3dvcmQ="
    }
  },
  "target": {
    "url":  "https://anothercouch.example.com/another-db",
    "headers": {
      "Authorization": "Basic Ym9iOnBAc3N3b3Jk"
    }
}

The Authorization headers include the base64 encoded credential string like the usual Basic auth header:
echo -n "alice:password" | base64
echo -n "bob:p@ssword" | base64

Steps to Reproduce
Start a couch. I used Docker for this:
docker run --rm -p 5984:5984 --name couchdb -e COUCHDB_USER=admin -e COUCHDB_PASSWORD=admin couchdb:3.0

and set COUCHDB_ADMIN_URL environment variable including admin credentials for convenience:
export COUCHDB_ADMIN_URL="http://admin:admin@localhost:5984"

Configure an admin user containing @ char:
curl -XPUT "$COUCHDB_ADMIN_URL/_node/nonode@nohost/_config/admins/bob" -d '"p@ssword"'

Create a db to replicate
curl -XPUT "$COUCHDB_ADMIN_URL/alice-db"

Issue replication
curl -XPOST "$COUCHDB_ADMIN_URL/_replicate"  \
  -H 'Content-Type:application/json' \
  -d "{\"source\": \"$COUCHDB_ADMIN_URL/alice-db\", \"target\": \"http://bob:p%40ssword@localhost:5984/alice-db-copy-for-bob\", \"create_target\": true }"

replication fails with
{"error":"replication_auth_error","reason":"{session_request_unauthorized,\"http://localhost:5984/_session\",\"bob\"}"}

Expected Behaviour

URLs provided in replication requests should support basic authentication even if special chars like @ is used, in which case the credentials part should be percent encoded.

Your Environment

CouchDB version used: 3.0.0

Hi @jo ,
A workaround (for now) is to create the replication using the Basic authentication header in your replication document, instead of specifying the credentials in the URL.
This is just a workaround, we need to determine if this is a regression or not and resolve the issue. Just want to get you on your way :)
The source and target properties can be urls, or they can be a json object with {“url”:”url in here”, “headers”: {“header1”:”value1”, …}} properties. You could specify a Bearer or Authorization header in there.

The fix for this is provided in https://github.com/apache/couchdb/commit/1860ebbf2fa1731a62f3c9b107b2e52811489c1e
Documentation was updated as well: https://docs.couchdb.org/en/stable/replication/replicator.html?highlight=auth#specifying-usernames-and-passwords
The preferred version is:
{
    "target": {
        "url": "http://someurl.com/mydb",
        "auth": {
            "basic": {
                "username": "$username",
                "password": "$password"
             }
        }
    },
    ...
}


Incorrect code example

In git readme.md in first code example, arguments to method is shown as array
var Dwolla = require('dwolla-node')(['{CLIENT_ID}', '{CLIENT_SECRET}']);

I misunderstood that and passed client id and secret as array. Better change it to
var Dwolla = require('dwolla-node')('{CLIENT_ID}', '{CLIENT_SECRET}');

ping