Error building client - linking to libunwind?

Description
Unable to build android client.
I am new to ALVR and Android Development/RUST but well versed with C++ development on Ubuntu. I was successful in building the streamer.
Thanks in advance for any help!
I am targeting using ALVR after this commit -> for this feature
The following shows the error when building the client - linking to libunwind
~/ALVR/ALVR$ export JAVA_HOME=/usr/lib/jvm/default-java/bin
~/ALVR/ALVR$ export ANDROID_HOME=$HOME/Android/Sdk
~/ALVR/ALVR$ export ANDROID_NDK_HOME=/usr/lib/android-sdk/ndk-bundle
~/ALVR/ALVR$ cargo xtask prepare-deps --platform android --release &>/dev/null
~/ALVR/ALVR$ cargo xtask build-client --release
   Compiling bincode v1.3.3
   Compiling settings-schema v0.2.0 (https://github.com/alvr-org/settings-schema-rs?rev=676185f#676185f3)
   Compiling alvr_common v21.0.0-dev00 (/home/zdjeffries/ALVR/ALVR/alvr/common)
warning<EMAIL_ADDRESS>cpp/graphics.cpp:502:18: warning: format specifies type 'int' but the argument has type 'size_t' (aka 'unsigned long') [-Wformat]
warning<EMAIL_ADDRESS>                 i,
warning<EMAIL_ADDRESS>                 ^
warning<EMAIL_ADDRESS>cpp/utils.h:18:65: note: expanded from macro 'LOGD'
warning<EMAIL_ADDRESS>        __android_log_print(ANDROID_LOG_DEBUG, "[ALVR Native]", __VA_ARGS__);                        \
warning<EMAIL_ADDRESS>                                                                ^~~~~~~~~~~
warning<EMAIL_ADDRESS>1 warning generated.
   Compiling alvr_sockets v21.0.0-dev00 (/home/zdjeffries/ALVR/ALVR/alvr/sockets)
   Compiling alvr_packets v21.0.0-dev00 (/home/zdjeffries/ALVR/ALVR/alvr/packets)
   Compiling alvr_audio v21.0.0-dev00 (/home/zdjeffries/ALVR/ALVR/alvr/audio)
error: linking with `/usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/home/zdjeffries/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-

  ######################################################################
  ######### (A whole bunch of terminal spam that I don't think is usefule...) ###########
  ######################################################################

  z,relro,-z,now" "-nodefaultlibs" "--target=aarch64-linux-android26"
  = note: /usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -lunwind
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

The following warnings were emitted during compilation:

warning<EMAIL_ADDRESS>cpp/graphics.cpp:502:18: warning: format specifies type 'int' but the argument has type 'size_t' (aka 'unsigned long') [-Wformat]
warning<EMAIL_ADDRESS>                 i,
warning<EMAIL_ADDRESS>                 ^
warning<EMAIL_ADDRESS>cpp/utils.h:18:65: note: expanded from macro 'LOGD'
warning<EMAIL_ADDRESS>        __android_log_print(ANDROID_LOG_DEBUG, "[ALVR Native]", __VA_ARGS__);                        \
warning<EMAIL_ADDRESS>                                                                ^~~~~~~~~~~
warning<EMAIL_ADDRESS>1 warning generated.

error: could not compile `alvr_client_core` (lib) due to 1 previous error
Error: Command `AR_aarch64-linux-android=/usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-ar CARGO_ENCODED_RUSTFLAGS=-Clink-arg=--target=aarch64-linux-android26 CARGO_TARGET_AARCH64_LINUX_ANDROID_AR=/usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-ar CARGO_TARGET_AARCH64_LINUX_ANDROID_LINKER=/usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang CC_aarch64-linux-android=/usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang CFLAGS_aarch64-linux-android=--target=aarch64-linux-android26 CXXFLAGS_aarch64-linux-android=--target=aarch64-linux-android26 CXX_aarch64-linux-android=/usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ cargo build --target aarch64-linux-android --target-dir /home/zdjeffries/ALVR/ALVR/target` had a non-zero exit code.
thread 'main' panicked at alvr/xtask/src/build.rs:394:6:
called `Result::unwrap()` on an `Err` value: command exited with non-zero code `cargo apk build --target-dir=/home/zdjeffries/ALVR/ALVR/target`: 1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Checking Android SDK:
~/ALVR/ALVR$ ls ~/Android/Sdk/platforms
android-29

And running with the RUST backtrace did not yield any new information.
Checking libunwind
~/ALVR/ALVR$ sudo apt install libunwind-dev
[sudo] password for zdjeffries:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libunwind-dev is already the newest version (1.3.2-2build2.1).
0 upgraded, 0 newly installed, 0 to remove and 48 not upgraded.

Checking the 2nd error path: (check that ld exists - it does...)
note: /usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -lunwind
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

ls /usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/aarch64-linux-android/bin
ar  as  ld  ld.bfd  ld.gold  nm  objcopy  objdump  ranlib  readelf  strip

Checking the 1st error path: (check that clang exists - it does... also idk why lack of a linter util would cause a build to fail, maybe tests to not pass)
ls /usr/lib/android-sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin
... (removed for brevity) ...
clang
... (removed for brevity) ...

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environment
Dell Laptop
Hardware
Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload
I cannot do this for other reasons. If something is pertinent and not contained below, please let me know.
CPU: 12th Gen Intel® Core™ i7-12850HX
GPU: NVIDIA RTX A1000 Laptop GPU
GPU Driver Version: 535.154.05 (CUDA 12.2)
Audio: Intel Corportation Audio Device (Internal)
Installation
ALVR Version: master as of 19Feb2024 1400 EST
ALVR Settings File: n/a
SteamVR Version: n/a
Install Type:

[ ] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[x] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
Ubuntu 22.04.3 LTS

Wellllll... I foolishly used the NDK that Android Studio installed (along with SDK 29 and 34)...
After replacing it with this NDK it built.


Fix batching formula of xmap

Turns out that once you insert multiple dimensions things become much
more tricky than in the case of batching a one-dimensional map. Also
strenghten our tests to make sure we don't depend too much on the
semantics of the einsum batching rule.

Agreed, just wanted to unblock @hawkinsp. Added the test now (and verified that it would catch this issue on master).


Added 0x9B, 0xB3, 0xB5, 0xB6, 0xAB and 0xAF.

0x9B: PacketPlayTakeItemEntity
0xB3: PacketPlayRespawn
0xB5: PacketPlayContainerOpen
0xB6: PacketPlayContainerClose
0xAB: PacketPlayPlayerAction
0xAF: PacketPlaySetEntityLink

These need accessor methods, e.g. PacketPlayContainerClose.getWindowId(). Otherwise they ain't gonna help much..

@nickrobson discussed that with @Serializator, and together we decided that's for another PR (which he's also willing to make) because they are missing from packets outside this PR.

Sounds good.


GIF for README

adding homepage GIF for readme

Hey this is cool :D

@lauras5  can u make gif of updated site

Yes I can do that tonight!
On Wed, Oct 31, 2018 at 12:52 AM Pranjal Vyas<EMAIL_ADDRESS>wrote:

@lauras5 https://github.com/lauras5 can u make gif of updated site
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lingonsaft/hacktoberfest/pull/1344#issuecomment-434592732,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgVsgE0XtYrIgTkNEfACDVDvcR4j-8OGks5uqVbGgaJpZM4XUijP
.


Add an AMOLED theme

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
8.0b4
Problem you are trying to solve
Thunderbird currently doesn't provide an AMOLED theme (i.e. a theme with a pure black background). Since my phone has an OLED display, I prefer to use AMOLED themes where possible since they look pretty good on an OLED.
Suggested solution
Add a theme option to use AMOLED colors. I've seen other apps implement this in two different ways:

As a standalone option in the themes combo box
As a switch that can be used to modify the dark theme

Screenshots / Drawings / Technical details
No response

I think we might be able to handle this via #8340, if you can set custom colors via Material You, you should be able to set a full black.

I think we might be able to handle this via ..., if you can set custom colors via Material You, you should be able to set a full black.

Not the greatest solution, most ROMs don't let you pick the entire palette, and it usually requires root to enable such a feature on those ROMs. Simply having a toggle in the app, that makes the dark background parts of the palette forcibly black would however work.

It should be on OxygenOS and OneUI also.

It's on most ROMs in the dark mode menu. At least on LineageOS, where there's an option to enable pure black mode

Keyword here: most
Not all... Phone's stuck below Android 11 straight up can't have this option, not without some modification, and most Android 12 ROMs don't have this either. There's no actual good reason to not have a separate option. No downsides to adding it, only upsides.


APIService https issue for v0.6.2 visibility api

What happened:
TLDR; looks like APIService is possibly ignoring insecureSkipTLSVerify: true field on APIService when enabling visibility api?
Running Kueue on KIND (docker-upstream.apple.com/kindest/node:v1.25.16).
kubectl edit deployment -n kueue-system kueue-controller-manager
I add:
- name: manager
   args:
     - --feature-gates=MultiKueue=true
     - --feature-gates=LendingLimit=true
     - --feature-gates=VisibilityOnDemand=true
     - --feature-gates=QueueVisibility=true
     - --feature-gates=PartialAdmission=true

kubectl apply --server-side -f https://github.com/kubernetes-sigs/kueue/releases/download/v0.6.2/visibility-api.yaml
kubectl get --raw "/apis/visibility.kueue.x-k8s.io/v1alpha1/clusterqueues/team-a/pendingworkloads?limit=1&offset=1"
Error from server (ServiceUnavailable): the server is currently unable to handle the request

⭐Note: server error ServiceUnavailable only appears after I apply the visibility api yaml serverside.
kubectl get apiservice v1alpha1.visibility.kueue.x-k8s.io -o yaml
...
...
...
status:
  conditions:
  - lastTransitionTime: "2024-05-14T20:31:25Z"
    message: 'failing or missing response from https://<IP_ADDRESS>:443/apis/visibility.kueue.x-k8s.io/v1alpha1:
      Get "https://<IP_ADDRESS>:443/apis/visibility.kueue.x-k8s.io/v1alpha1": http:
      server gave HTTP response to HTTPS client'
    reason: FailedDiscoveryCheck
    status: "False"
    type: Available

What you expected to happen:
I expected to be able to look at workload position via the kubectl api visibility call
Environment:

Kubernetes version (use kubectl version):

Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.16", GitCommit:"c5f43560a4f98f2af3743a59299fb79f07924373", GitTreeState:"clean", BuildDate:"2024-02-14T00:40:21Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}

Kueue version (use git describe --tags --dirty --always):
v0.6.2

/assign @PBundyra

Could you please share output of kubectl describe pod -n kueue-system on kueue-controller-manager?

Also, can you try changing the arguments to:
     - --feature-gates=MultiKueue=true,LendingLimit=true,VisibilityOnDemand=true,QueueVisibility=true,PartialAdmission=true

Deleted old KIND cluster, created fresh KIND Kueue cluster
Updated arguments to: https://github.com/kubernetes-sigs/kueue/issues/2205#issuecomment-2117810447
Bounced pods

Amys-MacBook-Pro-2:kueue-experiments amychen$ kubectl describe apiservice v1alpha1.visibility.kueue.x-k8s.io
Name:         v1alpha1.visibility.kueue.x-k8s.io
Namespace:
Labels:       <none>
Annotations:  <none>
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
  Creation Timestamp:  2024-05-17T17:07:12Z
  Managed Fields:
    API Version:  apiregistration.k8s.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:spec:
        f:group:
        f:groupPriorityMinimum:
        f:insecureSkipTLSVerify:
        f:service:
          f:name:
          f:namespace:
        f:version:
        f:versionPriority:
    Manager:      kubectl
    Operation:    Apply
    Time:         2024-05-17T17:07:12Z
    API Version:  apiregistration.k8s.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        f:conditions:
          .:
          k:{"type":"Available"}:
            .:
            f:lastTransitionTime:
            f:message:
            f:reason:
            f:status:
            f:type:
    Manager:         kube-apiserver
    Operation:       Update
    Subresource:     status
    Time:            2024-05-17T17:07:13Z
  Resource Version:  1067
  UID:               171d577b-7c1d-47c9-b45a-aa52e89f5377
Spec:
  Group:                     visibility.kueue.x-k8s.io
  Group Priority Minimum:    100
  Insecure Skip TLS Verify:  true
  Service:
    Name:            kueue-visibility-server
    Namespace:       kueue-system
    Port:            443
  Version:           v1alpha1
  Version Priority:  100
Status:
  Conditions:
    Last Transition Time:  2024-05-17T17:07:13Z
    Message:               failing or missing response from https://<IP_ADDRESS>:443/apis/visibility.kueue.x-k8s.io/v1alpha1: Get "https://<IP_ADDRESS>:443/apis/visibility.kueue.x-k8s.io/v1alpha1": http: server gave HTTP response to HTTPS client
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available
Events:                    <none>
Amys-MacBook-Pro-2:kueue-experiments amychen$ kubectl describe pod -n kueue-system
Name:                 kueue-controller-manager-5b6f4b4c97-5ngkg
Namespace:            kueue-system
Priority:             500000
Priority Class Name:  p1
Service Account:      kueue-controller-manager
Node:                 test-kueue-worker/<IP_ADDRESS>
Start Time:           Fri, 17 May 2024 10:06:36 -0700
Labels:               control-plane=controller-manager
                      pod-template-hash=5b6f4b4c97
Annotations:          kubectl.kubernetes.io/default-container: manager
                      kubernetes.io/limit-ranger:
                        LimitRanger plugin set: cpu, memory request for container kube-rbac-proxy; cpu, memory limit for container kube-rbac-proxy
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/kueue-controller-manager-5b6f4b4c97
Containers:
  manager:
    Container ID:  containerd://ee6437d6134ddec3b423e52af94e359cb96086aff0ad3a214255ca82ed0b173a
    Image:         registry.k8s.io/kueue/kueue:v0.6.2
    Image ID:      registry.k8s.io/kueue/kueue@sha256:ef1f07fa559eb396a93e67d682743bac602b512cf11d203e14b10bcfa2e89112
    Ports:         8082/TCP, 9443/TCP
    Host Ports:    0/TCP, 0/TCP
    Command:
      /manager
    Args:
      --config=/controller_manager_config.yaml
      --zap-log-level=2
    State:          Running
      Started:      Fri, 17 May 2024 10:06:39 -0700
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     500m
      memory:  512Mi
    Requests:
      cpu:        500m
      memory:     512Mi
    Liveness:     http-get http://:8081/healthz delay=15s timeout=1s period=20s #success=1 #failure=3
    Readiness:    http-get http://:8081/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /controller_manager_config.yaml from manager-config (rw,path="controller_manager_config.yaml")
      /tmp/k8s-webhook-server/serving-certs from cert (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dfhxh (ro)
  kube-rbac-proxy:
    Container ID:  containerd://a63c330b11eddcd163a5d50a56d273ec82f549c9074b6e31ab8e0ac996ac8bd9
    Image:         gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0
    Image ID:      gcr.io/kubebuilder/kube-rbac-proxy@sha256:db06cc4c084dd0253134f156dddaaf53ef1c3fb3cc809e5d81711baa4029ea4c
    Port:          8443/TCP
    Host Port:     0/TCP
    Args:
      --secure-listen-address=<IP_ADDRESS>:8443
      --upstream=http://<IP_ADDRESS>:8080/
      --logtostderr=true
      --v=10
    State:          Running
      Started:      Fri, 17 May 2024 10:06:40 -0700
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  128Mi
    Requests:
      cpu:        100m
      memory:     128Mi
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-dfhxh (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  cert:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kueue-webhook-server-cert
    Optional:    false
  manager-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      kueue-manager-config
    Optional:  false
  kube-api-access-dfhxh:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Guaranteed
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  95s   default-scheduler  Successfully assigned kueue-system/kueue-controller-manager-5b6f4b4c97-5ngkg to test-kueue-worker
  Normal  Pulling    94s   kubelet            Pulling image "registry.k8s.io/kueue/kueue:v0.6.2"
  Normal  Pulled     93s   kubelet            Successfully pulled image "registry.k8s.io/kueue/kueue:v0.6.2" in 1.336599868s (1.336603463s including waiting)
  Normal  Created    92s   kubelet            Created container manager
  Normal  Started    92s   kubelet            Started container manager
  Normal  Pulled     92s   kubelet            Container image "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0" already present on machine
  Normal  Created    91s   kubelet            Created container kube-rbac-proxy
  Normal  Started    91s   kubelet            Started container kube-rbac-proxy

Amys-MacBook-Pro-2:kueue-experiments amychen$ kubectl describe apiservice v1alpha1.visibility.kueue.x-k8s.io
Name:         v1alpha1.visibility.kueue.x-k8s.io
Namespace:
Labels:       <none>
Annotations:  <none>
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
  Creation Timestamp:  2024-05-17T17:07:12Z
  Managed Fields:
    API Version:  apiregistration.k8s.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:spec:
        f:group:
        f:groupPriorityMinimum:
        f:insecureSkipTLSVerify:
        f:service:
          f:name:
          f:namespace:
        f:version:
        f:versionPriority:
    Manager:      kubectl
    Operation:    Apply
    Time:         2024-05-17T17:07:12Z
    API Version:  apiregistration.k8s.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        f:conditions:
          .:
          k:{"type":"Available"}:
            .:
            f:lastTransitionTime:
            f:message:
            f:reason:
            f:status:
            f:type:
    Manager:         kube-apiserver
    Operation:       Update
    Subresource:     status
    Time:            2024-05-17T17:07:13Z
  Resource Version:  1067
  UID:               171d577b-7c1d-47c9-b45a-aa52e89f5377
Spec:
  Group:                     visibility.kueue.x-k8s.io
  Group Priority Minimum:    100
  Insecure Skip TLS Verify:  true
  Service:
    Name:            kueue-visibility-server
    Namespace:       kueue-system
    Port:            443
  Version:           v1alpha1
  Version Priority:  100
Status:
  Conditions:
    Last Transition Time:  2024-05-17T17:07:13Z
    Message:               failing or missing response from https://<IP_ADDRESS>:443/apis/visibility.kueue.x-k8s.io/v1alpha1: Get "https://<IP_ADDRESS>:443/apis/visibility.kueue.x-k8s.io/v1alpha1": http: server gave HTTP response to HTTPS client
    Reason:                FailedDiscoveryCheck
    Status:                False
    Type:                  Available
Events:                    <none>

@PBundyra this message is interesting http:  server gave HTTP response to HTTPS client
Shouldn't that be handled by the kube-rbac-proxy container?
@amy any Service configuration that differs from the manifests including in the release?

Actually, can you share your KueueConfiguration? In particular, the internalCertManagement.
Or do you see any log lines from this file? https://github.com/kubernetes-sigs/kueue/blob/main/pkg/visibility/server.go#L49

kubectl get configmap -n kueue-system kueue-manager-config -o yaml
E0517 11:58:37.520554   99641 memcache.go:255] couldn't get resource list for visibility.kueue.x-k8s.io/v1alpha1: the server is currently unable to handle the request
E0517 11:58:37.544339   99641 memcache.go:106] couldn't get resource list for visibility.kueue.x-k8s.io/v1alpha1: the server is currently unable to handle the request
E0517 11:58:37.546758   99641 memcache.go:106] couldn't get resource list for visibility.kueue.x-k8s.io/v1alpha1: the server is currently unable to handle the request
E0517 11:58:37.549032   99641 memcache.go:106] couldn't get resource list for visibility.kueue.x-k8s.io/v1alpha1: the server is currently unable to handle the request
apiVersion: v1
data:
  controller_manager_config.yaml: |
    apiVersion: config.kueue.x-k8s.io/v1beta1
    kind: Configuration
    health:
      healthProbeBindAddress: :8081
    metrics:
      bindAddress: :8080
      ## Enable resource utilisation metrics for the ClusterQueue
      enableClusterQueueResources: true
    ## Enable pprof endpoints
    pprofBindAddress: :8082
    webhook:
      port: 9443
    leaderElection:
      leaderElect: true
      resourceName: kueue-manager.kueue.x-k8s.io
    controller:
      groupKindConcurrency:
        Job.batch: 5
        Pod: 5
        Workload.kueue.x-k8s.io: 5
        LocalQueue.kueue.x-k8s.io: 1
        ClusterQueue.kueue.x-k8s.io: 1
        ResourceFlavor.kueue.x-k8s.io: 1
    clientConnection:
      qps: 50
      burst: 100
    ## This is required to optionally turn on "all or nothing" scheduling
    ## https://kueue.sigs.k8s.io/docs/tasks/manage/setup_sequential_admission/
    #waitForPodsReady:
    #  enable: true
    manageJobsWithoutQueueName: true
    internalCertManagement:
      enable: true
      webhookServiceName: kueue-webhook-service
      webhookSecretName: kueue-webhook-server-cert
    integrations:
      frameworks:
      ## Enable Job integration: https://kueue.sigs.k8s.io/docs/tasks/run/jobs/
      - "batch/job"
      ## Enable Pod integration (requires k8s 1.27): https://kueue.sigs.k8s.io/docs/tasks/run/plain_pods/
      #- "pod"
      #- "kubeflow.org/mpijob"
      #- "ray.io/rayjob"
      #- "ray.io/raycluster"
      #- "jobset.x-k8s.io/jobset"
      #- "kubeflow.org/mxjob"
      #- "kubeflow.org/paddlejob"
      #- "kubeflow.org/pytorchjob"
      #- "kubeflow.org/tfjob"
      #- "kubeflow.org/xgboostjob"
kind: ConfigMap
metadata:
  creationTimestamp: "2024-05-17T17:05:46Z"
  name: kueue-manager-config
  namespace: kueue-system
  resourceVersion: "12952"
  uid: 34e3aab5-8480-4e17-b45b-3b5a72addb68

Uhm, looks like the similar situation as https://github.com/kubernetes-sigs/kueue/issues/1519

It looks like you didn't add back the feature-gates?
From https://github.com/kubernetes-sigs/kueue/issues/2205#issuecomment-2118032745
  manager:
    Container ID:  containerd://ee6437d6134ddec3b423e52af94e359cb96086aff0ad3a214255ca82ed0b173a
    Image:         registry.k8s.io/kueue/kueue:v0.6.2
    Image ID:      registry.k8s.io/kueue/kueue@sha256:ef1f07fa559eb396a93e67d682743bac602b512cf11d203e14b10bcfa2e89112
    Ports:         8082/TCP, 9443/TCP
    Host Ports:    0/TCP, 0/TCP
    Command:
      /manager
    Args:
      --config=/controller_manager_config.yaml
      --zap-log-level=2
    State:          Running

Weird, so it shows up in my deployment spec, but not the pod spec...

Amys-MacBook-Pro-2:kueue-experiments amychen$ kubectl describe deployment -n kueue-system
Name:                   kueue-controller-manager
Namespace:              kueue-system
CreationTimestamp:      Fri, 17 May 2024 10:05:47 -0700
Labels:                 control-plane=controller-manager
Annotations:            deployment.kubernetes.io/revision: 2
Selector:               control-plane=controller-manager
Replicas:               1 desired | 0 updated | 1 total | 1 available | 1 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:           control-plane=controller-manager
  Annotations:      kubectl.kubernetes.io/default-container: manager
  Service Account:  kueue-controller-manager
  Containers:
   manager:
    Image:       registry.k8s.io/kueue/kueue:v0.6.2
    Ports:       8082/TCP, 9443/TCP
    Host Ports:  0/TCP, 0/TCP
    Command:
      /manager
    Args:
      --feature-gates=MultiKueue=true,LendingLimit=true,VisibilityOnDemand=true,QueueVisibility=true,PartialAdmission=true
      --config=/controller_manager_config.yaml
      --zap-log-level=2

kubectl describe pod -n kueue-system
Name:                 kueue-controller-manager-5b6f4b4c97-9bl44
Namespace:            kueue-system
Priority:             500000
Priority Class Name:  p1
Service Account:      kueue-controller-manager
Node:                 test-kueue-worker/<IP_ADDRESS>
Start Time:           Fri, 17 May 2024 11:58:10 -0700
Labels:               control-plane=controller-manager
                      pod-template-hash=5b6f4b4c97
Annotations:          kubectl.kubernetes.io/default-container: manager
                      kubernetes.io/limit-ranger:
                        LimitRanger plugin set: cpu, memory request for container kube-rbac-proxy; cpu, memory limit for container kube-rbac-proxy
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/kueue-controller-manager-5b6f4b4c97
Containers:
  manager:
    Container ID:  containerd://e7b593a55c4b31a5756e9b26b852730cc8e8243752dba78f4367b539a93ae269
    Image:         registry.k8s.io/kueue/kueue:v0.6.2
    Image ID:      registry.k8s.io/kueue/kueue@sha256:ef1f07fa559eb396a93e67d682743bac602b512cf11d203e14b10bcfa2e89112
    Ports:         8082/TCP, 9443/TCP
    Host Ports:    0/TCP, 0/TCP
    Command:
      /manager
    Args:
      --config=/controller_manager_config.yaml
      --zap-log-level=2

This is even after deleting the pod and waiting for deployment bring up. Weird...

can you try changing other parameters? Like the log-level?

yeah log level doesn't change either

Could you show the replicaset with the kubectl get replicaset -n keueu-system?

This looks suspicious:
Replicas:               1 desired | 0 updated | 1 total | 1 available | 1 unavailable
StrategyType:           RollingUpdate
RollingUpdateStrategy:  25% max unavailable, 25% max surge

I guess that your updated replicaset failed to start somehow.

okay! Got the pod to update its args. Getting new error logs in the kueue controller:
I0517 20:12:46.090825       1 leaderelection.go:250] attempting to acquire leader lease kueue-system/kueue-manager.kueue.x-k8s.io...
{"level":"info","ts":"2024-05-17T20:12:46.192216512Z","logger":"cert-rotation","caller":"rotator/rotator.go:347","msg":"no cert refresh needed"}
{"level":"info","ts":"2024-05-17T20:12:46.192300248Z","logger":"cert-rotation","caller":"rotator/rotator.go:867","msg":"certs are ready in /tmp/k8s-webhook-server/serving-certs"}
{"level":"info","ts":"2024-05-17T20:12:46.261857114Z","caller":"controller/controller.go:220","msg":"Starting workers","controller":"cert-rotator","worker count":1}
{"level":"info","ts":"2024-05-17T20:12:46.263417658Z","logger":"cert-rotation","caller":"rotator/rotator.go:347","msg":"no cert refresh needed"}
{"level":"info","ts":"2024-05-17T20:12:46.264107092Z","logger":"cert-rotation","caller":"rotator/rotator.go:828","msg":"Ensuring CA cert","name":"kueue-validating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration","name":"kueue-validating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration"}
{"level":"info","ts":"2024-05-17T20:12:46.274077578Z","logger":"cert-rotation","caller":"rotator/rotator.go:828","msg":"Ensuring CA cert","name":"kueue-mutating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=MutatingWebhookConfiguration","name":"kueue-mutating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=MutatingWebhookConfiguration"}
{"level":"info","ts":"2024-05-17T20:12:46.284022151Z","logger":"cert-rotation","caller":"rotator/rotator.go:347","msg":"no cert refresh needed"}
{"level":"info","ts":"2024-05-17T20:12:46.284846815Z","logger":"cert-rotation","caller":"rotator/rotator.go:828","msg":"Ensuring CA cert","name":"kueue-validating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration","name":"kueue-validating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration"}
{"level":"info","ts":"2024-05-17T20:12:46.294002625Z","logger":"cert-rotation","caller":"rotator/rotator.go:828","msg":"Ensuring CA cert","name":"kueue-mutating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=MutatingWebhookConfiguration","name":"kueue-mutating-webhook-configuration","gvk":"admissionregistration.k8s.io/v1, Kind=MutatingWebhookConfiguration"}
I0517 20:12:46.493666       1 serving.go:374] Generated self-signed cert (/tmp/apiserver.crt, /tmp/apiserver.key)
{"level":"error","ts":"2024-05-17T20:12:46.493819819Z","logger":"visibility-server","caller":"visibility/server.go:52","msg":"Unable to apply VisibilityServerOptions","error":"failed to create listener: failed to listen on <IP_ADDRESS>:8082: listen tcp <IP_ADDRESS>:8082: bind: address already in use","stacktrace":"sigs.k8s.io/kueue/pkg/visibility.CreateAndStartVisibilityServer\n\t/workspace/pkg/visibility/server.go:52"}
F0517 20:12:46.493924       1 config.go:681] cannot derive external address port without listening on a secure port.

It looks like our default configuration recommends the same port for pprofBindAddress: :8082 and the visibility API :)
Try putting the pprof in a different address?

it works! thanks for taking a look folks

thanks for opening the follow up issue!


bar charts axis starting at non-zero

Hi,
While changing the y-axis domain of a bar chart, bars are overlapping the x-axis. How can i avoid this?

Reference: https://github.com/d3plus/d3plus/issues/480

Instead of starting from zero (which is often a big "no no" in Bar Charts), I'd prefer to add support for "breaking" the scale: https://github.com/d3plus/d3plus-plot/issues/99


Matrix stops working when "off" command issued upon deletion

It stays non-functional until it's reconnected.  This regression was introduced in PR #121 where all devices issue the "off" command to themselves upon destruction.  Using the "off" command is specifically avoided in BuildHAT.shutdown() with an exception built into the type identifier for the Matrix but a similar carveout in Device.__del__() has not been made.

Good spot! Thanks for that


MInor fixes

Fixes of potential out of bounds error and faulty recursion implementation.

Thank you for contributing!


ImportError: No module named 'docopt'

Any idea why I'm getting ImportError: No module named 'docopt', on Ubuntu 16.10?

Yes, it uses docopt to parse input in the repl (which is perhaps not the best way, but it's how it is...).  You can install it with pip: https://github.com/barrucadu/markov#getting-started

@barrucadu I did follow the exact instructions and everything worked well. I also did pip install docopt manually, and it still shows that error...

Then I'm afraid I don't know, the virtualenv should put the module into scope


Memory leak in __NSThreadPerformPerform

zcash4mac 1.0.4-208
Steps:
Launch zcash4mac.
What happened:
Memory leak in __NSThreadPerformPerform
https://www.dropbox.com/s/pf54fy2ge7yx5o9/zcash4mac.trace.zip?dl=0
Expected result:
No leaks.
Notes:
Unzip and open file with Apple Instruments (part of Xcode tools).

This project is dead so retracting.


fpZ not working

Hello,
GraphQL does not allow hyphenated names. The property fpZ just get past to the generated URL and Imgix does not seem to know what to do with it (fpZ=1 instead of fp-z=1).
I'm using the version 1.6.0.
Thanks.

Hey there @hazzyeer - this shouldn't be happening. Can you please let me know what your GraphQL query is, and how you're using the plugin? Then I'll be able to take a look at this. Thanks!

Version of the dependency that i'm using "@imgix/gatsby": "^1.6.0".
Here is my configuration of the plugin:
{
    resolve: `@imgix/gatsby`,
    options: {
      domain: '<domain>',
      secureURLToken: '<token>',
      sourceType: ImgixSourceType.WebFolder,
      defaultImgixParams: { auto: 'format,compress' },
      fields: [
        {
          nodeType: 'Image',
          // This is used to pull the raw image URL from the node you want to
          // transform. It is passed the node to transform as an argument, and
          // expects a URL to be returned.
          getURL: (node) => {
            const urlBlocks: ReadonlyArray<string> = node.url.split('/')
            return urlBlocks[urlBlocks.length - 1]
          },
          // This is the name of imgix field that will be added to the type.
          fieldName: 'imgixImage',
        }
      ]
    },
  }

And here is the graphql query:
image {
        ...
        imgixImage {
          gatsbyImageData(
            layout: FIXED
            width: 70
            imgixParams: {auto: "format,compress", ar: "0.74", fit:"crop", fpZ: 4, crop: "focalpoint"}
          )
        }
      }


Improved Windows support

Running on Windows, I had the same problem of issue #23. The proposed solution was a merge request #24 + adding a node.cmd for each project root that uses atom-mocha-test-runner with the following contents:
@echo off
"C:\Program Files\nodejs\node.exe" %*

To avoid this extra step, I've added to lib/mocha-test-runner.coffee another default path verifying if the user is running on Windows.
I'd like to avoid this hard coded paths, but I could not find another way and I've seen
two others projects using the same approach.
Note that os.platform() returns 'win32' even for 64 machines.

Thanks for the fix!
From what I understand:

we definitely needed the mocha.cmd fix from #24
Mocha then tries to run node from your $PATH
the test runner updates $PATH to contain nodeBinaryPath, which is a config setting

This means Windows users could also update the value straight from the Atom preference pane, no need to add node.cmd in the project root.

However it's great to have a sensible default for Windows :+1:


Telegram notification fail to send alert with error "Cannot read properties of undefined (reading 'data')"

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Hi, I have to setup Telegram notification and fill the required Bot token and Chat ID correctly, but the Test was fail and prompted "Cannot read properties of undefined (reading 'data'), my network require to use proxy for internet access, the uptime-kuma hosts already have proxy setting and internet access is ok, I don't know this error is related to internet access or other issue.
🐻 Uptime-Kuma Version
1.14.0
💻 Operating System and Arch
Raspberry Pi OS 11 (bullseye)
🌐 Browser
Chrome
🐋 Docker Version
Docker version 20.10.14, build a224086
🟩 NodeJS Version
No response

Proxy is not support for notifications.

Proxy is not support for notifications.

Hi Louis, Thank you for your reply, it is possible to apply the proxy setting in the notification ?

See #616

I am seeing this error in 1.21.0 - both notifications and test.
Tried to recreate using a standalone script and the only way to get this exception is to have some error in the try/catch that doesn't set a response property
const axios = require("axios");

async function send(telegramBotToken) {
  let okMsg = "Sent Successfully.";

  try {
    let params = {
      chat_id: '12345678',
      text: 'Test message',
      disable_notification: false,
      protect_content: false,
    };

    await axios.get(`https://api.telegram.org/bot${telegramBotToken}/sendMessage`, {
      params: params,
    });
    return okMsg;

  } catch (error) {
    let msg = (error.response.data.description) ? error.response.data.description : "Error without description";
    throw new Error(msg);
  }
}

