create experiment failed

2020-03-31 07:53:41.921193 Step: [The END]: Apply the chaos result CR for pod-network-loss experiment
task path: /utils/runtime/update_chaos_result_resource.yml:33
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "kubectl apply -f /utils/runtime/chaos-result.yml -n ", "delta": "0:00:00.342643", "end": "2020-03-31 07:53:41.900082", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2020-03-31 07:53:41.557439", "stderr": "Error: flag needs an argument: 'n' in -n

@badashanren thanks for reporting this issue. Can you please elaborate/provide the following details so that we can help you get this running/fix the problem:

Litmus version
Outputs of:

kubectl get chaosengine <chaosengine-name> -n <your namespace> -o yaml (your chaosengine spec)
kubectl get chaosexperiments -n <your namespace> (experiments available in your ns)
kubectl describe pod <experiment pod> -n <your namespace> (env and other params passed to your exp)
`kubectl logs  -n  (basically the complete log as against the error snippet)

@badashanren thanks for reporting this issue. Can you please elaborate/provide the following details so that we can help you get this running/fix the problem:

Litmus version

Outputs of:

kubectl get chaosengine <chaosengine-name> -n <your namespace> -o yaml (your chaosengine spec)
kubectl get chaosexperiments -n <your namespace> (experiments available in your ns)
kubectl describe pod <experiment pod> -n <your namespace> (env and other params passed to your exp)
`kubectl logs  -n  (basically the complete log as against the error snippet)

Litmus version: v1.2.0
kubectl get chaosexperiments nginx-chaos -n litmus output:
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"litmuschaos.io/v1alpha1","kind":"ChaosEngine","metadata":{"annotations":{},"name":"nginx-chaos","namespace":"default"},"spec":{"annotationCheck":"true","appinfo":{"appkind":"deployment","applabel":"run=mynginx","appns":"default"},"auxiliaryAppInfo":"","chaosServiceAccount":"pod-delete-sa","engineState":"active","experiments":[{"name":"pod-delete","spec":{"components":{"env":[{"name":"TOTAL_CHAOS_DURATION","value":"30"},{"name":"CHAOS_INTERVAL","value":"10"},{"name":"FORCE","value":"false"}]}}}],"jobCleanUpPolicy":"delete","monitoring":false}}
creationTimestamp: "2020-03-31T07:31:54Z"
finalizers:

chaosengine.litmuschaos.io/finalizer
generation: 2
name: nginx-chaos
namespace: default
resourceVersion: "2664037585"
selfLink: /apis/litmuschaos.io/v1alpha1/namespaces/default/chaosengines/nginx-chaos
uid: a520e377-da43-4099-b056-69c897c88379
spec:
annotationCheck: "true"
appinfo:
appkind: deployment
applabel: run=mynginx
appns: default
chaosServiceAccount: pod-delete-sa
components:
monitor:
image: ""
runner: {}
engineState: active
experiments:
name: pod-delete
spec:
components:
env:
- name: TOTAL_CHAOS_DURATION
value: "30"
- name: CHAOS_INTERVAL
value: "10"
- name: FORCE
value: "false"
rank: 0
jobCleanUpPolicy: delete
status:
engineStatus: initialized
experiments: null
kubectl get chaosexperiments,output:
No resources found in litmus/default namespace

