Router: Type mismatch, expected: Int, actual: Any

Finch: 0.6.0
The code below( from the route.md file )
  def getUserTicket(userId: Int, ticketId: Int): Ticket = ???
  val router: Router[Int / Int] = Get / "users" / int("userId") / "tickets" / int("ticketId")
  val tickets: Router[Ticket] = router /> { case userId / ticketId => getUserTicket(userId, ticketId) }

gives the following compilation error:
constructor cannot be instantiated to expected type;
[error]  found   : io.finch.route./[A,B]
[error]  required: (Int, Int)
[error]   val tickets: Router[Ticket] = router /> { case userId / ticketId => getUserTicket(userId, ticketId) }

and for the code getUserTicket(userId, ticketId) IntelliJ complains with the following message:
Type mismatch, expected: Int, Actual:Any

Well. This is a typical example of an outdated documentation. It should be much simpler in 0.6.0:
scala> val tickets: Router[Ticket] = router /> getUserTicket
tickets: io.finch.route.Router[Ticket] = GET/users/:userId/tickets/:ticketId

@lderks do you mind to make a PR that updates docs?

@vkostyukov https://github.com/vkostyukov
https://github.com/finagle/finch/pull/231 https://github.com/finagle/finch/pull/231

On 13 Apr 2015, at 18:53, Vladimir Kostyukov<EMAIL_ADDRESS>wrote:
@lderks https://github.com/lderks do you mind to make a PR that updates docs?
—
Reply to this email directly or view it on GitHub https://github.com/finagle/finch/issues/230#issuecomment-92423583.

I bet we can close it now.


Why don't you have safe observers for subjects?

While all Producer<T>'s cast the anonymous observers they receive to safe observers or safe anonymous observers, why don't you have safe observers for subjects?

Mostly for performance because a subject is often used as a multicast block, e.g. within operators like Publish. The rationale is that a subject is transparent and inherits all the sins of the publisher (i.e. the user of the observer side of the subject). Any safeguarding should happen there: because it's an observer, one should use it conform the grammar (or use Observer.* methods to wrap it with safe-guarding or synchronization logic in case it's to be passed to an untrusted party, i.e. this safety is pay-for-play). Note that operators rely on the input(s) being conform the observer grammar and - if this condition is met - guarantee that they will only produce output conform to the observer grammar. That's where we put in safeguarding if an input is not "trusted".

As I remember it, waaay back in v1 days (2010/2011) everything was safe. However it meant that even if you wrote safe code, you had to pay the cost of all the safety checks in Rx.
Thankfully this has been relaxed, so you can opt-in to safety if a source isnt' trustworthy using features like .Synchroinze(). Due to these design choices Rx performs much faster :-)

Thanks, @bartdesmet and @LeeCampbell. :-)
Thanks for closing this, @onovotny, and sorry about having left it open for so long.
I started doing things other than Rx in the meantime and so I hadn't had a chance to think more about this since @bartdesmet  and @LeeCampbell  posted their answers and so I left them open on purpose. I realize now that I can still keep thinking about these issues even later. :-)


Use yield on openai services

there should be yield or something like that used to get faster output
at the moment it takes a long time to see the result if a few hundred translations are sent to openai

i thinks its already working :D


Report FabricASEngineAnalytics fails to load content for ExecutionMetrics:

Hi all,
The report FabricASEngineAnalytics fails to load the content for ExecutionMetrics:

The other tables work just fine. I also tried to reduce the amount of data (by loading only one day). However the issue remains.
Anyone else facing this issue or suggestions on how to resolve the issue?
Thank you,
Daniel

could you please try entering a semantic model Id to further filtering the data?

still showing the same error message.. tried with different semantic model id's :(

Have you tried the PBIASEngine.pbit? does it load successfully for you?

yes that one works - but I want to use the new report for Fabrics

Our proxy vendor confirmed that the requests are blocked due to exceeded URL length (8192 characters). Refresh in PBI Service works fine


visualize() not able to save the image

Getting the following error during run:
Traceback (most recent call last):
  File "main.py", line 96, in <module>
    tf.app.run()
  File "....../tensorflow/python/platform/app.py", line 44, in run
    _sys.exit(main(_sys.argv[:1] + flags_passthrough))
  File "main.py", line 93, in main
    visualize(sess, dcgan, FLAGS, OPTION)
  File "...../DCGAN-tensorflow/utils.py", line 174, in visualize
    save_images(samples, [8, 8], './samples/test_arange_%s.png' % (idx))
  File "....../DCGAN-tensorflow/utils.py", line 26, in save_images
    return imsave(inverse_transform(images), size, image_path)
  File "....../DCGAN-tensorflow/utils.py", line 47, in imsave
    return scipy.misc.imsave(path, merge(images, size))
  File "....../DCGAN-tensorflow/utils.py", line 43, in merge
    img[j*h:j*h+h, i*w:i*w+w, :] = image
ValueError: could not broadcast input array from shape (64,64,3) into shape (0,64,3)

visualize() is working if the batch-size <= 64. More than 64 is failing.

That's why I manually set the number of images to be visualize as 8x8 as https://github.com/carpedm20/DCGAN-tensorflow/blob/master/utils.py#L156. You can change this 8, 8 or 64 values in utils.py to make it work for batch_size > 64

Thanks @carpedm20,
Yes, that's right. I have also arrived at the same place while I was debugging. I will try to find a way to set these sizes automatically based on batch-size.

The following changes resolve my issue:
image_frame_dim = int(math.ceil(config.batch_size**.5))
save_images(samples, [image_frame_dim, image_frame_dim], './samples/test_arange_%s.png' % (idx))

Fixed by #122

@asispatra can you generate more than 100 images?? Help needed

@rp2017, I have made one PR #216 , I have tested only for "OPTION = 1" as specified in main.py. Please verify for other possible value of OPTION.


Support to laravel 5.8

In laravel I get the following error, when executing php artisan tunneler: active
Fatal error: Uncaught ReflectionException: Class config does not exist in /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Container/Container.php:790
Stack trace:
#0 /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Container/Container.php(790): ReflectionClass->__construct('config')
#1 /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Container/Container.php(667): Illuminate\Container\Container->build('config')
#2 /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Container/Container.php(615): Illuminate\Container\Container->resolve('config', Array)
#3 /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(767): Illuminate\Container\Container->make('config', Array)
#4 /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Container/Container.php(1225): Illuminate\Foundation\Application->make('config')
#5 /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.ph in /Users/humerez/Sites/manage/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 790

Huh, this was never closed.


JSNode reusing

ILBlockTranslator reuse at least JSVariable/JSIndirectVariable (through Variables/IndirectVariables dictionaries).
I used JSNode to store source mapping information, so reusing of them make such use problematically.
@kg, do you remember why you introduced such reusing? How will be better replace it?

Mostly used for performance reasons, I think? And maybe for reference equality, but that's not really useful. I don't see any problem with just creating new instances every time as necessary.


Strict null check 'vs/workbench/contrib/debug/*'

Part of #60565
Tracks updating files under vs/workbench/contrib/debug/ to have strict null checking. The current files are currently eligible:
-'vs/workbench/contrib/debug/common/debugModel.ts'
-'vs/workbench/contrib/debug/electron-browser/breakpointWidget.ts'

'vs/workbench/contrib/debug/node/debugger.ts'
-'vs/workbench/contrib/debug/node/terminals.ts'

Other files under debug may become eligible once these files are strict null checked
Steps

Add target file to the files section of src/tsconfig.strictNullChecks.json
Run yarn strict-null-check -- --watch
Fix strict null check compiler errors
Verify normal build still works

@weinand let me know if you would like to help out here?
debugger.ts would be a good candidate to start

@isidorn I can look into debugger.ts...

@weinand cool, if you like it feel free to pick up other files.
I finished /common and plan to continue with /browser tomorrow.

no, I won't like it.

@weinand could you look into loadedScriptsView.ts? I can also look into it if you prefer.

@isidorn will do

loadedScriptsView.ts done

This is done.
Only 3 test files remain which depends on contrib/files to be null check aware (which I am looking into right now as part of https://github.com/Microsoft/vscode/issues/70338)
@weinand thanks for help!


[Kafka] keda-operator-metrics-apiserver begins failing SSL handshake

Report
I've set up a a few Keda scalers for deployments based off some Kafka topics, which begun scaling the deployment up. After some time, I've observed Kafka logs saying:
Jan 17 14:10:22 kafka4 kafka-server-start.sh[127212]: [2022-01-17 14:10:22,653] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1005] Failed authentication with /<IP_ADDRESS> (SSL handshake failed) (org.apache.kafka.common.network.Selector)
Jan 17 14:10:23 kafka4 kafka-server-start.sh[127212]: [2022-01-17 14:10:23,071] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1005] Failed authentication with /<IP_ADDRESS> (SSL handshake failed) (org.apache.kafka.common.network.Selector)
Jan 17 14:10:23 kafka4 kafka-server-start.sh[127212]: [2022-01-17 14:10:23,511] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1005] Failed authentication with /<IP_ADDRESS> (SSL handshake failed) (org.apache.kafka.common.network.Selector)
Jan 17 14:10:23 kafka4 kafka-server-start.sh[127212]: [2022-01-17 14:10:23,944] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1005] Failed authentication with /<IP_ADDRESS> (SSL handshake failed) (org.apache.kafka.common.network.Selector)

On all Kafka nodes I see the same warning about the same IP so all requests are coming from a single node. After finding out which node it was:
kubectl get nodes -o wide | grep <IP_ADDRESS>
scw-web-crawler-flannel-pool-proxies-b6da4a90e   Ready      <none>   3d1h   v1.22.3   <IP_ADDRESS>     <IP_ADDRESS>    Ubuntu 20.04.1 LTS 4f7656de55   5.4.0-80-generic   containerd://1.5.5

Scheduled pods on this node:
Non-terminated Pods:          (7 in total)
  Namespace                   Name                                                CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                                ------------  ----------  ---------------  -------------  ---
  keda                        keda-operator-metrics-apiserver-7549b7db99-cp5mr    100m (3%)     1 (35%)     100Mi (3%)       1000Mi (34%)   22h
  kube-system                 csi-node-9w4tz                                      0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d1h
  kube-system                 flannel-shntz                                       100m (3%)     100m (3%)   50Mi (1%)        50Mi (1%)      3d1h
  kube-system                 konnectivity-agent-wkbpj                            0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d1h
  kube-system                 kube-proxy-wwbk6                                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         3d1h
  kube-system                 metrics-server-74cf4b5cf9-24k7d                     100m (3%)     0 (0%)      300Mi (10%)      0 (0%)         37h
  kube-system                 node-problem-detector-2f59w                         10m (0%)      10m (0%)    80Mi (2%)        80Mi (2%)      3d1h

