Update deprecated 'set-output' of GitHub Actions

This PR updates the calls to 'set-output' using the new format to set outputs on the GitHub Actions workflows. More info in: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

LGTM


Netty autoread should be enabled after response is completed

Netty autoread should be enabled after the previous response is completed. It is otherwise possible to run into a race condition with the next response.

Currently being enabled after receiving the last event related to a request, but this is too early and under heavy load a race condition may occur.

PR #823


Disable image stretching in TensorBoard

Example of how it looks today, and an example of how it would look without stretching.
TensorBoard's CSS for image summaries stretches the image to 100% which makes it hard to interpret images, especially with pooling operations like in VGG-like neural networks.
Also, considering datasets as CIFAR have images of 32x32, the large amount of stretching leads to very blurry images. Could we either have control of the number of columns in a pane, or disable image stretching altogether?

What browser are you using? What happens if you tune the interpolation algorithm in the CSS? Those screenshots look like nearest neighbor, and it does kind of feel like it's losing something when resized.
Disabling image stretching is probably not something we would consider. Perhaps instead we should provide a choice of image interpolation algorithms.
cc: @dandelionmane

The latest version of TensorBoard has a button attached to every image that lets you view it as true pixel size. Will that solve the need for you?
Also, +1 for Justine's question about which browser you're using. On chrome by default it doesn't interpolate, just increases size, so it will become blocky rather than blurry. Maybe we don't have the right CSS setting for your browser, though.

Yes, screenshots are from Chrome.
The button to show the actual size is nice, but IMO it would be better if the stretching didn't occur, or at least was controlled with max-height: 50vh or something because width: 100% really goes bonkers with height: auto. For example, this slice of a spectrogram stretches from 62x672 to 340x3685 pixels on my 1080p display in Chrome.
Could we at least control the number of columns or something with a slider?

I retract my previous comment about stretching algorithm. I failed to notice the two screenshots were at different steps, which explains why they looked so different.
It's been really difficult for us to find a way to make the images dashboard fit all use cases. For example, the mnist tutorial has really tiny images, so we'd naturally want to stretch those.
Your suggestion of vh is actually a really interesting idea that we hadn't considered. Especially if we can make the number of card columns increase when max-height: 100vh kicks in. However this could potentially make the card title less useful in your case, since it's overflow hidden.

3f6404f2069a1baf795cc618e700dd43dcbeeb15 limits the default max height of images to 800px. One can always view true pixel size (the full image) if they desire, so I am closing this issue.


Portfolio Mobile First

Day 3 project where we have to create a toolbar and headline sections referring to Figma's template.

Added an index.html and style.css
Added two sections in the HTML page for the toolbar and headline
Added breakpoints in style with minimum screen sizes of 375px for mobile and 768px for desktop.

Thank you so much for the reviews to @taldr27 and @Owusu-Desmond . It was of great help. :)


Multiple files upload have all the same name

Version 2.10.1
Windows 7
I can simulate the issue easily

When I select several files in Windows Explorer and then drag and drop it on RocketChat conversation there is all files with same file name.

Duplicate of RocketChat/Rocket.Chat#7291


rad group switch output

Description
rad cli group switch output to display success message when switching output to a group
Type of change

This pull request fixes a bug in Radius and has an approved issue (issue link required).

Fixes: #7395

UPDATE: I will look into the test. I did some manual testing but I didn't run tests locally as the change was insignificant... We live and learn.

Updated and tests running successfully locally.

You also need a rebase/merge with the main branch.

@rynowak hows this looking?
Let me know if you need anything else.

Th

@rynowak hows this looking? Let me know if you need anything else.

I'm merging this now. Thanks again.


Challenge http://www.freecodecamp.com/challenges/waypoint-create-a-bootstrap-button has an issue

Please tell us in detail here how we can make this challenge better.
Small typo:
Challenge reads: your button should have the test "like this photo";
I think it meant to read: your button should have the text "like this photo";

Thanks Thiago


modify CheckBlockIndex to newest

other modify are Park related function, we do not need it now.

I have upgrade the BlockIndexWorkComparator


After Deploy infinispan don't work correcrtly

Hello!
There is a question i have deployed infinispan
But have a lot of lags in console, can you tell me what the problem ?
It's freez on loading when you click on any tabs

as you see on screenshot
I send you my value file
# Default values for infinispan-helm-charts.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

images:
  # [USER] The container images for server pods.
  server: quay.io/infinispan/server:14.0
  initContainer: registry.access.redhat.com/ubi8-micro

deploy:
  # [USER] Specify the number of nodes in the cluster.
  replicas: 2

  clusterDomain: cluster.local

  container:
    extraJvmOpts: ""
    libraries: ""
    # [USER] Define custom environment variables using standard K8s format
    # env:
    #  - name: STANDARD_KEY
    #    value: standard value
    #  - name: CONFIG_MAP_KEY
    #    valueFrom:
    #      configMapKeyRef:
    #        name: special-config
    #        key: special.how
    #  - name: SECRET_KEY
    #    valueFrom:
    #      secretKeyRef:
    #        name: special-secret
    #        key: special.how
    env:
    storage:
      size: 1Gi
      storageClassName: ""
      # [USER] Set `ephemeral: true` to delete all persisted data when clusters shut down or restart.
      ephemeral: true
    resources:
      # [USER] Specify the CPU limit and the memory limit for each pod.
      limits:
        cpu: 1000m
        memory: 1024Mi
      # [USER] Specify the maximum CPU requests and the maximum memory requests for each pod.
      requests:
        cpu: 1000m
        memory: 1024Mi

  security:
    secretName: ""
    batch: ""

  expose:
    # [USER] Specify `type: ""` to disable network access to clusters.
    type: Route
    nodePort: 0
    host: dummy
    annotations:
      - key: kubernetes.io/ingress.class
        value: alb
      - key: alb.ingress.kubernetes.io/group.name
        value: dummy
      - key: alb.ingress.kubernetes.io/group.order
        value: dummy
      - key: alb.ingress.kubernetes.io/scheme
        value: internal
      - key: alb.ingress.kubernetes.io/target-type
        value: ip
      - key: alb.ingress.kubernetes.io/listen-ports
        value: '[{"HTTP": 80}, {"HTTPS":443}]'
      - key: alb.ingress.kubernetes.io/certificate-arn
        value: dummy
      - key: alb.ingress.kubernetes.io/ssl-redirect
        value: '443'

  monitoring:
    enabled: false

  logging:
    categories:
      # [USER] Specify the FQN of a package from which you want to collect logs.
      - category: com.arjuna
        # [USER] Specify the level of log messages.
        level: warn
      # No need to warn about not being able to TLS/SSL handshake
      - category: io.netty.handler.ssl.ApplicationProtocolNegotiationHandler
        level: error

  makeDataDirWritable: false

  nameOverride: ""

  resourceLabels: []

  podLabels:
    - key: microservice
      value: infinispan

  svcLabels: []

  tolerations: []

  nodeAffinity: {}

  nodeSelector: {}

  infinispan:
    cacheContainer:
      # [USER] Add cache, template, and counter configuration.
      name: default
      # [USER] Specify `security: null` to disable security authorization.
      security:
        authorization: {}
      transport:
        cluster: ${infinispan.cluster.name:cluster}
        node-name: ${infinispan.node.name:}
        stack: kubernetes
    server:
      endpoints:
      # [USER] Hot Rod and REST endpoints.
      - securityRealm: default
        socketBinding: default
        connectors:
          rest:
            restConnector:
          hotrod:
            hotrodConnector:
          # [MEMCACHED] Uncomment to enable Memcached endpoint
          # memcached:
          #   memcachedConnector:
          #     socketBinding: memcached
      # [METRICS] Metrics endpoint for cluster monitoring capabilities.
      - connectors:
          rest:
            restConnector:
              authentication:
                mechanisms: BASIC
        securityRealm: metrics
        socketBinding: metrics
      interfaces:
      - inetAddress:
          value: ${infinispan.bind.address:<IP_ADDRESS>}
        name: public
      security:
        credentialStores:
        - clearTextCredential:
            clearText: secret
          name: credentials
          path: credentials.pfx
        securityRealms:
        # [USER] Security realm for the Hot Rod and REST endpoints.
        - name: default
          # [USER] Comment or remove this properties realm to disable authentication.
          propertiesRealm:
            groupProperties:
              path: groups.properties
            groupsAttribute: Roles
            userProperties:
              path: users.properties
          # [METRICS] Security realm for the metrics endpoint.
        - name: metrics
          propertiesRealm:
            groupProperties:
              path: metrics-groups.properties
              relativeTo: infinispan.server.config.path
            groupsAttribute: Roles
            userProperties:
              path: metrics-users.properties
              relativeTo: infinispan.server.config.path
      socketBindings:
        defaultInterface: public
        portOffset: ${infinispan.socket.binding.port-offset:0}
        socketBinding:
          # [USER] Socket binding for the Hot Rod and REST endpoints.
        - name: default
          port: 11222
          # [METRICS] Socket binding for the metrics endpoint.
        - name: metrics
          port: 11223
          # [MEMCACHED] Uncomment to enable Memcached endpoint
        # - name: memcached
        #   port: 11221