kubectl logs , output:
ansible-playbook 2.7.3
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
executable location = /usr/local/bin/ansible-playbook
python version = 2.7.17 (default, Nov  7 2019, 10:07:09) [GCC 7.4.0]
Using /etc/ansible/ansible.cfg as config file
/etc/ansible/hosts did not meet host_list requirements, check plugin documentation if this is unexpected
/etc/ansible/hosts did not meet script requirements, check plugin documentation if this is unexpected
statically imported: /experiments/generic/pod_network_loss/pod_network_loss_ansible_prerequisites.yml
2020-03-31 07:53:35.172737 PLAYBOOK: pod_network_loss_ansible_logic.yml
1 plays in ./experiments/generic/pod_network_loss/pod_network_loss_ansible_logic.yml
2020-03-31 07:53:35.234972 ************ BRACE YOURSELF, EXPERIMENT BEGINS! ************
2020-03-31 07:53:38.384323 Step: Gathering Facts
task path: /experiments/generic/pod_network_loss/pod_network_loss_ansible_logic.yml:2
META: ran handlers
2020-03-31 07:53:38.785794 Step: Identify the chaos util to be invoked
task path: /experiments/generic/pod_network_loss/pod_network_loss_ansible_prerequisites.yml:1
details => {"changed": true, "checksum": "d4fade44014f3046d27936f97fae9366fb9fe827", "dest": "./chaosutil.yml", "gid": 0, "group": "root", "md5sum": "dce3efa87bee52e3cf15fd1e1a7d44cc", "mode": "0644", "owner": "root", "size": 56, "src": "/root/.ansible/tmp/ansible-tmp-1585641218.43-1285708157619/source", "state": "file", "uid": 0}
2020-03-31 07:53:38.831654 Step: include_vars
task path: /experiments/generic/pod_network_loss/pod_network_loss_ansible_logic.yml:28
details => {"ansible_facts": {"c_util": "/chaoslib/pumba/network_chaos/network_chaos.yml"}, "ansible_included_var_files": ["/experiments/generic/pod_network_loss/chaosutil.yml"], "changed": false}
included: /utils/runtime/update_chaos_result_resource.yml for <IP_ADDRESS>
2020-03-31 07:53:39.162245 Step: [PreReq]: Generate the chaos result CR to reflect SOT (Start of Test)
task path: /utils/runtime/update_chaos_result_resource.yml:3
details => {"changed": true, "checksum": "4edcce04ed6f9f7bc15ec3987184a37661a65597", "dest": "/utils/runtime/chaos-result.yml", "gid": 0, "group": "root", "md5sum": "2446f755323d9b516cc3aea457a84ecd", "mode": "0644", "owner": "root", "size": 267, "src": "/root/.ansible/tmp/ansible-tmp-1585641218.98-204941604955563/source", "state": "file", "uid": 0}
2020-03-31 07:53:39.761213 Step: [PreReq]: Apply the chaos result CR for pod-network-loss experiment
task path: /utils/runtime/update_chaos_result_resource.yml:13
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "kubectl apply -f /utils/runtime/chaos-result.yml -n ", "delta": "0:00:00.353071", "end": "2020-03-31 07:53:39.738645", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2020-03-31 07:53:39.385574", "stderr": "Error: flag needs an argument: 'n' in -n
Examples:
Apply the configuration in pod.json to a pod.
kubectl apply -f ./pod.json
Apply the JSON passed into stdin to a pod.
cat pod.json | kubectl apply -f -
Note: --prune is still in Alpha
Apply the configuration in manifest.yaml that matches label app=nginx and delete all the other resources that are not in the file and match label app=nginx.
kubectl apply --prune -f manifest.yaml -l app=nginx
Apply the configuration in manifest.yaml and delete all the other configmaps that are not in the file.
kubectl apply --prune -f manifest.yaml --all --prune-whitelist=core/v1/ConfigMap
Available Commands:
edit-last-applied Edit latest last-applied-configuration annotations of a resource/object
set-last-applied  Set the last-applied-configuration annotation on a live object to match the contents of a file.
view-last-applied View latest last-applied-configuration annotations of a resource/object
Options:
--all=false: Select all resources in the namespace of the specified resource types.
--allow-missing-template-keys=true: If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
--cascade=true: If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a ReplicationController).  Default true.
--dry-run=false: If true, only print the object that would be sent, without sending it.
-f, --filename=[]: that contains the configuration to apply
--force=false: Only used when grace-period=0. If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation.
--grace-period=-1: Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion).
--include-uninitialized=false: If true, the kubectl command applies to uninitialized objects. If explicitly set to false, this flag overrides other flags that make the kubectl commands apply to uninitialized objects, e.g., "--all". Objects with empty metadata.initializers are regarded as initialized.
--openapi-patch=true: If true, use openapi to calculate diff when the openapi presents and the resource can be found in the openapi spec. Otherwise, fall back to use baked-in types.
-o, --output='': Output format. One of: json|yaml|name|template|go-template|go-template-file|templatefile|jsonpath|jsonpath-file.
--overwrite=true: Automatically resolve conflicts between the modified and live configuration by using values from the modified configuration
--prune=false: Automatically delete resource objects, including the uninitialized ones, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all.
--prune-whitelist=[]: Overwrite the default whitelist with <group/version/kind> for --prune
--record=false: Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.
-R, --recursive=false: Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.
-l, --selector='': Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2)
--server-dry-run=false: If true, request will be sent to server with dry-run flag, which means the modifications won't be persisted. This is an alpha feature and flag.
--template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
--timeout=0s: The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object
--validate=true: If true, use a schema to validate the input before sending it
--wait=false: If true, wait for resources to be gone before returning. This waits for finalizers.
Usage:
kubectl apply -f FILENAME [options]
Use "kubectl  --help" for more information about a given command.
Use "kubectl options" for a list of global command-line options (applies to all commands).
flag needs an argument: 'n' in -n", "stderr_lines": ["Error: flag needs an argument: 'n' in -n", "", "", "Examples:", "  # Apply the configuration in pod.json to a pod.", "  kubectl apply -f ./pod.json", "  ", "  # Apply the JSON passed into stdin to a pod.", "  cat pod.json | kubectl apply -f -", "  ", "  # Note: --prune is still in Alpha", "  # Apply the configuration in manifest.yaml that matches label app=nginx and delete all the other resources that are not in the file and match label app=nginx.", "  kubectl apply --prune -f manifest.yaml -l app=nginx", "  ", "  # Apply the configuration in manifest.yaml and delete all the other configmaps that are not in the file.", "  kubectl apply --prune -f manifest.yaml --all --prune-whitelist=core/v1/ConfigMap", "", "Available Commands:", "  edit-last-applied Edit latest last-applied-configuration annotations of a resource/object", "  set-last-applied  Set the last-applied-configuration annotation on a live object to match the contents of a file.", "  view-last-applied View latest last-applied-configuration annotations of a resource/object", "", "Options:", "      --all=false: Select all resources in the namespace of the specified resource types.", "      --allow-missing-template-keys=true: If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.", "      --cascade=true: If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a ReplicationController).  Default true.", "      --dry-run=false: If true, only print the object that would be sent, without sending it.", "  -f, --filename=[]: that contains the configuration to apply", "      --force=false: Only used when grace-period=0. If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation.", "      --grace-period=-1: Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion).", "      --include-uninitialized=false: If true, the kubectl command applies to uninitialized objects. If explicitly set to false, this flag overrides other flags that make the kubectl commands apply to uninitialized objects, e.g., "--all". Objects with empty metadata.initializers are regarded as initialized.", "      --openapi-patch=true: If true, use openapi to calculate diff when the openapi presents and the resource can be found in the openapi spec. Otherwise, fall back to use baked-in types.", "  -o, --output='': Output format. One of: json|yaml|name|template|go-template|go-template-file|templatefile|jsonpath|jsonpath-file.", "      --overwrite=true: Automatically resolve conflicts between the modified and live configuration by using values from the modified configuration", "      --prune=false: Automatically delete resource objects, including the uninitialized ones, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all.", "      --prune-whitelist=[]: Overwrite the default whitelist with <group/version/kind> for --prune", "      --record=false: Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.", "  -R, --recursive=false: Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.", "  -l, --selector='': Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2)", "      --server-dry-run=false: If true, request will be sent to server with dry-run flag, which means the modifications won't be persisted. This is an alpha feature and flag.", "      --template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].", "      --timeout=0s: The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object", "      --validate=true: If true, use a schema to validate the input before sending it", "      --wait=false: If true, wait for resources to be gone before returning. This waits for finalizers.", "", "Usage:", "  kubectl apply -f FILENAME [options]", "", "Use "kubectl  --help" for more information about a given command.", "Use "kubectl options" for a list of global command-line options (applies to all commands).", "", "flag needs an argument: 'n' in -n"], "stdout": "", "stdout_lines": []}
2020-03-31 07:53:39.806324 Step: set_fact
task path: /experiments/generic/pod_network_loss/pod_network_loss_ansible_logic.yml:88
details => {"ansible_facts": {"flag": "Fail"}, "changed": false}
included: /utils/runtime/getting_failure_step.yml for <IP_ADDRESS>
2020-03-31 07:53:39.956392 Step: [Failure-Detection]: Recording the offset, on the basis of verbosity
task path: /utils/runtime/getting_failure_step.yml:8
details => {"ansible_facts": {"offset": 2}, "changed": false}
2020-03-31 07:53:40.560620 Step: [Failure-Detection]: Getting name of failure step from experiment pod
task path: /utils/runtime/getting_failure_step.yml:14
details => {"changed": true, "cmd": "kubectl logs  -n  | grep "FAILED!" -B 2 | head -1 | awk -F "Step:" '{print $2}'", "delta": "0:00:00.338976", "end": "2020-03-31 07:53:40.542517", "rc": 0, "start": "2020-03-31 07:53:40.203541", "stderr": "Error: flag needs an argument: 'n' in -n
Aliases:
logs, log
Examples:
Return snapshot logs from pod nginx with only one container
kubectl logs nginx
Return snapshot logs from pod nginx with multi containers
kubectl logs nginx --all-containers=true
Return snapshot logs from all containers in pods defined by label app=nginx
kubectl logs -lapp=nginx --all-containers=true
Return snapshot of previous terminated ruby container logs from pod web-1
kubectl logs -p -c ruby web-1
Begin streaming the logs of the ruby container in pod web-1
kubectl logs -f -c ruby web-1
Display only the most recent 20 lines of output in pod nginx
kubectl logs --tail=20 nginx
Show all logs from pod nginx written in the last hour
kubectl logs --since=1h nginx
Return snapshot logs from first container of a job named hello
kubectl logs job/hello
Return snapshot logs from container nginx-1 of a deployment named nginx
kubectl logs deployment/nginx -c nginx-1
Options:
--all-containers=false: Get all containers's logs in the pod(s).
-c, --container='': Print the logs of this container
-f, --follow=false: Specify if the logs should be streamed.
--limit-bytes=0: Maximum bytes of logs to return. Defaults to no limit.
--pod-running-timeout=20s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
-p, --previous=false: If true, print the logs for the previous instance of the container in a pod if it exists.
-l, --selector='': Selector (label query) to filter on.
--since=0s: Only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used.
--since-time='': Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used.
--tail=-1: Lines of recent log file to display. Defaults to -1 with no selector, showing all log lines otherwise 10, if a selector is provided.
--timestamps=false: Include timestamps on each line in the log output
Usage:
kubectl logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER] [options]
Use "kubectl options" for a list of global command-line options (applies to all commands).
flag needs an argument: 'n' in -n", "stderr_lines": ["Error: flag needs an argument: 'n' in -n", "", "", "Aliases:", "logs, log", "", "Examples:", "  # Return snapshot logs from pod nginx with only one container", "  kubectl logs nginx", "  ", "  # Return snapshot logs from pod nginx with multi containers", "  kubectl logs nginx --all-containers=true", "  ", "  # Return snapshot logs from all containers in pods defined by label app=nginx", "  kubectl logs -lapp=nginx --all-containers=true", "  ", "  # Return snapshot of previous terminated ruby container logs from pod web-1", "  kubectl logs -p -c ruby web-1", "  ", "  # Begin streaming the logs of the ruby container in pod web-1", "  kubectl logs -f -c ruby web-1", "  ", "  # Display only the most recent 20 lines of output in pod nginx", "  kubectl logs --tail=20 nginx", "  ", "  # Show all logs from pod nginx written in the last hour", "  kubectl logs --since=1h nginx", "  ", "  # Return snapshot logs from first container of a job named hello", "  kubectl logs job/hello", "  ", "  # Return snapshot logs from container nginx-1 of a deployment named nginx", "  kubectl logs deployment/nginx -c nginx-1", "", "Options:", "      --all-containers=false: Get all containers's logs in the pod(s).", "  -c, --container='': Print the logs of this container", "  -f, --follow=false: Specify if the logs should be streamed.", "      --limit-bytes=0: Maximum bytes of logs to return. Defaults to no limit.", "      --pod-running-timeout=20s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running", "  -p, --previous=false: If true, print the logs for the previous instance of the container in a pod if it exists.", "  -l, --selector='': Selector (label query) to filter on.", "      --since=0s: Only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used.", "      --since-time='': Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used.", "      --tail=-1: Lines of recent log file to display. Defaults to -1 with no selector, showing all log lines otherwise 10, if a selector is provided.", "      --timestamps=false: Include timestamps on each line in the log output", "", "Usage:", "  kubectl logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER] [options]", "", "Use "kubectl options" for a list of global command-line options (applies to all commands).", "", "flag needs an argument: 'n' in -n"], "stdout": "", "stdout_lines": []}
2020-03-31 07:53:40.615354 Step: [Failure-Detection]: Recording the name of failed step
task path: /utils/runtime/getting_failure_step.yml:21
details => {"ansible_facts": {"failStep": ""}, "changed": false}
2020-03-31 07:53:40.666403 Step: [Failure-Detection]: Printing the name of failed step
task path: /utils/runtime/getting_failure_step.yml:25
details => {
"msg": "failStep: "
}
included: /utils/runtime/update_chaos_result_resource.yml for <IP_ADDRESS>
2020-03-31 07:53:41.416221 Step: [Result]: Update the chaos result CR to reflect EOT (End of Test)
task path: /utils/runtime/update_chaos_result_resource.yml:23
details => {"changed": true, "checksum": "8e6f0336496f729a3945fd981ff0dbb108885787", "dest": "/utils/runtime/chaos-result.yml", "gid": 0, "group": "root", "md5sum": "5b4ef093edf79e52ce377e85d709445f", "mode": "0644", "owner": "root", "size": 281, "src": "/root/.ansible/tmp/ansible-tmp-1585641220.94-197404778969050/source", "state": "file", "uid": 0}
2020-03-31 07:53:41.921193 Step: [The END]: Apply the chaos result CR for pod-network-loss experiment
task path: /utils/runtime/update_chaos_result_resource.yml:33
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "kubectl apply -f /utils/runtime/chaos-result.yml -n ", "delta": "0:00:00.342643", "end": "2020-03-31 07:53:41.900082", "failed_when_result": true, "msg": "non-zero return code", "rc": 1, "start": "2020-03-31 07:53:41.557439", "stderr": "Error: flag needs an argument: 'n' in -n
Examples:
Apply the configuration in pod.json to a pod.
kubectl apply -f ./pod.json
Apply the JSON passed into stdin to a pod.
cat pod.json | kubectl apply -f -
Note: --prune is still in Alpha
Apply the configuration in manifest.yaml that matches label app=nginx and delete all the other resources that are not in the file and match label app=nginx.
kubectl apply --prune -f manifest.yaml -l app=nginx
Apply the configuration in manifest.yaml and delete all the other configmaps that are not in the file.
kubectl apply --prune -f manifest.yaml --all --prune-whitelist=core/v1/ConfigMap
Available Commands:
edit-last-applied Edit latest last-applied-configuration annotations of a resource/object
set-last-applied  Set the last-applied-configuration annotation on a live object to match the contents of a file.
view-last-applied View latest last-applied-configuration annotations of a resource/object
Options:
--all=false: Select all resources in the namespace of the specified resource types.
--allow-missing-template-keys=true: If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
--cascade=true: If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a ReplicationController).  Default true.
--dry-run=false: If true, only print the object that would be sent, without sending it.
-f, --filename=[]: that contains the configuration to apply
--force=false: Only used when grace-period=0. If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation.
--grace-period=-1: Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion).
--include-uninitialized=false: If true, the kubectl command applies to uninitialized objects. If explicitly set to false, this flag overrides other flags that make the kubectl commands apply to uninitialized objects, e.g., "--all". Objects with empty metadata.initializers are regarded as initialized.
--openapi-patch=true: If true, use openapi to calculate diff when the openapi presents and the resource can be found in the openapi spec. Otherwise, fall back to use baked-in types.
-o, --output='': Output format. One of: json|yaml|name|template|go-template|go-template-file|templatefile|jsonpath|jsonpath-file.
--overwrite=true: Automatically resolve conflicts between the modified and live configuration by using values from the modified configuration
--prune=false: Automatically delete resource objects, including the uninitialized ones, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all.
--prune-whitelist=[]: Overwrite the default whitelist with <group/version/kind> for --prune
--record=false: Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.
-R, --recursive=false: Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.
-l, --selector='': Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2)
--server-dry-run=false: If true, request will be sent to server with dry-run flag, which means the modifications won't be persisted. This is an alpha feature and flag.
--template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
--timeout=0s: The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object
--validate=true: If true, use a schema to validate the input before sending it
--wait=false: If true, wait for resources to be gone before returning. This waits for finalizers.
Usage:
kubectl apply -f FILENAME [options]
Use "kubectl  --help" for more information about a given command.
Use "kubectl options" for a list of global command-line options (applies to all commands).
flag needs an argument: 'n' in -n", "stderr_lines": ["Error: flag needs an argument: 'n' in -n", "", "", "Examples:", "  # Apply the configuration in pod.json to a pod.", "  kubectl apply -f ./pod.json", "  ", "  # Apply the JSON passed into stdin to a pod.", "  cat pod.json | kubectl apply -f -", "  ", "  # Note: --prune is still in Alpha", "  # Apply the configuration in manifest.yaml that matches label app=nginx and delete all the other resources that are not in the file and match label app=nginx.", "  kubectl apply --prune -f manifest.yaml -l app=nginx", "  ", "  # Apply the configuration in manifest.yaml and delete all the other configmaps that are not in the file.", "  kubectl apply --prune -f manifest.yaml --all --prune-whitelist=core/v1/ConfigMap", "", "Available Commands:", "  edit-last-applied Edit latest last-applied-configuration annotations of a resource/object", "  set-last-applied  Set the last-applied-configuration annotation on a live object to match the contents of a file.", "  view-last-applied View latest last-applied-configuration annotations of a resource/object", "", "Options:", "      --all=false: Select all resources in the namespace of the specified resource types.", "      --allow-missing-template-keys=true: If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.", "      --cascade=true: If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a ReplicationController).  Default true.", "      --dry-run=false: If true, only print the object that would be sent, without sending it.", "  -f, --filename=[]: that contains the configuration to apply", "      --force=false: Only used when grace-period=0. If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation.", "      --grace-period=-1: Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion).", "      --include-uninitialized=false: If true, the kubectl command applies to uninitialized objects. If explicitly set to false, this flag overrides other flags that make the kubectl commands apply to uninitialized objects, e.g., "--all". Objects with empty metadata.initializers are regarded as initialized.", "      --openapi-patch=true: If true, use openapi to calculate diff when the openapi presents and the resource can be found in the openapi spec. Otherwise, fall back to use baked-in types.", "  -o, --output='': Output format. One of: json|yaml|name|template|go-template|go-template-file|templatefile|jsonpath|jsonpath-file.", "      --overwrite=true: Automatically resolve conflicts between the modified and live configuration by using values from the modified configuration", "      --prune=false: Automatically delete resource objects, including the uninitialized ones, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all.", "      --prune-whitelist=[]: Overwrite the default whitelist with <group/version/kind> for --prune", "      --record=false: Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.", "  -R, --recursive=false: Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.", "  -l, --selector='': Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2)", "      --server-dry-run=false: If true, request will be sent to server with dry-run flag, which means the modifications won't be persisted. This is an alpha feature and flag.", "      --template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].", "      --timeout=0s: The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object", "      --validate=true: If true, use a schema to validate the input before sending it", "      --wait=false: If true, wait for resources to be gone before returning. This waits for finalizers.", "", "Usage:", "  kubectl apply -f FILENAME [options]", "", "Use "kubectl  --help" for more information about a given command.", "Use "kubectl options" for a list of global command-line options (applies to all commands).", "", "flag needs an argument: 'n' in -n"], "stdout": "", "stdout_lines": []}
to retry, use: --limit @/experiments/generic/pod_network_loss/pod_network_loss_ansible_logic.retry
2020-03-31 07:53:41.923791 ************ RELAX, EXPERIMENT ENDS! ************
<IP_ADDRESS>                  : ok=13   changed=4    unreachable=0    failed=2