(async () => {
  send('12345678900:token-characters');
})();

When I remove the line const axios = require("axios"); I get the following error, which leads me to believe a non-axios error is being thrown
TypeError: Cannot read properties of undefined (reading 'data')
    at send (/home/workspace/temp/telegram/test.js:20:31)
    at /home/workspace/temp/telegram/test.js:26:3
    at Object.<anonymous> (/home/workspace/temp/telegram/test.js:27:3)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47

A fix could be to check if the exception has a response property


'crumb' is not recognized as an internal or external command

Steps to Reproduce

...While creating a flutter project in Android Studio
...While accessing flutter through Command Prompt
...

Logs

flutter doctor

'crumb' is not recognized as an internal or external command,
operable program or batch file.
Error: Unable to find git in your PATH.

where do i can find the crumb location

how to add path to crumb?

Can you explain the whole process


Do not call python directly in tests

At least on openSUSE it requires python2 interpreter, but like this it calls the interpreter we are working with.

@scarabeusiv thanks!

Thanks a lot for your contribution! Please make your branch to derive from our 0.x branch (instead of master), with the following commands:
git checkout 0.x
git checkout patch-1
git rebase --onto 0.x master patch-1
git push -f origin patch-1

It is cherry-pickalble without merge conflict in the 0.1 branch. Do you want me to create the PR against that branch?

