Elemental node registered to Rancher but elemental-system-agent at node keeps on loop with no proper error message

I took steps as suggested in the Elemental Quickstart guide but after booting Elemental Teal ISO, my machine reboot and then get stuck with error as below:

rancher-31156:~ # journalctl -f -u elemental-system-agent
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[K8s] Processing secret m-e1473c86-171d-4f84-a67f-54b20398180b in namespace fleet-default at generation 0 with resource version 467933"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[K8s] Applied checksum was the same as the plan from remote. Not applying."
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[K8s] last applied resource version (467933) did not change. running probes, skipping apply."
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[Applyinator] Applying plan with checksum 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[Applyinator] Writing applied calculated plan contents to historical plan directory /var/lib/elemental/agent/applied"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[Applyinator] Not writing applied plan to file 20230118-172906-applied.plan as the last file written (20230118-171542-applied.plan) had identical contents"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[Applyinator] Cleaning working directory before applying /var/lib/elemental/agent/work"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[K8s] writing an applied checksum value of 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a to the remote plan"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[K8s] Enqueueing after 5.000000 seconds"
Jan 18 17:29:06 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:06Z" level=debug msg="[K8s] secret data/string-data did not change, not updating secret"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[K8s] Processing secret m-e1473c86-171d-4f84-a67f-54b20398180b in namespace fleet-default at generation 0 with resource version 467933"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[K8s] Applied checksum was the same as the plan from remote. Not applying."
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[K8s] last applied resource version (467933) did not change. running probes, skipping apply."
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[Applyinator] Applying plan with checksum 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[Applyinator] Writing applied calculated plan contents to historical plan directory /var/lib/elemental/agent/applied"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[Applyinator] Not writing applied plan to file 20230118-172911-applied.plan as the last file written (20230118-171542-applied.plan) had identical contents"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[Applyinator] Cleaning working directory before applying /var/lib/elemental/agent/work"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[K8s] writing an applied checksum value of 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a to the remote plan"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[K8s] Enqueueing after 5.000000 seconds"
Jan 18 17:29:11 rancher-31156 elemental-system-agent[1738]: time="2023-01-18T17:29:11Z" level=debug msg="[K8s] secret data/string-data did not change, not updating secret"
^C
rancher-31156:~ # journalctl -f -u rancher-system-agent
^C
rancher-31156:~ #

Where as elemental shows no error:

rancher-31156:~ # journalctl -f -t elemental
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Done executing stage 'network.after'
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Running stage: network.before
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Executing BOOT_IMAGE=(loop0)/boot/vmlinuz console=tty1 console=ttyS0 root=LABEL=COS_ACTIVE cos-img/filename=/cOS/active.img panic=5 rd.cos.oemlabel=COS_OEM rd.neednet=0 rd.emergency=reboot rd.shell=0 panic=5 systemd.crash_reboot systemd.crash_shell=0
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Done executing stage 'network.before'
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Running stage: network
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Executing BOOT_IMAGE=(loop0)/boot/vmlinuz console=tty1 console=ttyS0 root=LABEL=COS_ACTIVE cos-img/filename=/cOS/active.img panic=5 rd.cos.oemlabel=COS_OEM rd.neednet=0 rd.emergency=reboot rd.shell=0 panic=5 systemd.crash_reboot systemd.crash_shell=0
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Done executing stage 'network'
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Running stage: network.after
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Executing BOOT_IMAGE=(loop0)/boot/vmlinuz console=tty1 console=ttyS0 root=LABEL=COS_ACTIVE cos-img/filename=/cOS/active.img panic=5 rd.cos.oemlabel=COS_OEM rd.neednet=0 rd.emergency=reboot rd.shell=0 panic=5 systemd.crash_reboot systemd.crash_shell=0
Jan 18 17:15:41 rancher-31156 elemental[1699]: INFO[2023-01-18T17:15:41Z] Done executing stage 'network.after'
What did you expect to happen:

I expect Device on boarded to RMS elemental cluster and install k3s and my elemental cluster active, not in provisioning

Anything else you would like to add:

I tried multiple times and even tried after uninstalling elemental-operator helm charts from scratch, but still get same issue.

Environment:

Elemental release version (use cat /etc/os-release):
rancher-31156:~ # cat /etc/os-release
NAME="SLE Micro"
VERSION="5.3"
VERSION_ID="5.3"
PRETTY_NAME="SUSE Linux Enterprise Micro for Rancher 5.3"
ID="sle-micro-rancher"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sle-micro-rancher:5.3"
IMAGE_REPO="registry.opensuse.org/isv/rancher/elemental/stable/teal53/15.4/rancher/elemental-teal/5.3"
IMAGE_TAG="1.0.0-33.29"
IMAGE="registry.opensuse.org/isv/rancher/elemental/stable/teal53/15.4/rancher/elemental-teal/5.3:1.0.0-33.29"
TIMESTAMP=20230110084743
GRUB_ENTRY_NAME="Elemental"
rancher-31156:~ #

Rancher version: 2.7

Kubernetes version (use kubectl version):

hades22@hades2xxxx:~$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:58:30Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.4+k3s1", GitCommit:"c3f830e9b9ed8a4d9d0e2aa663b4591b923a296e", GitTreeState:"clean", BuildDate:"2022-08-25T03:45:26Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.26) and server (1.24) exceeds the supported minor version skew of +/-1

Cloud provider or hardware configuration:
HW is Intel NUC i7 with 8 core , 32 GB ram and TPM in it

Hi @yshashix
Could you also please post the elemental-operator logs kubectl logs -n cattle-elemental-system -l app=elemental-operator and the resources used (MachineRegistration, Cluster,  and MachineInventorySelectorTemplate)  and also the generated MachineInventory kubectl get machineinventory -n fleet-default -o yaml

Did you remove the elemental resources when reinstalling the operator? One thing that could show this behavior is reinstalling a machine without removing the MachineInventory. Then the rancher-system-agent will still believe plans are applied to the machine and do nothing.

@frelon ,
I have deleted selector.yaml ,cluster.yaml ,registration.yaml and also deleted Namespace: [cattle-elemental-system]. It was fresh installation and there was no MachineInventory before I reboot node with ISO, so I guess it could be something more.
Steps I followed to delete operators are:
       kubectl delete -f registration.yaml

501  kubectl delete -f cluster.yaml
502  kubectl delete -f selector.yaml
503  helm --uninstall elemental-operator -n cattle-elemental-system
504  helm uninstall elemental-operator -n cattle-elemental-system
505  helm list -A
506  kubectl get pods -n cattle-elemental-system
507  kubectl get ns
508  kubectl delete namespace cattle-elemental-system
Elemental Operator is not able to connect to steve aggregations:
hades22@hades22-NUC8i7HVK:~$ kubectl logs -n cattle-elemental-system -l app=elemental-operator
time="2023-01-19T08:41:58Z" level=info msg="Starting steve aggregation client"
time="2023-01-19T08:41:58Z" level=info msg="Starting /v1, Kind=ServiceAccount controller"
time="2023-01-19T08:41:58Z" level=error msg="Failed to dial steve aggregation server: dial tcp <IP_ADDRESS>:443: connect: connection refused"
time="2023-01-19T08:42:01Z" level=error msg="error syncing 'fleet-default/my-nodes': handler machine-registration: add Secret to my-nodes ServiceAccount: Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s\": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:9443, code 503: 503 Service Unavailable, requeuing"
time="2023-01-19T08:42:04Z" level=error msg="error syncing 'fleet-default/my-nodes': handler machine-registration: add Secret to my-nodes ServiceAccount: Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s\": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:9443, code 503: 503 Service Unavailable, requeuing"
time="2023-01-19T08:42:07Z" level=error msg="error syncing 'fleet-default/my-nodes': handler machine-registration: add Secret to my-nodes ServiceAccount: Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s\": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:9443, code 503: 503 Service Unavailable, requeuing"
time="2023-01-19T08:42:10Z" level=error msg="error syncing 'fleet-default/my-nodes': handler machine-registration: add Secret to my-nodes ServiceAccount: Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s\": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:9443, code 503: 503 Service Unavailable, requeuing"
time="2023-01-19T08:42:13Z" level=error msg="error syncing 'fleet-default/my-nodes': handler machine-registration: add Secret to my-nodes ServiceAccount: Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s\": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:9443, code 503: 503 Service Unavailable, requeuing"
time="2023-01-19T08:42:16Z" level=error msg="error syncing 'fleet-default/my-nodes': handler machine-registration: add Secret to my-nodes ServiceAccount: Internal error occurred: failed calling webhook "rancher.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s\": proxy error from <IP_ADDRESS>:6443 while dialing <IP_ADDRESS>:9443, code 503: 503 Service Unavailable, requeuing"
time="2023-01-19T09:41:58Z" level=info msg="Creating event broadcaster for mos-sync"
hades22@hades22-NUC8i7HVK:~$

Generated Mahineinventory:
hades22@hades22-NUC8i7HVK:~$ kubectl get machineinventory -n fleet-default -o yaml
apiVersion: v1
items:

apiVersion: elemental.cattle.io/v1beta1
kind: MachineInventory
metadata:
creationTimestamp: "2023-01-18T17:10:09Z"
generation: 1
labels:
machineUUID: e1473c86-171d-4f84-a67f-54b20398180b
manufacturer: Intel-R-Client-Systems
productName: NUC7i7DNHE
serialNumber: BTDN018000NP
name: m-e1473c86-171d-4f84-a67f-54b20398180b
namespace: fleet-default
resourceVersion: "467936"
uid: 63439049-8b42-4979-ad34-910b2af6e28a
spec:
tpmHash: 4964b06a18e943db64b547996fc17e22513667fa175766679905582571c3a313
status:
conditions:

lastUpdateTime: "2023-01-18T17:10:09Z"
reason: InitializedPlan
status: "True"
type: Initialized
lastUpdateTime: "2023-01-18T17:16:21Z"
reason: PlanSuccefullyApplied
status: "True"
type: Ready
lastUpdateTime: "2023-01-18T17:16:21Z"
reason: PlanSuccefullyApplied
status: "True"
type: PlanReady
plan:
appliedChecksum: 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a
checksum: 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a
secretRef:
name: m-e1473c86-171d-4f84-a67f-54b20398180b
namespace: fleet-default
kind: List
metadata:
resourceVersion: ""
hades22@hades22-NUC8i7HVK:~$

MachineRegistration, Cluster, and MachineInventorySelectorTemplate are attached

Hey @yshashix 👋🏼
I think you miss the location=europe label in your MachineInventory, which is used to pick up nodes for building cluster.
You can either add the label in the MachineRegistration (under machineInvetoryLabels, but before doing the registration) or you can add the label manually once the MachineInventory got created. Something like:
kubectl label -n fleet-default machineinventories.elemental.cattle.io m-e1473c86-171d-4f84-a67f-54b20398180b location=europelocation=europe