After seeing this I've concluded that the "culprit" is keda-operator-metrics-apiserver-7549b7db99-cp5mr, but it doesn't make sense for me as why the metrics server would try authenticating with Kafka.
Expected Behavior
Keda should properly and consistently scale deployments based off Kafka topics lag
Actual Behavior
After receiving those warnings on Kafka node, one of the scaled objects will constantly fail, causing it to use the Fallback
Steps to Reproduce the Problem

Deploy keda using helm charts and provided values
Setup TLS and auth secrets, trigger and scaled objects
Observe scaling up and then scaling down due to falling back to original replica count

Logs from KEDA operator
2022-01-16T14:29:20.663Z	INFO	controller-runtime.metrics	Metrics server is starting to listen	{"addr": ":8080"}
2022-01-16T14:29:20.678Z	INFO	setup	Running on Kubernetes 1.22	{"version": "v1.22.3"}
2022-01-16T14:29:20.678Z	INFO	setup	Starting manager
2022-01-16T14:29:20.678Z	INFO	setup	KEDA Version: 2.5.0
2022-01-16T14:29:20.678Z	INFO	setup	Git Commit: 22d71631c7a6e0e0ea8aef434263321d65975c29
2022-01-16T14:29:20.678Z	INFO	setup	Go Version: go1.17.3
2022-01-16T14:29:20.678Z	INFO	setup	Go OS/Arch: linux/amd64
I0116 14:29:20.679368       1 leaderelection.go:248] attempting to acquire leader lease keda/operator.keda.sh...
2022-01-16T14:29:20.679Z	INFO	Starting metrics server	{"path": "/metrics"}
I0116 14:30:05.162680       1 leaderelection.go:258] successfully acquired lease keda/operator.keda.sh
2022-01-16T14:30:05.163Z	INFO	controller.clustertriggerauthentication	Starting EventSource	{"reconciler group": "keda.sh", "reconciler kind": "ClusterTriggerAuthentication", "source": "kind source: *v1alpha1.ClusterTriggerAuthentication"}
2022-01-16T14:30:05.163Z	INFO	controller.clustertriggerauthentication	Starting Controller	{"reconciler group": "keda.sh", "reconciler kind": "ClusterTriggerAuthentication"}
2022-01-16T14:30:05.164Z	INFO	controller.triggerauthentication	Starting EventSource	{"reconciler group": "keda.sh", "reconciler kind": "TriggerAuthentication", "source": "kind source: *v1alpha1.TriggerAuthentication"}
2022-01-16T14:30:05.164Z	INFO	controller.triggerauthentication	Starting Controller	{"reconciler group": "keda.sh", "reconciler kind": "TriggerAuthentication"}
2022-01-16T14:30:05.165Z	INFO	controller.scaledobject	Starting EventSource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "source": "kind source: *v1alpha1.ScaledObject"}
2022-01-16T14:30:05.166Z	INFO	controller.scaledobject	Starting EventSource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "source": "kind source: *v2beta2.HorizontalPodAutoscaler"}
2022-01-16T14:30:05.166Z	INFO	controller.scaledobject	Starting Controller	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject"}
2022-01-16T14:30:05.165Z	INFO	controller.scaledjob	Starting EventSource	{"reconciler group": "keda.sh", "reconciler kind": "ScaledJob", "source": "kind source: *v1alpha1.ScaledJob"}
2022-01-16T14:30:05.166Z	INFO	controller.scaledjob	Starting Controller	{"reconciler group": "keda.sh", "reconciler kind": "ScaledJob"}
2022-01-16T14:30:05.265Z	INFO	controller.clustertriggerauthentication	Starting workers	{"reconciler group": "keda.sh", "reconciler kind": "ClusterTriggerAuthentication", "worker count": 1}
2022-01-16T14:30:05.267Z	INFO	controller.triggerauthentication	Starting workers	{"reconciler group": "keda.sh", "reconciler kind": "TriggerAuthentication", "worker count": 1}
2022-01-16T14:30:05.267Z	INFO	controller.scaledjob	Starting workers	{"reconciler group": "keda.sh", "reconciler kind": "ScaledJob", "worker count": 1}
2022-01-16T14:30:05.268Z	INFO	controller.scaledobject	Starting workers	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "worker count": 5}
2022-01-16T14:30:05.268Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-content-crawler", "namespace": "default"}
2022-01-16T14:30:05.268Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-directory-crawler", "namespace": "default"}
2022-01-16T14:30:05.268Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-head-crawler", "namespace": "default"}
2022-01-16T14:30:05.268Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-parallel-proxy", "namespace": "default"}
2022-01-16T14:30:05.719Z	INFO	controller.scaledobject	Initializing Scaling logic according to ScaledObject Specification	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-content-crawler", "namespace": "default"}
2022-01-16T14:30:05.772Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-content-crawler", "namespace": "default"}
2022-01-16T14:30:05.927Z	INFO	controller.scaledobject	Initializing Scaling logic according to ScaledObject Specification	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-directory-crawler", "namespace": "default"}
2022-01-16T14:30:06.233Z	INFO	controller.scaledobject	Initializing Scaling logic according to ScaledObject Specification	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-head-crawler", "namespace": "default"}
2022-01-16T14:30:06.486Z	INFO	kafka_scaler	invalid offset found for topic fsn1.crawler.cmd.process.high.0 in group crawler-group-directory-prod and partition 611, probably no offset is committed yet
2022-01-16T14:30:06.542Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-directory-crawler", "namespace": "default"}
2022-01-16T14:30:07.146Z	INFO	controller.scaledobject	Initializing Scaling logic according to ScaledObject Specification	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-parallel-proxy", "namespace": "default"}
2022-01-16T14:30:07.192Z	INFO	controller.scaledobject	Reconciling ScaledObject	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "kafka-scaledobject-parallel-proxy", "namespace": "default"}
2022-01-16T14:30:07.564Z	INFO	kafka_scaler	invalid offset found for topic fsn1.crawler.cmd.process.high.0 in group crawler-group-directory-prod and partition 611, probably no offset is committed yet
2022-01-16T14:30:56.069Z	INFO	kafka_scaler	invalid offset found for topic fsn1.crawler.cmd.process.high.0 in group crawler-group-directory-prod and partition 611, probably no offset is committed yet
2022-01-16T14:31:12.288Z	INFO	kafka_scaler	invalid offset found for topic fsn1.crawler.cmd.process.high.0 in group crawler-group-directory-prod and partition 611, probably no offset is committed yet

and some more repeating lines about the topic which did not had offsets committed yet, but that's not controlling the scaled object which fails.
KEDA Version
2.5.0
Kubernetes Version
1.22
Platform
Other
Scaler Details
Kafka
Anything else?
I've deployed Keda using the official helm chart with the default values, except http timeout which I've set to 30 seconds:
# Default values for keda.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

image:
  keda:
    repository: ghcr.io/kedacore/keda
    # Allows people to override tag if they don't want to use the app version
    tag:
  metricsApiServer:
    repository: ghcr.io/kedacore/keda-metrics-apiserver
    # Allows people to override tag if they don't want to use the app version
    tag:
  pullPolicy: Always

crds:
  install: true

watchNamespace: ""

imagePullSecrets: []
operator:
  name: keda-operator
  replicaCount: 1

metricsServer:
  # use ClusterFirstWithHostNet if `useHostNetwork: true` https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy
  dnsPolicy: ClusterFirst
  useHostNetwork: false

# -- Custom labels to add into metadata
additionalLabels: {}
  # foo: bar

podAnnotations:
  keda: {}
  metricsAdapter: {}
podLabels:
  keda: {}
  metricsAdapter: {}

## See `kubectl explain poddisruptionbudget.spec` for more
## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
podDisruptionBudget: {}
#  minAvailable: 1
#  maxUnavailable: 1

rbac:
  create: true

serviceAccount:
  # Specifies whether a service account should be created
  create: true
  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  name: keda-operator
  # Annotations to add to the service account
  annotations: {}

# Set to the value of the Azure Active Directory Pod Identity
# This will be set as a label on the KEDA Pod(s)
podIdentity:
  activeDirectory:
    identity: ""

# Set this if you are using an external scaler and want to communicate
# over TLS (recommended). This variable holds the name of the secret that
# will be mounted to the /grpccerts path on the Pod
grpcTLSCertsSecret: ""

# Set this if you are using HashiCorp Vault and want to communicate
# over TLS (recommended). This variable holds the name of the secret that
# will be mounted to the /vault path on the Pod
hashiCorpVaultTLS: ""

logging:
  operator:
    ## Logging level for KEDA Operator
    # allowed values: 'debug', 'info', 'error', or an integer value greater than 0, specified as string
    # default value: info
    level: info
    # allowed valuesL 'json' or 'console'
    # default value: console
    format: console
  metricServer:
    ## Logging level for Metrics Server
    # allowed values: '0' for info, '4' for debug, or an integer value greater than 0, specified as string
    # default value: 0
    level: 0

podSecurityContext: {}
  # fsGroup: 2000

securityContext: {}
  # capabilities:
  #   drop:
  #   - ALL
  # readOnlyRootFilesystem: true
  # runAsNonRoot: true
  # runAsUser: 1000

service:
  type: ClusterIP
  portHttp: 80
  portHttpTarget: 8080
  portHttps: 443
  portHttpsTarget: 6443

  annotations: {}

# We provides the default values that we describe in our docs:
# https://keda.sh/docs/latest/operate/cluster/
# If you want to specify the resources (or totally remove the defaults), change or comment the following
# lines, adjust them as necessary, or simply add the curly braces after 'operator' and/or 'metricServer'
# and remove/comment the default values
resources:
  limits:
    cpu: 1
    memory: 1000Mi
  requests:
    cpu: 100m
    memory: 100Mi

nodeSelector: {}

tolerations: []

affinity: {}
  # podAntiAffinity:
  #   requiredDuringSchedulingIgnoredDuringExecution:
  #   - labelSelector:
  #       matchExpressions:
  #       - key: app
  #         operator: In
  #         values:
  #         - keda-operator
  #         - keda-operator-metrics-apiserver
  #     topologyKey: "kubernetes.io/hostname"

## Optional priorityClassName for KEDA Operator and Metrics Adapter
priorityClassName: ""

## The default HTTP timeout in milliseconds that KEDA should use
## when making requests to external services. Removing this defaults to a
## reasonable default
http:
  timeout: 30000

## Extra environment variables that will be passed onto KEDA operator and metrics api service
env:
# - name: ENV_NAME
#   value: 'ENV-VALUE'