Yes please. We then merge with master On our side
Thanks!

closing as the new one is for the 0.x branch.


Hints content revision for next release

Please go through the pages:

[x] dashboard
[x] state channel details
[x] state channel
[x] transactions
[x] token details
[x] tokens
[x] oracle details
[x] oracles
[x] account details
[x] name details
[x] names
[x] smart contracts

and evaluate the content.
Ideally, provide comments to this Issue.

@janmichek are the hints already visible on the latest dev deployment or do I have to check several PRs? if so a short summary of where to check what would be great 🙏

Spot on @marc0olo 👍

token details

[ ] replace with: "Price of the token in AE and USD."

[ ] replace with: "Amount of tokens in circulation."

reason: my assumption is that burned tokens won't be included in that value, so that statement was not accurate

[ ] replace "interface" with "fungible token standard"

we are displaying the hints mainly for the average joe, right? 😁

[ ] replace with: "Extensions that are implemented for this token according to the creator of the Smart Contract."

oracle details

[ ] "Block" -> "Keyblock"
[ ] "estimated date" -> "exact date"

[ ] "Block" -> "Keyblock"
[ ] "estimated date" -> "exact date"

[ ] rename label to "Last queried" ?
[ ] replace hint with: "Keyblock height and exact date of the last query to the Oracle."

