facade/ignition-contracts should be part of require instead of require-dev

Describe the bug

My Laravel project does not have facade/ignition installed, so some exceptions thrown by stancl/tenancy end with
Symfony \ Component \ Debug \ Exception \ FatalErrorException (E_UNKNOWN)
Interface 'Facade\IgnitionContracts\ProvidesSolution' not found

This is because facade/ignition-contracts is only part of require-dev not require in composer.json
Steps to reproduce
Remove facade/ignition from project and trigger exception, e.g. TenantCouldNotBeIdentifiedException
Expected behavior
See the real exception TenantCouldNotBeIdentifiedException instead of Interface 'Facade\IgnitionContracts\ProvidesSolution' not found
This works if facade/ignition-contracts is installed manually.
Your setup

Laravel version: 6.5.2
stancl/tenancy version: 2.2.0
Storage driver: database

Hi,
thanks for reporting this. Fixed in https://github.com/stancl/tenancy/commit/4e477b472feff93fdfe6d4a23963b5e295171dc9.
After tests in CI pass, I'll tag 2.2.1. So in about 10 minutes, running composer update should fix.

awesome! :+1:


UWP support

Hi, I used to be a Microsoft uwp developer, now turning to Flutter.
But If Flutter support uwp, that will be perfect.
[This issue will be closed in a few days, just let the flutter team hear the voice.]

#30726

Closing as a duplicate of 30726 and #14967


Web Site for the Project

I started the gh-pages branch awhile ago and haven't gotten any time to put towards it.  Mainly due to wanting to make the API as feature-rich as possible and because my UI skills are sub par.  That being the case, I'll gladly take any suggestions or help on getting a basic static content site going in the gh-pages branch.  Thanks!

Up and running for now though a more customized version would be preferred.  http://briandowns.github.io/openweathermap/


Added documentation regarding inter-resource set dependency constraints (#5786)

Pull request opened by the merge tool on behalf of #5786

Merged in 21ac917df9b3b7cd18153ddaff2ebb83f4d17980


test(config): fuzz profile sections

added more tests to cover current fallback behavior with profiles. the logic is the following

if the selected profile is default and no invariant config values were set, then common values (runs, dictionary_weight etc) will be taken from fuzz section if present or InvariantConfig::default
if the selected profile is other than default and no invariant section present, the common values will be taken from [profile.default.invariant] (which in turn falls back to [profile.default.fuzz])

open for comments. happy to change/revert the fallback if it's too confusing
cc @mds1 @devtooligan @transmissions11 @gakonst

That fallback logic makes sense to me 👌
What is the full list of common params between fuzz and invariant that this applies for? From running forge config I see run, dictionary_weight, include_storage, and include_push_bytes, which all makes sense. And I'd expect seed to be the last one but don't see that in the invariant section

@mds1 i think it's omitted because seed is optional and is None by default

@mds1 we can discuss it here, that's fine. just tried setting default seed for [fuzz] locally and it showed up in pretty print. so, toml::to_string_pretty simply omits Option::None

Got it, that's good to know. We may want to have the entire config, including empty values, show up in forge config, so it's fully self-documenting in that sense. Right now there's potentially an edge case where None isn't a default setting for a param, so you specify that in the config, but then forge config doesn't print it
Also is seed = None the right way to specify that in the toml?

@mds1 that's actually invalid toml. the correct way would be to omit the seed

Got it, thank you for the info! 🙏

We should document all these ways to set values for forge config btw, e.g. the fallback rules mentioned in the OP

@gakonst agreed, i added fuzz & invariant configs today. will amend those sections

done https://github.com/foundry-rs/book/pull/574


Return details of custom function libraries

As the title indicates, details of custom function libraries should be passed to the frontend to be able to provide suggestions on them.

We are handling with @FhirPathFunction annotation tags.


HDDS-1819. Implement S3 Commit MPU request to use Cache and DoubleBuffer.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
37
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
620
trunk passed

+1
compile
361
trunk passed

+1
checkstyle
62
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
793
branch has no errors when building and testing our client artifacts.

+1
javadoc
153
trunk passed

0
spotbugs
410
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
602
trunk passed

_ Patch Compile Tests _

+1
mvninstall
545
the patch passed

+1
compile
364
the patch passed

+1
javac
364
the patch passed

+1
checkstyle
72
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
647
patch has no errors when building and testing our client artifacts.

+1
javadoc
156
the patch passed

+1
findbugs
694
the patch passed

_ Other Tests _

+1
unit
295
hadoop-hdds in the patch passed.

-1
unit
1679
hadoop-ozone in the patch failed.

+1
asflicense
47
The patch does not generate ASF License warnings.

7292

Reason
Tests

Failed junit tests
hadoop.ozone.om.snapshot.TestOzoneManagerSnapshotProvider

hadoop.ozone.client.rpc.TestOzoneRpcClientWithRatis

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.ozone.client.rpc.TestCloseContainerHandlingByClient

hadoop.ozone.TestStorageContainerManager

hadoop.ozone.client.rpc.TestCommitWatcher

hadoop.ozone.client.rpc.TestOzoneClientRetriesOnException

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

Subsystem
Report/Notes

Docker
Client=19.03.0 Server=19.03.0 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1140

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 9aed8d5664cf 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c533b79

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/1/testReport/

Max. process+thread count
3883 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thank You @arp7 for the review.
Addressed the review comments.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
1012
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
641
trunk passed

+1
compile
386
trunk passed

+1
checkstyle
74
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1001
branch has no errors when building and testing our client artifacts.

+1
javadoc
230
trunk passed

0
spotbugs
539
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
795
trunk passed

_ Patch Compile Tests _

+1
mvninstall
702
the patch passed

+1
compile
448
the patch passed

+1
javac
448
the patch passed

+1
checkstyle
94
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
1
The patch has no whitespace issues.

+1
shadedclient
895
patch has no errors when building and testing our client artifacts.

+1
javadoc
215
the patch passed

+1
findbugs
841
the patch passed

_ Other Tests _

+1
unit
400
hadoop-hdds in the patch passed.

-1
unit
2650
hadoop-ozone in the patch failed.

+1
asflicense
42
The patch does not generate ASF License warnings.

10636

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

hadoop.hdds.scm.pipeline.TestRatisPipelineProvider

hadoop.ozone.client.rpc.TestOzoneClientRetriesOnException

hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.ozone.om.snapshot.TestOzoneManagerSnapshotProvider

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.ozone.client.rpc.TestCloseContainerHandlingByClient

hadoop.ozone.client.rpc.TestWatchForCommit

hadoop.ozone.client.rpc.TestOzoneRpcClientWithRatis

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

Subsystem
Report/Notes

Docker
Client=18.09.7 Server=18.09.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1140

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 3e381da75de5 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / ecb9f81

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/2/testReport/

Max. process+thread count
5030 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1140/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thank You @arp7 and @xiaoyuyao for the review.
I have committed this to trunk.


use cargo install --git

use cargo install --git
set proper permissions for executable

you could also pass --locked to cargo if you want

@camuward thanks for contributing 👍🏽


Need an example of @JunctionTable where column names are specified

I'm trying 1.0.0-rc1, but this still doesn't seem to have support for this (at least I couldn't find an example in the repo).
The DB schema looks like this:
CREATE TABLE routes (route STRING PRIMARY KEY, color INTEGER, oppositecolor INTEGER, pathblob BLOB, listorder INTEGER, agencyid INTEGER, routetitle STRING);
CREATE TABLE stopmapping (route STRING, tag STRING, PRIMARY KEY (route, tag));
CREATE TABLE stops (tag STRING PRIMARY KEY, lat FLOAT, lon FLOAT, title STRING, parent STRING);

The Stops interface includes this:
    @JunctionTable(name="stopmapping")
    @ManyToMany
    Set<Routes> getRoutes();

The Routes interface includes this:
    @ManyToMany
    Set<Stops> getStops();

@JunctionTable appears to be able to take a columns parameter but I can't figure out what to put into it.  I tried doing
columns = { "route", "tag"}
but it wanted Column data types, so I also tried this, but it wanted constants:
columns = { RouteEntity.ROUTE, StopsEntity.TAG }
Neither seem to work because when I do StopsEntity.getRoutes(), it tries using routesId and stopsId for the column names instead of route and tag :-(

Annotations can only contain compile time constants, check the type to see it takes @Column not strings or attributes the other things won't compile. However this currently only mean't to define the foreign key columns not arbitrary columns. For your case you should define your own type using @JunctionTable.type()
    @JunctionTable(columns = {
            @Column(name = "personId", foreignKey =
                @ForeignKey(references = AbstractPerson.class, referencedColumn = "id")),
            @Column(name = "groupId", foreignKey =
                @ForeignKey(references = AbstractGroup.class, referencedColumn = "id")) } )

I think there's a bug...it seems to be mixing the class and column names which your test above wouldn't notice because both referenced columns are "id" :-)
I used this:
    @JunctionTable(name="stopmapping", columns = {
            @Column(name = "route", foreignKey =
            @ForeignKey(references = RoutesEntity.class, referencedColumn = "route")),
            @Column(name = "tag", foreignKey =
            @ForeignKey(references = StopsEntity.class, referencedColumn = "tag")) })
    @ManyToMany
    Set<Routes> getRoutes();

But the generated code (thanks for the source.setDefaultLogging setting :-) looks like this:
select a."route", a."agencyid", a."color", a."listorder", a."oppositecolor", a."pathblob", a."routetitle" from routes a inner join stopmapping b on a."route" = b."tag" inner join stops c on b."route" = c."tag" where c."tag" = '36540';
Note that it's matching a.route w/ b.tag and b.route with c.tag.  I can hack around it for now by flipping the column names but I suspect that wasn't the intention :-)

@npurushe : 'fraid this code change didn't work.  When I do a stop.getRoutes() in my code, I get this error now:
Attempt to invoke interface method 'java.lang.Object io.requery.util.function.Supplier.get()' on a null object reference
at this line in EntityReader:
QueryAttribute<E, Object> tId = Attributes.get(tKey.getReferencedAttribute());
instead of no results.  There is no SQL output by the Requery obviously...fails before it gets to that point.
On the bright side, thanks for the @Transient fix...that worked well :-)