# Extra volumes and volume mounts for the deployment. Optional.
volumes:
  keda:
    extraVolumes: []
    extraVolumeMounts: []

  metricsApiServer:
    extraVolumes: []
    extraVolumeMounts: []

prometheus:
  metricServer:
    enabled: false
    port: 9022
    portName: metrics
    path: /metrics
    podMonitor:
      # Enables PodMonitor creation for the Prometheus Operator
      enabled: false
      interval:
      scrapeTimeout:
      namespace:
      additionalLabels: {}
  operator:
    enabled: false
    port: 8080
    path: /metrics
    podMonitor:
      # Enables PodMonitor creation for the Prometheus Operator
      enabled: false
      interval:
      scrapeTimeout:
      namespace:
      additionalLabels: {}
    prometheusRules:
      # Enables PrometheusRules creation for the Prometheus Operator
      enabled: false
      namespace:
      additionalLabels: {}
      alerts: []
        # - alert: KedaScalerErrors
        #   annotations:
        #     description: Keda scaledObject {{ $labels.scaledObject }} is experiencing errors with {{ $labels.scaler }} scaler
        #     summary: Keda Scaler {{ $labels.scaler }} Errors
        #   expr: sum by ( scaledObject , scaler) (rate(keda_metrics_adapter_scaler_errors[2m]))  > 0
        #   for: 2m
        #   labels:

Another strange thing I've just noticed is that operator metrics are not even enabled in this chart.

CRDs used for scaling:
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: keda-trigger-auth-kafka-credential
  namespace: default
spec:
  secretTargetRef:
    - parameter: sasl
      name: keda-kafka-secrets
      key: sasl
    - parameter: username
      name: keda-kafka-secrets
      key: username
    - parameter: password
      name: keda-kafka-secrets
      key: password
    - parameter: tls
      name: keda-kafka-secrets
      key: tls
    - parameter: ca
      name: keda-kafka-secrets
      key: ca
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: kafka-scaledobject-content-crawler
  namespace: default
spec:
  scaleTargetRef:
    name: avro-crawler
  pollingInterval: 55
  idleReplicaCount: 0
  minReplicaCount: 1 # Optional Default 0
  maxReplicaCount: 1800 # Optional Default 100
  fallback: # Optional. Section to specify fallback options
    failureThreshold: 10
    replicas: 50
  triggers:
    - type: kafka
      metadata:
        bootstrapServers: broker-svc
        # Make sure that this consumer group name is the same one as the one that is consuming topics
        consumerGroup: crawler-group-normal-prod
        topic: fsn1.crawler.cmd.process.normal.0
        # Optional
        lagThreshold: "10"
        offsetResetPolicy: latest
        version: 3.0.0
      authenticationRef:
        name: keda-trigger-auth-kafka-credential
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: kafka-scaledobject-directory-crawler
  namespace: default
spec:
  scaleTargetRef:
    name: avro-high-crawler
  pollingInterval: 50
  idleReplicaCount: 0
  minReplicaCount: 1 # Optional Default 0
  maxReplicaCount: 300 # Optional Default 100
  fallback: # Optional. Section to specify fallback options
    failureThreshold: 10
    replicas: 50
  triggers:
    - type: kafka
      metadata:
        bootstrapServers: broker-svc
        # Make sure that this consumer group name is the same one as the one that is consuming topics
        consumerGroup: crawler-group-directory-prod
        topic: fsn1.crawler.cmd.process.high.0
        # Optional
        lagThreshold: "10"
        offsetResetPolicy: latest
        version: 3.0.0
      authenticationRef:
        name: keda-trigger-auth-kafka-credential
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: kafka-scaledobject-parallel-proxy
  namespace: default
spec:
  scaleTargetRef:
    name: parallel-proxy
  pollingInterval: 65
  idleReplicaCount: 0
  minReplicaCount: 1 # Optional Default 0
  maxReplicaCount: 150 # Optional Default 100
  fallback: # Optional. Section to specify fallback options
    failureThreshold: 10
    replicas: 50
  triggers:
    - type: kafka
      metadata:
        bootstrapServers: broker-svc
        # Make sure that this consumer group name is the same one as the one that is consuming topics
        consumerGroup: crawler-group-directory-prod
        topic: fsn1.crawler.cmd.process.high.0
        # Optional
        lagThreshold: "10"
        offsetResetPolicy: latest
        version: 3.0.0
      authenticationRef:
        name: keda-trigger-auth-kafka-credential
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: kafka-scaledobject-head-crawler
  namespace: default
spec:
  scaleTargetRef:
    name: avro-head-crawler
  pollingInterval: 60
  idleReplicaCount: 0
  minReplicaCount: 1 # Optional Default 0
  maxReplicaCount: 1200 # Optional Default 100
  fallback: # Optional. Section to specify fallback options
    failureThreshold: 10
    replicas: 50
  triggers:
    - type: kafka
      metadata:
        bootstrapServers: broker-svc
        # Make sure that this consumer group name is the same one as the one that is consuming topics
        consumerGroup: crawler-group-head-prod
        topic: fsn1.crawler.cmd.process.head.0
        # Optional
        lagThreshold: "10"
        offsetResetPolicy: latest
        version: 3.0.0
      authenticationRef:
        name: keda-trigger-auth-kafka-credential

KEDA Metrics Server needs to access Kafka to scrape metrics used for 1<->N scaling.
This is an open issure related to the not committed offset: https://github.com/kedacore/keda/issues/2033
Still I am not sure why is the Metrics Server not able to authenticate 🤷♂

I'll do some more investigating, maybe try with different versions of Keda as I've been using it for months and now is the first time I encounter such error.

It might be related to the caching bug introduced in 2.5.0. This will be solved in 2.6.0, which should be released soon.

I upgraded keda to 2.6.0 last night and the issue didn't come up, cheers!


app: object-spriter.js errors in master

These errors are appearing in latest master.

Thanks, probably a double-encoding issue.
https://github.com/webaverse/totum/pull/91

I think this was caused by the UI refactor rewinding totum: https://github.com/webaverse/app/commit/01c2d01243624e0884678fffa37d281c567e9e67
That PR was reverted, so it should be ok in master now -- please confirm.
CC @ohmed @0reo

Resolved.


HTTP 403 for images from services.digitalglobe.com

URL
https://services.digitalglobe.com/earthservice/tmsaccess/tms/1.0.0/DigitalGlobe:ImageryTileService@EPSG:3857@jpg/18/155211/132645.jpg?connectId=ca613e76-811f-46e7-9e1d-84f6795441c2
How to reproduce the issue?
Open project https://tasks.hotosm.org/projects/11966 and start mapping. You will see a black map without any images. HTTP 403 error for all images from services.digitalglobe.com
Screenshot(s) or anything else?
No response
Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
<IP_ADDRESS>
Which browsers are you seeing this problem on?
Microsoft Edge

Can you please show screenshot of the issue

Yes, you'll want to contact the manager of that HOT project to have them update the imagery source in use, unfortunately. They've configured a custom imagery source, so it's not an issue with iD, but with the task configuration. I submitted a report of bad imagery on a task within the broader task there already, but if you have any relation with them, you might communicate that directly.
Closing as duplicate.

[like]  Clemens Schotte reacted to your message:

From: Nick Santos @.>
Sent: Tuesday, October 24, 2023 6:19:05 PM
To: openstreetmap/iD @.>
Cc: Author @.***>
Subject: Re: [openstreetmap/iD] HTTP 403 for images from services.digitalglobe.com (Issue #9947)
Yes, you'll want to contact the manager of that HOT project to have them update the imagery source in use, unfortunately. They've configured a custom imagery source, so it's not an issue with iD, but with the task configuration. I submitted a report of bad imagery on a task within the broader task there already, but if you have any relation with them, you might communicate that directly.
Closing as duplicate.
—
Reply to this email directly, view it on GitHubhttps://github.com/openstreetmap/iD/issues/9947#issuecomment-1777785066 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACDMVFATZ6XQERF3YORVMYDYBABBVBFKMF2HI4TJMJ2XIZLTSWBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIYTKOBQGI4DMMBVGKSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRTGUZDQOJXHE3DEMVENZQW2ZNJNBQXGX3MMFRGK3FMON2WE2TFMN2F65DZOBS2YSLTON2WKQ3PNVWWK3TUUZ2G64DJMNZZJAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWTTIOJYHEZDGNMCUR2HS4DFUVUXG43VMWSXMYLMOVS2UMJZGUZDCNZUHAZDFAVEOR4XAZNFNRQWEZLMUV3GC3DVMWVDCNJYGAZDQNRQGUZIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZTKMRYHE3TSNRSGKTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you authored the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Fixed nodejs net$Socket.connect signatures

According to node.js docs, net$Socket.connect has three signatures:

connect(options: Object, connectListener?: Function): https://nodejs.org/dist/latest-v10.x/docs/api/net.html#net_socket_connect_options_connectlistener
connect(path: string, connectListener?: Function): https://nodejs.org/dist/latest-v10.x/docs/api/net.html#net_socket_connect_path_connectlistener
connect(port: number, host?: string, connectListener?: Function): https://nodejs.org/dist/latest-v10.x/docs/api/net.html#net_socket_connect_port_host_connectlistener

All three are returning socket itself, instead of void

Please describe Function as concrete function types


Remove isWsl flag for WSL.

Couple of months ago this code was introduced to fix the problem that @ivpavici had with WSL and starknet-hardhat-plugin. So now in utils.ts we have this code that is supposed to fix some issues with WSL:
/**
 * Adapts `url` by replacing localhost and <IP_ADDRESS> with `host.internal.docker`
 * @param url string representing the url to be adapted
 * @returns adapted url
 */
export function adaptUrl(url: string): string {
    if (process.platform === MACOS_PLATFORM || isWsl) {
        for (const protocol of ["http://", "https://", ""]) {
            for (const host of ["localhost", "<IP_ADDRESS>"]) {
                if (url === `${protocol}${host}`) {
                    return `${protocol}${DOCKER_HOST}`;
                }

                const prefix = `${protocol}${host}:`;
                if (url.startsWith(prefix)) {
                    return url.replace(prefix, `${protocol}${DOCKER_HOST}:`);
                }
            }
        }
    }

but it seems that currently, this code is causing a problem with running quick test:
npx hardhat test test/quick-test.ts
error:
       should work for a fresh deployment:
     StarknetPluginError: Could not perform call on getPublicKey.
Got ClientConnectorError while trying to access http://host.docker.internal:5050/feeder_gateway/call_contract?blockNumber=pending
      at StarknetContract.<anonymous> (node_modules/@shardlabs/starknet-hardhat-plugin/src/types.ts:602:19)
      at Generator.next (<anonymous>)
      at fulfilled (node_modules/@shardlabs/starknet-hardhat-plugin/dist/src/types.js:28:58)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)

so || isWsl in if the statment should be removed.

This is probably responsible: https://github.com/Shard-Labs/starknet-hardhat-plugin/pull/210


Custom filtering

Since https://dns.bebasid.com/login.html shows AGH login page I'm assuming you're using AGH. The custom client setting in AGH makes it trivial to provide customized filtering, eg
https://dns.bebasid.com/dns-query works just like it's now
https://dns.bebasid.com/dns-query/family enable safe search and parental control service,
https://dns.bebasid.com/dns-query/security only uses browsing security service,
https://dns.bebasid.com/dns-query/unfiltered doesn't use any filter
I give DoH examples because setting up the domain for DoT & DoQ would require a wildcard cert and it's way more annoying to set up with LetsEncrypt than a regular domain.
Granted, this is a really small niche, but setting it up for DoH only requires a few clicks, with no extra overhead.

This is a good idea, thank you for your suggestion!
We have already added unfiltered and family variant to filter NSFW
https://dns.bebasid.com/dns-query/family
and unfiltered variant
https://dns.bebasid.com/dns-query/unfiltered


HP Chromebook 13 G1: Script does nothing

Greetings friends,
Part of my job is to wipe Chromebooks using these scripts. However with this particular model I am having some trouble.
https://github.com/MrChromebox/scripts/assets/25714534/d5389ba9-5f90-40d0-9987-035997a4ded3
^as you can see when I try to install legacy firmware the script doesn't do anything and doesn't even give an error. Lamentably I'm not to familiar with the debugging options for these scripts. But I'd needed I can provide more system information.
Any idea as to what might be causing this to occur?

You haven't disabled WP(write-protect).
-- The quality of your thoughts will determine the quality of your life.
On Wednesday, October 25, 2023 at 02:52:07 PM MST, Martin<EMAIL_ADDRESS>wrote:

Greetings friends,
Part of my job is to wipe Chromebooks using these scripts. However with this particular model I am having some trouble.
https://github.com/MrChromebox/scripts/assets/25714534/d5389ba9-5f90-40d0-9987-035997a4ded3
^as you can see when I try to install legacy firmware the script doesn't do anything and doesn't even give an error. Lamentably I'm not to familiar with the debugging options for these scripts. But I'd needed I can provide more system information.
Any idea as to what might be causing this to occur?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

RW_LEGACY firmware is not supported for EOL devices; your terminal colors are causing the disabled/gray text to show up as white apparently.
Installing RW_LEGACY firmware doesn't have anything to do with wiping the device, so I'm curious what you are actually trying to do?

I gotcha, I didn't know that these were EOL. Looks like I'll have to try another way then.
You're right, I'm just using the firmware to boot a USB to wipe it. I could have been more clear about that

You're right, I'm just using the firmware to boot a USB to wipe it. I could have been more clear about that

and then what? A ChromeOS recovery USB will wipe it as well you know

Yes, the USB image that the company uses also collects system information and uploads it to a server so that the Chromebook can be inventoried

I see. Is ChromeOS kept on the device or is Linux/Windows installed?

closing due to inactivity / lack of reply


⚠ gorzdrav.org has degraded performance

In 37ed0e6, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 4793 ms

Resolved: gorzdrav.org performance has improved in 2faf246.


Fix sle12_node detection

The result of a knife search node is unstable, so slap in a sort to
have a predictable outcome.

+1


NullHandler doesn't bubble

The current implementation of NullHandler doesn't allow the handler to bubble, it doesn't care about the bubble attrbute at all.
Here's a use case of having the NullHandler to bubble :
I'm using MonologBundle and I configure it to have the same handlers for all symfony's environments. I still need to disable some handlers so I simply override the type to "null" in config_*.yml and expect them to be noop and bubble.
Anyway, it's weird that it behaves differently from all other handlers (I suppose all, I didn't check)
Let me know what you think about it :)

The point of the null handler is to suppress all log records, so if it bubbled it would just become a noop and might as well not be there. You could use a type group or something instead if you want a noop.


implement Log.withMdc for creating Log with MDC preset

On line 144 in the changed file, Log.scala, there was already a similar, albeit slightly different, method:
    def withMDC(mdc: Log.Mdc)(log: => Unit): Unit = {
      import Mdc.MdcOps
      mdc.context match {
        case None => log
        case Some(mdc) =>
          val backup = MDC.getCopyOfContextMap
          MDC.clear()
          mdc.toSortedMap foreach { case (k, v) => MDC.put(k, v) }
          log
          if (backup == null) MDC.clear() else MDC.setContextMap(backup)
      }
    }

I can't immediately discern whether that's for the same use case (as catered for in this MR) or another one. Can you elaborate, please? Perhaps some ScalaDoc-ing is warranted for these two? Or one of them should be deprecated?


PowerDistributingActor should use min SoP

What's needed?
Microgrid will expose min bounds for charge/discharge power soon.
After that we should update PowerDistributing algorithm to look at it.
Proposed solution
Implementation should be in old MOS repository, because in past we had this min bounds.
To be checked
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response

Blocking because we need a new version of the microgrid API service to be released for being able to merge this.

@sahas-subramanian-frequenz the min and max SoP bounds should be first exposed via the BatteryPool. Second step would also be to look at the bounds if someones sends a power request thats out of bounds.


supporting Documentation for samples

Where does one find the supporting documentation that describes how to locally test and deploy these samples?

Many of the README's will talk about their tests, though most of the tests in this repository are Integration tests.  Do you have a specific sample (or group of samples) your interested in?


On logout return to homepage

Given I am an logged in and on an interior page,
When I logout,
Then I should be redirected to the homepage.

You need to handle this on your end – this is app logic.

Oops wrong repo!


Chapter 8 page 283 Express Node

Working on the expressapp.mjs :
The CURL command for the terminal is not working anymore.
we set up all the middleware -> then we set up a route object and set up the middleware routes -> then we want to test our POST method with curl, but its not working as intended.
This is the curl code we should use:
curl --header "Content-Type: application/json" --request POST
 --data `{"userid":"1","message":"hello"}` "http://localhost:8000/c"

this error message in the terminal output:
userid:1: command not found
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information

note: im running my express Node server on another terminal. The CURL worked for a previous section of the chapter where I also had to test a POST url request.

Your curl command is broken. Your sample is actually written as two lines instead of one. It needs to be a single line.

Excuse me for that, I broke the command in multiple lines as it was printed on page 269, but actually i am using it in one line, the previous example with node but without express was working with the curl command as intended, just for the express example its not working.

yes, the route http://localhost:8000/a leads me to the route "/a" as intended, in the browser. My server is running on a second terminal, so im sure the server is running.

I have also tried to change the package.json file to start the expressApp.mjs with npm start, so im 100% the server is running, as any change even restarts the server.


[BUG] User Profile APIs not working

GET /user/profile is used to fetch the UserProfile associated with the logged in user. But it is fetching the details of the User, instead of the details of UserProfile.

POST /user/profile is used to edit the UserProfile of the logged in user. But it is not updating the UserProfile

Notes:

For more details regarding the API, check this
Here UserProfile is the extended User model
The code associated with this is in develop branch of this repo.

Solved in #20


remove Ingress api version switch logic

This PR removes the Ingres apiVersion switch logic.
Ingress from networking.k8s.io/v1 is available from Kubernetes v1.19 on.
v1.19 had it's EOL on 2021-10-28 (https://kubernetes.io/releases/patch-releases/#non-active-branch-history), therefore there is no need to longer support networking.k8s.io/v1beta1.
Contributing a Chart / update to an existing Chart

[x] Run helm lint on the chart dir.
[x] (Update) Bump the Chart.yaml version before merging, to release it as a new version.
[ ] (Update) If the PR includes new configurable parameters in the chart's values.yaml. Add documentation in the appropiate README.

Thx for your contribution @wkloucek!


Fix tests on nightly

Nightly has richer IO error kinds
Sorry about the extensive reformatting of the yml... editors and we haven't dropped a common config file :/

Sorry about the extensive reformatting of the yml... editors and we haven't dropped a common config file :/

It's fine, as long as it's readable I don't care.
It seems like this is failing the ensure_rm test now though.

I intended to make it work on both nightly and stable; the issue is just a new IOErrorKind that is only emitted on nightly, but tests need to check for it. I will fix.

Looks like that new kind has leaked into stable. This is an API break IMO. :/


Add Eigen

Hi Chad,
I'm hoping you'll let me add this FindEigen CMake module to the project. Eigen is stable and fast linear algebra library for C++, more information is included in my commit's message. Having the module included here will be useful for me, and hopefully someone else too!
Thanks for taking a look! Also, I'm happy to provide any further information on Eigen if required.

Thanks @chadmv!


v1.6 - SIGSEGV on libasyncProfiler.so ElfParser::parseFile

I am trying to run async-profiler from a host Linux on a docker container running a Java application:
Host:
$ uname -a
Linux nobeh13 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ perf version
perf version 5.0.21

Example Dockerfile:
FROM ubuntu:18.04

SHELL [ "/bin/bash", "-c" ]

RUN \
    apt-get update && \
    apt-get install -y openjdk-8-jdk-headless && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

RUN \
    groupadd --gid 1000 bnobakht && \
    useradd --uid 1000 --gid 1000 --shell /bin/bash bnobakht && \
    chown -R bnobakht:root /opt && \
    mkdir /app && \
    chown -R bnobakht:root /app

ENV APP_ROOT /app

COPY ./highcpu/target/highcpu.jar ${APP_ROOT}/highcpu.jar
COPY ./run-highcpu.sh ${APP_ROOT}
COPY ./run.sh ${APP_ROOT}
COPY ./profile.sh ${APP_ROOT}

USER bnobakht
WORKDIR ${APP_ROOT}
CMD [ "./run-highcpu.sh" ]

For the docker container, I've tried docker base images openjdk:8-jdk, ubuntu:19.04 and ubuntu:18.04 (just to rule out potential issue on perf_event_open versions).
The following is how async-profiler is run from the host:
$ docker top $(docker ps | grep highcpu |cut -d ' ' -f 1)
$ sudo /opt/async-profiler/profiler.sh -d 10 -e cpu -o collapsed -f ./perf.txt JPID

and how the docker container is run:
$ docker run -it --rm --security-opt=seccomp:unconfined --volume $(pwd)/perf:/perf:rw --volume /opt/async-profiler:/opt/async-profiler:rw