[ ] replace with: "The default lifetime of an Oracle is 500 keyblocks. The initial lifetime can be set to a higher value and an Oracle can be extended anytime, e.g. by setting up an automated service. In case the Oracle lifetime is passed, the Oracle operator can re-register it anytime."

[ ] replace with: "The default fee required to query an Oracle is 30,000 aettos and is defined by the Oracle operator when registering it. The Oracle operator can set it to any value and even allow to query the Oracle for free."

[ ] rename label to "Operator"
[ ] replace hint with: "The account that operates the Oracle."

[ ] replace with: "The default fee required to query an Oracle is 30,000 aettos and is defined by the Oracle operator when registering it. The Oracle operator can set it to any value and even allow to query the Oracle for free."

[ ] replace with: "Defines how long the response will be accessible in keyblocks. The displayed lifetime is relative and if a Smart Contract relies on the response, the user or a service should make sure the response is consumed during its lifetime."

[ ] replace with "The response payload to the given query."

not sure about the binary format 🤔 e.g. in this example here I see the account address: https://aescan.dev.aepps.com/oracles/ok_4HGhEdjeRtpsWzfSEJZnBKNmjgHALAifcBUey8EvRAdDfRsqc

oracles

[ ] replace "creator" with "operator"

[ ] "Block" -> "Keyblock"
[ ] "extimated" -> "exact"

[ ] replace with: "The default lifetime of an Oracle is 500 keyblocks. The initial lifetime can be set to a higher value and an Oracle can be extended anytime, e.g. by setting up an automated service. In case the Oracle lifetime is passed, the Oracle operator can re-register it anytime."

[ ] replace with: "The default fee required to query an Oracle is 30,000 aettos and is defined by the Oracle operator when registering it. The Oracle operator can set it to any value and even allow to query the Oracle for free."

account details

[ ] "Fiat" -> "USD" (depending on consistency with other places where I commented)

Is this true? Or is the the amount of transactions executed by this account? 🤔 @michele-franchi

edit: I think it is correct, looking at the tx-table

[ ] "Names" -> "names" (depends on consistency, see other comments)

[ ] replace with: "The nonce that has been used to execute the last transaction for the account. The nonce is used to prevent replay attacks and to keep transactions in the right order. If a transaction with a way higher nonce is broadcasted, it won't be executed until all transactions with lower nonces are executed."

[ ] replace with: "Keyblock height and exact date and time when the transaction has been executed by inclusion into a microblock."

[ ] Add a hint for "Data" label: "The data displayed differs for each tx type."
[ ] hints for tx-type within the column values are missing (should be similar to those on "transactions")

name details

[ ] "Name" -> "name" ? (consistency topic)

Note: for expired names we should change the label to "Last owner" and also adjust the hint maybe? cc @michele-franchi

[ ] "Block" -> "Keyblock"
[ ] "estimated" -> "exact"
[ ] "Name" -> "name" ? (consistency topic)

Expires

[ ] "Block" -> "Keyblock"
[ ] Add sentence: "After expiration, the name enters into a revoked state and can be claimed again after a fixed timeout of 2016 keyblocks."

Expired

[ ] "Block" -> "Keyblock"
[ ] "estimated" -> "exact"
[ ] Add sentence: "After expiration, the name entered into a revoked state and can be claimed again after a fixed timeout of 2016 keyblocks."

In Auction

replace with: "Keyblock height and estimated date and time when the auction ends and the name will be activated and owned by the highest bidder."

Note: maybe change label to "Ends" instead of "Expires" ? I remember we wanted to keep it simple, but the hint needs to have a different content anyway 🤷♂ cc @michele-franchi

[ ] "Name" -> "name" ? (consistency topic)

[ ] "Name" -> "name" ? (consistency topic)

[ ] "Block" -> "Keyblock"
[ ] "estimated" -> "exact"

names
Active

[ ] replace with: "Account that paid the shown price to claim the name."

[ ] "Name" -> "name" ? (consistency topic)

[ ] replace with: "The account the name points to."

In Auction

[ ] "need to be auctioned" -> "are always auctioned"

[ ] "Block" -> "Keyblock"

here we should add an info about the required min. bid increase which I wasn't able to figure out quickly (cc @michele-franchi)

