Veldrid fails to build on iOS

Happens due to Veldrid referencing Vortice.Direct3D11, which depends on SharpGen.Runtime for generating bindings, and that library cannot be AOT'd on iOS.
0>Mono Ahead of Time compiler - compiling assembly /Users/salman/Projects/osu-framework/SampleGame.iOS/obj/iPhone/Debug/net6.0-ios/ios-arm64/linked/SharpGen.Runtime.dll
AOTID 7CA136D1-DC5C-CDE1-6269-4B4A034E7F8B
* Assertion at /Users/runner/work/1/s/src/mono/mono/metadata/custom-attrs.c:599, condition `out_obj' not met

0>Tool /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/6.0.11/Sdk/../tools/mono-aot-cross execution started with arguments: --aot=mtriple=arm64-ios,data-outfile=obj/iPhone/Debug/net6.0-ios/ios-arm64/nativelibraries/aot-output/arm64/System.Drawing.Common.aotdata,static,asmonly,direct-icalls,full,readonly-value=ObjCRuntime.Runtime.Arch=i4/0,soft-debug,dwarfdebug,no-direct-calls,outfile=obj/iPhone/Debug/net6.0-ios/ios-arm64/nativelibraries/aot-output/arm64/System.Drawing.Common.dll.s --aot= --debug -O=gsharedvt /Users/salman/Projects/osu-framework/SampleGame.iOS/obj/iPhone/Debug/net6.0-ios/ios-arm64/linked/System.Drawing.Common.dll

0>/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/16.0.527/targets/Xamarin.Shared.Sdk.targets(1003,3): Error  : Failed to AOT compile SharpGen.Runtime.dll, the AOT compiler exited with code 134
0>Tool /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/6.0.11/Sdk/../tools/mono-aot-cross execution started with arguments: --aot=mtriple=arm64-ios,data-outfile=obj/iPhone/Debug/net6.0-ios/ios-arm64/nativelibraries/aot-output/arm64/System.Security.Cryptography.Pkcs.aotdata,static,asmonly,direct-icalls,full,readonly-value=ObjCRuntime.Runtime.Arch=i4/0,soft-debug,dwarfdebug,no-direct-calls,outfile=obj/iPhone/Debug/net6.0-ios/ios-arm64/nativelibraries/aot-output/arm64/System.Security.Cryptography.Pkcs.dll.s --aot= --debug -O=gsharedvt /Users/salman/Projects/osu-framework/SampleGame.iOS/obj/iPhone/Debug/net6.0-ios/ios-arm64/linked/System.Security.Cryptography.Pkcs.dll

0>Tool /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/6.0.11/Sdk/../tools/mono-aot-cross execution finished (exit code = 134).

0>Mono Ahead of Time compiler - compiling assembly /Users/salman/Projects/osu-framework/SampleGame.iOS/obj/iPhone/Debug/net6.0-ios/ios-arm64/linked/SharpGen.Runtime.COM.dll
AOTID A48F61D9-2494-6DF6-EBD4-7824B1850F51
* Assertion at /Users/runner/work/1/s/src/mono/mono/metadata/custom-attrs.c:599, condition `out_obj' not met

0>/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/16.0.527/targets/Xamarin.Shared.Sdk.targets(1003,3): Error  : Failed to AOT compile SharpGen.Runtime.COM.dll, the AOT compiler exited with code 134

That's a major blocker from using Veldrid on iOS platforms, and there's no way to exclude such libraries manually as far as I've seen.

I've worked around this by placing stub assemblies for the affected libraries using the following:
  <Target Name="CopyStubAssemblies" BeforeTargets="_AOTCompile">
    <Copy SourceFiles="@(StubFiles)" DestinationFolder="obj/$(Platform)/$(Configuration)/$(TargetFramework)/$(RuntimeIdentifier)/linked/" />
  </Target>


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #44.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #44

@conda-forge-admin , please re-render


Fix typo on style at top-chart.html

This change is

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

Reviewed 1 of 2 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Question about training loss.

Thank you for your excellent work, which has been very inspiring to me.
I have some questions about the loss function used for fine-tuning your network in the context of your paper. In the paper, you mentioned using 'the same training objective in standard LDMs' during fine-tuning. However, in Figure 4 of the paper, it is stated that the network uses a pixel-wise reconstruction loss, which seems to compute based on the input video and the reconstructed video instead of the predicted noise. Could you please clarify if I am misunderstanding something?

输入输出视频一样？视频拆成一帧帧图片，和同样的句子描述，输入sd，得到原始输入图片？
好像是这样。。

他的finetune网络估计就是这样训练的

I have a same question!!!!!
please help!


Unable to find image

@mburumaxwell Since yesterday (I think) when I run the task, I get this error:
Cannot find the image 'ghcr.io/tinglesoftware/dependabot-updater-npm:1.20' locally.
docker: Daemon error response: unknown manifest.
See 'docker run --help'.

Here I see that there is no 1.20 tag:
https://github.com/tinglesoftware/dependabot-azure-devops/pkgs/container/dependabot-updater-npm/versions?filters[version_type]=tagged

Same for dependabot-updater-docker, and I assume others.

Thanks for reporting. Check again, please

Thanks! Fixed!


Parametrize syslog extraction for Android

Device.isConnected()
Do we need to extract system logs everytime? Maybe we can parametrize this action and enable only for cloud execution...

Device.saveSysLog()
LOGGER.debug("STF is enabled. Sys log will be extracted...");
those message should be changed to something related to extraction log and remove any refernce to STF

6.1.25+
https://github.com/qaprosoft/carina/pull/778


[stable/redis] Split brain after failover

Hey,
I'm running into some issue running redis for HA using sentinel.

The cluster contains 3 nodes and each node is running redis+sentinel
3 pods are started redis-master-0, redis-slave-0 and redis-slave1 (all on different nodes)
If I force of failover of redis-master-0 then one of the slave is promoted, in this case slave-0
Problem is when master-0 comes back online redis ends up being split-brain:

slave-0 is master (from the promotion) with slave-1 as a slave
slave-1 is a slave of slave-0
master-0 is also master and doesn't have any slaves

I've attached some logs to hopefully provide some context
Here are the relevant redis info from the different nodes:
redis-master-0 (after restart from failover)
# Replication
role:master
connected_slaves:0
master_replid:81e9f47b37fab6f3aa19c5cc7f7ebd88b35e6bb5
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:0
second_repl_offset:-1
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

redis-slave-0 (after promotion to master)
# Replication
role:master
connected_slaves:1
slave0:ip=<IP_ADDRESS>,port=6379,state=online,offset=742199557,lag=1
master_replid:c81fc2e5d50177c91b8113909459302139039932
master_replid2:0a4fc8dbd0c9b315eda864042c40c771e58a23cd
master_repl_offset:742199557
second_repl_offset:526794803
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:741150982
repl_backlog_histlen:1048576

redis-slave-1
# Replication
role:slave
master_host:<IP_ADDRESS>
master_port:6379
master_link_status:up
master_last_io_seconds_ago:2
master_sync_in_progress:0
slave_repl_offset:742202495
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:c81fc2e5d50177c91b8113909459302139039932
master_replid2:0a4fc8dbd0c9b315eda864042c40c771e58a23cd
master_repl_offset:742202495
second_repl_offset:526794803
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:741153920
repl_backlog_histlen:1048576

Here is the config i'm using:
# Based on values-production.yaml

global:
  redis: {}

## Bitnami Redis image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
  registry: docker.io
  repository: bitnami/redis
  tag: 5.0.7-debian-9-r50
  pullPolicy: IfNotPresent

## String to partially override redis.fullname template (will maintain the release name)
##
# nameOverride:

## String to fully override redis.fullname template
##
# fullnameOverride:

## Cluster settings
cluster:
  enabled: true
  slaveCount: 2

## Use redis sentinel in the redis pod. This will disable the master and slave services and
## create one redis service with ports to the sentinel and the redis instances
sentinel:
  enabled: true
  ## Require password authentication on the sentinel itself
  ## ref: https://redis.io/topics/sentinel
  usePassword: true
  ## Bitnami Redis Sentintel image version
  ## ref: https://hub.docker.com/r/bitnami/redis-sentinel/tags/
  ##
  image:
    registry: docker.io
    repository: bitnami/redis-sentinel
    ## Bitnami Redis image tag
    ## ref: https://github.com/bitnami/bitnami-docker-redis-sentinel#supported-tags-and-respective-dockerfile-links
    ##
    tag: 5.0.7-debian-9-r44
    ## Specify a imagePullPolicy
    ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
    ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
    ##
    pullPolicy: IfNotPresent
    ## Optionally specify an array of imagePullSecrets.
    ## Secrets must be manually created in the namespace.
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
    ##
    # pullSecrets:
    #   - myRegistryKeySecretName
  masterSet: mymaster
  initialCheckTimeout: 5
  quorum: 2
  downAfterMilliseconds: 60000
  failoverTimeout: 18000
  parallelSyncs: 1
  port: 26379
  ## Additional Redis configuration for the sentinel nodes
  ## ref: https://redis.io/topics/config
  ##
  configmap:
  ## Enable or disable static sentinel IDs for each replicas
  ## If disabled each sentinel will generate a random id at startup
  ## If enabled, each replicas will have a constant ID on each start-up
  ##
  staticID: false
  ## Configure extra options for Redis Sentinel liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  ##
  livenessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 5
    successThreshold: 1
    failureThreshold: 5
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 1
    successThreshold: 1
    failureThreshold: 5
  ## Redis Sentinel resource requests and limits
  ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
  # resources:
  #   requests:
  #     memory: 256Mi
  #     cpu: 100m
  ## Redis Sentinel Service properties
  service:
    ##  Redis Sentinel Service type
    type: ClusterIP
    sentinelPort: 26379
    redisPort: 6379

    ## Specify the nodePort value for the LoadBalancer and NodePort service types.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
    ##
    # sentinelNodePort:
    # redisNodePort:

    ## Provide any additional annotations which may be required. This can be used to
    ## set the LoadBalancer service type to internal only.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
    ##
    annotations: {}
    labels: {}
    loadBalancerIP:

## Specifies the Kubernetes Cluster's Domain Name.
##
clusterDomain: cluster.local

