Gem::Ext::BuildError: ERROR: Failed to build gem native extension. (use of undeclared identifier 'EV_UDATA_SPECIFIC')

Hello, I'm trying to build io-event (1.0.9) for a Solidus project (https://github.com/solidusio/solidus/discussions/4583) but I get this output
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /usr/local/lib/ruby/gems/3.1/gems/io-event-1.0.9/ext
/usr/local/bin/ruby31 -I /usr/local/lib/ruby/site_ruby/3.1 -r
./siteconf20220907-35220-ny28ez.rb extconf.rb
checking for rb_ext_ractor_safe()... yes
checking for &rb_fiber_transfer()... yes
checking for -luring... no
checking for sys/epoll.h... no
checking for sys/event.h... yes
checking for sys/eventfd.h... no
checking for rb_io_descriptor()... yes
checking for &rb_process_status_wait()... no
checking for rb_fiber_current()... yes
checking for &rb_fiber_raise()... yes
checking for ruby/io/buffer.h... yes
creating extconf.h
creating Makefile

current directory: /usr/local/lib/ruby/gems/3.1/gems/io-event-1.0.9/ext
make DESTDIR\= clean

current directory: /usr/local/lib/ruby/gems/3.1/gems/io-event-1.0.9/ext
make DESTDIR\=
compiling ./io/event/event.c
compiling ./io/event/selector/selector.c
compiling ./io/event/selector/kqueue.c
./io/event/selector/kqueue.c:193:50: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
        event.flags = EV_ADD | EV_ENABLE | EV_ONESHOT | EV_UDATA_SPECIFIC;
                                                        ^
./io/event/selector/kqueue.c:217:28: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
        event.flags = EV_DELETE | EV_UDATA_SPECIFIC;
                                  ^
./io/event/selector/kqueue.c:276:60: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
                kevents[count].flags = EV_ADD | EV_ENABLE | EV_ONESHOT | EV_UDATA_SPECIFIC;
                                                                         ^
./io/event/selector/kqueue.c:291:60: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
                kevents[count].flags = EV_ADD | EV_ENABLE | EV_ONESHOT | EV_UDATA_SPECIFIC;
                                                                         ^
./io/event/selector/kqueue.c:313:38: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
                kevents[count].flags = EV_DELETE | EV_UDATA_SPECIFIC;
                                                   ^
./io/event/selector/kqueue.c:321:38: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
                kevents[count].flags = EV_DELETE | EV_UDATA_SPECIFIC;
                                                   ^
./io/event/selector/kqueue.c:697:20: error: use of undeclared identifier 'EVFILT_USER'
                trigger.filter = EVFILT_USER;
                                 ^
./io/event/selector/kqueue.c:698:39: error: use of undeclared identifier 'EV_UDATA_SPECIFIC'
                trigger.flags = EV_ADD | EV_CLEAR | EV_UDATA_SPECIFIC;
                                                    ^
./io/event/selector/kqueue.c:699:20: error: use of undeclared identifier 'NOTE_TRIGGER'
                trigger.fflags = NOTE_TRIGGER;
                                 ^
9 errors generated.
*** Error 1 in /usr/local/lib/ruby/gems/3.1/gems/io-event-1.0.9/ext (Makefile:246 'kqueue.o':
@ cc -I. -I/usr/local/include/ruby-3.1/x86_64-...)

make failed, exit code 2

Gem files will remain installed in /usr/local/lib/ruby/gems/3.1/gems/io-event-1.0.9 for
inspection.
Results logged to
/usr/local/lib/ruby/gems/3.1/extensions/x86_64-openbsd/3.1/io-event-1.0.9/gem_make.out

My OS is OpenBSD 7.1 x64 and my ruby version is 3.1.2

Does your kqueue implementation support EV_UDATA_SPECIFIC?
If not, is there an alternative?

So, this appears to be an issue with OpenBSD not fully supporting the required kqueue features.
@jeremyevans do you have any thoughts or suggestions?
We could disable the kqueue if this header define is not found. You'd end up falling back to Ruby's select backend which is not ideal but at least should work.

@joyboy67 can you please test the above fix (#49) and confirm that kqueue is skipped on your system.


Road shield funk, missing artwork

TANGRAM VERSION:
v0.15.2 and 0.14.x
ENVIRONMENT:
Mac Chrome Version 68.0.3440.106 (Official Build) (64-bit)
TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:

Viewing Bubble Wrap in in Canada at 11/49.8643/-97.1439
This branch: https://github.com/tangrams/bubble-wrap/tree/sensescape/shields-polish
Checkout the branch locally and preview.

RESULT:
Some shield artwork fails to draw (but the text draws fine)
EXPECTED RESULT:
The shield artwork and the text should both draw in v0.15.x. It does in Tangram 0.14.x!
v0.15.x

v0.14.x

For comparision:

master Bubble Wrap at same location: http://tangrams.github.io/bubble-wrap/#12/49.9062/-97.1199

Seems to affect both legit shields (like CA:transcanada) and "generic" fallback shields.

Should be fixed by 417e4b9cdcfa26b2d5b4a87da1866136d8233c92
Problem was caused by more than one texture being used for rendering by the same style (multiple sprite sheets for shields in this case).

This is fix is live in 0.15.3 and I've confirmed it's working for me. Thank you!


compare typesupport identifier symbols instead of strings

Connects to ros2/ros2#30.

Finally ready for review. Windows slave was able to build this: http://<IP_ADDRESS>:8080/view/ros2/job/ros2_batch_ci_test_windows/15/

+1

+1

+1


Don't terminate indexing after an indexing failure

Description
If there is an error indexing any items, continue the indexing operation instead of terminating it.
Also, when logging the indexing error, log the the problematic entry's id to help track it down.
Background
One entry is failing to index on dev because its workflowname property length is > 75K. Elasticsearch, Lucene really, has a 32K limit on a term, see here (look at the bottom of the page). This particular workflowname is so long for PEN testing purposes.
This is the simple fix. A more complex fix could be some combination of these -- push back if you think it's worth it (I don't, but can be convinced):

Enforce a max length on workflowname and other properties that end up being indexed.
Truncate strings greater than 32K before indexing them.
The index API response should be the number of items that were actually indexed, not the number attempted to index.
Variant of above, instead of only returning a number with items indexed, return a JSON object, with fields for number of items indexed, number of items not indexed, maybe something else as well, etc.
The index API response should be a 5xx not a 2xx.
Create a CloudWatch alarm for when we fail to index an entry

Issue
SEAB-4596
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future

Enforce a max length on workflowname and other properties that end up being indexed.

Truncate strings greater than 32K before indexing them.

I think we should tackle one of these before the database at all though it can be a follow-up ticket,

One entry is failing to index on dev because its workflowname property length is > 75K. Elasticsearch, Lucene really, has a 32K limit on a term,

To clarify, because I had it wrong in my head even though the word "term" was in my description, the limit is a term limit, nor a property/field limit. I was concerned that READMEs > 32K would prevent an entry from indexing, but verified they work. In the case of the this bug, the workflowname is one big term, which is why it fails.

I think we should tackle one of these before the database at all though it can be a follow-up ticket. Wouldn't this show up in browse view, take up space in the DB, and just generally be annoying anyway?

Yes, there's another one in there with 18K workflowname, which works from an ES perspective, but clicking on it in search sends you to the home page, because, I would guess, the url is too long for the browser.

I think we should tackle one of these before the database at all though it can be a follow-up ticket. Wouldn't this show up in browse view, take up space in the DB, and just generally be annoying anyway?

It turns out there is already code that ensures the workflowname and toolname doesn't go over 256. It's was done in PR #4545. It's a bigger limit than what I was going to do, but that PR was approved, so leaving it.
I did add a database constraint in case there are any code paths that bypass that check. Also added a @Size annotation to the entities, for the same reason, although see #5030 -- those don't seem do anything today.
The migration also truncates existing names > 256 (no existing "real" workflows go over 60 characters).

(on build success)


.clang-tidy file can not implement

Describe the bug
.clang-tidy file can not implement
CodeChecker version
compile with newest code on branch master (6.17)
.clang-tidy file can not implement
I have added a .clang-tidy file to make my own config for clang-tidy, but it didn't work, did I lose some steps about clang-tidy settings or any other thing?

If I delete a space in .clang-tidy on purpose,  codechecker can recognize the syntax error:

So I am so confused that did .clang-tidy file implemented or not?

If I delete a space in .clang-tidy on purpose, codechecker can recognize the syntax error:

So I am so confused that did .clang-tidy file implemented or not?

I think your problem is related to my PR: #3203

@csordasmarton Thanks too much, I saw it , it's the same problem. By the way, does it will be fixed in next version ?

@basakerhz I hope so that it will be merged in the next release. It's still under review. I will try to ping my colleague to review it.

@csordasmarton Glad to hear that, thank you for your efforts🤗.

@csordasmarton Hi, I want to only enable the rules about performance-*, so I disabled sensitive, and --enbale performance rule one by one , it seems worked, but the truth is our code was still checked by default rules , is that also a known issue?

actually:

Under the hood in case of Clang Tidy first it will enable all the checkers in the default profile first:
https://github.com/Ericsson/codechecker/blob/ed16b5d58f75002b465ea0944be0abf071f0b958/analyzer/codechecker_analyzer/analyzers/config_handler.py#L170-L172
After it will iterate over all the checkers enabled or disabled by the command line parameters:
https://github.com/Ericsson/codechecker/blob/ed16b5d58f75002b465ea0944be0abf071f0b958/analyzer/codechecker_analyzer/analyzers/config_handler.py#L201-L220
The list of checkers which are in the sensitive profile can be found in this file: https://github.com/Ericsson/codechecker/blob/master/config/labels/analyzers/clang-tidy.json
And can be listed with the following command: CodeChecker checkers --analyzers clang-tidy --profile sensitive


How to run a development server in a Docker container

Useful to speed up new developer on boarding/setup/cleanup. Also helps avoid dependency conflicts between projects

Thanks for the effort, but we've decided to temporarily put a hold on non-critical changes to ensure a smooth migration to v3 docs :).