Expired

[ ] "Block" -> "Keyblock"
[ ] "estimated" -> "exact"
[ ] "Name" -> "name" ? (consistency topic)
[ ] "address" -> "account"

[ ] replace with: "Account that previously paid the shown price to claim the name."

[ ] "Name" -> "name" ? (consistency topic)

I agree to use Keyblock instead of Block.
After the observation of 2 of our competitors, they are sung Big Caps in labels but small caps in hints. Both the same approach, so I guess we can imitate it.

Agree?

After the observation of 2 of our competitors, they are sung Big Caps in labels but small caps in hints. Both the same approach, so I guess we can imitate it.

this is exactly how I would propose it, too. great to hear that they are using the same approach. makes it a lot easier to avoid spelling inconsistency

Agree, let's use lowercase then 👍

I have another topic (if not already mentioned above)

[ ] change label to "Response format"

In state channels there is actually estimated time calculated on FE from keyblock

In state channels there is actually estimated time calculated on FE from keyblock

ok, but why? 🤔 but I am also seeing some inconsistency here again for "Last Updated" (just in case you want to align that also everywhere)

In state channels there is actually estimated time calculated on FE from keyblock

ok, but why? 🤔 but I am also seeing some inconsistency here again for "Last Updated" (just in case you want to align that also everywhere)

Simply just there is no micro_time in the response

Where we are using micro_time I used the exact phrasing. Other places were left with estimated. I have added comment above per occurrence where it's not possible to use exact

@marc0olo Some of the dashboard comments were more related to future improvements, so I move them here https://github.com/aeternity/aescan/issues/307 for clarity

yeah definitely enhancements / requests. makes sense 👍

Is this true? Or is the the amount of transactions executed by this account?

Yes, it's correct.

maybe change label to "Ends" instead of "Expires" ? I remember we wanted to keep it simple, but the hint needs to have a different content anyway

Agree, it's "Ends" in the names table for "In Auction" names so it should be the same.

for expired names we should change the label to "Last owner" and also adjust the hint maybe

Agree, it's "Last Owner" in the names table for "Expired" names.

How about this

here we should add an info about the required min. bid increase which I wasn't able to figure out quickly (cc @michele-franchi)

That would also be great, please have a look at it.

That would also be great, please have a look at it.

Well I haven't found any information about it
https://docs.aeternity.com/protocol/AENS/

That would also be great, please have a look at it.

Well I haven't found any information about it https://docs.aeternity.com/protocol/AENS/

Added


threefry random number generator broken

Hi,
There are 2 issues.

Threefry does not adhere to the interface of generators. The following program will not compile:

#include <boost/compute/system.hpp>
#include <boost/compute/random/threefry_engine.hpp>
#include <boost/compute/random/normal_distribution.hpp>
#include <boost/compute/random/uniform_real_distribution.hpp>

namespace compute = boost::compute;
int main()
{
	// get default device and setup context
	compute::device gpu = compute::system::default_device();
	compute::context context(gpu);
	compute::command_queue queue(context, gpu);
	compute::threefry_engine<> random_engine(queue);

	compute::uniform_real_distribution<float> random_distribution(0.f, 4.f); //does not compile
	// compute::normal_distribution<float> random_distribution(0.f, 4.f); // compiles

	compute::vector<float> random_values(10, 0.0,queue);

	random_distribution.generate(
		random_values.begin(), random_values.end(), random_engine, queue
	);
}

Threefry does not have any source of entropy and adding the following to the code above will print out two times the same sequence:

    for(std::size_t i = 0; i != 2; ++i){
		compute::vector<compute::uint_> random_values(10, 0.0,queue);

		random_engine.generate(
			random_values.begin(), random_values.end(), queue
		);

		std::vector<compute::uint_> values_cpu(10);
		boost::compute::copy(random_values.begin(),random_values.end(), values_cpu.begin(), queue);

		for(std::size_t i = 0; i != 10; ++i){
			std::cout<<values_cpu[i]<<" ";
		}
		std::cout<<std::endl;
	}

This behaviour is not observed when generating normally distributed numbers from the generator. This is because the input sequence to the generator is not initialized and thus the generator relies on uninitialized memory, see https://github.com/boostorg/compute/blob/d36ef02b7860b9bcf5ea4911b77f1aa77b5f4059/include/boost/compute/random/normal_distribution.hpp#L91

How to fix this:
Threefry relies on its key as source of entropy and then generates the random numbers from a simple counting sequence 1,2,3.. . So an easy solution would be to use a mt19937 on cpu to generate a key and set it as kernel argument. This would also allow seeding through the mt19937. Then, within the kernel the function threefry2x32_R should be given the number of the current random number as first and the key as second argument. It is okay if the sequence starts every time from 0, as threefry would still be able to generate 2^64 different sequences. If this is not enough, either use threefry4x32_R for 2^128 different sequences or initialize the counter to some random offset.

is actually worse, this is the first line of the output:
1.93434e+26 -1.92639e-23 1.93434e+26 -1.92639e-23 1.93434e+26 -1.92639e-23 1.93434e+26 -1.92639e-23 1.93434e+26 -1.92639e-23

see how it is two numbers alternating?

I've been thinking about reimplementing it or introducing working Philox
RNG. I'll take a look at it this week.
08.10.2017 12:52 PM "Oswin Krause"<EMAIL_ADDRESS>napisał(a):

is actually worse, this is the first line of the output:
1.93434e+26 -1.92639e-23 1.93434e+26 -1.92639e-23 1.93434e+26
-1.92639e-23 1.93434e+26 -1.92639e-23 1.93434e+26 -1.92639e-23

see how it is two numbers alternating?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/boostorg/compute/issues/745#issuecomment-334998303,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACmCBMOFHEXgoxXH27153CO9IgBYl5poks5sqKligaJpZM4PxqcS
.

i'd be happily offering a quick code check if you want

Thanks, when I have something I'll make a push request, so you can review it. Are you more interested in Threefry or Philox, or you just need fast RNG?

I mostly checked the threefry implementation in boost.compute to compare it with the Shaw-paper. I unfortunately need to roll my own, so I wanted to make sure i understood it correctly. But I mostly need a fast Rng and the most interesting aspect of threefry/philox etc is that one can easily transform matrix-indices to random numbers, which makes a lot of kernel logic very simple.

transform matrix-indices to random numbers, which makes a lot of kernel logic very simple.

Can you elaborate?
How I plan to implement Philox: one state (128-bit counter) for the generator, key is generated from seed given by a user (64-bit unsigned integer), in each thread generates 4 random numbers using counter, thread index, and key (we sum counter and thread idx to get unique counter for each thread), finally we update the counter increasing it by the number of generated values.

The pull request seems okay. Nice improvement.

Can you elaborate?
I would implement it as outlined above by picking a random key and use a counter starting from 0.
This allows to use a nice property of the counter based rng: if you want to generate N random numbers, then the subsequences i,i+N,i+2*N... (i=0...N-1) are sequences of independent random numbers. This allows to implement rejection sampling extremely efficiently in kernel by just letting the kernel reject (compare with the discrete distribution). I would also favour a design where only one kernel is run to generate a random number instead of first generating a vector of 32 bit uint numbers which are then transformed in another kernel call. This could be done by having one program that has kernels to generate all supported types of random numbers (but at least the uniform distributions)

I am currently playing around with a very basic implementation of this:
https://github.com/Shark-ML/Remora/blob/gpu_kernel_rework/include/remora/kernels/gpu/random.hpp

I would also favour a design where only one kernel is run to generate a random number instead of first generating a vector of 32 bit uint numbers which are then transformed in another kernel call. This could be done by having one program that has kernels to generate all supported types of random numbers (but at least the uniform distributions)

Indeed, that would save some performance. Maybe I'll do that late (because I'd have to do this update for every RNG in BC).

Fixed by #747


UNMET PEER DEPENDENCY<EMAIL_ADDRESS>

npm i --save react-native-admob@next
I get the following error when I run it. Then i guess install nothing.
+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>

Which version of React and React native do you use?

react-native-cli: 2.0.1
react-native: 0.48.0

react-native-admob has no peerDependency on  react, so this is probably an issue with a different library.


FrankerFaceZ sending same message multiple times

Hello
I use Franker FaceZ on my computer together with BTTV, now in FFZ there is an option that allows you to send the same message multiply times without getting the "same message"error.
I think this is really nice and would fit very well in this app.

Lol what a nice welcome here ❤


error while press  in normal mode.

Errors while press esc in normal mode.
Thanks.

What is the exact steps to reproduce?

Cursor in blank area(no word) then press esc.

can you describe the steps so that even a newbie can reproduce it following the steps.

I test the key map and find I make a mistake to noremap the key to call "Leaderf! gtags -d %s --auto-jump".
Sorry and thank you!


Adding "unkown"

Summary
It can happen that the network can't locate the device, because it is offline and the location is also not cached. In this there should be coming the right response from the API.
Changes
Adding to true or false the return value unkown, when it is not possible to get the location

@NoelWirzius Write issue, wrong API :) please move this to DeviceLocation


Fix the link to the github repo

👍 thanks!

@erickmerchant This actually needs to be fixed in master as well, because the gh-pages are built from master. I'll handle that.


PH and SH are not supported

AS you can see here https://wiki.openstreetmap.org/wiki/Key:opening_hours PH and SH can be used as a prefix to differentiate hours for holidays.
RIght now if used it breaks the parsing.
Would be nice to support it

Would be nice to support it

Couldn't agree more! I do wonder though, how it could work? Like, would we need to have PH database? Require passing PH list in some format when passing a string with PH in it? 🤔

I think they should just be handled as special days like sh_no or something. That way everything else stays the same. Thinking our loud...


Proposal: Default Arguments in Go

Go Programming Experience
Intermediate
Other Languages Experience
Python, PHP, JavaScript
Related Idea

[ ] Has this idea, or one like it, been proposed before?
[ ] Does this affect error handling?
[ ] Is this about generics?
[X] Is this change backward compatible? Breaking the Go 1 compatibility guarantee is a large cost and requires a large benefit