Thanks @badashanren ! Here are my observations from the first look:

The chaosexperiment CRs are not available in the default ns which is where nginx app w/ run=mynginx label is created. We need the pod-delete experiment CR there from [here](kubectl apply -f https://hub.litmuschaos.io/api/chaos?file=charts/generic/pod-delete/experiment.yaml).

Any kubectl command inside the exp pod seems to fail with invalid namespace value (error for invalid value after -n -- which is why the kubectl apply help is getting printed.

It would be worthwhile to see what values have been passed to the exp pod by the runner - which will help us identify the issue.  It will really help if you add these 2 outputs:

kubectl describe nginx-chaos-runner
kubectl describe <experiment-pod>

If these are disappearing too quickly before you can collect this, pls make .spec.jobCleanupPolicy: retain in chaosengine spec.

Thanks @badashanren ! Here are my observations from the first look:

The chaosexperiment CRs are not available in the default ns which is where nginx app w/ run=mynginx label is created. We need the pod-delete experiment CR there from [here](kubectl apply -f https://hub.litmuschaos.io/api/chaos?file=charts/generic/pod-delete/experiment.yaml).
Any kubectl command inside the exp pod seems to fail with invalid namespace value (error for invalid value after -n -- which is why the kubectl apply help is getting printed.

It would be worthwhile to see what values have been passed to the exp pod by the runner - which will help us identify the issue. It will really help if you add these 2 outputs:

kubectl describe nginx-chaos-runner
kubectl describe <experiment-pod>

If these are disappearing too quickly before you can collect this, pls make .spec.jobCleanupPolicy: retain in chaosengine spec.

kubectl get chaosexperiments
NAME                     AGE
container-kill           2m29s
disk-fill                2m30s
disk-loss                2m30s
node-cpu-hog             2m29s
node-drain               2m31s
node-memory-hog          2m29s
pod-cpu-hog              2m30s
pod-delete               2m30s
pod-network-corruption   2m30s
pod-network-latency      2m30s
pod-network-loss         2m30s
kubectl describe nginx-chaos-runner
sorry, what is nginx-chaos-runner? It's some resources?I can't find it~
kubectl describe ,output:
Name:         pod-network-loss-ktwrf-5nfw9
Namespace:    default
Node:         <IP_ADDRESS>/<IP_ADDRESS>
Start Time:   Tue, 31 Mar 2020 17:15:35 +0800
Labels:       controller-uid=9bb28634-048b-4979-a604-37325b8e4b2b
experiment=pod-network-loss
job-name=pod-network-loss-ktwrf
Annotations:  tke.cloud.tencent.com/networks-status:
[{
"name": "tke-bridge",
"ips": [
"<IP_ADDRESS>"
],
"default": true,
"dns": {}
}]
Status:       Succeeded
IP:           <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  Job/pod-network-loss-ktwrf
Containers:
ansibletest:
Container ID:  docker://21969cac8ff049a4ae688720f6b1237c1e65f57623966b8d9d1eef18158b5f9d
Image:         litmuschaos/ansible-runner:ci
Image ID:      docker-pullable://litmuschaos/ansible-runner@sha256:20ed0263bf8cf68f2c90c2e128b92f38309edbd52c75921d88f9bbb4bc9907d4
Port:
Host Port:
Command:
/bin/bash
Args:
-c
ansible-playbook ./experiments/generic/pod_network_loss/pod_network_loss_ansible_logic.yml -i /etc/ansible/hosts -vv; exit 0
State:          Terminated
Reason:       Completed
Exit Code:    0
Started:      Tue, 31 Mar 2020 17:15:37 +0800
Finished:     Tue, 31 Mar 2020 17:15:49 +0800
Ready:          False
Restart Count:  0
Environment:
ANSIBLE_STDOUT_CALLBACK:         default
APP_NAMESPACE:                   default
APP_LABEL:                       run=mynginx
APP_KIND:
TARGET_CONTAINER:
NETWORK_INTERFACE:               eth0
NETWORK_PACKET_LOSS_PERCENTAGE:  70
TOTAL_CHAOS_DURATION:            1800
RAMP_TIME:
LIB:                             pumba
LIB_IMAGE:                       gaiaadm/pumba:0.6.5
CHAOS_SERVICE_ACCOUNT:            (v1:spec.serviceAccountName)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from litmus-token-rzsq6 (ro)
Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
litmus-token-rzsq6:
Type:        Secret (a volume populated by a Secret)
SecretName:  litmus-token-rzsq6
Optional:    false
QoS Class:       BestEffort
Node-Selectors:
Tolerations:
Events:
Type    Reason     Age   From                 Message

Normal  Scheduled  117s  default-scheduler    Successfully assigned default/pod-network-loss-ktwrf-5nfw9 to <IP_ADDRESS>
Normal  Pulling    116s  kubelet, <IP_ADDRESS>  Pulling image "litmuschaos/ansible-runner:ci"
Normal  Pulled     115s  kubelet, <IP_ADDRESS>  Successfully pulled image "litmuschaos/ansible-runner:ci"
Normal  Created    115s  kubelet, <IP_ADDRESS>  Created container ansibletest
Normal  Started    115s  kubelet, <IP_ADDRESS>  Started container ansibletest

Hey @badashanren are you still facing the same error / does the earlier log hold ? I see that you have successful runs of some experiments like pod-delete / network-delays etc., in the edit describe output of the chaosengine?

Meanwhile, please feel free to hop on to the community google hangouts here to have a chat or join our slack channel (#litmus) on Kubernetes workspace to start/join discussions!

are you still facing the same error / does the earlier log hold ? I see that you have successful runs of some experiments like pod-delete / network-delays etc., in the edited describe output of the chaosengine

No，it still failed! The experiment like  pod-delete / network-loss is launched
kubectl logs ,We found the error log. It can't get "namespace", Due to permission ？

Yes, you are correct. The namespace is invalid. Having said that there are a couple of missing items in the describe output provided earlier / as well as the chaosengine. In the snippet you have shared, the ENVs looked like this:
APP_NAMESPACE: default
APP_LABEL: run=mynginx
APP_KIND:
TARGET_CONTAINER:
NETWORK_INTERFACE: eth0
NETWORK_PACKET_LOSS_PERCENTAGE: 70
TOTAL_CHAOS_DURATION: 1800
RAMP_TIME:

Typically we expect the .spec.appinfo.appkind field in the chaosengine to be filled with the appropriate type (deployment/statefulset/daemonset). Also, the target container needs to be provided in the ENV override section. For ex:
# chaosengine.yaml
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: nginx-network-chaos
  namespace: default
spec:
  # It can be delete/retain
  jobCleanUpPolicy: 'delete'
  # It can be true/false
  annotationCheck: 'true'
  # It can be active/stop
  engineState: 'active'
  #ex. values: ns1:name=percona,ns2:run=nginx
  auxiliaryAppInfo: ''
  monitoring: false
  appinfo:
    appns: 'default'
    # FYI, To see app label, apply kubectl get pods --show-labels
    applabel: 'app=nginx'
    appkind: 'deployment'
  chaosServiceAccount: pod-network-loss-sa
  experiments:
    - name: pod-network-loss
      spec:
        components:
          env:
            #Container name where chaos has to be injected
            - name: TARGET_CONTAINER
              value: 'nginx'

            - name: LIB_IMAGE
              value: 'gaiaadm/pumba:0.6.5'

            #Network interface inside target container
            - name: NETWORK_INTERFACE
              value: 'eth0'

            - name: NETWORK_PACKET_LOSS_PERCENTAGE
              value: '100'

            - name: TOTAL_CHAOS_DURATION
              value: '60' # in seconds

In the previous comment, the "nginx-chaos-runner" I mentioned was the pod that gets launched immediately on creating the chaosengine. It bears the name "-runner" - The logs of this will help us to find out why the experiment is using invalid namespace etc.,
By default we delete this pod and the experiment pod immediately on completion. However in the spec.jobCleanupPolicy of chaosengine - we can use value retain to keep these pods after completion to help us troubleshoot.

Ah, now I get it ! I suppose you are using an example from here: https://github.com/litmuschaos/chaos-operator/blob/master/deploy/crds/chaosengine.yaml for your evaluation!
My Apologies, this is an old version which has undergone several changes since. Please refer to the https://docs.litmuschaos.io to find the latest specs and steps to run the experiments. Let me create an issue to fix it
BTW, we are still available on the hangout link I mentioned if you would like a quick chat about this/debug live!

Ah, now I get it ! I suppose you are using an example from here: https://github.com/litmuschaos/chaos-operator/blob/master/deploy/crds/chaosengine.yaml for your evaluation!
My Apologies, this is an old version which has undergone several changes since. Please refer to the https://docs.litmuschaos.io to find the latest specs and steps to run the experiments. Let me create an issue to fix it
BTW, we are still available on the hangout link I mentioned if you would like a quick chat about this/debug live!

It works,thanks much~

Thank you @badashanren for trying this out. While we will get better w/ our docs & instructions (as pointed out by this issue) - it would be great if you could share some feedback/thoughts around litmus in general - fixes/improvements/enhancements you would like to see in the project to help you better. Here is the roadmap for your reference.


URI.decode/encode is obsoleted. Use WEBrick::HTTPUtils.escape/unescape

URI.escape/unescape is obsoleted.
This methods are following RFC 2396.
However, RFC 2396 was obsoleted by RFC 3986.

https://tools.ietf.org/html/rfc2396
https://tools.ietf.org/html/rfc3986

Ruby core team says "Instead, use CGI.escape, URI.encode_www_form or URI.encode_www_form_component" but those methods are incompatible between URI.escape/unescape.
So, I choose WEBrick::HTTPUtils.escape/unescape instead, its compatible with URI.escape/unescape.
We need take off this obsoleted rfc dependent behavior in the future.
It shows many warning messages in Ruby 2.7.

Thanks!

Thank you! and I'm sorry, I misunderstood.
I said

It shows many warning messages in Ruby 2.7.

, but this warning messages from Ruby 1.9. https://github.com/ruby/ruby/commit/238b979f


Unable to load dashboard properties after dashboard opens awhile - Database dashboard

Issue Type: Bug

Connect a server and open dashboard
Open a query or notebook, do some db operations in OE.
Switch back to dashboard tab after half hour or awhile.

Noticed database dashboard has the following two issues. (Not sure how server dashboard is changed to db dashboard.)

Tasks are empty
Database properties are unable to load for cloud server in screenshot 1.

Azure Data Studio version: azuredatastudio 1.7.0 (1c694cbd3bfccbbd17cb68a65c7731ccc5f4e3dd, 2019-05-07T16:39:17.607Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.92GB (41.49GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (2)

Extension
Author (truncated)
Version

azuredatastudio-pgsql
Mic
0.1.0

profiler
Mic
0.7.0

Does this ever recover on its own (for example if you browse away and then back again, or try to do stuff on the dashboard to force a refresh such as edit)
Did you see if the console had any errors?
This was for an Azure server? Have you tested/seen it on any other server type?

@Charles-Gagnon
Once in such state, can't recover by  itself
Did see any error any where
Tasks are empty for BDC and cloud. Second image is BDC.

Closing older issues without recent repros.  Please let us know if you're still impacted by this issue.


unrecognized keyword :straight with built in version of use-package

What's wrong
I recently compiled Emacs from source. It has built in use-package. When trying to run my setup it fails with the error about unrecognized keyword :straight
Directions to reproduce

build Emacs directrly from emacs/HEAD
delete previous emacs.d to start from a blank slate
try the following minimal config

;;; package --- Summary
;;; Commentary:
;;; Code:

;;(package-initialize)

(let ((file-name-handler-alist nil))
  (require 'package)

(setq straight-repository-branch "develop")
(defvar bootstrap-version)
(let ((bootstrap-file
       (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
      (bootstrap-version 5))
  (unless (file-exists-p bootstrap-file)
    (with-current-buffer
        (url-retrieve-synchronously
         "https://raw.githubusercontent.com/raxod502/straight.el/develop/install.el"
         'silent 'inhibit-cookies)
      (goto-char (point-max))
      (eval-print-last-sexp)))
  (load bootstrap-file nil 'nomessage))

(straight-use-package 'use-package)

(use-package dash
  :straight t)

(use-package f
  :straight t)

(use-package async ;; :defer t
  :straight t)

(provide 'init))

;;; init.el ends here

It fails with the following errors

⛔ Error (use-package): Failed to parse package dash: use-package: Unrecognized keyword: :straight
⛔ Error (use-package): Failed to parse package f: use-package: Unrecognized keyword: :straight
⛔ Error (use-package): Failed to parse package async: use-package: Unrecognized keyword: :straight

Version information

Emacs version:
This is GNU Emacs 30.0.50 (build 7, x86_64-pc-linux-gnu, GTK+ Version 3.24.35, cairo version 1.17.6) of 2022-12-22

Operating system:
Linux fedora 6.0.15-300.fc37.x86_64

Try replacing:
(straight-use-package 'use-package)

with:
(straight-use-package-mode)

Actually,  bootstrap.el should already take care of that.
You may just be able to remove the (straight-use-package 'use-package) line.

Thank you @progfolio  adding (require 'use-package-core)  before bootstrap and  (use-package doct :straight t) worked for me. It might be worth adding it to the documentation if it is a must do when using builtin use-package.

Sorry I jumped the gun. It just cloned melpa and non-gnu-elpa and reverted back to the previous errors.

Please try evaluating the test case from above in your *scratch* buffer:
https://github.com/radian-software/straight.el/issues/1035#issuecomment-1367081185
When it finishes running the *straight-bug-report-process* buffer should pop up.
Please copy the entire buffer contents here.

It said  that lexial binding was required so I run  (setq lexical-binding t) before evaluating it.

Test Case
(straight-bug-report
  :pre-bootstrap
  (require 'use-package-core)
  :post-bootstrap
  (use-package doct :straight t))

Test run at: 2022-12-29 11:36:59
system-type: gnu/linux
straight-version: prerelease (HEAD -> develop, origin/develop) e407ed5 2022-12-26
emacs-version: GNU Emacs 30.0.50 (build 7, x86_64-pc-linux-gnu, GTK+ Version 3.24.35, cairo version 1.17.6) of 2022-12-22

Output
Bootstrapping straight.el...
Bootstrapping straight.el...done
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...done
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...done
Looking for emacsmirror-mirror recipe → Cloning el-get...
Looking for emacsmirror-mirror recipe → Cloning el-get...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done

Test run with version: prerelease (HEAD -> develop, origin/develop) e407ed5 2022-12-26
Cloning doct...
Cloning doct...done
Building doct...

What does your init file currently look like?

Currently I am running the config I mentioned above because I'm trying to start from scratch.

Was there any definitive solution for this issue? Running straight.el on the latest Emacs 29 version only works consistently when using my non-bytecompiled init.el file.
When loading with my byte-compiled init.elc, the native compilation yields the same error messages as mentioned above (e.g., "Error (use-package): Failed to parse package paradox: use-package: Unrecognized keyword: :straight"). The next time I restart Emacs, the initialization process encounters the following error: "Warning (initialization): An error occurred while loading ‘/Users/bram/.emacs.d/eln-cache/29.0.60-4bf8ba72/init-563b6df7-97eefad5.eln’:".
I tried with and without the suggested workaround ("(require 'use-package-core)").

@bramadams: See https://www.gnu.org/software/emacs/manual/html_node/elisp/Compiling-Macros.html
You'd likely have to wrap some forms in eval-and-compile or eval-when-compile to get that working.
Honestly, I wouldn't recommend compiling your init file. It's more trouble than it's worth. That's the official consensus, too:
https://www.gnu.org/software/emacs/manual/html_node/emacs/Init-File.html

Thanks a lot, @progfolio, this suggestion got it to work!
My full initialization code to make byte/native compilation work with straight.el on Emacs 29 (23/03/2023 snapshot):
(eval-and-compile
  (defvar bootstrap-version)
  (setq straight-repository-branch "develop") ; TEMPORARY issue with straight, see https://jeffkreeftmeijer.com/emacs-straight-use-package/
  (let ((bootstrap-file
         (expand-file-name "straight/repos/straight.el/bootstrap.el" user-emacs-directory))
        (bootstrap-version 6))
    (unless (file-exists-p bootstrap-file)
      (with-current-buffer
          (url-retrieve-synchronously
           "https://raw.githubusercontent.com/radian-software/straight.el/develop/install.el"
           'silent 'inhibit-cookies)
        (goto-char (point-max))
        (eval-print-last-sexp)))
    (load bootstrap-file nil 'nomessage))

  ;; Install use-package
  (straight-use-package '(use-package :type built-in))
  (require 'bind-key)
  (setq straight-use-package-by-default t))

I can confirm @bramadams 's solution works.
But as @progfolio points out, it's better not to byte compile the init file.

Having read the Emacs manual link @progfolio mentioned, I got a feeling I should try out disabling byte-compilation of my init file, thanks for the encouragement @lebensterben :-)

Yeah, you can definitely byte-compile the init-file, but it takes special handling and custom code to make it work right. Otherwise you'll get all manner of problems. https://github.com/radian-software/radian is one reference configuration for taking care of this with straight.el.


Fix trimv typo -> trim-v

Appreciated!

You are welcome Mike. Is there a way to contact you personally for helping me to find a job in the Sydney area? I'm from France and am planning to stay 6 months in an English speaking country. I'd understand a «No, sorry but no»<EMAIL_ADDRESS>


runtime/cgo: cgo can't work with some old versions glibc

Go version
go version go1.22.3 linux/amd64
Output of go env in your module/workspace:
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/root/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/root/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.3'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3943136906=/tmp/go-build -gno-record-gcc-switches'

What did you do?
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# docker run -dit --name=test busybox
0a20c06c6413ee5b417f5292ccdd95650d6206494c6f180060172e69e4f908e9
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# docker top test
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
root                354966              354946              0                   22:44               ?                   00:00:00            sh
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# # We want to enter the process with pid 354966's mount namespace
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# vim setns.go
root@iZj6cjf6t1l6rdg0tqzfrfZ:~#
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# go build -o setns setns.go
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# ./setns
enter mnt ns(3): 0
Segmentation fault

cat setns.go
package main

/*
#cgo CFLAGS: -Wall
#define _GNU_SOURCE
#include <errno.h>
#include <fcntl.h>
#include <pthread.h>
#include <stdlib.h>
#include <stdio.h>
#include <sched.h>
#include <unistd.h>

void test() {
        int fd = open("/proc/354966/ns/mnt", O_RDONLY);
        int r = setns(fd, CLONE_NEWNS);
        printf("enter mnt ns(%d): %d\n", fd, r);
}
void __attribute__((constructor)) init(void) {
        test();
}
*/
import "C"

import "fmt"

func main() {
        fmt.Println("hello world!")
}

What did you see happen?
The go program crashed: Segmentation fault
This is similar with the issue #65625, but not the same as it.
I wrote a c programe, and found that this is also a bug of pthread_getattr_np in some old glibc.
define _GNU_SOURCE
#include <errno.h>
#include <fcntl.h>
#include <pthread.h>
#include <stdlib.h>
#include <stdio.h>
#include <sched.h>
#include <unistd.h>

int main(int argc, char **argv) {
        //printf("%d\n", argc);
        int pid;
        sscanf(argv[1], "%d", &pid);
        char path[256];
        sprintf(path, "/proc/%d/ns/mnt", pid);
        int fd = open(path, O_RDONLY);
        int r = setns(fd, CLONE_NEWNS);
        printf("setns pidns(%d): %d\n", fd, r);
        pthread_attr_t attr;
        pthread_attr_init(&attr);
        r = pthread_getattr_np(pthread_self(), &attr);
        printf("getattr: %d\n", r);
}

root@iZj6cjf6t1l6rdg0tqzfrfZ:~# gcc -o setnsc setnsc.c -lpthread
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# ./setnsc 354966
setns pidns(3): 0
getattr: 2
root@iZj6cjf6t1l6rdg0tqzfrfZ:~# strace -f ./setnsc 354966
execve("./setnsc", ["./setnsc", "354966"], 0x7ffc612b61e0 /* 22 vars */) = 0
brk(NULL)                               = 0x556d6270a000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd12ad2890) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=25966, ...}) = 0
mmap(NULL, 25966, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f817b1e9000
close(3)                                = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220q\0\0\0\0\0\0"..., 832) = 832
pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\f\4K\246\21\256\356\256\273\203t\346`\6\0374"..., 68, 824) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=157224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f817b1e7000
pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\f\4K\246\21\256\356\256\273\203t\346`\6\0374"..., 68, 824) = 68
mmap(NULL, 140408, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f817b1c4000
mmap(0x7f817b1ca000, 69632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f817b1ca000
mmap(0x7f817b1db000, 24576, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7f817b1db000
mmap(0x7f817b1e1000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c000) = 0x7f817b1e1000
mmap(0x7f817b1e3000, 13432, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f817b1e3000
close(3)                                = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300A\2\0\0\0\0\0"..., 832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0<EMAIL_ADDRESS>784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32, 848) = 32
pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\356\276]_K`\213\212S\354Dkc\230\33\272"..., 68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029592, ...}) = 0
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0<EMAIL_ADDRESS>784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32, 848) = 32
pread64(3, "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\356\276]_K`\213\212S\354Dkc\230\33\272"..., 68, 880) = 68
mmap(NULL, 2037344, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f817afd2000
mmap(0x7f817aff4000, 1540096, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7f817aff4000
mmap(0x7f817b16c000, 319488, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19a000) = 0x7f817b16c000
mmap(0x7f817b1ba000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f817b1ba000
mmap(0x7f817b1c0000, 13920, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f817b1c0000
close(3)                                = 0
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f817afcf000
arch_prctl(ARCH_SET_FS, 0x7f817afcf740) = 0
mprotect(0x7f817b1ba000, 16384, PROT_READ) = 0
mprotect(0x7f817b1e1000, 4096, PROT_READ) = 0
mprotect(0x556d60a62000, 4096, PROT_READ) = 0
mprotect(0x7f817b21d000, 4096, PROT_READ) = 0
munmap(0x7f817b1e9000, 25966)           = 0
set_tid_address(0x7f817afcfa10)         = 355143
set_robust_list(0x7f817afcfa20, 24)     = 0
rt_sigaction(SIGRTMIN, {sa_handler=0x7f817b1cabf0, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f817b1d8420}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {sa_handler=0x7f817b1cac90, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f817b1d8420}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
openat(AT_FDCWD, "/proc/354966/ns/mnt", O_RDONLY) = 3
setns(3, CLONE_NEWNS)                   = 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x1), ...}) = 0
brk(NULL)                               = 0x556d6270a000
brk(0x556d6272b000)                     = 0x556d6272b000
write(1, "setns pidns(3): 0\n", 18setns pidns(3): 0
)     = 18
openat(AT_FDCWD, "/proc/self/maps", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(1, "getattr: 2\n", 11getattr: 2
)            = 11
exit_group(0)                           = ?
+++ exited with 0 +++

What did you expect to see?
Should see hello world! in the output, looks like in go 1.22.3 with glibc 2.35.
root@iZj6c2w08pe0hl9lwk8mdiZ:~# go version
go version go1.22.3 linux/amd64
root@iZj6c2w08pe0hl9lwk8mdiZ:~# ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.7) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
root@iZj6c2w08pe0hl9lwk8mdiZ:~# go build -o setns setns.go
root@iZj6c2w08pe0hl9lwk8mdiZ:~# ./setns
enter mnt ns(-1): -1
hello world!

@ianlancetaylor May I ask you some tech questions, if you can show me some datailed explanations, it will be appreciated.

I think the stack low address and the stack size are pthread's private data, why we need to get these data in cgo?
Why we choose using pthread_getattr_np to get the stack low address instead of __builtin_frame_address(0) + 4096 - size which has been used for many years before go 1.22.

Besides this issue and #65625 , we have found two issues about swith to pthread_getattr_np, and we can't sure that there is no other issues for pthread_getattr_np in old versions glibc. So I think we should consoder some ways to dertermine how to have a backward compatibility with previous versions. I have some ways to discuss:

switch back to __builtin_frame_address(0) + 4096 - size;
using __GLIBC_PREREQ(maj, min) macro to check glibc's version;
fail back to __builtin_frame_address(0) + 4096 - size. (Like the Patch Set 4 in https://github.com/golang/go/pull/67328#issuecomment-2119257356 / https://go-review.googlesource.com/c/go/+/585019, obviously need rebase)

Looking forward to your reply.
And welcome some other people's opinions.
Thanks a lot.

As we should know that if apply the patch https://go-review.googlesource.com/c/go/+/587919 , it can really make the program work, but the low address is 0, I don't know whether it will let the programme in a dangerous state or not.

I think the stack low address and the stack size are pthread's private data, why we need to get these data in cgo?

They aren't strictly private data, as shown by the fact that there are functions that return them.

Go uses an automatically extensible stack. In order to implement that, the start of every function checks whether the stack is close to the bounds. That means that we need to know the stack bounds in order to run Go code. In particular, when a thread started by C code calls into Go code, we need to know the stack bounds in order to run the Go code. See callbackUpdateSystemStack in runtime/cgocall.go.

Why we choose using pthread_getattr_np to get the stack low address instead of __builtin_frame_address(0) + 4096 - size which has been used for many years before go 1.22.

See #59294 and https://go.dev/cl/479915.
I don't think we should make any changes for older versions of glibc until we find specific problems that we can test.

Thanks your explanation, I agree your opinion. Because it has no impact for normal users, just only for container runtime written by golang.
Looking forward go 1.22.4, thanks a lot.

As we should know that if apply the patch https://go-review.googlesource.com/c/go/+/587919 , it can really make the program work, but the low address becomes 0, I don't know whether it will let the programme in a dangerous state or not.

@lifubang Given that the problems we know about will be fixed in Go 1.22.4, is there anything else to be done here? Thanks!

Given that the problems we know about will be fixed in Go 1.22.4, is there anything else to be done here? Thanks!

After looked into the code, I think there is maybe no other thing needs to be worked here. Because in cgo we have aleady checked whether the low address returned by pthread libaray is zero or not:
https://github.com/golang/go/blob/master/src/runtime/cgocall.go#L302-L305
So, this one can be closed.


Any chance to add Virpil Panels so we can use just one program to manage different panels?

https://github.com/charliefoxtwo/ViLA
https://github.com/Nereid42/VLEDCONTROL

These are some existing community written projects that effect status lights. etc.

Hi,
it should be possible but the problem is getting the hardware. Generally we do not want to purchase hardware.

Would you only need one VPC device or each kind to make it compatible?
I could try to find something used and mail it.

Would need one of each model to be sure the code works. But I am not familiar with these at all, how the various models differ etc. And there are two of us developing so. That is the problem.


Github wiki docs: Broken link regarding mTLS troubleshoot

Bug Description
Hey guys!
https://github.com/istio/istio/wiki/Mutual-TLS-TroubleShooting
This link have multiple broken links that would help us to fix our issues regarding mTLS / HTTPS / Certificates.
Version
istioctl version
client version: 1.17.1
control plane version: 1.17.1
data plane version: 1.17.1 (9 proxies)

kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.26.1
Kustomize Version: v4.5.7
Server Version: v1.25.3

helm version --short

Additional Information
not relevant

I will try to fix them

@adamSplendex ptal

Good thank you this helped! We didn't find these parts exactly! Thank you!


LUNAR #1435 - add script for harvesting core dumps

Coverage increased (+0.2%) to 76.993% when pulling b7a4a7556c39f1b32edada8db904234bff11239a on amarcine:master into e9a39ce39c9287be2a62d73c2cda41f90da171bf on contiv:master.


fix(middleware): solved function viteServePublicMiddleware will be the first to deal with the index.html url and return the static index.html

Description
fixed #11920
What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Why do you have a index.html in both root and publicDir? That sounds like it'll cause more issues down the road.

Why do you have a index.html in both root and publicDir? That sounds like it'll cause more issues down the road.

company level projects need supporting vue-cli and Vite to start the development
we encountered this problem. we found it was this problem

I think it is better to use only one or the other, otherwise you'd need to find a workaround at the meantime. The current behaviour makes sense to me as if a raw public file is found, it should always have higher priority. This PR also break HTML in public files if the user wants it intentionally.

I think it is better to use only one or the other, otherwise you'd need to find a workaround at the meantime. The current behaviour makes sense to me as if a raw public file is found, it should always have higher priority. This PR also break HTML in public files if the user wants it intentionally.

okey. i think you are right i should use one of two. change webpack config or vite config can handle this.
and
I noticed that there is no description of the priority of static files in the vite documentation. Should we add a description of the priority of static files in the documentation?
just like "root file and public file can not use index.html at same time Unless you did it on purpose"

Should we add a description of the priority of static files in the documentation?
just like "root file and public file can not use index.html at same time Unless you did it on purpose"

Yeah that sounds like a great addition if you can find spot in the docs to note it. I think the logic works generically as say you have a SSR route at /foobar.json, if you have a public file called foobar.json, the public file will take highest priority too. I believe this is how most SSR frameworks work now.
I'll close this PR for now.

Should we add a description of the priority of static files in the documentation?
just like "root file and public file can not use index.html at same time Unless you did it on purpose"

Yeah that sounds like a great addition if you can find spot in the docs to note it. I think the logic works generically as say you have a SSR route at /foobar.json, if you have a public file called foobar.json, the public file will take highest priority too. I believe this is how most SSR frameworks work now.
I'll close this PR for now.
Thank you for taking the time to answer my questions. thanks a lot

Should we add a description of the priority of static files in the documentation?
just like "root file and public file can not use index.html at same time Unless you did it on purpose"

Yeah that sounds like a great addition if you can find spot in the docs to note it. I think the logic works generically as say you have a SSR route at /foobar.json, if you have a public file called foobar.json, the public file will take highest priority too. I believe this is how most SSR frameworks work now.
I'll close this PR for now.

Thank you for taking the time to answer my questions. thanks a lot


make latch counter_ protected for deriving latch in hpxmp

@tianyi93 After thinking about this some more, we should have made all members protected, if for nothing else but consistency...

@hkaiser Yes, I will do that.


⚠🐞BUG: smallint is not defined in introspected schema.ts

I personally think this is a kind of critical bug🐞.
When I'm introspecting my local mysql database, in the generated schema.ts file, smallint is not imported hence resulting in this:

The generated code with error is below (this is the only table I have with smallint):

Once I manually added smallint import from drizzle-orm/mysql-core, everything works well.

Other than that, there are also 2 unused imports but they are trivial.

⚠This is critical to me
because I'm managing the migration & other db stuffs in another backend repo. In this one I'm just using Next.js and drizzle-orm to simply fetching and mutating some tables in DB, for some simple functionalities.
So my plan is run the introspection in CI/CD pipeline everytime (with status.ts in .gitignore) code is deployed.
Please have a look, thanks.

should not be an issue on latest(0.30.0+), if it's still an issue - please reopen


add time commitements for experts and break down into possible bullet…

… points
only a small change really! :)

Thanks !


libvirt_volume with base_volume_id creates file with wrong permissions

System Information
Linux distribution
Ubuntu 19.10
Terraform version
Terraform v0.12.10

Provider and libvirt versions
/home/wonko/.terraform.d/plugins/terraform-provider-libvirt 0.6.0+git.1569597268.1c8597df
Compiled against library: libvirt 4.0.0
Using library: libvirt 5.4.0
Running hypervisor: QEMU 4.0.0
Running against daemon: 5.4.0

Description of Issue/Question
The base libvirt_volume gets created correctly with the right user:group. The volumes that are built from that are getting set to root:root as owner which means the VMs can't actually start because the user attempting to start the VMs (me!) doesn't have permission to those files.
wonko@deepthought:/var/lib/libvirt $ sudo ls -lh images
total 283G
-rw------- 1 wonko kvm   21G Oct 11 09:55 debian9.qcow2
-rw-r--r-- 1 wonko kvm  2.8G Oct 15 16:22 k8s
-rw-r--r-- 1 root  root 194K Oct 15 16:22 k8s_worker_root_volume-0
-rw-r--r-- 1 root  root 194K Oct 15 16:22 k8s_worker_root_volume-1
-rw-r--r-- 1 root  root 194K Oct 15 16:22 k8s_worker_root_volume-2
-rw-r--r-- 1 root  root 194K Oct 15 16:22 k8s_worker_root_volume-3
-rw-r--r-- 1 root  root 194K Oct 15 16:22 k8s_worker_root_volume-4
-rw------- 1 root  root  21G Oct 15 16:20 openbsd6.2.qcow2
-rw------- 1 wonko kvm  201G Oct 15 13:50 win10-1.qcow2
-rw------- 1 wonko kvm   41G Oct 15 13:50 win10.qcow2

Setup
main.tf:
  default = 2
}

variable "num_workers" {
  default = 3
}

resource "libvirt_volume" "k8s" {
  name   = "k8s"
  source = "http://deepthought.REDACTED.net/images/centos7-base.qcow2"
}

module "k8s-workers" {
  source = "./modules/VM"
  name = "worker"
//  network_id = libvirt_network.tf-k8s.id
  source_volume_id = libvirt_volume.k8s.id
  num_vms = 5
  vcpu = 4
  memory = 8192
}

modules/VM/main.tf:
resource "libvirt_volume" "root_volume" {
  name           = "${var.name_prefix}_${var.name}_root_volume-${count.index}"
  base_volume_id = var.source_volume_id
  count          = var.num_vms
}

// set boot order hd, network
resource "libvirt_domain" "virtual_machine" {
  name   = "${var.name_prefix}-${var.name}-${count.index}"
  memory = var.memory
  vcpu   = var.vcpu
  autostart = var.autostart
  qemu_agent = var.qemu_agent

  network_interface {
    network_name = "br.k8s"
    wait_for_lease = true
  }

  boot_device {
    dev = ["hd", "network"]
  }

  disk {
    volume_id = libvirt_volume.root_volume[count.index].id
  }

  graphics {
    type        = "spice"
    listen_type = "address"
  }

  console {
    type = "pty"
    target_port = "0"
    target_type = "serial"
  }

  count = var.num_vms

  provisioner "remote-exec" {
    inline = [
      "hostnamectl set-hostname ${self.name}",
      "systemctl stop firewalld",
      "systemctl disable firewalld",
      "systemctl mask --now firewalld",
      "yum install -y nfs-utils",
    ]

    connection {
      host     = self.network_interface[0].addresses[0]
      type     = "ssh"
      user     = "root"
      password = "REDACTED"
    }
  }
}

Steps to Reproduce Issue
Run terraform apply

Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration? No

@bhechinger  Are you sure you have checked this https://github.com/dmacvicar/terraform-provider-libvirt/issues/546#issuecomment-467151566 ?
I don't have any issue with Fedora 31 and 0.6.0

I am having exactly the same issue on ubuntu 18.04 LTS, with Terraform 0.12 and terraform-provider-libvirt 0.6.0.

@infwonder from experience and knowledge the volume creation is not something the provider manage.
The provider is an executable like terraform and we don't set any permission during code.
This is delegate to libvirt and OS which are things we don't maintian and control. So this is issue is more a OS system one. which can vary from setting of systems, user and so on

Thank you @MalloZup
and yes after some fiddling with OS I was able to finish terraform apply by disabling qemu security_driver. I will look into proper SELinux tag or AppArmor setup.

welcome! enjoy! and feel free to ping us via chat or issues..


AzCopy should not scan exclude path

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
azcopy version 10.8.0
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy sync "https://[SourceStorageAccount].file.c
ore.windows.net/jenkins?[SASToken]" "https://[TargetStorageAccount].file.core.windows.net/jenkins-backup-6111/2020-12-15?[SASToken]" --recursive=true --preserve-smb-permissions=true --exclude-path=".cache"
What problem was encountered?
AzCopy stopped during scanning the source storage account.
Here is the log
INFO: Any empty folders will be processed, because source and destination both support folders. For the same reason, permissions defi
ned on folders will be processed

Job 62b4c14a-ef11-8745-5864-611c7dbf41d9 has started
Log file is located at: /root/.azcopy/62b4c14a-ef11-8745-5864-611c7dbf41d9.log

0 Files Scanned at Source, 37619 Files Scanned at Destination
Cannot perform sync due to error: -> github.com/Azure/azure-storage-file-go/azfile.newStorageError, /home/vsts/go/pkg/mod/github.com/
!azure/azure-storage-file-go@v0.6.1-0.20201111053559-3c1754dc00a5/azfile/zc_storage_error.go:42
===== RESPONSE ERROR (ServiceCode=DeletePending) =====
Description=409 The specified resource is marked for deletion by an SMB client., Details: (none)
   HEAD https://saa5a05e4aad859ba59d50.file.core.windows.net/jenkins/.cache/JNA/temp/jna1415416010471507020.tmp?se=2020-12-17t00%3A20
%3A39z&sig=-REDACTED-&sp=rwlc&spr=https&srt=sco&ss=f&st=2020-12-16t16%3A20%3A39z&sv=2019-12-12&timeout=901
   User-Agent: [AzCopy/10.8.0 Azure-Storage/0.8.0 (go1.13; linux)]
   X-Ms-Client-Request-Id: [3f8ba798-38e1-48c0-6440-ed5de28a75b9]
   X-Ms-Version: [2020-02-10]
   --------------------------------------------------------------------------------
   RESPONSE Status: 409 The specified resource is marked for deletion by an SMB client.
   Date: [Wed, 16 Dec 2020 16:27:28 GMT]
   Server: [Windows-Azure-File/1.0 Microsoft-HTTPAPI/2.0]
   X-Ms-Client-Request-Id: [3f8ba798-38e1-48c0-6440-ed5de28a75b9]
   X-Ms-Error-Code: [DeletePending]
   X-Ms-Request-Id: [7b39902d-301a-0036-58c8-d3a30e000000]
   X-Ms-Version: [2020-02-10]

How can we reproduce the problem in the simplest way?
We have a Jenkins setup in which the jenkins_home is set to the file share in Azure storage account.
AzCopy sync command is used to backup the jenkins_home folder while Jenkins is running.
When Jenkins stops, the issue is also gone.
Not sure if there is another way to mark a file as DeletePending. If so, the issue could be reproduced easier.
Have you found a mitigation/solution?
No

I tried to repro this and sync with exclude-path works fine now. Please try the latest version of AzCopy and let us know if there are any issues!


Fix remove_italics not having an effect

It looks like remove_italics stopped working in 5b446a3394f28e1ba3ddb11dd46c3ca4343bd9d8 when configuration of italics moved from the style key to its own italic key. This change makes remove_italics edit the new italic key instead of the old style key.

Thanks for the PR!


Improper handling in register view when authy_user not OK

Line 36 of twofa/views.py should be:
for key, value in authy_user.errors().items():
or else a ValueError will be thrown for too many values to unpack

Thanks @cernerae we have added in your fix!


Uses official ollama testcontainers

Closes langchain4j#2101

@langchain4j I think the best way right now is to cache docker image (like langchain4j-ollama do, pull model and commit to new docker image). WDYT?

@Martin7-1 do you mean revert to the existing logic?

@langchain4j Yes. What we do now is just migrating from GenericContainer to OllamaContainer. But we can still have our own private docker image for testing. WDYT?

@Martin7-1 you're right! We should probably revive https://hub.docker.com/search?q=langchain4j
But I am surprised ollama does not provide official images for most popular models yet

@Martin7-1 you're right! We should probably revive https://hub.docker.com/search?q=langchain4j But I am surprised ollama does not provide official images for most popular models yet

I found another Ollama image which just support CPU version: https://hub.docker.com/r/alpine/ollama. Maybe it's enough for us as I think our tests are all run on CPU (Github Actions or locally).
This image is just ~70MB compared to the original Ollama image is ~4GB.

And, all Ollama models are stored at ~/.ollama, what about mounting it to container? It will reduce the time Ollama pull model.

This will work for local env, but not for running on github CI, right?

Maybe we can use actions/cache@v3 to cache ~/.ollama in Github Actions. But Github Actions can only cache 10GB files...

It seems that the slowest part is downloading the model from the ollama hub. And it seems that downloading container with backed-in model from docker hub is faster? IDK, just my feeling.

Maybe integrate them (alpine/ollama and ~/.ollama cache) will make it faster. But huge model size will execeed Github Actions cache limit I thinik...

Maybe we can use actions/cache@v3 to cache ~/.ollama in Github Actions. But Github Actions can only cache 10GB files...

Does it actually work? In my experience, caching (e.g. maven cache) does not really work on github actions. Or maybe I am doing something wrong

If you have a bit of time and want to spend it on this, I would compare download speeds from docker and from ollama hubs and calculate which option is faster :)

Does it actually work? In my experience, caching (e.g. maven cache) does not really work on github actions. Or maybe I am doing something wrong

Hmmm... Let me test it.

If you have a bit of time and want to spend it on this, I would compare download speeds from docker and from ollama hubs and calculate which option is faster :)

Thank you! I think I will focus on it recently as langchain4j-ollama is an important part of the whole project. And ensure the integration test (locally or github actions) is indeed importatnt.
I will check whether Github Actions cache works or not.

@Martin7-1 thank you so much for your help! ❤


Add a development profile to Maven

Add a development profile that allow to skip following things during project installation:

Running Findbugs checks;
Generating Javadoc;
Creating a verifying a sample project from the archetype;
Generating a shadowed artifact for the example project.

This allows to decrease the time to clean and install project from 4-5 minutes to 20-30 seconds during development.

LGTM, thanks!


feat(appeal): add appeal feature

Pull Request Test Coverage Report for Build 646

9 of 13 (69.23%) changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 44.192%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/contracts/implementations/arbitrable/ArbitrableTransaction.js
3
5
60.0%

src/contracts/implementations/arbitrator/KlerosPOC.js
4
6
66.67%

Totals

Change from base Build 642:
0.2%

Covered Lines:
428

Relevant Lines:
846

💛  - Coveralls


Wine: Unhandled Exception

Hi the start script hold.
hear the tail of the log:
space-engineers-dedicated-docker-linux |    at SpaceEngineersDedicated.MyProgram.Main(String[] args)
space-engineers-dedicated-docker-linux | wine: Unhandled exception 0xe0434352 in thread d8 at address 000000007B01129D (thread 00d8), starting debugger...
space-engineers-dedicated-docker-linux | ls: cannot access '/appdata/space-engineers/Plugins/*.dll': No such file or directory
space-engineers-dedicated-docker-linux | WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
space-engineers-dedicated-docker-linux | Redirecting stderr to '/home/wine/Steam/logs/stderr.txt'
space-engineers-dedicated-docker-linux | [  0%] Checking for available updates...
space-engineers-dedicated-docker-linux | [----] Verifying installation...
space-engineers-dedicated-docker-linux | Steam Console Client (c) Valve Corporation
space-engineers-dedicated-docker-linux | -- type 'quit' to exit --
space-engineers-dedicated-docker-linux | Loading Steam API...OK
space-engineers-dedicated-docker-linux |
space-engineers-dedicated-docker-linux | Connecting anonymously to Steam Public...OK
space-engineers-dedicated-docker-linux | Waiting for client config...OK
space-engineers-dedicated-docker-linux | Waiting for user info...OK
space-engineers-dedicated-docker-linux | "@sSteamCmdForcePlatformType" = "windows"
space-engineers-dedicated-docker-linux | Success! App '298740' already up to date.
space-engineers-dedicated-docker-linux | /entrypoint-space_engineers.bash: line 3: /home/wine/.bash_profile: No such file or directory
space-engineers-dedicated-docker-linux |
space-engineers-dedicated-docker-linux | Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'netstandard, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. Exception from HRESULT: 0x8009001D
space-engineers-dedicated-docker-linux |    at SpaceEngineersDedicated.MyProgram.Main(String[] args)
space-engineers-dedicated-docker-linux | wine: Unhandled exception 0xe0434352 in thread d4 at address 000000007B01129D (thread 00d4), starting debugger...

Hey,
Sorry, I can't provide support for personal installations here, it's your mileage may vary. If there's a widespread issue I will take a look, but I can't guarantee compatibility with every distro or machine.

Have you used this before, and are now just encountering this on a new world? Or is this the first time you are trying it?

The img never worked
On Tue, Sep 7, 2021, 19:05 mmmaxwwwell @.***> wrote:

Have you used this before, and are now just encountering this on a new
world? Or is this the first time you are trying it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mmmaxwwwell/space-engineers-dedicated-docker-linux/issues/19#issuecomment-914475199,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQWISTEJODNNZH2TOIWX3WTUAZA5XANCNFSM5DPCLNQQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I'm using ubuntu server 20.04 and docker-compose and i followed the install instructions, with the ./start script
I can provide more information if needed, like log.files or programm versions
Please help I would realy love if this would work
So long, and thanks for all the fish!

 I'll add you to my discord and would kontakt you on the weekend, if that would be okay for you.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61002

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/80495

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86142

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107296

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/109845

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113673

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120438


Main readme example doesn't work with Oak current

Hi, thanks for making this, it seems cool (and the Bedrock team selected it, so it must be good)!
I'm a not-so-good JS developer, but am experimenting with this.
I tried to use the Readme example with Deno, and got this error:
c@macmini ~/D/r/oak_sessions> deno run ./foo.ts
Check file:///Users/c/Documents/react/oak_sessions/foo.ts
error: TS2345 [ERROR]: Argument of type '(ctx: Context, next: () => Promise<unknown>) => Promise<void>' is not assignable to parameter of type 'Middleware<State, Context<State, AppState>>'.
  Types of parameters 'ctx' and 'context' are incompatible.
    Type 'Context<State, AppState>' is not assignable to type 'Context<State, Record<string, any>>'.
      Types of property 'app' are incompatible.
        Type 'Application<AppState>' is not assignable to type 'Application<Record<string, any>>'.
          Property '#contextState' in type 'Application' refers to a different member that cannot be accessed from within type 'Application'.
app.use(session.initMiddleware())
        ~~~~~~~~~~~~~~~~~~~~~~~~
    at file:///Users/c/Documents/react/oak_sessions/foo.ts:19:9

I had no idea what to do with that error.
Luckily, I found one of the Oak versions this was authored with in the file 'deps.ts'
By modifing the Readme example to use the same Oak version, the Readme example runs fine.
Maybe you want to change the Readme to include the Oak version, so it works for others out of the box?
Anyway, thanks for making & sharing this!

Thanks for the feedback. This will become less of an issue when Deno stops type-checking when running a program by default, but it should be made more clear in the README for now.
Another way to solve this in the future if there's a version mismatch, just add the --no-check argument when running the app. This is the same behavior as Deno Deploy.

Now that Deno 1.23 defaults to not running a type-check on deno run by default, the readme example should work regardless of type issues. It will still show up in the IDE text highlighting as an error, so we'll still have to keep up on the Oak version updates, but I'm sure we'll figure something out.
https://deno.com/blog/v1.23#no-type-checking-by-default

Any idea what we would need to do to fix the type error? I prefer to only ship code that type checks.


Generate fields annotation

C++ UDTFs generates field annotations to name cursor arguments. This PR adds the same for RBC.

LGTM! Just tested this and it does work for my branch for heavydb PR 6652.


want to Add Confetti Celebration on winning

before:

Proposed change
https://github.com/user-attachments/assets/70bf1e35-cd9d-4e1a-892b-dbc7908e5f97
please assign me this issue under suitable labels
thank you !

i also added animation, please check!!

Hi @iamparas0 please assign this issue


Create Event Activation CR for Github Events

Description
Defining an Event Activation Custom Resource for events that are currently implemented in Github Connector (which for now are 'issue opened' and 'pull request review comment') is necessary for Lambda triggering. Those should be automatically deployed with our Helm Chart as part of Github Connector deployment.
AC

[ ] Event Activation CR for 'issue opened' event
[ ] Event Activation CR for 'pull request review comment' event
[ ] Adding CRs above to existing Helm Chart structure so they're included in Github Connector deployment

There was a suggestion to look into this e2e test as it does some of the things that may suit our needs in case of automation the process of creating CRs.

According to (Kyma documentation)[https://kyma-project.io/docs/components/application-connector#architecture-application-broker-provisioning-and-binding-for-an-event-serviceclass] "During the provisioning process, the EventActivation resource is created together with the ServiceInstance.". This was proven on our existing infrastructure, where only ServiceInstance is created from Helm Chart. Running:
k get eventactivations.applicationconnector.kyma-project.io -n flying-julia 8cee79e8-7b4e-453b-8b6a-3d9eb0677fbc -o yaml

as an example returns:
apiVersion: applicationconnector.kyma-project.io/v1alpha1
kind: EventActivation
metadata:
  creationTimestamp: 2019-08-05T08:16:16Z
  finalizers:
  - eventactivation.finalizers.kyma-project.io
  generation: 1
  name: 8cee79e8-7b4e-453b-8b6a-3d9eb0677fbc
  namespace: flying-julia
  ownerReferences:
  - apiVersion: servicecatalog.k8s.io/v1beta1
    kind: ServiceInstance
    name: lambda-test-4a6c6-damaged-hall
    uid: 4b64e7d2-b759-11e9-bdfe-267c9c7e8f90
  resourceVersion: "44422"
  selfLink: /apis/applicationconnector.kyma-project.io/v1alpha1/namespaces/flying-julia/eventactivations/8cee79e8-7b4e-453b-8b6a-3d9eb0677fbc
  uid: 4bd00ece-b759-11e9-9342-42010a8401a0
spec:
  displayName: lambda-test
  sourceId: lambda-test-app

which has all the fields marked as mandatory ergo it is not necessary to add EventActivation to our Helm Chart structure - Kyma handles it.


Can't log in

i was told about this launcher and was really excited to try it but whenever i try to log in this shows in the log
Caused by: java.lang.ClassNotFoundException: javax.xml.ws.http.HTTPException
i am not too experienced on java and i'd like to know how to fix it

Sounds like it has to do with Java libraries. What version launcher and
Java?
On Mon, Nov 22, 2021 at 13:41 gayfieri @.***> wrote:

i was told about this launcher and was really excited to try it but
whenever i try to log in this shows in the log
Caused by: java.lang.ClassNotFoundException:
javax.xml.ws.http.HTTPException
i am not too experienced on java and i'd like to know how to fix it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ModificationStation/Glass-Launcher-Legacy/issues/4,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJN2B3JT6SMPUBQYD2JZL5LUNKMIPANCNFSM5IRZ46BA
.

Java 17, glass launcher 0.4.5

There’s the problem, 0.4.5 is broken. You’ll have to build 0.5.
On Mon, Nov 22, 2021 at 15:11 gayfieri @.***> wrote:

Java 17, glass launcher 0.4.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ModificationStation/Glass-Launcher-Legacy/issues/4#issuecomment-975921784,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJN2B3KHLIR77A74Z7KUJBLUNKWXJANCNFSM5IRZ46BA
.

Heads up that glass-launcher does not support java versions other than eight, so you know.
Closing for now, feel free to reopen the issue if your problem persists, even if you are using java 8.

I’m up for sorting issues with 17, since it is LTS now.
On Mon, Nov 22, 2021 at 17:41 calmilamsy @.***> wrote:

Closed #4
https://github.com/ModificationStation/Glass-Launcher-Legacy/issues/4.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ModificationStation/Glass-Launcher-Legacy/issues/4#event-5657282197,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJN2B3LNDOG4624FX6JAZJLUNLIMFANCNFSM5IRZ46BA
.

The versions of Minecraft that this launcher supports do not work on Java 17 at all,

That's a great point.
On Tue, Nov 23, 2021 at 4:38 PM calmilamsy @.***> wrote:

The versions of Minecraft that this launcher supports do not work on Java
17 at all,
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ModificationStation/Glass-Launcher-Legacy/issues/4#issuecomment-977236729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJN2B3ODALCU3A27YZAM4GTUNQJXFANCNFSM5IRZ46BA
.


Any way to tell a user you visited their profile?

I didn't see a way to do this. I know this happens automatically for free accounts, but A-list members can browse anonymously and manually notify users that you visited their profiles. I guess a workaround for now is to just disable anonymous browsing.

@mconigliaro /anyone else who is interested in this feature. Can you test https://github.com/IvanMalison/okcupyd/tree/stalk_profile to make sure it works? It would be super cool if you could also record the vcrpy cassette that is used in testing for the test_stalk test.
This should simply amount to putting your credentials in the file test_credentials.py, and then run inv r test_stalk. Obviously your credentials will be scrubbed from the recording. (the code that does this lives here: https://github.com/IvanMalison/okcupyd/blob/master/okcupyd_testing/util.py#L62)

I found that doing profile.gender() seems to create the request you desire (that is, appear in their visitor logs).

@chrism2671

Don't you mean profile.gender?
this will be true of any profile attribute, but only so long as invisible browsing is turned off. This is actually an unfortunate side effect of the way the libary works
@mconigliaro is asking for a way to do this when you have invisible browsing turned on.

Ah my mistake!
Out of curiosity, why is this 'unfortunate'?
Incidentally, have you been banned by OKC yet? Just trying to understand what suitably conservative behaviour is.

Out of curiosity, why is this 'unfortunate'?
@chrism2671 It's unfortunate because that it means that simply using this library with an unpaid account will result in lots of possibly unintended profile views. That is why i decided to delay the retrieval of profile information to the last possible moment.

Incidentally, have you been banned by OKC yet? Just trying to understand what suitably conservative behaviour is.

Yes, as I mentioned above, all of the accounts, as well as my home IP address have been banned from okcupid. The behavior of some of my accounts was highly irregular (beyond what most people would typically use this library for), and I imagine that simply using okcupyd to, for example, backup all of your messages or something like that will not incur okcupid's wrath. If you want to do stuff that involves on the order of 100s or 1000s of profiles/requests, I would advise some caution. Using the profile copy functionality is another thing that could get you banned.

@chrism2671if you could help test this feature I would really appreciate it. Do you have an a-list account?

Sorry for the delay, been on holiday! I don't have an A-list account at the moment, but I might sign up for one in due course.
In my script, that involves visiting a lot of profiles repeatedly, I inserted:
import random
import time
sleep_time = random.gauss(10,5)
time.sleep(sleep_time)

between requests, which seemed to keep okc happy (for now).

Good to know they've started banning accounts. I was using 2-4 second delays between requests to profiles. This is a good motivation for issue #44.


Add idNyplSourceId convenience prop to item serialization

This PR patches a previous edit to add nyplSource information to item serialization. This patch copies the source information into a more readily usable idNyplSourceId property using bibframe identifier style. E.g.
    ...
    "accessMessage": [
        {
            "@id": "accessMessage:2",
            "prefLabel": "ADV REQUEST"
        }
    ],
    "idBarcode": [
        "AR02092018"
    ],
    "idNyplSourceId": {
        "@type": "SierraNypl",
        "@id": "8962503"
    }
    ...

Hey @saverkamp , can you let me know if that looks right before we merge it?

For the value of the identifier I would use @value instead of @id (@id is used for URIs, @value is used for strings following a specific syntax, like an identifier pattern). Otherwise, looks great!

Ah right! Updated:
"idNyplSourceId": {
    "@type": "SierraNypl",
    "@value": "8962503"
}


Constant minor CPU usage while using node-sqlite3

Writing an Electron application, noticed that its CPU usage is constantly around 13-18% even when idling.
I think I have isolated the cause to node-sqlite3, as CPU usage is < 1% when disabling all DB calls entirely.
Examined the process using Process Hacker, it seems that there is one thread on each CPU constantly creating and closing files.

Is this expected behavior, or am I doing something wrong? The database connection is created on startup and kept open until the application closes.
The CPU usage persists regardless of the database mode (readonly/readwrite/create), and even when using :memory: as the database filename.

Thank you for the bug report,
I am unaware what would cause this. I will try and replicate this on Linux but I see some references to  libuv  which is a cross platform library. I have seen strange things come from there, especially on windows.
Would be nice to figure out what is causing this.

@u2892 Would you be able to provide a minimal reproduction and re-open with an issue template? 🙂