Unable to start k3s service in the master node

Hi,
After a power outage, I've realize, my master nodes can't boot up properly, please, could you help me??
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.292576    3494 server.go:659] external host was not specified, using <IP_ADDRESS>
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.296031    3494 server.go:196] Version: v1.20.4+k3s1
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.399832    3494 shared_informer.go:240] Waiting for caches to sync for node_authorizer
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.422451    3494 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.
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.422797    3494 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.438570    3494 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.
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.438781    3494 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
Oct 11 15:44:19 localhost k3s[3494]: I1011 15:44:19.739131    3494 instance.go:289] Using reconciler: lease
Oct 11 15:44:20 localhost k3s[3494]: I1011 15:44:20.047468    3494 rest.go:131] the default service ipfamily for this cluster is: IPv4
Oct 11 15:44:21 localhost k3s[3494]: I1011 15:44:21.093158    3494 trace.go:205] Trace[1098700547]: "List etcd3" key:/secrets,resourceVersion:,resourceVersionMatch:,limit:10000,continue: (11-Oct-2021 15:44:19.930) (total time: 1162ms):
Oct 11 15:44:21 localhost k3s[3494]: Trace[1098700547]: [1.162803764s] [1.162803764s] END
Oct 11 15:44:21 localhost k3s[3494]: time="2021-10-11T15:44:21.211867275+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:21 http: TLS handshake error from <IP_ADDRESS>:40382: remote error: tls: bad certificate"
Oct 11 15:44:21 localhost k3s[3494]: time="2021-10-11T15:44:21.291388240+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:21 http: TLS handshake error from <IP_ADDRESS>:32898: remote error: tls: bad certificate"
Oct 11 15:44:21 localhost k3s[3494]: I1011 15:44:21.833274    3494 trace.go:205] Trace[907858497]: "List etcd3" key:/apiextensions.k8s.io/customresourcedefinitions,resourceVersion:,resourceVersionMatch:,limit:10000,continue: (11-Oct-2021 15:44:19.477) (total time: 2355ms):
Oct 11 15:44:21 localhost k3s[3494]: Trace[907858497]: [2.355249555s] [2.355249555s] END
Oct 11 15:44:22 localhost k3s[3494]: I1011 15:44:22.348477    3494 trace.go:205] Trace[1364057824]: "List etcd3" key:/apiextensions.k8s.io/customresourcedefinitions,resourceVersion:,resourceVersionMatch:,limit:10000,continue: (11-Oct-2021 15:44:19.469) (total time: 2878ms):
Oct 11 15:44:22 localhost k3s[3494]: Trace[1364057824]: [2.878577676s] [2.878577676s] END
Oct 11 15:44:22 localhost k3s[3494]: time="2021-10-11T15:44:22.409754393+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:22 http: TLS handshake error from <IP_ADDRESS>:57622: remote error: tls: bad certificate"
Oct 11 15:44:22 localhost k3s[3494]: time="2021-10-11T15:44:22.516127365+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:22 http: TLS handshake error from <IP_ADDRESS>:57702: remote error: tls: bad certificate"
Oct 11 15:44:22 localhost k3s[3494]: time="2021-10-11T15:44:22.572661771+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:22 http: TLS handshake error from <IP_ADDRESS>:53968: remote error: tls: bad certificate"
Oct 11 15:44:23 localhost k3s[3494]: W1011 15:44:23.609847    3494 genericapiserver.go:419] Skipping API batch/v2alpha1 because it has no resources.
Oct 11 15:44:23 localhost k3s[3494]: W1011 15:44:23.751256    3494 genericapiserver.go:419] Skipping API discovery.k8s.io/v1alpha1 because it has no resources.
Oct 11 15:44:23 localhost k3s[3494]: W1011 15:44:23.906221    3494 genericapiserver.go:419] Skipping API node.k8s.io/v1alpha1 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: W1011 15:44:24.021273    3494 genericapiserver.go:419] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: W1011 15:44:24.069812    3494 genericapiserver.go:419] Skipping API scheduling.k8s.io/v1alpha1 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: W1011 15:44:24.150211    3494 genericapiserver.go:419] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: W1011 15:44:24.185404    3494 genericapiserver.go:419] Skipping API flowcontrol.apiserver.k8s.io/v1alpha1 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: W1011 15:44:24.256981    3494 genericapiserver.go:419] Skipping API apps/v1beta2 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: W1011 15:44:24.257151    3494 genericapiserver.go:419] Skipping API apps/v1beta1 because it has no resources.
Oct 11 15:44:24 localhost k3s[3494]: I1011 15:44:24.384797    3494 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.
Oct 11 15:44:24 localhost k3s[3494]: I1011 15:44:24.384989    3494 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.493498252+02:00" level=info msg="Waiting for API server to become available"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.493904193+02:00" level=info msg="Running kube-scheduler --address=<IP_ADDRESS> --bind-address=<IP_ADDRESS> --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --port=10251 --profiling=false --secure-port=0"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.502425570+02:00" 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 --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"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.580013076+02:00" level=info msg="Node token is available at /var/lib/rancher/k3s/server/token"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.580396830+02:00" level=info msg="To join node to cluster: k3s agent -s https://<IP_ADDRESS>:6443 -t ${NODE_TOKEN}"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.593023712+02:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.593392725+02:00" level=info msg="Run: k3s kubectl"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.594513204+02:00" level=info msg="Module overlay was already loaded"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.594706018+02:00" level=info msg="Module nf_conntrack was already loaded"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.594843259+02:00" level=info msg="Module br_netfilter was already loaded"
Oct 11 15:44:24 localhost k3s[3494]: time="2021-10-11T15:44:24.594965447+02:00" level=info msg="Module iptable_nat was already loaded"
Oct 11 15:44:25 localhost k3s[3494]: time="2021-10-11T15:44:25.131056520+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:25 http: TLS handshake error from <IP_ADDRESS>:46744: remote error: tls: bad certificate"
Oct 11 15:44:25 localhost k3s[3494]: time="2021-10-11T15:44:25.319794741+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:25 http: TLS handshake error from <IP_ADDRESS>:46752: remote error: tls: bad certificate"
Oct 11 15:44:25 localhost k3s[3494]: time="2021-10-11T15:44:25.761972793+02:00" level=info msg="certificate CN=noldork3sm2 signed by CN=k3s-server-ca@1611348520: notBefore=2021-01-22 20:48:40 +0000 UTC notAfter=2022-10-11 13:44:25 +0000 UTC"
Oct 11 15:44:25 localhost k3s[3494]: time="2021-10-11T15:44:25.875424624+02:00" level=info msg="certificate CN=system:node:noldork3sm2,O=system:nodes signed by CN=k3s-client-ca@1611348520: notBefore=2021-01-22 20:48:40 +0000 UTC notAfter=2022-10-11 13:44:25 +0000 UTC"
Oct 11 15:44:26 localhost k3s[3494]: time="2021-10-11T15:44:26.120051459+02:00" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
Oct 11 15:44:26 localhost k3s[3494]: time="2021-10-11T15:44:26.122832317+02:00" 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"
Oct 11 15:44:26 localhost k3s[3494]: time="2021-10-11T15:44:26.283677581+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:26 http: TLS handshake error from <IP_ADDRESS>:40390: remote error: tls: bad certificate"
Oct 11 15:44:26 localhost k3s[3494]: time="2021-10-11T15:44:26.422107128+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:26 http: TLS handshake error from <IP_ADDRESS>:32906: remote error: tls: bad certificate"
Oct 11 15:44:26 localhost k3s[3494]: time="2021-10-11T15:44:26.562304764+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:26 localhost k3s[3494]: time="2021-10-11T15:44:26.869943503+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:27 localhost k3s[3494]: time="2021-10-11T15:44:27.147306089+02:00" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: connection refused\""
Oct 11 15:44:27 localhost k3s[3494]: time="2021-10-11T15:44:27.519192677+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:27 http: TLS handshake error from <IP_ADDRESS>:57630: remote error: tls: bad certificate"
Oct 11 15:44:27 localhost k3s[3494]: time="2021-10-11T15:44:27.612221981+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:27 http: TLS handshake error from <IP_ADDRESS>:57710: remote error: tls: bad certificate"
Oct 11 15:44:27 localhost k3s[3494]: time="2021-10-11T15:44:27.682761192+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:27 http: TLS handshake error from <IP_ADDRESS>:53976: remote error: tls: bad certificate"
Oct 11 15:44:27 localhost k3s[3494]: time="2021-10-11T15:44:27.902814419+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:27 localhost k3s[3494]: time="2021-10-11T15:44:27.964965849+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:28 localhost k3s[3494]: time="2021-10-11T15:44:28.087406450+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:28 localhost k3s[3494]: time="2021-10-11T15:44:28.161383137+02:00" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: connection refused\""
Oct 11 15:44:29 localhost k3s[3494]: time="2021-10-11T15:44:29.181541574+02:00" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: connection refused\""
Oct 11 15:44:30 localhost k3s[3494]: time="2021-10-11T15:44:30.191166566+02:00" level=info msg="Containerd is now running"
Oct 11 15:44:30 localhost k3s[3494]: time="2021-10-11T15:44:30.704789001+02:00" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:6443/v1-k3s/connect"
Oct 11 15:44:30 localhost k3s[3494]: time="2021-10-11T15:44:30.863986948+02:00" level=info msg="Handling backend connection request [noldork3sm2]"
Oct 11 15:44:30 localhost k3s[3494]: time="2021-10-11T15:44:30.871063103+02:00" 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=/var/lib/rancher/k3s/data/912de41a65c99bc4d50bbb78e6106f3acbf3a70b8dead77b4c4ebc6755b4f9d6/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=noldork3sm2 --kubeconfig=/var/lib/rancher/k3s/agent/kubelet.kubeconfig --node-labels= --pod-manifest-path=/var/lib/rancher/k3s/agent/pod-manifests --read-only-port=0 --register-with-taints=k3s-controlplane=true:NoSchedule --resolv-conf=/etc/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"
Oct 11 15:44:30 localhost k3s[3494]: time="2021-10-11T15:44:30.877528837+02:00" level=info msg="Running kube-proxy --cluster-cidr=<IP_ADDRESS>/16 --healthz-bind-address=<IP_ADDRESS> --hostname-override=noldork3sm2 --kubeconfig=/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig --proxy-mode=iptables"
Oct 11 15:44:30 localhost k3s[3494]: Flag --cloud-provider has been deprecated, will be removed in 1.23, in favor of removing cloud provider code from Kubelet.
Oct 11 15:44:30 localhost k3s[3494]: 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.
Oct 11 15:44:30 localhost k3s[3494]: W1011 15:44:30.885477    3494 server.go:226] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
Oct 11 15:44:31 localhost systemd[1]: Started Kubernetes systemd probe.
Oct 11 15:44:31 localhost k3s[3494]: I1011 15:44:31.110173    3494 server.go:412] Version: v1.20.4+k3s1
Oct 11 15:44:31 localhost systemd[1]: run-rd3dafb4b84874f43849d3a6be96122d2.scope: Succeeded.
Oct 11 15:44:31 localhost k3s[3494]: time="2021-10-11T15:44:31.397245120+02:00" level=info msg="Node CIDR assigned for: noldork3sm2"
Oct 11 15:44:31 localhost k3s[3494]: I1011 15:44:31.399130    3494 flannel.go:92] Determining IP address of default interface
Oct 11 15:44:31 localhost k3s[3494]: I1011 15:44:31.406546    3494 flannel.go:105] Using interface with name eth0 and address <IP_ADDRESS>
Oct 11 15:44:31 localhost k3s[3494]: I1011 15:44:31.439786    3494 kube.go:117] Waiting 10m0s for node controller to sync
Oct 11 15:44:31 localhost k3s[3494]: I1011 15:44:31.440206    3494 kube.go:300] Starting kube subnet manager
Oct 11 15:44:31 localhost k3s[3494]: time="2021-10-11T15:44:31.542731591+02:00" level=info msg="labels have already set on node: noldork3sm2"
Oct 11 15:44:31 localhost k3s[3494]: time="2021-10-11T15:44:31.622141811+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:31 http: TLS handshake error from <IP_ADDRESS>:40418: remote error: tls: bad certificate"
Oct 11 15:44:31 localhost k3s[3494]: E1011 15:44:31.766657    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Namespace: failed to list *v1.Namespace: namespaces is forbidden: User "system:k3s-controller" cannot list resource "namespaces" in API group "" at the cluster scope
Oct 11 15:44:31 localhost k3s[3494]: E1011 15:44:31.858410    3494 node.go:161] Failed to retrieve node info: nodes "noldork3sm2" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
Oct 11 15:44:31 localhost k3s[3494]: E1011 15:44:31.899419    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.NetworkPolicy: failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:k3s-controller" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
Oct 11 15:44:31 localhost k3s[3494]: time="2021-10-11T15:44:31.945105707+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:31 http: TLS handshake error from <IP_ADDRESS>:32934: remote error: tls: bad certificate"
Oct 11 15:44:31 localhost k3s[3494]: E1011 15:44:31.969123    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:k3s-controller" cannot list resource "pods" in API group "" at the cluster scope
Oct 11 15:44:31 localhost k3s[3494]: time="2021-10-11T15:44:31.994156966+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:32 localhost k3s[3494]: I1011 15:44:32.194272    3494 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/agent/client-ca.crt
Oct 11 15:44:32 localhost k3s[3494]: time="2021-10-11T15:44:32.326172029+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:32 localhost k3s[3494]: I1011 15:44:32.443535    3494 kube.go:124] Node controller sync successful
Oct 11 15:44:32 localhost k3s[3494]: I1011 15:44:32.449585    3494 vxlan.go:121] VXLAN config: VNI=1 Port=0 GBP=false Learning=false DirectRouting=false
Oct 11 15:44:32 localhost k3s[3494]: time="2021-10-11T15:44:32.943749512+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:32 http: TLS handshake error from <IP_ADDRESS>:57738: remote error: tls: bad certificate"
Oct 11 15:44:33 localhost k3s[3494]: E1011 15:44:33.011722    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Namespace: failed to list *v1.Namespace: namespaces is forbidden: User "system:k3s-controller" cannot list resource "namespaces" in API group "" at the cluster scope
Oct 11 15:44:33 localhost k3s[3494]: time="2021-10-11T15:44:33.020476322+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:33 http: TLS handshake error from <IP_ADDRESS>:57658: remote error: tls: bad certificate"
Oct 11 15:44:33 localhost k3s[3494]: E1011 15:44:33.113077    3494 node.go:161] Failed to retrieve node info: nodes "noldork3sm2" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
Oct 11 15:44:33 localhost k3s[3494]: time="2021-10-11T15:44:33.138814897+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:33 http: TLS handshake error from <IP_ADDRESS>:54004: remote error: tls: bad certificate"
Oct 11 15:44:33 localhost k3s[3494]: time="2021-10-11T15:44:33.165318095+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:33 localhost k3s[3494]: E1011 15:44:33.316889    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.NetworkPolicy: failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:k3s-controller" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
Oct 11 15:44:33 localhost k3s[3494]: time="2021-10-11T15:44:33.362522247+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:33 localhost k3s[3494]: E1011 15:44:33.504235    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:k3s-controller" cannot list resource "pods" in API group "" at the cluster scope
Oct 11 15:44:33 localhost k3s[3494]: time="2021-10-11T15:44:33.517797286+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:34 localhost k3s[3494]: time="2021-10-11T15:44:34.612139961+02:00" level=info msg="Waiting for cloudcontroller rbac role to be created"
Oct 11 15:44:35 localhost k3s[3494]: E1011 15:44:35.321816    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:k3s-controller" cannot list resource "pods" in API group "" at the cluster scope
Oct 11 15:44:35 localhost k3s[3494]: E1011 15:44:35.331517    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.NetworkPolicy: failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:k3s-controller" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
Oct 11 15:44:35 localhost k3s[3494]: E1011 15:44:35.383080    3494 node.go:161] Failed to retrieve node info: nodes "noldork3sm2" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
Oct 11 15:44:35 localhost k3s[3494]: E1011 15:44:35.681164    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Namespace: failed to list *v1.Namespace: namespaces is forbidden: User "system:k3s-controller" cannot list resource "namespaces" in API group "" at the cluster scope
Oct 11 15:44:35 localhost k3s[3494]: time="2021-10-11T15:44:35.762841849+02:00" level=warning msg="Unable to watch for tunnel endpoints: unknown (get endpoints)"
Oct 11 15:44:37 localhost k3s[3494]: time="2021-10-11T15:44:37.028444908+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:37 http: TLS handshake error from <IP_ADDRESS>:40442: remote error: tls: bad certificate"
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.212074    3494 nvidia.go:81] Error reading "/sys/bus/pci/devices/": open /sys/bus/pci/devices/: no such file or directory
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.224774    3494 sysinfo.go:203] Nodes topology is not available, providing CPU topology
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.226547    3494 sysfs.go:348] unable to read /sys/devices/system/cpu/cpu0/online: open /sys/devices/system/cpu/cpu0/online: no such file or directory
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.226918    3494 sysfs.go:348] unable to read /sys/devices/system/cpu/cpu1/online: open /sys/devices/system/cpu/cpu1/online: no such file or directory
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.227352    3494 sysfs.go:348] unable to read /sys/devices/system/cpu/cpu2/online: open /sys/devices/system/cpu/cpu2/online: no such file or directory
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.227908    3494 sysfs.go:348] unable to read /sys/devices/system/cpu/cpu3/online: open /sys/devices/system/cpu/cpu3/online: no such file or directory
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.229521    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu0 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.229719    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu1 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.229883    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu2 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.230040    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu3 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: E1011 15:44:37.230103    3494 machine.go:72] Cannot read number of physical cores correctly, number of cores set to 0
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.231754    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu0 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.231935    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu1 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.232094    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu2 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: W1011 15:44:37.232238    3494 machine.go:253] Cannot determine CPU /sys/bus/cpu/devices/cpu3 online state, skipping
Oct 11 15:44:37 localhost k3s[3494]: E1011 15:44:37.232299    3494 machine.go:86] Cannot read number of sockets correctly, number of sockets set to 0
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.235732    3494 server.go:645] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.238433    3494 container_manager_linux.go:287] container manager verified user specified cgroup-root exists: []
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.239216    3494 container_manager_linux.go:292] Creating Container Manager object based on Node Config: {RuntimeCgroupsName: SystemCgroupsName: KubeletCgroupsName: ContainerRuntime:remote CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:cgroupfs KubeletRootDir:/var/lib/kubelet ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: ReservedSystemCPUs: EnforceNodeAllocatable:map[pods:{}] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[{Signal:imagefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>} {Signal:nodefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>}]} QOSReserved:map[] ExperimentalCPUManagerPolicy:none ExperimentalTopologyManagerScope:container ExperimentalCPUManagerReconcilePeriod:10s ExperimentalPodPidsLimit:-1 EnforceCPULimits:true CPUCFSQuotaPeriod:100ms ExperimentalTopologyManagerPolicy:none Rootless:false}
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.239972    3494 topology_manager.go:120] [topologymanager] Creating topology manager with none policy per container scope
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.240099    3494 container_manager_linux.go:323] [topologymanager] Initializing Topology Manager with none policy and container-level scope
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.240173    3494 container_manager_linux.go:328] Creating device plugin manager: true
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.242412    3494 kubelet.go:265] Adding pod path: /var/lib/rancher/k3s/agent/pod-manifests
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.242668    3494 kubelet.go:276] Watching apiserver
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.243392    3494 kubelet.go:453] Kubelet client is not nil
Oct 11 15:44:37 localhost k3s[3494]: time="2021-10-11T15:44:37.243663523+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.251012    3494 kuberuntime_manager.go:216] Container runtime containerd initialized, version: v1.4.3-k3s3, apiVersion: v1alpha2
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.255086    3494 server.go:1177] Started kubelet
Oct 11 15:44:37 localhost k3s[3494]: E1011 15:44:37.287874    3494 cri_stats_provider.go:376] Failed to get the info of the filesystem with mountpoint "/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs": unable to find data in memory cache.
Oct 11 15:44:37 localhost k3s[3494]: E1011 15:44:37.288058    3494 kubelet.go:1292] Image garbage collection failed once. Stats initialization may not have completed yet: invalid capacity 0 on image filesystem
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.289573    3494 server.go:148] Starting to listen on <IP_ADDRESS>:10250
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.307930    3494 server.go:410] Adding debug handlers to kubelet server.
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.333512    3494 fs_resource_analyzer.go:64] Starting FS ResourceAnalyzer
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.375940    3494 volume_manager.go:271] Starting Kubelet Volume Manager
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.401189    3494 desired_state_of_world_populator.go:142] Desired state populator starts to run
Oct 11 15:44:37 localhost k3s[3494]: time="2021-10-11T15:44:37.499390402+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:37 http: TLS handshake error from <IP_ADDRESS>:32958: remote error: tls: bad certificate"
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.547089    3494 kubelet.go:449] kubelet nodes not sync
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.547440    3494 kubelet.go:449] kubelet nodes not sync
Oct 11 15:44:37 localhost k3s[3494]: I1011 15:44:37.712551    3494 kubelet_node_status.go:71] Attempting to register node noldork3sm2
Oct 11 15:44:38 localhost k3s[3494]: time="2021-10-11T15:44:38.376591610+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:38 http: TLS handshake error from <IP_ADDRESS>:57762: remote error: tls: bad certificate"
Oct 11 15:44:38 localhost k3s[3494]: time="2021-10-11T15:44:38.466238574+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:38 localhost k3s[3494]: time="2021-10-11T15:44:38.521111595+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:38 http: TLS handshake error from <IP_ADDRESS>:57682: remote error: tls: bad certificate"
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.570206    3494 kuberuntime_manager.go:1006] updating runtime config through cri with podcidr <IP_ADDRESS>/24
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.594525    3494 kubelet_network.go:77] Setting Pod CIDR:  -> <IP_ADDRESS>/24
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.616714    3494 cpu_manager.go:193] [cpumanager] starting with none policy
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.616859    3494 cpu_manager.go:194] [cpumanager] reconciling every 10s
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.617089    3494 state_mem.go:36] [cpumanager] initializing new in-memory state store
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.625968    3494 state_mem.go:88] [cpumanager] updated default cpuset: ""
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.626139    3494 state_mem.go:96] [cpumanager] updated cpuset assignments: "map[]"
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.626312    3494 policy_none.go:43] [cpumanager] none policy: Start
Oct 11 15:44:38 localhost k3s[3494]: W1011 15:44:38.634372    3494 manager.go:594] Failed to retrieve checkpoint for "kubelet_internal_checkpoint": checkpoint is not found
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.639185    3494 plugin_manager.go:114] Starting Kubelet Plugin Manager
Oct 11 15:44:38 localhost k3s[3494]: time="2021-10-11T15:44:38.685001955+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:38 http: TLS handshake error from <IP_ADDRESS>:54028: remote error: tls: bad certificate"
Oct 11 15:44:38 localhost k3s[3494]: time="2021-10-11T15:44:38.862148835+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.903514    3494 kubelet_network_linux.go:56] Initialized IPv4 iptables rules.
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.903914    3494 status_manager.go:158] Starting to sync pod status with apiserver
Oct 11 15:44:38 localhost k3s[3494]: I1011 15:44:38.904137    3494 kubelet.go:1829] Starting kubelet main sync loop.
Oct 11 15:44:38 localhost k3s[3494]: E1011 15:44:38.904614    3494 kubelet.go:1853] skipping pod synchronization - PLEG is not healthy: pleg has yet to be successful
Oct 11 15:44:39 localhost k3s[3494]: time="2021-10-11T15:44:39.028526715+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:39 localhost k3s[3494]: I1011 15:44:39.128733    3494 reconciler.go:157] Reconciler: start to sync state
Oct 11 15:44:39 localhost k3s[3494]: E1011 15:44:39.140997    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:k3s-controller" cannot list resource "pods" in API group "" at the cluster scope
Oct 11 15:44:39 localhost k3s[3494]: time="2021-10-11T15:44:39.175366145+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:39 localhost k3s[3494]: E1011 15:44:39.461582    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.NetworkPolicy: failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:k3s-controller" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
Oct 11 15:44:39 localhost k3s[3494]: E1011 15:44:39.526817    3494 node.go:161] Failed to retrieve node info: nodes "noldork3sm2" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
Oct 11 15:44:40 localhost k3s[3494]: time="2021-10-11T15:44:40.823311390+02:00" level=warning msg="Unable to watch for tunnel endpoints: unknown (get endpoints)"
Oct 11 15:44:41 localhost k3s[3494]: E1011 15:44:41.640768    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Namespace: failed to list *v1.Namespace: namespaces is forbidden: User "system:k3s-controller" cannot list resource "namespaces" in API group "" at the cluster scope
Oct 11 15:44:42 localhost k3s[3494]: time="2021-10-11T15:44:42.274294551+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:42 http: TLS handshake error from <IP_ADDRESS>:40466: remote error: tls: bad certificate"
Oct 11 15:44:42 localhost k3s[3494]: time="2021-10-11T15:44:42.440869505+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:43 localhost k3s[3494]: time="2021-10-11T15:44:43.514190368+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:43 http: TLS handshake error from <IP_ADDRESS>:32982: remote error: tls: bad certificate"
Oct 11 15:44:43 localhost k3s[3494]: time="2021-10-11T15:44:43.844702540+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:43 localhost k3s[3494]: time="2021-10-11T15:44:43.905892693+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:43 http: TLS handshake error from <IP_ADDRESS>:57786: remote error: tls: bad certificate"
Oct 11 15:44:44 localhost k3s[3494]: time="2021-10-11T15:44:44.092561406+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:44 http: TLS handshake error from <IP_ADDRESS>:57706: remote error: tls: bad certificate"
Oct 11 15:44:44 localhost k3s[3494]: time="2021-10-11T15:44:44.124497041+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:44 localhost k3s[3494]: time="2021-10-11T15:44:44.223655170+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:44 http: TLS handshake error from <IP_ADDRESS>:54052: remote error: tls: bad certificate"
Oct 11 15:44:44 localhost k3s[3494]: time="2021-10-11T15:44:44.446750283+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:44 localhost k3s[3494]: time="2021-10-11T15:44:44.574290005+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:45 localhost k3s[3494]: time="2021-10-11T15:44:45.652838945+02:00" level=info msg="Waiting for cloudcontroller rbac role to be created"
Oct 11 15:44:45 localhost k3s[3494]: time="2021-10-11T15:44:45.888170771+02:00" level=warning msg="Unable to watch for tunnel endpoints: unknown (get endpoints)"
Oct 11 15:44:47 localhost k3s[3494]: E1011 15:44:47.039253    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: pods is forbidden: User "system:k3s-controller" cannot list resource "pods" in API group "" at the cluster scope
Oct 11 15:44:47 localhost k3s[3494]: time="2021-10-11T15:44:47.470846416+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:47 http: TLS handshake error from <IP_ADDRESS>:40490: remote error: tls: bad certificate"
Oct 11 15:44:47 localhost k3s[3494]: time="2021-10-11T15:44:47.666725195+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:48 localhost k3s[3494]: I1011 15:44:48.185482    3494 trace.go:205] Trace[1021595152]: "Create" url:/api/v1/namespaces/default/events,user-agent:k3s/v1.20.4+k3s1 (linux/arm) kubernetes/838a906,client:<IP_ADDRESS> (11-Oct-2021 15:44:38.179) (total time: 10005ms):
Oct 11 15:44:48 localhost k3s[3494]: Trace[1021595152]: [10.005268937s] [10.005268937s] END
Oct 11 15:44:48 localhost k3s[3494]: E1011 15:44:48.192958    3494 node.go:161] Failed to retrieve node info: nodes "noldork3sm2" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
Oct 11 15:44:48 localhost k3s[3494]: E1011 15:44:48.310307    3494 event.go:264] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"noldork3sm2.16acfdd9ed048b6f", GenerateName:"", Namespace:"default", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"Node", Namespace:"", Name:"noldork3sm2", UID:"noldork3sm2", APIVersion:"", ResourceVersion:"", FieldPath:""}, Reason:"Starting", Message:"Starting kubelet.", Source:v1.EventSource{Component:"kubelet", Host:"noldork3sm2"}, FirstTimestamp:v1.Time{Time:time.Time{wall:0xc0512dd14f31196f, ext:20715723711, loc:(*time.Location)(0x5917578)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0xc0512dd14f31196f, ext:20715723711, loc:(*time.Location)(0x5917578)}}, Count:1, Type:"Normal", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'events "noldork3sm2.16acfdd9ed048b6f" is forbidden: not yet ready to handle request' (will not retry!)
Oct 11 15:44:48 localhost k3s[3494]: E1011 15:44:48.335745    3494 controller.go:187] failed to update lease, error: Put "https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/noldork3sm2?timeout=10s": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Oct 11 15:44:48 localhost k3s[3494]: I1011 15:44:48.361750    3494 trace.go:205] Trace[1287239117]: "Create" url:/api/v1/nodes,user-agent:k3s/v1.20.4+k3s1 (linux/arm) kubernetes/838a906,client:<IP_ADDRESS> (11-Oct-2021 15:44:38.327) (total time: 10034ms):
Oct 11 15:44:48 localhost k3s[3494]: Trace[1287239117]: [10.034476968s] [10.034476968s] END
Oct 11 15:44:48 localhost k3s[3494]: E1011 15:44:48.366844    3494 kubelet_node_status.go:93] Unable to register node "noldork3sm2" with API server: nodes "noldork3sm2" is forbidden: not yet ready to handle request
Oct 11 15:44:48 localhost k3s[3494]: I1011 15:44:48.539107    3494 trace.go:205] Trace[1957906643]: "Update" url:/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/noldork3sm2,user-agent:k3s/v1.20.4+k3s1 (linux/arm) kubernetes/838a906,client:<IP_ADDRESS> (11-Oct-2021 15:44:38.534) (total time: 10003ms):
Oct 11 15:44:48 localhost k3s[3494]: Trace[1957906643]: [10.00398902s] [10.00398902s] END
Oct 11 15:44:48 localhost k3s[3494]: I1011 15:44:48.573959    3494 trace.go:205] Trace[349769923]: "GuaranteedUpdate etcd3" type:*coordination.Lease (11-Oct-2021 15:44:38.559) (total time: 10014ms):
Oct 11 15:44:48 localhost k3s[3494]: Trace[349769923]: [10.014266289s] [10.014266289s] END
Oct 11 15:44:48 localhost k3s[3494]: I1011 15:44:48.576147    3494 kubelet_node_status.go:71] Attempting to register node noldork3sm2
Oct 11 15:44:48 localhost k3s[3494]: E1011 15:44:48.602808    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.NetworkPolicy: failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:k3s-controller" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
Oct 11 15:44:48 localhost k3s[3494]: time="2021-10-11T15:44:48.894876995+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:48 http: TLS handshake error from <IP_ADDRESS>:33006: remote error: tls: bad certificate"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.167525108+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:49 http: TLS handshake error from <IP_ADDRESS>:57810: remote error: tls: bad certificate"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.253824006+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.388213202+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.501691650+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:49 http: TLS handshake error from <IP_ADDRESS>:57730: remote error: tls: bad certificate"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.627186657+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:49 http: TLS handshake error from <IP_ADDRESS>:54076: remote error: tls: bad certificate"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.878580737+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:49 localhost k3s[3494]: time="2021-10-11T15:44:49.981068208+02:00" level=error msg="runtime core not ready"
Oct 11 15:44:50 localhost k3s[3494]: time="2021-10-11T15:44:50.968247637+02:00" level=warning msg="Unable to watch for tunnel endpoints: unknown (get endpoints)"
Oct 11 15:44:52 localhost k3s[3494]: E1011 15:44:52.293654    3494 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Namespace: failed to list *v1.Namespace: namespaces is forbidden: User "system:k3s-controller" cannot list resource "namespaces" in API group "" at the cluster scope
Oct 11 15:44:52 localhost k3s[3494]: time="2021-10-11T15:44:52.700332454+02:00" level=info msg="Cluster-Http-Server 2021/10/11 15:44:52 http: TLS handshake error from <IP_ADDRESS>:40514: remote error: tls: bad certificate"
Oct 11 15:44:52 localhost k3s[3494]: I1011 15:44:52.776908    3494 trace.go:205] Trace[802387318]: "GuaranteedUpdate etcd3" type:*core.Node (11-Oct-2021 15:44:32.726) (total time: 20050ms):
Oct 11 15:44:52 localhost k3s[3494]: Trace[802387318]: [20.05053322s] [20.05053322s] END
Oct 11 15:44:52 localhost k3s[3494]: I1011 15:44:52.777779    3494 trace.go:205] Trace[1432266599]: "Patch" url:/api/v1/nodes/noldork3sm2/status,user-agent:k3s/v1.20.4+k3s1 (linux/arm) kubernetes/838a906,client:<IP_ADDRESS> (11-Oct-2021 15:44:32.724) (total time: 20052ms):
Oct 11 15:44:52 localhost k3s[3494]: Trace[1432266599]: ---"About to apply patch" 10010ms (15:44:00.762)
Oct 11 15:44:52 localhost k3s[3494]: Trace[1432266599]: [20.05269579s] [20.05269579s] END
Oct 11 15:44:52 localhost k3s[3494]: time="2021-10-11T15:44:52.835532430+02:00" level=fatal msg="flannel exited: failed to acquire lease: nodes \"noldork3sm2\" is forbidden: not yet ready to handle request"
Oct 11 15:44:53 localhost systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 15:44:53 localhost systemd[1]: k3s.service: Failed with result 'exit-code'.
Oct 11 15:44:53 localhost systemd[1]: Failed to start Lightweight Kubernetes.