Has this idea, or one like it, been proposed before?
I think no
Does this affect error handling?
No
Is this about generics?
No
Proposal
Introduce default arguments to Go functions to simplify function calls when certain arguments have common or default values. This change will help developers avoid boilerplate code and make function signatures cleaner.
Language Spec Changes
The language spec would be updated to include syntax for default arguments in function definitions.
Informal Change
You could define a function with default values for some parameters, allowing you to call it without specifying those parameters each time.
Is this change backward compatible?
Yes
Orthogonality: How does this change interact or overlap with existing features?
How does this change interact or overlap with existing features?
Default arguments would be an additional feature but would not conflict with existing Go language features. It will integrate naturally with existing function calls and parameter handling.
Is the goal of this change a performance improvement? No
Would this change make Go easier or harder to learn, and why?
It would make Go easier to learn and use for developers familiar with default arguments in other languages, reducing boilerplate code and improving code readability.
Cost Description
Implementation complexity and potential changes to the Go compiler and toolchain to support default arguments.
Changes to Go ToolChain
Tools that analyze, format, or modify code might need updates to support default arguments.
Performance Costs
What is the compile time cost? Minimal, as default arguments would be a syntactic change rather than a runtime feature.  What is the run time cost? Minimal impact on runtime performance. The change primarily affects function call syntax and does not introduce significant runtime overhead.
Prototype
The implementation could involve modifying the Go parser and compiler to recognize default argument syntax and handle it appropriately during function calls. The default values would be substituted during function call resolution.

Related Issues and Documentation

proposal: spec: allow having default values for function declaration - Go2 #50766 (closed)
proposal: Go 2: allow default values in methods #38484 (closed)
proposal: Go 2: default values for named return parameters #44396 (closed)
proposal: Go 2: provide default values for function parameters when caller uses "_" #28197 (closed)
Set default value for functions or methods params #18765 (closed)
proposal: Go 2: default methods #23185 (closed)
Optional (or default) function arguments #1675 (closed)
proposal: Go 2: initialise funcs with custom type names #36855 (closed)
proposal: Go 2: make(...) should have the last (optional) parameter for configuring default values for all types (slices, maps and chans) #65332 (closed)
proposal: Go 2: default initializers for types #32076 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

see https://go.dev/doc/faq#overloading


User updates single action

As a User
I want to edit a record of an actin
So that I can make changes to its attributes. associated recommendations. indicatiors and assigned categories

This issue was moved to dumparkltd/hr-nmrf-client#10


Please invite me to the Recode-Hive GitHub Community Organization

Name
KAMTAM AMULYA
Discord Username (if applicable)
No response
Additional Context
No response

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/recodehive/people


[QUESTION] generated query includes invalid implicit type conversion

About You:
Name: Zhong Wang
Company: Alibaba
Your question:
Hi, I am the developer of the Alibaba MaxCompute plugin. We have received an issue from our customer that the query generated by Tableau is rejected by MaxCompute due to some semantic errors.
Here is part of the query generated by Tableau. The type of Fact_Suborders.order_date is DATETIME (a MaxCompute-defined type)
`Fact_Suborders`.`order_date` >= CAST(CONCAT(DATE_ADD(CAST(CAST(CONCAT(TO_DATE(CAST(FROM_UNIXTIME(UNIX_TIMESTAMP()) AS TIMESTAMP)), ' 00:00:00') AS TIMESTAMP) AS TIMESTAMP), CAST(-89 AS INT)), SUBSTR(CAST(CAST(CAST(CONCAT(TO_DATE(CAST(FROM_UNIXTIME(UNIX_TIMESTAMP()) AS TIMESTAMP)), ' 00:00:00') AS TIMESTAMP) AS TIMESTAMP) AS TIMESTAMP), 11)) AS TIMESTAMP)

The generated query includes a comparison between a DATETIME and a TIMESTAMP, which is invalid. Since the implicit conversion from DATETIME to TIMESTAMP is unsupported yet, we have to cast the DATETIME to a TIMESTAMP before comparing them.
Can I have some advice from your team?
Thank you very much!

Hey Zhong, we have a work item internal to track this issue, will get back to you as soon as we have a clear solution, thanks

Hey Zhong, we have a work item internal to track this issue, will get back to you as soon as we have a clear solution, thanks

@cornmonster Any updates on this? I sent you an email regarding help needed for maxcompute tdvt last Thursday, don't know if you got it or not, please let me know if you can help me with setting up maxcompute's tdvt, thanks.

@cornmonster Any updates on this? I sent you an email regarding help needed for maxcompute tdvt last Thursday, don't know if you got it or not, please let me know if you can help me with setting up maxcompute's tdvt, thanks.

@cornmonster Hey Zhong, after spending some time with this bug, the issue was due to how maxcompute format datetime literal, the old behavior was like CAST('2022-01-01 00:00:00' AS TIMESTAMP), which inherits from base dialect.
Two things are wrong with this format, one is maxcompute doesn't have implicit conversion between DATETIME and TIMESTAMP, so it will cause type mismatch when compare datetime with timestamp, two is the for datetime format, the correct one for maxcompute is yyyy-MM-dd HH:mm:ss, otherwise the comparison will be invalid. My fix is add this line to dialect file:
<format-datetime-literal formula="('%1')" format='yyyy-MM-dd HH:mm:ss' />
I manually tested this change locally, it can resolve the issue. I was trying to open a pull request in your repo, failed to do so since I don't have permission for that. can you give me permission for that? in the meanwhile, I am making this change to our internal repo, will keep you updated on that.

Sorry I didn't see your replies. I will verify the solution locally. And I have invited you as a contributor to our repo. Could you please submit a merge request?

@cornmonster I sent out a PR in your repo https://github.com/aliyun/aliyun-maxcompute-tableau-connector/pull/2, let us know how it goes, thanks.

@cornmonster I sent out a PR in your repo aliyun/aliyun-maxcompute-tableau-connector#2, let us know how it goes, thanks.

Hi, I changed the dialect and run the TDVT. But there is a new failure:
Test name: Filter.datetime_fractional
Test path: /tdvt/logicaltests/setup/calcs/setup.Filter.datetime_fractional.tdvt_test2_logical.xml
Generated SQL:
SELECT ('2016-07-15 10:11:12') AS calculation_958703807427547136,
1.1000000000000001 AS x__alias__0
FROM tdvt_test3.calcs Calcs
WHERE (CAST('2016-07-15 10:11:12.123' AS TIMESTAMP) = ('2016-07-15 10:11:12'))
GROUP BY 1.1000000000000001
Please see the attachment for the raw TDVT results.
tdvt_results.zip

The test case fails because of the where condition. (CAST('2016-07-15 10:11:12.123' AS TIMESTAMP) results in a MaxCompute Timestamp value. And ('2016-07-15 10:11:12') will be parsed as another MaxCompute Timestamp value before the comparison.
Since the MaxCompute Timestamp supports nanosecond precision, the where condition returns false so that there is no output.

The string literal of MaxCompute DATETIME is: "DATETIME 'yyyy-MM-dd hh:mm:ss'". But the test case still fails after I changed the line to
<format-datetime-literal formula="(DATETIME '%1')" format='yyyy-MM-dd HH:mm:ss' />
Also, I am not sure why changing the format of DATETIME's string literal solves this issue, could you please explain it?
Thanks!

I guess the problem is that Tableau follows the type system defined by java.sql.Types, while MaxCompute driver maps both MaxCompute-defined DATETIME and TIMESTAMP to java.sql.Types.TIMESTAMP. So Tableau cannot tell the difference between a MaxCompute DATETIME from a MaxCompute TIMESTAMP.
Thus, one solution is that Tableau sees a java.sql.Types.TIMESTAMP, it cast the column to MaxCmopute TIMESTAMP explicitly. For example, let's say the type of my_table.my_col is DATETIME, the generated SQL should be "CAST my_table.my_col AS TIMESTAMP".
Is it possible to do it by changing the dialect?

@cornmonster
can we set up a call for this issue? It is too tricky to comment back and forth on the github issue page, if ok with you, let me know your availability please, thanks.

Haven't heard from @cornmonster for two weeks, so close this, feel free to reopen if you think my solution is not sufficient.


Ordination plots with trajectories: add examples

Ordination plots can be complemented with trajectories over points when time series are available for some or all subjects, other entities. It is not yet clear whether this would deserve its own function but illustrative examples for basic use cases can be useful.
Examples to implement:

Paired data with multiple time points:

plot data with some ordination method (PCA, MDS, or other)
overlay trajectory for (a) all and (b) one or more selected subjects (based on subject ID/s, based on top10% changes, based on group indicated in colData)
indicate the strength of change by color

Paired data with two time points. This is already included in (1) but is a simpler case and could potentially come with some extra capabilities that are feasible for general time series.

The most suitable open data set for this could be discussed.

This would be the file: vignettes/miaViz.Rmd

Could be done with the vaginal microbiota data set from Gajer et al. (2012) also to reproduce the figure I created for the review Faust et al. (2015)

Where can I get the phyloseq object?


grpcat lacks any unit tests.

grpcat doesn't have any unit tests, and needs some.

The following unit test ideas start at basic functionality and progress to the more involved tasks of the program.
1. Argument Parsing
The goal of this unit test is to confirm whether the first part of grpcat.py is parsing command line arguments correctly. The test can be expanded to check whether invalid arguments, sequences and formats produce the correct error output, and whether the program is handling exceptions correctly. The test would involve comparing (using assert) the return value of the function with expected output. The error handling tests would involve feeding various types of incorrect input as arguments, and checking if the appropriate error output is as expected.
2. Server/RPC Response
The first part of this unit test would determine whether the connection with the server was successful or has failed and the program terminated. The second part - if there was a successful connection - tests if the response matches the expected value. The expected value, or its features to generate the expected value (the get_hello_request.txt for instance) could be provided to the unit test as input. The test would then determine if the response matches the expected value.
3. Timeout and deterministic output
This unit test would check how long it takes the program to produce the expected response given the input data in the get_hello_request.txt. This would include testing if the program takes too much time (exceeds a limit) and how much time it takes for a particular input, which can be tested multiple times and its duration could be compared, averaged and asserted with an expected value. (This would be useful to see how the input affects the runtime as well.) The second part of this test would be to check whether the program (or response) is deterministic, i.e. produces the same output given the same input multiple times. This could be implemented using a loop and comparing actual vs expected output. If the output differs with the same input one can look for the cause and fix the issue.

Thanks @danielOsvath !
I like all the ideas! One thing to make sure is that for #2 you don't require a server be up - eg, you mock the server in the unit test (doing #2 with a server running would be a good integration test, but outside the scope of this issue).
Thanks!

I have revised test #2 and divided the other tests to the smallest units possible.

Argument Parsing
a) Expected Parse
The goal of this unit test is to confirm whether the first part of grpcat.py is parsing command line arguments correctly. The test would involve comparing (using assert) the return value of the parse_args() function with expected output.
b) Errors
Another test can be implemented to check whether invalid arguments, sequences and formats produce the correct error output, and whether the program is handling exceptions correctly. The error handling tests would involve feeding various types of incorrect input as arguments, and checking if the appropriate error output is as expected.