networkPolicy:
  ## Specifies whether a NetworkPolicy should be created
  ##
  enabled: false

  ## The Policy model to apply. When set to false, only pods with the correct
  ## client label will have network access to the port Redis is listening
  ## on. When true, Redis will accept connections from any source
  ## (with the correct destination port).
  ##
  # allowExternal: true

  ## Allow connections from other namespacess. Just set label for namespace and set label for pods (optional).
  ##
  ingressNSMatchLabels: {}
  ingressNSPodMatchLabels: {}

serviceAccount:
  ## Specifies whether a ServiceAccount should be created
  ##
  create: false
  ## The name of the ServiceAccount to use.
  ## If not set and create is true, a name is generated using the fullname template
  name:

rbac:
  ## Specifies whether RBAC resources should be created
  ##
  create: false

  role:
    ## Rules to create. It follows the role specification
    # rules:
    #  - apiGroups:
    #    - extensions
    #    resources:
    #      - podsecuritypolicies
    #    verbs:
    #      - use
    #    resourceNames:
    #      - gce.unprivileged
    rules: []

## Redis pod Security Context
securityContext:
  enabled: true
  fsGroup: 1001
  runAsUser: 1001
  ## sysctl settings for master and slave pods
  ##
  ## Uncomment the setting below to increase the net.core.somaxconn value
  ##
  # sysctls:
  # - name: net.core.somaxconn
  #   value: "10000"

## Use password authentication
usePassword: true
## Redis password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
password:
## Use existing secret (ignores previous password)
existingSecret: redis
## Password key to be retrieved from Redis secret
##
existingSecretPasswordKey: redis-password

## Mount secrets as files instead of environment variables
usePasswordFile: false

## Persist data to a persistent volume (Redis Master)
persistence: {}
  ## A manually managed Persistent Volume and Claim
  ## Requires persistence.enabled: true
  ## If defined, PVC must be created manually before volume will be bound
  # existingClaim:

# Redis port
redisPort: 6379

##
## Redis Master parameters
##
master:
  ## Redis command arguments
  ##
  ## Can be used to specify command line arguments, for example:
  ##
  command: "/run.sh"
  ## Additional Redis configuration for the master nodes
  ## ref: https://redis.io/topics/config
  ##
  configmap:
  ## Redis additional command line flags
  ##
  ## Can be used to specify command line flags, for example:
  ##
  ## extraFlags:
  ##  - "--maxmemory-policy volatile-ttl"
  ##  - "--repl-backlog-size 1024mb"
  extraFlags: []
  ## Comma-separated list of Redis commands to disable
  ##
  ## Can be used to disable Redis commands for security reasons.
  ## Commands will be completely disabled by renaming each to an empty string.
  ## ref: https://redis.io/topics/security#disabling-of-specific-commands
  ##
  # disableCommands:
  # - FLUSHDB
  # - FLUSHALL

  ## Redis Master additional pod labels and annotations
  ## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
  podLabels: {}
  podAnnotations: {}

  ## Redis Master resource requests and limits
  ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
  # resources:
  #   requests:
  #     memory: 256Mi
  #     cpu: 100m
  ## Use an alternate scheduler, e.g. "stork".
  ## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
  ##
  # schedulerName:

  ## Configure extra options for Redis Master liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  ##
  livenessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 5
    successThreshold: 1
    failureThreshold: 5
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 5
    timeoutSeconds: 1
    successThreshold: 1
    failureThreshold: 5

  ## Redis Master Node selectors and tolerations for pod assignment
  ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
  ## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature
  ##
  # nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
  # tolerations: []
  ## Redis Master pod/node affinity/anti-affinity
  ##
  affinity: {}

  ## Redis Master Service properties
  service:
    ##  Redis Master Service type
    type: ClusterIP
    port: 6379

    ## Specify the nodePort value for the LoadBalancer and NodePort service types.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
    ##
    # nodePort:

    ## Provide any additional annotations which may be required. This can be used to
    ## set the LoadBalancer service type to internal only.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
    ##
    annotations: {}
    labels: {}
    loadBalancerIP:
    # loadBalancerSourceRanges: ["<IP_ADDRESS>/8"]

  ## Enable persistence using Persistent Volume Claims
  ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
  ##
  persistence:
    enabled: true
    ## The path the volume will be mounted at, useful when using different
    ## Redis images.
    path: /data
    ## The subdirectory of the volume to mount to, useful in dev environments
    ## and one PV for multiple services.
    subPath: ""
    ## redis data Persistent Volume Storage Class
    ## If defined, storageClassName: <storageClass>
    ## If set to "-", storageClassName: "", which disables dynamic provisioning
    ## If undefined (the default) or set to null, no storageClassName spec is
    ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    ##   GKE, AWS & OpenStack)
    ##
    # storageClass: "-"
    accessModes:
    - ReadWriteOnce
    size: 8Gi

  ## Update strategy, can be set to RollingUpdate or onDelete by default.
  ## https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
  statefulset:
    updateStrategy: RollingUpdate
    ## Partition update strategy
    ## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
    # rollingUpdatePartition:

  ## Redis Master pod priorityClassName
  # priorityClassName: {}

##
## Redis Slave properties
## Note: service.type is a mandatory parameter
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis Master
##
slave:
  ## Slave Service properties
  service:
    ## Redis Slave Service type
    type: ClusterIP
    ## Redis port
    port: 6379
    ## Specify the nodePort value for the LoadBalancer and NodePort service types.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
    ##
    # nodePort:

    ## Provide any additional annotations which may be required. This can be used to
    ## set the LoadBalancer service type to internal only.
    ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
    ##
    annotations: {}
    labels: {}
    loadBalancerIP:
    # loadBalancerSourceRanges: ["<IP_ADDRESS>/8"]

  ## Redis slave port
  port: 6379
  ## Can be used to specify command line arguments, for example:
  ##
  command: "/run.sh"
  ## Additional Redis configuration for the slave nodes
  ## ref: https://redis.io/topics/config
  ##
  configmap:
  ## Redis extra flags
  extraFlags: []
  ## List of Redis commands to disable
  # disableCommands:
  # - FLUSHDB
  # - FLUSHALL

  ## Redis Slave pod/node affinity/anti-affinity
  ##
  affinity: {}

  ## Configure extra options for Redis Slave liveness and readiness probes
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
  ##
  livenessProbe:
    enabled: true
    initialDelaySeconds: 30
    periodSeconds: 10
    timeoutSeconds: 5
    successThreshold: 1
    failureThreshold: 5
  readinessProbe:
    enabled: true
    initialDelaySeconds: 5
    periodSeconds: 10
    timeoutSeconds: 10
    successThreshold: 1
    failureThreshold: 5

  ## Redis slave Resource
  # resources:
  #   requests:
  #     memory: 256Mi
  #     cpu: 100m

  ## Redis slave selectors and tolerations for pod assignment
  # nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
  # tolerations: []

  ## Use an alternate scheduler, e.g. "stork".
  ## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
  ##
  # schedulerName:

  ## Redis slave pod Annotation and Labels
  podLabels: {}
  podAnnotations: {}

  ## Redis slave pod priorityClassName
  # priorityClassName: {}

  ## Enable persistence using Persistent Volume Claims
  ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
  ##
  persistence:
    enabled: true
    ## The path the volume will be mounted at, useful when using different
    ## Redis images.
    path: /data
    ## The subdirectory of the volume to mount to, useful in dev environments
    ## and one PV for multiple services.
    subPath: ""
    ## redis data Persistent Volume Storage Class
    ## If defined, storageClassName: <storageClass>
    ## If set to "-", storageClassName: "", which disables dynamic provisioning
    ## If undefined (the default) or set to null, no storageClassName spec is
    ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    ##   GKE, AWS & OpenStack)
    ##
    # storageClass: "-"
    accessModes:
    - ReadWriteOnce
    size: 8Gi

  ## Update strategy, can be set to RollingUpdate or onDelete by default.
  ## https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
  statefulset:
    updateStrategy: RollingUpdate
    ## Partition update strategy
    ## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
    # rollingUpdatePartition:

## Prometheus Exporter / Metrics
##
metrics:
  enabled: false

##
## Init containers parameters:
## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup
##
volumePermissions:
  enabled: false

## Redis config file
## ref: https://redis.io/topics/config
##
configmap: |-
  # Enable AOF https://redis.io/topics/persistence#append-only-file
  appendonly yes
  # Disable RDB persistence, AOF persistence already enabled.
  save ""

## Sysctl InitContainer
## used to perform sysctl operation to modify Kernel settings (needed sometimes to avoid warnings)
sysctlImage:
  enabled: false

## PodSecurityPolicy configuration
## ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/
##
podSecurityPolicy:
  ## Specifies whether a PodSecurityPolicy should be created
  ##
  create: false

I've just switched to a fairly similar setup with redis-ha and the failover / recovery is working as expected

Hi,
@miguelaeh is working on a major refactor of the chart, feel free to take a look: https://github.com/helm/charts/pull/21258
@miguelaeh make sure that this issue does not occur in the new chart

@javsalgar thanks for pointing to this, I indeed saw that refactor, however the move to a cluster topology instead of sentinel isn't necessarily desirable.
Switching to a cluster requires more resources (more redis master+slaves), it shards the keys across the different masters, it doesn't support multiple databases, and there are limitations with multi-key operations. (https://redis.io/topics/cluster-spec)
I haven't had a deep look at the MR at all, but if it replaces the master+slave topology with the cluster topology altogether I can imagine that it won't be suitable for quite a few people anymore (me included)

Thanks for the input! I will forward it for evaluation.

@javsalgar Probably would have been good to try and talk to @ssalaues and I before doing this. We're intentionally not using cluster topology and wouldn't have accepted this PR, it may be better in it's own chart as everyone has their preference.
There's a number of other problems with the cluster topology and many seem to prefer Sentinel for clustered Redis instances.
@simon-jouet To the original issue, I'll take a look as it's not something I've come across.
Do you know what the original cause for failure was in the master and how long it was down? This might help to pin point the root cause.

@DandyDeveloper thanks, yes I moved to redis-ha after struggling a bit with this issue and so far I haven't had any problems. I reported this issue for stable/redis as i'm sure the split brain isn't intended


[Coverity] Check return value

Check return value of the socke lib function.
Signed-off-by: gichan<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #25. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Do not work with MPT!

Hope to be compatible with MPT, very grateful, excellent plugin!

MPT not working +

Please, mod not working with MPT or Fika mod.

I can't test MPT/Fika, but I applied the same fix from the graphics mod which worked for some people so might be working

Yeah, Just downloaded now and still seems to not work with Fika