The following is the header of the core dump:
# JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10)
# Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libasyncProfiler.so+0x1d0c3]  ElfParser::parseFile(NativeCodeCache*, char const*, char const*, bool)+0x83

The hs_err log is attached.
What am I missing or could this be a bug though not sure in which layer?
highcpu-error-29-2019-09-27_21-56-26.log

I've committed the fix, please check it if works.
It looks strange though, that in your case a file could be successfully opened, but could not be mmap'ed. Have you edited hs_err.log? It misses mapped file names, and the problem seems to be caused by one of those files.

I also encountered that bug. I can confirm that it works again with the fix. Interestingly enough, this has worked with v1.5 in the past for me, but now does not work with v1.5 either (admittedly, I did an OS upgrade from Ubuntu 19.04 to 19.10 inbetween). With commit 78a83a31b2e3d22df6fff5653cd17e53d40d84d2, I can attach to my Java application running inside a docker container again (async-profiler is also fully contained in the container, using itimer mode)

@knittl Right, the bug existed since the beginning, but it looks like some recent OS changes actually triggered it.
I've created debug branch where the profiler prints an error on JVM's stderr whenever the problem happens - can you please try it and tell what the error is?

This line is printed 26 times in the target VM, when I try to attach the profiler (application and profiler both in same Docker image and running in the same container):
Failed to parse / of length -1: Cannot allocate memory

Async-profiler started with ./profiler.sh -d 1 -e itimer 1

@knittl Thank you for the details.
In hs_err.log provided by @nobeh there are also many lines with just "/" path in the memory map instead of the shared library names. What is also common in both cases is a docker container and Linux 5.x kernel. So, I guess this might be some "security feature" of a newer kernel. Will try to reproduce the problem on my side.

Right, it does not happen when attaching to a regular process outside of docker.
In case it helps, here is my docker version:
$ docker version
Client:
 Version:	17.12.0-ce
 API version:	1.35
 Go version:	go1.9.2
 Git commit:	c97c6d6
 Built:	Wed Dec 27 20:10:45 2017
 OS/Arch:	linux/amd64

Server:
 Engine:
  Version:	17.12.0-ce
  API version:	1.35 (minimum version 1.12)
  Go version:	go1.9.2
  Git commit:	c97c6d6
  Built:	Wed Dec 27 20:09:19 2017
  OS/Arch:	linux/amd64
  Experimental:	false

I found the problem, it appears to be Ubuntu/Linux bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843018
The above link suggests the workaround to downgrade kernel to 5.0.0-25-generic.
I added the diagnostic message in async-profiler and the paragraph in README, so let me close the issue. Hopefully the bug will be resolved on Linux side soon, as it affects many other projects, too.

I confirm that with a master branch build, it also started to work for me and I could generate a collapsed output with the following warning messages:
Could not parse symbols due to the OS bug
WARNING: Install JVM debug symbols to improve profile accuracy

The second is because I did not install -dbg package for JDK yet.
Thanks @apangin for the fix and @knittl for more details on why this is happening.


Version bug

And because no versions of flutter_paystack match >1.0.7 <2.0.0, syncfusion_flutter_datepicker >=24.1.47 is incompatible with flutter_paystack ^1.0.7.
So, because laundry depends on both flutter_paystack ^1.0.7 and syncfusion_flutter_datepicker ^24.2.4, version solving failed.
You can try the following suggestion to make the pubspec resolve:

Consider downgrading your constraint on syncfusion_flutter_datepicker: flutter pub add syncfusion_flutter_datepicker:^21.2.3

If he doesn't merge then do this.
1 - Fork the project.
2 - Upgrade dependences the way you want them to be in, eg http: ^1.2.1
3 - Inject the github package straight to your project by following below example 👇
 flutter_paystack:
   git:
      url: https://github.com/KarlMathuthu/flutter_paystack.git # Repo link from your profile
      ref: master # branch name

I hope this helps 😍


Not works in ASUS ROG GL552-VW

Hi
I tested this tool on ASUS ROG GL552-VW and this message printed while setting the threshold:
$ sudo ./bat -t 80
This program is most likely not compatible with your system. See
https://github.com/leveson/bat#disclaimer.

Other commands like -c or -s works correctly.
I have ubuntu 20.10 and here is the output of uname -a:
Linux mojighahar 5.8.0-55-generic #62-Ubuntu SMP Tue Jun 1 08:21:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Please inform me if any other data required for clearing this issue. (output of lshw , ...)

Run the following command and tell me if you get any output back.
sudo find /sys/ -name "charge_control*"

It didn't find anything.
I do some relative search and find it:
$ sudo find /sys/ -name "charge*"
/sys/bus/platform/drivers/charger-manager

Seems that it requires some extra kernel modules. Not?
If kernel upgrade may help, I can upgrade to ubuntu 21.04 and test it again.

Here is content of /sys/class/power_supply/BAT0 directory:
-rw-r--r-- 1 root root 4.0K Jun 12 21:44 alarm
-r--r--r-- 1 root root 4.0K Jun 12 09:53 capacity
-r--r--r-- 1 root root 4.0K Jun 12 21:44 capacity_level
-r--r--r-- 1 root root 4.0K Jun 12 21:44 cycle_count
lrwxrwxrwx 1 root root    0 Jun 12 21:44 device -> ../../../PNP0C0A:00
-r--r--r-- 1 root root 4.0K Jun 12 09:53 energy_full
-r--r--r-- 1 root root 4.0K Jun 12 09:53 energy_full_design
-r--r--r-- 1 root root 4.0K Jun 12 09:53 energy_now
drwxr-xr-x 3 root root    0 Jun 12 09:52 hwmon2
-r--r--r-- 1 root root 4.0K Jun 12 09:53 manufacturer
-r--r--r-- 1 root root 4.0K Jun 12 09:53 model_name
drwxr-xr-x 2 root root    0 Jun 12 21:33 power
-r--r--r-- 1 root root 4.0K Jun 12 09:53 power_now
-r--r--r-- 1 root root 4.0K Jun 12 09:53 present
-r--r--r-- 1 root root 4.0K Jun 12 09:53 serial_number
-r--r--r-- 1 root root 4.0K Jun 12 09:53 status
lrwxrwxrwx 1 root root    0 Jun 12 09:52 subsystem -> ../../../../../../../class/power_supply
-r--r--r-- 1 root root 4.0K Jun 12 09:53 technology
-r--r--r-- 1 root root 4.0K Jun 12 09:53 type
-rw-r--r-- 1 root root 4.0K Jun 12 09:52 uevent
-r--r--r-- 1 root root 4.0K Jun 12 09:53 voltage_min_design
-r--r--r-- 1 root root 4.0K Jun 12 09:53 voltage_now

Upgrading might help.


GPU requirement for running the ROSMonitoring

Hi, could you advise if following GPU is capable enough for running the ROSMonitoring?
Nvidia RTX A1000 GPU w/ 4GB RAM
Thanks in advance for your time and response.

No worries, happy to help. If you try ROSMonitoring and you have any other doubts or issues let me know!
Cheers,
Angelo


Yield delegation fails for class instance of async iterable

TS 2.3 RC
{
    const iterable: Iterable<number> = {
        [Symbol.iterator]: () => 1 as any as Iterator<number>
    }

    const asyncIterable: AsyncIterable<number> = {
        [Symbol.asyncIterator]: () => 1 as any as AsyncIterator<number>
    }

    class AsyncIterable2 implements AsyncIterable<number> {
        [Symbol.asyncIterator] = () => 1 as any as AsyncIterator<number>
    }

    const asyncIterable2 = new AsyncIterable2()

    const gen = async function*(): AsyncIterator<number> {
        yield 0;
        yield* [1]
        yield* iterable
        yield* asyncIterable
        yield* asyncIterable2 // Error: The type returned by the 'next()' method of an iterator must have a 'value' property.
    }

    gen()
}

I would expect asyncIterable2 to work, but it errors. See code comment above.
I'm using type assertions because the values don't matter so much, just trying to prove the types should fit together.

This is a duplicate of #14442.


Added my profile :)

A little refresher for me on how to create a pull request

@annahothai  try this year for Hacktoberfest and have a look at the updated repo and contribute.
HAPPY HACKING


Show deployments in Jira

Hi there,
We are using GitHub deployment api for our apps, and we've lots of stage environments.
It will be super-useful if deployments appear in Jira alongside with PR's, commits and branches. Is it possible?

+1