Server/RPC Response
This unit test checks whether the output from grpcat using a mock server produces the expected value. The expected outputs could be created manually, or generated based on the get_hello_request.txt, and compared with the grpcat output (the server response). The test inputs for grpcat could be written to the .txt file.

Timeout and deterministic output
a) Time Limit
This unit test would check how long it takes the program to produce the expected response given the input data in the get_hello_request.txt. This would include testing if the program takes too much time (exceeds a limit).
b) Expected time based on input
This test would check how much time it takes for a particular input, which can be tested multiple times and its duration could be compared, averaged and asserted with an expected value. (This would be useful to see how the input affects the runtime as well.)
c) Consistent output
The second test would be to check whether the program (or response) is deterministic, i.e. produces the same output given the same input multiple times. This could be implemented using a loop and comparing actual vs expected output. If the output differs with the same input one can look for the cause and fix the issue.

Perfect! Send a pull request and I'l review. Thanks!


How to turn off all funky stuff... no brace matching, no auto-completion, just want basic mode

Title says it all. I can't find anything.
Also, on a light themed terminal the default grays are just unreadable. I can't find any documentation on how to chnage that.

I guess some hints are found in isocline.c for example:
ic_enable_brace_matching(false);
ic_enable_brace_insertion(false);
ic_enable_completion_preview(false);
ic_enable_color(false);
and it seems that NULLs disable functionality as well (I don't get bus errors or segfaults so far)
ic_set_default_completer(NULL, NULL);
ic_set_default_highlighter(NULL, NULL);

Thanks.
On Mon, Feb 28, 2022 at 7:59 AM flexoron @.***> wrote:

I guess some hints are found in isocline.c for example:
ic_enable_brace_matching(false);
ic_enable_brace_insertion(false);
ic_enable_completion_preview(false);
ic_enable_color(false);
and it seems that NULLs disable functionality as well (I don't get bus
errors or segfaults so far)
ic_set_default_completer(NULL, NULL);
ic_set_default_highlighter(NULL, NULL);
—
Reply to this email directly, view it on GitHub
https://github.com/daanx/isocline/issues/10#issuecomment-1053696142, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEU6AEHXFUERJWO76MDU5KNCPANCNFSM5PMXJQ3A
.
You are receiving this because you authored the thread.Message ID:
@.***>

I am now using ISOCLINE as the default in https://github.com/trealla-prolog/trealla
Thanks

Yes, the header file shows these options best, see https://github.com/daanx/isocline/blob/main/include/isocline.h#L315
Trealla looks like a fun project -- let me know if you find further issues.


Not using Environment variables defined in docker-compose.yml

I have defined some environment variable under the field environment in my docker-compose.yml. However, it seems like they are not used, and I had to manually copy them to the secrets tab.
Is this how it is intended to work when deploying with docker-compose?
Would it be possible to add a feature to use the environment variables defined in docker-compose.yml?

Yeah, I had that problem too. coolify version 3.12.36

Yeah, I had that problem too. coolify version 3.12.36

Looks like it was fixed in version 3.12.37

Can this issue be closed then?

@Kuzat This has been fixed in v4.
Hardcoded environment variables are not shown in the UI (TEST=TEST -> not shown, as it is not needed to be changed), only those defined as variables can be set in the UI ('TEST=${TEST}' shown in the UI to change).


Add binary tree

i added searching and sorting on binary tree

Thank you for contributing to @AllAlgorithms, your pr got merged! ✨ Make sure that you ⭐ the project 🤓, and continue helping us!


exec does not working in mingw bash in windows

seems like exec works in cmd and powershell in windows but stalls when running in mingw bash in windows.

@arturadib any progress regarding this ;)

Cause stall for this snippet ;)
			// Run external tool synchronously.
			var command = 'msgfmt -o ' + file.dest + ' ' + file.src[0];
			if( shell.exec( command ).code !== 0 ) {
				grunt.log.error( 'Failed to Compile "*.po" files into binary "*.mo" files with "msgfmt".'.cyan );
				shell.exit(1);
			} else {
				grunt.verbose.writeln( 'File ' + file.dest.cyan + ' Created.' );
			}

we recently changed the exec command to use Node's latest execSync.. can you please try the latest version from npm? (0.4.0) thanks

@arturadib
The latest update may fix this issue, don't know yet because now there is a new error. I'm guessing it has to due with space characters in the path name. Please see the attached screenshot. Notice the very first error, the path name is truncated at the first space in the path name.
I think there might be an issue with spaces in the path name in po

Ref: https://github.com/WP-Translations/grunt-transifex-wordpress/issues/9#issuecomment-82490659

Oh, it  works fine when run from cmd.exe.

@devTristan I know you've been looking for Windows bugs to solve, this may be a good one! :)

Ok, I did two tests...

I move my project to a path which did not contain spaces in the path name. I got the exact same error message when using powershell; cmd worked fine.
I created a new admin user on my Win8.1 machine and logged into it. This new user did not have a space in its name. I opened powershell and navigated to the project that i created for 1. and it worked.

So the issue definitely has to do with the space in the file path but not the path in relation to the actual project. I suspect it has something to do with the file that shelljs writes to the users temp folder.

Ok, I tracked it down to the _tempDir() function.
I changed this:
  state.tempDir = writeableDir(os.tempDir && os.tempDir()) || // node 0.8+
                  writeableDir(process.env['TMPDIR']) ||
                  writeableDir(process.env['TEMP']) ||
                  writeableDir(process.env['TMP']) ||
                  writeableDir(process.env['Wimp$ScrapDir']) || // RiscOS
                  writeableDir('C:\\TEMP') || // Windows
                  writeableDir('C:\\TMP') || // Windows
                  writeableDir('\\TEMP') || // Windows
                  writeableDir('\\TMP') || // Windows
                  writeableDir('/tmp') ||
                  writeableDir('/var/tmp') ||
                  writeableDir('/usr/tmp') ||
                  writeableDir('.'); // last resort

To this:
	state.tempDir = writeableDir('C:\\TEMP') || // Windows
	writeableDir('C:\\TMP') || // Windows
	writeableDir('\\TEMP') || // Windows
	writeableDir('\\TMP') || // Windows
	writeableDir('.'); // last resort

And it worked from powershell. The temp file ended up being written to the project folder instead of the temp folder in c:\TEMP.
What the solution is from here, I do not know... but hopefully this helps!

Any news on this? Experiencing the same (see below) with shelljs 0.5.3.
Error: Command failed: "c:\Program Files\nodejs\node.exe" c:\Users\Arve Seljebu\AppData\Local\Temp\shelljs_5f1db58f6af48df8b8a5
    at checkExecSyncError (child_process.js:464:13)
    at Object.execSync (child_process.js:504:13)
    at execSync (c:\Users\Arve Seljebu\Documents\GitHub\lesson_editor\node_modules\shelljs\src\exec.js:81:11)
    at _exec (c:\Users\Arve Seljebu\Documents\GitHub\lesson_editor\node_modules\shelljs\src\exec.js:214:12)
    at c:\Users\Arve Seljebu\Documents\GitHub\lesson_editor\node_modules\shelljs\src\common.js:182:23
    at Object.<anonymous> (c:\Users\Arve Seljebu\Documents\GitHub\lesson_editor\ghpages.js:13:1)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)

@ariporad Why remove the bug label? Is breaking on usersnames with spaces intended behavior?
I see you write

I'm going to setup some better labels, is that OK?

in #272. What is a better label?

I think he just removed all the old labels. I think the label  we're using for bugs is "fix" (although I personally liked the "bug" label better). I suppose if we think of "fix" as meaning "please fix this" for github issues and "fix" as meaning "this is a fix" for pull requests, then it all makes sense.

@arve0, @nfischer: Yeah, that's exactly right. I have a script which nukes all the existing labels and creates new ones.
@nfischer: The reason for fix is that at the time we were planning to use the commit message guidelines, so I created a label for each commit message type (chore/fix/test/feat/etc.).

Yup, I figured that was the other reason.
Back to the issue at hand, I think we agree that this is in fact an issue, and I've applied the label. I'll try testing out #263 and see if this is in fact an issue and if that fixes the concern.


RNN  number of layers

Hi Marian,
Re the number of  rnn_layers for GaitNetwork in read.me:
At:  Gait recognition
.....
Initialize computational graphs of both sub-networks
net_pose = HumanPoseIRNetwork()
net_gait = GaitNetwork(recurrent_unit = 'GRU',  rnn_layers = 2)
.....
And At: Last Paragraph
....
The name describe used architecture (model-RNNcell-layers), so e.g. checkpoint H3.6m-GRU-1.ckpt should be loaded in this way:
net_pose = HumanPoseIRNetwork()
net_gait = GaitNetwork(recurrent_unit = 'GRU', rnn_layers = 1)
.....
Which value you used to obtain your results? 1 or 2?
Has any sense /reward to increase the rnn_layers?
Thanks in advance!

Hi @jbkarle
the results can be seen in the graph at the end of the page. And it turns out that adding more layers make model more complicated and harder to train. Thus, as you can see, the results was slightly worse.


Uncaught Error - new NativeEventEmitter() requires a non null argument

Hello,
I need to use harness for feature flags for react native project, I follow up every step from you documentation and I'm not able to build application because of crash:

I tried to debug this and I realise that this line of code is the issue

At this point it will try to execute new NativeEventEmitter with null

This is on react-native version 0.72.4
I also tried on older version 0.71.4 but it has the same issue.
Please help me how to solve this error

@davejohnston and @erdirowlands
As the (now) responsible team lead here and a paying customer it a bit frustrating to see how the issue from my team mate was ignored within the last 4 months. Today the question was raised why not switch the feature flag backend to other competitors.
So lets see: There is a deprecation note in your online documentation (now):