not sure if this helps, but during compile time, it sends out a bunch of these errors too:
Warning:(38, 23) Couldn't find referenced element com.keysolutions.mbtafail.db.models.RoutesEntity for com.keysolutions.mbtafail.db.models.Stopmapping.route
Warning:(29, 23) Couldn't find referenced element com.keysolutions.mbtafail.db.models.StopsEntity for com.keysolutions.mbtafail.db.models.Stopmapping.tag
Warning:Couldn't find referenced element com.keysolutions.mbtafail.db.models.RoutesEntity for com.keysolutions.mbtafail.db.models.Stopmapping.route
Warning:Couldn't find referenced element com.keysolutions.mbtafail.db.models.StopsEntity for com.keysolutions.mbtafail.db.models.Stopmapping.tag
Warning:Couldn't find referenced element com.keysolutions.mbtafail.db.models.RoutesEntity for com.keysolutions.mbtafail.db.models.Stopmapping.route
Warning:Couldn't find referenced element com.keysolutions.mbtafail.db.models.StopsEntity for com.keysolutions.mbtafail.db.models.Stopmapping.tag

Try using the source class (abstract class or interface) in references instead of the generated type.

@npurushe Thanks..that did it.  I updated my wiki page on that too in case you haven't used it yet :-)


[BUG] failing on linux kernel >= 5.12.2 (and >= 5.11.19, ...)

What did you do

How was the cluster created?

k3d cluster create "vald-cluster" -p "8081:80@loadbalancer" --agents 5

What did you do afterwards?

k3d commands?
docker commands?
OS operations (e.g. shutdown/reboot)?

What did you expect to happen
I expect that k3d works with the latest kernels, just as it worked with Linux Kernel 5.11.
When multiple Agents were specified, k3d did not proceed to start the Agents when the cluster was created, and the Docker logs showed that the K3D Server was restarting at a high frequency.
In the container log, it looks like kube-proxy is failing to start due to failure to set nf_conntrack_max.
I looked into this a bit and found a similar problem in kind and minikube, and it seems to be fixed in the following Issue and PR.
for kind
https://github.com/kubernetes-sigs/kind/issues/2240
https://github.com/kubernetes-sigs/kind/pull/2241
for minikube
https://github.com/kubernetes/minikube/pull/11419
Screenshots or terminal output
k3d command cli log
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-vald-cluster' (dd17969b82f64e60516154a7a8492e91daf0e1eb9f4ed8a70d5d6d57601b3692)
INFO[0000] Created volume 'k3d-vald-cluster-images'
INFO[0001] Creating node 'k3d-vald-cluster-server-0'
INFO[0001] Creating node 'k3d-vald-cluster-agent-0'
INFO[0001] Creating node 'k3d-vald-cluster-agent-1'
INFO[0001] Creating node 'k3d-vald-cluster-agent-2'
INFO[0001] Creating node 'k3d-vald-cluster-agent-3'
INFO[0001] Creating node 'k3d-vald-cluster-agent-4'
INFO[0001] Creating LoadBalancer 'k3d-vald-cluster-serverlb'
INFO[0001] Starting cluster 'vald-cluster'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-vald-cluster-server-0'
INFO[0005] Starting agents...
INFO[0005] Starting Node 'k3d-vald-cluster-agent-0'  <----- creating process stops here!!!

docker ps
CONTAINER ID   IMAGE                      COMMAND                  CREATED         STATUS                          PORTS     NAMES
4ad2f4712ae1   rancher/k3s:v1.20.6-k3s1   "/bin/k3s agent"         6 minutes ago   Up 3 minutes                              k3d-vald-cluster-agent-0
f9e815595dcf   rancher/k3s:v1.20.6-k3s1   "/bin/k3s server --t…"   6 minutes ago   Restarting (1) 42 seconds ago             k3d-vald-cluster-server-0