It's a raspberry cluster, running v1.20.4+k3s1, two master nodes, and 5 workers.

Hi Brandond
Many thanks for your quick answer and your tip.
Poor performance, interesting, I'll check the sd card, since it was an outage, perhaps it's performing an deep-check.
What else should I check?.
I didn't filled the Bug Report, since I don't think it's a bug, the cluster was working fine for more than 200 days.
Best
i5Js

I'll also note that I've not had great results with datastores hosted on NFS. If you're going to host the datastore on another server, you might get better results from running mysql os postgres on that node and pointing at that via --datastore-endpoint, as opposed to just keeping the sqlite or etcd data on a NFS volume.

Oct 12 09:50:59 localhost avahi-daemon[272]: Joining mDNS multicast group on interface flannel.1.IPv4 with address <IP_ADDRESS>.
Oct 12 09:50:59 localhost avahi-daemon[272]: New relevant interface flannel.1.IPv4 for mDNS.
Oct 12 09:50:59 localhost avahi-daemon[272]: Registering new address record for <IP_ADDRESS> on flannel.1.IPv4.

I have seen Avahi trying to attach itself to all the pod interfaces cause really bad behavior. Could you try disabling/uninstalling avahi?

Sure thing @brandond , I’ll many thanks


Tooltip

How to make that hovering the mouse over some key words show a hint with the description of the word?
for example VS scren