Hi, Amand, Thanks for your work on these mods, Great additions to the game. Can confirm what OmGxM Said earlier, It appears the fix that was applied doesnt work with MPT/Fika. tested with the pre-release 2.0.0 Is there any output from the server/game that i can enable to help you identify and test this compatibility? Happy to help.

sorry I was meant to release the update but had other issues, I'll be putting the build for it now

Legend, Thank you.

Just checked out the latest build you've popped up. Confirmed working for me with FIKA.  Thank you.

Ooooooh nice, thanks Amands, I’ll be sure to update the mod tomorrow appreciate the quickness your a god.

thanks!


Readme Updates

Description
This is now independent from the Swift SDK's readme changes. Whenever we update the headers in that readme, I have TODO's in this one of where to make updates.
TODO - need to verify simulator installs before we OK those green checkmarks for iOS versions.
Check List

[x] Are you changing anything with the public API? NO
[x] Are your changes backwards compatible with previous SDK Versions? YES

Changelog / Code Overview

Changes to the README
Minor tweak to the documentation automation

Test Plan

Review and proofread the README

Related Issues/Tickets

CHNL-4780
CHNL-4773

Latest content will be accurate when #71 is merged.


Feature/d1.7 update h3 crawls dynamically

This feature provides access to the H3 scripting console, in much the same way that the Heritrix GUI does. The Target Instance results view will show an additional 'action' icon to access the console, which is opened in a pop-up window. There are two ways to use the scripting console

Add existing scripts to a pre-defined directory on the OS, which are then loaded and accessible in this window to run. The directory location is determined in wct-core.properties, and is read each time the scripting console window is opened. Only files with the following extensions are read - .groovy (Groovy), .bsh (BeanShell) and .js (ECMAScript). These scripts are editable in a text box before you execute them.

The text box that scripts are loaded into can also be used for writing your own or pasting in scripts. You just need to select the engine to use (Groovy, BeanShell or ECMAScript) and then execute it.

The results box below is where the response from H3 is shown.
@hannakoppelaar here is a list of existing H3 scripts for testing https://webarchive.jira.com/wiki/spaces/Heritrix/pages/7570099/Heritrix3+Useful+Scripts


Add support for "polymorphic attribute"

This feature is needed for the workflow tasks.
@achursin-zenefits, @glynn-zenefits mentioned that you did something with ember-models, but I forgot what it was or how it was related to what I am trying to do here.
cc @zenhenryl, @edzen

Previous tests pass:

Is not it(almost) same as line 16444 in yourpeople2/statis/js/models.js?
Ember.Model.reopen({
	getBelongsTo: function (key, type, meta, store) {
		if (meta.options.is_polymorphic) {
			var model_name = Ember.get(this, '_data.' + key)['type'];
			var polymorphic_model = this.container.lookup('model:' + model_name);
			if (polymorphic_model) {
				type = polymorphic_model.constructor
			} else {
				console.error('Can not find polymorphic mapping for ', model_name);
			}
		}
		return this._super(key, type, meta, store);
	}
});

@gliatzenefits see @achursin-zenefits 's comment

@achursin-zenefits, one is for models that can be polymorphic, and one is for attr, but let me double check w/ @edzen

Whats the difference?

@achursin-zenefits, I'm not too familiar with what you pasted, but it seems like it's for belongsTo relationship. The polymorphic attr data takes an arbitrary JSON and it is not necessarily a model in our database. We use the type field to determine which transformer to use. For example, the following is tasks-carrier-level-business-step.js:

This feature allows us to supply to the frontend the information of how to treat the data attribute. If we did not do this, then we have to hard-code the data attribute like in wf-crediential-verification.js:

With this PR, we can supply 'adminCredentialVerificationData' from the backend into the type attribute, and then we know that we can treat data as an object with that type (so we know which transformer to use).

So, differences I see so far:
a) You are using attr function instead of belongsTo. I am actually not sure about this 'should be model in db' stuff... Is there difference between belongsTo with embedded=True and attr? Is not attr for rather scalar types?
b) You store type in (attr name +'_type') field inside top-level struct, in opposition to my approach when type is stored inside embedded obj... I think this are equivalent stuff

The code works with existing front-end code that Ed wrote for workflow tasks. I am actually not sure about belongsTo and embedded=True. You have to ask Ed if we can use belongsTo here. There may be some caveats. Ed is busy until Monday, so I will touch base with him then. In the meantime, I will also ask Glynn for his opinion.

@glynn-zenefits  also said to move it to its own field polymorphicAttr so that we can reduce the scope of what this PR affects. Doing that now.


Update on PyPI

Hi there, just wondering why Esri updates the arcgis package on PyPI, but not lerc. The PyPI lerc package is severely outdated. I understand that conda is the preferred install method, but if one pacakge is kept up to date on PyPI, then why not another?
Thanks

@egorbn Thanks for bringing this up. These 2 packages are maintained by different teams, that's why. We just updated it.

Thank you, @tmaurer3!


Add Pinecone to trace operations involving vector databases.

Description
Extended the @tracer.trace_tool decorator to trace operations involving Pinecone Vector Database
Type of Change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
There is test file with this PR in tests/vector/test_pinecone_db.py run python -m unittest pinecone_unit_test.py to verify the tests.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@ujjman Also add the documentation for the feature added to the docs folder

I have made the changes to the docs folder @kiranscaria


capa-iam-operator fails to remove most of it's finalizers

Bug description
We have already fixed the same bug in capa-iam-operator for AWSMachineTemplates and AWSCluster, but I continue to observe this happening. For cluster-eks it happens on the AWSManagedControlPlane and for cluster-aws it happens for the AWSMachinePool.
I haven't investigated but from my previous efforts I can say that the problem is most likely two separate things acting together:

reconciliation takes too long and by the time it finishes the object has changed. Notably some other operator has removed a finalizer and our old copy would technically be adding one or more of those back, which is not allowed on deletion.
Reconciliation fails on subsequent delete requests. If deletion has succeed the operator will fail because resources are now gone, or in other words it's not idempotent.

Designed behavior
Since this can also affect e2e clusters, a quick solution would be to use the retry logic we already have for these resources too. However, the best solution here is to redesign/rewrite this operator so the above observations aren't a problem in the first place.
Reproduction Steps
You may need to try several times as it is a timing issue, but it happens often enough and you won't need to retry too much

Create a EKS or CAPA cluster
Wait for the cluster to become ready
Delete the cluster
Notice finalizers for capa-iam-operator are still present on either AWSMachinePools or AWSManagedControlPlane and block cluster deletion.

Technical information
Example Logs:
E0403 15:46:23.381338       1 awsmanagedcontrolplane_controller.go:118] controllers/AWSManagedControlPlane "msg"="failed to remove finalizer on AWSManagedControlPlane" "error"="AWSManagedControlPlane.controlplane.cluster.x-k8s.io \"wario61\" is invalid: metadata.finalizers: Forbidden: no new finalizers can be added if the object is being deleted, found new finalizers []string{\"capa-operator.finalizers.giantswarm.io/dns-controller\"}" "AWSManagedControlPlane"="wario61" "namespace"="org-giantswarm"
E0403 15:46:23.381387       1 controller.go:326]  "msg"="Reconciler error" "error"="AWSManagedControlPlane.controlplane.cluster.x-k8s.io \"wario61\" is invalid: metadata.finalizers: Forbidden: no new finalizers can be added if the object is being deleted, found new finalizers []string{\"capa-operator.finalizers.giantswarm.io/dns-controller\"}" "AWSManagedControlPlane"={"name":"wario61","namespace":"org-giantswarm"} "controller"="awsmanagedcontrolplane" "controllerGroup"="controlplane.cluster.x-k8s.io" "controllerKind"="AWSManagedControlPlane" "name"="wario61" "namespace"="org-giantswarm" "reconcileID"="76f828ff-1e96-4d15-9a8f-40ae214b7dbf"

Fixed in https://github.com/giantswarm/capa-iam-operator/releases/tag/v0.21.1


Fixed 404 due to incorrect case

/assets/learn/Curves/
Should be
/assets/learn/curves/
per your directory structure

hi @theTaikun
thanks so much for helping us detect the bug and make this pull request!
the way our website is built, the files in the src/ folder are compiled, and then generate
the files inside of dist/, so in order to fix bugs we need to fix the file in src/
in this case, it was src/templates/pages/learn/curves.hbs
I fixed it on #278 based on your suggestion, and this file will know in turn fix the one you proposed
thanks so much and i hope this doesn't discourage you of keeping on contributing
if you want to know more about the way the website is built, it's on our README file, best!

Alright, I'm just starting to learn p5.js, so I'll make sure to commit properly if I find anything else


Scorecards job failing for most merged PRs

Describe the bug
Example failure at the bottom:
https://github.com/microsoft/ebpf-for-windows/actions/runs/6383992434/job/17325721329
This looks like some private endpoint used for signing the results is no longer available:
Generating ephemeral keys...
Retrieving signed certificate...
2023/10/02 18:26:05 error signing scorecard results: getting key from Fulcio: retrieving cert: client: Post "https://fulcio.sigstore.dev/api/v1/signingCert": dial tcp <IP_ADDRESS>:443: connect: connection refused

Steps taken to reproduce bug
submit a PR
Expected behavior
our merged PRs have the green checkmar signifying all jobs passed, including this optional one.
Otherwise, we might as well remove this.
Actual outcome
scorecards job has been failing for a while

@rectified95 please consult with @nibanks  for this issue.


Screen Border Fade-Out

Changes
This PR adds a new parameter ssr_screen_border_fadeout.
It can be used to control a fade-out effect of reflections close to the screen borders
and supports a range from 0 (fade-out disabled) to 1 (max fade-out). The default value is 0.
If you move the camera so that a reflected object is no longer visible,
its reflection on the water also disappears, even though it should still be visible.
This is a general weakness of SSR, as only objects that are visible can be reflected.
Enabling screen border fade-out mitigates this to some degree and helps to make it less distracting.
This implementation is based on https://github.com/marcelb/GodotSSRWater/pull/3 by @Xtarsia and another variant, which was proposed in https://github.com/marcelb/GodotSSRWater/issues/2 by @farfalk.
I decided to change a couple of things to make it easier to use and also the code easier to understand:

Setting the parameter to 0 disables the effect
The logic is moved to its own function.
Calculate the transparency simply based on distance from the screen center.