docker logs --defail -t f9e815595dcf
2021-05-16T05:05:29.445125257Z  time="2021-05-16T05:05:29.444942848Z" level=info msg="Starting k3s v1.20.6+k3s1 (8d043282)"
2021-05-16T05:05:29.445182399Z  time="2021-05-16T05:05:29.445150819Z" level=info msg="Cluster bootstrap already complete"
2021-05-16T05:05:29.455391273Z  time="2021-05-16T05:05:29.455257589Z" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
2021-05-16T05:05:29.455407602Z  time="2021-05-16T05:05:29.455285849Z" level=info msg="Configuring database table schema and indexes, this may take a moment..."
2021-05-16T05:05:29.455409948Z  time="2021-05-16T05:05:29.455311476Z" level=info msg="certificate CN=k3s,O=k3s signed by CN=k3s-server-ca@1621141073: notBefore=2021-05-16 04:57:53 +0000 UTC notAfter=2022-05-16 05:05:29 +0000 UTC"
2021-05-16T05:05:29.455444959Z  time="2021-05-16T05:05:29.455362850Z" level=info msg="Database tables and indexes are up to date"
2021-05-16T05:05:29.456363097Z  time="2021-05-16T05:05:29.456238613Z" level=info msg="Kine listening on unix://kine.sock"
2021-05-16T05:05:29.456432105Z  time="2021-05-16T05:05:29.456335058Z" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,k3s --authorization-mode=Node,RBAC --bind-address=<IP_ADDRESS> --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction --etcd-servers=unix://kine.sock --feature-gates=ServiceAccountIssuerDiscovery=false --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/k3s/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=<IP_ADDRESS>/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
2021-05-16T05:05:29.456995072Z  Flag --insecure-port has been deprecated, This flag has no effect now and will be removed in v1.24.
2021-05-16T05:05:29.457269375Z  I0516 05:05:29.457197       7 server.go:659] external host was not specified, using <IP_ADDRESS>
2021-05-16T05:05:29.457451380Z  I0516 05:05:29.457389       7 server.go:196] Version: v1.20.6+k3s1
2021-05-16T05:05:29.460661489Z  I0516 05:05:29.460623       7 shared_informer.go:240] Waiting for caches to sync for node_authorizer
2021-05-16T05:05:29.461489325Z  I0516 05:05:29.461466       7 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
2021-05-16T05:05:29.461498436Z  I0516 05:05:29.461474       7 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
2021-05-16T05:05:29.462113819Z  I0516 05:05:29.462055       7 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
2021-05-16T05:05:29.462123361Z  I0516 05:05:29.462061       7 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
2021-05-16T05:05:29.474074978Z  I0516 05:05:29.473963       7 instance.go:289] Using reconciler: lease
2021-05-16T05:05:29.492167498Z  I0516 05:05:29.492094       7 rest.go:131] the default service ipfamily for this cluster is: IPv4
2021-05-16T05:05:29.650038941Z  W0516 05:05:29.649900       7 genericapiserver.go:425] Skipping API batch/v2alpha1 because it has no resources.
2021-05-16T05:05:29.655280702Z  W0516 05:05:29.655185       7 genericapiserver.go:425] Skipping API discovery.k8s.io/v1alpha1 because it has no resources.
2021-05-16T05:05:29.661628727Z  W0516 05:05:29.661533       7 genericapiserver.go:425] Skipping API node.k8s.io/v1alpha1 because it has no resources.
2021-05-16T05:05:29.666259481Z  W0516 05:05:29.666153       7 genericapiserver.go:425] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
2021-05-16T05:05:29.668215081Z  W0516 05:05:29.668089       7 genericapiserver.go:425] Skipping API scheduling.k8s.io/v1alpha1 because it has no resources.
2021-05-16T05:05:29.671398493Z  W0516 05:05:29.671305       7 genericapiserver.go:425] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
2021-05-16T05:05:29.672868265Z  W0516 05:05:29.672771       7 genericapiserver.go:425] Skipping API flowcontrol.apiserver.k8s.io/v1alpha1 because it has no resources.
2021-05-16T05:05:29.676425119Z  W0516 05:05:29.676254       7 genericapiserver.go:425] Skipping API apps/v1beta2 because it has no resources.
2021-05-16T05:05:29.676434571Z  W0516 05:05:29.676262       7 genericapiserver.go:425] Skipping API apps/v1beta1 because it has no resources.
2021-05-16T05:05:29.681968471Z  I0516 05:05:29.681798       7 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
2021-05-16T05:05:29.681978716Z  I0516 05:05:29.681805       7 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
2021-05-16T05:05:29.689958434Z  time="2021-05-16T05:05:29.689772088Z" level=info msg="Running kube-scheduler --address=<IP_ADDRESS> --bind-address=<IP_ADDRESS> --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --leader-elect=false --port=10251 --profiling=false --secure-port=0"
2021-05-16T05:05:29.690001012Z  time="2021-05-16T05:05:29.689866940Z" level=info msg="Waiting for API server to become available"
2021-05-16T05:05:29.690364949Z  time="2021-05-16T05:05:29.690274194Z" level=info msg="Running kube-controller-manager --address=<IP_ADDRESS> --allocate-node-cidrs=true --bind-address=<IP_ADDRESS> --cluster-cidr=<IP_ADDRESS>/16 --cluster-signing-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --leader-elect=false --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --secure-port=0 --service-account-private-key-file=/var/lib/rancher/k3s/server/tls/service.key --use-service-account-credentials=true"
2021-05-16T05:05:29.691579980Z  time="2021-05-16T05:05:29.691499972Z" level=info msg="Node token is available at /var/lib/rancher/k3s/server/token"
2021-05-16T05:05:29.691588379Z  time="2021-05-16T05:05:29.691532877Z" level=info msg="To join node to cluster: k3s agent -s https://<IP_ADDRESS>:6443 -t ${NODE_TOKEN}"
2021-05-16T05:05:29.692480504Z  time="2021-05-16T05:05:29.692335848Z" level=info msg="Wrote kubeconfig /output/kubeconfig.yaml"
2021-05-16T05:05:29.692511505Z  time="2021-05-16T05:05:29.692424415Z" level=info msg="Run: k3s kubectl"
2021-05-16T05:05:29.692662540Z  time="2021-05-16T05:05:29.692560855Z" level=info msg="Module overlay was already loaded"
2021-05-16T05:05:29.692668059Z  time="2021-05-16T05:05:29.692584060Z" level=info msg="Module nf_conntrack was already loaded"
2021-05-16T05:05:29.692691286Z  time="2021-05-16T05:05:29.692590031Z" level=info msg="Module br_netfilter was already loaded"
2021-05-16T05:05:29.693054521Z  time="2021-05-16T05:05:29.692989749Z" level=warning msg="Failed to start iptable_nat module"
2021-05-16T05:05:29.703958256Z  time="2021-05-16T05:05:29.703817885Z" level=info msg="Cluster-Http-Server 2021/05/16 05:05:29 http: TLS handshake error from <IP_ADDRESS>:49440: remote error: tls: bad certificate"
2021-05-16T05:05:29.706308528Z  time="2021-05-16T05:05:29.706185602Z" level=info msg="Cluster-Http-Server 2021/05/16 05:05:29 http: TLS handshake error from <IP_ADDRESS>:49446: remote error: tls: bad certificate"
2021-05-16T05:05:29.717045241Z  time="2021-05-16T05:05:29.716906780Z" level=info msg="certificate CN=k3d-vald-cluster-server-0 signed by CN=k3s-server-ca@1621141073: notBefore=2021-05-16 04:57:53 +0000 UTC notAfter=2022-05-16 05:05:29 +0000 UTC"
2021-05-16T05:05:29.718456054Z  time="2021-05-16T05:05:29.718327116Z" level=info msg="certificate CN=system:node:k3d-vald-cluster-server-0,O=system:nodes signed by CN=k3s-client-ca@1621141073: notBefore=2021-05-16 04:57:53 +0000 UTC notAfter=2022-05-16 05:05:29 +0000 UTC"
2021-05-16T05:05:29.743269834Z  time="2021-05-16T05:05:29.743103566Z" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
2021-05-16T05:05:29.743306120Z  time="2021-05-16T05:05:29.743211177Z" level=info msg="Running containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd"
2021-05-16T05:05:30.745224049Z  time="2021-05-16T05:05:30.745113942Z" level=info msg="Containerd is now running"
2021-05-16T05:05:30.749774235Z  time="2021-05-16T05:05:30.749667049Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:6443/v1-k3s/connect"
2021-05-16T05:05:30.750983191Z  time="2021-05-16T05:05:30.750914236Z" level=info msg="Handling backend connection request [k3d-vald-cluster-server-0]"
2021-05-16T05:05:30.751362185Z  time="2021-05-16T05:05:30.751272040Z" level=info msg="Running kubelet --address=<IP_ADDRESS> --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/k3s/agent/client-ca.crt --cloud-provider=external --cluster-dns=<IP_ADDRESS> --cluster-domain=cluster.local --cni-bin-dir=/bin --cni-conf-dir=/var/lib/rancher/k3s/agent/etc/cni/net.d --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=<IP_ADDRESS> --hostname-override=k3d-vald-cluster-server-0 --kubeconfig=/var/lib/rancher/k3s/agent/kubelet.kubeconfig --node-labels= --pod-manifest-path=/var/lib/rancher/k3s/agent/pod-manifests --read-only-port=0 --resolv-conf=/tmp/k3s-resolv.conf --serialize-image-pulls=false --tls-cert-file=/var/lib/rancher/k3s/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/k3s/agent/serving-kubelet.key"
2021-05-16T05:05:30.751655452Z  time="2021-05-16T05:05:30.751584847Z" level=info msg="Running kube-proxy --cluster-cidr=<IP_ADDRESS>/16 --healthz-bind-address=<IP_ADDRESS> --hostname-override=k3d-vald-cluster-server-0 --kubeconfig=/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig --proxy-mode=iptables"
2021-05-16T05:05:30.751837779Z  Flag --cloud-provider has been deprecated, will be removed in 1.23, in favor of removing cloud provider code from Kubelet.
2021-05-16T05:05:30.751843191Z  Flag --containerd has been deprecated, This is a cadvisor flag that was mistakenly registered with the Kubelet. Due to legacy concerns, it will follow the standard CLI deprecation timeline before being removed.
2021-05-16T05:05:30.751929721Z  W0516 05:05:30.751853       7 server.go:226] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
2021-05-16T05:05:30.752339535Z  I0516 05:05:30.752269       7 server.go:412] Version: v1.20.6+k3s1
2021-05-16T05:05:30.752347133Z  W0516 05:05:30.752286       7 proxier.go:651] Failed to read file /lib/modules/5.12.3-zen1-1-zen/modules.builtin with error open /lib/modules/5.12.3-zen1-1-zen/modules.builtin: no such file or directory. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
2021-05-16T05:05:30.752714692Z  W0516 05:05:30.752674       7 proxier.go:661] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
2021-05-16T05:05:30.752975127Z  W0516 05:05:30.752944       7 proxier.go:661] Failed to load kernel module ip_vs_rr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
2021-05-16T05:05:30.753328453Z  W0516 05:05:30.753198       7 proxier.go:661] Failed to load kernel module ip_vs_wrr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
2021-05-16T05:05:30.753597919Z  W0516 05:05:30.753517       7 proxier.go:661] Failed to load kernel module ip_vs_sh with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
2021-05-16T05:05:30.753896991Z  W0516 05:05:30.753828       7 proxier.go:661] Failed to load kernel module nf_conntrack with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
2021-05-16T05:05:30.756976987Z  time="2021-05-16T05:05:30.756939289Z" level=info msg="Waiting for node k3d-vald-cluster-server-0 CIDR not assigned yet"
2021-05-16T05:05:30.757863082Z  E0516 05:05:30.757804       7 node.go:161] Failed to retrieve node info: nodes "k3d-vald-cluster-server-0" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
2021-05-16T05:05:30.766593282Z  I0516 05:05:30.766529       7 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/agent/client-ca.crt
2021-05-16T05:05:30.766603912Z  W0516 05:05:30.766573       7 manager.go:159] Cannot detect current cgroup on cgroup v2
2021-05-16T05:05:30.826258097Z  I0516 05:05:30.826155       7 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
2021-05-16T05:05:30.826278544Z  I0516 05:05:30.826163       7 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
2021-05-16T05:05:30.826402499Z  I0516 05:05:30.826374       7 dynamic_serving_content.go:130] Starting serving-cert::/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt::/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key
2021-05-16T05:05:30.826668880Z  I0516 05:05:30.826616       7 secure_serving.go:197] Serving securely on <IP_ADDRESS>:6444
2021-05-16T05:05:30.826678699Z  I0516 05:05:30.826636       7 autoregister_controller.go:141] Starting autoregister controller
2021-05-16T05:05:30.826681363Z  I0516 05:05:30.826640       7 cache.go:32] Waiting for caches to sync for autoregister controller
2021-05-16T05:05:30.826683407Z  I0516 05:05:30.826649       7 tlsconfig.go:240] Starting DynamicServingCertificateController
2021-05-16T05:05:30.826759615Z  I0516 05:05:30.826736       7 available_controller.go:475] Starting AvailableConditionController
2021-05-16T05:05:30.826764180Z  I0516 05:05:30.826742       7 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
2021-05-16T05:05:30.826770368Z  I0516 05:05:30.826754       7 controller.go:83] Starting OpenAPI AggregationController
2021-05-16T05:05:30.826776183Z  I0516 05:05:30.826761       7 apf_controller.go:261] Starting API Priority and Fairness config controller
2021-05-16T05:05:30.826937152Z  I0516 05:05:30.826838       7 dynamic_serving_content.go:130] Starting aggregator-proxy-cert::/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt::/var/lib/rancher/k3s/server/tls/client-auth-proxy.key
2021-05-16T05:05:30.826942590Z  I0516 05:05:30.826867       7 apiservice_controller.go:97] Starting APIServiceRegistrationController
2021-05-16T05:05:30.826945390Z  I0516 05:05:30.826872       7 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
2021-05-16T05:05:30.826970033Z  I0516 05:05:30.826937       7 crdregistration_controller.go:111] Starting crd-autoregister controller
2021-05-16T05:05:30.826978302Z  I0516 05:05:30.826945       7 shared_informer.go:240] Waiting for caches to sync for crd-autoregister
2021-05-16T05:05:30.827001376Z  I0516 05:05:30.826966       7 customresource_discovery_controller.go:209] Starting DiscoveryController
2021-05-16T05:05:30.827061951Z  I0516 05:05:30.827035       7 controller.go:86] Starting OpenAPI controller
2021-05-16T05:05:30.827105498Z  I0516 05:05:30.827068       7 cluster_authentication_trust_controller.go:440] Starting cluster_authentication_trust_controller controller
2021-05-16T05:05:30.827117880Z  I0516 05:05:30.827084       7 shared_informer.go:240] Waiting for caches to sync for cluster_authentication_trust_controller
2021-05-16T05:05:30.827144380Z  I0516 05:05:30.827123       7 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
2021-05-16T05:05:30.827176146Z  I0516 05:05:30.827143       7 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
2021-05-16T05:05:30.827208563Z  I0516 05:05:30.827073       7 naming_controller.go:291] Starting NamingConditionController
2021-05-16T05:05:30.827256586Z  I0516 05:05:30.827233       7 establishing_controller.go:76] Starting EstablishingController
2021-05-16T05:05:30.827308442Z  I0516 05:05:30.827283       7 nonstructuralschema_controller.go:192] Starting NonStructuralSchemaConditionController
2021-05-16T05:05:30.827353842Z  I0516 05:05:30.827330       7 apiapproval_controller.go:186] Starting KubernetesAPIApprovalPolicyConformantConditionController
2021-05-16T05:05:30.827395085Z  I0516 05:05:30.827374       7 crd_finalizer.go:266] Starting CRDFinalizer
2021-05-16T05:05:30.831179268Z  time="2021-05-16T05:05:30.831125056Z" level=info msg="Running cloud-controller-manager with args --profiling=false"
2021-05-16T05:05:30.833689279Z  I0516 05:05:30.833640       7 controllermanager.go:141] Version: v1.20.6+k3s1
2021-05-16T05:05:30.840625877Z  E0516 05:05:30.840565       7 controller.go:156] Unable to remove old endpoints from kubernetes service: no master IPs were listed in storage, refusing to erase all endpoints for the kubernetes service
2021-05-16T05:05:30.861097073Z  I0516 05:05:30.860948       7 shared_informer.go:247] Caches are synced for node_authorizer
2021-05-16T05:05:30.927147030Z  I0516 05:05:30.926809       7 cache.go:39] Caches are synced for autoregister controller
2021-05-16T05:05:30.927212193Z  I0516 05:05:30.926844       7 apf_controller.go:266] Running API Priority and Fairness config worker
2021-05-16T05:05:30.927229303Z  I0516 05:05:30.926892       7 cache.go:39] Caches are synced for AvailableConditionController controller
2021-05-16T05:05:30.927240386Z  I0516 05:05:30.926923       7 cache.go:39] Caches are synced for APIServiceRegistrationController controller
2021-05-16T05:05:30.927394395Z  I0516 05:05:30.927149       7 shared_informer.go:247] Caches are synced for crd-autoregister
2021-05-16T05:05:30.927418697Z  I0516 05:05:30.927158       7 shared_informer.go:247] Caches are synced for cluster_authentication_trust_controller
2021-05-16T05:05:31.779966985Z  I0516 05:05:31.779715       7 node.go:172] Successfully retrieved node IP: <IP_ADDRESS>
2021-05-16T05:05:31.780031732Z  I0516 05:05:31.779791       7 server_others.go:143] kube-proxy node IP is an IPv4 address (<IP_ADDRESS>), assume IPv4 operation
2021-05-16T05:05:31.781659505Z  I0516 05:05:31.781468       7 server_others.go:186] Using iptables Proxier.
2021-05-16T05:05:31.782141843Z  I0516 05:05:31.781934       7 server.go:650] Version: v1.20.6+k3s1
2021-05-16T05:05:31.783060048Z  I0516 05:05:31.782851       7 conntrack.go:103] Set sysctl 'net/netfilter/nf_conntrack_max' to 524288
2021-05-16T05:05:31.783130013Z  F0516 05:05:31.782902       7 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_max: permission denied