A combination of the dwell event, get word at position, and then user/call tips is the approach I would suggest. You can learn about all of those topics by going through the wiki or past forum posts.

Thank you. After only a year I returned to this issue) Your approach works, but I get a word incorrectly. Even when the cursor is outside the word far below then take the final word. Also if the cursor is on the right side of the screen, then take the word from this line. I need to get a clear word on the cursor. Look at my code part:
System.Drawing.Point point = System.Windows.Forms.Control.MousePosition;         var cor = target.PointToClient(point);         var pos = target.CharPositionFromPoint(cor.X, cor.Y);         var word = target.GetWordFromPosition(pos);

I believe if you switch to the CharPositionFromPointClose method, it will return -1 when it is not actually on a valid char (i.e. word) position. Check for -1 and adjust your logic accordingly.


fix(Mercy): even more accurate OW1 Guardian Angel (credit: oreoslurpee)

fixes #1590

:tada: This issue has been resolved in version 3.1.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Feature/atrayano/mit config gmready

Yes, the latest changes affect only MITgcm, and the are zero diff for MOM and MOM6.
However, the previous PR (#26) makes impossible to merge to develop. I'll be working with @mathomp4 to fix this. The issue is that the CMakeList.txt refers to files in MOM6 that are not in the version of MOM6 referred by components.yaml

@sanAkel are you happy with me superpowering this in?
Once we do, we should probably then do a develop → main PR, and make releases of Ocean and MOM6.

@sanAkel , after talking to @mathomp4 this morning, he suggested the following plan: he could use github super-powers to merge my PR (#27) to develop. After that, you need you to do 2 things:

create a release of MOM6
create a release of OceanGridComp
Then I will create a PR of GEOSgcm fixture to reflect the updated versions of MOM6, and OceanGridComp, and also independent of all this, we need a newer tag of MITgcm

Matt is waiting for your OK of this plan before he merges PR#27

@sanAkel are you happy with me superpowering this in?
Once we do, we should probably then do a develop → main PR, and make releases of Ocean and MOM6.
Also, I think @atrayano needs a new tag of MITgcm in fixture components.yaml so that needs an Ocean release as well

@mathomp4 Go ahead! Thanks for asking.

Superpowered in! Thanks @sanAkel


MM-11359: add hint text for search exclusion

Summary

Frontend work for https://github.com/mattermost/mattermost-server/issues/11071
Ticket Link

Related Pull Requests

Has server changes server change
Has redux changes (please link here)
Has mobile changes (please link here)

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3432.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


added list of fix map types

Use a list to set the same icon for specific map types (like biome) to use on every dimension.
E.g. biome maps:
The icon is a colorful cube, which doesn't fit to the overworld. So the icon is also useful for other dimensions like the nether. Otherwise you have to copy the same icon for every dimension.
Currently only biome is used, but the list could be extended in the future.
(Pull Request reopened after branch reorganization.)

Thanks


Admin module

Supersedes https://github.com/meanjs/mean/pull/615

@rhutchison Did you see my comment in #615? I think we should go with this implementation. It really is clean, and extendable. My reservations have been addressed. I read through your conversation with @trainerbill, and I saw the light :smile:
LGTM

@rhutchison Overall, I like it.
My only question right now is:
Any particular reason that we don't allow administrators to change the email field?

@codydaig I see no reason not to - just wasn't apart of the original design.  I can see many areas to improve the admin functions once we get this merged.
@lirantal @ilanbiala any concerns with this PR?  Can probably close #615 at this point.

@rhutchison Sounds Good!
Tested and LGTM

I noticed that the Admin routes are still accessible to a user without the 'admin' role.
I saw the discussion in #686. I think this could be extended for this purpose. What have you come up with so far on the client-side roles/security?

We obviously need to fix security issues if exists here. I saw #686 but that's client side which is "tolerable" unlike if it's an actual security problem on the backend where roles/functions can be tempered with.
@rhutchison thanks a lot for the work here, please ping when we have all issues addressed and let's merge it in.

@lirantal I should have clarified. The client routes are still accessible, when manually typed into the browser address bar. The API routes return a proper 403 Forbidden response. We seem to be good on the backend security with this.

@lirantal the back-end is secure, the front-end routes are not secure.  This has been mentioned even prior to the introduction of an admin module - with articles.
#686 does not completely address the problem.  What we need is better client-side (role-based) security implementation.
This needs to be addressed in a separate PR.  If you merge #686 ahead of this commit, I will update this PR to follow that approach.

Haha.  I knew this was going to come up.  The backend is secure as no REST calls can be made.  All a user can do is get to the page, but not do anything.  I had the same problem with angular-fullstack-generator in the past and solved it with this commit:  https://github.com/trainerbill/generator-angular-fullstack/commit/7d192a343096f0800493380b1d3e9f6dcb77aef3  Basically it allowed you to put an authorize: 'admin' on the state which got check on statechangestart in ui.router.  I am guessing we could take the same approach and was actually going to look into it.

LGTM. Very good work done here. Excited to merge this into my project. No more need to manually handle this.

Great work guys.
@rhutchison do we need to make any changes to this PR since we already merged #686  ?

@rhutchison I notice both this PR and merged #686 both define the client routes with the 'admin' role. @lirantal Is this what you're referring to? This could cause conflicts when merging this in.

@mleanos I was referring in general to the fact that we should just make sure that merging this in won't cause any troubles since #686 is already merged.
With regards to the routes there specifically, both this PR and #686 are making the same change so I don't see any "code" problem or conflict to merge.

@lirantal we closed #686 and merged #700. This PR was updated to reflect the implementation of #700 and is ready to merge.

Got it. Merging.

Hi guys,
I am taking 0.4.0 for a ride and I think something is missing but maybe is on the todo list: shouldn't the app be seeded with an admin user now that the module exists? (I am just asking this since it is common practice in other frameworks)

@rmlopes That's a great point. Would you mind Opening up an issue about this? Since this is closed, discussion is bound to get missed.

it's a good point although we don't want meanjs to become a cms/platform but rather keep it lean and agile for anyone to kickstart a project.
I think I remember the meanjs generator had the option to create user/roles, no? (I might be confusing it with meanio)

@lirantal How about adding a line in the getting started position of the documentation with the mongo command to add the admin role to a user?

I'm open to suggestions. Let's continue this in a new User Roles discussion though, would you care to open the issue and let's move it there?

@rmlopes @codydaig @lirantal
https://github.com/meanjs/mean/pull/785


ColorArray definition is incorrect

This seems to be an issue with the factorio typedefs, too.
In v2.7.1, I've corrected this as a manual override.


Readme edge probing link is dead

Edge probing analysis tasks: see probing/data for more information.

This links to a 404, mainly because there is no README on the repo. Not sure what the link should be/what info should be there so can't really propose a PR.

There might be a more complete version somewhere; this is the most complete version I found (on another branch) https://github.com/jsalt18-sentence-repl/jiant/tree/edgeprobe_docs/probing/data
Even that version isn't complete (it's missing some things), so there might be a different branch with more.

Sorry, as Patrick mentioned that file exists on a branch, but I haven't had a chance to go through everything on there and clean it up to merge yet.

@iftenney - Fix or or close or unassign yourself?

Working on it, will send a PR soon. (Sorry, tied up with a conference the past week.)

See #430


Cannot map Logitech G35 keys

Since there is no official support from Logitech to support this headset in mac, I decided to give a try. The sound is ok because i can tune it with Boom2 but the custom keys are not mapped or i can't customize them. So I tryed karabiner and the event viewer can detect the key press but in the main app I can't find a way to map them to, for example mute sound.
These are the values:
eventType:SysKeyUp        code:0x11       name:                flags:                                   misc:
eventType:SysKeyUp        code:0x10       name:play_or_pause   flags:                                   misc:
eventType:SysKeyUp        code:0x12       name:                flags:                                   misc:

The fourth one is my command for screenshoot.
Thanks in advance.

So noone is able to add the custom buttons from the headset ? This is similar to the mouse with another buttons


Allowances/expectations on properties with setter

class Foo(object):
    @property
    def bar(self):
        pass

    @bar.setter
    def bar(self, value):
        pass

def do_bar(foo):
    foo.bar = 3

def test_bar_property():
    foo = Foo()
    allow(foo).bar

    do_bar(foo)

Fails with AttributeError. Besides, it is not possible to validate what was the value passed to the setter (with_args fails cannot be used with properties).

Please, consider my question in https://stackoverflow.com/questions/54327367/expectation-on-property-getter-setter-in-python-with-doubles were I posted a workaround. The workaround allows doing state testing on the property, but not creating expectation (which would also be useful):
Something like:
allow(foo).bar
expect(foo).bar = 3
expect(foo).bar = 5

do_bar()

Or even better, some syntax that allow to create expectations and allowances on the setter just as for any other method:
allow(foo).bar
expect(foo).bar.setter.withargs(3)
expect(foo).bar.setter.withargs(5)

do_bar()


Alpine Linux mktemp is very fussy...

Same fix is needed for OpenBSD:
mktemp: insufficient number of Xs in template


refactor of our python datahub client

We should revisit, refactor and tidy our python package following the alpha assessment/user research sessions. Some useful comments made in this PR https://github.com/ministryofjustice/data-platform/pull/3767

see #265


Update README

Updates README file
:ballot_box_with_check: Definition of Done checklist

[x] Meaningful title and valuable description in pull request
[x] Code change tested manually if not covered by automated tests
[x] Pull request linked to one or more issues/stories
[x] Acceptance criteria of the linked stories satisfied
[x] Code change comprehended by those who approved it
[x] State of target branch maintained or improved after the code change

I agree, good job everyone :smile:


Add TouchBar and others TouchBar.. in Main Process list

Add TouchBar and others TouchBar in the main process list in /docs/

I feel as though this folder is auto-generated from somewhere 🤔

Ah! I don't know where so? I've investigate this :) cc @zeke