void mainImage( out vec4 fragColor, in vec2 fragCoord )
{
    // Normalized pixel coordinates (from 0 to 1)
    vec2 uv = fragCoord/iResolution.xy;

    uv *= 1.0 - uv;

    float edgeFade = 2.0; // Range 0.0 (Fade disabled) to 8.0~ (Fully faded out..)
    float col = smoothstep(0.0, edgeFade, uv.x * uv.y * 64.0);

    fragColor = vec4(col, 0.0, 0.0, 1.0);
}

smoothstep version, a tad more square and the fade is disabled with a value of 0.0

0.5

2.0

0.0

Looks amazing. @Xtarsia

Yes, that looks much better! I see the advantage of this variant: The fading behaves more similar at the corners as well as at the edges of the screen. I updated this PR to implement this with some adjustments: The parameter now ranges exactly from 0 to 1.
Here is the shadertoy code to try yourself. I mapped the parameter to the x-position of the mouse.
You can play with it by dragging the mouse over the canvas.
void mainImage( out vec4 fragColor, in vec2 fragCoord ) {

    vec2 uv = fragCoord/iResolution.xy;

    float edgeFade = iMouse.x / iResolution.x;

    vec2 shiftedUv = 4.0 * uv * (1.0 - uv);
    float factor = shiftedUv.x*shiftedUv.y;
    float offset = mix(0.0, 0.5, (clamp(edgeFade, 0.75, 1.0) - 0.75) / 0.25);

    float alpha = smoothstep(0.0, 2.0*edgeFade, factor) - offset;

    fragColor = vec4(alpha, 0.0, 0.0, 1.0);
}

@marcelb I just updated the branch with your feedback and also added a check to skip the calculation in the case when ssr_screen_border_fadeout == 0.0

Thank you everyone @ulfbiallas @ulfbiallas @farfalk, I merged this!


There seems problem with api.

@ErKiran What was the issue?. There is no description in your closed issue. can you please let me what was the issue.


add type definition

support TypeScript

Hey @taoqf, what's the point of having test.ts?

Also lets use ES3?
https://github.com/alferov/array-to-tree/commit/8fc8e98cd1a9ff1bae3f172efdfb237aa6efec24
Apparently, UglifyJs doesn't support ES6 (https://github.com/gruntjs/grunt-contrib-uglify/issues/480), therefore using const and let might break production build

All done.

Thank you!


Propagate the current client disposition to the requeue_message event handler

Having last error as a meta field on message object would allow flexible requeueing of messages to different egress pools based on SMTP response text.
The value can be ephemeral and does not need to be spooled to avoid IO overhead.

We discussed this in discord with the following summary:

Want to avoid storing the disposition in the metadata because it will add a constant factor to the I/O cost of a transient failure. In this case it will take it to 2x the IO because it will be logging the failure to the logs (as normal) as well as spooling out an updated copy of the metadata.
Persisting the info in the metadata is not necessary
Passing the info to the requeue_event should be sufficient


docs/design: add README.md

Add README.md which outlines the proposal process, with its content copy/pasted from the approved process.

I'm going to merge regardless of whether the project board is public yet, it'll be made public as soon possible.


feat: Integrate OneAuth library

Description
This PR updates the Electron-side authentication code to use the new OneAuth library that allows the app to authenticate against Microsoft resources in a compliant way.
This is a requirement for the Electron application due to a recent tenant-level security policy change.
Fixes #4131, #4385
Highlights:

Auth flow is initiated at the server-level /api/auth/getAccesssToken route

added CSRF protection to this route that should prevent external client code from being able to call this route and get a token via Composer

This route then delegates the auth flow to the ElectronAuthProvider or the WebAuthProvider depending on the platform

this supports both Electron & Web (to be implemented) auth flows

The ElectronAuthProvider uses the oneAuthService.ts to call the OneAuth library's APIs and do OS-level authentication

New build steps for the OneAuth library

Coverage decreased (-0.4%) to 55.363% when pulling 2d23c8776f89d6c14656b4bb1258bc97e3e2d965 on toanzian/feat/oneauth into ea889fb017ea335cff31a05aa2e03bafe3688cd5 on main.


Implement Class and SingletonClass methods on values.

This is pretty straightforward, but here's a full-featured example to play with:
https://gist.github.com/cbf1578a03b09713b2813071ecea8291
Let me know! Thanks!

from "debian"
3.times do
  run "echo hi >>root-test"
end

run "mkdir /test"
run "chown nobody /test"

user "nobody" do
  workdir "/test" do
    3.times do
      run "echo hi >>test"
    end
  end
end

Just in case you're interested in the use case. :)

Looks great!


Tabular: Improved LGBM training speed by 100%-200% on most datasets

Issue #, if available:
Description of changes:
Tabular: Improved LGBM training speed by 100%-200% on most datasets
This is achieved by using the built-in evaluation metrics of LGBM when possible, as they are much faster than the sklearn versions AutoGluon natively uses, while resulting in identical final models. I have added support for all of the most common metrics in this PR, and have done a benchmark which confirmed the speedup, which stays consistent on both large and small datasets.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-511-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-511/1/index.html


Stable channel is supported and default

Depends on #523 . the second commit is the content of this PR.
\cc @aaronlevy @cgag @pbx0

Can you remind me why we didn't have stable supported before?
Code LGTM.

@cgag we need rkt >= 1.0 for kubelet-wrapper to work.

rkt 1.0 has been in stable for a while... but the kubelet-wrapper just made it to stable.

Just want to note that we're going to need to use alpha again for supporting rkt+kubernetes (need newer versions of rkt).


Localization

I've been developing a react-native app with great success but now I need to make it available in different languages based on phone settings. I've come across this library https://github.com/stefalda/ReactNativeLocalization which looks promising but my question is, do you have any official tool to expose the IOS NSLocalizedString or any plan to expose it later ?

I too have a need to localize my app. ReactNativeLocalization looks good but I'd like to have that feature supported in core.

@vjeux @brentvatne @sahrens

+1

+1

We use a localization library and pipeline that's very custom to Facebook and that is not easy to extract out. So don't expect much from us in the near term.
I would love if there was a pure-js library that does translations that we could just npm install instead of having it part of react native. Translations is a problem that everyone faces and not tied to react-native.

Just an idea but perhaps a Babel plugin could address this. Since the packager loads .babelrc automatically, you could have the plugin do the i18n transform during packaging.

We've been looking at the possibility of using Intl.js of Format.js.
There's an open issue for the React integration that seems to suggest that the changes required would not be scary. https://github.com/yahoo/react-intl/issues/119

There is also the issue of RTL layouts. I would love for react-native support a flexbox/CSS extension for this, in a similar way to how Android or iOS auto layout implement this, with properties such as paddingStart (instead of paddingLeft) .

@miracle2k: I actually want to get it auto-swapped by default instead of having the developer write paddingStart as very few people do. Would love a pull request!