Which OS & Architecture
OS: Arch Linux x86_64
Host: 20QTCTO1WW ThinkPad P1 Gen 2
Kernel: 5.12.3-zen1-1-zen
Shell: zsh 5.8
CPU: Intel i9-9880H (16) @ 4.800GHz
GPU: Intel UHD Graphics 630
GPU: NVIDIA Quadro T2000 Mobile / Max-Q
Memory: 8385MiB / 63983MiB

Which version of k3d
k3d version
k3d version v4.4.3
k3s version v1.20.6-k3s1 (default)

Which version of docker
docker version
Client: Docker Engine - Community
 Version:           20.10.0-rc2
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        dca98e3
 Built:             Wed Dec  2 22:15:25 2020
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.3
  Git commit:       8728dd246c
  Built:            Mon Apr 12 14:10:25 2021
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.5.0
  GitCommit:        8c906ff108ac28da23f69cc7b74f8e7a470d1df0.m
 runc:
  Version:          1.0.0-rc94
  GitCommit:        2c7861bc5e1b3e756392236553ec14a78a09f8bf
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.5.1)
  compose: Docker Compose (Docker Inc., 2.0.0-beta.1)

Server:
 Containers: 8
  Running: 2
  Paused: 0
  Stopped: 6
 Images: 34
 Server Version: 20.10.6
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runsc runu io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8c906ff108ac28da23f69cc7b74f8e7a470d1df0.m
 runc version: 2c7861bc5e1b3e756392236553ec14a78a09f8bf
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.12.3-zen1-1-zen
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 62.48GiB
 Name: archpango
 ID: VRVW:GWHR:MEGI:BZLM:CPYT:RLPQ:OGWK:Q5KP:UM4E:4ERY:CSDK:K5YQ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: true
 Default Address Pools:
   Base: <IP_ADDRESS>/16, Size: 24