Ohh yes, I mentioned ith using kubectl label and restarted machine. But somehow it seems doing nothing even now I don't see anything in journalctl -f -u elemental-system-agent but in rancher-system-agent I see below message:
m-e1473c86-171d-4f84-a67f-54b20398180b:~ # journalctl -f -u rancher-system-agent
Jan 20 08:45:52 m-e1473c86-171d-4f84-a67f-54b20398180b systemd[1]: Started Rancher System Agent.
Jan 20 08:45:53 m-e1473c86-171d-4f84-a67f-54b20398180b rancher-system-agent[1703]: time="2023-01-20T08:45:53Z" level=info msg="Rancher System Agent version v0.2.13 (4fa9427) is starting"
Jan 20 08:45:53 m-e1473c86-171d-4f84-a67f-54b20398180b rancher-system-agent[1703]: time="2023-01-20T08:45:53Z" level=info msg="Using directory /var/lib/rancher/agent/work for work"
Jan 20 08:45:53 m-e1473c86-171d-4f84-a67f-54b20398180b rancher-system-agent[1703]: time="2023-01-20T08:45:53Z" level=info msg="Starting remote watch of plans"
Jan 20 08:45:53 m-e1473c86-171d-4f84-a67f-54b20398180b rancher-system-agent[1703]: time="2023-01-20T08:45:53Z" level=info msg="Starting /v1, Kind=Secret controller"
^C

May be I should do fresh installation next week with Europe location

Well, if all went right you should have elemental-system-agent stopped now, and rancher-system-agent running (as above).
Seems the selector (which should pick the node based on labels) did not picked up the machineinventory of the host (yet?).
That would explain rancher-system-agent waiting for plans.
You should also get "Waiting for viable init node" on Rancher, for the cluster. If not, I would bet the selector already picked up a "old?" machineinventory (old installed system). In that case I would delete the cluster and then recreate it.

closing for lack of progress


Fix issue #188: '[Enhancement] PR update message with summarized details

This change makes it possible to summarize the details responding to each PR comment.

New openhands update


About the rotation of normal map

Dear Authors:
Thank you for your great work. After reading the code, I have a question about the normal loss. The normal map between the    omnidata's perdition and the monosdf is different, calculating the loss between these two normal maps should get the rotation, but I do not find the rotation during the loss calculation.

Hi, the code for rotation is here: https://github.com/autonomousvision/monosdf/blob/main/code/model/network.py#L501-L504

Thank you for your reply.


A few roles are missing even after using the Intelligent BPM Setup recipe

Tutorial URL: https://developers.sap.com/tutorials/cp-starter-ibpm-employeeonboarding-4-visibility.html
Step 1: Create a business scenario- Here when we click on the Configure Visibility Scenarios app, got the below permission error:

Later noticed that below process visibility roles were missing for my user-
PVAdmin, PVDeveloper, PVEventSender, PVOperator, PVTenantOperator
These roles should have been added when the recipe was used. But these roles were missing due to which the above shown permission error was displayed.
Please include these roles to be added when we start the recipe or include a step in the tutorial to add these roles.
Thanks & Regards,
Priyanka

Hello Priyanka,
Was the process visibility entitlement assigned in your account?

Hi Archana,
yes the process visibility entitlement was assigned to my account.
Thanks & Regards,
Priyanka

The hotfix is provided for the recipe.
@thecodester - please close the issue


Test error on dotnet sdk 2.1.300

I'm using Debian 10 for building.
Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Testhost process exited with error: Unhandled Exception: System.MissingMethodException: Method not found: 'Void Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TestRequestHandler..ctor()'.
at Microsoft.VisualStudio.TestPlatform.TestHost.DefaultEngineInvoker..ctor()
at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Run(String[] args)
at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Main(String[] args)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources, CancellationToken cancellationToken)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyExecutionManager.StartTestRun(TestRunCriteria testRunCriteria, ITestRunEventsHandler eventHandler)
Test Run Aborted.

Hey there! Thank you for contacting our development team at GitHub.
We believe that your issue does not meet our contributing guidelines referenced during issue creation.

Before you open an issue please review the contributing guidelines for this repository.
(...)
I understand that if my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue that is not related to ASF development in any way, then it will be closed and left unanswered.

Reason for closing: this is intended ASF behaviour / technical issue / not a bug.
Please check out our wiki if you need further help.
Have a nice day!
~Archi


A proposal to add the base property to standard slice types

Next time you assign a number to a proposal, please update README.md also.

@dabrahams That isn't really practical for contributors to do, nor is it the standard protocol - they don't know what order evolution proposals will get merged in, so they can't number them.


Fix missing import and illegal removal of new

Not sure how these were not caught via the analyzer upstream but they are breaking Google.

Wasn't Future added/going to be added dart:core? If upstream linters/analyzer are using an older dart it might not work...still odd

Gah... I think it is the analyzer version problem... For this PR, I am getting
info • Unnecessary new keyword • packages/flutter_tools/lib/src/commands/daemon.dart:187:5 • unnecessary_new
Internally (and on Dartpad), this idiom does not work:
new Future.sync() vs Future.sync().
I assume the latter is just assumed to be a static fn call, which I admit, is probably the right way to interpret it. Removing new keyword from named ctrs is probably not the right move.
@keertip

@leafpetersen

@mehmetf, you don't need the import. dart:async is now exported by dart:core

Yep Flutter is now at 2.1.0-dev.4 whereas internally we are at dev.3.1
One way to mitigate this would be to allow a grace period of backward compat. I think the import is one example where both importing and not importing works.
The new vs not-new Future.sync() is not backward compatible. I will seek permission to disable this analyzer check and unblock Google rolls. The dev.4 is not landing to google until next week.


Upgrade to Mosby

Moxy has silently released a few bug fixes, include some memory leak fixes.  Upgrade the apps usage to use the latest version.

Moxy does not seem to be being maintained as much as it used to be, and the app is in a better state for mvp, so migrate to the Mosby framework.

Moxy has been forked and is now under moxy-community which addresses several issues I had with moxy.   Upgraded to moxy 2.x.


[Bug]: Docker Registry not working

Is there an existing issue for this?

[X] I have searched the existing issues

Example public repository
coolify
Description
I Added a docker registry "ghcr" when I try to do deployment using docker-compose it say "unauthorized"
-Remote docker
[12:29:22.719] Debug logging is disabled. Enable it above if necessary!
[12:29:23.100] Cloning repo:staging...
[12:29:28.933] Configuration changed
[12:29:33.709] Command failed with exit code 18: docker compose --project-directory /tmp/build-sources/repo-name/clff74xxd003a9alt4oq436vo -f /tmp/build-sources/repo-name/clff74xxd003a9alt4oq436vo/docker/stg.yml pull
worker Pulling
api Pulling
api Error
time="2023-03-19T09:29:33Z" level=warning msg="commandConn.CloseWrite: commandconn: failed to wait: signal: killed"
worker Error
Error response from daemon: Head "https://ghcr.io/v2/user-name/package-name/manifests/staging": unauthorized
[12:29:33.712] Command failed with exit code 18: docker compose --project-directory /tmp/build-sources/repo-name/clff74xxd003a9alt4oq436vo -f /tmp/build-sources/repo-name/clff74xxd003a9alt4oq436vo/docker/stg.yml pull
worker Pulling
api Pulling
api Error
time="2023-03-19T09:29:33Z" level=warning msg="commandConn.CloseWrite: commandconn: failed to wait: signal: killed"
worker Error
Error response from daemon: Head "https://ghcr.io/v2/user-name/package-name/manifests/staging": unauthorized

Steps To Reproduce

Create an app
Use github
Choose docker compose
Deploy

Version
3.12.28

Same issue for me, but when get the error when pulling images from ghrc.io. Token is generated and working with github cli etc.

Is this still an issue?


Backend AlarmMuteRequest KeyError exception

Backend prints an exception for AlarmMuteRequest:

The cause is unclear
frontend seems to have no side effects from this exception

Steps to reproduce:

random

This issue was split off from #386 comment
exception log:
021-06-10 14:35:32,522 ventserver.integration._trio INFO     Initializing from file: ParametersRequest
2021-06-10 14:35:32,524 ventserver.integration._trio INFO     Initializing from file: AlarmLimitsRequest
2021-06-10 14:35:32,527 ventserver.integration._trio INFO     Initializing from file: AlarmMuteRequest
2021-06-10 14:35:32,530 ventserver.integration._trio INFO     Initializing from file: SystemSettingRequest
2021-06-10 14:35:32,537 ventserver.protocols.devices.file.ReceiveFilter ERROR    MessageSender:
Traceback (most recent call last):
  File "/home/pi/pufferfish-software/backend/ventserver/protocols/transport/messages.py", line 65, in parse
    self.payload = message_object.parse(body_payload)
  File "/home/pi/.pyenv/versions/3.7.7/envs/ventserver/lib/python3.7/site-packages/betterproto/__init__.py", line 760, in parse
    parsed.wire_type, meta, field, parsed.value
  File "/home/pi/.pyenv/versions/3.7.7/envs/ventserver/lib/python3.7/site-packages/betterproto/__init__.py", line 701, in _postprocess_single
    fmt = _pack_fmt(meta.proto_type)
  File "/home/pi/.pyenv/versions/3.7.7/envs/ventserver/lib/python3.7/site-packages/betterproto/__init__.py", line 288, in _pack_fmt
    }[proto_type]
KeyError: 'uint64'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/pi/pufferfish-software/backend/ventserver/protocols/devices/file.py", line 90, in output
    message = self._message_receiver.output()
  File "/home/pi/pufferfish-software/backend/ventserver/protocols/transport/messages.py", line 118, in output
    message.parse(body, self.message_classes)
  File "/home/pi/pufferfish-software/backend/ventserver/protocols/transport/messages.py", line 70, in parse
    ) from exc
ventserver.protocols.exceptions.ProtocolDataError: Unparseable payload: b'\x15\x00\x00\xf0B'
2021-06-10 14:35:32,539 ventserver.protocols.backend.server.ReceiveFilter ERROR    The state type NoneType data in the file does not match the filename AlarmMuteRequest.

We've been unable to reproduce this, so I'll close it; we can reopen it if we see similar problems in the future.


Bug: CORS Filter issue

PHP Version
7.4
CodeIgniter4 Version
4.2.1
CodeIgniter4 Installation Method
Manual (zip or tar.gz)
Which operating systems have you tested for this bug?
macOS
Which server did you use?
apache
Database
Mariadb
What happened?
Set a Cors filter in $globals before filter
It was working before but filter doesn't runs work the new version of CI
Doesn't work even setting $multipleFilters and/or $autoRoutesImproved on true.
Only works when set "not recommended" $routes->setAutoRoute(true); in Routes.php
Steps to Reproduce
Set filter as below
public function before(RequestInterface $request, $arguments = null) {
        $response = service('response');

        // allow origin
        $response->setHeader('Access-Control-Allow-Origin', '*');

        // allow headers
        $response->setHeader('Access-Control-Allow-Headers', [
            'Authorization',
            'Content-Type',
            'X-Api-Key',
            'X-Requested-With',
        ]);

        // allow methods
        $response->setHeader('Access-Control-Allow-Methods', [
            'OPTIONS',
            'GET',
            'POST',
            'PUT',
            'DELETE',
        ]);

        $response->setHeader('Access-Control-Allow-Credentials', 'true');
        $response->setHeader('Access-Control-Max-Age', '3600');

        if ($request->getMethod() === 'options') {
            $response->send();

            exit();
        }
}