Nope this file is actually not generated. Curated by hand up until now, though it obviously doesn't need to be, given that we have electron-api.json


Problem installing add-ins

I'm using ChemDraw Professional for Mac (v <IP_ADDRESS> (4318)).
I tried downloading the Examples in this repo.
If I install the '.chemdrawaddin' files directly via the Add-in Manager it works but if I try and zip the individual folders and change the extension to '.chemdrawaddin' I get the message
The "chemdraw-addin-metadata.json" package file is either missing or cannot be recognized as JSON format.

This happens if you zip the folder. Try selecting the files, right-click and select Compress x Items from the menu and rename extension to chemdrawaddin.

Thanks for the quick response, this has solved the issue!


Display a custom key in the front matter block

Problem
I manage time data in the front matter block, and the reason for doing so can be seen in this post
I hope to provide another way to display the created time and updated time
Idea
Provide an option to choose data from front matter, and then provide an input to fill in the specific key

Sorry for the late response. I would accept a PR on this, but I'm not in a position to write it myself anytime soon.

Got it, thank you for considering this request

I have implemented this feature. If you think it is OK, I will submit a PR.
https://github.com/hanaTsuk1/novel-word-count-obsidian/tree/feat/custom-key

The code looks great. Really solid work. I have a few small suggestions and want to do some testing, but go ahead and PR and I'll add a few comments.