Same error on kernel 5.12.4

Hi @kpango , thanks for opening this issue and especially for doing some investigation already :+1:
Similar issue was already mentioned before in #604 (closed in favor of this issue).
Let's see what we can do here :+1:

I'm currently setting up a test system, but I guess that given the workaround mentioned in the kind issue, this could work here: k3d cluster create --k3s-server-arg "--kube-proxy-arg conntrack-max-per-core=0" --k3s-agent-arg "--kube-proxy-arg conntrack-max-per-core=0" (https://rancher.com/docs/k3s/latest/en/installation/install-options/agent-config/ & https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ & https://github.com/kubernetes-sigs/kind/pull/2241)

Just finished my test setup:

Command: k3d cluster create --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0" --image rancher/k3s:v1.20.6-k3s (before: export K3D_FIX_CGROUPV2=true as the system is on cgroupv2)
OS: openSUSE Tumbleweed
Kernel: 5.12.3-1-default
Docker: 20.10.6-ce
k3d: v4.4.3
k3s: v1.20.6-k3s

This works just fine :+1:

Hi, I just faced this issue and the solution proposed by @iwilltry42 is working perfectly!

OS: Arch Linux
Kernel: 5.12.4
Docker: 20.10.6
k3d: v4.4.3
k3s: v1.20.6-k3s1