@vjeux what do you think about generalized StyleSheet plugins? For example you could inject StyleSheet.addTransformer(new RtlStyleSheetPlugin) which flips directional style props. (Basically middleware but I think that's just not a good word.)
Also it is sometimes useful to distinguish left/right from start/end. For example if you build a layout for left-handed people you don't always want to flip that just because they speak Hebrew.

I like the middleware idea, but unclear if it should be inside of StyleSheet.create. If you use inline styles outside of StyleSheet.create (we do it all the time for dynamic values) then you won't get it and your app will feel broken.
This also come up a lot with browser pre-fixing
cc @sebmarkbage who is thinking a lot about this specific issue.

We just implemented a differ and compute functions for specific props. Helps with color pre-processing and transforms

Great point about inline styles. Two things I'd like to see with an i18n system are to be able to customize it (middleware) and for it to be available on npm for awhile so it can evolve and eventually converge on a few solutions.

I have a broader question related more with the React philosophy. Should the i18n strings live with each component or all the localised strings in a separate file?

BTW, how about navigator.language and navigator.languages? Looks like we can easily follow the specification in this case.

@grabbou if we can get Intl.js working on-top of react native that would be great indeed

I can tell you that this:
// Polyfill the things
import './node_modules/intl/index.js';
import './node_modules/intl/locale-data/jsonp/en.js';

works just fine

+1

@miracle2k @vjeux +1 for automatic approach, similar to css direction that you can apply to html element to mirror everything.
I read apple is supporting right to left languages but how does it fit into the react-native View system ?
Could you throw some light on this ?

For right alignment, on container level, I define alignItems: 'flex-end', works pretty good with hebrew.

For RTL, it seems that css-layout already has some support for a direction attribute (https://github.com/facebook/react-native/blob/45e0423b4ea1f29d6f86803057b94c710f8b9835/React/Layout/Layout.h#L38), and I was taken by surprise how well supported the CSS Logical Properties spec is (http://caniuse.com/#search=logical).
Supporting these two things in react-native would get us a long way, and it seems a sensible and standards-supported approach.

I was thinking about this for react-native-web too, because it blocks us from the possibility of using it in production at Twitter.
Our existing CSS tooling auto-flips padding-left, background positions, etc. Probably more than is practically necessary. But we also have a special syntax to avoid flipping specific declarations (for example, the @username is styled to always be presented LTR). And whatever your writing direction we always present RTL text right-to-left and LTR text left-to-right. So we need to be able to say "flip all horizontal padding/margin/border/textAlign except for these cases".
Using properties like paddingStart supports that use case, because you can expect paddingLeft to always set padding on the left and there's no babel transform required. It would be fairly easy to build  into web's StyleSheet. It does mean that its easier for people to build layouts that don't properly adjust to RTL, but in our experience, without the ability to prevent certain props/values from being auto-flipped you can't produce a good RTL experience.
What are some ways that would support the use case described?

At fb, this is also something that we need to solve in order to be able to use inline style on our main website. The way we enable disabling the autoflip is via a comment /* @noflip */ above the rule.
I've been thinking a lot about this for react native and I'm convinced that paddingStart instead of paddingLeft is a mistake. You're going to face a never ending battle to get developers to switch their existing behavior. And the worse is that it'll work doing left, so you'll have a ton of mixed code in your codebase.
The best way imo is to convert paddingLeft to right in rtl and provide another property to force left like paddingLeftRTL (we can bikeshed on the exact naming).

We use something very similar at Twitter. I agree with the drawback of relying on paddingStart, etc., style props. That would not be viable for us either, and all the OSS RN components would need changing.
Inventing new style props excluded from flipping would work. I can try prototyping it for Web in the next few weeks

If not having a full blown localization support, can we at least have API to extract the device locale information?

I am thinking we could add a JS module similar to Dimensions that exposes these properties, also include language & languages as per spec to support web i18n modules. I got that working on iOS, can submit a PR if that works.

For Web, we can only reliably infer the language on the server.

Since this issue is "for discussion" and there hasn't been any discussion in the past few months, I'm closing it. It would be great if there was some library that made this better, but nobody seems to have any plans to work on it at this time. If someone does have such plans in the future, I suggest opening a new issue as an "RFC" with some specifics about how they'd build this.

Just in case anybody stumbles upon this issue looking for what @axelg12 was originally asking about, a way to retrieve the language locale strings (en, fr, etc) from the device.
If you just want the strings without extra libraries
import {NativeModules} from 'react-native'
let locale_ios = NativeModules.SettingsManager.settings.AppleLocale;
let locale_android = NativeModules.I18nManager.localeIdentifier;

This is the approach that I took. Requires a bit of extra work. I created a custom function that essentially extracts the first two letters if they exists. From this StackOverflow answer.
By using a library
https://github.com/rebeccahughes/react-native-device-info
If you are using fnando/i18n
https://github.com/AlexanderZaytsev/react-native-i18n

How to add attributes (bold, color, etc.) to words in a i18n string?
// en.js
{
  "hello": "Greeting, {{name}}. I'm JARVIS."
}

// React Native
<Text>I18n.t("hello", { name: "Xavier" })</Text>

What I got: Greeting, Xavier. I'm JARVIS.
Expected: Greeting, Xavier. I'm JARVIS.

Please Provide Telugu Language ,This is Very Popular in India Country, and Please Make it Telugu, Hindi Tamil Etc.


Integration with Phony

Hi guys, thanks for the work on Peridot, I really like what you've done.
I've written a mocking framework called Phony that works pretty well with Peridot. In addition to traditional object mocking, it supports callback spying and stubbing, which fits nicely (at least thematically) with the describe-it style. It has support for HHVM and PHP 7, which I noticed you are also targeting.
So I'm creating this issue basically to ask: is there anything more I can do to improve integration with Peridot?
One thing I do have planned, is to write a Leo plugin as well, so that you can use expect style assertions. But for now, it works fine to use Phony directly. Check out the Peridot example test suite if you're interested.
Thanks again for the awesome work!

Wow. This looks really cool. Functions definitely make this appear simple. I can't really think of a formal integration path with Peridot other than plugins. This would only save having to include the Phony namespace.
Something like adding mock and spy methods to a Peridot scope:
beforeEach(function() {
  $this->handle = $this->mock(); // $this->mock provided by a plugin
  $this->spyA = $this->spy(); // $this->spy provided by a plugin
});

Maybe @austinsmorris has some input?
I will definitely give this a try next time I start a PHP project. Good work.

@brianium Thanks! You know, strangely, I didn't even think of an actual Peridot plugin, but that would make it slightly nicer to use, even if it's only a small thing. I'll check out the plugin system when I get a chance.


integration test support for k8s CSR

Add a component into our integration test framework which will contain a controller to reconsile k8s CSR and sign certs with full cert-chain

all related PRs have been merged, so I think it can be closed.


position:sticky is enabled in Chrome 56 and Opera 43

https://www.chromestatus.com/feature/6190250464378880
https://bugs.chromium.org/p/chromium/issues/detail?id=231752#c72
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/X_vBQp60kp8

@Fyrd How do I set y to Android Browser and Chrome for Android starting with version 56? Should I add version 56 to the JSON?

Thanks!
Those versions will be updated once 56 becomes stable.


Readline.bind_key doesn't work

By example:
require "readline"

Readline.bind_key('a') do
  puts "Hi!"
end

sleep

Shows:
Error in keysignal.cr:3: expected block to return Int32, not Nil

Readline.bind_key('a') do

So, I tried this:
require "readline"

Readline.bind_key('a') do
  puts "Hi!"
  0
end

sleep

and it compiles, but it doesn't detect a keyword
Ref: https://github.com/crystal-lang/crystal/pull/1290#issuecomment-135134592
Version:
[main@pc ~]$ crystal -v
Crystal 0.27.0 (2018-11-02)

LLVM: 6.0.1
Default target: x86_64-pc-linux-gnu

Readline is going to go. I just need to get around to pulling it out.

Not relevant any more, see https://github.com/crystal-lang/crystal/pull/8364


Custom bindings aren't being honored

I have two modules, each provides an instance of the same class (a specific Gson configuration). So, each module has a method like so:
@Provides
@ModuleA (this is @ModuleB in the other module)
public Gson provideGson() { ... }

Then I have constructors for classes that use those Gson items, that look like:
@Inject
public FooBar(@ModuleA gson) { ... }

This does NOT work consistently. Sometimes it injects the @ModuleB version of Gson into things annotationed with @ModuleA.
I'm using Dropwizard with the dropwizard-guice library, which uses Guice 4.1.

Please provide a testcase using Guice only (not dropwizard) that replicates the problem.

Sigh, I knew that would be the answer. No one will look at this. Dropwizard points at Guice, Guice won't take a dropwizard example.
It's non-deterministic, sometimes it works, sometimes it doesn't.

I'm happy to look at it, I just need a testcase to look at that I can grok.  Including Dropwizard in the mix makes it so I can't actually understand what's happening, since I have no idea what Dropwizard does or how it does it.
It's very likely the problem is with the way Dropwizard is using Guice.

What do the ModuleA and ModuleB annotation declarations look like?
Are they meta-annotated with @BindingAnnotation or @Qualifier?

@BindingAnnotation
@Target({ FIELD, PARAMETER, METHOD }) @Retention(RUNTIME)
public @interface ModuleA {
}

I've gone ahead and filed the issue with the dropwizard-guice library. I'd communicated with someone I thought was part of that library before a few months ago, but maybe my memory is crap so we'll see if they've got an idea. I'll have to set aside a day to try and create a small test case for them.

Talking with the dropwizard-guice developer, I'll reopen this if it looks like it's Guice rather than it's integration with Guice.


Add sample_batched and log_prob_batched to posteriors

Description
The current posterior estimators only support a single x_o (or iid x_os), for sampling and log_prob.
This can be inefficient when we want to sample from a batch of x_o (or iid x_os) as it requires a for-loop.
Fix
The new DensityEstimators already implement the capability to evaluate and sample for batches.
To preserve the current behaviour of the posterior classes, we would instead add:

sample_batched samples for a batch of x_o
log_prob_batched log_probs for a batch of x_o

#1153 implemets this


winutils.exe

[Enter feedback here]
I am trying to make databricks connect on my Windows (11) machine, and I get the winutils.exe error.
I understand I have to have it on my machine, but the suggested link to solve the problem is fraightening.
From other sources, I understand it is just enough to copy the compiled file locally and set an environment varible.
Would appreciate some more tight guidance.
thanks
paolo
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3642022f-a58f-6290-ecf1-3c551a9bfc96
Version Independent ID: cf117e4e-c261-858c-517e-04d67e44c35e
Content: Databricks Connect - Azure Databricks
Content Source: databricks/dev-tools/databricks-connect.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@PAOLT Did you get a chance to check the instructions to configure the Hadoop path on Windows mentioned in this document?

@PAOLT  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Updating docker install instructions for new image.

@DavidLu1997 please review and share any feedback?

Looks good to me, my PR is redundant now.

Closing because it duplicates my PR

+1, works


Add performance tests with its make target

Add performance tests with its make target
Make command example
❯ make test-performance API_TOKEN=$token
Building docker image 'performance:latest'...
sha256:4d52cfda7fcb62d1115afab6a9c8a20b529d9342e2265bc9ea04e1d168eb4ecf
Done!

Running benchmark on http://cluster-registry-api:8080/readyz for 10s ...
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Benchmark ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
 Total Requests: 13284 ┃ Requests/s: 1328 ┃ Average: 0.038 ┃ 99.9th: 0.294
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Running benchmark on http://cluster-registry-api:8080/livez for 10s ...
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Benchmark ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
 Total Requests: 324371 ┃ Requests/s: 32433 ┃ Average: 0.002 ┃ 99.9th: 0.011
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Running benchmark on http://cluster-registry-api:8080/api/v1/clusters for 10s ...
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Benchmark ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
 Total Requests: 18656 ┃ Requests/s: 1865 ┃ Average: 0.027 ┃ 99.9th: 0.830
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Geting cluster name... Done! Got cluster01-prod-useast1.
Running benchmark on http://cluster-registry-api:8080/api/v1/clusters/cluster01-prod-useast1 for 10s ...
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Benchmark ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
 Total Requests: 31720 ┃ Requests/s: 3172 ┃ Average: 0.016 ┃ 99.9th: 0.047
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

More info in the docs update.
Motivation and Context
We needed some performance tests so we can see how the project performs over time.
After this, a mechanism that runs these tests automatically should be added.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

run tests


bug: can't disable margin

Setting all margins as 0 does absolutely nothing as it continues to use the defaut 25 margin, setting margins to something like 0.001 does work in the mean time

Thanks for letting us know. We will make sure to fix it. Undefined or null will be no margins. 0 will be zero margins.


Several candidates for source class in Move Method refactoring

Example:
Moved method
Two methods with equal names and bodies that are originally located in two different objects:
First one,
Second one
Which of the classes/objects should be marked as a source?

Tested the original tool RefactoringMiner, its behavior is the same in the case like this.


Fix: RollingFileAppender does not work on Android and iOS

However netstandard contains cross-process Mutex, Android and iOS platform does not support it.
Therefore, current implementation of RollingFileAppender cannot be used on these platforms.
To fix it, Mutex object is replaced to a file based cross-process implementation.

This PR is quite stale & conflicts with the target branch; please re-open if it's still an issue you'd like to solve (: Thanks for your contribution.


Update drives.json

Added OR end_position.usable_battery_level IS NULL for situations where intermittent LTE issues cause the end_position.usable_batter_level is NULL.. These were low efficiency drives going up extreme elevations in low LTE coverage areas.

@Dulanic Are you on grafana:edge? I redid drives.json for Grafana 7. I could need some testing for Fahrenheit und Miles...
Drives7-1599493320315.zip

@DrMichael do you want to open a WIP pull request for your changes? We do not have to merge it immediately.

@DrMichael Sorry i haven't looked at any edge stuff yet. Have been pretty slammed lately.


Add pylama configuration and refactor code

Add pylama.ini file for local and GitHub Actions purposes
To run pylama with configuration file execute pylama -o pylama.ini
Refactor code accordingly to issues reported by pylama

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@aacae39). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #66   +/-   ##
=========================================
  Coverage          ?   51.28%
=========================================
  Files             ?       13
  Lines             ?      585
  Branches          ?        0
=========================================
  Hits              ?      300
  Misses            ?      285
  Partials          ?        0

Continue to review full report at Codecov.

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


Example on how to modify Sln files

Could you add a simple example of how to actually modify an .sln file? I am looking for something like, e.g. load an .sln file, search through the names of projects included in it, and remove one of these project inclusions, then save the .sln file again. How is this done?
Unfortunately, I failed to see any hint to that in the readme file. There is some talk about custom "handlers" that can apparently be used to write something, but all I am getting from the Sln object is a Results object with (read-only) enumerables.

There is some talk about custom "handlers"

The custom handlers may be applied (this is not required for your case) for any non-standard logic, or for any new not yet supported data from .sln format, and so on.
That is, you don't need to implement this yourself for any common operations with known data because it's already implemented for ISlnResult via Core.SlnHandlers.
Map is the main idea of any modifications.
And the Core.ObjHandlers just provides "committing" new data vice versa from any related collection.

I am looking for something like, e.g. load an .sln file, search through the names of projects included in it, and remove one of these project inclusions, then save the .sln file again. How is this done?

For example:
// new collection from available projects but without project 'UnLib'
var projects = sln.Result.ProjectItems.Where(p => p.name != "UnLib");

// prepare write-handlers
var whandlers = new Dictionary<Type, HandlerValue>() {
    [typeof(LProject)] = new HandlerValue(new WProject(projects, sln.Result.ProjectDependencies)),
};

// save result
using(var w = new<EMAIL_ADDRESS>whandlers)) {
    w.Write(sln.Result.Map);
}

// That's all. You should get .sln without `UnLib` project.

Thank you for your fast response. I still don't really know how to use the API:
using (var sln = new Sln(args[0], SlnItems.Header | SlnItems.Projects | SlnItems.SolutionItems)) {
                var folders = sln.Result.SolutionFolders.ToList();
                folders.Add(new SolutionFolder(...)); // What to insert here? ProjectItem has only one ctor; IEnumerable<RawText> def is a text list of guids I guess?

                var whandlers = new Dictionary<Type, HandlerValue>() {
                    [typeof(LProjectSolutionItems)] = new HandlerValue(new WProjectSolutionItems(folders)),
                };

                using (var w = new SlnWriter(args[0] + ".better", whandlers)) {
                    w.Write(sln.Result.Map);
                }
            }

Thank you :)