Expected Output
Doesn't show Cors error when call Api
Anything else?
No response

Set a Cors filter in $globals before filter

How did you set? Can you show us exact code?

It was working before but filter doesn't runs work the new version of CI

What did you get? Error message?
And the page can be accessible from the same origin?

It seems your CORS filter is broken.
$response->setHeader('Access-Control-Allow-Origin', '*');
$response->setHeader('Access-Control-Allow-Credentials', 'true');

How did you set? Can you show us exact code?

I set the filter as below
/**
 * Configures aliases for Filter classes to
 * make reading things nicer and simpler.
 *
 * @var array
 */
public $aliases = [
    'csrf'          => CSRF::class,
    'toolbar'       => DebugToolbar::class,
    'honeypot'      => Honeypot::class,
    'invalidchars'  => InvalidChars::class,
    'secureheaders' => SecureHeaders::class,
    'cors'          => Cors::class,
];

/**
 * List of filter aliases that are always
 * applied before and after every request.
 *
 * @var array
 */
public $globals = [
    'before' => [
        // 'honeypot',
        // 'csrf',
        // 'invalidchars',
        'cors',
    ],
    'after' => [
        // 'toolbar',
        // 'honeypot',
        // 'secureheaders',
    ],
];

What did you get? Error message?

I have a Cors policy error message as following attaching file

And the page can be accessible from the same origin?

Yes i can, the problem looks to be than CI doesn't run the filter

It seems your CORS filter is broken.

I am sorry i don't get where the CORS filter is broken?

Don't use exit()

if ($request->getMethod() === 'options') {
-   $response->send();

-    exit();
+   return $response;
}

You must have a route for the HTTP OPTIONS method.

I am sorry i don't get where the CORS filter is broken?

Basically you should not use *:
$response->setHeader('Access-Control-Allow-Origin', '*');

You should set your site. Because * means you allow access from anywhere.
 It is like just disabling CORS protection.
And credential is not supported if the CORS header Access-Control-Allow-Origin is *.
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials
Because it is too dangerous.
I recommend you learn what CORS is.
See https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

As iRedds say, it seems you did not define a route for the HTTP OPTIONS method.

@kenjis

Basically you should not use $response->setHeader('Access-Control-Allow-Origin', '*');

Oh i get it, i put that for my tests but you are right, i shouldn't allow all origins.
@iRedds

You must have a route for the HTTP OPTIONS method.

After adding a route for the OPTIONS method it works properly, thank you very much.

Don't use exit()

I've removed that part, thanks for your help

I have the same problem. What would it be "You must have a route for the HTTP OPTIONS method."?

It means HTTP verb OPTIONS.
See https://codeigniter4.github.io/CodeIgniter4/incoming/routing.html#setting-routing-rules

Thank You!
Would it add this?
$routes->options('(:any)', '', ['filter' => 'cors']);

If the filter returns correct responses, yes.
See https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS


For using jquery autocomplete plugin with some json editor

Is there a way to add css class or id attribute to a some of the input fields
for example : Apply a css class to the field with title person.
{
"title":"config",
"type":"object",
"properties":{
"person":{
"title":"person",
"type":"string"},
"age":{
"title":"age",
"type":"number"}
}
}