@iwilltry42 thanks for the workaround, it works well on Arch.

OS: Arch Linux
Kernel: 5.12.4
Docker: 20.10.6
k3d: v4.4.3
k3s: v1.20.6-k3s1

@iwilltry42 actually it works,
command:
k3d cluster create --servers 1 --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0"

However, if we use an agent, it will not work. (--agent 1)
k3d cluster create --servers 1 --agents 1 --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0"

Also, if we use 2 servers, it will not work. (--servers 2)
k3d cluster create --servers 2 --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0"

OS: Arch Linux
Kernel: 5.12.4
Docker: 20.10.6
k3d: v4.4.3
k3s: v1.20.6-k3s1 (default)

Closing this, as it will be fixed upstream (in k3s), thanks to @brandond :pray:

Just finished my test setup:

Command: k3d cluster create --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0" --image rancher/k3s:v1.20.6-k3s (before: export K3D_FIX_CGROUPV2=true as the system is on cgroupv2)
OS: openSUSE Tumbleweed
Kernel: 5.12.3-1-default
Docker: 20.10.6-ce
k3d: v4.4.3
k3s: v1.20.6-k3s

This works just fine
@nemonik can you try this please?

So, I finally got to the point where I could try to press forward with this... Creating a cluster straight away with k3d on Arch running  5.12.10-arch1-1 still doesn't work using k3d installed out of AUR.  I did as you asked modifying for the latest k3s docker image or by just stripping out the image param like so
k3d cluster create ${k3d_cluster_name}  --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" \
    --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0" --image rancher/k3s:v1.21.1-k3s1 \
    --api-port <IP_ADDRESS>:6443 -p 80:80@loadbalancer -p 443:443@loadbalancer \
    -p 2022:2022@loadbalancer --k3s-server-arg "--no-deploy=traefik" --registry-use ${registry_name}:${registry_port} \
    --servers ${k3d_server_count} --agents ${k3d_agent_count}

or
k3d cluster create ${k3d_cluster_name}  --k3s-server-arg "--kube-proxy-arg=conntrack-max-per-core=0" \
    --k3s-agent-arg "--kube-proxy-arg=conntrack-max-per-core=0" \
    --api-port <IP_ADDRESS>:6443 -p 80:80@loadbalancer -p 443:443@loadbalancer \
    -p 2022:2022@loadbalancer --k3s-server-arg "--no-deploy=traefik" --registry-use ${registry_name}:${registry_port} \
    --servers ${k3d_server_count} --agents ${k3d_agent_count}

@iwilltry42  Thank you for the fix.  Sorry it took so long to try it.
And I got it working as you advised...  But is this the advised way now (as per the faq) or has this been replaced over the past 20 some days?

Thanks for the reply @nemonik :+1:

Creating a cluster straight away with k3d on Arch running 5.12.10-arch1-1 still doesn't work using k3d installed out of AUR.

k3d v4.4.4 uses k3s v1.20.6 by default (that's hardcoded at build time), so that won't work.

So, I did as you asked modifying for the latest k3s docker image or by just stripping out the image param like so ...

When setting the --image flag with one of the newer k3s versions (that include the fix referenced from k3s earlier in this thread), you don't need the kube-proxy-arg flags anymore :+1:
Also, v4.4.5 is just being released (there were issues with the release system delaying it), which will be using one of the newer versions by default (so no image or kube-proxy flags required).

When setting the --image flag with one of the newer k3s versions (that include the fix referenced from k3s earlier in this thread), you don't need the kube-proxy-arg

Do you still need the conntrack-max-per-core=0 args to be passed to the server and agent or do they go too?
I will watch for k3d v4.4.5 to drop in AUR
Thanks for the reply.

Do you still need the conntrack-max-per-core=0 args to be passed to the server and agent or do they go too?

Not with the new versions of k3s (v1.21.1-k3s1 is the new default in k3d v4.4.5 and includes the fix).
I'll update the FAQ accordingly.

Danke schön @iwilltry42

k3d v4.4.5 hit AUR last night...

Note that I experienced the same issue with lower versions of the Linux Kernel, :
My Stack versions
$ ./versions.sh
Client: Docker Engine - Community
 Version:           20.10.8
 API version:       1.41
 Go version:        go1.16.6
 Git commit:        3967b7d
 Built:             Fri Jul 30 19:54:22 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.8
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.6
  Git commit:       75249d8
  Built:            Fri Jul 30 19:52:31 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.9
  GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
 runc:
  Version:          1.0.1
  GitCommit:        v1.0.1-0-g4144b63
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
k3d version v4.4.1
k3s version v1.20.5-k3s1 (default)
go version go1.17 linux/amd64
hugo v0.83.1+extended linux/amd64 BuildDate=unknown
flux version 0.17.0

The error message that I get for all k3s server nodes
k3s server open /proc/sys/net/netfilter/nf_conntrack_max: permission denied

And I found :

an entry in the issues : https://github.com/rancher/k3d/issues/607

and the FAQ referencing my exact issue, caused by a GNU/Linux Kernel change (the kernel version used by my debian 11 bullseye is 5.10.0-8-amd64), see https://k3d.io/faq/faq/#solved-nodes-fail-to-start-or-get-stuck-in-notready-state-with-log-nf_conntrack_max-permission-denied

what is funny though, is that the k3d documentation states that this issue raises for a kernel version >= 5.12.2 , but my version is 5.10.0-8-amd64 and I still have the exact same issue

Check kernel version :

jbl@fluxcd:~$ uname -r
5.10.0-8-amd64
jbl@fluxcd:~$ cat /proc/version
Linux version 5.10.0-8-amd64<EMAIL_ADDRESS>(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-4 (2021-08-03)

Yes, some Linux distributions backported the fix into earlier kernel versions. It was only present in mainline linux 5.12.2 and 5.11.19. You'd have to check with the Debian folks to see which releases they backported it to. Either way, there's a fix available. Just use newer K3s.

@brandond Oh, thanks very much for the information :)

I confirm that upgrading to k3d 4.4.5 solved the issue for me, thanks all :)


Check that vim.treesitter is not nil

When opening nvim with no file argument. I.e.
$ nvim

I receive the error
(UNKNOWN PLUGIN): Error executing lua: attempt to call a nil value
                                                                  stack traceback:

This is a corrupted line of output and i don't know how to get the actual stack trace.
However, i tracked down the bug to commit 504e897, and Line 192 of the enabled function in spellsitter.lua
if not vim.treesitter.highlighter.active[bufnr] then

It looks like vim.treesitter is nil if there is not a file open (though it could also be that displaying the open file just hides the error above). Here is a patch that fixes it, but i'm not sure if it's the "right" solution. Perhaps oddly, returning false if vim.treesitter is nil results in the same error.
Version info:
$ nvim -v
NVIM v0.6.0
Build type: Release
LuaJIT 2.0.5
Compiled by builduser

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Spellsitter: 2cb4700
nvim-treesitter: 288ef60edde1b5a49c325b0770bdf999ae648a92