There is a log
`08:25:38,381 WARN  [ServiceFinder] Skipping service: java.security.Provider: Provider org.wildfly.security.auth.client.WildFlyElytronClientDefaultSSLContextProvider could not be instantiated
08:25:38,482 WARN  [ServiceFinder] Skipping service: org.aesh.command.Command: org.infinispan.cli.commands.kubernetes.Delete$Cluster Unable to get public no-arg constructor
08:25:38,484 WARN  [ServiceFinder] Skipping service: org.aesh.command.Command: org.infinispan.cli.commands.kubernetes.Get$Clusters Unable to get public no-arg constructor
2023-11-06 08:25:45,392 INFO  (main) [BOOT] JVM OpenJDK 64-Bit Server VM Red Hat, Inc. 17.0.9+9-LTS
2023-11-06 08:25:45,405 INFO  (main) [BOOT] JVM arguments = [-server, --add-exports, java.naming/com.sun.jndi.ldap=ALL-UNNAMED, --add-opens, java.base/java.util=ALL-UNNAMED, --add-opens, java.base/java.util.concurrent=ALL-UNNAMED, -Xlog:gc*:file=/opt/infinispan/server/log/gc.log:time,uptimemillis:filecount=5,filesize=3M, -Djgroups.dns.query=infinispan-ping.keycloak.svc.cluster.local, -Xmx512m, -XX:+ExitOnOutOfMemoryError, -XX:MetaspaceSize=32m, -XX:MaxMetaspaceSize=96m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Dvisualvm.display.name=infinispan-server, -Djava.util.logging.manager=org.infinispan.server.loader.LogManager, -Dinfinispan.server.home.path=/opt/infinispan, -classpath, :/opt/infinispan/boot/infinispan-server-runtime-14.0.19.Final-loader.jar, org.infinispan.server.loader.Loader, org.infinispan.server.Bootstrap, --cluster-name=infinispan, --server-config=/etc/config/infinispan.yml, --logging-config=/etc/config/log4j2.xml, --bind-address=<IP_ADDRESS>]
2023-11-06 08:25:45,410 INFO  (main) [BOOT] PID = 170
2023-11-06 08:25:45,533 INFO  (main) [org.infinispan.SERVER] ISPN080000: Infinispan Server 14.0.19.Final starting
2023-11-06 08:25:45,534 INFO  (main) [org.infinispan.SERVER] ISPN080017: Server configuration: /etc/config/infinispan.yml
2023-11-06 08:25:45,534 INFO  (main) [org.infinispan.SERVER] ISPN080032: Logging configuration: /etc/config/log4j2.xml
2023-11-06 08:25:47,267 INFO  (main) [org.infinispan.SERVER] ISPN080027: Loaded extension 'query-dsl-filter-converter-factory'
2023-11-06 08:25:47,267 INFO  (main) [org.infinispan.SERVER] ISPN080027: Loaded extension 'continuous-query-filter-converter-factory'
2023-11-06 08:25:47,276 INFO  (main) [org.infinispan.SERVER] ISPN080027: Loaded extension 'iteration-filter-converter-factory'
2023-11-06 08:25:47,280 WARN  (main) [org.infinispan.SERVER] ISPN080059: No script engines are available
2023-11-06 08:25:48,609 INFO  (main) [org.infinispan.CONTAINER] ISPN000556: Starting user marshaller 'org.infinispan.commons.marshall.ImmutableProtoStreamMarshaller'
2023-11-06 08:25:49,022 WARN  (main) [org.infinispan.PERSISTENCE] ISPN000554: jboss-marshalling is deprecated and planned for removal
2023-11-06 08:25:50,697 INFO  (main) [org.infinispan.CLUSTER] ISPN000078: Starting JGroups channel infinispan with stack kubernetes
2023-11-06 08:25:50,705 INFO  (main) [org.jgroups.JChannel] local_addr: 2ef175c5-249b-4ec5-8e2f-e055c8a47169, name: infinispan-0-38584
2023-11-06 08:25:50,765 INFO  (main) [org.jgroups.protocols.FD_SOCK2] server listening on *.57800
2023-11-06 08:25:52,772 INFO  (main) [org.jgroups.protocols.pbcast.GMS] infinispan-0-38584: no members discovered after 2001 ms: creating cluster as coordinator
2023-11-06 08:25:52,796 INFO  (main) [org.infinispan.CLUSTER] ISPN000094: Received new cluster view for channel infinispan: [infinispan-0-38584|0] (1) [infinispan-0-38584]
2023-11-06 08:25:53,071 INFO  (main) [org.infinispan.CLUSTER] ISPN000079: Channel infinispan local address is infinispan-0-38584, physical addresses are [<IP_ADDRESS>:7800]
2023-11-06 08:25:53,090 INFO  (main) [org.infinispan.CONTAINER] ISPN000390: Persisted state, version=14.0.19.Final timestamp=2023-11-06T08:25:53.089106869Z
2023-11-06 08:25:53,715 INFO  (main) [org.jboss.threads] JBoss Threads version 2.3.3.Final
2023-11-06 08:25:54,419 INFO  (main) [org.infinispan.CONTAINER] ISPN000104: Using EmbeddedTransactionManager
2023-11-06 08:25:55,057 WARN  (main) [org.infinispan.SERVER] ISPN080072: JMX remoting enabled without a default security realm. All connections will be rejected.
2023-11-06 08:25:55,096 INFO  (main) [org.infinispan.server.core.telemetry.TelemetryServiceFactory] ISPN000953: OpenTelemetry integration is disabled
2023-11-06 08:25:55,307 INFO  (ForkJoinPool.commonPool-worker-1) [org.infinispan.SERVER] ISPN080018: Started connector HotRod (internal)
2023-11-06 08:25:55,481 INFO  (main) [org.infinispan.SERVER] ISPN080018: Started connector REST (internal)
2023-11-06 08:25:55,515 INFO  (main) [org.infinispan.SERVER] Using transport: Epoll
2023-11-06 08:25:55,724 INFO  (main) [org.infinispan.SERVER] ISPN080004: Connector SinglePort (default) listening on <IP_ADDRESS>:11222
2023-11-06 08:25:55,726 INFO  (main) [org.infinispan.SERVER] ISPN080034: Server 'infinispan-0-38584' listening on http://<IP_ADDRESS>:11222
2023-11-06 08:25:55,810 INFO  (main) [org.infinispan.SERVER] ISPN080018: Started connector REST (internal)
2023-11-06 08:25:55,812 INFO  (main) [org.infinispan.SERVER] Using transport: Epoll
2023-11-06 08:25:55,861 INFO  (main) [org.infinispan.SERVER] ISPN080004: Connector SinglePort (metrics) listening on <IP_ADDRESS>:11223
2023-11-06 08:25:55,863 INFO  (main) [org.infinispan.SERVER] ISPN080034: Server 'infinispan-0-38584' listening on http://<IP_ADDRESS>:11223
2023-11-06 08:25:55,988 INFO  (main) [org.infinispan.SERVER] ISPN080001: Infinispan Server 14.0.19.Final started in 10452ms
2023-11-06 08:26:22,286 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] ISPN000094: Received new cluster view for channel infinispan: [infinispan-0-38584|1] (2) [infinispan-0-38584, infinispan-1-63294]
2023-11-06 08:26:22,301 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Scope=infinispan-0-38584]ISPN100000: Node infinispan-1-63294 joined the cluster
2023-11-06 08:26:22,324 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Scope=infinispan-0-38584]ISPN100000: Node infinispan-1-63294 joined the cluster
2023-11-06 08:26:23,396 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.PERMISSIONS]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:23,400 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=org.infinispan.PERMISSIONS][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:23,414 INFO  (non-blocking-thread--p2-t1) [org.infinispan.LIFECYCLE] [Context=org.infinispan.PERMISSIONS][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:23,675 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.ROLES]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:23,679 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=org.infinispan.ROLES][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:23,682 INFO  (non-blocking-thread--p2-t2) [org.infinispan.LIFECYCLE] [Context=org.infinispan.ROLES][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:23,803 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.PERMISSIONS]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:23,858 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.PERMISSIONS]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:23,874 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CLIENT_SERVER_TX_TABLE]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:23,876 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=org.infinispan.CLIENT_SERVER_TX_TABLE][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:23,878 INFO  (non-blocking-thread--p2-t1) [org.infinispan.LIFECYCLE] [Context=org.infinispan.CLIENT_SERVER_TX_TABLE][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:23,933 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.PERMISSIONS]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:23,934 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.ROLES]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:23,942 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.ROLES]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:23,950 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.ROLES]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:23,952 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CLIENT_SERVER_TX_TABLE]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:23,958 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CLIENT_SERVER_TX_TABLE]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:24,005 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CLIENT_SERVER_TX_TABLE]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:24,076 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___protobuf_metadata]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,079 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=___protobuf_metadata][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,084 INFO  (non-blocking-thread--p2-t2) [org.infinispan.LIFECYCLE] [Context=___protobuf_metadata][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:24,144 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CONFIG]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,151 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=org.infinispan.CONFIG][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,158 INFO  (non-blocking-thread--p2-t1) [org.infinispan.LIFECYCLE] [Context=org.infinispan.CONFIG][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:24,185 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CONFIG]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:24,258 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CONFIG]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:24,266 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.CONFIG]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:24,270 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___protobuf_metadata]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:24,284 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___protobuf_metadata]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:24,296 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.COUNTER]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,302 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=org.infinispan.COUNTER][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,309 INFO  (non-blocking-thread--p2-t2) [org.infinispan.LIFECYCLE] [Context=org.infinispan.COUNTER][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:24,332 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___protobuf_metadata]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:24,436 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.COUNTER]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:24,448 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.COUNTER]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:24,476 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.COUNTER]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:24,508 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___script_cache]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,518 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=___script_cache][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,532 INFO  (non-blocking-thread--p2-t1) [org.infinispan.LIFECYCLE] [Context=___script_cache][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:24,602 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___script_cache]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:24,649 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___script_cache]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:24,654 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___script_cache]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:24,685 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.LOCKS]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,686 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=org.infinispan.LOCKS][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:24,688 INFO  (non-blocking-thread--p2-t1) [org.infinispan.LIFECYCLE] [Context=org.infinispan.LOCKS][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:24,752 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.LOCKS]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:24,760 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.LOCKS]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:24,765 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=org.infinispan.LOCKS]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5
2023-11-06 08:26:25,266 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___hotRodTopologyCache_hotrod-default]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:25,268 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.LIFECYCLE] [Context=___hotRodTopologyCache_hotrod-default][Scope=infinispan-0-38584]ISPN100002: Starting rebalance with members [infinispan-0-38584, infinispan-1-63294], phase READ_OLD_WRITE_ALL, topology id 2
2023-11-06 08:26:25,270 INFO  (non-blocking-thread--p2-t2) [org.infinispan.LIFECYCLE] [Context=___hotRodTopologyCache_hotrod-default][Scope=infinispan-0-38584]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 2
2023-11-06 08:26:25,379 INFO  (jgroups-6,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___hotRodTopologyCache_hotrod-default]ISPN100009: Advancing to rebalance phase READ_ALL_WRITE_ALL, topology id 3
2023-11-06 08:26:25,387 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___hotRodTopologyCache_hotrod-default]ISPN100009: Advancing to rebalance phase READ_NEW_WRITE_ALL, topology id 4
2023-11-06 08:26:25,393 INFO  (jgroups-5,infinispan-0-38584) [org.infinispan.CLUSTER] [Context=___hotRodTopologyCache_hotrod-default]ISPN100010: Finished rebalance with members [infinispan-0-38584, infinispan-1-63294], topology id 5`