I have created it, please check

PR merged and released. Thanks for your help!

🥳

I tried the latest version and found that after turning on 'Use advanced formatting', the file tree displayed 'undefined'🧐. I looked for the reason and found that 'COUNT_TYPE-DEFAULT_SHOR_SUFFIXES' did not set the initial value for' FrontmatterKey '. I missed this point and left a message here for you to see
https://github.com/isaaclyman/novel-word-count-obsidian/blob/master/logic/settings.ts#L88
[CountType.FrontmatterKey]: "",

Good catch. Fixed in v3.11.1.


ref_designator --> reference_designator

@FBRTMaka @oceanzus heads up

this only affects the json, it's inconsistent from the model definition in the database.


Update README.md

We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.

This PR is rejected because reference to JIra ticket does not exist in the comments section of this PR. Reviewers approve only after jira reference is added.

OP-12356

This PR is rejected because reference to JIra ticket does not exist in the comments section of this PR. Reviewers approve only after jira reference is added.


[Feature-974][connector] Add Elasticsearch7 connetcor

What problem does this PR solve?
Issue Number: close #947
Problem Summary: add elasticsearch7 connector

add streamx-flink-connector-elasticsearch7 module
code format && fix wrong words spell

Contribution Checklist

Make sure that the pull request corresponds to a GITHUB issue.

Name the pull request in the form "[Feature] [component] Title of the pull request", where Feature can be replaced by Hotfix, Bug, etc.

Minor fixes should be named following this pattern: [hotfix] [docs] Fix typo in README.md doc.

Purpose of this pull request

@monrg PTAL. I add the elasticsearch7 connector

Thanks for you review.


Update lowdb.js

Fixes #15

Coverage decreased (-0.2%) to 88.624% when pulling e11e8949c721be4e687b538c3f501d6aa068dfb4 on agentilela:master into f304c3ffc0d4623b01b810cfc731cd4a15a9f3a8 on esbenp:master.

np!


Oddity in 1.0.0-M5 when using sbt libs. Message "value xxx is not a member"

steps
$ cat K.scala
package xyz
class A() {
 def c(s:sbt.ModuleID): sbt.ModuleID = {
    s.copy(name="xxx")
  }
}
$ cat build.sbt
scalaVersion := "2.12.2"
scalacOptions ++= Seq("-Ydebug","-Ylog-classpath")
libraryDependencies += "org.scala-sbt" % "sbt" % sbtVersion.value % "provided"
$ cat project/build.properties
sbt.version=1.0.0-M5

problem
$ sbt compile
[...]
[info] [running phase typer on K.scala]
[error] /home/cunei/iii/kkk/K.scala:4:7: value copy is not a member of <root>.this.sbt.ModuleID
[error]     s.copy(name="xxx")
[error]       ^

expectation
[warn] one warning found
[success] Total time: 15 s, completed May 17, 2017 9:19:07 PM

(which is what happens with 1.0.0-M4)

copy method is actually gone. plz use .withName("xxx").

See:

https://github.com/sbt/contraband/pull/38 "Add support for public, overloaded, bincompat copy"
https://github.com/sbt/contraband/pull/44 "Allow by-name selection by adding parameter default values"
https://github.com/sbt/contraband/issues/48 "exposing copy is not safe"
https://github.com/sbt/contraband/issues/49 "Default Arguments vs Interspersed Growth (Design Decision)"
https://github.com/sbt/contraband/pull/50 "Remove public copy method"