I pushed another version. This one creates a highlighter variable at the start of the file (just like the get_parser variable) and then uses that instead of vim.treesitter.highlighter in the enabled function. I don't know why this would work (or if it's good usage), but it seems to.

I bet the highlighter variable calls the __index metamethod of vim.treesitter to actually create the entry of highlighter.
This explains why the nil checks were failing because nothing was calling the metamethod.

Thanks!


ZEPPELIN-74 Update document for changing interpreter selection from %[name] to %[group].[name]

Update document for changing interpreter selection from %[name] to %[group].[name], which is addressed in #96

Merging it if there're no more discussions

looks good


Problem with null values

Hello,
I need to create an object with a null value and I am having this error when I try to use the following statement:
fixture.customise().propertyOf(MyClass.class, "value", null);

The error is:
java.lang.NullPointerException
at com.flextrade.jfixture.customisation.OverridePropertyBuilder.create(OverridePropertyBuilder.java:44)
at com.flextrade.jfixture.builders.CompositeBuilder.create(CompositeBuilder.java:26)
at com.flextrade.jfixture.behaviours.autoproperty.AutoPropertyBuilder.create(AutoPropertyBuilder.java:22)
at com.flextrade.jfixture.behaviours.recursion.RecursionGuard.create(RecursionGuard.java:33)
at com.flextrade.jfixture.behaviours.noresolution.NoResolutionGuard.create(NoResolutionGuard.java:27)
at com.flextrade.jfixture.behaviours.specimentype.SpecimenTypeInjector.create(SpecimenTypeInjector.java:26)
at com.flextrade.jfixture.SpecimenBuilderContext.resolve(SpecimenBuilderContext.java:13)

Looks like the type condition is not prepared to check a null against a setter. Looks to be an easy localized fix. @richkeenan would you accept a PR?