Hi,
When using the example above on an 'empty' solution, sln.Result.ProjectDependencies is null and thus the code will throw an exception when adding a new project. Is this the proper way to add new projects to a solution that doesn't contain any project (or project dependencies) yet?

sln.Result.ProjectDependencies is null and thus the code will throw an exception

You should notice much more null-values when loading an 'empty' solution :)
An sln.Result just represents various collections, so you can just initialize something from scratch if you need it. For example, for mentioned ProjectDependencies and WProject from my example above:

WProject requires any ISlnProjectDependencies instance.
The default public implemention exactly is LProjectDependencies, ie. nothing easer than just:

new WProject(projects, new LProjectDependencies())

etc.

Is this the proper way to add new projects to a solution that doesn't contain any project (or project dependencies) yet?

However, you need a little bit more if we're talking about adding new projects into absolutely 'empty' solution (when no initial records about projects at all), like:
MinimumVisualStudioVersion = 10.0.40219.1
Global
	GlobalSection(SolutionProperties) = preSolution
		HideSolutionNode = FALSE
	EndGlobalSection
EndGlobal

Today we need add information about planned projects into prepared map data. For example:

// some project collection from scratch ~
var projects = new[] { new ProjectItem("MyProject", ProjectType.Cs, "path") };

// place LProject handler inside map:
sln.Result.Map.Insert
(
    (int)sln.Result.Map.First(i => i.Raw == "Global").Line - 1,
    new Section(new LProject(), null)
);

// now you can use SlnWriter as before

2.2 does not provide any wrapper for some automation of this. But I think we need an additional layer anyway.
Moreover, in #9 I already voiced about preparing some "intermediate wrapper for creating new write-handlers from result"

Thanks, I got it to work.

Since this issue is mentioned too much, please note that there are new related features in 2.7+
SMap
Map wrapper in order to control ISections easily. For example,
smap.Add
(
    SMap.AddType.Before,
    typeof(LExtensibilityGlobals), //type of handler
    new Section(....)
);

smap.Add
(
    SMap.AddType.After,
    SMap.RawSectionType.Global,
    [new Section(null, "custom1"), new Section(null, "custom2")]
);

see tests for details
ISlnResult -> ISlnWhData
ISlnWhData is new minimal subset of the data for the default handlers. That is, in addition to standard handler definitions, I mean:
Dictionary<Type, HandlerValue> whandlers = new()
{
    [typeof(LVisualStudioVersion)] = new(new WVisualStudioVersion(SlnHeader.MakeDefault())),
    [typeof(LProject)] = new(new WProject(projects)),
    ...
};

using SlnWriter w = new(solutionFile, whandlers));

the modern SlnWriter now understands also ISlnWhData. And while ISlnWhData can be implemented manually, 2.7 also provides LhDataHelper helper in order to use it in a chain like style:
LhDataHelper hdata = new();
hdata.SetHeader(SlnHeader.MakeDefault())
        .SetProjects(projects)
        .SetProjectConfigs(prjConfs)
        .SetSolutionConfigs(slnConf);

using SlnWriter w = new(solutionFile, hdata);
await w.WriteAsync(sln.Result.Map);

And new DefaultHandlers can also help to generate the default w\handlers using this data
Dictionary<Type, HandlerValue> whandlers = DefaultHandlers.MakeFrom(data)

Modern SlnWriter
SlnWriter now also provides WriteAsString() & WriteAsStringAsync() to save the result as string instead of file.
using SlnWriter w = new(handlers);
string data = await w.WriteAsStringAsync(sln.Result.Map);

I hope that now modifications can actually be done in a few steps.


Fix clearCache link in index

The id for the clearCache method is clearCachebool, but the index was incorrectly only referencing clearCache.

Sure thing! Let me know if there's anything else. :)

Argh. Obviously the CI failure is unrelated to your change... I'm guessing it's a break from using the latest XCode version... (possibly combined with not using the latest version of react-native-macos)

Thanks for merging back in the most recent changes @TheAlmightyBob . 👍


Use axom::Array in quest::findTriMeshIntersections API

Now that we have an axom::Array type, we could consider changing the mesh tester API to return intersection/degeneracy information with axom::Array instead of with std::vector.

To be addressed as part of https://github.com/LLNL/axom/issues/83


How are the hyperparameters tuned?

Hi @yaoyao-liu,
Thanks for your wonderful work.
I have a question: How are the hyperparameters for your model set, in general (not in particular for AANets, I mean parameters such as lambda etc that determine the stability-plasiticity tradeoff).
Do you do multiple runs on the entire dataset with a lot of hyperparameter combinations sampled from a coarse grid?
Or do you determine the hyperparameter separaterly for each task?
Thank you!

Hi @ashok-arjun,
Thanks for your interest in our work. For the hyperparameters that occurred in LUCIR, we directly follow their settings for a fair comparison. You may check their hyperparameter here.
Best,
Yaoyao


Add operations for mutate write::DebuggingInformationEntry

Are there operations for remove the child DIE or attributes? It will be useful to have such operations to mutate in-memory UnitTable forest.

Not yet, but we definitely want them.
For DIEs, removing them just needs to update the children field of the parent, without actually deleting the child from the entries Vec. Attributes can simply be deleted.
One catch with that will be if a deleted attribute referenced something in another table (strings or range lists), then we'll still write those values out (deleting them from the other tables isn't easy). I don't have a solution for that yet.


Understanding Nesting VJP Functions

I have a question about binary_op_broadcasting_test specifically when it pertains to testing the semirings.times on Log semirings.
When looking at the expected function nested in the test, we run the operation through jax.vjp. However, within Log.times there _logaddexp which in itself is a custom vjp function.
So if my understanding is correct, this means that we are converting a function (which contains a custom vjp) into another vjp for testing.
First, is my understanding correct?
Second, I wanted to understand how JAX handles something like this, because torch cannot allow a custom vjp function to be fed into the the torch equivalent of jax.vjp.
Thanks!

First, is my understanding correct?

Yes, we are asking for the VJP of a function part of which is computed with an operation that has a custom VJP implementation

There are 2 different vjp functions in torch - I only used one in which I got a rather dubious (and not clear) error. I later found out through ad-hoc debugging that it comes from calling, for example, torch.func.vjp(semiring.sum, x, y) in which the specific semiring.sum has a custom vjp within it.
There is another vjp within the autograd.functional module that the base class for the custom vjp comes from. I have yet to test this and this perhaps could be more useful in investigating. I will test this today and see if I can write up the tests in a similar fashion to you. Otherwise, I will use something like grad as you mentioned.
Thanks!

After testing both, torch.gradient was most useful. Thank you!


Release does not have esm files

Description

Release does not have esm files
Steps to Reproduce
npm install @kusto/monaco-kusto
System configuration
monaco-kusto version: 0.0.65
monaco-editor version: 0.44.0
Browser:
OS:

Hi Asakiran,

monaco-kusto version: 0.0.65

Could you be looking at a different packages version number? I don't see anything on NPM with that version:

https://www.npmjs.com/package/@kusto/monaco-kusto/v/10.0.7?activeTab=versions
I checked our last few releases and I'm seeing all the files:

https://yarnpkg.com/package?q=%40kusto%2Fmonaco-kusto&name=%40kusto%2Fmonaco-kusto&version=10.0.7


Add internal protobuf dep for py test

Prevent breaks of protobuf's default change

Thanks! Will leave for @achoum to approve and merge

That's awesome. Thanks.


Semver incompatibility

Hi,
It seems the recent version has broken semantic version for any previous version, which we heavily use in our project, microbit-dal.
We have had two new users on v18 who have reported this breakage: https://github.com/lancaster-university/microbit-dal/issues/282
Any help would be greatly appreciated :smile:

Hi @jamesadevine
I don't think this is semver version issue, but a problem with the + characters in the tag names being used.
The method and regex's used to correctly support github URLs was changed in the recent release.
A fix would likely require a modification to the regex to add a + here:
https://github.com/ARMmbed/yotta/blob/master/yotta/lib/sourceparse.py#L60

@thegecko Thanks for the amazingly swift response and solution :smile:

nps


Autorest Regen Preview to 3.0.0-alpha.20230714.5 by Josh Love from refs/pull/3553/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3553

API change check
API changes are not detected in this pull request.


How to automatically refresh OAuth token?

Not an issue but title.
Do I need to run my own interval to refresh the access token?
Because it seems like the library does not support auto refresh

Seems like it is not possible to run an interval since cache_token is never being invalidated since it just checks for a truthy value.
https://github.com/cyperdark/osu-api-extended/blob/master/src/api/v2/index.ts#L21
What I did for a project is something along thoses lines:
if (
    (this.tokenExpire && new Date() > this.tokenExpire) ||
    !this.tokenExpire
  ) {
    console.log('osu! API v2 access_token is expired or needs to be created')
    await this.getToken()
  }

oh, let me added this

With the API login osu should return
{
    "access_token": "verylongstring",
    "expires_in": 86400,
    "refresh_token": "anotherlongstring",
    "token_type": "Bearer"
}

technically u can use the refresh_token if the lease expires to instantly request a new access_token. This is probly a better way of doing it then compleatly re-login like proposed before

i guess auto refresh is working but i can't test it properly, and also there new way to auth
now will make a migrate.md for it and will push

new version is published
migration https://github.com/cyperdark/osu-api-extended/blob/master/changes/2.1.2.md

Nice thanks @cyperdark!

So I tried running my server for more than 24 hours and it was yielding the auth error, Is it a me problem or it doesn't seem to work? :(

hmm, let me see

@cyperdark after 24 hours 😢

bruh, i guess i need to run debug for a 24 hours to see why its failing

Sure thing don't worry
Updated, will let you know!

nice to hear that

i pushed new version, could i ask you to test it (was complete rewrited)
also docs are look better now https://github.com/cyperdark/osu-api-extended/wiki
some sort of migration https://github.com/cyperdark/osu-api-extended/blob/master/changes/2.5.0.md

Do I still need to call auth.login() in each of my files? From what I've seen, you are relogging if the request yield the auth error, does that mean I can just run auth.login() in my root file and everywhere else just doing resources calls ?

once in any files and then it will work in any files


Track RISC-V Compliance Framework

It looks like RISCOF is v2 of riscv-compliance as mentioned in https://github.com/riscv/riscv-compliance/pull/80#issuecomment-585485427.
It is still WIP, but as I was not aware of this and I am not sure how well it is known, I wanted to raise awareness for the new framework.

Interesting find! Let's see how that one evolves.

https://github.com/riscv/riscv-compliance/issues/90#issuecomment-747524231
Looks like it evolved, will check it out.

https://github.com/riscv/riscv-compliance/issues/90#issuecomment-747524231
Looks like it evolved, will check it out.

Nice! https://riscof.readthedocs.io actually looks promising.

Nice! https://riscof.readthedocs.io actually looks promising.

Closing in favor of issue #1233

Closing in favor of issue #1233


As a TA, I want to specify the module details when I first use the app

so that the app can track details such as attendance, student grades and class participation about the module

Config command has been added


add get_targeted_long

addresses https://github.com/delvtech/hyperdrive/issues/775
The solution first attempts to directly compute targeted reserve levels:
For some target rate, $r_t$, the pool share reserves, $z_t$, must be:
$$
z_t = \frac{1}{\mu} \left(
\frac{k}{\frac{c}{\mu} + \left(
(r_t t + 1)^{\frac{1}{T}}
\right)^{1 - T}}
\right)^{\tfrac{1}{1 - T}}
$$
and the pool bond reserves, $y_t$, must be:
$$
y_t = \left(
\frac{k}{ \frac{c}{\mu} +  \left(
\left( r_t t + 1 \right)^{\frac{1}{T}}
\right)^{1-T}}
\right)^{1-T} \left( r_t t + 1 \right)^{\frac{1}{T}}
$$
where $c$ is the vault share price, $\mu$ is the initial vault share price, $t$ is the annualized position duration, and $T$ is the time stretch constant. The corresponding deltas are then:
$$
\Delta x = c * (z_t - z_e)
$$
$$
\Delta y = y - y_t - c(\Delta x)
$$
If that is not successful, then it performs newtons method to minimize
$$
l(x) = r(x) - r_t
$$
for some realized fixed rate, $r(x) = (1 - p(x)) / (p(x) t)$ after a long was opened with $x$ base, where $p(x)$ is the realized price after the long was opened.

A detailed derivation of the solution can be found in section 2 of the attached document.
get_targeted_long.pdf


Create snipe.go.tmpl

Snipe Command :D
A Custom Command to fetch the latest deleted message in a channel

[x] Code changes have been tested on an instance of YAGPDB, or there are no code changes
[x] I have read and followed the contribution guide

Preview

This is literally already a thing in the -undelete command...
Yes, YAGPDB doesn't cache files in that case, but multimedia handling is also pretty bandwidth intensive.

Lol, my bad, i should've included the words custom command, edited it now ^^

More the case that there's the two repository channels in the server, and I thought I was looking at the source code one... 😂 Idk the particular use of it in this case...


No graphics in OS X

I have already encountered this, it is solved by using SDL v2 instead of SDL v1.

I'm afraid there's no quick way of porting Atrium to SDL2 due to serious API changes. I'm working on this, but can't promise this work will be finished soon. Actually, Atrium is known to work on OSX (https://github.com/gecko0307/atrium/issues/2), maybe the problem is somewhere else.


Question: supporting json schema / ajv

First off, thanks for all the work y'all put into this.
Are you guys planning to add a resolver for json schema / ajv?
https://json-schema.org/specification.html
https://github.com/ajv-validator/ajv

That would be great, would you please to contribute a resolver for that? https://github.com/react-hook-form/react-hook-form-resolvers V6 will support different types of schema.

Hey guys! Great to see a PR open for that one!
Can we hope to see it merged anytime soon?

This would be awesome! I have a backend writter in Golang and all the JSON schemas are already defined. Being able to use the same JSON schema would be really good for making the code more concise and DRY. Also, the JSON schema is a standard (ajv is just an implementation for javascript) and it should have been one of the first validation methods.

anyone would like to take over that PR and address some of the comments?

I'll read through the code and comments to see if I can help

Any update on this ? I didn't see it anymore on ReadMe since rework :/

There is an opened PR https://github.com/react-hook-form/resolvers/pull/59 with some issues

Sorry, we are not going to support ajv for now. i know this will make some users angry, but the module ajv old and hard to integrate as far as I can tell. if you need to get it working, please build a custom resolver at your app level.

@bluebill1049 , do you have any further information on what you mean by "the module ajv old and hard to integrate"? ajv is a lot faster than most of the competitors, is still actively developed by lots of developers and has a lot of users, downloads and stars. I didn't look in detail at the code but if it is abstracted properly then I'm not sure I see why that would be a wontfix.
Or do you simply not want to support json schema at all?

https://github.com/react-hook-form/resolvers/issues/309


[WIP] Update and improve integration with dry-struct

Fix #241

Add Dry::Struct

I had to make this work with dry-struct already in another branch which is now merged into master, so you could just hard-reset to latest master and continue from there :)

Will do that, thanks
On Mon, Sep 5, 2016, 9:17 AM Piotr Solnica<EMAIL_ADDRESS>wrote:

I had to make this work with dry-struct already in another branch which is
now merged into master, so you could just hard-reset to latest master and
continue from there :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dry-rb/dry-validation/pull/244#issuecomment-244744748,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAtxw_Kc7DRkLeO1oTKPfdGJAWHztoUks5qnBZjgaJpZM4Jvv1X
.

Thanks to @flash-gordon we now support optional extensions via Dry::Validation.register_extension(:foo) { something that must happen when it is enabled }. You can see how this was used here.
So, now I'd imagine we could refactor code a bit so that we load :struct extension as optional, via something like this:
Dry::Validation.register_extension(:struct) do
  require 'dry/validation/extensions/struct'
end

And in this file we'd just extend APIs to support inferring rules from structs. This does need some refactoring as struct integration has never been written as something optional, so now we gotta improve it :)

Interesting, I will check it out.
On Sun, Sep 11, 2016, 7:36 AM Piotr Solnica<EMAIL_ADDRESS>wrote:

Thanks to @flash-gordon https://github.com/flash-gordon we now support
optional extensions via Dry::Validation.register_extension(:foo) {
something that must happen when it is enabled }. You can see how this was
used here
https://github.com/dry-rb/dry-validation/commit/1bf33a893de4e088ec737c1ea1880e67ce20aa7b
.
So, now I'd imagine we could refactor code a bit so that we load :struct
extension as optional, via something like this:
Dry::Validation.register_extension(:struct) do
require 'dry/validation/extensions/struct'end
And in this file we'd just extend APIs to support inferring rules from
structs. This does need some refactoring as struct integration has
never been written as something optional, so now we gotta improve it :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dry-rb/dry-validation/pull/244#issuecomment-246175769,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAtx403wZRQDF1CKhEIZIgPiT-ee-Kiks5qo-fDgaJpZM4Jvv1X
.

@solnic ah, I was about to write just the same :)

@solnic Closing this @flash-gordon already implemented it.

@cored well, not exactly 😄  We're still lack of support for arrays and nested structs. The part I implemented was the easiest tbh :)


Non-english titles

Hello, i'm asking this on behalf of my father, who has been
using an older version of Kodi (18.9), for a specific reason. He doesn't speak english, so he uses an old Exodus Redux addon in combination with magnetizer. The reason is Exodus shows movie titles and plot in his language and when you use magnetizer it automatically picks the english title of the movie when it searches. I'm asking if it's possible to implement this feature in Burst?

@R3dr0s1d hi. burst is torrents search engine. it does not have UI and does not show title/plot/etc, plugin.video.elementum does all UI things.
And yes, elementum has options to use use any language, just open its settings and go to "Appearance" tab - you can choose primary and secondary language.
Or just change Kodi's interface language and elementum will use it as primary language, and if needed you can choose secondary language - it will be used if there is no translation (of movie's title, for example) to primary language in TMDB database.
If you will see bugs in elementum - please create issue in its repo.
Then, if you want to search torrents in your language - please read this guide https://github.com/elgatito/script.elementum.burst/issues/386
(i can not explain it better than i already explained, so please read/try/repeat until you get desired result)