[Master] Support unpackdiskimage to recheck dasdfmt.

Signed-off-by: zhengxiaomei123<EMAIL_ADDRESS>

lgtm, need fix conflict..


preact-router not compatible with history v5 types

Hey folks,
I'm on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(both latest stable versions), and I'm running into similar / the same issues as reported in https://github.com/preactjs/preact-router/issues/385. I was looking around a bit and found https://github.com/preactjs/preact-router/pull/410 and https://github.com/preactjs/preact-router/pull/387 which claim to have solved the history v5 issue.
I have checked my package and package-lockfile to make sure the versions installed are the versions reported above.
Here is the use case and the error message, in case it helps
import { createHashHistory } from 'history';

// ...

<Router history={createHashHistory()}>

src/components/app.tsx:20:17 - error TS2322: Type 'HashHistory' is not assignable to type 'CustomHistory'.
  Types of property 'listen' are incompatible.
    Type '(listener: Listener) => () => void' is not assignable to type '(callback: (location: Location) => void) => () => void'.
      Types of parameters 'listener' and 'callback' are incompatible.
        Types of parameters 'location' and 'update' are incompatible.
          Type 'Update' is missing the following properties from type 'Location': pathname, search

20         <Router history={createHashHistory()}>
                   ~~~~~~~

  node_modules/preact-router/index.d.ts:46:2
    46  history?: CustomHistory;
        ~~~~~~~
    The expected type comes from property 'history' which is declared here on type 'IntrinsicAttributes & RouterProps<Record<string, string | undefined> | null> & Readonly<Attributes & { children?: ComponentChildren; ref?: Ref<...> | undefined; }>'