I could merge a PR but I can't do releases as I've not worked for the parent company for many years (I don't have the keys). Tagging @philipwhiuk who'd be a better contact

Hi @philipwhiuk, do you know if this project is alive? It would be a great idea if the community can evolve the library.

Hi @TWiStErRob,
how would you fix it?
I want to learn


Extend test coverage

From @benjaminwood on April 10, 2018 17:30
Test coverage is very low and should be extended.
Simplecov report on rspec suite:

All Files (62.88%)
Controllers (46.26%)
Models (77.6%)
Mailers (100.0%)
Helpers (68.0%)
Libraries (75.64%)
Ungrouped (75.74%)

Simplecov report on cucumber suite (via firefox):

All Files (46.32%)
Controllers (27.71%)
Models (64.21%)
Mailers (100.0%)
Helpers (55.97%)
Libraries (61.61%)
Ungrouped (55.14%)

Copied from original issue: hintmedia/rigse#10

We spiked on this for a week and extended coverage by ~6%. Closing this for now.


Bug: Ability to see in the darkness after welding without protection

Description
You can see around your character in the darkness after using welding tool without eye protection
Reproduction

Go into the darkness with welding tool in your hand
Use welding tool

you only have 1 tile radius vision so not really that important
the light from the welder alone will let you see that


Bump python version in client

Read this before submitting the PR

Always create a Draft PR first
Go through sections 1-5 below, fill them in and check all the boxes
Make sure that the branch is updated; if there's an "Update branch" button at the bottom of the PR, rebase or update branch.
When all boxes are checked, information is filled in, and the branch is updated: mark as Ready For Review and tag reviewers (top right)
Once there is a submitted review, implement the suggestions (if reasonable, otherwise discuss) and request an new review.

If there is a field which you are unsure about, enter the edit mode of this description or go to the PR template; There are invisible comments providing descriptions which may be of help.
1. Description / Summary
To have web and client syncrhoniezed:
This libraries needs to be bumped as well to have support:
https://github.com/corenting/immutabledict/blob/master/CHANGELOG.md
https://github.com/jazzband/prettytable/releases
https://github.com/prompt-toolkit/python-prompt-toolkit/blob/master/CHANGELOG
https://github.com/yaml/pyyaml/releases
https://github.com/psf/requests/blob/main/HISTORY.md#2320-2024-05-20
https://github.com/Textualize/rich/blob/master/CHANGELOG.md#1360---2023-09-30
Also need to update the documentation due to end of life for python 3.7
https://devguide.python.org/versions/
2. Jira task / GitHub issue
Link to the github issue or add the Jira task ID here.
3. Type of change
What type of change(s) does the PR contain?
Check the relevant boxes below. For an explanation of the different sections, enter edit mode of this PR description template.

[ ] New feature

[ ] Breaking: Why / How? Add info here.
[ ] Non-breaking

[ ] Bug fix
[X] Security Alert fix

[X] Package update

[X] Major version update

[ ] Documentation <!-- Should be checked if the PR adds or updates the CLI documentation -- anything in docs/ directory. -->
[ ] Workflow
[ ] Tests only

4. Additional information

[ ] Sprintlog
[ ] Blocking PRs

[ ] Merged

[ ] PR to master branch: If checked, read the release instructions

[ ] I have followed steps 1-8.

5. Actions / Scans
Check the boxes when the specified checks have passed.
For information on what the different checks do and how to fix it if they're failing, enter edit mode of this description or go to the PR template.

[x] Black

[x] Pylint

[x] Prettier

[x] Yamllint

[x] Tests

[x] TestPyPI

[x] CodeQL

[x] Trivy

[x] Snyk

Is there a way to test this locally?

@valyo I think if you invoke the docker-compose with this branch checked out, it should install this version of the libraries. Because it tries to bind a volume.
In my case I have a structure like this and it works
hemes/
hermes/dds_web
hermes/dds_cli
When calling the docker-compose in dds_web, it still binds to the repository in dds_cli. So I can have that branch checked out and install those version of the dependencies.
It wouldn't work for the python version if that wasn't in the other PR. Because the Dockerfiles are only located in dds_web

@rv0lt : when the local environment is started with docker-compose, then the container is build based on python:3.12-alpine and the cli repo is checked out in the container itself, but it is the default branch, dev, that is checked out. This means that none of the changes in this PR have effect, or?!
I think pip install --upgrade -r requirements.txt after checking this PR's branch should give us a binary based on these changes.

@valyo Yes! But the docker-compose actually re-install the libraries because it runs again sh -c "pip install --upgrade -e . && tail -f /dev/null"
The issue is that the docker-compose is located in the dds_web repository. That is why I mention that it needs to have this specific structure in order for it to bind with the other branch of dds_cli.
When I do it like that, then pip show package | grep Version shows the updated version in the client container.
Tomorrow I can go to the office to talk about this. It can be confusing by messages here

@rv0lt : when the local environment is started with docker-compose, then the container is build based on python:3.12-alpine and the cli repo is checked out in the container itself, but it is the default branch, dev, that is checked out. This means that none of the changes in this PR have effect, or?!
I think pip install --upgrade -r requirements.txt after checking this PR's branch should give us a binary based on these changes.

you are right, @rv0lt
I knew that the dds_cli repo is mounted in the container but I completely ignored the fact that sh -c "pip install --upgrade -e . && tail -f /dev/null" gets run.
I'll check some common commands and I can approve this.

@rv0lt Update the branch as well before you do the tests mentioned in my review

Tested it and also works
@i-oden


int64 format not specified in some (at least one?) location

https://github.com/openzipkin/zipkin-api/blob/master/zipkin2-api.yaml line 319 has type: integer, but format: int64 is not specified. due to this, my client generator (nswag) made the Annotation.timestamp property an int32 which of course blows up. Is this yml file the source of truth or is something generating it? If the yml file can just be edited i can go through it and see if there is this problem anywhere else and make a PR.
Thanks.

The YAML file is maintained by hand. A contribution would be very welcome, thanks

+1
José Carlos Chávez
ons. 24. feb. 2021 kl. 00:44 skrev Brian Devins-Suresh <
<EMAIL_ADDRESS>
The YAML file is maintained by hand. A contribution would be very welcome,
thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin-api/issues/93#issuecomment-784611571,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATJGXZDASFR7NPENX3TAQ4WFANCNFSM4YDMG75A
.

I'm looking through it now as well as the output from my client generator :)

This is solved by this PR https://github.com/openzipkin/zipkin-api/pull/94 which makes the swagger file work well with nswag. I think write operations were already OK.

You know what.. I don't see how writes would work if someone generated a client using this before the modification. Here is what the current master 7692ca7 looks like on my screen:

Maybe I'm agonizing over this too much but I do worry about breaking other people's stuff.
Here is my client after the fix from the PR.

That looks really good. I'm using NSwag v<IP_ADDRESS>

The opentelemetry-dotnet people appear to have wrote their own class (rather than generate one from the swagger file) which makes use of long data type, similar to my result after adding the format to this YAML file. This must be why I did not encounter any problems sending telemetry to zipkin but only querying from it when I raised the issue. I am using their package for sending telemetry.


patch: add new ESR devices

Add new ESR devices
Change-type: patch
Signed-off-by: Aaron Shaw<EMAIL_ADDRESS>

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@balena-ci retest

@balena-ci rebase

@balena-ci rebase

Looks good to me @shawaj, can you rebase and I'll approve?

@shawaj can you please rebase the PR and we can get these added?

Sorry missed this. One sec

All done @klutchell @vipulgupta2048

Thanks again for your contributions @shawaj !


[HWKALERTS-222] add cassalog verification checks

When we are good with this PR I will open another one for the 1.5 branch assuming we want the changes there as well.

LGTM


Wuxiaworld.site note working?[Solved]/Other miscellaneous issues

Hey!
I'm a user of your novel grabber and it's REALLY made my day, especially when my internet cuts out. I just wanted to mention that wuxiaworld.site links don't seem to work, it just says "HTTP error fetching URL" anytime I try to use a wuxiaworld.site link.
Thanks

Seems like they're using Cloudflare during heavy traffic as well. Same problem as #65. Can't really do anything until I find a workaround.

understood, also I have another problem.. I was downloading a novel from scribblhub and the recent chapters weren't fully 'acquired' per say. Simply put theres a lot of text missing, is it because it's in italics? I tried using remove styling as well but it didn't change anything, parts of the chapter(s) were still missing, for the record the novel I'm referring to is this one:
https://www.scribblehub.com/series/10957/the-simulacrum/
the most recent few chapters(63 part 1,2 and 3) are missing some of the dialogue, presumably because it was in a different format or something(Idk I'm a noob here) would appreciate a solution here.
Also for the record, here is an image comparison from chapter 62 part 1,
Epub:

From ScribblHub:

Thanks.

"Remove styling" only removes the style attribute from HTML elements so it won't help in this case since the symbols to annotate the dialog (< and >) are the problem. The HTML cleaner sees them as broken HTML elements and deletes them. I will try to think of a solution or work around.
Can you elaborate on your scrolling problem a bit more? The Calibre E-Book Viewer works like it's supposed to for me, maybe I misunderstood you through:

I see, I hope you can come up with a workaround for the annotated text. Regarding the scroll, in the previous version of Novel grabber(prior to version 3) the epub files were segregated into pages and could be flipped through using right and left(arrow keys) now it has somehow made the entire chapter as a page, so I can't flip through it like a book, but have to scroll down kind of like how you read webnovels on Qidian(webnovel.com) that infinite scroll type format. After checking this appears to be a Calibre problem but it was perfectly fine before I used version 3 to make an epub file, thus I'm a little confused and if there is a setting in Calibre that would allow me to use my arrow keys to flip pages I would appreciate some help.

Closed in favour of #73


Improve docs on threshold configuration and the implications

Improve documentation on the different change detection algotrithms, how they are configured and how they work

e.g. https://github.com/Hyperfoil/Horreum/issues/633


switch from jest to vitest

This PR switches our test setup from jest to vitest.
How it's configured
vitest.workspace.json defines our workspaces as ["packages/*"]. vitest looks for a vitest.config file in each workspace and uses it to run that workspace's tests. This allows each workspace to define the plugins (like vite-plugin-solid for @xstate/solid) and test configuration used to run that workspace's tests.
This allows us to run tests for specific workspaces using vitest --project <package name> (vitest --project @xstate/react).
Major changes

removed all jest dependencies (11❗), configs, scripts, etc.
replaced jsdom with happy-dom
replaced deprecated done callbacks with new Promise callbacks + resolve
added vite plugins to some packages for out-of-the-box support in tests
removed @xstate-repo/jest-utils package

replaced toMatchMockCallsInlineSnapshot with toMatchInlineSnapshot (vitest doesn't support wrapping snapshot functions the way we could with jest-snapshot)
replaced spyOnConsole with inline console spies for the tests that require it
replaced sleep with setTimeout from node:timers/promises

removed redundant patches

I'd like to block this on updating the VS Code launch.json script. It's essential to my workflow.
Extra questions:

Does Vitest have an interactive watch mode in which I could filter tests using filenames or/and test names?
If yes, does it have something akin to jest-watch-typehead?

Yes; here is an example in @statelyai/agent:

Does anyone know anything about svelte-check? I have no idea how to get it to pick up the types: ["vitest/globals"] in tsconfig.json. Couldn't really find anything on its repo either.

I'd like to block this on updating the VS Code launch.json script. It's essential to my workflow.

I've got you buddy 🤗

I'd like to block this on updating the VS Code launch.json script. It's essential to my workflow.

@Andarist Wanna test it locally and make sure it's working the way you expect?

I noticed it's fairly easy to lose those typeahead filters in watch mode (for example pressing Enter clears them). It's annoying but not a big deal.
When debugging with VS Code, I can't disable source mapped stepping - it still shows me a location in the source file (albeit a different/broken one). This is way more annoying, probably something I can live with but well. I just wish that console evaluation could use original references, is this too much to ask for? 😭 😭 😭 (to clarify, this is just something that current debuggers suck at cause they are not utilizing sourcemapped info to its full extent)

I noticed it's fairly easy to lose those typeahead filters in watch mode (for example pressing Enter clears them). It's annoying but not a big deal.

Yeah for some reason they chose to use r for re-running filtered tests. Quite an annoying change if you're a long-time jest user 🥲

Just wanted to plug Wallaby for running tests in "watch" mode (or even as you type).  I've been a user for years and I haven't found anything better.