This repo is no longer maintained (see also https://github.com/jdorn/json-editor/issues/800)
Development is continued at https://github.com/json-editor/json-editor
For details please visit https://github.com/json-editor/json-editor/issues/5

Also have a look at the issues, we had something similar I think.


Feeds in .csv (also .txt) are not reachable through the URL api/feeds/all/all/recent.csv

Hello,
In new installed greedybear trying to get feeds in csv or txt format and get the error- Object of type StreamingHttpResponse is not JSON serializable
For testing, tried to get https://greedybear.honeynet.org/api/feeds/all/all/recent.csv, received SERVER ERROR (500). I believe with DEBUG=True the output will be the same- Object of type StreamingHttpResponse is not JSON serializable

hey, thanks for reporting. I'll check this out

meanwhile use the .json format that works properly

I fixed the problem, will be released in few days in a new patch release


New version of Evernote is unsupported

Since about 2 days ago, when I start Whatever, I get a message saying:
"Sorry, we don't support your browser at this moment...."

The only workaround for this issue is to either open Evernote Web in a regular Chrome tab, or download their app if your OS is supported (Linux isn't). Any ideas if/when this might be fixed?
Thanks in advance,
L

@cellardoor42, any progress on this? Don't we just need to update the version of Electron?


Mybatis defind a generic sql provider?

I defind a generic sql provider,but I can't set generic type in the mapper?
the mapper likes:
@InsertProvider(type = BaseSQLProvider<Entity>.class, method = "insertSQL")

Java does not allow that syntax, I think.


Custom Extension doesn't show up in VerifiableGroupInfo.extensions() object

I have created a custom GroupContext extension to store some application specific data. I noticed while building out the welcome flow that the extension isn't present in the VerifiableGroupInfo.extensions() response. Which comes back with just the ratchet tree extension.
I'm not sure if this is the expected behavior or not. I would have expected to get a list of all extensions for the group in the welcome objects so that I can inspect (and ultimately show the user) some of that context before they decide to join the group. There doesn't seem to be another easy way to get to the group_context directly via the ProcessedWelcome or StagedWelcome structs given the group_context is a private prop.
 The missing piece here seems to be access to the GroupContext s.t. you can get access to the GroupContext extensions. There really should be a getter for the GroupContext for the StagedWelcome. Do you want to create a PR for that?

Happy to. Thanks!

@kkohbrok https://github.com/openmls/openmls/pull/1666

@erskingardner should #1666 close this?

Yes! Thanks for the reminder


AppState feature request: better logs

When doing this:
  AppState.set('doc', {
    tentative: { docId: docId, queryParams: {} },
    actual   : null
  });

...I get this in the console:
"doc" => Object {tentative: Object, actual: null}
"doc.tentative" => Object {docId: "9c6HBqLtHLpWd6zND", queryParams: Object}
"doc.tentative.docId" => 9c6HBqLtHLpWd6zND
"doc.tentative.docId.queryParams" => Object {}
"doc.tentative.docId.queryParams.actual" => null

IMO, this is too verbose. Two lines would be enough, like this:
State change: "doc" =>
► Object {tentative: Object, actual: null}

and you let users open and browse the Object content in the console if they want to.
(you need two lines because you need a separate console.log to benefit from the browser ► feature).

Problem with your solution is that "doc" may contain objects which didn't change, so a new log is added for each invalidation.
"doc.tentative.docId.queryParams" is a bug, it should say "doc.tentative.queryParams".
Anyway, update to v1.1.0 to get rid of that console log. Once I add hooks to the AppState we can have a proper debug package.

I will keep track of this in #6


direct message

Hi
Is there anyway to create chat with user in inline keyboard (user has not username)
like telegram.me/userid

Dear sinaprog,
Please close the issue (since it's not caused by the library) and contact https://telegram.me/BotSupport, they will probably be able to help you with your challenge.
Kind regards,
Martijn Verbakel


MG Review - Confusion Matrix Module

The confusion matrix is a good way to analyze the results of your model ✅, however, there are many other metrics that are used and provided for free by sci-kit learn.
Perhaps it's worth changing this module to be more abstract, like Metrics Module? Or something that provides a confusion matrix, but also any other metrics you may want at some point (f1 score, accuracy, averaging over the classes - different ways to compute a lot of stuff lol).

Addressed in Commit 6dc32ba


Add a check for invalid property names

Scope is a property name that is not allowed/working. But all cmdlets in this module let me use it, took me some hours to find out why my new resource was not loaded.

I think https://twitter.com/craigmartineh hit the same problem.


python311Packages.bqscales: fix build

Description of changes
https://hydra.nixos.org/build/241872101

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 269227 at e9fda01c run on x86_64-linux 1

4 packages built successfully:

python310Packages.bqplot
python310Packages.bqscales
python311Packages.bqplot
python311Packages.bqscales


added definitions for Mongo metrics

Relevant information
Describe what you have done and any details that you think are relevant or that you might want to discuss with us.
Checklist

[x] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[x] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

hi @kfalconer ! can you give us a bit more context on this?
This PR will create the types but how is the data going to be created & managed

I am not sure I understand the question. Do you mean source of the metrics? This is the coming from the nri-mongo integration.
I followed the same pattern as the other Infrastructure based integrations by defining the types. But it wasn't clear on the examples how the data is actually synthesized since there was no examples of that.

@kfalconer I see what you mean.
Let me run down this on the teams providing this integrations.
The thing is that Infra entities go to a different pipeline and they don't use synthesis (yet) so manual work needs to be done in order to create such entities.
In the future these will go through synthesis and the process of creating entities will be simpler

@kfalconer bringing more info from the team!
The work to bring these entities into the platform is already prioritized on the team backlog.
So i'll close this PR and let them do the required work and create the types.
Thanks a lot for your contribution!

Thanks for the update


fix(server): :bug: add bundled flag to rusqlite dependency on musl-libc

fix(server): :bug: add bundled flag to rusqlite dependency on musl-libc target

fixes #228
the musl libc is used on Alpine, a minimal linux distribution commonly
used in docker images. It's also used on OpenWRT which might be of
interest to innernet.

Seems reasonable to me, especially since it only affects the musl target.

I imagine this same problem exists, and we should be consistent for both binaries. I'll merge this, and then add a commit that also does this for the client and refers to rusqlite's GitHub issue for reference.
Thanks!


Example's bug for array parameter

The example should be --days "Sunday" "Monday" instead of --days "Sunday" --days "Monday"

fixed in latest private release


Update Expr::CompoundIdentifier to have more accurate data format

Currently, the format of Expr::CompoundIdentifier(Vec<String>) is a superset of what GlueSQL execution can handle it.
Only single pair of (table_alias, column_name) can exist, so the current shape Vec<String> is too broad.
We can consider to change the type of Expr::CompoundIdentifier to have more narrow info.
e.g.
Expr::AliasedIdentifier {
  alias: String,
  ident: String,
}

It would be nice that we can dicuss about this. @ever0de @devgony

I agree. We discussed it verbally, but I was also thinking about it, and it seems to be the right way to go in the direction you wrote.


feat: add support for ravencoin

Hi, this PR adds support for ravencoin and lays the basis for other kawpow coins.
The code was tested on the ravencoin testnet.
[2023-02-14 22:57:54.7180] [I] [rvn1] Submitting block 936632 [00000003ca6b9e3312aa952d952a757705fe88e807b43b2f4cfa8a798d4da9ba]
[2023-02-14 22:57:54.7426] [I] [rvn1] Daemon accepted block 936632 [00000003ca6b9e3312aa952d952a757705fe88e807b43b2f4cfa8a798d4da9ba] submitted by mu3CRvK5eMB3JiiNmQUwu2JLubobuhdfdb
[2023-02-14 22:57:54.7441] [I] [rvn1] [0HMOEQPKV1L0Q] Share accepted: D=0.02
[2023-02-14 22:57:54.7517] [I] [rvn1] Detected new block 936633 [BLOCK]
[2023-02-14 22:57:54.7517] [I] [rvn1] Broadcasting jobs
[2023-02-14 22:57:56.7884] [I] [rvn1] [0HMOEQPKV1L0Q] Share accepted: D=0.02
[2023-02-14 22:58:04.2436] [I] [rvn1] [0HMOEQPKV1L0Q] Share accepted: D=0.02
[2023-02-14 22:58:04.7487] [I] [rvn1] Broadcasting jobs

Even though ravencoin is a fork of bitcoin, it has a different stratum protocol. This is why I added it as a custom family which extends the BitcoinJob and BitcoinJobManagerBase classes.
Payouts are handled by the BitcoinPayoutHandler without any modifications.
rel:
https://github.com/oliverw/miningcore/issues/1174
https://github.com/oliverw/miningcore/discussions/876

Nice :)
I was planning to give Kawpow a try but it looks like, you beat me to it :)

I would like to try raven coin. Is this merged into miningcore or do I need to submit a request from jon4hz?

no, this isn't merged yet. Hence the PR..

Cool. Hopefully oliverw will merge the pr soon. If I clone your repo will
it work? If I checkout the branch ravencoin?
On Wed, Feb 22, 2023, 7:05 PM jon4hz @.***> wrote:

no, this isn't merged yet. Hence the PR..
—
Reply to this email directly, view it on GitHub
https://github.com/oliverw/miningcore/pull/1627#issuecomment-1441026231,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIAKRQHBKXZEEFDLTXHZK3WY2SURANCNFSM6AAAAAAU4DJW24
.
You are receiving this because you commented.Message ID:
@.***>

Probably, yes

Tested this project conditionally working there are many inaccuracies such as diff target
correctgey will be
    public static BigInteger BigMaxValue = BigInteger.Pow(2, 256);
    public static readonly BigInteger Diff1 = BigInteger.Parse("00000000ffff0000000000000000000000000000000000000000000000000000", NumberStyles.HexNumber);
    public static double Mul = (double) BigInteger.Divide(BigMaxValue, Diff1);

 var shareDiff = (double) BigInteger.Divide(RavencoinConstants.BigMaxValue, resultValueBig) / RavencoinConstants.Mul;
    public static string EncodeTarget(double difficulty)
    {

        BigInteger BaseTarget = BigInteger.Parse("00000000ffff0000000000000000000000000000000000000000000000000000", System.Globalization.NumberStyles.AllowHexSpecifier, null);

        difficulty = 1.0 / difficulty;

        BigInteger NewTarget;
        BigInteger DecimalDiff;
        BigInteger DecimalTarget;

        NewTarget = BigInteger.Multiply(BaseTarget, new BigInteger(difficulty));

        string StringDiff = difficulty.ToString(System.Globalization.CultureInfo.InvariantCulture);
        int DecimalOffset = StringDiff.IndexOf(".");
        if(DecimalOffset > -1)
        {
            int Precision = (StringDiff.Length - 1) - DecimalOffset;
            DecimalDiff = BigInteger.Parse(StringDiff.Substring(DecimalOffset + 1));
            DecimalTarget = BigInteger.Multiply(BaseTarget, DecimalDiff);

            string s = DecimalTarget.ToString();
            s = s.Substring(0, s.Length - Precision);

            DecimalTarget = BigInteger.Parse(s);
            NewTarget += DecimalTarget;
        }

        return string.Format("{0:x64}", NewTarget);
    }

and OnSubscribeAsync
        manager.PrepareWorker(connection);

        var data = new object[]
        {
           null,
           context.ExtraNonce1,
        }
        .ToArray();

    public void PrepareWorker(StratumConnection client)
    {
        var context = client.ContextAs<RavencoinWorkerContext>();
        context.ExtraNonce1 = extraNonceProvider.Next();
    }

I didn’t check the block on the test network, I didn’t catch the payout yet, but I’m going to do it and write it.

Hi @Konstantin35
Thanks a lot for taking a look at this!
Good hint with the target encoding. I was actually quite unsure if I handled that correctly but I kinda forgot about it since the code seemed to work. (It actually does work but I think I'm loosing some precision down the line.)
I ported the share validation from blinkhash's foundation pool and I never heard that they do it wrong.
https://github.com/blinkhash/foundation-v2-ravencoin/blob/4ed8f799ff6594926c48509c8f3292886d660932/stratum/main/manager.js#L167
What makes you think that Diff1 should be "00000000ffff0000000000000000000000000000000000000000000000000000"?
As for the subscribe params: wildrig accepts both variants. Is there a particular reason to only send the null + extraNonce1?

RavenPool.cs messageBus.SendMessage(share); needs to be changed to messageBus.SendMessage(new StratumShare(connection, share)); to correctly record data in to DB.

No it does not.
https://github.com/oliverw/miningcore/commit/683d8dce97fcca522daab5544e209f83fead65fa

Ok, for me it did need that change, and that is how its done for other Blockchains.
On another note to display the algo on the site I also needed to add, otherwise it would use the headerhasher algo:
        KawpowHasher = new EthashLight();
    }
    #region Overrides of CoinTemplate

    public override string GetAlgorithmName()
    {
        return "KAWPOW";
    }

    #endregion

in ClusterConfigExtensions.cs

No it does not. d3dcec6

Stand corrected, not sure if its because of old base for me, but I also needed to add:
`    {
KawpowHasher = new EthashLight();
}
#region Overrides of CoinTemplate
public override string GetAlgorithmName()
{
    return "KAWPOW";
}

#endregion`
to clusterconfigextension so it would not use the headerhasher as displayed algo.

As for the subscribe params: wildrig accepts both variants. Is there a particular reason to only send null + extraNonce1?

https://github.com/nicehash/Specifications/blob/master/KawPow_NiceHash_v1.0.txt

When testing the same problem as Ethash: Abstract and light cache jumping pings on Ethash tested with dag generation there is a stable ping difference with my pool of 1ms it turns out that with dag is much better. If you use light cache then you also need to generate cache files and test them.

When testing the same problem as Ethash: Abstract and light cache jumping pings on Ethash tested with dag generation there is a stable ping difference with my pool of 1ms it turns out that with dag is much better.

I'm no expert on ethash by all means but I think the performance difference can be explained, because the light cache has to calculate the required dag sequences on the fly, where as the dag has them already precalculated.
See: https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms/ethash/

Mining involves grabbing random slices of the dataset and hashing them together. Verification can be done with low memory by using the cache to regenerate the specific pieces of the dataset that you need, so you only need to store the cache.

How big was the performance difference in your experience? If it's only a ms I dare to say the advantage of being able to scale overwhelms the disadvantages. But yeah, that all depends on how big the difference is.

If you use light cache then you also need to generate cache files and test them.

I though that was already handled by the c++ code but I'll take another look.

Hello. I try kawpow algo on hivecoin. Have error with block submission: submission failed with: bad-cb-community-autonomous-amount
To coins.json i add "payFoundersReward": true,
Maybe we need to add something else. Or is the support for kawpow not finished yet?
Thanks.

Hello. I try kawpow algo on hivecoin. Have error with block submission: submission failed with: bad-cb-community-autonomous-amount To coins.json i add "payFoundersReward": true, Maybe we need to add something else. Or is the support for kawpow not finished yet? Thanks.

You need to add support for "CommunityAutonomousAddress" and "CommunityAutonomousValue" as those are different to founder/payee/masternode/minerfund. Check the minerfund commit and follow that. Pretty easy to add.

Hello. I try kawpow algo on hivecoin. Have error with block submission: submission failed with: bad-cb-community-autonomous-amount To coins.json i add "payFoundersReward": true, Maybe we need to add something else. Or is the support for kawpow not finished yet? Thanks.

You need to add support for "CommunityAutonomousAddress" and "CommunityAutonomousValue" as those are different to founder/payee/masternode/minerfund. Check the minerfund commit and follow that. Pretty easy to add.
I did lazy way and just added to getblocktemplate. Was going to do it properly with its own file and submit a pull request to jon4hz, but got distracted In bitcoinjob:
        if (coin.HasCommunityAddress)
            rewardToPool = CreateCommunityAddressOutputs(tx, rewardToPool);

    #region CommunityAddress

    protected virtual Money CreateCommunityAddressOutputs(Transaction tx, Money reward)
    {
        if(BlockTemplate.CommunityAutonomousAddress != null && BlockTemplate.CommunityAutonomousValue > 0)
        {
        var payeeReward = BlockTemplate.CommunityAutonomousValue;
        reward -= payeeReward;
        var payeeAddress = BitcoinUtils.AddressToDestination(BlockTemplate.CommunityAutonomousAddress, network);
        tx.Outputs.Add(payeeReward, payeeAddress);
        }
        return reward;
    }
    #endregion // CommunityAddress

in getblocktemplate
        [JsonProperty(DefaultValueHandling = DefaultValueHandling.Ignore)]
        public string CommunityAutonomousAddress { get; set; }
        [JsonProperty(DefaultValueHandling = DefaultValueHandling.Ignore)]
        public long CommunityAutonomousValue { get; set; }

in clusterconfig
    [JsonProperty(DefaultValueHandling = DefaultValueHandling.Ignore)]
    public bool HasCommunityAddress { get; set; }

I think didn't miss anything, but might have.

I add all this code, recompile. But submission failed again.

did you also add "hasCommunityAddress": true in to the coins.json for the coin?

did you also add "hasCommunityAddress": true in to the coins.json for the coin?

No. just add code. Thank you, now try add to coins.json

Find new issue. Payments work, but there are no records in the database about payments made. No records in "payments" in db.

Are you using the same wallet for the pool fee and mining?

Yes 1 wallet for fee and mining. Now try change wallet

Miningcore doesn't store payments sent to the fee wallet. You'll have to use a different wallet for mining if you want to test payouts.

Miningcore doesn't store payments sent to the fee wallet. You'll have to use a different wallet for mining if you want to test payouts.

Thank you. Understand. Now change wallet

Have new problem :)
On Paprikacon wrong block reward. On cryptonote pool right reward 36 coin.
On miningcore reward 12 coins.
Think miningcore set wrong CommunityReward.
In code set % reward? or miningcore give info from network?

Have new problem :) On Paprikacon wrong block reward. On cryptonote pool right reward 36 coin. On miningcore reward 12 coins. Think miningcore set wrong CommunityReward. In code set % reward? or miningcore take info from network?