Workarounds I tried (and don't work)

Downgrading to history@4 does not work, because it doesn't seem to come with typescript types, and tsc type checking then fails.

Using history@5 with the workaround from https://github.com/preactjs/preact-router/issues/385#issuecomment-894076265 type-checks, but then at build time results in a very strange non-descriptive error message.

 Build  [=========== ] 95% (13.6s) emitting
ReferenceError: document is not defined
method: null
at: undefined:null:null

Source code:

✖ ERROR TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received undefined
    at new NodeError (node:internal/errors:371:5)
    at _write (node:internal/streams/writable:312:13)
    at WriteStream.Writable.write (node:internal/streams/writable:334:10)
    at handlePrerenderError (/app/node_modules/preact-cli/lib/lib/webpack/prerender.js:110:18)

Any ideas what could be the cause of this? Curious if other folks successfully are using latest preact-router and history v5 with typyescript. Let me know if I can provide more information here.

Types not lining up doesn't mean it's incompatible. It might be on you to configure your tsconfig.json to be more lenient or simply use // @ts-ignore.

Downgrading to history@4 does not work, because it doesn't seem to come with typescript types, and tsc type checking then fails.

This is purely a result of your strict configuration; you can disable noImplicitAny or, again, use ignore comments.
It does have types at @types/history, which might be usable (DefinitelyTyped can be a bit hit-or-miss).

but then at build time results in a very strange non-descriptive error message.

The error tells you exactly what the problem is: document is not defined.
This is the same issue as #414, and maybe there's a disconnect here? Hash routers only work in a browser environment; this is the key underlying functionality that powers them. Therefore you cannot use them in Node, which Preact-CLI (I assume you're using, though you haven't specified) uses in order to prerender your apps. They're fundamentally incompatible.
You can get around this by dropping out of prerendering or using window checks (see https://github.com/preactjs/preact-cli#pre-rendering). However, without the router being available, there's likely little value in prerendering.

PRs welcome, but I'd push people to use preact-iso instead.

@rschristian preact-iso doesn't support hash-based routing (and not planned based on issues)

The use case I had in mind when I originally opened the ticket was deploying a preact page on a static host such as Github Pages or AWS S3. On there you'd deploy a single index.html plus assets such as css, js, etc.
And on these deployments it makes a difference if the route is

example.com/myroute, or
example.com/#/myroute

because in the first case if a user goes to that route, the static page server will respond with an error page and/or error response code even before the preact code has any chance to run. In the second case the user goes to index.html where the route gets properly handled by the preact hash router.
On some deployments there are workaround but on others there are not; and there's also a high chance that I might not fully understand how such a preact deployment without a hash router is supposed to look like.
Just adding this context because from this use case's point of view a hash router is definitely needed. Is this not a use case other people are running into and am I just using this wrong?

I'll also throw in hash routing is useful for local/standalone deployment scenarios as well. Having the ability to do both means you routing can "just work" regardless of whether you control the server, or if it is even on a server. While these are not the most common use case, they are not uncommon either.

preact-router isn't going anywhere, it can continued to be used for any hash routers people need, as can the ecosystem of alternative routers. preact-iso looks to offer isomorphic tooling and hash routers are inherently non-isomorphic, which is why it will not be offered there at any point. It just wouldn't make sense and would clash with some of the tools offered.
Ideally those static hosts that are still stuck in the 90's will catch up though -- Nginx & Apache have offered fallback routes for 20+ years, it's quite embarrassing that some hosts that are unable to do the same. That just isn't an issue you'll run into on a properly established web host.

That is of course your prerogative. I only wanted to voice support for the feature as it is something I'd use myself.

Was this not fixed in #410 ? It's still an issue for me

Was this not fixed in #410 ? It's still an issue for me

The implementation was fixed so that it functions as intended; types are a separate issue however, and one that won't be addressed as preact-router is unfortunately not actively maintained anymore

@rschristian is there a viable alternative to preact-router?

If you need hash routing, you can look to react-router or wouter perhaps.


Modifications for 1.1.0 version

Hello! Excellent plugin! I made some changes to make it more generic.
Options added:

updateComponentOnChange: true
Description: If false, it will not update the content inside the component when the user pick an item;

itemProperty: null
Description: Defines which property will be accessed to show the value. It is used when you pass an array of Objects to 'items' option;

pickerItemClass: "picker-item"
Description: Defines the selector class of the picker item. Use this option along with the "pickerItem" in template option;

itemValueSelector: "i"
Description: For default, it will consider to use an <i> element for displaying the value of pickerItem, but to be more generic, you may specifies other element like a 'span' element. Use this option along with the "pickerItem" in template option;

Bugs fixed:

Fix issue that occurs when the value selected matches with more than one option in popover like '1' and '11';
Fix problem when define a "pickerItem" template that does not have "picker-item" class;
Fix implementation of method isEmptyObject

Aditional:

Update README.md file
Update index.html with new example

See it online here and here

With these modifications you can generate a 1.1.0 version, like here

Hi Victor thanks a lot for the awesome contribution! I find all that very useful.
I added you as a collaborator of the project so you could also regularly contribute directly with the project and release new versions.
Could you release 1.1.0 (I don't have access to the markdown of your release), it would be nice, but before could you update the version in package.json and remove the version property of bower.json (which is not longer used because Bower is using now tag versioning).
Thanks!

Ok, @mjolnic ! I will try to implement some suggestions made by @jasondavis before release a new version.

That would be great. Thank you both


⚠ SceneTime has degraded performance

In 32f679a, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 9114 ms

Resolved: SceneTime performance has improved in f2c5f3b after 5 minutes.


Replace ncar_pylib with CISL's conda module

Description
The ncar_pylib scripts on cheyenne/casper will be deprecated soon.  See #97 for more details.
This PR transitions MPAS-Workflow to use CISL's new conda module for python.  The least invasive and only functional way to do this that I found was to move the python environment setup to the cylc init-script phase.  I.e., see the various phases of cylc tasks. As such, config/environmentPython.csh is deprecated in favor of the new loading mechanism in include/tasks.rc. I.e., L18-24 of include/tasks.rc:
  [[BATCH]]
    # load conda + activate npl
    init-script = '''
source /etc/profile.d/modules.sh
module load conda/latest
conda activate npl
'''

config/environment.csh is additionally streamlined to only load the JEDI environment and is renamed to config/environmentJEDI.csh, while config/environmentForJedi.csh is removed.  That was done to avoid two scripts when one is enough.  A small change was needed in ObsToIODA.csh as a result.  Other task scripts are touched in order to rename the environment script or totally remove it when no longer needed (e.g., PrepJEDI.csh and PrepVariational.csh, which only need the python environment).
The nccmp module was only used by compareobs.csh and comparmodelcsh.  So it is moved there.  ncdiff is distributed as part of the npl conda environment, and does not require additional module loads.  We are no longer using nco, because the formerly used ncks command was replaced by in-core file I/O of the applicable model fields.
The many files touched by this PR achieves an untying of overly-complex environment dependencies, which should ease future maintenance.
Issue closed
Closes #97
Tests completed

[x] 3dvar_OIE120km_WarmStart
[x] 3denvar_OIE120km_WarmStart
[x] 3dvar_OIE120km_ColdStart
[x] 3denvar_O30kmIE60km_WarmStart
[x] eda_OIE120km_WarmStart

Users should be aware that in order for the modified env-setup scripts to work properly, they must be sourced in a new terminal window or one where ncar_pylib is not activated and where the python module is not loaded.  If you already have NPL activated via ncar_pylib, you may execute the following.
deactivate
module unload python
source env-setup/cheyenne.${YourShell}


Intro to data engineering with Snowpark Python: For BUILD HOL

This PR adds Intro to Data Engineering with Snowpark Python BUILD HOL contents as a quickstart.

Hi @vinodhini-sd! To be consistent with all other QS Guides, please replace '-' with '_' in the filename of the .md file as well as the 'id' of the QS. Thanks!

Updated it


Add fullpath attribute to Spectrum Node

This is necessary to implement a delete functionality.

AFAIK the fullpath should also be in there. So if it's not, than that'd be a bug.
https://github.com/cryptoadvance/specter-desktop/blob/master/src/cryptoadvance/specter/managers/node_manager.py#L246-L250

The spectrum node doesn't have a fullpath attribute and the line you cited in the node manager is not setting it.


Nuxt 2.15.7 vue-confirm-dialog not found

ERROR  Failed to compile with 1 errors                                                                                friendly-errors 21:46:41
This dependency was not found:

vue-confirm-dialog in ./plugins/vue_confirm_dialog.client.js

1.1.0 version of vue-confirm-dialog.
I tried everything.

same issue

Me too, Same issue

same - downgraded to 1.0.0 all ok


Pass extra props down to wrapped component

I have been using redux-subspace with react-router to isolate my pages from one another.
This has worked great as it has allowed me to develop each page as almost an entirely seperate application.
How I have this setup is as follows (simplified from my actual code)
index.js
import React from 'react'
import ReactDOM from 'react-dom'
import { createStore, combineReducers, applyMiddleware } from 'redux'
import { Provider } from 'react-redux'
import { Router, Route, browserHistory } from 'react-router'
import { syncHistoryWithStore, routerMiddleware, routerReducer as routing } from 'react-router-redux'
import { SubspaceProvider, namespaced } from 'redux-subspace'
import { SubPage1, reducer as subpage1 } from './SubPage1'
import { SubPage2, reducer as subpage2 } from './SubPage2'

const reducer = combineReducers({
    routing,
    subpage1: namespaced(subpage1, 'subpage1'),
    subpage2: namespaced(subpage2, 'subpage2'),
})
const middleware = applyMiddleware(routerMiddleware(browserHistory))
const store = createStore(reducer, middleware);
const history = syncHistoryWithStore(browserHistory, store)

const SubspacedSubPage1 = () =>
    <SubspaceProvider mapState={state => state.login} namespace='subPage1'>
        <SubPage1 />
    </SubspaceProvider>

const SubspacedSubPages2 = () =>
    <SubspaceProvider mapState={state => state.characters} namespace='subpage2'>
        <SubPage2 />
    </SubspaceProvider>

ReactDOM.render(
    <Provider store={store}>
        <Router history={history}>
            <Route path="/sub-page-1" component={SubspacedSubPage1} />
            <Route path="/sub-page-2/:someParam" component={SubspacedSubPage2} />
        </Router>
    </Provider>,
    document.getElementById('root')
)

SubPage1.js
import React from 'react';
import { connect } from 'react-redux';

const SubPage1 = () =>

Hello From SubPage1

const mapStateToProps = (state) => {
    return {
        ...state
    }
}

export default connect(mapStateToProps)(SubPage1)

SubPage2.js
import React from 'react';
import { connect } from 'react-redux';

const SubPage2 = (someParam) =>

Hello From SubPage2 with someParam={someParam}

const mapStateToProps = (state, ownProps) => {
    return {
        ...state
        ...ownProps.params
    }
}

export default connect(mapStateToProps)(SubPage2)

This works great, except for the someParam part. React router provides the params to the components props, which is SubspaceProvider and not the wrapped component.
I did manage to get around this with the following changes to index.js
const SubspacedSubPages2 = (props) =>
    <SubspaceProvider mapState={state => state.characters} namespace='subpage2'>
        <SubPage2 {...props}/>
    </SubspaceProvider>

However, I can also see other use cases where the parent component wants to pass params down to the underlying component, but either doesn't have access to the child to do so (like my case above where it was wrapped by another component) or it has imported a subspaced component and doesn't realise it cannot pass props (its is probably a bad design to expect props and also subspace yourself, but if you did want that its current not doable).
I propose that SubspaceProvider passes any extra props it receives down to the child component.

My initial reaction to this was "sure, why not", but I have been thinking about it and I don't think passing on the props makes much sense.
SubspaceProvider is designed to written in a jsx block and as such, any props can easily be provided to the children, as your workaround quite nicely shows.  Implementing your suggesting might work in this case but the following snippet might behave a bit unexpectedly for someone else:
const MyAwesomeComponent = () =>
    <SubspaceProvider mapState={state => state.childState} childValue='value1'>
        <ChildComponent childValue='value2'/>
    </SubspaceProvider>

What would you expect childValue to equate to?
I have 2 thoughts to get around this:

Can you move the SubspaceProvider to be around the Route instead of inside it (Route might not allow this), i.e.

ReactDOM.render(
    <Provider store={store}>
        <Router history={history}>
            <SubspaceProvider mapState={state => state.login} namespace='subPage1'>
                <Route path="/sub-page-1" component={SubPage1} />
            </SubspaceProvider>
            <SubspaceProvider mapState={state => state.characters} namespace='subPage2'>
                <Route path="/sub-page-2/:someParam" component={SubPage2} />
            </SubspaceProvider>
        </Router>
    </Provider>,
    document.getElementById('root')
)

Perhaps we could provide a function similar to react-redux's connect function for cases where you don't want to use SubspaceProvider in a jsx block that does pass on the props, e.g.

ReactDOM.render(
    <Provider store={store}>
        <Router history={history}>
            <Route path="/sub-page-1" component={subspaced(state => state.login, 'subPage1')(SubPage1)} />
            <Route path="/sub-page-2/:someParam" component={subspaced(state => state.characters, 'subPage2')(SubPage2)} />
        </Router>
    </Provider>,
    document.getElementById('root')

Happy to hear any comments or suggestions on this.

While it didn't cause any errors in the console in relation to proptypes, option 1 did not work. If I did a console.log(state) in the mapStateToProps function, it gave me the entire state tree.
Option 2 (using a HOC) seems like a good compromise for places that you just want to add in subspace to something that needs to accept props.
Although having said all that, the more I play with my little project (adding more routes and default routes that point to "home" style pages), the more my "workaround" seems to actually be good solution, as I can wrap the component once and use it in any route I like... however, option 2 could probably give the same result.


Only export test coverage for current version

Pull Request Test Coverage Report for Build 32cd20c886e1155a8d8b87bbc2e23f730fd270d6-PR-39

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build e8de45611981f75053bc7d1a53e552720a95949c:
0.0%

Covered Lines:
349

Relevant Lines:
349

💛  - Coveralls

Pull Request Test Coverage Report for Build 508845a22713dc0057c056c156fa6bbeccd83fc0-PR-39
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build e8de45611981f75053bc7d1a53e552720a95949c:
0.0%

Covered Lines:
349

Relevant Lines:
349

💛  - Coveralls


Enable/Disable wakeup by motion

Hello,
First of all, thank you for amazing app,
I would have one small feature request. It would be nice if I could enable or disable waking up of screen by motion sensor by MQTT or REST command. Background behind this is I would like to setup automation, and have the screen active whole time as somebody is home, but to have motion wakeup only at night. I could send wakeup command periodically to keep screen on but it could be more elegant if this could be set by commands.
thanks

Since this request hasn't been worked or hasn't been voted up, I am closing the request for now.  Thanks!


Custom image upload function (#103)

I'm submitting a...

[ ] Bug Fix
[x] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[x] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"
A document related commit is prefixed "docs:"

[x] Docs have been added / updated (for bug fixes / features)

Description
Just like in issue #103 I'm submitting the implementation of exposing image upload event - this way it's possible to call custom method when the image is uploaded. It can be useful in cases where the endpoint is for example protected and needs some additional headers, etc.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR affects any existing issues?

[ ] Yes
[x] No

if yes mention the issue number and what kind of change it is
for example: closes #1, fixes #1, etc.,

Sorry for the long delay. And sorry for closing the PR. I hate to see the work go to waste.
Since v5 its possible to add plugins see and custom toolbar items
Ref:
https://sibiraj.dev/ngx-editor/additional-documentation/menu-plugin.html
https://prosemirror.net/examples/upload/
You can add your own function to upload images.


Admin actions in C: drive doesnt work

Description
When trying to do an admin required action it just does nothing. (no in app pop out or the Windows UAC prompt) I haven't tried in other drives/partitions since I don't have any.
Steps To Reproduce
No response
Expected behavior
It should ask for admin
Files Version
1.9.21
Windows Version
10.0.19043.1151
Relevant Assets
debug.log
debug_fulltrust.log

When trying to do an admin required action it just does nothing.

Delete? Copy? Everything?

i have tried creating, deleting and moving

Thanks, do you remember it working on Files <=1.9.20?

last time I test was with 1.9.0,0 I think.

This issue should be resolved with #5757.


Sort by Path

Because path is stored as a blob, COLLATE NOCASE doesn't work, lowercase entries come after uppercase ones.
ORDER BY LOWER(path) does work though.

Sounds good. A patch to make this work would be helpful.


chore: update Catppuccin source URLs

Description
Closes #8 by pulling from esm.sh like I suggested.
Linked Issues
#8

Urls should be a valid GitHub link as we fetch the sha and commit info from it. I would wish the dist on GH could still be preserved, but if that's the decision, we could fetch from the extension dist instead: https://github.com/antfu/textmate-grammars-themes/blob/326db1cd5f95513a45372a458e0cef13a684f50f/sources-themes.ts#L138-L146


The details for this page appear to be out of date

Going through the instructions, step 5b which says, "b.For the Office 365 Audit Logs connector, Common Data Service connection, and Office 365 Audit Logs Connection, select Select during import, and then choose your connection. "
I have different connections at this point. See attached. The one for "O365 Logs" doesn't give me any clues on what, or where, I should connect it to, nor does it tell me what's wrong. Everything up until this point has worked perfectly.

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

ID: 1855a9ee-8713-c8e6-2091-bc972f877c13
Version Independent ID: c87a0108-4de6-49df-8ba3-3bdb06216ad8
Content: Set up audit log components - Power Platform
Content Source: power-platform/guidance/coe/setup-auditlog.md
Service: power-platform
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Went through again and it's working now. not sure what happened. Closing this issue.


Add GitHub Action build workflows

Mac workers mean we can build and test all current targets.

It ran in my fork: https://github.com/JakeWharton/kotlin-codepoints/actions/runs/3959685800/jobs/6782832165

Thanks


add title test case

Travis is failing

it's the same failure as https://github.com/sindresorhus/fkill/pull/38#issuecomment-657739763 and I think this is a good regression test case
It's all because of https://github.com/sindresorhus/ps-list/pull/45

This needs to be made a separate test.failing.