I expect this ticket will never be solved and it also does not make sense to solve it with that in mind. Anyway I think some feedback in a reasonable time can be expected for next time in such a case.
Also this repository does not contain any deprecation note, so you should add one with a red color. I am no expert in that area, but there is no hint in the react SDK about usage in react native environment. So nothing to mention? Works as perfect replacement for React Native on iOS?

@bormm let me give you my apologies for this.  We should have been updating you're colleague on the plans for react native.
As an existing customer please do raise tickets via the customer support portal as they will be routed directly to us and flagged with both the product and engineering team (though that is no excuse for not keeping these issues active).
We are currently working to provide examples of how to use the react SDK within a reactive native environment.  Can I ask, have you adopted the react native SDK anywhere in existing code, or were you alway blocked from using it?  In either case we can offer some time with one of our engineers to help provide guidance on using the react SDK.
If you would like to discuss how the react SDK can be used, please raise a support ticket (if you don't have access to the support portal let me know here and I will work with CS to reach out to you).

@KOKOdeveloper, @bormm we've just released v2.0.0 of the React Native Client SDK that simplifies how to install and use the SDK in React Native. I'm going to close this issue now. Please reach out if there is anything we can help with!


Archive logfile not created when using --skip-download when getting subtitles.

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2019.06.08
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

N/A

Description

When --skip-download is used apparently --download-archive has no effect.
It has to initialize each youtube video download and only then figures out there's a subtitle file already present, the process is very slow, almost the same as if when it's downloading them.

This is expected behavior.


Files in public directory being opened as UTF8 Strings

I'm trying to load images from the public directory but it seems from looking at the router code that anything loaded from the public directory needs to be source code—like css or js files.
// In Router.swift
if let body = String(data:contents!, encoding: NSUTF8StringEncoding) {
    return Response(.Ok, contentType: "text/plain; charset=utf8", body: body)
}

We should be able to also load images and other assets from that directory. Also CSS files and JS files should return a different mimetype than text/plain.

This issue isn't as simple as writing an else statement and returning a different response since responses must have a body of the following type: String?
I'm trying to figure out a solution for this but most likely won't come up with the most graceful one. I'll submit a PR if I think my solution is viable.

@califrench thanks. I believe there is solution for mime types management in Swift, we should not be very first facing this issue :) Please let me know if you will find something.

@sauliusgrigaitis I realized that this was highlighting two different issues as I typed my explanation up.
One issue is the fact we are sending all assets with text/plain but the bigger issue is we can only return text resources and not binary files with a Response

This is no longer an issue.

This is a duplicate of #28


Role based redirects using _redirects

Today i encountered an issue with trying to use role based redirect in the _redirects file
eg:
/about 200! Role=authorized
/about /.netlify/functions/login 401!
But then i found these rules only worked for pages that were statically built at buildtime (so they had a .html file)
I realised this was because i was overriding the standard nextjs redirects that would take the user to the appropriate function and build the page on demand or show a 404 error.
I was able to resolve my issue withe the following config:
/about /.netlify/functions/___netlify-handler 200! Role=authorized
/about /.netlify/functions/login 401!
Question:
Does this seem like the correct solution, should i expect any issues with the above config?

Hi. It's not ideal, but yes I think that's the only realistic approach. You'll need to do something with the data route too if people are likely to navigate there. You can set a static build id by adding this to your next.config.js:
generateBuildId: () => "build-id",

...and then add this route to your rules:
/_next/data/build-id/about.json


Unused code gets go vet error

 go vet ./...
# mosn.io/envoy-go-extension/pkg/utils
pkg/utils/string.go:12:22: possible misuse of unsafe.Pointer
pkg/utils/string.go:20:22: possible misuse of unsafe.Pointer
# mosn.io/envoy-go-extension/pkg/http
pkg/http/capi.go:36:79: possibly passing Go type with embedded pointer to C

I have checked all the errors, and it seems they come from unused file or argument, so we can simply remove them.
	C.moeHttpSendLocalReply(r, C.int(response_code), unsafe.Pointer(&body_text), unsafe.Pointer(&strs), C.longlong(grpc_status), unsafe.Pointer(&details))

We can pass the addr of a flat buffer instead of []string to avoid possibly passing Go type with embedded pointer to C
	sHdr.Data = uintptr(unsafe.Pointer(uintptr(ptr)))

It seems we can simply write sHdr.Data = uintptr(ptr) in this case? Do I miss something?

@spacewander Nice catch~

for possible misuse of unsafe.Pointer
yes, it's a misuse. Patch welcome ~

for possibly passing Go type with embedded pointer to C
it's an expected warning. It's unsafe usage for cgo, which is also desired.
(We also disabled cgocheck for unsafe passing Go pointer from go to c and c to go).

We can pass the addr of a flat buffer instead of []string

this could be a proper way to mute this vet warning, but I'm not sure if it's worthing, it may complicate the code.
we need to reflect the flat buffer into []string before using it as strings. thoughts?

this could be a proper way to mute this vet warning, but I'm not sure if it's worthing, it may complicate the code.

What about passing the Data ptr like:
https://github.com/mosn/envoy-go-extension/blob/c20a07ecb9add915f8f8f17f499bdf95949ac549/pkg/http/capi.go#L46-L55

Actually we can delay the possibly passing Go type with embedded pointer to C suppression as the headers argument is not used at all. 😃


minimal instrumentation example for SFN-WDL

@tfrcarvalho Here's a minimal starting point for custom task instrumentation. It causes a JSON message like the following to be emitted in the SFN-WDL environment, where it's picked up by CloudWatch Logs (probably along with further contextual details about the execution, though we may need to do more -- elaborated below).
{
  "message": "SFN-WDL task done",
  "level": "NOTICE",
  "run_id": "call-hello-2",
  "task_name": "hello",
  "elapsed_seconds": 8.465,
  "timestamp":<PHONE_NUMBER>.337,
  "source": "wdl.w:hello_caller.t:call-hello-2",
  "levelno": 25
}

The code measures the time between points in the task plugin "coroutine" which gets control at a few key moments in the task lifecycle (detailed in this example).
Some discussion points:

Is there enough detail to group/aggregate the collected timings in the ways we want to, by searching for these messages in CloudWatch Logs?
In particular, the task and run_id (reflecting specific place the task is called in the workflow) are included but not anything identifying the inputs or the "execution." Some identifying information might be added by CloudWatch Logs, we need to check if it's adequate.
The plugin does have access to all the inputs and outputs, as well as task.meta (the arbitrary metadata stanza one can put in the source code), so there are all sorts of details we can add; just need to spec them out after closing the proof-of-concept loop with CloudWatch Logs.

@mlin  I think this is a good starting point.
I think an idseq engineer can follow up on this and add the necessary detail.
To facilitate that work can you add a comment next to the logger call on how to access the inputs, outputs and source or wdl/tasks names if we move to a directly call to cloudwatch metrics? If there is a documentation link for the plugin's interface, that would probably suffice.

@mlin  I think this is a good starting point.
I think an idseq engineer can follow up on this and add the necessary detail and make the call if we need to publish the metric directly.
To facilitate that work can you add a comment next to the logger call on how to access the inputs, outputs and source or wdl/tasks names if we move to a directly call to cloudwatch metrics? If there is a documentation link for the plugin's interface, that would probably suffice.

@tfrcarvalho Yea, I added links to the docs for the AST data structure, and a thoroughly commented example which is currently the best available documentation we have for the plugin interface. (Creating proper docs for that is one item later on @lynnlangit agenda)

@tfrcarvalho Yea, I added links to the docs for the AST data structure, and a thoroughly commented example which is currently the best available documentation we have for the plugin interface. (Creating proper docs for that is one item later on @lynnlangit agenda)

Great, the example is ideal.


[Disk Manager]: Except hanging tasks types in tests

Currently, we have an overwhelming number of hanging tasks which are not seen on the prod in tests. Need to add ExceptHangingTaskTypes config option to the tests recipe.

We are going to reconsider hanging task metric to make it non-dependent on task type


Added Pyenv file system watcher

This is very similar to workspace virtualenv watcher https://github.com/microsoft/vscode-python/pull/14780, and global virtual env as well. I have consolidated all of them in this PR.

@int19h @kimadeline I'm merging this now. If there're other concerns you can still comment here, and I'll address them separately.


[Task]

Description
remove and translate chinese to english in code
Task List

[ ] remove and translate chinese to english in moudle alerter
[ ] remove and translate chinese to english in collector
[ ] remove and translate chinese to english in common
[ ] remove and translate chinese to english in manager
[ ] remove and translate chinese to english in push
[ ] remove and translate chinese to english in remoting
[ ] remove and translate chinese to english in script
[ ] remove and translate chinese to english in warehouse
[ ] remove and translate chinese to english in web-app
[ ] remove and translate chinese to english in home

I claim alerter module.

[ ] remove and translate chinese to english in moudle alerter

I claim common module.
remove and translate chinese to english in common

i claim collector,script,push,remoting and manager module
remove and translate chinese to english in module collector
remove and translate chinese to english in module script
remove and translate chinese to english in module push
remove and translate chinese to english in module remoting
remove and translate chinese to english in module manager

I claim warehouse module.

hello, are there any other modules  i can help ?

hello, are there any other modules i can help ?

hi sorry it seem all tasks have been pinned.


Use "" instead of -1 to represent unknowns

What's New?

One last tweak to <AxisInputBox/> before diving into the big FBJS 4.2.0 upgrade.

Coverage remained the same at 21.14% when pulling aa292385cf2f9454f60a7ae8e380ffb65c454dc7 on RickCarlino:master into 9d18b5324ca310b1abd501901d92a932ea3074c7 on FarmBot:master.


(Request) weapon,nade icons for esp

i tried to add nade image too make this but it fucked my fps so i found this (https://www.unknowncheats.me/forum/cs-go-releases/169881-csgo-weapon-icons-ttf-font.html) post that he made for every gun
im just gonna ask can someone make it for osiris please @danielkrupinski its nice if u can add this to main cheat better than "granade" text i think
Here is example: https://streamable.com/254fu0

+++ nade timer is necessary feature for legit cheat

just paste it from sensum.


fix: Parity IAP analytics with legacy app

Description:

Update IAP analytics structure.
Update flow_type for all the IAP analytics events
Generalized event triggering in ViewModels

fix: LEARNER-10225

Hey @dixidroid & @HamzaIsrar12 , I have rebased the PR with 2U/develop  and update the code accordingly.