Getting OT on kawpow, but paprikacoin has incorrect coinbase on getblocktemplate, I submitted a pull request to fix it. In the meanwhile, check the pull request in paprikacoin git and apply it and build from source.

@papagruz This PR is about ravencoin and not some random other coin. Please keep this thread on topic and open another issue if you have issues with paprikacoin...

Ok. Thanks

I tested with nicehash on Paprikacoin, it seems to have banned continuously. No shares were sent even though Nicehash is still running!

Read the comments! This PR is for Ravencoin. Not other coins based on kawpow. Open a new discussion for the coin you are trying to work with

Sorry i'm a little bit late to the party.
I tried to mine RVN testnet using that PR, and both T-Rex Miner and SRBMiner-Multi are sending this method to the pool:
[2023-06-06 04:14:36.6697] [D] [rvn1] [0HMR68ARULC2F] [NET] Received data: {"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x00000000000000000000000000000000000000000000000000000000002c80d8", "0xd0cadda1c061988bd7a4b83d3ca08fb04d6c4dad4c4ddd6bbdb12e89662ea60d"],"id":7}

Command lines for both miners:
/home/ceedii/SRBMiner-Multi-2-2-8/SRBMiner-MULTI --api-enable --api-port 4448 --api-rig-name ganymede --algorithm kawpow --pool stratum+ssl://callisto.cedric-crispin.com:4055 --wallet mzASNqJJPTKcASFcFjNiA1j4jYxD5VFZee.ganymede --password x --gpu-id GPU0 --disable-cpu

/home/ceedii/t-rex-0.26.8-linux/t-rex -a kawpow -o stratum+ssl://callisto.cedric-crispin.com:4055 -u mzASNqJJPTKcASFcFjNiA1j4jYxD5VFZee.ganymede -p x --no-strict-ssl -d 0 --api-bind-http <IP_ADDRESS>:4448 --no-watchdog

Am i the only one having that issue?

@blackmennewstyle that isn't an issue, just the miner reporting its hashrate to the pool. Miningcore doesn't support that though, so the message gets ignored.

Hi, sorry for the confusion i wanted to write behavior not issue, another brain glitch i guess. Everything is working fine, i had to decrease my minDiff though because my GPU for testing isn't really great at KAWPOW lol
Nice job mate :+1:

Have anyone managed to successfully catch a block on  Ravencoin mainnet?

Yes. How long have you been mining and what is your hashrate on the pool?
On Mon, Jun 26, 2023 at 1:42 AM Cédric CRISPIN @.***>
wrote:

Have anyone managed to successfully catch a block on Ravencoin mainnet?
—
Reply to this email directly, view it on GitHub
https://github.com/oliverw/miningcore/pull/1627#issuecomment-1606689984,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIAKRUSN4WWHD2O4EK5GLTXNEONRANCNFSM6AAAAAAU4DJW24
.
You are receiving this because you commented.Message ID:
@.***>

--
Randy Hasson
199 East Markison Avenue
Columbus, Ohio 43207

Yes. How long have you been mining and what is your hashrate on the pool?
On Mon, Jun 26, 2023 at 1:42 AM Cédric CRISPIN @.> wrote: Have anyone managed to successfully catch a block on Ravencoin mainnet? — Reply to this email directly, view it on GitHub <#1627 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIAKRUSN4WWHD2O4EK5GLTXNEONRANCNFSM6AAAAAAU4DJW24 . You are receiving this because you commented.Message ID: @.>
-- Randy Hasson 199 East Markison Avenue Columbus, Ohio 43207

Almost 4 days with just 130 MH/s lol
Did you implement @Konstantin35 suggestions with the target encoding and also the shareDiff calculation?

With 130 mh/s it will take weeks if not months to find a block
On Mon, Jun 26, 2023 at 10:26 AM Cédric CRISPIN @.***>
wrote:

Yes. How long have you been mining and what is your hashrate on the pool?
On Mon, Jun 26, 2023 at 1:42 AM Cédric CRISPIN @.> wrote: Have anyone
managed to successfully catch a block on Ravencoin mainnet? — Reply to this
email directly, view it on GitHub <#1627 (comment)
https://github.com/oliverw/miningcore/pull/1627#issuecomment-1606689984>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIAKRUSN4WWHD2O4EK5GLTXNEONRANCNFSM6AAAAAAU4DJW24
https://github.com/notifications/unsubscribe-auth/AAIAKRUSN4WWHD2O4EK5GLTXNEONRANCNFSM6AAAAAAU4DJW24
. You are receiving this because you commented.Message ID: @.>
-- Randy Hasson 199 East Markison Avenue Columbus, Ohio 43207
https://www.google.com/maps/search/199+East+Markison+Avenue+Columbus,+Ohio+43207?entry=gmail&source=g
Almost 4 days with just 130 MH/s lol
Did you implement @Konstantin35 https://github.com/Konstantin35
suggestions with the target encoding and also the shareDiff calculation?
—
Reply to this email directly, view it on GitHub
https://github.com/oliverw/miningcore/pull/1627#issuecomment-1607606046,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIAKRWKRVYN5RZF3OBLUMTXNGLY5ANCNFSM6AAAAAAU4DJW24
.
You are receiving this because you commented.Message ID:
@.***>

--
Randy Hasson
199 East Markison Avenue
Columbus, Ohio 43207

I implemented what is suggested here https://github.com/oliverw/miningcore/pull/1627#issuecomment-1441639530
After restart, all my low difficulty rejected shares are gone. That GPUs rig was mining on flypool before and it never got the amount of rejected shares i was seeing, maximum one per 24h.
[2023-06-27 02:22:24] Stats Uptime: 0 days, 09:22:09
[2023-06-27 02:22:24] ----------------------------------------- GPU Status -------------------------------------------
[2023-06-27 02:22:24] GPU  0 [57C, fan 76%]      kawpow: 16.76Mh/s, avg 16.66Mh/s, pool 16.85Mh/s a:414 r:0 hw:0
[2023-06-27 02:22:24] GPU  1 [59C, fan 80%]      kawpow: 16.76Mh/s, avg 16.66Mh/s, pool 15.52Mh/s a:385 r:0 hw:0
[2023-06-27 02:22:24] GPU  2 [59C, fan 78%]      kawpow: 16.78Mh/s, avg 16.68Mh/s, pool 15.68Mh/s a:387 r:0 hw:0
[2023-06-27 02:22:24] GPU  3 [59C, fan 78%]      kawpow: 16.62Mh/s, avg 16.51Mh/s, pool 17.30Mh/s a:421 r:0 hw:0
[2023-06-27 02:22:24] GPU  4 [49C, fan 68%]      kawpow: 16.77Mh/s, avg 16.67Mh/s, pool 16.90Mh/s a:407 r:0 hw:0
[2023-06-27 02:22:24] GPU  5 [59C, fan 78%]      kawpow: 16.76Mh/s, avg 16.66Mh/s, pool 16.26Mh/s a:405 r:0 hw:0
[2023-06-27 02:22:24] Total                      kawpow: 100.5Mh/s, avg 99.84Mh/s, pool 98.51Mh/s a:2419 r:0
[2023-06-27 02:22:24] ----------------------------------------- Pool Status ------------------------------------------
[2023-06-27 02:22:24] stratum.cedric-crispin.com kawpow: 96.59Mh/s, avg 97.84Mh/s, pool 98.51Mh/s a:2419 r:0
[2023-06-27 02:22:24] ------------------------------------------------------------------------------------------------

using System.Globalization;
using System.Numerics;
using Miningcore.Util;

namespace Miningcore.Blockchain.Ravencoin;

public class RavencoinConstants
{
    public const int EpochLength = 7500;
    public static BigInteger BigMaxValue = BigInteger.Pow(2, 256);
    public static readonly BigInteger Diff1B = BigInteger.Parse("00000000ff000000000000000000000000000000000000000000000000000000", NumberStyles.AllowHexSpecifier, null);
    public static readonly BigInteger Diff1 = BigInteger.Parse("00000000ff000000000000000000000000000000000000000000000000000000", NumberStyles.HexNumber);
    public const int ExtranoncePlaceHolderLength = 2;
    public static double Multiplier = (double) new BigRational(BigMaxValue, Diff1);
}

using System.Globalization;
using System.Numerics;

namespace Miningcore.Blockchain.Ravencoin;

public static class RavencoinUtils
{
    public static string RavencoinEncodeTarget(double difficulty)
    {
        difficulty = 1.0 / difficulty;

        BigInteger NewTarget;
        BigInteger DecimalDiff;
        BigInteger DecimalTarget;

        NewTarget = BigInteger.Multiply(RavencoinConstants.Diff1B, new BigInteger(difficulty));

        string StringDiff = difficulty.ToString(CultureInfo.InvariantCulture);
        int DecimalOffset = StringDiff.IndexOf(".");
        if(DecimalOffset > -1)
        {
            int Precision = (StringDiff.Length - 1) - DecimalOffset;
            DecimalDiff = BigInteger.Parse(StringDiff.Substring(DecimalOffset + 1));
            DecimalTarget = BigInteger.Multiply(RavencoinConstants.Diff1B, DecimalDiff);

            string s = DecimalTarget.ToString();
            s = s.Substring(0, s.Length - Precision);

            DecimalTarget = BigInteger.Parse(s);
            NewTarget += DecimalTarget;
        }

        return string.Format("{0:x64}", NewTarget);
    }
}

I use Ravencoin diff 00000000ff000000000000000000000000000000000000000000000000000000 instead of 00000000ffff0000000000000000000000000000000000000000000000000000, the later is FIRO diff if i am not mistaken.


Copy-Paste from excel error