And errors from browser

@ryanemerson Hello!
Can you tell me what is this an error ?
Thank you

All those 403 indicate a wrong authentication.

It's happened after authentication
I can show you @tristantarrant if you need this

@tristantarrant

There is an auth by default user developer
same problems

After i logged to console i see next error in Network Inspect
https://dns.name/console/fonts/RedHatText-Regular.woff
Request Method:
GET
Status Code:
403 Forbidden
Remote Address:
<IP_ADDRESS>:443
Referrer Policy:
strict-origin-when-cross-origin
Content-Length:
0
Date:
Mon, 06 Nov 2023 11:29:23 GMT
:authority:
ispn.kulu.com
:method:
GET
:path:
/console/fonts/RedHatText-Regular.woff
:scheme:
https
Accept:
*/*
Accept-Encoding:
gzip, deflate, br
Accept-Language:
en-US,en;q=0.9
Cookie:
locale=en-US
Origin:
https://ispn.kulu.com
Referer:
https://dns.name/console/app.css
Sec-Ch-Ua:
"Google Chrome";v="119", "Chromium";v="119", "Not?A_Brand";v="24"
Sec-Ch-Ua-Mobile:
?0
Sec-Ch-Ua-Platform:
"Windows"
Sec-Fetch-Dest:
font
Sec-Fetch-Mode:
cors
Sec-Fetch-Site:
same-origin
User-Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

Problem with console as i see
So any suggestions ? Because it's very bad

@oburd Are you providing an authentication secret via deploy.security.secretName or are you using the users that are auto-generated?

@ryanemerson both

one time it's default
i added to deploy.security.batch this one "user create ${local.infinispan.infinispan_admin_user} -p ${local.infinispan.infinispan_admin_password} -g admin"

Hmm you're correctly adding the -g admin in step 2, so I would expect that to work.
Can you try disabling authorization by setting infinispan.cacheContainer.security.authorization: null and see if the problem persists?

Hmm you're correctly adding the -g admin in step 2, so I would expect that to work.
Can you try disabling authorization by setting infinispan.cacheContainer.security.authorization: null and see if the problem persists?

Okay i will try, but it's very strange for me
I did right like it wrote in instruction :)
I tried to use infinispan docker image with tag 12.1, but received error
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "--cluster-name=infinispan": executable file not found in $PATH: unknown
:D

@ryanemerson so there is a result:

infinispan.cacheContainer.security.authorization: null nothing changed error the same

infinispan:
cacheContainer:
# [USER] Add cache, template, and counter configuration.
name: default
# [USER] Specify security: null to disable security authorization.
security: null
Little better but errors same and as i thought that i dont need to authentication but i need to enter login and password
There is a screenshot
![error](https://github.com/infinispan/infinispan-helm-charts/assets/130356827/f635fced-32b7-4899-a26a-c8fa066fe4d2)

Little better but errors same and as i thought that i dont need to authentication but i need to enter login and password

Setting infinispan.cacheContainer.security.authorization: null disables authorization, not authentication, which is why you still need to login.
To disable authentication you can comment the following lines https://github.com/infinispan/infinispan-helm-charts/blob/main/values.yaml#L136-L141

Little better but errors same and as i thought that i dont need to authentication but i need to enter login and password

Setting infinispan.cacheContainer.security.authorization: null disables authorization, not authentication, which is why you still need to login.
To disable authentication entirely you can comment the following lines https://github.com/infinispan/infinispan-helm-charts/blob/main/values.yaml#L136-L141

@ryanemerson
okay, i understood, but error still present which i have described upper
Question:
what this line doing ?
infinispan.cacheContainer.security.authorization: {}
because i didn't find anything about it

@ryanemerson
okay, i understood, but error still present which i have described upper

If you're still getting 403 errors with both Authorization and Authentication disabled, then I think this is an issue with your Ingress configuration.

I did what you wrote infinispan.cacheContainer.security.authorization: null nothing changed
i turn off
infinispan:
    cacheContainer:
      # [USER] Add cache, template, and counter configuration.
      name: default
      # [USER] Specify `security: null` to disable security authorization.
      security: null

nothing changed
About Ingress
I take default part of your and add only annotation that i can use AWS ALB
If the problem with ALB i can't enter at all on console page
i did same Ingress configuration for different services and they work fine
There is my annotations
annotations:
      - key: kubernetes.io/ingress.class
        value: alb
      - key: alb.ingress.kubernetes.io/group.name
        value: dummy
      - key: alb.ingress.kubernetes.io/group.order
        value: dummy
      - key: alb.ingress.kubernetes.io/scheme
        value: internal
      - key: alb.ingress.kubernetes.io/target-type
        value: ip
      - key: alb.ingress.kubernetes.io/listen-ports
        value: '[{"HTTP": 80}, {"HTTPS":443}]'
      - key: alb.ingress.kubernetes.io/certificate-arn
        value: dummy
      - key: alb.ingress.kubernetes.io/ssl-redirect
        value: '443'
      - key: alb.ingress.kubernetes.io/healthcheck-path
        value: /rest/v2/cache-managers/default/health/status

@ryanemerson
good news
i have done:
infinispan.cacheContainer.security.authorization: null
and turned off
          #propertiesRealm:
            #groupProperties:
              #path: groups.properties
            #groupsAttribute: Roles
            #userProperties:
              #path: users.properties

And it's work most better
But it's not good that we dont have authorization and authentication

@ryanemerson
I dont understand only one thing, why the default dont want to to correct work with your configuration
Because as i understand  authentication is pass, but authorization isn't work well
Maybe something i need to add to my file?
# Default values for infinispan-helm-charts.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

images:
  # [USER] The container images for server pods.
  server: quay.io/infinispan/server:14.0
  initContainer: registry.access.redhat.com/ubi8-micro

deploy:
  # [USER] Specify the number of nodes in the cluster.
  replicas: 2

  clusterDomain: cluster.local

  container:
    extraJvmOpts: ""
    libraries: ""
    # [USER] Define custom environment variables using standard K8s format
    # env:
    #  - name: STANDARD_KEY
    #    value: standard value
    #  - name: CONFIG_MAP_KEY
    #    valueFrom:
    #      configMapKeyRef:
    #        name: special-config
    #        key: special.how
    #  - name: SECRET_KEY
    #    valueFrom:
    #      secretKeyRef:
    #        name: special-secret
    #        key: special.how
    env:
    storage:
      size: 1Gi
      storageClassName: ""
      # [USER] Set `ephemeral: true` to delete all persisted data when clusters shut down or restart.
      ephemeral: true
    resources:
      # [USER] Specify the CPU limit and the memory limit for each pod.
      limits:
        cpu: 1000m
        memory: 1024Mi
      # [USER] Specify the maximum CPU requests and the maximum memory requests for each pod.
      requests:
        cpu: 1000m
        memory: 1024Mi

  security:
    secretName: ""
    batch: ""

  expose:
    # [USER] Specify `type: ""` to disable network access to clusters.
    type: Route
    nodePort: 0
    host: dummy
    annotations:
      - key: kubernetes.io/ingress.class
        value: alb
      - key: alb.ingress.kubernetes.io/group.name
        value: dummy
      - key: alb.ingress.kubernetes.io/group.order
        value: '17'
      - key: alb.ingress.kubernetes.io/scheme
        value: internal
      - key: alb.ingress.kubernetes.io/target-type
        value: ip
      - key: alb.ingress.kubernetes.io/listen-ports
        value: '[{"HTTP": 80}, {"HTTPS":443}]'
      - key: alb.ingress.kubernetes.io/certificate-arn
        value: dummy
      - key: alb.ingress.kubernetes.io/ssl-redirect
        value: '443'
      - key: alb.ingress.kubernetes.io/healthcheck-path
        value: /rest/v2/cache-managers/default/health/status

  monitoring:
    enabled: false

  logging:
    categories:
      # [USER] Specify the FQN of a package from which you want to collect logs.
      - category: com.arjuna
        # [USER] Specify the level of log messages.
        level: warn
      # No need to warn about not being able to TLS/SSL handshake
      - category: io.netty.handler.ssl.ApplicationProtocolNegotiationHandler
        level: error

  makeDataDirWritable: false

  nameOverride: ""

  resourceLabels: []

  podLabels:
    - key: microservice
      value: infinispan

  svcLabels: []

  tolerations: []

  nodeAffinity: {}

  nodeSelector: {}

  infinispan:
    cacheContainer:
      # [USER] Add cache, template, and counter configuration.
      name: default
      # [USER] Specify `security: null` to disable security authorization.
      security:
        authorization: {}
      transport:
        cluster: ${infinispan.cluster.name:cluster}
        node-name: ${infinispan.node.name:}
        stack: kubernetes
    server:
      endpoints:
      # [USER] Hot Rod and REST endpoints.
      - securityRealm: default
        socketBinding: default
        connectors:
          rest:
            restConnector:
          hotrod:
            hotrodConnector:
          # [MEMCACHED] Uncomment to enable Memcached endpoint
          # memcached:
          #   memcachedConnector:
          #     socketBinding: memcached
      # [METRICS] Metrics endpoint for cluster monitoring capabilities.
      - connectors:
          rest:
            restConnector:
              authentication:
                mechanisms: BASIC
        securityRealm: metrics
        socketBinding: metrics
      interfaces:
      - inetAddress:
          value: ${infinispan.bind.address:<IP_ADDRESS>}
        name: public
      security:
        credentialStores:
        - clearTextCredential:
            clearText: secret
          name: credentials
          path: credentials.pfx
        securityRealms:
        # [USER] Security realm for the Hot Rod and REST endpoints.
        - name: default
          # [USER] Comment or remove this properties realm to disable authentication.
          propertiesRealm:
            groupProperties:
              path: groups.properties
            groupsAttribute: Roles
              userProperties:
                path: users.properties
          # [METRICS] Security realm for the metrics endpoint.
        - name: metrics
          propertiesRealm:
            groupProperties:
              path: metrics-groups.properties
              relativeTo: infinispan.server.config.path
            groupsAttribute: Roles
            userProperties:
              path: metrics-users.properties
              relativeTo: infinispan.server.config.path
      socketBindings:
        defaultInterface: public
        portOffset: ${infinispan.socket.binding.port-offset:0}
        socketBinding:
          # [USER] Socket binding for the Hot Rod and REST endpoints.
        - name: default
          port: 11222
          # [METRICS] Socket binding for the metrics endpoint.
        - name: metrics
          port: 11223
          # [MEMCACHED] Uncomment to enable Memcached endpoint
        # - name: memcached
        #   port: 11221

@ryanemerson  Hello!
There are my 2 posts, can you please check ?
Thank you

We think the issue might be caused by DIGEST authentication. If the Loadbalancer is using a round robin policy and sticky sessions are not enabled, then the challenge/response of the DIGEST protocol will be sent to different Infinispan pods. There are two workarounds for this:

Enable sticky sessions on the loadbalancer with the following annotation: alb.ingress.kubernetes.io/target-group-attributes: stickiness.enabled=true
Disable the DIGEST protocol on the Infinispan rest server, to do this update your values to:

    server:
      endpoints:
      # [USER] Hot Rod and REST endpoints.
      - securityRealm: default
        socketBinding: default
        connectors:
          rest:
            restConnector:
              authentication:
                mechanisms: BASIC
          hotrod:
            hotrodConnector:
          # [MEMCACHED] Uncomment to enable Memcached endpoint
          # memcached:
          #   memcachedConnector:
          #     socketBinding: memcached
      # [METRICS] Metrics endpoint for cluster monitoring capabilities.
      - connectors:
          rest:
            restConnector:
              authentication:
                mechanisms: BASIC

@ryanemerson nice, thank you for help, i will check it and back with results

@ryanemerson
Hello!
Thank you for help
It's work with BASIC auth


Logo

We need a proper logo. Nik's quickly made for launch one is alright, but I want some stickers with a nice logo!
/cc @elioqoshi @okonet who've helped before with logos!

Do we want to refer to React in the logo?

I don't think so, to be honest. Especially keeping in mind that carte-blanche has plan to support other frameworks/libs.

I'd be happy to take this on :)

That'd be awesome!

What do you think about this? @mxstbr

i'll also make one tonight.

yay, looking forward to a couple of variations 🙌
@elioqoshi nice one, what I recommend in general is to not use uppercase characters all the way (which is funny, because yet I couldn't even convince my own team 😜)

@nikgraf why specifically? There is no thumb rule as in "avoid doing x" in that case so is there any reason for that here apart personal preference?

@elioqoshi it is about preference (I guess) but I also think that in most cases it makes it harder to read. I realize logos aren't about reading, but I'd also would like to see a version without all caps.

I'm not sure I understand what the icon means, how is it related to Carte Blanche? Looks like an "N" to me, kind of invokes feeling of a construction company…

@okonet makes sense
@mxstbr it's supposed to be 2 cards stacked against each other (like you would do with a card house). Seems it's not too obvious...

"Studies have been conducted on the readability and legibility of all caps text. Scientific testing from the 20th-century onwards has generally indicated that all caps text is less legible and readable than lower-case text.[2][3] In addition, switching to all caps may make text appear hectoring and obnoxious for cultural reasons, since all-capitals is often used in transcribed speech to indicate that the speaker is shouting." https://en.wikipedia.org/wiki/All_caps
@elioqoshi To me readability in a logo is not too important to me as it is not a long text to read, but the second part doesn't "hectoring and obnoxious" is not reflecting what I like this tool be perceived. How do you feel about it?

I should probably get back to work.  But spent a few minutes trying to be helpful.

Here's a possible version. Have alot of work so maybe will have more designs later.

@paulxuca I like the idea with cards but I think the opacity won't work well on most screens. It's hard to see the last card even on the iPhone. It also look to similar to the Medium's logo IMO.

different approach (playing on the idea of a blanche card and testing components).

I like where this is going! I like the colors in @ac360, though I'm not sure a whisky glass is what we want as an icon :grin: @eddiewang and @paulxuca's direction is great!
The last @paulxuca one is a bit too explicit in my opinion, there's too much fidelity in the icon.

Here is my (very rough) attempt.
It is based on a geometric form of 2 cards (what else!) and first capital letters of Carte Blanche. First variant resembles similarity with Node.js (JavaScript).

Both are quick sketches and should be cleaned up in case we go with them. I'm also not completely sold on the type yet but I think for the GitHub project this isn't important since we can't change it on the GH page itself and only the sign will appear (I guess).

A few more ideas:

I like the right one in your last comment @okonet, but the colors seem a bit… muddy? The b is also a bit hard to see.

What do you think about this?


Add edit/bake/refresh buttons to transcluded pages

They're missing now, but would be useful. Also for consistency.

Just mentioning @onespaceman in case he's bored and wants continue is excellent work in this area 🥸


Unique dataset value not working

The other combinations are working fine except for this one, I am not sure if I am doing anything wrong.
When I was trying to select the unique row on each iteration/once the jmeter is throwing below error:
2023-03-13 16:17:55,943 ERROR o.a.j.t.JMeterThread: Test failed!
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:675) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:781) ~[?:?]
at com.di.jmeter.config.ExtendedCsvDataSetConfig.initBlockFeatures(ExtendedCsvDataSetConfig.java:164) ~[di-extended-csv-2.0.jar:?]
at com.di.jmeter.config.ExtendedCsvDataSetConfig.initVars(ExtendedCsvDataSetConfig.java:152) ~[di-extended-csv-2.0.jar:?]
at com.di.jmeter.config.ExtendedCsvDataSetConfig.iterationStart(ExtendedCsvDataSetConfig.java:53) ~[di-extended-csv-2.0.jar:?]
at org.apache.jmeter.control.GenericController.fireIterationStart(GenericController.java:399) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.GenericController.fireIterEvents(GenericController.java:391) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.GenericController.next(GenericController.java:160) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.TransactionController.nextWithoutTransactionSampler(TransactionController.java:205) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.TransactionController.next(TransactionController.java:135) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.GenericController.nextIsAController(GenericController.java:222) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.GenericController.next(GenericController.java:175) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.control.LoopController.next(LoopController.java:134) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.threads.AbstractThreadGroup.next(AbstractThreadGroup.java:99) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:266) ~[ApacheJMeter_core.jar:5.5]
at java.lang.Thread.run(Thread.java:1589) ~[?:?]

I have updated the code for gui as well - It should select the autoallocate by default (if not set) when unique selection is enabled
Can you try uninstalling the plugin and install it again ?

Hello Vikash
Thanks for bringing up - From the screenshot you have shared I could see the Allocate block is unset
Try setting the value to Autoallocate or custom allocate and give it a try

I tried autoallocating the value and still it is throwing some error:

I have updated the code for gui as well - It should select the autoallocate by default (if not set) when unique selection is enabled
Can you try uninstalling the plugin and install it again ?

I will try this method.

I tried the same - it works fine with me

Couple of things:

Check your csv file path
Check your csv file by clicking Edit button
Check your delimiter value

Hi,
Did you get a chance to check the issue?

Thanks,
After building the jar again it was running fine.

FYI: It's already available with plugins manager.
I will mark this issue as closed
Feel free to hit a star, it means a lot


Simplify constructN and nAry

Again, this uses techniques not available in old environments.  This should come post-1.0.


failure with uvloop and @fail_on

While testing with uvloop, the @fail_on decorator seems to rely on the internals of the default asyncio loop:
import asyncio
import asynctest
import uvloop

# make calls to asyncio.get_event_loop() return an instance of uvloop
asyncio.set_event_loop_policy(uvloop.EventLoopPolicy())

@asynctest.fail_on(active_handles=True)
class TestFailOn(asynctest.TestCase):
    """
    This raises in asynctest with:
        AttributeError: 'Loop' object has no attribute '_scheduled'
    at .../asynctest/_fail_on.py:88
    """

    use_default_loop = True

    async def test_async_task(self):
        await asyncio.sleep(0)

Yes, the public API of asyncio doesn't expose enough methods to implement these features.
Unfortunately, fixing this is complicated and I've no plans yet.


[Question] how about add a change log file for each release

Can you descirbe more detail about the workflow?

Hi @shaobo322
That's a good point!
Currently KubeVela is under heavy development. Releases roll out frequently and our developers work closely together on Ding Group. Our roadmap is also a big one which includes major features across releases.
Once hitting BETA KubeVela would have more formal release process including roadmap and changelog for each release.

Closing, we will add a breif release note. Thanks for reminding.


Quadratic probing in java

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Quadratic probing in hashing in java
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#5466

@ankitaggarwal23  please review it


[Enhancement] Propagate Conf.default_bucket_num to CREATE TABLE AS SELECT

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes # N/A
Problem Summary(Required) ：

Previously, Conf.default_bucket_num only applies to CREATE TABLE. CREATE TABLE AS SELECT used a hard-coded default bucket num of 10.
This PR  propagates Conf.default_bucket_num to CREATE TABLE AS SELECT.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/CTASAnalyzer.java
1
1
100.00%
[]

run starrocks_admit_test

run starrocks_admit_test

https://github.com/Mergifyio backport branch-2.5

https://github.com/Mergifyio backport branch-2.4

https://github.com/Mergifyio backport branch-2.3


[FEATURE REQUEST] Could you support subscription of some specific symbols for GetTickersWebSocket()

I have a [FEATURE REQUEST]
Details:
Could you change the interface from
IDisposable GetTickersWebSocket(System.Action<IReadOnlyCollection<KeyValuePair<string, ExchangeTicker>>> tickers);
to
IDisposable GetTickersWebSocket(System.Action<IReadOnlyCollection<KeyValuePair<string, ExchangeTicker>>> tickers, IList symbols = null);
so, I can subscribe some specific symbols for market data using websocket method, But I don't want subscribe all symbols include some unused symbols. I have check the exchange API documents, most of them supports this usage, so could you support that.

maybe need subscribe and unsubscribe functions

Happy with the change, but let's make it params string[] symbols = null. Send a pull request and I will look it over.

The method call subscribes and returns IDisposable, which when disposed unsubscribes.


Avalonia error XAMLIL: Unable to find public constructor for type ResourceInclude

Error:
/home/ubuntu/projects/Dock/samples/AvaloniaDemo.Experimental/Layouts/Default.xaml(9,31,9,31): Avalonia error XAMLIL: Unable to find public constructor for type Avalonia.Markup.Xaml:Avalonia.Markup.Xaml.MarkupExtensions.ResourceInclude(System.Runtime:System.String) (line 9 position 31) Line 9, position 31. [/home/ubuntu/projects/Dock/samples/AvaloniaDemo.Experimental/AvaloniaDemo.Experimental.csproj]

Repro:
<Style xmlns="https://github.com/avaloniaui"
       xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
       xmlns:idc="clr-namespace:Dock.Avalonia.Controls;assembly=Dock.Avalonia"
       xmlns:dmc="clr-namespace:Dock.Model.Controls;assembly=Dock.Model.Avalonia"
       xmlns:vmd="clr-namespace:AvaloniaDemo.ViewModels.Documents;assembly=AvaloniaDemo"
       xmlns:vmt="clr-namespace:AvaloniaDemo.ViewModels.Tools;assembly=AvaloniaDemo"
       xmlns:vmv="clr-namespace:AvaloniaDemo.ViewModels.Views;assembly=AvaloniaDemo"
       Selector="idc|DockControl.Default">
    <Setter Property="Layout" Value="{ResourceInclude avares://AvaloniaDemo/Layouts/Root.xaml}"/>
</Style>

I'm not sure how your XAML is supposed to work. According to the tests, it's supposed to be used like this:
https://github.com/AvaloniaUI/Avalonia/blob/master/tests/Avalonia.Markup.Xaml.UnitTests/MarkupExtensions/ResourceIncludeTests.cs#L25
I don't see any code that would load anything but IResourceProvider.

@kekekeks I was just trying stuff and found the issue. I was also unsure if this will work.

It doesn't seem to be compiler-related. The ResourceInclude doesn't have a constructor that accepts a string as a parameter. It also seems to be only used in merged resource dictionaries.
However this brings up a question. Should we cache loaded xaml resource instances?

I am not sure about the question. My use case is to instantiate object declared using xaml.

I think the current supported way of instantiating custom xaml-declared objects is an empty class in XAML's codebehind that could be used as an alias.

I think the current supported way of instantiating custom xaml-declared objects is an empty class in XAML's codebehind that could be used as an alias.

What about a scenario when I want to instantiate existing class and not derived.
From my example: https://github.com/kekekeks/XamlIl/issues/6
The Dock class is already present in my library, I just want to instantiate it and use as value for some property. Requiring additional empty class is not possible here as you have to create new class which seems unnecessary. This would make XAML so much powerful in Avalonia and enable more scenarios.
<Dock xmlns="https://github.com/avaloniaui"
      xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
      xmlns:vm="clr-namespace:Demo.ViewModels;assembly=Demo"
      ActiveLayout="{x:Reference layout1}">
  <Dock.Items>
      <vm:Item1ViewModel x:Name="item1"/>
      <vm:Item2ViewModel x:Name="item2"/>
      <vm:Item3ViewModel x:Name="item3"/>
  <Dock.Items>
  <Dock.Layouts>
    <Layout x:Name="layout1">
      <x:Reference Name="item1"/>
      <x:Reference Name="item2"/>
    </Layout>
    <Layout x:Name="layout2">
      <x:Reference Name="item1"/>
      <x:Reference Name="item2"/>
      <x:Reference Name="item3"/>
    </Layout>
  </Dock.Layouts>
</Dock>

@kekekeks I have managed to resolve my issue. If you want we can close this issue.
For reference this is my solution for loading object instances from xaml using custom markup extension.
https://github.com/wieslawsoltes/Dock/blob/8eed1ba62b3f3da51c40aad0a13c9fbe00d14639/samples/AvaloniaDemo.Perspectives/Views/MainView.xaml#L19
https://github.com/wieslawsoltes/Dock/blob/8eed1ba62b3f3da51c40aad0a13c9fbe00d14639/src/Dock.Avalonia/Controls/LayoutIncludeExtension.cs#L12-L51


Tessera change (Privacy Enhancements)

Privacy Enhancements (tessera changes):

Updated send/receive APIs to handle ACOTHs and ExecutionHash
Updated push API to handle ACOTHs
New encrypt/decrypt APIs for use in quorum contract extension
Batch resend (improved resend performance and logic changes to validate ACOTHs)

Additional
• Support deprecated enable-sync-poller spring profile

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 4 committers have signed the CLA.:x: nicolae-leonte-go:x: prd-fox:x: melowe:x: namtruongYou have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #1152 into master will increase coverage by 0.14%.
The diff coverage is 99.79%.

@@             Coverage Diff              @@
##             master    #1152      +/-   ##
============================================
+ Coverage     99.31%   99.46%   +0.14%
- Complexity     2347     2911     +564
============================================
  Files           369      445      +76
  Lines          6598     8389    +1791
  Branches        377      451      +74
============================================
+ Hits           6553     8344    +1791
  Misses            5        5
  Partials         40       40

Flag
Coverage Δ
Complexity Δ

#unittests
99.46% <99.79%> (+0.14%)
2911.00 <477.00> (+564.00)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ
Complexity Δ

.../com/quorum/tessera/config/cli/TesseraCommand.java
100.00% <ø> (ø)
1.00 <0.00> (ø)

...com/quorum/tessera/app/TesseraRestApplication.java
100.00% <ø> (ø)
3.00 <0.00> (ø)

...m/quorum/tessera/partyinfo/model/NodeInfoUtil.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...java/com/quorum/tessera/partyinfo/model/Party.java
100.00% <ø> (ø)
7.00 <0.00> (ø)

.../com/quorum/tessera/partyinfo/model/PartyInfo.java
100.00% <ø> (ø)
4.00 <0.00> (-2.00)

...essera/p2p/partyinfo/PartyInfoParserException.java
100.00% <ø> (ø)
1.00 <0.00> (?)

...om/quorum/tessera/p2p/partyinfo/RestP2pClient.java
88.88% <ø> (ø)
4.00 <0.00> (?)

...um/tessera/p2p/partyinfo/RestP2pClientFactory.java
100.00% <ø> (ø)
3.00 <0.00> (?)

...quorum/tessera/p2p/resend/ResendClientFactory.java
100.00% <ø> (ø)
3.00 <0.00> (?)

...uorum/tessera/p2p/resend/ResendPartyStoreImpl.java
100.00% <ø> (ø)
6.00 <0.00> (?)

... and 199 more

Continue to review full report at Codecov.

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


Missing required parameter client_id when using useTokenClient on vite

I'm trying to use useTokenClient on a vite and vue 3 project to have custom buttons. But the project show this error on console.

@ArthurWize is this resolved?

I am getting the same error with nuxt 3... @ArthurWize did u ever resolve this?

I am getting the same error with nuxt 3... @ArthurWize did u ever resolve this?

I first initialized the plugin in plugins/auth.server.ts but then I changed the file name to plugins/auth.tsand the problem was solved.
This is my code:
import GoogleSignInPlugin from 'vue3-google-signin'

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.vueApp.use(GoogleSignInPlugin, {
    clientId: 'my-client-id'
  });
})


Informational: eleventy-plugin-error-overlay crashes 1.0.0-beta.1

Passing this on FYI regarding the Eleventy 1.0.0-beta.1 version released today...
If an existing Eleventy site (or clone thereof in my case) updated to Eleventy 1.0.0-beta.1 already had the eleventy-plugin-error-overlay plugin installed, running Eleventy will result in the following console error message (substituting my-computer below for actual computer name):
[11ty] Uncaught exception: (more in DEBUG output)
[11ty] > Cannot read property '__original' of undefined

`TypeError` was thrown:
[11ty]     TypeError: Cannot read property '__original' of undefined
        at overrideStatic (/Users/my-computer/eleventy_site_beta/node_modules/eleventy-plugin-error-overlay/index.js:84:35)
        at Immediate.<anonymous> (/Users/my-computer/eleventy_site_beta/node_modules/eleventy-plugin-error-overlay/index.js:45:7)
        at processImmediate (internal/timers.js:461:21)

Removing the plugin resolves the problem.
Environment where used:

macOS 11.6
Eleventy version 1.0.0-beta.1

I'm having this problem, too!

Hi, thanks for great plugin!
I've upgraded to Eleventy 1.0.0 and I'm getting the same error:
[11ty] Uncaught exception: (more in DEBUG output)
[11ty] > Cannot read properties of undefined (reading '__original')

`TypeError` was thrown:
[11ty]     TypeError: Cannot read properties of undefined (reading '__original')
        at overrideStatic (/home/ntraum/coding/ntraum/studiolineatur/node_modules/eleventy-plugin-error-overlay/index.js:84:35)
        at Immediate.<anonymous> (/home/ntraum/coding/ntraum/studiolineatur/node_modules/eleventy-plugin-error-overlay/index.js:45:7)
        at processImmediate (node:internal/timers:473:21)

FYI, might have a fix for this at #4. 😄
You can install and test my fixed version via:
npm i "https://github.com/patricknelson/eleventy-plugin-error-overlay.git#fix-11ty-v1.0.0"

Hey, forgot to update this issue! Fixed in v1.0.0.


Make initialization vector dependant on password or random seed in ReversibleRenamer instead of input data

I suggest the following options:

Calculate IV (initialization vector) based on a password or hardcoded string. It's not secure safe but does not differs from the current scheme because ConfuserEx sources are open and encrypted IV into input data does not provide additional security and only consumes one byte.
Calculate IV based on seed if it's specified. If not then generate a random IV and dump it into the output file. This value or seed can be used later during stack trace decryption. This way looks much more secure safe since it can generate different identifiers every run despite the same encryption key. But it has drawback: IV value from value is required together with the encryption key (I don't think it's a big problem).

I do not fully understand the major advantage of what you are proposing. We can easily change the way the IV is calculated, that isn't much of an issue. But it still needs to be part of the encoded name to ensure that decoding with only the password is possible.
The advantage of the current implementation is that the IV is different for every name, only deriving it from the seed would change that, but even if we create the IV from the name, the seed and the password used, it still wouldn't add much additional security I can see.
I'd like to avoid adding a secondary password that is used create the IV. Two keys aren't more secure than one.

The advantage of the current implementation is that the IV is different for every name

This does not differ from the implementation with just hardcoded and constant IV because once you get the key you are able to decrypt all names despite the fact that IV is inlined into the encrypted name.

I'd like to avoid adding a secondary password that is used to create the IV. Two keys aren't more secure than one.

It's more secure if the seed is different for every obfuscation (random), but not the constant.

The current deobfuscation scheme with reversible mode allows attackers to use the same map encrypted_id → id for the present and future versions of an application. The map can be built one time for valuable identifiers.
It is not possible if a random seed will be used on every obfuscation step.

I got it, I got it :wink:
I'll change it to use the random value generator that is based on the seed.

I also can implement it but a bit later 😃
I suggest using the current scheme if seed is defined (for instance, seed="", seed="qwer")  but without inlined IV in encrypted data because it does not make sense. But If a seed is not defined it will be generated every time and stored in Seed file alongside with Symbols.map.


Ensure channel norm and pixel norm files get re-computed if a new set of channels are provided

What is the purpose of this PR?
Closes #599. The underlying issue is if the user provides a different set of channels on a pixel_output_dir that has an existing channel_norm.feather computed on a different set of channels.
How did you implement your changes
We need to ensure that the set of channels provided when loading in an existing channel_norm.feather match the channels argument set-wise. If they don't, then we simply re-compute and re-save.
The same needs to be done for pixel_norm.feather. We store a checkpoint during the channel_norm.feather check to ensure this can happen seamlessly for the pixel norm too.

@ngreenwald normally, the step of regenerating the FOVs gets skipped if all the FOV .feather files exist, however these will also need to be re-generated if a new set of channels are provided to an existing channel_norm.feather. Will need to spend a bit more time testing this one.

Maybe if the norm_files need to be regenerated, have a warning to the user saying different parameters were detected, then delete the norm files and the feather files. Then none of the downstream logic has to change.

Maybe if the norm_files need to be regenerated, have a warning to the user saying different parameters were detected, then delete the norm files and the feather files. Then none of the downstream logic has to change.

This works. Only additional thing is to delete all the existing preprocessed FOVs as well (to prevent downstream logic from not recomputing these).


Change pathfinding between two paths in auto builder & add options for specifying counterclockwise/clockwise rotation to rotation targets.

Pathfinding Transition and Rotation Target Optimizations
1. Default the pathfinding transition between two auto paths in the auto builder/editor to pathfind to the next path's starting pose. Create an option within the path block in the auto builder/editor that when selected causes the drivetrain to pathfind to the closest point of that specific path as it does now.
Further explanation:
The current pathfinding implementation between two paths in the auto builder/editor is not intuitive. As of this moment PathPlanner links two paths together from the first paths ending pose to the closest point of the second path as seen below:

While this feature of being able to pathfind to the next paths closest point is cool and can be useful in certain scenarios, this should not be the default.
Sometimes this can cause the user to fight more with the GUI than is needed to achieve a desired outcome, such as when creating and connecting to a path that crosses over itself or contains a loop, causing the drivetrain to effectively skip over a path that the user wants it to follow.

The intuitive expectation is that the drivetrain will pathfind from the first path's ending pose to the second path's starting pose.
This is why I would suggest that the more intuitive expectation be the default method used when connecting two paths in the auto builder/editor and that an option in the "follow path" block be added that when selected changes the behavior so that the drivetrain pathfinds to the second path's closest point as it does now.
2. There is no easy way to specify the drivetrain's rotational direction (counterclockwise or clockwise) when rotating to a rotation target in the path editor.
Further explanation:
Yes, you can get the desired outcome of either a counterclockwise or clockwise rotation when the drivetrain is rotating to its rotation target.
However the current way is not very intuitive and can add extra unwanted clutter to the GUI elements being displayed on the path. This can also make it harder and more finicky to edit and make small/large changes to a path since this way forces the managing of two rotation targets to achieve the desired direction of rotation.

This is why I would suggest an option within the rotation target that allows the user to specify counterclockwise or clockwise rotation when the drivetrain attempts to rotate to that rotation target's specifications.
This makes forcing a rotational direction easily manageable in one rotation target instead of two, and makes the path editing experience more intuitive and easy to grasp.

What you've described is path replanning, not pathfinding. Replanning is meant to ease the transition between disjoint paths (within reason), allow for starting pre-planned paths from an unknown position (i.e. some scoring path in teleop), and react to collisions in auto causing large errors. It is not something to be relied on to create autos. If you want an auto to transition from one path's end to the start every time, then align their start/end points. There is a linked waypoint feature in the next release that makes this easier. If you try to string together a bunch of random paths that you wouldn't actually run in auto, replanning can do weird things. But this is not what it is meant for. If you wouldn't string together paths like that without replanning, then don't do it if replanning is enabled. So, this is not going to be changed to support a use-case that just generally shouldn't be done in the first place.
Forcing a rotation direction can be done, but would need quite a bit of generation changes to support it, so it will probably be low priority for a while, at least until python support is finished. I opened a separate issue for it: #501.

Thanks for reading my issue. However, I am still having a problem with the replanning feature in the sense that transitioning between two paths when the second path is a loop causes the loop path to be effectively skipped because of the replanning feature.

The ending pose of the first path is exactly the same as the starting pose for the next path, except it seems the replanning that should be acting upon disjointed paths seems to still be kicking into action despite the paths not being disjointed. There are no discontinuities as seen below in the first paths ending and the second paths starting pose.

Yeah that's not supposed to happen. I'll take a look


[Door-Lock-Server] Server sets LockState to 'Locked' upon initialization

Problem
door-lock-server's InitServer method sets the LockState to 'Locked'.
This creates two unwanted side effects:

LockState is assumed as 'Locked' until the application changes it (which could be misconstrued by a client).
A Lock-Operation-Event is generated in the Event List that says that the door was locked, which is not true.

Proposed Solution
Suggest modifying to set the LockState to null.
From the spec: "The LockState Attribute may be NULL if the lock hardware does not currently know the status of the locking mechanism. For example, a lock may not know the LockState status after a power cycle until the first lock actuation is completed."

Also seems pretty critical...


Intersection Types can be cast to any type V as long as it is nullable

Bug Report
🔎 Search Terms
intersection
type
cast
null
🕗 Version & Regression Information

This is a false-negative type checking issue. An error should be generated, but is not.
This changed between versions 4.2.3 and 4.3.5 and 4.4.2
The incorrect behavior occurs in 4.3.5. The correct behavior occurs in  4.2.3 and 4.4.2

⏯ Playground Link

Playground link with relevant code
💻 Code
interface A {
    a: string;
}

interface B {
    b: string;
}

const objA: A = { a: "hello" }
const objB: B = { b: "hello" }
const objAB: A & B = { a: "hello", b: "world" }

const castA = objA as null; // always an error
const castB = objB as null; // always an error
const castAB = objAB as null; // error on TypeScript 4.2.3 and 4.4.2, not an error on TypeScript 4.3.5
const castAB_string = objAB as string | null; // error on TypeScript 4.2.3 and 4.4.2, not an error on TypeScript 4.3.5
const castAB_number = objAB as number | null; // error on TypeScript 4.2.3 and 4.4.2, not an error on TypeScript 4.3.5

🙁 Actual behavior
In v4.3.5, we don't see the expected type error when casting an intersection type to null or null unions.
This issue does not occur in earlier or later versions.
🙂 Expected behavior
The type error behavior does not change depending on what version is being used, unless there is a well-documented breaking change.

Sounds like it was just a bug in 4.3.5.

Yes, I would assume this is something that needs to be patched on the 4.3.x minor version only

It's worth noting that 4.3.5 is the default version used in the latest VS Code, so it is probably widely used

It's worth noting that 4.3.5 is the default version used in the latest VS Code, so it is probably widely used

But you don't compile with the TypeScript version shipped with VSCode. And I'm confident that with the next August release of VSCode they will ship 4.4, as per microsoft/vscode#130601.

It's worth noting that 4.3.5 is the default version used in the latest VS Code, so it is probably widely used

But you don't compile with the TypeScript version shipped with VSCode. And I'm confident that with the next August release of VSCode they will ship 4.4, as per microsoft/vscode#130601.

Okay, well regardless of VS Code, there are people who use 4.3.x to build their code. 4.4.x has breaking changes. There should be a way to address this issue without requiring users to take on breaking changes. This is what the patch version is for.
Ultimately I can't make you fix it. I found a serious bug that wasted my time and I wanted to save other people the hassle by writing up a report.

We'll monitor comments on this issue, but if it wasn't noticed until a full version later, it's unlikely this warrants a patch.


Quick Search Notification Experiment

Task/Issue URL: https://app.asana.com/0/1157893581871903/1114784852684207
Description:
In previous tasks we saw that installing the widget to the home screen led to a significant increase in search and retention.
A sticky notification could work like a widget, however, unlike a widget would not be restricted to a home screen. It would be available at all times, across home screens as well as when users are in other apps; thus having the potential to increase search and retention further.
Instead of using CTA from Onboarding like we've done in the past, this time we are going to show a notification:

Quick Search Experience:
Two days after installing the application we'll show the "Quick Search Notification Prompt". Note that the time to show the notification is not reset if the app is not used. Should the user choose yes, the ongoing notification will be shown. The prompt is only shown once per install, but the option is always available in Settings

Steps to test this PR:
Concept test variant mf: Control group

Open app
Open Settings
Check that there is no "Open Search in Notifications" option

Concept test variant mg: Quick Search Experience

Open app
Open Settings and toggle Open Search in Notifications on
Check that the ongoing notification is enabled
Tapping on the notification should open the Interstitial Search
Check that ongoing notification is still showing
Open Settings and toggle Open Search in Notifications off
Check that notification has been removed

Screenshots:

Ongoing notification
Prompt
Settings

One more thing, API 21 is looking a little off. It may not be fixable but I wanted you to be aware of it in case there is something more you can do.

This is what I see on API 21 @subsymbolic. Nonetheless, I've changed the icons to be (+) and (X) for devices that show them.


Bug on launch

Today I got the next message

@HallEffect can you reproduce this issue every time you run vscode?
Please give us more details. Can you also reproduce with vscode insiders
https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions


Link to VirtualBox VM setup guide and other minor deployment doc updates

@uptimeDBA wrote up a guide for running CockroachDB in a VirtualBox VM. This PR links to his guide, updates our cloud deployment docs to link to our GCE instructions, and a few other minor updates.
Fixes #262

This change is

LGTM


c++ cooncepts and DSA codes in c++

I've contributed few of my own practised c++ codes covering DSA and cpp concepts

star this repo

Done
On Wed, Oct 12, 2022 at 7:20 PM Pavan Kamthane @.***>
wrote:

star this repo
—
Reply to this email directly, view it on GitHub
https://github.com/Pavan-Kamthane/Cpp_Lang/pull/42#issuecomment-1276205333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATZVZPVXJFAHKOOCA5DZKILWC262BANCNFSM6AAAAAARDJPV4U
.
You are receiving this because you authored the thread.Message ID:
@.***>


Support one_file_per_schema for model_props_strategy

We create one file per schema, as opposed to per table. Currently I am manually merging the table-specific data into a single file, but it would be nice for this to happen automatically.
Given that the strategy config exists at all, I assume this is already under consideration for the future!

That's right @joellabes. We already considered different strategies to create model props.
Thanks for pointing it out.

@joellabes this was done now there are 3 options:

One file for the whole project
One file per schema
One file per staging model (combined as it used to be)

Awesome! Thank you for letting me know 🌟

I just realized I didnt explain this well, basically in the config file you can define where the objects are created and this will achieve what you want.
Stay tuned for a video

heads up, I'm seeing this in the output of dbt-coves generate properties -h:
--model-props-strategy MODEL_PROPS_STRATEGY
                        Strategy for model properties file generation, i.e. 'one_file_per_model'

...but there's no explanation in the README.md - basically, I just need to know which values are available for the strategy, and what each of them do
here's where above command line stuff is defined:
https://github.com/datacoves/dbt-coves/blob/f14072d664ddf14c54f7fbb5b26c965b67ca19f2/dbt_coves/tasks/generate/properties.py#L40-L45

heads up, I'm seeing this in the output of dbt-coves generate properties -h:
--model-props-strategy MODEL_PROPS_STRATEGY
                        Strategy for model properties file generation, i.e. 'one_file_per_model'

...but there's no explanation in the README.md - basically, I just need to know which values are available for the strategy, and what each of them do
here's where above command line stuff is defined:
https://github.com/datacoves/dbt-coves/blob/f14072d664ddf14c54f7fbb5b26c965b67ca19f2/dbt_coves/tasks/generate/properties.py#L40-L45

--model-props-strategy was deprecated in favor of --destination usage
We forgot to remove the help message from the command parser, what resulted in the argument being present in -h help message. Thank you for pointing it out.
generate properties aims to generate and update the properties file for a given dbt model file, so with --destination you can place the resultant YML files wherever you need them. https://github.com/datacoves/dbt-coves#properties-generation-arguments
flags {{model_folder_path}} and {{model_file_name}} refer to the SQL containing folder and filename respectively. For example:
--destination {{model_folder_path}}/{{model_file_name}}.yml will create one YML per SQL file at the same level
--destination properties/{{model_file_name}}.yml will create one YML per SQL file in properties folder
--destination {{model_folder_path}}/properties.yml will create a single YML property file at the same level of selected models
and so on...


[stable/concourse] Concourse 5.3.0 Flags

What this PR does / why we need it:
Adds new flags introduced in concourse 5.3.0
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

/retest

/ok-to-test

/lgtm

Sidenote, sorry-- was the imageTag supposed to be updated to 5.3.0 in this PR?
the AppVersion was bumped to 5.3.0 (https://github.com/helm/charts/pull/14292/files#diff-459fb13dcf5560eb0c9f742a9d5109deR4)
https://github.com/helm/charts/blob/master/stable/concourse/values.yaml#L22

damnnn, we do that every single time hahah - I guess this is something that we should be paying more attention to ...
Internally, we're never really caught by this as we use digests, but this can be quite annoying for others 😞
Thanks for spotting it, @aegershman !

Will create a new issue for this if needed, but--
Is there an intended way to use this? Here's a trimmed down example:
concourse:
  web:
    externalUrl: "https://concourse.example.com"
    letsEncrypt:
      enabled: true

web:
  ingress:
    enabled: true
    hosts:
    - concourse.example.com

and pods fail to start due to the following message:
kubectl -n concourse-external logs -f concourse-external-web-84d86b5b55-bnpgq
1 error occurred:
        * must specify --tls-bind-port to use TLS

but the only way to specify tls-bind-port is to turn on concourse.web.tls.enabled=true, which will then require you to provide secrets.webTlsCert and secrets.webTlsKey, despite the fact that it's supposed to be auto-generated by certbot...?
Any thoughts?

hmmmm as far as I can tell, the letsencrypt integration would only work without the use of ingress as web would be the thing doing the TLS termination, instead of the ingress controller 🤔
Anyway, I think it's good to have an issue so we can discuss and, in the "worst" case, come up with documentation that lets users know how to properly make use of it 😁
Thanks again, @aegershman !

Sure thing, I opened an issue about it https://github.com/helm/charts/issues/14867 I'll play around w/ it a bit more later


Sonoff SPM with the Relay BUS module

I'm using this integration and I successfully integrate this device sonoff SPM but when I use the virtual buttons in the HA the device doesn't report de correctly states
And some times the status keeps wrong...
Is there any way to try solve this issue?
Thank you for your support and best regards

You need to provide more useful info

You need to provide more useful info

Ok what more info do you need the logs? Or something to test like a task?

I have the same problem. I'm using SPM integration, when I use HA control to turn ON, the devices turn on, but in a few seconds, the HA Buttons, return to off, and device still on. I think is some problem with synchronization status on entity. I try to use device button ( hardware button ), and status in HA about entity works fine.

SPM support improved in the latest release https://github.com/AlexxIT/SonoffLAN/releases/tag/v3.5.0
Please reopen the issue if there are still any problems


makes Single.error() return a Single

A Single produced by Single.error() should be assignable to any Single<T> type.
const willAlwaysError = Single.error(new Error());
const mySingle: Single<Foo> = willAlwaysError; // <-- this should always typecheck

This PR changes the default value of Single.error's type param to be never, making it assignable to any Single<T> type.
This is the direct analogy of the default of never (same as empty) in TypeScript's Promise.reject:
reject<T = never>(reason?: any): Promise<T>;

I also have a branch ready for a PR on DefinitelyTyped: https://github.com/DefinitelyTyped/DefinitelyTyped/compare/master...hearnden:rsocket-single-error?expand=1

Thanks @hearnden for the improvement!
Based on my limited knowledge in Flow, this looks good to me.


CE App Container Plug-in Driver doc

Per Chirag - PRing this doc for future release.

Docs Build status updates of commit b610090:
:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/windows-ce-app-container-driver-getting-started.md
:warning:Warning

Details

windows-iotcore/media/WindowsCEAppContainer/image3.png
:white_check_mark:Succeeded

windows-iotcore/media/WindowsCEAppContainer/image4.png
:white_check_mark:Succeeded

windows-iotcore/windows-ce-app-container-driver-getting-started.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1e5afe2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/media/WindowsCEAppContainer/image3.png
:white_check_mark:Succeeded

windows-iotcore/media/WindowsCEAppContainer/image4.png
:white_check_mark:Succeeded

windows-iotcore/windows-ce-app-container-driver-getting-started.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[libdef] prismic.io v3.x.x

Caveat: I decided to support the latest promise API.  We can extend the definitions to include the optional callback mechanism if there is demand for it.

Resolves #179

Thanks for the tips.  I've done this.  I see the build is failing, but it's due to an issue with i18next definitions.

I just pushed https://github.com/flowtype/flow-typed/commit/9141ae363c91b2c2e258e1e883aecbc1321dec1c if you want to rebase on top of it to get a clean build

(otherwise we can just verify with the build results -- should auto-merge cleanly anyway)

Please don't be afraid to be as OCD as you like with reviewing my definition.  I appreciate any type of corrections at all as I plan to be writing lots more definitions. :)

awesome!


Home Assitant Compatible ?

Hey, I was wondering if this package was compatible with Home Assistant, I would love to use it with this app ! :D

Hi, sorry this package is for homebridge only. Code is not too big so it may be easy to adapt for homeassistant except that homeassistant is written in python and homebridge in JavaScript.
For the moment I don’t use this lamp anymore so it’s not my priority to make this but maybe a day on my spare time...
Anyway you can look into it if you know how to program. Code is quite simple.


Ensure that we don't explicitly check user roles

Instead, we should rely on policies for this purpose.
It'll allow us easier add new roles in the future.

We can just grep for has_role? to find places where do we use it


Cancel emits an error instead of a next event

I'm not sure if is it good to send an Error event when use cancels during picking an image.
Even more, my app crash when I press cancel, what is the reason?

fatal error: Binding error to variable: canceled: file /Users/adamsmaka/Dropbox/Projects/TakeActionInspire/Pods/RxCocoa/RxCocoa/RxCocoa.swift, line 154

Hey @adamsmaka

I can't reproduce this on the demo project. Did you do anything specific here with code you could share? Also, is this simulator or device ?

I don't think there's a problem with sending an error for a cancel event, there's no "Result" in this case. But i'm open to suggestions on changing if the community feels it shouldn't be this way.

Oh yes it was my mistake. I did something like this, and in Error case, it crashed the app.
newImageObs             .subscribeOn(MainScheduler.instance)             .bind(to: goalImage)             .addDisposableTo(self.bag)
I don't think that canceling action should emit error :) I would rather expect it when a camera is not available or something like that.

@adamsmaka bind is not Error-compatible. You have to take care that errors are handled before binding, for example by doing
newImageObs.subscribeOn(MainScheduler.instance)
           .catchErrorJustReturns(nil)
           .bind(to: goalImage)
           .disposed(by: self.bag)

thank you, im still newbie with RxSwift 👍

@adamsmaka
Two things

I renamed the issue to reflect your current question
If there's a consensus of changing this (a few more members) to a next event we can do that. To be honest I think an error event makes sense (you can't have any more emissions after the user cancels the dialog which makes sense to me)

changing this (a few more members) to a next event we can do that

.completed maybe, definitely not .next, but that may be a bit inconvenient as now it'll be unclear (without additional actions) why it was completed :smile:
I'd say this is misusage and issue can be closed.

I prefer Error as an event since completed happens after selecting an asset and not exclusively for cancel so it's hard to target that specific event.
Moving to Single later on will make this more important in that case, since it will only have a single success event.
I think I'm gonna close this for the time being but if a good reason to change this will come up, we can rediscuss.
Thanks for the feedback @vhbit !


Token Cloning: TokenDocument5e#actorData Error

The Token cloning is "sort of" broken for several months now. It throws errors if a token is cloned.

The cloning function allows to clone a token from a source drawing to a destination drawing. That is used to show tokens that should be seen on your scene but AREN'T on your scene (For example if you are in the second floor map and "should" see someone on the first floor map. MLT uses the same drawings as it uses for the teleportation but just clones from source to destination.

Every time you move a token in the "source" drawing area a TokenDocument Error is thrown.
localhost-1718376971541.log
https://github.com/BeneosBattlemaps/Beneos-Multilevel-Tokens/assets/93905181/ab442c59-ba50-4eee-903e-5b828700a6db

Sorry, I do not see the issue here. The token copy function is working. The warning in the console are not due to Multilevel Tokens at all, seems related to libWrapper. Hence the bug must be redirected to the libWrapper module.


Improve discoverability of the default 101 byte partition key hashing limit

Hi,
We have just been caught out by the 101byte limit if large partitions are not enabled.
As per https://learn.microsoft.com/en-us/azure/cosmos-db/large-partition-keys?tabs=dotnetv3#supported-sdk-versions
This restriction is not clearly called out in the documentation in other sections that explain the partition key and therefore rely on you having read all documentation in detail and not just the sections that appear relevant.
e.g.

Uniqueness of the id property is enforced within each logical partition. Multiple documents can have the same id property with different partition key values.

Does not explain that it is only 101bytes of the partition key by default (on Azure Portal created containers)
To avoid anyone having a similar issue that took us a long time to discover the root cause can:

The docs be updated in the various places to call this out like this explicit comment that can be false but also maybe worth at least linking in the https://learn.microsoft.com/en-us/azure/cosmos-db/partitioning-overview and especially calling it out in the limits https://learn.microsoft.com/en-us/azure/cosmos-db/concepts-limits#per-item-limits that make it appear like you have a full 2048 bytes available.
Update the docs at the learn more link for the unintuitive 403 error should you not enable it, but accidentally end up with a large composite key.

Forbidden (403); Substatus: 0; ActivityId: 471c06de-41fa-4163-951b-ce4a59bbe0ea; Reason: (Message: {"Errors":["Request is blocked. Please check your authorization token and Cosmos DB account firewall settings. Learn more: https://aka.ms/cosmosdb-tsg-forbidden"]}
ActivityId: 471c06de-41fa-4163-951b-ce4a59bbe0ea, Request URI: /apps/f4a8289a-6ec1-4489-bd84-6cb661ea7acc/services/e7908fe1-b3dd-4baf-9d79-d421b2680bd3/partitions/dc85d127-10a3-45f0-9e17-a267caf08e8e/replicas/133149777014528418p/, RequestStats: Microsoft.Azure.Cosmos.Tracing.TraceData.ClientSideRequestStatisticsTraceDatum, SDK: Windows/10.0.14393 cosmos-netstandard-sdk/3.28.2);

Also should a separate ticket be raised somewhere (where?) to improve the cosmos error itself to better explain that the 403 is nothing to do with the auth token or firewall?

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

ID: af9dbd47-fa87-2e2b-c359-820c51603c1e
Version Independent ID: 6fb95e4c-4472-022e-4198-8e3c0f76c40a
Content: Azure Cosmos DB resource model
Content Source: articles/cosmos-db/account-databases-containers-items.md
Service: cosmos-db
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

@Euan-McVie Thank you for reaching out. We will look into it and update you as appropriate.

Hello @Euan-McVie, I generally agree with your points here. Once the holidays are over, we'll take a look at the docs and put together an update to include this information much earlier so less people will be caught by surprise.
Thanks for this feedback!

Hello @Euan-McVie, we have a change that will publish this week that clarifies this in two places:

The partitioning overview now mentions the limit. The best practice is to enable large partition keys for new containers. If you have a container that existed prior to this change (sometime in 2019), you may not have large partition keys enabled.
The per-item limits page now mentions the limit as a note. Again, the value is 2048, but it's 101 if you have an older container or opted-out of large partition keys.

I hope this helps. If you want to submit feedback about the error message, I recommend opening a support request to update the error message.


feat: allow user to override blop sound on first boot volume change

https://github.com/OpenVoiceOS/ovos-PHAL-plugin-alsa/blob/da06817ddd9d03c0dcf611f05d5fa6fa36cd294f/ovos_PHAL_plugin_alsa/__init__.py#L54
set_volume() does have a play_sound option but there is no way to set it in the code as it is now
Create a config option, defaulting to true, that allows users to disable the initial blop sound when booting
Per Matrix chat: https://matrix.to/#/!ZhEZYNzKBfpEAhtQIz:matrix.org/$279GVdCG20Gv3dG-3fZ449YGnQlulOyS0g3-eMgpWH8?via=matrix.org&via=nitro.chat&via=strugee.net

this only happens on very first boot, should not really be configurable
i think the source of your issue is not the place you linked, but a bus message emitted from somewhere else

@JarbasAl You're right... if the user wants to configure it, they can edit ~/.config/OpenVoiceOS/ovos-PHAL-plugin-alsa.json, although that's kind of a weird place to do it.
I think the source of the Neon-reported issue is when Neon updates the Mark 2, it may be removing or overwriting that file, causing it to play the blop sound every time it updates.

Although closed, if indeed the NEON update overwrites user config files, that might be a proper bug to report to that update system.
I believe a system update should not overwrite user config files?

issue comes from https://github.com/OpenVoiceOS/ovos-shell/blob/master/application/qml/panel/quicksettings/VolumeSlider.qml
when shell loads it requests volume value (for the slider)
Connections {
        target: Mycroft.MycroftController
        onSocketStatusChanged: {
            if (Mycroft.MycroftController.status == Mycroft.MycroftController.Open) {
                Mycroft.MycroftController.sendRequest("mycroft.volume.get", {},
                    {"session": {"session_id": "default"}});
            }
        }
        onIntentRecevied: {
            if (type == "mycroft.volume.get.response") {
                slider.value = Math.round(data.percent * 100);
            }
        }
    }
}

when value changes in the slider, it emits a bus event for the alsa plugin
 onChangeValueChanged: {
        Mycroft.MycroftController.sendRequest("mycroft.volume.set", {"percent": (changeValue / 100)},
            {"session": {"session_id": "default"}});
    }

whenever something "reads" the volume from the alsa plugin the shell "sets" alsa volume to that same value again
the listener for the .get.response should not trigger the "mycroft.volume.set" , the shell needs better event handling


Create doctor command to fix repo_units broken by dumps from 1.14.3-1.14.6

There was a serious issue with the gitea dump command in 1.14.3-1.14.6 which led to corruption of the config field of the repo_unit table.
This PR adds a doctor command to attempt to fix the broken repo_units. Users affected by #16961 should run:
gitea doctor --fix --run fix-broken-repo-units

Fix #16961
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@868e937). Click here to learn what that means.
The diff coverage is 37.91%.

@@           Coverage Diff           @@
##             main   #17136   +/-   ##
=======================================
  Coverage        ?   45.27%
=======================================
  Files           ?      775
  Lines           ?    87223
  Branches        ?        0
=======================================
  Hits            ?    39492
  Misses          ?    41324
  Partials        ?     6407

Impacted Files
Coverage Δ

models/helper.go
52.94% <0.00%> (ø)

models/repo_unit.go
84.52% <0.00%> (ø)

modules/doctor/fix16961.go
38.76% <38.76%> (ø)

Continue to review full report at Codecov.

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

make lgtm work