Is this related to the newer Deployment views in Jira? (https://support.atlassian.com/jira-software-cloud/docs/integrate-your-deployment-pipelines-with-jira/). There are integrations with some CI providers but not with GitHub Actions yet (other than using the API yourself).

Is this related to the newer Deployment views in Jira? (https://support.atlassian.com/jira-software-cloud/docs/integrate-your-deployment-pipelines-with-jira/). There are integrations with some CI providers but not with GitHub Actions yet (other than using the API yourself).

Hi @pznamensky. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
This is something we're actively working on at the moment. Stay tuned 😄

Glad to hear it!
Thank you!  :slightly_smiling_face:

@rachellerathbone Is that possible to update deployment info from Github actions? I tried to find the related documents but couldn't found the way to do it. Could you support me on this case?

Hi @pznamensky, GitHub Actions is now fully integrated with Jira, which means you can see your Builds and Deployments from GitHub in your Jira issues. You should've received an email from GitHub asking for a permissions review and once that's accepted, your CI/CD data will start flowing automatically into Jira when a Jira issue key is used on a commit message or branch name.
Please let us know if you have any issues.
Thank you,
Amanda.


docs: added CHARTER.md

As a member for the OpenJS foundation, we are required to have a well defined charter for the project.  I tried to pull it together based on the template they provide and our existing docs.
This is part of the onboarding process: https://github.com/openjs-foundation/project-onboarding/issues/15

Also, I just found this document in the node TCS repo: https://github.com/nodejs/TSC/blob/master/Applications/Express.md
Is there information from there we should pull into the new charter document?

@wesleytodd I don't see any more info that could be pulled from the TSC document. Would be nice to add some definitions in there though. Is this the document where we'd define roles and responsibilities like "Triage", "Contributor", "TSC", etc ?

Can I get atleast a few of our other TC members to take a look?  I would love to get approval from @dougwilson, @blakeembrey, @crandmck & @LinusU before merging (but I will accept just one or two approvals as meeting the threshold)!

I will read though it tonight

Is this the document where we'd define roles and responsibilities like "Triage", "Contributor", "TSC", etc ?

@fed135 I think it probably should be.  I will add those once we get the rest of the changes sorted out.

Alright, squashed the commits and will let this sit overnight and merge in the morning (approx 10 hours). I didn't change any wording, so I expect no objections 👍


Complex query criteria

Statement:
As a research student, my job is to collect data for making policy changes regarding the Hemp Industries. I am interested in analyzing the data based on specific criteria queries to notice trends, gain insight, prediction, optimization, and understanding data patterns.
Background:
This feature will require a back-end database to have basic C.R.U.D commands for the database to be able to query the data meeting the criteria of the users. The data needed to do this action is already provided from the project partner’s previous method of data storage.
Requirements:
-Web Browser
-Client/server API
-Database (Python, MySQL, DBMongo, …) with software Implemented C.R.U.D command.
-Take existing data from the Excel spreadsheet and import it into the database.
Dependencies:
-Front-End \ Back-End

DBMS
-Programming Language framework (Django, Nodejs………..)
-basic data manipulation of C.R.U.D

Definition of done
An implementation of a database that lets users perform complex queries with diverse criteria to meet their requirements. Also, it will be implemented for resilient, reliable, highly efficient data transactions in handling a high volume of data.

feedback:
put this in data viz layer, keep UI for data entry only


Is localization possible?

As you probably know you can use localization for the label of widgets in C++.  The output looks great, everything retains their "C++" Name: field!  This is just fantastic work!  I don't know the best localization methods in rust yet, nor much about how to do it.  I know the label would need to be some sort of mutable string, that can be set from a LANG.po file if that ${LANG/_*}.po file exists.  But I have only used C++ and shell for this type of thing.
This is what the fld file has:
i18n_type 1
i18n_include <libintl.h>
i18n_function gettext

OR
i18n_type 2
i18n_include <nl_types.h>
i18n_set 1

It may be better to do it from the rust fluid, perhaps?

It should be possible. FLUID just wraps the text ina gettext macro, which can be replaced with a Rust based macro from one of the i18n crates, which I also haven’t worked with so I don’t have any preferences.
I’ll take a look thru some of them.

Oh good idea!  Thank you for looking, I have not used any of the i18n crates, so I am sure whatever you find will work.  Thank you for looking into this.  It is so exciting to quickly build UI for Rust apps, having translations will make it even better!

I've published version 0.4.4. If you enable internalization in FLUID, it should prepend all labels with the tr! macro from the tr crate.
tr uses gettext-rs (C Wrapper) or gettext (rust reimplementation) and only requires initialization in the main.rs file:
#[macro_use]
extern crate tr;

fn main() {
    tr_init!("some path");
    // rest of the code
}

gettext-rs has build issues with window msvc, so to use the rust reimplementation, you would need to disable gettext-rs since it's the default for tr:
[dependencies]
tr = { version = "*", default-features=false, features=["gettext"] }

tr has its own ecosystem built on it with tools to extract strings and others to embed translation files with cargo etc.

I suppose I should have closed this already, sorry for the delay


Change getAuthorities to reduce number of executed SQL-Statements

Any time a user is retrieved using this class, the getAuthorities method is executed to retrieve all of the user's direct and indirect group memberships recursively.
As mentioned in #463 by my colleague @mwdb the number of SQL queries used to do this grows with the number of scopes assigned.
As the methods are called very frequently, this highly increases the load on the database. With this PR the number of SQL queries is reduced. According to our performance tests this highly increases the performance of the database.

Coverage decreased (-0.2%) to 84.517% when pulling 50dbd177fdcdd97e782924e062e8fe6569546f0a on tack-sap:sql-performance into 03aaa42f4e0950fb730e88348b95991f7553f79d on cloudfoundry:develop.

Thank you for the PR
It appears that we have a coverage decrease here. Meaning, not all lines of code added were exercised by the tests. We prefer code changes that are test driven. https://en.wikipedia.org/wiki/Test-driven_development
It may take longer to merge a PR, when we have to write supplementary tests or try to figure out what lines are not tested in this feature.

Hi Filip,
With the added test all lines of the methods we changed are covered by tests (according to our tooling).
When we tried to cover all lines, we found, that the return in the catch-block was never executed by tests. The catch-block itself is taken from the original coding, but is empty there. We added the return because our guidelines do not allow empty catch-blocks.
The catch-block is never executed, because queryForList does not throw this exception on an empty result, but returns an empty list (which is why the catch was never used in the previous coding as well).
As there is no other catch, we removed then the try-catch from the method.

Coverage decreased (-0.08%) to 84.665% when pulling 21be2df00f0108bd9610e5fae7e6b8da716314dd on tack-sap:sql-performance into 03aaa42f4e0950fb730e88348b95991f7553f79d on cloudfoundry:develop.

Coverage decreased (-0.08%) to 84.665% when pulling 21be2df00f0108bd9610e5fae7e6b8da716314dd on tack-sap:sql-performance into 03aaa42f4e0950fb730e88348b95991f7553f79d on cloudfoundry:develop.

Coverage decreased (-0.08%) to 84.665% when pulling 21be2df00f0108bd9610e5fae7e6b8da716314dd on tack-sap:sql-performance into 03aaa42f4e0950fb730e88348b95991f7553f79d on cloudfoundry:develop.

Is there a reason why this PR is still "unscheduled" after such a long time?
All checks have been passed, the coverage report says "coverage increased", there a no conflicts and I got no feedback left, that some further action is required (as the feedback I got was already addressed with the second commit)..
Is there anything I can do for this PR to get processed?

We will get this scheduled for UAA 4.0

@tack-sap Thank you for your contribution. It is running through.
I corrected your test. In a Test Driven Development process, the test should fail before a change is applied, and succeed after. Your test succeeded before and after, thus the test does not detect a change in the code base.
I have modified your test - there is a neat trick using the Mockito.spy proxy
https://github.com/cloudfoundry/uaa/commit/eb0a970283cb8bf0ebf0d0b97308c73ca816ca5d

Merged via https://github.com/cloudfoundry/uaa/commit/d4a9baae31f97238cc0e02154e55816ed3f3854c


Revamp the feedback page according to the existing theme of website.

Describe the bug
The current feedback page is little off theme.
Expected behavior
User expects a feedback page according to the theme of website as given below.
Screenshots (Mandatory)

Additional Context (Mandatory )
Are you contributing under any open-source program ?
Yes I am contributing to jwoc 2024

@apu52 I would like to contribute to this issue under jwoc 2024

@Aashi19234 thank you for raising the issue but on  Which feedback page you want to work on as I can't see any feedback page...can you please share some proper SS

@apu52 Here is the feedback page i am talking about,

@Aashi19234 You are assigned. you just have 1 day to complete this issue


add link to resources and Windows instructions

Should links to Mac and Linux also be added also to the README?

is it possible to have Blocks with hyperlinks in rst:

Installation requires >= 80 GB of disk space. See details here

> Installation requires >= 80 GB of disk space. See details [here ](https://github.com/MannLabs/CKG/blob/master/docs/source/system_requirements.rst)

vs
..

    Installation requires >= 80 GB of disk space. See details `here <docs/source/system_requirements.rst>`_

where does this link point to? /_static/images/banner.jpg Should it be removed?

Thank you @enryH!
The steps to install CKG in MacOS and Linux are described in the Intro, in principle only the Windows installation requires different steps.

Thank you @enryH!
The steps to install CKG in MacOS and Linux are described in the Intro, in principle only the Windows installation requires different steps.


Training is failed without any model built

System Information (please complete the following information):

Model Builder or CLI Version:
Visual Studio Version (if applicable):

Describe the bug

On which page of the tutorial did you run into an issue (URL):
Clear description of the problem:

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hello @Akash01nov,
Training failed without any model built happened most of the time  if your data is very small or the training time is not enough .
could you try it larger dataset  or increasing  training time ?

No customer response for log time , if you hit the issues let us know we will reopen it .
Thanks.


Link from react-router or routeActions.push from react-redux-router ?

Hi guys,
I use it and  I was wondering, should I use Link component from react-router or routerActions.push from react-redux-router to make a link ?
I don't know very well how those tools works, but it seems to be equivalent, isn't it ?
Thanks for your very helpful work

You should use the Link component. The normal router tools all work as expected.


BlazorWebAppOidc sample: incorrect CookieOidcRefresher implementation

Description
CookieOidcRefresher expects an ID token from the token endpoint. This seems wrong, based on the spec, the Duende implementation and the fact that it always fails in my app.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/blazor-web-app-with-oidc?view=aspnetcore-8.0&pivots=without-bff-pattern
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/blazor-web-app-with-oidc.md
Document ID
c3346d3a-346b-8db4-2650-ec044b3f0dd9
Article author
@guardrex
Related Issues

It looks like we need to determine whether the refresh token is really an ID token before indiscriminately reading claims from it. If it's not an ID token, we should probably just continue to use the old claims stored in the cookie. https://github.com/dotnet/aspnetcore/issues/58826 is also related to getting the right claims on refresh, but that's focused on refreshing claims from the /userinfo endpoint if it's enabled.

So ... @halter73 ... do you want to transfer this issue to the PU repo, or should @albi005 open a new PU issue on this?

In the meantime, I think it would make sense to add a comment to the sample/docs noting that the refresh implementation might need to be updated depending on the Identity Provider.

I can add whatever makes sense to add, but it's best if one of you who understands what the text should say write it in a comment here for publication, and then I'll edit it for style+grammar and place it in the article. If it should go in under a heading to help surface it in the article, give me proposed heading text as well.

Token refresh
The sample includes code in CookieOidcRefresher.cs showing how to update the user's claims automatically when they expire. The current implementation expects to receive an ID token from the token endpoint in exchange for the refresh token. This ID token is then used to overwrite the user's claims.
The sample implementation doesn't include code for requesting claims from the UserInfo endpoint on token refresh. Refer to the following issue for an example on how to do that: https://github.com/dotnet/aspnetcore/issues/58826#issuecomment-2492738142

[!NOTE]
Some identity providers only return an access token when using a refresh token^1. You should handle this as needed.

## Token refresh

The sample includes code in `CookieOidcRefresher.cs` showing how to update the user's claims automatically when they expire. The current implementation expects to receive an ID token from the token endpoint in exchange for the refresh token. This ID token is then used to overwrite the user's claims.

The sample implementation doesn't include code for requesting claims from the UserInfo endpoint on token refresh. Refer to the following issue for an example on how to do that: https://github.com/dotnet/aspnetcore/issues/58826#issuecomment-2492738142

> [!NOTE]
> Some identity providers only return an access token when using a refresh token[^1]. You should handle this as needed.

[^1]: https://openid.net/specs/openid-connect-core-1_0.html#RefreshTokenResponse

I think this should go above the "Cryptographic nonce" section.
@halter73 could you please check if this is correct?

Great ... I'm going to go ahead and update the PR with language closer to this.
We can take up the discussion over there on https://github.com/dotnet/AspNetCore.Docs/pull/34315.


Add optional timer to !day -> !vote

Add a way that you can specify a number of minutes when you start the !day phase
After N-1 minutes the bot will post a 1-minute warning to the players (or to the text chat if we add knowledge of the text chat)
After N minutes the bot will auto-run the !vote command

I think I'd want:

ability to do this independently of !day if desired
ability to auto run !vote or not
The main feature is the timer and warning message


Image saving in local storage.

Hello,
I am trying to save the image in local storage using a path. But facing some issues. I was using your code but seems like I am unable to solve these errors.

Can you show me the full code please?

I have not done anything extra. It is written (in comment) inside the
example's void renderAndDisplayImage() function of your package.
https://pub.dev/packages/flutter_painter/example
[image: image.png]
On Wed, Feb 9, 2022 at 6:56 PM omarhurani @.***> wrote:

Can you show me the full code please?
—
Reply to this email directly, view it on GitHub
https://github.com/omarhurani/flutter_painter/issues/20#issuecomment-1033732350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHWYARX5JJLSK5YG7SEWI3U2JP6TANCNFSM5N4Q34CQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards,
Ibrahim Hossen Rahad
Phone: 01792-530023
Email: @.***

Yes, you'll just need to make the function asynchronous and await the future.
void renderAndSaveImage() async {
    if (backgroundImage == null) return;
    final backgroundImageSize = Size(
        backgroundImage!.width.toDouble(), backgroundImage!.height.toDouble());

    // Render the image
    // Returns a [ui.Image] object, convert to to byte data and then to Uint8List
    final image = await controller.renderImage(backgroundImageSize);
    final byteData = await image.pngBytes;

    // Save image to the temporary directory.
    final file = File('${(await getTemporaryDirectory()).path}/img.png');
    await file.writeAsBytes(byteData.buffer.asUint8List(byteData.offsetInBytes, byteData.lengthInBytes));
}

Thanks for the quick response.
But unfortunately, I can not find the saved photo anywhere. I doubt it is
not working.
On Wed, Feb 9, 2022 at 9:58 PM omarhurani @.***> wrote:

Yes, you'll just need to make the function asynchronous and await the
future.
void renderAndSaveImage() async {
if (backgroundImage == null) return;
final backgroundImageSize = Size(
backgroundImage!.width.toDouble(), backgroundImage!.height.toDouble());
// Render the image
// Returns a [ui.Image] object, convert to to byte data and then to Uint8List
final image = await controller.renderImage(backgroundImageSize);
final byteData = await image.pngBytes;

// Save image to the temporary directory.
final file = File('${(await getTemporaryDirectory()).path}/img.png');
await file.writeAsBytes(byteData.buffer.asUint8List(byteData.offsetInBytes, byteData.lengthInBytes));

}
—
Reply to this email directly, view it on GitHub
https://github.com/omarhurani/flutter_painter/issues/20#issuecomment-1033915640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHWYASRCJE62SQJHC74DNTU2KFITANCNFSM5N4Q34CQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards,
Ibrahim Hossen Rahad
Phone: 01792-530023
Email: @.***

Well getTemporaryDirectory gets the cache directory of the device. Check out the path provider documentation to see which directory suits you better.

I used ExternalStorageDirectory() and it worked for me. Thanks for your
help. Your package was really helpful.
On Thu, Feb 10, 2022, 00:11 omarhurani @.***> wrote:

Well getTemporaryDirectory gets the cache directory of the device. Check
out the path provider documentation
https://pub.dev/documentation/path_provider/latest/path_provider/path_provider-library.html
to see which directory suits you better.
—
Reply to this email directly, view it on GitHub
https://github.com/omarhurani/flutter_painter/issues/20#issuecomment-1034053134,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASHWYAQMGUN3QSS74TSTJDTU2KU6FANCNFSM5N4Q34CQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Add __quantum__rt__device_init(int8_t *, int8_t *, int8_t *)

We currently lower the device name, kwargs, and library with 3 __quantum__rt__device(key, spec) calls. The runtime initializes the targeted device after getting the device name and kwargs at the third call:
__quantum__rt__device("rtd_name", "lightning.qubit");
__quantum__rt__device("rtd_kwargs", "{...}");
__quantum__rt__device("rtd_lib", "rtd_lightning.so"); <--- init device

This PR reduces the number of these device calls into 1 single __quantum__rt__device_init("rtd_lib", "rtd_name", "rtd_kwargs") call and deprecates the __quantum__rt__device instruction. We also add __quantum__rt__device_release() to release the initialized device by request (this'll be used in the async support).

@maliasadi what is the context behind this change?

@maliasadi what is the context behind this change?

@josh146 First, it removes 2 instructions calls from the generated LLVM IR with hardcoding the device triple (name, library, kwargs) from the frontend to the backend in one single rt__device_init call instead of 3 rt__device calls.
// Before this change, (calls should be in some order: name->kwargs->lib)
__quantum__rt__device("rtd_name", "LightningQubit");
__quantum__rt__device("rtd_kwargs", "{...}");
__quantum__rt__device("rtd_lib", "rtd_lightning.so"); <--- init device

// Now,
__quantum__rt__device_init("rtd_lightning.so", LightningQubit", "{...}");

Second, it lets runtime to initialize device instances without keeping record of any partial information about that device. Before this change, the runtime had to store partial information about name and kwargs of the device before initializing it. But now, the runtime is able to initialize the device without necessarily storing partial device info or implying any specific order to define these specifications in the IR and the runtime. This PR is related to #381 and will help better scope the lifetime of device instances.

thanks :)


nixops_unstable: 2023-10-26 -> 2023-12-17

Description of changes
Fix #278250

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@k900 @roberth @AmineChikhaoui

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/88

Thank you!


New PR to test SignCLA at 2017-12-05 10:11:27.615172854 -0800 PST m=+73.073677022

Body of PR

corp-pass-fork-staging: test succeeded


Change the new/updated/preview tags for samples

Describe the bug

The new/updated/preview designations haven't been updated in a little while. Feels like it's time to make a pass through the samples and update their status.
@stmoy, I would love your help in wrangling this information and filling out the New state column. (If the sample shouldn't appear on the What's New page, let's call its New state None.)

Sample name
Current state
New state

AnimatedVisualPlayer
New

Animation interop
New

ColorPaletteResources
New

CommandBarFlyout
New
Updated

Compact Sizing
New

Connected Animation
New

DataGrid
New

DropDownButton
New

Easing Functions
New

Implicit Transitions
New

ItemsReater
New
New

Page transitions
New

SplitButton
New

StandardUICommand
New
Updated

TeachingTip
New

Theme Transitions
New

ToggleSplitButton
New

WebView
New

XamlUICommand
New

ComboBox
Updated

CommandBar
Updated

ListView
Updated

MenuBar
Updated
Updated

NavigationView
Updated
Updated

RichEditBox
Updated

TreeView
Updated

ScrollViewer (preview)
Preview
Preview

Acrylic
None
Updated

Thanks for writing this up. I agree that we should update the new/updated/preview designations. A few thoughts:

TeachingTip

I'd argue that TeachingTip is still relatively "new" since it just came out last release.
We've also got a few new controls/features coming down the pipe (TabView, corner radius) which will have New pages associated with them. I think we should aim to update the designations at the same time the next WinUI 2.X package comes out. Is that an ok timeframe?

Timeframe sounds good. I would like us to release a new Gallery version to the store by end of September, which I believe gives us a few weeks to update the app's WinUI package.
Will corner radius get its own page or just be incorporated into the appearance of the existing samples?

Current POR is that @kikisaints will add a page for CornerRadius that links out to the theme tool, same as the ColorPaletteResources page.

Timeframe sounds good. I would like us to release a new Gallery version to the store by end of September, which I believe gives us a few weeks to update the app's WinUI package.

I'm thinking about releasing one sooner than that given all of the great work that @chingucoding has been doing. (Plus, the Acrylic page is crashing so that's another motivator >_> )

Sooner is also great. I'm hoping to be able to include a fix for #141, which is also gated on a new WinUI package.
And huge thanks to @chingucoding for making so many improvements!


Be able to assign RPC port

So I have a particular use case in which I am running amman in a docker container and spawning it to do testing of my contracts and apis via heroku. I am able to make the container work however, heroku does not respect the docker EXPOSE keywords and requires me to inject a port for the app to listen to. solana-test-validator has the --rpc-port command and it seems like it would work for this. I could add this to the project myself via a validator mapping but I would like to have feedback as another way would be to add extra arguments. Ex: amman start --extra="--rpc-port=8080"

Ah ok .. that requires a change in amman and amman-client.
Basically making this configurable on start and being able to override LOCALHOST.
If you want please take a stab at adding this. I'd prefer this as a property on the validator config (vs. a command line arg), but we if you need this then we can add an arg that can override that config value per amman start.
That could be as simple as amman start --rpc-port=8080 or maybe amman start --rpc-url=http://<some url>:<some-port. (I don't like the --extra way too much).

Yeah thats what I thought. Np! I had expected to do it myself as it is such a specific use-case.

Yes, you can assign an RPC port to the Solana test validator using the --rpc-port flag. To specify the port number, simply add --rpc-port=<port number> to the command line when starting the validator. For example, to start the validator on port 8080, you would run the following command:
solana-test-validator --rpc-port=8080

If you want to pass extra arguments to the solana-test-validator command, you can use the -- separator to separate the arguments for the validator from the arguments for the solana-test-validator command. For example, to start the validator on port 8080 and pass an extra argument to the validator, you would run the following command:
solana-test-validator --rpc-port=8080 -- --extra="--my-extra-argument"

I hope this helps! Let me know if you have any further questions.


ResponseEntityExceptionHandler with @ControllerAdvice is Ignored When Using spring-modulith-observability

Issue: ResponseEntityExceptionHandler with @ControllerAdvice is Ignored When Using spring-modulith-observability
Description
When spring-modulith-observability is included in the project dependencies, a custom class that extends ResponseEntityExceptionHandler and is annotated with @ControllerAdvice fails to catch exceptions as expected.
It appears that the exception handling flow is being disrupted, and the @ControllerAdvice is completely ignored.
From initial investigation, the issue seems to be related to the ModuleEntryInterceptor class. The interceptor wraps the controller method invocation (MethodInvocation.proceed()), and it appears to interfere with Spring MVC’s exception handling mechanism.
Steps to Reproduce
1.	Include spring-modulith-observability in your dependencies.
2.	Create a class that extends ResponseEntityExceptionHandler and annotate it with @ControllerAdvice.
3.	Throw an exception (e.g., RuntimeException) from a controller method.
4.	Observe that the exception is not handled by the custom exception handler.

Expected Behavior
•	The @ControllerAdvice class that extends ResponseEntityExceptionHandler should catch exceptions and provide the appropriate response.

Actual Behavior
•	The @ControllerAdvice is ignored, and exceptions are not caught by the custom exception handler.

Suspected Cause
•	The ModuleEntryInterceptor from spring-modulith-observability appears to intercept the method invocation and disrupt exception propagation.
•	It does not properly propagate the exceptions back to Spring MVC’s error handling flow, potentially causing the issue.

Environment
•	Spring Boot Version: 3.3.x
•	Spring Modulith Observability Version: 1.2.4
•	Java Version: 21

This seems to duplicate GH-933 as ResponseEntityExceptionHandler implements an interface. Thus, a JDK proxy is created and the annotations on the actual class are not visible anymore. As a workaround, would you mind not making the class public? If a type is not part of a module's API it is not decorated anyway, and I'd argue that a REEH doesn't need to be a type exposed by a module.
For future reference, it would be appreciated if you provided a minimal reproducer instead of instructions on how to create a sample.


move from travis to github action

add readme info
add specific failure if user has old version of python

https://github.com/tableau/tabcmd/issues/44


If ubos-admin does not exist, fall back from UBOS Driver to manual Driver

Maybe with a nice warning message.
Test when NodeManager is first accessed, and return a different NodeManager instead

I think I disagree with myself here. Let's simply not run anything if it can't run, that's less confusing.

Done with c857a62522c94428aa6a6c4c252dfe3635016440 and fb9aa50899e28d3fc8560ae32666934711d4eeea.


Remove .transform(null) in BaseImageRecordReader

What changes were proposed in this pull request?
In hasNext() there were multiple calls to imageTransform.transform(null). From reviewing the code and our transforms, I could not find any benefits to doing so. Removing this code.
How was this patch tested?
Ran unit tests and runs on my local.

I think this was done for ShowImageTransform? But how about we just fix ShowImageTransform and avoid all of these calls to the transformer?

If we don't care that the process doesn't terminate when processing is
done, then we can remove that, sure.

If we do care, we'll need another mechanism to close the Frame that displays images in ShowImageTransform, for example.

We could have a NullOpShowImageTransform variant that we'd call on this ?

The issue is not the transform itself, but the call to some method of the transform in RecordReader.hasNext(). It's supposed to be idempotent method.
One solution I see is forcing users to call some ImageTransform.close() method (or try-with-resources)...

@AlexDBlack IIRC, you had a similar issue in Arbiter or some such not terminating because of opened windows. What did you end up doing in that case?


Bug in ArkPlanner

I think Device, Integrated Device, and so on need not be displayed.
Correct behavior(Original ArkPlanner)

This is a by-design behavior: The new planner now doesn't select Large demand of LMD to be true by default, but in the old ArkPlanner it is selected by default. With different settings, the planner will indeed produce different results.
Closing due to not able to reproduce; feel free to reopen if the issue occurs again ;)


Overlapping edges labels hidden

Describe the bug
When there are two edges in the graph, when two overlaps each other and both of them has labels, the edge which is last added, only that label is visible
Your Example Website or App
https://codesandbox.io/s/youthful-bash-3oqdm0?file=/src/app.tsx
Steps to Reproduce the Bug or Issue

Visit the sandbox, the bug is visible

Expected behavior
As a user, I need to see both the labels when the edges overlap. Or atleast have an option to control the opacity and make both visible.
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

you can set text area fill attr as transparent,like this:
graph.addEdge({
  source: rect2,
  target: rect1,
  label: "world",
  attrs: {
    rect: {
      fill: 'transparent'
    }
  }
});


added separate file for getcurrency function.

Have you tested in a different folder after removing the currency function in a new file?
__        Summary: ❓ I have a question

Yes I have tested .Its working fine.


Programmatically moving between Stages

If I interpret the documentation correctly, you can set the active stage to the next or previous stage.
But what if I have a condition after a stage? I can't set the stage (programmatically within my external flow) without replicating the condition logic.
How about having an option to set the current stage as complete, then the BPF can process the condition to determine the next stage?

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

ID: 8a13ad7f-5f83-d1d4-0d33-0a7842aea1de
Version Independent ID: 792cbd63-a2d0-5793-bb62-55835392b977
Content: Work with business process flows using code - Power Automate
Content Source: articles/developer/business-process-flows-code.md
Service: flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@woodyarray Thanks for your suggestion. The product team uses https://powerusers.microsoft.com/t5/Power-Automate-Ideas/idb-p/MPAIdeas to track ideas. Kindly consider making your suggestion there. Thanks!


odo dev fails if multiple deployments exist for a component

Example devfile used for the project https://github.com/odo-devfiles/nodejs-ex:

 devfile.yaml
commands:
- exec:
    commandLine: npm install
    component: runtime
    group:
      isDefault: true
      kind: build
    workingDir: ${PROJECT_SOURCE}
  id: install
- exec:
    commandLine: npm start
    component: runtime
    group:
      isDefault: true
      kind: run
    workingDir: ${PROJECT_SOURCE}
  id: run
- exec:
    commandLine: npm run debug
    component: runtime
    group:
      isDefault: true
      kind: debug
    workingDir: ${PROJECT_SOURCE}
  id: debug
- exec:
    commandLine: npm test
    component: runtime
    group:
      isDefault: true
      kind: test
    workingDir: ${PROJECT_SOURCE}
  id: test
components:
- container:
    endpoints:
    - name: http-3000
      targetPort: 3000
    image: registry.access.redhat.com/ubi8/nodejs-14:latest
    memoryLimit: 1024Mi
    mountSources: true
    command: ["tail"]
    args: ["-f", "/dev/null"]
  name: runtime
- name: infinitepodtwo
  kubernetes:
    inlined: |
      apiVersion: v1
      kind: Pod
      metadata:
        name: infinitepodtwo
      spec:
        containers:
          - name: blah
            image: docker.io/dharmit/infiniteloop
- name: infinitepodone
  kubernetes:
    inlined: |
      apiVersion: v1
      kind: Pod
      metadata:
        name: infinitepodone
      spec:
        containers:
          - name: blah
            image: docker.io/dharmit/infiniteloop
- name: mydeployment
  kubernetes:
    inlined: |
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: infinitedeployment
      spec:
        replicas: 1
        selector:
          matchLabels:
            app: infinite
        template:
          metadata:
            labels:
              app: infinite
          spec:
            containers:
            - name: blah
              image: docker.io/dharmit/infiniteloop
metadata:
  description: Stack with Node.js 14
  displayName: Node.js Runtime
  icon: https://nodejs.org/static/images/logos/nodejs-new-pantone-black.svg
  language: javascript
  name: node
  projectType: nodejs
  tags:
  - NodeJS
  - Express
  - ubi8
  version: 1.0.1
schemaVersion: 2.0.0
starterProjects:
- git:
    remotes:
      origin: https://github.com/odo-devfiles/nodejs-ex.git
  name: nodejs-starter

First pass of odo dev works just fine. Modify server.js and save the file. odo dev which is watching the current working directory fails with:
$ odo dev
  __
 /  \__     Developing using the node Devfile
 \__/  \    Namespace: myproject
 /  \__/    odo version: v3.0.0-alpha2
 \__/

↪ Deploying to the cluster in developer mode
 ✓  Searching resource in cluster
 ✓  Creating kind Pod [13ms]
 ✓  Searching resource in cluster
 ✓  Creating kind Pod [15ms]
 ✓  Searching resource in cluster
 ✓  Creating kind Deployment [13ms]
 ✓  Waiting for Kubernetes resources [3s]
 ✓  Syncing files into the container [158ms]
 ✓  Executing install command "npm install" on container "runtime" [2s]

Your application is now running on the cluster
 - Forwarding from <IP_ADDRESS>:40001 -> 3000

Watching for changes in the current directory /home/dshah/src/nodejs-ex
Press Ctrl+c to exit `odo dev` and delete resources from the cluster

File /home/dshah/src/nodejs-ex/server.js changed
Pushing files...

Error occurred on Push - watch command was unable to push component: failed to create the component: unable to determine if component node exists: multiple Deployments exist for the selector: app.kubernetes.io/instance=node,app.kubernetes.io/managed-by=odo,app.kubernetes.io/part-of=app,odo.dev/mode=Dev. Only one must be present

/kind bug
/area dev

Test with #5923

@dharmit Can you try to reproduce this issue?

I used #5923 and the devfile I have mentioned in issue description with the nodejs-ex project. Below is the output from two such runs.
$ odo dev
  __
 /  \__     Developing using the node Devfile
 \__/  \    Namespace: myproject
 /  \__/    odo version: v3.0.0-beta1
 \__/

↪ Deploying to the cluster in developer mode
 ✓  Creating kind Deployment [14ms]
 ✓  Creating kind Pod [9ms]
 ✓  Creating kind Pod [33ms]
 ✓  Waiting for Kubernetes resources [14s]
 ✓  Syncing files into the container [200ms]
 ✓  Building your application in container on cluster (command: install) [4s]
 •  Executing the application (command: run)  ...
 - Forwarding from <IP_ADDRESS>:40001 -> 3000

Your application is now running on the cluster

Watching for changes in the current directory /home/dshah/src/nodejs-ex
Press Ctrl+c to exit `odo dev` and delete resources from the cluster

File /home/dshah/src/nodejs-ex/server.js changed
Pushing files...

 ✓  Creating kind Pod [10ms]
 ✓  Creating kind Pod [10ms]
 ✓  Creating kind Deployment [12ms]
 ✗  Waiting for Kubernetes resources [66ms]
Error occurred on Push - watch command was unable to push component: unable to create or update component: unable to create PVC: unable to create PVC: persistentvolumeclaims "odo-projects-nodejs-app" already exists

^C

Cancelling deployment.
This is non-preemptive operation, it will wait for other tasks to finish first

Cleaning resources, please wait
 ✗  Executing the application (command: run) [2m]
Failed to delete the "Pod" resource: infinitepodtwo
Failed to delete the "Pod" resource: infinitepodone
Failed to delete the "Deployment" resource: infinitedeployment

@dharmit what's the status on this? Can you still reproduce it?


Master

merge pull request

@pooja07541A0240  This PR appears to duplicate changes that were made and merged months ago; it introduces conflicts as well. I'm closing this request. If you'd like to contribute to this repo, please do you work in the dev branch and PR to stage; nothing gets directly PR'd to master.
cc: @macdonst @hirenoble