@R3dr0s1d Sorry, I don't get the ask. If your Kodi is set to, let's say Spanish language (or you have selected Spanish language in Elementum settings), then you would see everything in Spanish and depending on the tracker - Burst can also search for Spanish titles. For that you need to select trackers that have Spanish items. Burst is not deciding that for you.


[Bug]: When the connected Github repo's name is too long, the UI wraps and get rendered weirdly

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
If the connected github repo's name is too long, the lower right corner repo label becomes 2-lines and makes the bottom bar of the workspace render badly.
Suggestions:

allow the repo box to grow in width to accommodate the longer repo name
make it fixed width and instead of line-wrapping, make it do ... to keep to 1 line

OpenHands Installation
Docker command in README
OpenHands Version
No response
Operating System
None
Logs, Errors, Screenshots, and Additional Context
No response

A duplicate of this issue: https://github.com/All-Hands-AI/OpenHands/issues/4676

Keeping this issue instead of the linked issue because it has a better description

/assign
I am looking into this

I am looking into this

Thanks @nafisreza for looking into this, assigned you now.


Around consume instance method

Reasoning:

Consistency/readability: It's generally confusing that #before_consume is an instance method on the handler and .around_consume is a class method.

Flexibility: Allows users to set custom instance variables on the handler that will be accessible in around_consume.

This feature has come up consistently during development. For example, we have built some custom logic into around_consume that relies on metadata from the original payload. We lose that metadata in the before_consume step, forcing us to put all of the logic into around_consume. Another example is error handling for before_consume. In some cases we want to catch exceptions in before_consume and continue to proceed with message processing. Setting an instance variable on the handler is a logical way to signal this downstream.

Hi @michberr and welcome to Phobos!
Spontaneosly I like the idea, and I agree with your reasoning. I will have to look into what this means for us and especially for https://github.com/klarna/phobos_db_checkpoint
I am on vacation 🏝 right now so response time might be varying.

Question to you @michberr and @jasondoc3
Given that this change is merged in the future:
Could this, from your perspective, also mean removing #before_consume since that can be part of #around_consume now...? 🤔
I am not to fond of #before_consume, it is very dodgy, but as Phobos works atm we need it right now.

I moved the discussion about before consume to a separate issue, see klarna/phobos#84

@klippx having some issues with Travis. The first build failed for some reason I can't comprehend (undefined method 'debug' for logging::logger)https://travis-ci.com/klarna/phobos/builds/79593666. I triggered a rebuild by pushing an empty commit which then passed https://travis-ci.com/klarna/phobos/builds/79595739, but github the PR is still pointing to the failed build.

Yes, that is a separate issue which is hard to recreate. We should track it
and fix it. I think it has to do with concurrency and logging not being
thread safe. We are seeing it in production for a different project but
have not tackled it yet. Only speculation from my side...
fre 20 juli 2018 kl. 18:47 skrev Michelle Berry<EMAIL_ADDRESS>
@klippx https://github.com/klippx having some issues with Travis. The
first build failed for some reason I can't comprehend (undefined method
'debug' for logging::logger)
https://travis-ci.com/klarna/phobos/builds/79593666. I triggered a
rebuild by pushing an empty commit which then passed
https://travis-ci.com/klarna/phobos/builds/79595739, but github the PR is
still pointing to the failed build.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/klarna/phobos/pull/82#issuecomment-406658850, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACqAT_OWZEJKz3ITa_TPs2ZRUal3rslPks5uIgmFgaJpZM4VL6A8
.

Thanks for the effort, really good first PR ❤ I will update changelog.

Released in 1.8.0


Incorrect documented  istioctl ctl  in egressgateway manifest generation

Bug description
Executing the command to generate the egress gateway generates invalid output
[x] Configuration Infrastructure
[x] Docs
[ ] Installation
[x ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
The command should succeed and generate an egress gateway manifest
Steps to reproduce the bug

Execute the following command as documented in https://istio.io/docs/tasks/traffic-management/egress/wildcard-egress-hosts/#setup-egress-gateway-with-sni-proxy

$ cat <<EOF | istioctl manifest generate --set values.global.istioNamespace=istio-system -f - > ./istio-egressgateway-with-sni-proxy.yaml
> gateways:
>   enabled: true
>   istio-ingressgateway:
>     enabled: false
>   istio-egressgateway:
>     enabled: false
>   istio-egressgateway-with-sni-proxy:
>     enabled: true
>     labels:
>       app: istio-egressgateway-with-sni-proxy
>       istio: egressgateway-with-sni-proxy
>     replicaCount: 1
>     autoscaleMin: 1
>     autoscaleMax: 5
>     cpu:
>       targetAverageUtilization: 80
>     serviceAnnotations: {}
>     type: ClusterIP
>     ports:
>       - port: 443
>         name: https
>     secretVolumes:
>       - name: egressgateway-certs
>         secretName: istio-egressgateway-certs
>         mountPath: /etc/istio/egressgateway-certs
>       - name: egressgateway-ca-certs
>         secretName: istio-egressgateway-ca-certs
>         mountPath: /etc/istio/egressgateway-ca-certs
>     configVolumes:
>       - name: sni-proxy-config
>         configMapName: egress-sni-proxy-configmap
>     additionalContainers:
>     - name: sni-proxy
>       image: nginx
>       volumeMounts:
>       - name: sni-proxy-config
>         mountPath: /etc/nginx
>         readOnly: true
> EOF
could not read values from file -: open -: no such file or directory

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl  version --remote
client version: 1.4.3
control plane version: 1.4.3
data plane version: 1.4.3 (8 proxies)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"archive", BuildDate:"2020-02-12T14:56:45Z", GoVersion:"go1.13.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2+k3s1", GitCommit:"cdab19b09a84389ffbf57bebd33871c60b1d6b28", GitTreeState:"clean", BuildDate:"2020-01-27T18:09:26Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
Istioctl
Environment where bug was observed (cloud vendor, OS, etc)
Native k8s

@ayj did you have some pr adding reading from stdin?

Yes, support for reading from stdin went into master. 1.5 support is also pending.

Thanks . What's the equivalent command I can use in 1.4.x ? I tried reading the snippet from a temp file but that didn't work either .
Please advise / update the 1.4.x doc . Thanks

Closing as a duplicate of https://github.com/istio/istio/issues/21015


Proposal: add admin-only registration mode

Currently registration can be either enabled or disabled.
There's probably a good use case for allowing registration only by admins.  This would allow admins to create accounts on behalf of developers and set an initial password.  Developers can reset their password after initial login.
This helps admins avoid the "enable registration long enough for a new developer to register and then disable it again" dance.

Already exists. deisctl config controller set registrationMode=adminOnly!

This was implemented in #3399.

Nice.  Missed that!!!  Closing.


unable to export to external Prometheus server

Hi,
I have a working grafana with prometheus server (on a node). ON a diffarent node I am runnibng burow and burrow_exporter (as 2 docker services). For burrow_exporter i have the below configuration. when i see burrow_logs i dont see any errors (docker logs -f ; I see Scraping burrow.. , and Finished scraping burrow....  ). But i dont see any entries into my prometheus server with substring "burrow" so clearly the scrapped data is not sent across.
if you can give me a way to push data from burrow_exporter to external promethus server over an arbitary IP, will be a great help.
services:
  burrow:
    build: .
    environment:
        BURROW_ADDR: http://<IP_ADDRESS>:8000
        METRICS_ADDR: <IP_ADDRESS>:9090
        INTERVAL: 5
        API_VERSION: 3
    volumes:
      - ../burrow-master/docker-config:/etc/burrow/
      - ${PWD}/tmp:/var/tmp/burrow

I understood now. I think I need to have prometheus server which calls this exporter. Will check and mark this resolved.

OK got it. The docker doesnt start a prometheus server. But opens a port so that a prometheus server can scrape it. Working now fine

@ravieze I've pushed https://github.com/jirwin/burrow_exporter/releases/tag/v0.0.6 that adds support for environment variables like you have in your example. Thanks for bringing this up!

Can u also add relevant documentation?


Add blog-post about the features in 2021

The markdown can be seen here, but to see the final version with images, use hugo to locally build the webpage (instructions can be found here or see the image bellow:

@TomasTomecek @jpopelka thanks a lot for a really precise review!

Really nice summary, thanks for taking the time to write it up! :1st_place_medal:


Add cpu-profiling to kpod

Add a global flag for cpu-profiling to allow us to
profile kpod for performance issues.
To parse its results, use:
go tool pprof --text <profile_path>
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM. Tests are green, merging
@rh-atomic-bot r+

LGTM. Tests are green, merging

BTW remember one nice thing with Homu is you don't need to wait for the tests to pass - they're rerun on merge, so if the patch looks good you can fearlessly r+ and if the tests don't pass, it isn't merged.


Modifying multiple blog posts from one page

I need the testimonial-style editing UI that's available on the front page for blog articles. In particular, I am envisioning a "listing page" that lists all the blog titles in a table or list, and I'd like all of those titles to be editable.
It appears that the testimonials are saved as one JSON dump in the DB, while the articles get their individual entries/rows in the DB. I wasn't able to figure out how to adapt the code to suit my use case: I do want the articles/blog posts to retain their individual identities in the DB, but I'd like to be able to move them around (ideally this is a custom ordering that gets saved on the go, specific to the "listing page") and edit the titles simultaneously as well.
I am afraid I know nothing about how Svelte works, so sorry if this is somehow an obvious adaptation of the existing code.
PS. Off-topic, but many thanks for making this awesome template and workflow!

Hey! Sorry for taking me sooo long to respond. The testimonials are "self-contained" within one page (the page just has one JSON data field in the database) while the blog posts (articles) are separate entites in the database, with fields for title, content (html) and some metadata.
See: https://github.com/michael/editable-website/blob/main/sql/schema.sql
You could easily come up with a listings table powered by a custom SQLite query. For simultaneous edits of titles you'd need to come up with some infrastructure, basically a rest endpoint that takes an array of article_id + title pairs and update them accordingly in the datbase (see api.js). You can basically achieve anything that be done with Svelte and SvelteKit, but the template is only meant as a starting point, so I think if you want to do more advanced things, studying Svelte/SvelteKit is important.
Hope I wasn't too late and this is still helpful for you. All the best!