Whenever I copy-paste from excel more that one row, whether we are talking about changes or additions, I receive one extra change/addition with value "" in the onCellsChanged handler (on a row that doesn't have changes/additions).
Should be easy to reproduce.
In the example below I have 3 rows with OOB rendering, simple text as follows:

1 2 3 on first row
4 5 6 on second row
7 8 9 on last row

I then paste from excel two rows as follows:

a b on first row
c d on second row

Unexpected behavior: first cell on last row, that previously had 7 in it, is cleared.

Seems like excel is pasting data oddly. You might wanna use the parsePaste to remove any odd delimiters:
https://github.com/nadbm/react-datasheet#options

Ok, will do, thanks.
Since it was the default parsePaste method being used, I thought you might want to include a fix in the next release.


Possible bug (wrong sign) in BTRS algorithm for binomial sampling?

This is a very esoteric issue: I was reading the BTRS paper and trying to understand the algorithm by reading the TF implementation, and I think I found a bug on line 99, in the Stirling approximation for log(k!):
return (1.0 / 12 - (1.0 / 360 + 1.0 / 1260 / kp1sq) / kp1sq) / (k + 1);

If I'm reading the paper correctly, the sign on the third term is wrong, because it should be positive in the final sum (see page 106-106 of Hörmann et al):
return (1.0 / 12 - (1.0 / 360 - 1.0 / 1260 / kp1sq) / kp1sq) / (k + 1);

Or maybe there's an error in the paper? Anyway just thought I'd mention it.

@jamestwebber  It appears you are correct. I verified the equation from the original paper which can found here: https://epub.wu.ac.at/1242/1/document.pdf (Page 7)
I am sending a PR request now.

This is merged and will be updated on the site the next docs push/release.
Thank you, all


NullReferenceException thrown on invalid model state on Admin/Activity/Edit

If you post with bad data to the Admin/Activity/Edit page a NullReferenceException is thrown.
Here is what I think is happening:
On submission of an edit, the Activity object is populated by the ModelBinder and not read from the DB.  As a result it's Campaign property is not filled in.
On success, ActivityAdminController.Edit redirects to admin's list of activities, so this doesn't matter.
But on failure - when, e.g., the user just enters no date at all - the edit view is redisplayed; this view displays Campaign.Name and as activity.Campaign is null the exception is thrown.

Oh, and I'm happy to take this on if people think my assessment above sounds accurate enough.

Correct, the Campaign property should be repopulated when the model state is invalid. The Create method does this properly but the Edit method does not. Feel free to submit a PR.

I just pushed this, for the interim fix.  It's attached itself to the already open PR, as I didn't use a separate branch - sorry about that.

For review: https://github.com/ksk100/allReady/commit/a878fb139c0dfba2be9d82797b64b4281141ca5b

@ksk100 Can you add "Closes #120 and closes #122" as a comment to PR #123 . That will ensure these issues are autoclosed when the PR is merged.

Of course

this can be closed


Introduce a prototype program registry

Motivation
This PR introduces a prototype program registry where programs must be deployed before use. In it's current form, the deployed program is stored in the Execution struct.
How deployment transactions are constructed:

Create a program deployment Request that includes the program and it's corresponding function vks.
The Ledger checks that the program doesn't already exist in the registry.
Program is added to the registry when the block is mined. (Also included in the Execution struct of the deployment transaction).

There is no check for whether the vk associated with a program is valid, right?

Not at the moment, I have a TODO for that check. Was thinking to hold off on it, since we'll be storing the IRs down the line anyways.


net/http: also make Transport retry POST request if no bytes were written

We should retry non-idempotent HTTP requests (like POSTs) too if no bytes were ever written.
A fix for #15446 adds tracking of the number of bytes written. This makes this trivial to fix, but it's too late for Go 1.7.
Easy to switch early in Go 1.8. Could also use a few more tests.

See https://go-review.googlesource.com/#/c/23160/2


Error overlay does not work

The error overlay does not seem to appear, so far I haven't seen it any circumstance even when esbuild encounters an error. Is there any configuration that needs to be set for it to work?
I found that there's this package, but it seems that's only intended for using within esbuild-plugin-livereload.
Do you think there's something I'm doing wrong or could there be a bug that causes the error overlay not to appear?

Closing for now until more details are provided. Feel free to reopen.


cnt: use set_montage at the end of the init

This PR is part of #6461. The concrete goal here is to make sure that:
1 - RawCNT is always called with montage=None
2 - ensure self.set_montage(montage) is called at the end of init

I don't know of any CNT montage. You can just create one from scratch using the correct ch_names and np.random.randn(n_chs, 3) if you want.

thx @massich


Make priority queues totally ordered in debug mode

In #210 I realized that the tpie::priority_queue is not stable - i.e. when two elements are tied, then the oldest element is not necessarily output. It has just been a pure coincidence or due to the stability of merge sort, that I haven't noticed this in the first 700 unit tests.
We don't really care about this in production, as it does provide a slowdown and does not affect correctness of our algorithms. But, for our unit tests - since they are so strictly defining the order - we need the ordering to be total. If we didn't, then orderings will break, when we switch to other sorting algorithms and priority queue implementations, such as the ones mentioned in #98

Codecov Report

Merging #214 (238c2d7) into main (77fc303) will increase coverage by 0.024%.
The diff coverage is 100.000%.

@@              Coverage Diff              @@
##              main      #214       +/-   ##
=============================================
+ Coverage   96.698%   96.722%   +0.024%
=============================================
  Files           52        52
  Lines         2574      2593       +19
=============================================
+ Hits          2489      2508       +19
  Misses          85        85

Impacted Files
Coverage Δ

src/adiar/bdd/if_then_else.cpp
96.610% <100.000%> (+0.134%)
:arrow_up:

src/adiar/data.h
100.000% <100.000%> (ø)

src/adiar/internal/intercut.h
100.000% <100.000%> (ø)

src/adiar/internal/product_construction.h
100.000% <100.000%> (ø)

src/adiar/internal/quantify.h
100.000% <100.000%> (ø)

Continue to review full report at Codecov.

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


Undertand few code in iOS

Hi Team, Can you please let me know why the below line is used in AppDelegate+notification.m file,
[pushHandler.handlerObj setObject:safeHandler forKey:@"handler"];
I was facing problem with this line, when the status bar notifications will come, then it will be shown only for a while. After that in iPad device, if i go to notification center i am unable to see received status bar notifications. But after commenting the above line. I was able to see in the notification center as well
We also get below warning
Application delegate received call to -application:didReceiveRemoteNotification:fetchCompletionHandler: but the completion handler was never called.

@pallaviMN if you read the sections on Background notifications and Action Buttons you will see the importance of calling push.finish(). If you don't do that then you'll get the warning:
Application delegate received call to -application:didReceiveRemoteNotification:fetchCompletionHandler: but the completion handler was never called.


Feature/newregister

Linked updates to hawq register and hawq extract for functionality in 2.0.1.

Only the hawq register and hawq extract features actually in the current 2.0.1 code are included, plus some reorganization for added clarity.

@janebeckman - these changes look good, but I thought you were going to resubmit this PR against the develop branch.

I had thought I had closed this out and resubmitted against develop. Did
the one against master somehow not get closed?
Jane
On Wed, Oct 26, 2016 at 5:49 PM, David Yozie<EMAIL_ADDRESS>wrote:

@janebeckman https://github.com/janebeckman - these changes look good,
but I thought you were going to resubmit this PR against the develop branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-hawq-docs/pull/30#issuecomment-256517663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AN-v12-KpkBXoNi-MgDBJED2-nQ9gZrtks5q3_UPgaJpZM4Kbdiz
.


5 syncinfo update action

Summary

Adds method to update the syncinfo of an order
Fixes #5
Reviewers

[ ] Reviewer 1 has approved the PR
[ ] Reviewer 2 has approved the PR

TODO

Tests

[ ] Unit
[ ] Integration
[ ] Acceptance

[ ] Documentation

So is this ready for review? Asking since there is a in progress label attached.

Current coverage is 98.78% (diff: 100%)

Merging #6 into master will decrease coverage by 1.21%

@@           master         #6   diff @@
========================================
  Files           4          4
  Lines          67         82    +15
  Methods         0          0
  Messages        0          0
  Branches        0          0
========================================
+ Hits           67         81    +14
- Misses          0          1     +1
  Partials        0          0

Powered by Codecov. Last update e300488...3dc8c13

Yeah, it's ready for review
I moved the ticket on waffle and I assumed that this PR too will be updated but only the issue was Review status added too
Very strange 🤔


Publish 7.5-20220511195339+0000

Publish 7.5-20220511195339+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.


Remove more memory requests (400Mi) and second packageserver container

Memory requests with 4.7.0:
Before: 6097Mi (68%)
After:  5697Mi (64%)

/cherry-pick 4.7

Run the k8s conformance tests and it works as expected.
$ cat ignoretests.txt
[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]
[sig-cli] Kubectl client Kubectl cluster-info should check if Kubernetes control plane services is included in cluster-info  [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]
[sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]
[sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]
[k8s.io] [sig-node] NoExecuteTaintManager Multiple Pods [Serial] evicts pods with minTolerationSeconds [Disruptive] [Conformance] [Suite:k8s]
[k8s.io] [sig-node] NoExecuteTaintManager Single Pod [Serial] removing taint cancels eviction [Disruptive] [Conformance] [Suite:k8s]

$ ./openshift-tests run kubernetes/conformance --dry-run  | grep -F -v -f ignoretests.txt  | ./openshift-tests run -f -
[...]
/NotReady
Mar 15 09:54:46.745 W ns/e2e-emptydir-wrapper-6848 pod/wrapped-volume-race-3da7af1c-2827-433a-b517-d9dd9525f283-tpvzq node/crc-zsdx7-master-0 reason/Deleted
Mar 15 09:54:46.779 W ns/e2e-emptydir-wrapper-6848 pod/wrapped-volume-race-3da7af1c-2827-433a-b517-d9dd9525f283-rlv9n node/crc-zsdx7-master-0 reason/Deleted
Mar 15 09:54:46.812 W ns/e2e-emptydir-wrapper-6848 pod/wrapped-volume-race-3da7af1c-2827-433a-b517-d9dd9525f283-8hp9n node/crc-zsdx7-master-0 reason/Deleted
Mar 15 09:54:46.890 W ns/e2e-emptydir-wrapper-6848 pod/wrapped-volume-race-3da7af1c-2827-433a-b517-d9dd9525f283-qwb4n node/crc-zsdx7-master-0 reason/Deleted
Mar 15 09:54:46.932 W ns/e2e-emptydir-wrapper-6848 pod/wrapped-volume-race-3da7af1c-2827-433a-b517-d9dd9525f283-xjb2f node/crc-zsdx7-master-0 reason/Deleted
Mar 15 09:54:47.376 I e2e-test/"[sig-storage] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]" finishedStatus/Passed

Flaky invariants:

[sig-arch] Monitor cluster while tests execute

304 pass, 0 skip (34m45s)

/lgtm


PHP 7.2 Deprecated

PHP Deprecated:  Function create_function() is deprecated in \wp-content\plugins\airplane-mode\airplane-mode.php on line 789

hey @chriscct7 is that function still needed?

@norcross no it can be removed now it appears

this has been fixed in https://github.com/norcross/airplane-mode/releases/tag/0.2.4


Generated source maps are empty

All of the generated source map files don't actually contain any mappings:

https://github.com/krakenjs/zoid/blob/master/dist/zoid.frame.js.map
https://github.com/krakenjs/zoid/blob/master/dist/zoid.frame.min.js.map
https://github.com/krakenjs/zoid/blob/master/dist/zoid.js.map
https://github.com/krakenjs/zoid/blob/master/dist/zoid.min.js.map

I suspect, that this is actually bug in krakenjs/grumbler-scripts, as the same bug is in krakenjs/post-robot as well.

Fixed! Thanks again for letting me know.


Feature Request: Keybinding Overloading

I'm not asking for the ability to run multiple commands in sequence, as mentioned in

https://github.com/Microsoft/vscode/issues/18621
https://github.com/Microsoft/vscode/issues/871
https://github.com/Microsoft/vscode/issues/171

or as addressed with the macros extension
I'd like to be able to assign a given keybinding to multiple different commands separately, and if multiple commands are applicable in the current context when the keystroke is used, present the user with a menu of the options, rather than considering it a conflict, where only one can "win".
There are many significant benefits to this:

You don't have to worry about keybindings from your multiple extensions conflicting with each other.
All extension authors can add the keybinding they think makes the most sense, instead of telling you to manually add it in your own personal keybindings.json.
You don't have to worry about your personal keybindings clobbering a default keybinding (this sort of conflict does not appear when you use "Show Conflicts"—at least it did not in my tests).
You will never accidentally use the wrong command because of a conflict in which you expected another command to be triggered by your keybinding.
You can purposefully add multiple related commands to the same keybinding, so that you have fewer bindings to memorize.  For example,

you could assign all of your Git-related commands to ⌘⌥G, or, for more focused groupings,
you could assign all variations of Git commands related to adding files to ⌘⌥A, and those related to commiting to ⌘⌥C, and so forth.

You can experiment with changed keybindings without having to change the whole world in order to accommodate the change you think you might prefer.

Since there may be people who have grown accustomed to existing conflicts in their keybindings (and accustomed to the current winner) it would make sense for this behavior to have a setting to turn it on or off, so that they are not presented with a menu containing what used to be considered "conflicts" but under the new behavior are simply alternate options assigned to the same keystroke.

I've just discovered that VS Code apparently lacks a Key Resolver, which makes this suggestion even more valuable than I realized when I posted this.  (But even with a key resolver, this would be very valuable, for the reasons given above.)

I also encountered a conflict that resulted from the "one binding wins" approach, which caused me much initial confusion.
While editing a markdown file, I tried navigating one tab to the left, but nothing happened.  After testing the usual suspects—frozen OS, keyboard disconnected, accidentally activated MouseKeys—I had to test whether VS Code supported that nearly universal keystroke.
Of course it does, but it turns out some Markdown-related extension clobbered it, so that ⌘⇧[ was instead bound to changing the heading level of the current line.  Since it had no heading level there was no change visible, hence the appearance that the keystroke had done nothing.
Eliminating this sort of confusion would be just one of the many benefits of replacing a one-binding-wins approach with a menu-of-bound-commands approach.

It should be number 1 implemented feature.

@alexandrudima any chance of this being pulled out of the backlog?

This is certainly something I would like to see implemented as it causes an extension that I built to break the functionality of another


DefaultMessagestore start block

When I start the broker, the log for registering namesrv doesn't print. When I use jstack to check, I found that the main thread has been running on FileChannelImpl.trylock, and the status is not blocked. This situation has been going on for two days. What could be the reason for this?

deployment to k8s
operator: rocketmq-broker:4.5.0-alpine-operator-0.3.0

It seems stuck on the lock operation when getting the lock of the Rocketmq store folder.
Try to check the store folder, '{user.home}/store` by default.

It seems stuck on the lock operation when getting the lock of the Rocketmq store folder. Try to check the store folder, '{user.home}/store` by default.
@HScarb  it is deployed on k8s, and the mounted directories are all isolated from each other, so the lock files will not be read by multiple brokers.  The current confusion is that FileChannelImpl. trylock is non-blocking, and if the lock already exists, it will immediately cause an exception or return null.  However, in reality, it has been blocked on this method.


Add Amber support

Amber is a nostr event signer for Android. It allows users to keep their nsec segregated in a single, dedicated app.
https://github.com/greenart7c3/Amber/

+1 for Amber support... This would be really useful.


[KBM] Remapping CapsLock to another key when using RDP incorrectly toggles CapsLock behaviour

ℹ Computer information

PowerToys version: v0.23.0
PowerToy Utility: Keyboard Manager
Running PowerToys as Admin: Yes
Windows build number: Version 20H2 (19042.508)

📝 Provide detailed reproduction steps (if any)

Make sure CapsLock behaviour is off
Remap CapsLock key to Escape using KBM.
RDP into another computer.
Press CapsLock key

✔ Expected result

Escape is invoked
CapsLock toggle should remain off

❌ Actual result

Escape is invoked
CapsLock toggle is on

I tried using PowerToys instead of other keyboard mapping tools (e.g. KeyTweak), and it works great until I have to RDP. The caps lock remapping doesn't work properly.
Other tools does this correctly (KeyTweak, SharpKeys).

@paolsson-msft KBM doesn't work consistently with RDP because of this setting. If it is set to remote computer or full-screen and you are using RDP in full screen RDP overwrites the key events generated by KBM causing weird behavior like what you mentioned.

The ideal fix is to install PowerToys on the remote machine (but this may not always be feasible).
The other option is to set the above mentioned setting to on this computer or set it to the full-screen option and not use RDP in full-screen. All remappings work normally in this situation (as if RDP was just another program). The downside of doing this is that if you use Windows shortcuts, they will get invoked on the local machine and not on the remote machine. So hitting Win key while on the remote machine will open start menu in your local machine (which could make this work around unusable).
@crutkas @saahmedm FYI

@arjunbalgovind - Thanks for your fast reply. It indeed works well when installing PowerToys on the remote machine as well. So far I haven't experienced any issues.
As you say, as long as I can do that, this works fine. Still curious that other remappers solve this differently, is it because they use registry modifications?

Just tried everything again, and there is still one issue. It works correctly when using RDP into another physical machine, but it doesn't work when RDP:ing into a local Hyper-V machine, despite PowerToys running with remapping on both, however, the actual results has changed slightly. Now the caps behaviour is toggled on the source machine, instead of the target machine.

I'm going to change that answer once again. It works for RDP, but it works very bad. It seems like Caps lock is triggered for about ~0.5s after clicking Escape, despite PowerToys running on both the source and target machine (despite using Hyper-V or not).

@paolsson-mst you should have KBM running only on one machine at a time. If you have the same remapping active on both machines it could lead to some unexpected behavior. Can you check if you're still facing issues if it is active only on the remote machine?

@arjunbalgovind Thanks for your reply. I can validate it and see if it works and get back to you, but unfortunately that's not a feasible solution for me. I am frequently switching back and forwards between the remote/local computer.

closing this against #9337 which will be our host KBM and RDP tracker.  We believe RDP is causing a finite set of issues, we figure out the root cause and most, if not all, will be resolved.

closing this against #9337 which will be our host KBM and RDP tracker.  We believe RDP is causing a finite set of issues, we figure out the root cause and most, if not all, will be resolved.


Unable to Sign-In post upgrade to v1.1.1

Expected Behavior

A user is able to sign in with supported auth mechanisms.
For our Portal, we support auth with GitLab (Only Dev Environments) & Ping for All environments.
Actual Behavior

Post upgrading Backstage to v1.1.1, we get an error and are unable to sign in.
Most probably we missed something on our end during the upgrade process but would love to understand the root cause.
It states that the provider is not configured which is not true as it was working earlier and we haven't changed the app-config recently. Attaching the app-config for reference.
auth:
  environment: production
  session:
    secret: ${AUTH_SESSION_SECRET}
  providers:
    gitlab:
      production:
        clientId: ${AUTH_GITLAB_CLIENT_ID}
        clientSecret: ${AUTH_GITLAB_CLIENT_SECRET}
    oidc:
      production:
        metadataUrl: ${AUTH_OIDC_METADATA_URL}
        clientId: ${AUTH_OIDC_CLIENT_ID}
        clientSecret: ${AUTH_OIDC_CLIENT_SECRET}
        authorizationUrl: ${AUTH_OIDC_AUTH_URL}
        tokenUrl: ${AUTH_OIDC_TOKEN_URL}
        tokenSignedResponseAlg: ${AUTH_OIDC_TOKEN_SIGNED_RESPONSE_ALG}
        scope: ${AUTH_OIDC_SCOPE}
        prompt: ${AUTH_OIDC_PROMPT}

Steps to Reproduce

Upgrade Backstage to v1.1.1

Context

No longer able to Sign-In to the Portal experience.
Your Environment

Browser Information: Google Chrome 97.0.4692.99

Got the answer to our problem in Discord
https://github.com/backstage/backstage/blob/master/plugins/auth-backend/CHANGELOG.md#0130
https://backstage.io/docs/auth/identity-resolver
Closing the ticket!


Scroll: content not scrolling using list of cards

Short description of the problem:
I have a segmented view that consists of lists with ion-card elements. I am unable to scroll the content.
What behavior are you expecting?
Content should scroll.
Steps to reproduce:

create segmented page using ion-segment
for each switch case, use ion-list
within each list, populate it with an array of ion-card elements

<ion-header>
  <ion-toolbar>
    <ion-segment [(ngModel)]="relationship" >
      <ion-segment-button value="following" >Following</ion-segment-button>
      <ion-segment-button value="public" >Public</ion-segment-button>
    </ion-segment>
  </ion-toolbar>
</ion-header>
<ion-content padding>
  <div [ngSwitch]="relationship" style="height:100%">
    <ion-list *ngSwitchCase="'following'">
      <ion-card *ngFor="let feed of followingFeed">
          ...
      </ion-card>
    </ion-list>
    <ion-list *ngSwitchCase="'public'">
      <ion-card *ngFor="let feed of publicFeed">
          ...
      </ion-card>
    </ion-list>
  </div>
</ion-content>

Which Ionic Version? 1.x or 2.x
Ionic 2.x
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.3.1
Gulp version:  CLI version 1.2.2
Gulp local:
Ionic CLI Version: 2.1.0
Ionic App Lib Version: 2.1.0-beta.1
ios-deploy version: 1.9.0
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v6.3.1
Xcode version: Xcode 8.0 Build version 8A218a

Hello, thanks for opening an issue with us!  Would you be able to provide a repo that i can use to reproduce this issue?

Upon further investigation I discovered that the issue was actually being caused by an error in a separate tab. With that said, aren't different pages/tabs isolated from one another?

Hello! Segments are actually not seperate. It is the same dom element but depending on which segment is selected it will switch out the content. Awesome to hear that your issue is fixed now!


fix(runtime-core): update traverseStaticChildren for teleport

fix #4942 .
An egde case.Because of the hoist vnode, the new vnode can't get right reference of element.

#6858 (merged in 3.2.45) seems to be trying to fix the same problem. Is this PR still required, or can it be closed?


ELECTRON-66 (Unit tests)

Fixed the target version

@lneir Please review.

this will work for now as we have 7.10.0 on our build servers.  but is there a way to make this dynamically configurable?


WIP: Add support for Debian

One thing I haven't figured out yet is how to fix the tests for Debian. I have added the defaults for the OS in data/os/Debian.yaml, but they do not seem to be used.
Pull Request (PR) description
Adds support for Debian Buster (10).
This Pull Request (PR) fixes the following issues
Fixes #65

The syntax used in https://github.com/voxpupuli/puppet-nftables/blob/master/manifests/rules/nfs3.pp#L5 (more specifically the transport header keyword), does not seem to be recognised by the version of nftables shipped by Debian 10:
https://github.com/voxpupuli/puppet-nftables/pull/66/checks?check_run_id=1743370200#step:5:514
0.9.3' s manpage (shipped by CentOS8) reads:
       Matching destination port of both UDP and TCP.

           inet filter input meta l4proto {tcp, udp} @th,16,16 { 53, 80 }

       The above can also be written as

           inet filter input meta l4proto {tcp, udp} th dport { 53, 80 }

whereas that does not seem to be mentioned in 0.9.0's (Debian 10.7).

The syntax used in https://github.com/voxpupuli/puppet-nftables/blob/master/manifests/rules/nfs3.pp#L5 (more specifically the transport header keyword), does not seem to be recognised by the version of nftables shipped by Debian 10:
https://github.com/voxpupuli/puppet-nftables/pull/66/checks?check_run_id=1743370200#step:5:514
0.9.3' s manpage (shipped by CentOS8) reads:
       Matching destination port of both UDP and TCP.

           inet filter input meta l4proto {tcp, udp} @th,16,16 { 53, 80 }

       The above can also be written as

           inet filter input meta l4proto {tcp, udp} th dport { 53, 80 }

whereas that does not seem to be mentioned in 0.9.0's (Debian 10.7).

I think these four need tweaking, too:
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/all_rules_spec.rb#L78
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/all_rules_spec.rb#L80
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/default_spec.rb#L19
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/default_spec.rb#L21
as if I understand the proposed patch correctly /etc/nftables.conf is used as the root configuration file instead of /etc/sysconfig/nftables.conf.

I think these four need tweaking, too:
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/all_rules_spec.rb#L78
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/all_rules_spec.rb#L80
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/default_spec.rb#L19
https://github.com/voxpupuli/puppet-nftables/blob/master/spec/acceptance/default_spec.rb#L21
as if I understand the proposed patch correctly /etc/nftables.conf is used as the root configuration file instead of /etc/sysconfig/nftables.conf.

The syntax used in https://github.com/voxpupuli/puppet-nftables/blob/master/manifests/rules/nfs3.pp#L5 (more specifically the transport header keyword), does not seem to be recognised by the version of nftables shipped by Debian 10:
https://github.com/voxpupuli/puppet-nftables/pull/66/checks?check_run_id=1743370200#step:5:514
0.9.3' s manpage (shipped by CentOS8) reads:
       Matching destination port of both UDP and TCP.

           inet filter input meta l4proto {tcp, udp} @th,16,16 { 53, 80 }

       The above can also be written as

           inet filter input meta l4proto {tcp, udp} th dport { 53, 80 }

whereas that does not seem to be mentioned in 0.9.0's (Debian 10.7).

It looks like nfs is not recognized either. Something like @th,16,16 2049 instead of th dport nfs works. I am not sure if nfs always evaluates to 2049, or how that lookup happens.

The syntax used in https://github.com/voxpupuli/puppet-nftables/blob/master/manifests/rules/nfs3.pp#L5 (more specifically the transport header keyword), does not seem to be recognised by the version of nftables shipped by Debian 10:
https://github.com/voxpupuli/puppet-nftables/pull/66/checks?check_run_id=1743370200#step:5:514
0.9.3' s manpage (shipped by CentOS8) reads:
       Matching destination port of both UDP and TCP.

           inet filter input meta l4proto {tcp, udp} @th,16,16 { 53, 80 }

       The above can also be written as

           inet filter input meta l4proto {tcp, udp} th dport { 53, 80 }

whereas that does not seem to be mentioned in 0.9.0's (Debian 10.7).

It looks like nfs is not recognized either. Something like @th,16,16 2049 instead of th dport nfs works. I am not sure if nfs always evaluates to 2049, or how that lookup happens.

I don't see how to easily change the acceptance tests yet. Do you have an idea off-hand? In any case I'll keep at it

I don't see how to easily change the acceptance tests yet. Do you have an idea off-hand? In any case I'll keep at it

It looks like nfs is not recognized either. Something like @th,16,16 2049 instead of th dport nfs works. I am not sure if nfs always evaluates to 2049, or how that lookup happens.

Named ports nfs are mapped by their entries in /etc/services are they really different on debian than on EL based systems? Wow...

It looks like nfs is not recognized either. Something like @th,16,16 2049 instead of th dport nfs works. I am not sure if nfs always evaluates to 2049, or how that lookup happens.

Named ports nfs are mapped by their entries in /etc/services are they really different on debian than on EL based systems? Wow...

It looks like nfs is not recognized either. Something like @th,16,16 2049 instead of th dport nfs works. I am not sure if nfs always evaluates to 2049, or how that lookup happens.

/cc @dvanders

It looks like nfs is not recognized either. Something like @th,16,16 2049 instead of th dport nfs works. I am not sure if nfs always evaluates to 2049, or how that lookup happens.

/cc @dvanders

What is left here?

There's still some fixes for the the CI tests in live systems. I don't really know how to tackle changing them, but that's more a result of not being able to reproduce the testing environment locally and just requires more of my time.
A larger issue I think is how to approach the nfs rulesets which aren't compatible. One way would simply to be case against the OS version, but it looks like it's more a question of the nftables version - 0.9.0 not supporting the same syntax as 0.9.3. I think the commit I added (https://github.com/voxpupuli/puppet-nftables/pull/66/commits/df9a09bb3b8bde7c47097fee9779a12ee2f1bfd3) is flawed since the nfs port may vary from system to system.

We could extend the existing nftables fact to contain a nftables::version

One idea here would be to switch the metadata to support  ubuntu 20.04 for instance which has
# nft --version
nftables v0.9.3 (Topsy)

And then the narrower problem of older nft can be solved outside this ticket.

We could extend the existing nftables fact to contain a nftables::version

https://github.com/voxpupuli/puppet-nftables/pull/84  adds nftables.version

Just started to roll out puppet (again) and taking Debian into account and was happy to see there is already an issue running for this.

@ kienanstewart are you still working/interested  in this?
I continued your work, updated it to latest master and fixed the broken CI tests (see https://github.com/roock/puppet-nftables/pull/1). Do you wanna integrate my changes so we get that into master or should I create a new PR?

Since #124 has been merged this needs to be rebased.

@bastelfreak thanks! and sorry I wasn't able to get it into a working state


Permission precendence on inheritance is not correctly documented

The following statement is wrong:

"For members of the Project Collection Administrators or Team Foundation Administrators groups, Deny doesn't trump Allow"

If I deny "Contribute" rights on the master of my git repo for the "Contributors" group, Project Collection Administrators which are also part of that group cannot push or merge / complete PRs to master.
I would really appreciate if this could be fixed ...

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

ID: aa32191d-6d0a-058f-2ffe-3ce1b58e2c59
Version Independent ID: 858d1ed3-b2af-699f-9d51-86ac0962086b
Content: How are permissions and groups defined? - Azure DevOps
Content Source: docs/organizations/security/about-permissions.md
Product: devops
Technology: devops-security
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@IngmarVoigt2 - Could you clarify if you believe the content is inacurrate, or you believe the way the system works should be changed. If the latter, please file your request on our  Developer Community page.

@IngmarVoigt2 - I'm closing this issue. Please reopen if you can provide more clarifying information. Thank you.


Adding a new site for portfolio

Heres's the gtmetric link
https://gtmetrix.com/reports/bala-frontdev.github.io/0rynLZ1y/

Added bala-frontdev.github.io to the green team.


browserify support doesnt work

the docs advertise this as being npm installable but the module exports is an empty object

:+1: this doesn't work in a way that someone installing from NPM would expect. The module should export MediaStreamRecorder

:+1:

@muaz-khan when do you plan on having this make its way to master? Anything I can do to help. Super trivial for me to just modify the file so it exports properly, but it would be cool for this to part of the official node package.


How to use serial.read()?

Is this for read last sent bytes or it is using by inside the registerReadCallback ?
I use an android phone and connect to a pc node-serial that whatever android send some data, it just sends back.
I've put serial.read inside write success callback and register read callback, but it can't get any data.
How to use that ?

Any updates @crapthings ?

hey @xseignard registerReadCallback works great. but still don't know how and when to use read function.

The truth is that I may remove serial.read() as it is a bit useless, because it mean that you would need to know exactly when you need to read, and that's almost impossible to know it, and to time it.

I'll update the code sample in the README, according to this.

Should be ok to close it then,
Feel free to reopen it if needed.
Regards


unable to record Logitech MX Master 3 Gesture button

OS
macOS 13.4 (22F66)
LinearMouse
0.9.1
Describe the bug

can not record Gesture button button from MX Master 3
default MX Master 3 press the Gesture button will execute cmd+tab
Gesture button：

To reproduce

uninstall Logitech options puls and G HUB
restart system
use Buttons/Assign actions to mouse buttons record
press the Gesture button record get cmd

Expected behavior
No response
Anything else?
No response

LinearMouse.log

LinearMouse.log

复现过程中还发现，按下 Gesture button 获取为 cmd 时还会出现设置页面卡死现象，只能强制退出重新启动 LinearMouse 才能导出日志

Thank you for the detailed feedback!
There's a related issue (https://github.com/Hammerspoon/hammerspoon/issues/3373) I found that might be able to explain what's going on. According to this article performs the same function as the left command key.
I think it might be worth giving Karabiner-Elements a try and binding the left command on your Logitech MX Master 3, just like the article suggests. I'll consider how to approach this situation within LinearMouse and whether or not to implement this feature.

I have been finding this problem with all mouse programs I'm downloading, including logitech options+, whenever I try to add a keyboard shortcut with CMD, it will only pull that up and never the next key. I'm losing my mind here, downloaded two other programs that I'm going to go try out now - this one isn't working for me.


Specify secrets output directory

Hello, hiddengearz!
Is it possible to specify directory to store secrets?
Right now its os.OpenFile("secrets_"+OutputFile and its impossible to use because if I open file located in the another path it wont work as expected
For example:
/tmp/jsubfinder.binary search --crawl -t 10 -s --sig '/tmp/.jsf_signatures.yaml' -f /dockerresults/httpx.txt -o /dockerresults/js.txt

Will give an error
 open secrets_/dockerresults/js.txt: no such file or directory

which is 100% right , it cant open absolute url like that
So for example i would like to have something like -store-secrets-dir /dockerresults/secrets
Hope to hear your answer soon,
Regards, wellenc :)

This has been resolved in 557fd90d99fa247e7bb3013115e08e2c3e666b9d
-s now takes a string argument for the location of the secrets file.
jsubfinder search -u www.youtube.com -s /home/user/somefolder/secrests_test.txt


[NETBEANS-1243] Community link

On the Welcome Screen, the Community link points here:
https://netbeans.org/community/index.html?utm_source=netbeans&utm_campaign=welcomepage
...should maybe point here instead:
https://netbeans.apache.org/community/index.html

Sounds reasonable - @vieiro and @neilcsmith-net might have an opinion about trackability though.

Any objections to merging this?

As there was no objection, I would say: Merge it, we can change it at anytime. Same goes for #869. Thank you.