Grafana Alloy UI freezes, stops not displaying targets for discovery.kubernetes

What's wrong?

Alloy UI freezes and does not display the information.
I suspect that this is related to CPU/Mem, however the QoS for the DeamonSets are set to Burstable with sufficient CPUs and RAM available for higher load. We are using the default configurations for the resource allocation and deployed Alloy as Deamonsets to EKS cluster.
The number of targets is relatively small (250 Pods).
Steps to reproduce
Install Grafana Helm Chart v0.3.2 with the values.yaml to EKS cluster version v1.27.
System information
EKS v1.27
Software version
Grafana Alloy v0.3.2
Configuration
# -- Overrides the chart's name. Used to change the infix in the resource names.
nameOverride: null

# -- Overrides the chart's computed fullname. Used to change the full prefix of
# resource names.
fullnameOverride: null

## Global properties for image pulling override the values defined under `image.registry` and `configReloader.image.registry`.
## If you want to override only one image registry, use the specific fields but if you want to override them all, use `global.image.registry`
global:
  image:
    # -- Global image registry to use if it needs to be overriden for some specific use cases (e.g local registries, custom images, ...)
    registry: ""

    # -- Optional set of global image pull secrets.
    pullSecrets: []

  # -- Security context to apply to the Grafana Alloy pod.
  podSecurityContext: {}

crds:
  # -- Whether to install CRDs for monitoring.
  create: true

## Various Alloy settings. For backwards compatibility with the grafana-agent
## chart, this field may also be called "agent". Naming this field "agent" is
## deprecated and will be removed in a future release.

alloy:
  configMap:
    # -- Create a new ConfigMap for the config file.
    create: true
    # -- Content to assign to the new ConfigMap.  This is passed into `tpl` allowing for templating from values.
    content: |-
      // config.alloy
      // Reference: https://grafana.com/docs/alloy/latest/reference/components

      // Meta Monitoring Logs - https://grafana.com/docs/alloy/latest/tasks/metamonitoring
      logging {
        level    = "info"
        format   = "logfmt"
        write_to = [loki.write.default.receiver]
      }

      // Meta Monitoring Metrics - https://grafana.com/docs/alloy/latest/tasks/metamonitoring
      prometheus.exporter.self "alloy_meta_monitoring" {
      }

      // Kubernetes Pod Discovery
      discovery.kubernetes "pods" {
        role = "pod"
        enable_http2 = false
      }

      // Kubernetes Pod Targets Relabel Config
      discovery.relabel "logs" {

        targets = discovery.kubernetes.pods.targets

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_namespace"]
          target_label  = "namespace"
        }

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_pod_name"]
          target_label  = "pod"
        }

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_pod_container_name"]
          target_label  = "container"
        }

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_pod_label_app_kubernetes_io_name"]
          target_label  = "app"
        }

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_pod_node_name"]
          target_label  = "node"
        }

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_pod_container_image"]
          target_label  = "container_image"
        }

        rule {
          action = "replace"
          source_labels = ["__meta_kubernetes_pod_ready"]
          target_label  = "pod_status"
        }
      }

      // Loki Source
      loki.source.kubernetes "pods" {
        targets    = discovery.kubernetes.pods.targets
        forward_to = [loki.write.default.receiver]
      }

      // Kubernetes Events
      loki.source.kubernetes_events "k8s_events" {
        log_format = "logfmt"
        forward_to = [loki.write.default.receiver]
      }

      // Loki Write Config
      loki.write "default" {
        endpoint {
          name = "Loki"
          url = "http://grafana-loki-gateway/loki/api/v1/push"
          basic_auth {
            username = "grafana_cloud"
            password = "grafana_cloud_test_password"
          }
          tenant_id = "apps"
        }
      }

    # -- Name of existing ConfigMap to use. Used when create is false.
    name: null
    # -- Key in ConfigMap to get config from.
    key: null

  clustering:
    # -- Deploy Alloy in a cluster to allow for load distribution.
    enabled: true

    # -- Name for the port used for clustering, useful if running inside an Istio Mesh
    portName: http

  # -- Minimum stability level of components and behavior to enable. Must be
  # one of "experimental", "public-preview", or "generally-available".
  stabilityLevel: "public-preview"

  # -- Path to where Grafana Alloy stores data (for example, the Write-Ahead Log).
  # By default, data is lost between reboots.
  storagePath: /tmp/alloy

  # -- Address to listen for traffic on. <IP_ADDRESS> exposes the UI to other
  # containers.
  listenAddr: <IP_ADDRESS>

  # -- Port to listen for traffic on.
  listenPort: 12345

  # -- Scheme is needed for readiness probes. If enabling tls in your configs, set to "HTTPS"
  listenScheme: HTTP

  # --  Base path where the UI is exposed.
  uiPathPrefix: /

  # -- Enables sending Grafana Labs anonymous usage stats to help improve Grafana
  # Alloy.
  enableReporting: true

  # -- Extra environment variables to pass to the Alloy container.
  extraEnv: []

  # -- Maps all the keys on a ConfigMap or Secret as environment variables. https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#envfromsource-v1-core
  envFrom: []

  # -- Extra args to pass to `alloy run`: https://grafana.com/docs/alloy/latest/reference/cli/run/
  extraArgs: []

  # -- Extra ports to expose on the Alloy container.
  extraPorts: []
  # - name: "faro"
  #   port: 12347
  #   targetPort: 12347
  #   protocol: "TCP"

  mounts:
    # -- Mount /var/log from the host into the container for log collection.
    varlog: false
    # -- Mount /var/lib/docker/containers from the host into the container for log
    # collection.
    dockercontainers: false

    # -- Extra volume mounts to add into the Grafana Alloy container. Does not
    # affect the watch container.
    extra: []

  # -- Security context to apply to the Grafana Alloy container.
  securityContext: {}

  # -- Resource requests and limits to apply to the Grafana Alloy container.
  resources: {}

image:
  # -- Grafana Alloy image registry (defaults to docker.io)
  registry: "docker.io"
  # -- Grafana Alloy image repository.
  repository: grafana/alloy
  # -- (string) Grafana Alloy image tag. When empty, the Chart's appVersion is
  # used.
  tag: null
  # -- Grafana Alloy image's SHA256 digest (either in format "sha256:XYZ" or "XYZ"). When set, will override `image.tag`.
  digest: null
  # -- Grafana Alloy image pull policy.
  pullPolicy: IfNotPresent
  # -- Optional set of image pull secrets.
  pullSecrets: []

rbac:
  # -- Whether to create RBAC resources for Alloy.
  create: true

serviceAccount:
  # -- Whether to create a service account for the Grafana Alloy deployment.
  create: true
  # -- Additional labels to add to the created service account.
  additionalLabels: {}
  # -- Annotations to add to the created service account.
  annotations: {}
  # -- The name of the existing service account to use when
  # serviceAccount.create is false.
  name: null

# Options for the extra controller used for config reloading.
configReloader:
  # -- Enables automatically reloading when the Alloy config changes.
  enabled: true
  image:
    # -- Config reloader image registry (defaults to docker.io)
    registry: "ghcr.io"
    # -- Repository to get config reloader image from.
    repository: jimmidyson/configmap-reload
    # -- Tag of image to use for config reloading.
    tag: v0.12.0
    # -- SHA256 digest of image to use for config reloading (either in format "sha256:XYZ" or "XYZ"). When set, will override `configReloader.image.tag`
    digest: ""
  # -- Override the args passed to the container.
  customArgs: []
  # -- Resource requests and limits to apply to the config reloader container.
  resources:
    requests:
      cpu: "1m"
      memory: "5Mi"
  # -- Security context to apply to the Grafana configReloader container.
  securityContext: {}

controller:
  # -- Type of controller to use for deploying Grafana Alloy in the cluster.
  # Must be one of 'daemonset', 'deployment', or 'statefulset'.
  type: 'daemonset'

  # -- Number of pods to deploy. Ignored when controller.type is 'daemonset'.
  replicas: 1

  # -- Annotations to add to controller.
  extraAnnotations: {}

  # -- Whether to deploy pods in parallel. Only used when controller.type is
  # 'statefulset'.
  parallelRollout: true

  # -- Configures Pods to use the host network. When set to true, the ports that will be used must be specified.
  hostNetwork: false

  # -- Configures Pods to use the host PID namespace.
  hostPID: false

  # -- Configures the DNS policy for the pod. https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy
  dnsPolicy: ClusterFirst

  # -- Update strategy for updating deployed Pods.
  updateStrategy: {}

  # -- nodeSelector to apply to Grafana Alloy pods.
  nodeSelector: {}

  # -- Tolerations to apply to Grafana Alloy pods.
  tolerations: []

  # -- Topology Spread Constraints to apply to Grafana Alloy pods.
  topologySpreadConstraints: []

  # -- priorityClassName to apply to Grafana Alloy pods.
  priorityClassName: ''

  # -- Extra pod annotations to add.
  podAnnotations: {}

  # -- Extra pod labels to add.
  podLabels: {}

  # -- Whether to enable automatic deletion of stale PVCs due to a scale down operation, when controller.type is 'statefulset'.
  enableStatefulSetAutoDeletePVC: false

  autoscaling:
    # -- Creates a HorizontalPodAutoscaler for controller type deployment.
    enabled: false
    # -- The lower limit for the number of replicas to which the autoscaler can scale down.
    minReplicas: 1
    # -- The upper limit for the number of replicas to which the autoscaler can scale up.
    maxReplicas: 5
    # -- Average CPU utilization across all relevant pods, a percentage of the requested value of the resource for the pods. Setting `targetCPUUtilizationPercentage` to 0 will disable CPU scaling.
    targetCPUUtilizationPercentage: 0
    # -- Average Memory utilization across all relevant pods, a percentage of the requested value of the resource for the pods. Setting `targetMemoryUtilizationPercentage` to 0 will disable Memory scaling.
    targetMemoryUtilizationPercentage: 80

    scaleDown:
      # -- List of policies to determine the scale-down behavior.
      policies: []
        # - type: Pods
        #   value: 4
        #   periodSeconds: 60
      # -- Determines which of the provided scaling-down policies to apply if multiple are specified.
      selectPolicy: Max
      # -- The duration that the autoscaling mechanism should look back on to make decisions about scaling down.
      stabilizationWindowSeconds: 300

    scaleUp:
      # -- List of policies to determine the scale-up behavior.
      policies: []
        # - type: Pods
        #   value: 4
        #   periodSeconds: 60
      # -- Determines which of the provided scaling-up policies to apply if multiple are specified.
      selectPolicy: Max
      # -- The duration that the autoscaling mechanism should look back on to make decisions about scaling up.
      stabilizationWindowSeconds: 0

  # -- Affinity configuration for pods.
  affinity: {}

  volumes:
    # -- Extra volumes to add to the Grafana Alloy pod.
    extra: []

  # -- volumeClaimTemplates to add when controller.type is 'statefulset'.
  volumeClaimTemplates: []

  ## -- Additional init containers to run.
  ## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
  ##
  initContainers: []

  # -- Additional containers to run alongside the Alloy container and initContainers.
  extraContainers: []

service:
  # -- Creates a Service for the controller's pods.
  enabled: true
  # -- Service type
  type: ClusterIP
  # -- NodePort port. Only takes effect when `service.type: NodePort`
  nodePort: 31128
  # -- Cluster IP, can be set to None, empty "" or an IP address
  clusterIP: ''
  # -- Value for internal traffic policy. 'Cluster' or 'Local'
  internalTrafficPolicy: Cluster
  annotations: {}
    # cloud.google.com/load-balancer-type: Internal

serviceMonitor:
  enabled: false
  # -- Additional labels for the service monitor.
  additionalLabels: {}
  # -- Scrape interval. If not set, the Prometheus default scrape interval is used.
  interval: ""
  # -- MetricRelabelConfigs to apply to samples after scraping, but before ingestion.
  # ref: https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#relabelconfig
  metricRelabelings: []
  # - action: keep
  #   regex: 'kube_(daemonset|deployment|pod|namespace|node|statefulset).+'
  #   sourceLabels: [__name__]

  # -- Customize tls parameters for the service monitor
  tlsConfig: {}

  # -- RelabelConfigs to apply to samples before scraping
  # ref: https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#relabelconfig
  relabelings: []
  # - sourceLabels: [__meta_kubernetes_pod_node_name]
  #   separator: ;
  #   regex: ^(.*)$
  #   targetLabel: nodename
  #   replacement: $1
  #   action: replace
ingress:
  # -- Enables ingress for Alloy (Faro port)
  enabled: false
  # For Kubernetes >= 1.18 you should specify the ingress-controller via the field ingressClassName
  # See https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/#specifying-the-class-of-an-ingress
  # ingressClassName: nginx
  # Values can be templated
  annotations:
    {}
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  labels: {}
  path: /
  faroPort: 12347

  # pathType is only for k8s >= 1.1=
  pathType: Prefix

  hosts:
    - chart-example.local
  ## Extra paths to prepend to every host configuration. This is useful when working with annotation based services.
  extraPaths: []
  # - path: /*
  #   backend:
  #     serviceName: ssl-redirect
  #     servicePort: use-annotation
  ## Or for k8s > 1.19
  # - path: /*
  #   pathType: Prefix
  #   backend:
  #     service:
  #       name: ssl-redirect
  #       port:
  #         name: use-annotation

  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

Logs
No response

Related: https://github.com/grafana/alloy/issues/515


Bump version to 0.2.0

Codecov Report

Merging #87 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #87   +/-   ##
=======================================
  Coverage   51.26%   51.26%
=======================================
  Files          87       87
  Lines        4237     4237
=======================================
  Hits         2172     2172
  Misses       2065     2065

Impacted Files
Coverage Δ

mlflow/version.py
100% <100%> (ø)
:arrow_up:

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 86f9d07...bebd753. Read the comment docs.


chore(workspace): reorganize binary example programs

#294  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @refcell and the rest of your teammates on  Graphite


Add trove classifier + entry in third-party packages

I suggest adding the Framework :: Matplotlib classifier (https://discourse.matplotlib.org/t/framework-matplotlib-trove-classifier/20927) to your setup.py and adding your package to https://github.com/matplotlib/matplotlib/blob/master/doc/thirdpartypackages/index.rst .

Good advice thanks! I will close this once I have publish on pypi and added the package to that listing.


[RevEng] Error running "scaffold-dbcontext"

Using SQLCE provider with build: beta8-15719 I get this error when running scaffolding - any idea what could be causing this? (The beta 7 bits on NuGet work fine)
PM>  Scaffold-DbContext -Connection "Data Source=C:\data\Chinook.sdf" -Provider EntityFramework.SqlServerCompact40
Scaffold-DbContext : Exception calling "CreateInstance" with "8" argument    (s): "Type 'System.Management.Automation.SwitchParameter' in assembly 'System.Management.Automation, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' is not marked as serializable."
At line:1 char:2
+  Scaffold-DbContext -Connection "Data Source=C:\data\Chinook.sdf" -Provider Enti ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Scaffold-DbContext], MethodInvocationException
+ FullyQualifiedErrorId : SerializationException,Scaffold-DbContext

@ErikEJ  Are you able to do any other command e.g. a migration command? If not it's probably that something's changed about Activator.CreateInstance().

@lajones Yes, I am:
 PM> add-migration first
 No DbContext was found. Ensure that you're using the correct assembly and that the type is neither abstract nor generic.

Hmmm. Not sure. I'll investigate.

@lajones  Please let me know if I can provide any more info! The test project is a .NET 4.5 Console app.

@ErikEJ - will do. As a workaround does it works from the command line?

Does the command line work with a csproj project?

@ErikEJ - you'd need to have a project.json to use the command line. But I think I found the problem - I'll post a PR.

@ErikEJ - I checked in a fix - so closing. But if you still have problems please re-open.

@lajones Excellent - thanks for the quick response! :smile:


Too many, and too confusing kinds of candidates

I need to state what classes should continue to exist, and which ones can be deleted.

In the Rating model we have the following options for the candidate types:
CAND_TYPE_CHOICES = (
    (T, "Transient"),
    (AP, "Airplane"),
    (RFI, "RFI"),
    (SL, "Sidelobe"),
    (A, "Alias"),
    (CC, "CHG Centre"),
    (S, "Scintillation"),
    (P, "Pulsar"),
    (AGN, "AGN"),
    (D, "Drift"),
    (BF, "Bad Frame"),
    (O, "Other"),
)

The abbreviations and descriptions can be updated, delete, expanded, and we can have some reserved "ex1, ... , ex2" types that the user can define via the app.

This might be overkill, but if these choices are turned into a bona fide model, then we (i.e. Natasha and I) can grow and shrink the list ourselves without needing to deal with any more migrations in the future. More effort now, less effort later.

Good idea, that would be much nicer than the categories of ex1... ex2 that I suggested earlier.
I'll make a todo:

[ ] Convert the classification choices into a model which is a fk in the current ratings model.

In branch 24-custom-candidates the list of candidate classification options has been turned into a model called Classification, which works much like the Project tag that was added to the candidates table (see #22/#28).
Users can create/edit/delete Classification labels using the admin interface. Each classification has a (unique) name and a description. The name is what is displayed through most of the app, and it is recommended that this name be short to avoid strangely wide drop down menus.
Currently the classifications are not bound to a project (they are "global"), but it is possible to set this up if it is required.

[ ] Cause classifications to be 'enabled' on a per project basis. Eg not all classifications are visible to all projects by default.


Add Binary search tree documentation

Description
Step by step explanation of Search, Insertion, Deletion in Binary Search Trees with clean and concise code and complexity analysis(Both time and space complexity)
Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

Are you contributing under any open-source program ?
Hacktoberfest 2021

@girija0707 @siddhi-244 please assign this to me under hacktoberfest 2021

@siddhi-244 Kindly review and accept my PR.


Preset not loaded after put at directory

Tapad should load it automatically, or have a choice to refresh preset list.

It doesn't show at the installed tab on preset store?
On Sun, Jul 2, 2017, 10:28 AM Desperate_Kun<EMAIL_ADDRESS>wrote:

Tapad should load it automatically, or have a choice to refresh preset
list.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/berict/Tapad/issues/144, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMrq_cMX5ZGmkuTxu1P8QBiOvfftp2jRks5sJvJIgaJpZM4OLdin
.

On v2.3-alpha.4, you need to set the folder name to preset name
For faded, try alan_walker_faded_gesture
On Sun, Jul 2, 2017, 12:46 PM Bedrock Dev<EMAIL_ADDRESS>wrote:

It doesn't show at the installed tab on preset store?
On Sun, Jul 2, 2017, 10:28 AM Desperate_Kun<EMAIL_ADDRESS>wrote:

Tapad should load it automatically, or have a choice to refresh preset
list.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/berict/Tapad/issues/144, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMrq_cMX5ZGmkuTxu1P8QBiOvfftp2jRks5sJvJIgaJpZM4OLdin
.

trying

Open preset feature will be available


Use correct variant and version in UUID

As pointed out in https://github.com/assaf/uuid/issues/33 , the current implementation does not conform to https://www.ietf.org/rfc/rfc4122.txt with regards to version and variant.
This pull request corrects that by properly setting the variant and version.

Another fork has also addressed this in a slightly different manner: https://github.com/L2G/uuid/commit/17b6a9c3ebb51d5ad80dd03492e480a76f5463ab


Scrollbar not shown when navigating to a scrollable screen

When navigating to a screen, it would be great if it was possible to force show the scrollbar to indicate to the user that the content is scrollable. This should also work in case the content is loaded asynchronously.

cc @BowerSteve any advice here?

Hi - I don't think there's currently a way to force the PI to be shown initially with a ScalingLazyColumn (I seem to recall the UX spec was that it should not be shown until scrolling occurred). However, it's possible to provide a CustomPositionIndicatorState, like in this demo, which controls the Show/Hide visibility:
https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:wear/compose/integration-tests/demos/src/main/java/androidx/wear/compose/integration/demos/PositionIndicatorDemos.kt;l=216?q=file:wear%2Fcompose CustomPosition&sq=&ss=androidx%2Fplatform%2Fframeworks%2Fsupport

Functions are public by default in Kotlin - we normally state it explicitly in Wear/Material, but given that other libraries like Compose/Material omit it, we will also omit the 'public' in future APIs.

Hi, has there been any progress on this feature? My app has got rejected by Google due to missing scrollbar when user enters the screen

When did this happen? That requirement has been removed, so shouldn't have happened this week.
Can you copy the full message?

Happened again to me today:

Issue found: Missing scrollbar
Your app does not display the scroll bar when the user enters a scrollable view and/or when the user scrolls. For more information, see Show the scrollbar.
About the Wear App Quality Guidelines
We do not accept apps into Wear OS that don't adhere to Wear App Quality Guidelines.

It's likely a mistake in the text they sent. And only because of a screen with missing position indicator.

Sorry for the late reply. Here is the rejection message

I have then displayed the position indicator when entering the page and now they are challenging on other things. It means that this is really something that is taken into account during the approuval

ScrollBar should be showed by default in Wear Compose 1.4.0-alpha01


chore: light node test

Improve reliability of test.
Reduce the speed up of test from x10 to x5 to avoid two nodes being out of sync.
Increase the margin for checking blocks deleted since it can change slightly in time due to creation of new blocks.

prnet cleaned-up successfully


add the best tagline I can think of

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@ryanflorence 😄. Or even:

Saving the world from JS fatigue, one React app at a time.

I see no puns in your tagline. I still vote for mine. I like your avatar though.

@ryanflorence yeah, no puns, more tongue-in-cheek (and thanks!)

@facebook-github-bot honestly, I don't think that tagline is much better. What kind of bot are you?!

@facebook-github-bot You're welcome.

I liked the tagline, but in my opinion it shouldn't merged, looks amateur.

I can empathize with the sentiment but I also feel it’s a bit dismissive to all the tools that we build upon. After all we just put them in a nice package but they do all the heavy lifting!

I love how sincere you are. I'm just messing around, I wouldn't want it merged either.

I know but still worth saying it.

Also hope to see more PRs from you!


Flush handlers at the end of the main. Fix for #253.

As handlers are PLAY-scoped and not ROLE-scoped on Ansible.
It could be a good practice to add a meta flush handler
at the end of the main task. So we are sure that the DNS config is up
for next roles in the play.
https://docs.ansible.com/ansible/latest/modules/meta_module.html

Thanks!


<IP_ADDRESS>

https://ci.appveyor.com/project/jpboyce/cb-cis-windows-2016#L1529

Resolved by 9cc4dbe


Handle migration for the increase of CALLBACK_URL DB column size to 2048

Refer https://github.com/wso2/carbon-identity-framework/pull/2135

This is available in IS580 migration


EPERM once per package

When I install a new package, the first attempt fails with an EPERM error. If I re-run the command, the package installs fine. This also happens once for every dependency, so I need to run npm install once per dependency.

https://gist.github.com/1488023 is an npm-debug.log after two consecutive runs of npm install express.

The problem could be in here somewhere:
https://github.com/isaacs/npm/blob/master/lib/utils/tar.js#L253
We've run into some strange issues seeming to stem from this area as well, and a bit wary of the XXX warning at the top :)
cc @mdz @temas


kv-client(ticdc): decrease input buffer, correct watermark calculation

What problem does this PR solve?

Issue Number: ref #7886
What is changed and how it works?

Decrease input buffer size in kv client
Correct watermark calculation in region worker

Manual test

create 5000 empty tables with sysbench
pause cdc changefeed
Write 50GB data to the first 1000 tables with sysbench insert
resume cdc changefeed

Observation:

Unified sorter behaves much better (in memory usage) than db sorter, in the following graph, <IP_ADDRESS>:8031 uses db sorter, <IP_ADDRESS>:8302 uses unified sorter

Decrease input buffer size in kv client can reduce the risk of OOM, while it depends the cdc server configuration, including sorter.max-memory-percentage

About average events batch size in kv client, ranges from 1 to 64, where 64 happens in incremental scan scenario mostly.

5000 small tables

14:01-14:09 was incremental scan with 50GB data;
14:16-14:22 was normal replication with 15K QPS in upstream

3 large tables, with regions count 6000, 15000, 50000 respectively

16:56-17:22, run sysbench insert workflow with 13K QPS in upstream.
17:23-17:28, remove changefeeed, re-create a changefeed to incremental scan with 40GB data.

Conclusion

Since we won't maintain db sorter(in actor mode) after v6.5.1, we tend to use the following workaround in this scenario

Use a smaller sorter.max-memory-percentage
Set debug.enable-db-sorter to false to disable db sorter and use unified sorter.

The change in kv client doesn't have performance regression, based on some benchmark.

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/hold

/run-all-tests

/unhold

/run-all-tests

/merge

/run-verify


Justify Items and Justify Self

Report

[x] I have searched existing issues and this is not a duplicate

Issues and Steps to Reproduce
This project does not support the justify items and justify self properties MDN. All browsers since IE11 support this
I think the logic is pretty much the same as align items, so it might be possible to repurpose that code
Expected Behavior
Not relevant
Actual Behavior
Not relevant
Link to Code
Not relevant

Any status on this?

Any status on this?

It supports justify-items now, and I was wrong on justify-self - that only applies to grid items, not flex items (which is the only thing Yoga supports)


Add stats for prod104 release

See title.

I'm not sure if we're waiting for after the release, in case release date needs changing. /cc @francesw


Test on commit 26d03b6 to skip replay tests

Split tests to sql and non-sql to speed up
Revert the commit which make replay tests failed
To use leveldbjni-all.1.8 of org.openlabtesting.leveldbjni
To increase time of some tests to make them pass

recheck

recheck


Web dashboard

Like MEE6 and Dyno have

soon will be added

When is "soon"?

Idea: Make a dashboard, where people can create there own dashboard without any coding knowledge, so just filling in the mongodb url and discord bot token!
What you guys think of it?

YEEESSS PLSSSS

I like to contribute this enhancement.

Yes please

Where is it?


How to upload my translation?

Edit: Can someone tell me whether I did in pull request was right?

Yes, it's fine. Thank you.


Tile type 'B' and 'b' not defined in Super Mario Bros / Processed levels

Tiles of type 'B' and 'b' are not defined in smb.json, but are required by some levels.

Hi! If you are referring to the maps in the "Super Mario Bros" folder, "B" and "b" are not used in the maps in the "processed" folder, right? They do appear in the "Multi-layer" folder, but for maps in that folder you have the "smb-multi-layer.json" file that defines additional needed types.

Hi :)
The ‘mario-7-1.txt’ level contains ‘B’ and ‘b’ tiles.

Oh, I missed that one. Those are cannons! Sam and Adam might know better, but I think the .json file should be extended with these two lines there (I took these lines from the multilayered version, where they are "C" and "c", but I think it should be the same):
"B" : ["Cannon top","cannon","solid","hazard"],
"b" : ["Cannon bottom","cannon","solid"]

Sam? Adam?

Thank you for the help! I will use your solution at the moment, seems working fine.


Password has requirements, but requirements are not listed for user

need at least one uppercase letter, lowercase letter and number


'<EMAIL_ADDRESS>is not in the npm registry

Description
Next js related repositories are not registered to install via npm or yarn
Steps to reproduce
clone this repo, go to tinacms/packages/demo-next and run yarn install
Actual result
error An unexpected error occurred: "https://registry.yarnpkg.com/@tinacms%2fnext-tinacms-git: Not found".
info If you think this is a bug, please open a bug report with the information provided in "tinacms/packages/demo-next/yarn-error.log".

Hey @dmouse! Thanks for the report
Running yarn install from inside packages is not recommended. Checkout the README for how to get started running the demo sites locally.
As an aside next-tinacms-git does not meet our standards for general applicability, that's why it's not published to NPM. You can still use it in the demo site though!
I'm going to close this ticket, and I'll update the README to be a bit more explicit.


zar: initial support of s3

Use pkg iosrc when opening/creating files within zar, allowing zar
directories to be accessed via origins other than the local filesystem.
Also:

iosrc.URI: A struct for unifying file paths and url paths so that
operations like AppendPath will work for all supported path types.

A few initial thoughts:

As a phasing strategy, let's first support storing metadata for an archive as a local file, and not in s3. That will prevent AtomicWrite & Rename on the io sources, and we can figure out if/how we want to store & version metadata in s3.
During import of data, let's add the size of the individual zng files into the metadata info. This will prevent needing to Stat() (or s3 equivalent) the log files, and makes sense for us anyway, since these files will be immutable.

@alfred-landrum

As a phasing strategy, let's first support storing metadata for an archive as a local file, and not in s3. That will prevent AtomicWrite & Rename on the io sources, and we can figure out if/how we want to store & version metadata in s3.

This works be we would need to add a zar import option that would specify placing data files in a different location.

@alfred-landrum et al, this is ready for review. I still need to add some kind of s3 related zar and zar zqd tests. Working on that.


Release 1.1.2

Version 1.1.0
QuickUMLS
MedspaCy QuickUMLS (v3.0) is now installed by default on Windows!
Dependencies for this previously were challenging and required both conda and pip.  Now this all installs via pip.
Tests are updated so that these run on Windows.
Several areas of documentation have been updated to reflect.
Huge thanks to Jianlin Shi, and the developers of pysimstring (Luca Soldaini, Perceval Wajsburt, and any others) who made this possible.
Other
Fixed issues where an exception could be thrown in some components if set_extension() was called twice, such as when re-creating a component in a jupyter notebook.
Reverted a default success_value to True for Postprocessing rules to align with previous versions.
Added to_json method to ConText rules.
Prevented spacy v4 or later from being installed.
Fixed some documentation and spelling errors.

Finally merged in all code for 1.1.2.


ion-cordova-platform typo. Can't call platform.ready()

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ ] 3.x
[x] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request

Current behavior:

Platform.js inside @ionic/core at line 91 has a typo: ion-cordova-plaform. If you call platform.ready() it doesn't work.
Expected behavior:

const cordovaPlatform = this.el.querySelector('ion-cordova-platform');
Steps to reproduce:

Related code:

  constructor(platform: Platform) {
    platform.ready().then(() => {
    });
  }

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/Users/michele/.nvm/versions/node/v8.9.4/lib/node_modules)

   @ionic/cli-utils  : 2.0.0-rc.4
   ionic (Ionic CLI) : 4.0.0-rc.4

global packages:

   cordova (Cordova CLI) : 8.0.0

local packages:

   @angular-devkit/core       : 0.5.5
   @angular-devkit/schematics : 0.5.5
   @angular/cli               : 6.0.0-rc.4
   @ionic/schematics-angular  : 1.0.0-rc.4
   Cordova Platforms          : android 7.0.0
   Ionic Framework            : @ionic/angular 4.0.0-alpha.1

System:

   Android SDK Tools : 26.1.1
   ios-deploy        : 1.9.2
   NodeJS            : v8.9.4
   npm               : 5.7.1
   OS                : macOS Sierra
   Xcode             : Xcode 9.2 Build version 9C40b

Environment Variables:

   ANDROID_HOME : /Users/michele/Library/Android/sdk

 ion-cordova-plaform does not longer exist, the ionic/angular provider should work the same as it did in ionic v3


Perf optimizations

Disabling client height check that is run on every $digest and making optional via vsCheckClientSize
Adding debounce/throttle for scroll and resize handlers
Using $evalAsync instead of $apply/$digest where applicable

Approved!


Update LICENSE

Edit line 189: Copyright [2022] [Futurewei Technologies Inc.]

Edit line 189: Copyright [2022] [Futurewei Technologies Inc.]


Cache response headers in CorsSettingsImpl

Caching as much as possible headers that are derived solely from the settings should improve performance.
Fixed headers:

Access-Control-Expose-Headers
Access-Control-Allow-Credentials
Access-Control-Allow-Methods
Access-Control-Max-Age

Released in v0.3.1


fix: persist theme selection

Persist user theme selection

Title : Persist user theme selection
Issue No. : #420
Code Stack : host
Close #420

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md
[] I have updated the Index.html file for my contribution

Issues:

Unable to preserve dark mode between refresh
Select input options are not visible properly in dark mode

I have made changes for issue #1, I will update code to address issue #2 soon.


as a school-educated bro i am asking for unix support

As unix has no screen keyboard this is impossible to create this tweak for unix. Also orig unix systems have no hooking framework as i know.


[VL] Failed to build cmake-3.29

Problem description

gluten branch：main(1.2.0-snapshot)
oap velox branch: 2024_05_23
OS：centos7
Since Velox merged the PR ： Update cmake to version 3.28.3，executing ./build_velox.sh on centos7 has been failing. Can gluten support building cmake-3.29 on centos7？

System information
Velox System Info v0.0.2
Commit: 452c8a340e5ee29951bd57351f9e5a2564e8142b
CMake Version: 3.29.3
System: Linux-4.18.0-147.mt20200626.413.el8_1.x86_64
Arch: x86_64
C++ Compiler: /opt/rh/devtoolset-10/root/usr/bin/c++
C++ Compiler Version: 10.2.1
C Compiler: /opt/rh/devtoolset-10/root/usr/bin/cc
C Compiler Version: 10.2.1
CMake Prefix Path: /usr/local;/usr;/;/opt/cmake/cmake329;/usr/local;/usr/X11R6;/usr/pkg;/opt
CMake log
[ 42%] Built target cmcurl
[ 42%] Building C object Utilities/cmcurl/CMakeFiles/curltest.dir/curltest.c.o
[ 42%] Linking C executable curltest
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib64/libcrypto.a(dso_dlfcn.o): in function `dlfcn_load':
dso_dlfcn.c:(.text+0x111): undefined reference to `dlopen'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: dso_dlfcn.c:(.text+0x142): undefined reference to `dlerror'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: dso_dlfcn.c:(.text+0x1f4): undefined reference to `dlclose'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib64/libcrypto.a(dso_dlfcn.o): in function `dlfcn_unload':
dso_dlfcn.c:(.text+0x2ba): undefined reference to `dlclose'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib64/libcrypto.a(dso_dlfcn.o): in function `dlfcn_bind_func':
dso_dlfcn.c:(.text+0x3b4): undefined reference to `dlsym'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: dso_dlfcn.c:(.text+0x3e7): undefined reference to `dlerror'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib64/libcrypto.a(dso_dlfcn.o): in function `dlfcn_pathbyaddr':
dso_dlfcn.c:(.text+0x77e): undefined reference to `dladdr'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: dso_dlfcn.c:(.text+0x7e9): undefined reference to `dlerror'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib64/libcrypto.a(dso_dlfcn.o): in function `dlfcn_globallookup':
dso_dlfcn.c:(.text+0x82c): undefined reference to `dlopen'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: dso_dlfcn.c:(.text+0x84a): undefined reference to `dlsym'
/opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: dso_dlfcn.c:(.text+0x85a): undefined reference to `dlclose'
collect2: error: ld returned 1 exit status
make[2]: *** [Utilities/cmcurl/CMakeFiles/curltest.dir/build.make:102: Utilities/cmcurl/curltest] Error 1
make[1]: *** [CMakeFiles/Makefile2:1797: Utilities/cmcurl/CMakeFiles/curltest.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 42%] Linking CXX executable cmsysTestsCxx
[ 42%] Built target cmsysTestsCxx
[ 42%] Linking C static library libcmzstd.a
[ 42%] Built target cmzstd
[ 42%] Linking CXX static library libcmcppdap.a
[ 42%] Built target cmcppdap
make: *** [Makefile:166: all] Error 2

looks velox uses 3.28.
https://github.com/facebookincubator/velox/pull/9861

looks velox uses 3.28.
facebookincubator/velox#9861

Building cmake 3.28 will also fail.

Seems that -ldl is missing.

@kecookier

I encountered the same problem, did you solve it? How was it solved?

I encountered the same problem, did you solve it? How was it solved?

We use static compilation to work around this problem.


Some bluebird definitions are incorrect

Hi,
I am using the bluebird flowtype spec, I have noticed that there are some cases where a promise can be provided to the function, but this is not allowed by the flowtype spec.
e.g.
static map<T, U, Elem: $Promisable<T>>(
   Promises: Array<Elem>,
   mapper: (item: T, index: number, arrayLength: number) => U,
   options?: Bluebird$ConcurrencyOption
 ): Bluebird$Promise<Array<U>>;

Should be...
static map<T, U, Elem: $Promisable<T>>(
   Promises: Array<Elem> | $Promisable<Array<Elem>>,
   mapper: (item: T, index: number, arrayLength: number) => U,
   options?: Bluebird$ConcurrencyOption
 ): Bluebird$Promise<Array<U>>;

The definition from http://bluebirdjs.com/docs/api/promise.map.html allows this usage aswell.
Promise.map(
    Iterable<any>|Promise<Iterable<any>> input,
    function(any item, int index, int length) mapper,
    [Object {concurrency: int=Infinity} options]
) -> Promise

I think that there will be other cases too.
Thanks!

@wayne-nlt I've opened a PR, could you give the changes a sanity check? And if you could contribute/modify some tests in the comments, that would be fantastic.

Looks good @GAntoine
Just modifying a few of the existing tests...
Bluebird.all(Promise.resolve([
  new Bluebird(() => {}),
]));
Bluebird.map(Bluebird.resolve([1]), (x: number) => new Bluebird(() => {})).all();

Bluebird.reduce(Promise.resolve([5, Bluebird.resolve(6), Promise.resolve(7)]), (memo, next) => memo + next);
Bluebird.reduce(Bluebird.resolve([5, Bluebird.resolve(6), Promise.resolve(7)]), (memo, next) => memo + next, 1);

Awesome, I've updated the specs.


Icon Component overhead

I will try explain using Svelte as an example, but it should be the same.
Currently import an an icon, unplugin-icons will generate an component on the fly, like this
import IconComponent from '~icons/collection/name

to this IconComponent.svelte
<svg viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" {...$$props}>{@html `<path d="xxx" />`}</svg>

when bundling, it will compile to this for every component
function nt(t) {
	let e,
		n =
			'<path d="xxx"/>',
		r = [
			{ viewBox: '0 0 24 24' },
			{ fill: 'none' },
			{ xmlns: 'http://www.w3.org/2000/svg' },
			t[0],
		],
		s = {};
	for (let o = 0; o < r.length; o += 1) s = d(s, r[o]);
	return {
		c() {
			(e = V('svg')), _(e, s);
		},
		m(o, c) {
			A(o, e, c), (e.innerHTML = n);
		},
		p(o, [c]) {
			_(
				e,
				(s = P(r, [
					{ viewBox: '0 0 24 24' },
					{ fill: 'none' },
					{ xmlns: 'http://www.w3.org/2000/svg' },
					c & 1 && o[0],
				]))
			);
		},
		i: f,
		o: f,
		d(o) {
			o && k(e);
		},
	};
}

this is what I use for my projects to minify overhead and without losing reactivity (not 100% sure I'm right though)
A shared Icon component
<script>
    export let icon;
</script>

<svg xmlns="http://www.w3.org/2000/svg" {...icon.props} {...$$restProps}>
    {@html icon.path}
</svg>

and compile svg string to obj like this
export default {
    path: `<path d="xxx" />`,
    props: {
         fill: 'none',
         viewBox: '0 0 24 24',
    }
}

use it like this
<Icon icon={checked? icon1: icon2} height={size} width={size} on:click={onClick}/>

I think this way will save some code size, and keep reactivity, ssr should be ok too.
I know this way it may go against the main purpose of this project, use icon as Component, but maybe it can be an option

add object Compiler, svg to icon object
auto generate shared Icon component ~icons/component/svelte
maybe auto importing can work too, not sure

on second thought, this may only apply to svelte, solidjs, marko, compile language, not familiar with the others.

This is very svelte specific and requires a custom svelte icon compiler.
You have to import the <Icon> component you mentioned avove from an alias or virtual id (relative paths would not work)
You need to extraxt the attributes and content separately from the <svg> source to be able to bind them into the imported Icon.
Rather than providing that in unplugin-icons itself, i think a generic custom compiler option with importable third party compilers would be better for this case.
Regarding svelte there are other optimization options too eg. not using ...restProps but only binding style/class and the immutable compiler option which both result in even better runtime performance but should only be used if the limitations that come along with these work out. Again something a custom icon compiler could handle. I'll try to draft sth

Yes, I agree, custom compiler is the better approach.
Another small thing, to allow fully customize, right now scale option (width, height attr) can not be omitted(has to delete by custom compiler), and will always use em unit, I don't know if that is by design, I know it can be override by class or style, just think maybe it can be more flexible.


Hope the training code can update as quickly as possible

Great work，hope you can update the train code so that we can finetune the model for a typical work.

+1

+1

+1

+111111111111111111111

+1

谢谢我已收到您的来信~

+10086

谢谢我已收到您的来信~


multiple fixes of small things and QOL

multiple fixes of small things and QOL
What's Changed:

Fixes mkdirAll which would fail if one of the directories would already exist.
adds eprint and eprintln to the IO module
add a CMake option to not relocate the main executable(i use this to have two builds debug/not debug at the same time`
Adds a git hash and debug info to the version
fixes some stuff in the docs

Type of Change:

[x] Bug fix
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Housekeeping:

[x] Tests have been updated to reflect the changes done within this PR (if applicable).
[x] Documentation has been updated to reflect the changes done within this PR (if applicable).

Screenshots (If Applicable):

@briandowns @Jason2605

Nice, thanks for this!


Not generating compliant 'en_US' e164PhoneNumber

vagrant@homestead:~/code$ php artisan tinker
Psy Shell v0.9.3 (PHP 7.2.0-1+ubuntu16.04.1+deb.sury.org+1 — cli) by Justin Hileman
>>> $faker = new Faker\Generator();
=> Faker\Generator {#2436}
>>> $faker->addProvider(new Faker\Provider\en_US\PhoneNumber($faker));
=> null
>>> $faker->e164PhoneNumber;
=> "+9314623956023"
>>> $faker2 = new Faker\Generator('en_US');
=> Faker\Generator {#2429}
>>> $faker2->addProvider(new Faker\Provider\en_US\PhoneNumber($faker2));
=> null
>>> $faker2->e164PhoneNumber;
=> "+7138859816803"

US formatting for e164 should be 11 digits and always start with +1.
version using: "fzaninotto/faker": "^1.4",

I think you can make your own provider and extract this out of core, see #1349

Closing this since related ticket holds all the information required


Add an additional function named 'export'

I discussed with @qubixes and we agreed on more consistent usage of the term 'GMF file' as opposed to the longer, and sometimes more vague 'MetaFrame exported to JSON', but in line with this, it might be nice to add a new export function.
It could simply be a wrapper function around to_json, it does not have to replace it.
It's a very simple addition, but would avoid having to use confusing sentences in the docs along the lines of 'you can export a metaframe to a gmf file with to_json' and instead facilitate more a more natural 'you can export a metaframe to a gmf file with export'.

great idea.


Feature Request: Alerts clone, export or import

What kind of request is this (question/bug/enhancement/feature request):
Feature Request
Description
The ability to clone, export or import alerts between clusters.

This will be very helpful feature!

Vote +1


Is there a way to check if no results exist for multiple index searches?

I have an overall "All Results" component that displays search results for multiple categories/index names and we want to display some "No results" text if no matching results are found in any category.
I know you can do that for each individual index, but is there a way to aggregate all of the results together? I'm currently just adding a temporary container that tracks each individual category results and checking if all are have no results but wasn't sure if there's a way to do this already in your plugin.

Hi @tedlin182, we don't have something specific for it, so actually keeping track of each individual result and check if there is a global no results is a good way to achieve this :)

@tedlin182 Let us know if you need something more valuable or if you have any API ideas on how to do this.


PD - Linted the avo-acceptace-test new lines.

This PR Fixes the empty lines between the commnes to maintain the yaml format.

Codecov Report

Merging #129 (d2dcf42) into main (6eebe14) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #129   +/-   ##
=======================================
  Coverage   42.90%   42.90%
=======================================
  Files          29       29
  Lines        1508     1508
=======================================
  Hits          647      647
  Misses        785      785
  Partials       76       76

/approve
/lgtm


Refactor waitForExist to resolve immediately, handle nested selectors and more

Refactor waitForExist to resolve immediately, handle nested selectors, handle functions as selectors, and provide better error messages showing which selectors were not found and which variant the error happened in.

@teolisitza @PhyllisWong @joshua-barnard-evolv


Update file path for default data directory change

But why not simply use getDataFolder()?

It does. it just says it's going somewhere else in the console where users can be easily be confused.

Old users may still use the legacy directory plugins. It's better to use getDataFolder() rather than assuming things.


Albedo support

Add functionality to sign with Albedo in txsigner as per #545
https://github.com/tyvdh/stellar-quest-bounties/issues/11

Nice PR, thank you very much! 🙌 Just left a couple of very tiny comments.

I've made those changes 😃

Thank you, @ralphilius ! 🙂 We'll publish this very soon.

@tyvdh will you review this please

It's got the 👍  from me!


More coverage

Adding tests for coverage: I open a pull request since I like to see the delta as I commit new tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2d2cb8f) 35.40% compared to head (a00425e) 35.54%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   35.40%   35.54%   +0.13%
==========================================
  Files          37       37
  Lines        2909     2909
==========================================
+ Hits         1030     1034       +4
+ Misses       1879     1875       -4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


MultipleFileUploadEditor lost file

I have a problem with MultipleFileUploadEditor. I seem work when upload and save but file is in temporary folder and after day file in temporary folder is empty and when try to download the uploaded file, iis said file not found.

Put editor on Row.cs not Form.cs


Making sibling imports explicit

According to agreed rules:

add an index file per folder of files, which exports all files
within a folder, you MUST import siblings directly
outside a folder, you SHOULD import from the target folder’s index

As agreed in the following PR.

I updated the dependencies to the fundamentals packages


Difference in resource type naming prefix or suffix

This document shows resource types as suffixes, yet another page (https://docs.microsoft.com/en-us/azure/architecture/cloud-adoption/ready/considerations/name-and-tag#recommended-resource-type-prefixes) has the resource types as prefixes
Consistency would be nice :-)

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

ID: 0e540bb6-9f72-0529-28ea-ae82bc869835
Version Independent ID: 24e71392-985b-59fb-1552-46395b169612
Content: Naming conventions for Azure resources - Best practices for cloud applications
Content Source: docs/best-practices/naming-conventions.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @telmosampaio
Microsoft Alias: pnp

@steveculshaw Thank you for your feedback! Closing this issue as duplicate of https://github.com/MicrosoftDocs/architecture-center/issues/1757


[Bug Report] el-select dropdown 的 z-index 增加2每次点击的时候

Element UI version
2.13.2
OS/Browsers version
Mac os
Vue version
2.6.7
Reproduction Link
https://codepen.io/pgclrqvj/pen/eYdmZEp
Steps to reproduce

点击el-select。

用chrome的调试工具，看一看有class="el-select-dropdown el-popper"的元素。

它的z-index增加2每次点击的时候。

click el-select.

with chrome developer's tool, inspect element with "el-select-dropdown el-popper" class.

see its z-index increaes 2 whenever gets clicked.

What is Expected?
dropdown menu还原的时候z-index也要还原。
when dropdown menu get closed, increased z-index should be decrease so that it would be the same as before clicked.
What is actually happening?
有class="el-select-dropdown el-popper"的元素的z-index继续增加。
z-index of the element with "el-select-dropdown el-popper" class increases 2, never decreases.

你完全没get到z-index增加的意义


[BUG]: Theme performance slowdown due to backdrop-filter

See the related issue in my theme's repo: https://github.com/chrisgrieser/shimmering-focus/issues/132
Removing backdrop-filter solved the issue. 🙂

Thanks. I already have a setting to disable that effect in modals, so I'll point people to that solution in the future. 👍🏻


Failed to install 'ms-python.python'

Issue Type: Bug
Python extension is suggested. But when I select it I get this error message. I have tried turning off defender but it does not help.
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.18362

Please enable the log level to trace using the command F1 > Set Log Level and try to reproduce and provide us following

Shared log F1 > Open View > Log (Shared)
Window log F1 > Open View > Log (Window)


feat: Move Docker image to alpine

Decreased image size and build time:

All hooks
Ubuntu
Alpine
Decreased by

Build time
2m 50s
1m 47s
63s, 37%

Image size
625MB
568MB
67MB, 10%

Without hooks
Ubuntu
Alpine
Decreased by

Build time
1m 45s
0m 41s
64s, 61%

Image size
259MB
164MB
85MB, 37%

Co-authored-by: Balazs Hamorszky<EMAIL_ADDRESS>
Put an x into the box if that apply:

[ ] This PR introduces breaking change.
[x] This PR fixes a bug.
[ ] This PR adds new functionality.
[x] This PR enhances existing functionality.

Description of your changes
Something was updated in the Docker image based on Debian/Ubuntu and now it does not meet deps.
The quick fix was not found, so I decided to migrate the image to alpine, hopefully, @balihb found all needed deps earlier.
Fixes #277
Closes #239 as outdated duplicate
How has this code been tested
git clone git@github.com:antonbabenko/pre-commit-terraform.git
cd pre-commit-terraform
git checkout docker_to_alpine
# Install the latest versions of all the tools
docker build -t pre-commit --build-arg INSTALL_ALL=true .

LGTM (if it works) :)


Cxxbuild set std.upstream

Fix and implementation for #323
Let's make sure that the core lib (cxx.h|cc) and the demo code is compiled with the same features, i.e. C++ standard only at this time. These are the first two commits (code + documentation update):

b780338 Set C++ std in Cargo.toml for demo
1fa8579 Align documentation to use cxxbridge_flags.STD with cxx_build

I also moved the setting of features to cxx_build to avoid any potential miscompilation between core (cxx.h|cc) and any cargo-based client compilation using cxx_build. cxx_build can already set the CXX crate's features for all client code. This enables clients to define the features required on the CXX crate in Cargo.toml and not having to think about adding the feature settings to their compilation in build.rs. Well, at least for cargo-based clients. Buck and bazel builds are different.
This should make adding new feature easier as well as one only needs to update cxx_build and then clients can enable the features in their Cargo.toml. This should help with C++17 (string_view) support as well as folly support that I will be looking into.
Moving the feature setting into cxx_build are commits 3&4:

d328816 Set C++ std in cxx_build for simpler usage
4602329 Align documentation to no longer set cxxbridge_flags manually

Hope my explanation makes sense.
Anyhow, food for thought. Review best done by commit.

Is this necessary? As I understand it, it isn't a requirement that the standard be globally consistent across translation units. What potential miscompilation are you referring to?

E.g. only enabling c++17 in demo, but compiling cxx.h|cc with C++11 could result in the string_view API enabled while compiling the demo, but not when compiling and linking the core lib (cxx.h|cc).

I wouldn't consider that a miscompilation. If the demo doesn't use string_view then there should be no problem. If the demo does use string_view then it needs to enable the corresponding feature on its dependency on cxx according to what standard types it needs.

Sorry was rushing this out before picking up kids at school yesterday...

Is this necessary?

Not strictly. It's a usability/convenience functionality, so that I don't have to enable a feature in build.rs as well as on the cxx crate, but only in one place - the cxx crate. It theoretically also makes for less explaining/documentation as one only has to enable features on the cxx crate for cxx_build-based integration.

As I understand it, it isn't a requirement that the standard be globally consistent across translation units.

That is correct. You'll be fine mixing it across TUs if compiled on the same machine with the same compiler. Same ABI for libstdc++/libc++. I might have some questions about using STL features only available in newer C++ releases when compiling with old standard as it pertains to platform behaviour, but the cxx usage should not run into these corners of STL usage.

What potential miscompilation are you referring to?

Sorry, I should have been more specific. Miscompilation to me is where you compile the core (cxx.h|cc) with different features/build settings than demo (that includes cxx.h). Problems happens mostly when you get into the game of enabling/disabling functionality in c++ libraries/headers with defines and where you end up having diverging APIs.
The result might be linking errors in some cases.
By setting compile options in demo's build.rs, demo will always compile fine. By setting features on the cxx crate, the core compilation will always be fine. However, where you can run into linking errors if you are using APIs in demo, that were not available in the core compilation. You might luck out on inlined APIs in cxx.h. Yes, there is no issue with using fewer features in demo than provided in the core if these APIs are additive as you mention.
Having said that, you might see a linking error and then you might react as I did when playing around with folly-based APIs enabled through defines: "Oh, I set that in build.rs. Ah, I also need to set it for cxx core. Would be nice to set it only one as I always will be compiling cxx core with the same features as my demo/real program.".
I personally find this use case to match features in cxx core and demo/real program more likely as upon building with cxx_build I will build the cxx core at the same time as demo/real program.
Is that a big deal? No. But I think it would be nicer to only having to set that in one place, i.e. the cxx crate as we can easily pick up the demo crate's cxx features in the cxx_build implementation.


v6.0.0 not start, error import TradingGraphs

Describe the bug
Not Run. Return error
To Reproduce
Steps to reproduce the behavior:

download and extract https://github.com/whittlem/pycryptobot/releases/tag/6.0.0
cd /home/user/
python3.9 -m pip install -r requirements.txt
python3.9 pycryptobot.py
See error

Expected behavior
Start running...
Screenshots

Desktop (please complete the following information):

OS: Linux Lite OS (debian)
Browser Firefox
Version 96

Additional context
transcript
#python3.9 -m pip install -r requirements.txt
Requirement already satisfied: urllib3>=1.26.5 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 1)) (1.26.8)
Requirement already satisfied: pandas==1.1.4 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 2)) (1.1.4)
Requirement already satisfied: requests==2.25.0 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 3)) (2.25.0)
Requirement already satisfied: statsmodels==0.12.2 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 4)) (0.12.2)
Requirement already satisfied: matplotlib==3.3.3 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 5)) (3.3.3)
Requirement already satisfied: mock==4.0.3 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 6)) (4.0.3)
Requirement already satisfied: pytest==6.2.2 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 7)) (6.2.2)
Requirement already satisfied: pytest-mock==3.6.1 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 8)) (3.6.1)
Requirement already satisfied: responses==0.13.3 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 9)) (0.13.3)
Requirement already satisfied: pyyaml==5.4.1 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 10)) (5.4.1)
Requirement already satisfied: websocket-client==0.59.0 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 11)) (0.59.0)
Requirement already satisfied: websockets==9.1 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 12)) (9.1)
Requirement already satisfied: flask in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 13)) (2.0.2)
Requirement already satisfied: python-telegram-bot==13.7 in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 14)) (13.7)
Requirement already satisfied: tradingview-ta in /home/user/.local/lib/python3.9/site-packages (from -r requirements.txt (line 15)) (3.2.10)
Requirement already satisfied: pytz>=2017.2 in /home/user/.local/lib/python3.9/site-packages (from pandas==1.1.4->-r requirements.txt (line 2)) (2021.3)
Requirement already satisfied: python-dateutil>=2.7.3 in /usr/lib/python3/dist-packages (from pandas==1.1.4->-r requirements.txt (line 2)) (2.7.3)
Requirement already satisfied: numpy>=1.15.4 in /home/user/.local/lib/python3.9/site-packages (from pandas==1.1.4->-r requirements.txt (line 2)) (1.22.2)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests==2.25.0->-r requirements.txt (line 3)) (2019.11.28)
Requirement already satisfied: chardet<4,>=3.0.2 in /usr/lib/python3/dist-packages (from requests==2.25.0->-r requirements.txt (line 3)) (3.0.4)
Requirement already satisfied: idna<3,>=2.5 in /usr/lib/python3/dist-packages (from requests==2.25.0->-r requirements.txt (line 3)) (2.8)
Requirement already satisfied: scipy>=1.1 in /home/user/.local/lib/python3.9/site-packages (from statsmodels==0.12.2->-r requirements.txt (line 4)) (1.8.0)
Requirement already satisfied: patsy>=0.5 in /home/user/.local/lib/python3.9/site-packages (from statsmodels==0.12.2->-r requirements.txt (line 4)) (0.5.2)
Requirement already satisfied: kiwisolver>=1.0.1 in /home/user/.local/lib/python3.9/site-packages (from matplotlib==3.3.3->-r requirements.txt (line 5)) (1.3.2)
Requirement already satisfied: pillow>=6.2.0 in /usr/lib/python3/dist-packages (from matplotlib==3.3.3->-r requirements.txt (line 5)) (7.0.0)
Requirement already satisfied: cycler>=0.10 in /home/user/.local/lib/python3.9/site-packages (from matplotlib==3.3.3->-r requirements.txt (line 5)) (0.11.0)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.3 in /usr/lib/python3/dist-packages (from matplotlib==3.3.3->-r requirements.txt (line 5)) (2.4.6)
Requirement already satisfied: py>=1.8.2 in /home/user/.local/lib/python3.9/site-packages (from pytest==6.2.2->-r requirements.txt (line 7)) (1.11.0)
Requirement already satisfied: packaging in /usr/lib/python3/dist-packages (from pytest==6.2.2->-r requirements.txt (line 7)) (20.3)
Requirement already satisfied: pluggy<1.0.0a1,>=0.12 in /home/user/.local/lib/python3.9/site-packages (from pytest==6.2.2->-r requirements.txt (line 7)) (0.13.1)
Requirement already satisfied: attrs>=19.2.0 in /home/user/.local/lib/python3.9/site-packages (from pytest==6.2.2->-r requirements.txt (line 7)) (21.4.0)
Requirement already satisfied: iniconfig in /home/user/.local/lib/python3.9/site-packages (from pytest==6.2.2->-r requirements.txt (line 7)) (1.1.1)
Requirement already satisfied: toml in /home/user/.local/lib/python3.9/site-packages (from pytest==6.2.2->-r requirements.txt (line 7)) (0.10.2)
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from responses==0.13.3->-r requirements.txt (line 9)) (1.14.0)
Requirement already satisfied: itsdangerous>=2.0 in /home/user/.local/lib/python3.9/site-packages (from flask->-r requirements.txt (line 13)) (2.0.1)
Requirement already satisfied: Werkzeug>=2.0 in /home/user/.local/lib/python3.9/site-packages (from flask->-r requirements.txt (line 13)) (2.0.3)
Requirement already satisfied: click>=7.1.2 in /home/user/.local/lib/python3.9/site-packages (from flask->-r requirements.txt (line 13)) (8.0.3)
Requirement already satisfied: Jinja2>=3.0 in /home/user/.local/lib/python3.9/site-packages (from flask->-r requirements.txt (line 13)) (3.0.3)
Requirement already satisfied: APScheduler==3.6.3 in /home/user/.local/lib/python3.9/site-packages (from python-telegram-bot==13.7->-r requirements.txt (line 14)) (3.6.3)
Requirement already satisfied: cachetools==4.2.2 in /home/user/.local/lib/python3.9/site-packages (from python-telegram-bot==13.7->-r requirements.txt (line 14)) (4.2.2)
Requirement already satisfied: tornado>=6.1 in /home/user/.local/lib/python3.9/site-packages (from python-telegram-bot==13.7->-r requirements.txt (line 14)) (6.1)
Requirement already satisfied: MarkupSafe>=2.0 in /home/user/.local/lib/python3.9/site-packages (from Jinja2>=3.0->flask->-r requirements.txt (line 13)) (2.0.1)
Requirement already satisfied: tzlocal>=1.2 in /home/user/.local/lib/python3.9/site-packages (from APScheduler==3.6.3->python-telegram-bot==13.7->-r requirements.txt (line 14)) (4.1)
Requirement already satisfied: setuptools>=0.7 in /usr/lib/python3/dist-packages (from APScheduler==3.6.3->python-telegram-bot==13.7->-r requirements.txt (line 14)) (45.2.0)
Requirement already satisfied: pytz-deprecation-shim in /home/user/.local/lib/python3.9/site-packages (from tzlocal>=1.2->APScheduler==3.6.3->python-telegram-bot==13.7->-r requirements.txt (line 14)) (0.1.0.post0)
Requirement already satisfied: tzdata; python_version >= "3.6" in /home/user/.local/lib/python3.9/site-packages (from pytz-deprecation-shim->tzlocal>=1.2->APScheduler==3.6.3->python-telegram-bot==13.7->-r requirements.txt (line 14)) (2021.5)
#python3.9 pycryptobot.py
Traceback (most recent call last):
  File "/home/user/Desktop/pycryptobot-main/pycryptobot.py", line 27, in <module>
    from views.TradingGraphs import TradingGraphs
  File "/home/user/Desktop/pycryptobot-main/views/TradingGraphs.py", line 5, in <module>
    import matplotlib.pyplot as plt
  File "/home/user/.local/lib/python3.9/site-packages/matplotlib/pyplot.py", line 36, in <module>
    import matplotlib.colorbar
  File "/home/user/.local/lib/python3.9/site-packages/matplotlib/colorbar.py", line 44, in <module>
    import matplotlib.contour as contour
  File "/home/user/.local/lib/python3.9/site-packages/matplotlib/contour.py", line 17, in <module>
    import matplotlib.text as text
  File "/home/user/.local/lib/python3.9/site-packages/matplotlib/text.py", line 16, in <module>
    from .textpath import TextPath  # Unused, but imported by others.
  File "/home/user/.local/lib/python3.9/site-packages/matplotlib/textpath.py", line 11, in <module>
    from matplotlib.mathtext import MathTextParser
  File "/home/user/.local/lib/python3.9/site-packages/matplotlib/mathtext.py", line 27, in <module>
    from PIL import Image
  File "/usr/lib/python3/dist-packages/PIL/Image.py", line 69, in <module>
    from . import _imaging as core
ImportError: cannot import name '_imaging' from 'PIL' (/usr/lib/python3/dist-packages/PIL/__init__.py)

It looks like it could be a missing dependancy, I had similar issues when working through the install for ARM installing these packages did the trick.
apt-get install build-essential libatlas3-base \
libfreetype6 libjpeg62-turbo \
libopenjp2-7 libtiff5 libxcb1

There is quite a bit of information on the dependancies in a separate fork by https://github.com/paulbruedgam
https://github.com/paulbruedgam/pycryptobot/blob/docker/Dockerfile
This gives you more specific details on which packages have which dependancies, but the commands in my previous answer should cover out most of them.
# Update the base image and install requirements
# - Base build tools
#   - build-essentials: contains build tools (e.g. gcc or g++) you need to build Python extensions
#   - python3-dev: contains the header files you need to build Python extensions (needed for ARM)
#
# - Pillow (https://pillow.readthedocs.io/en/stable/installation.html#building-on-linux)
#   - Python packages: setuptools tk
#   - Linux packages (dev): libfreetype6-dev libfribidi-dev libharfbuzz-dev libjpeg62-turbo-dev
#                           liblcms2-dev libopenjp2-7-dev libtiff5-dev libwebp-dev libxcb1-dev
#                           tcl8.6-dev tk8.6-dev zlib1g-dev
#
#   - Linux packages (prod): libfreetype6 libjpeg62-turbo libopenjp2-7 libtiff5 libxcb1
#
# - matplotlib (https://matplotlib.org/stable/devel/dependencies.html)
#   - Python packages: NumPy, Pillow
#   - Linux packages (dev): gcc libfreetype6-dev
#   - ToDo:
#       - https://matplotlib.org/stable/devel/testing.html#run-the-tests
#       - Evaluate python3 -m pytest --pyargs matplotlib.tests
#
# - NumPy (https://numpy.org/devdocs/user/building.html)
#   - Python packages: Cython
#   - Linux packages (dev): gcc gfortran libatlas-base-dev liblapack-dev libopenblas-dev
#   - Linux packages (prod): libatlas3-base libopenblas-base
#   - ToDo:
#       - https://numpy.org/devdocs/dev/development_environment.html#running-tests
#       - Evaluate python3 -c 'import numpy as np; np.test("full", verbose=2)'
#
# - pandas (https://pandas.pydata.org/docs/getting_started/install.html#dependencies)
#   - Python packages: NumPy, python-dateutil, pytz
#   - ToDo:
#       - https://pandas.pydata.org/docs/getting_started/install.html#running-the-test-suite
#       - Evaluate python3 -c 'import pandas as pd; pd.test()'
#
# - scipy (https://scipy.github.io/devdocs/building/linux.html#id1)
#   - Linux packages (dev): gcc g++ gfortran liblapack-dev libopenblas-dev
#   - Linux packages (prod): libatlas3-base libopenblas-base
#
# - statsmodels (https://www.statsmodels.org/stable/install.html)
#   - Python packages: Cython, NumPy, Pandas, SciPy, Patsy
#
# Note: OpenBLAS packages not available on all arm versions. Using libblas-dev and libblas3 instead
#

cannot find this package libjpeg62-turbo-dev just libjpeg62-dev and keeps same error :S
EDIT: Maybe system issue... retry with a new&clean OS

How did you get on?
I have found this post that suggests multiple installs of Pillow will do a similar thing.
https://stackoverflow.com/questions/25340698/importerror-cannot-import-name-imaging
They suggest learning out this folder and trying to install the requirements.txt again :)
/usr/lib/python3/dist-packages
Keep us updated on your progress. If you need any assists Holla! :)


API routes missing bouncer access specification

Bug description
A clear and concise description of what the bug is.
Hi there, I'm researching web framework route security and I've found some inconsistencies in a few of portainer's routes.
Specifically the following locations:

https://github.com/portainer/portainer/blob/9cca2998339f50e1d955808d0e437b7e9f04135c/api/http/handler/stacks/handler.go#L82
https://github.com/portainer/portainer/blob/9cca2998339f50e1d955808d0e437b7e9f04135c/api/http/handler/endpoints/handler.go#L88
https://github.com/portainer/portainer/blob/9cca2998339f50e1d955808d0e437b7e9f04135c/api/http/handler/endpoints/handler.go#L91

I believe these routes should include a bouncer.PublicAccess middleware. I do not believe this is a security vulnerability because the routes are meant to be public anyway, but I see that other public routes do include the PublicAccess middleware. This middleware includes some additional security headers that are mostly irrelevant for API calls, but I still thought the routes mentioned above could include the middleware for consistencies sake. Does this seem reasonable? I'd be happy to open a PR if you'd like.
Expected behavior
A clear and concise description of what you expected to happen.
Portainer Logs
Provide the logs of your Portainer container or Service.
You can see how here
Steps to reproduce the issue:

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

Technical details:

Portainer version:
Docker version (managed by Portainer):
Kubernetes version (managed by Portainer):
Platform (windows/linux):
Command used to start Portainer (docker run -p 9443:9443 portainer/portainer):
Browser:
Use Case (delete as appropriate): Using Portainer at Home, Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? Yes/No

Additional context
Add any other context about the problem here.

@mschwager
Thank you for the information.  I am forwarding this to Product for review.  I will update you as I learn more.
Thanks!

@mschwager
I wanted to follow up on this request.  An internal issue has been logged.  I do not yet have a timeline or release.
Thanks!


Please add sufficent error handling example with HTTP status codes to documentation

Is your feature request related to a problem?
In the current state of docs, it's unclear how the HTTP status interceptor determines the status code related to exception/returned data value in the resolver.
If you want to implement the 6a pattern and return 200 OK every time a "known" error occurs (for example validation issue), you have to do one of these things:
a) always return nullable! (otherwise, you'll get 500)
b) try-catch the exception -> report exception with resolverCtx.ReportError(...) -> return data/null.
Some people (including myself) don't automatically implement nullable return values, which results in non-sense 500 errors. This behavior of the HotChocolate pipeline should be documented in docs.
Note
This also affects errors related to authentication, if - for example - I return user data that are C# record (non-nullable by nature) and the user isn't authorized, it shoots out 500 HTTP code. When you make the user data record nullable, you get 200 HTTP code. (correct behavior, but this 'authorize' attribute should be namely documented because normally you don't even have to return null in resolver).
The solution you'd like
Add HotChocolate HTTP status code and error behavior in docs.
Product
Hot Chocolate

This actually is a wrong assumption.
When we talk about known error, or lets say domain errors. Things that are expected with stage 6a then you do not report it as an error et all.
resolverCtx.ReportError(...) is for real GraphQL errors.
Stage 6a is about exposing errors in you schema which we would do by either annotating the exceptions that are domain errors or using the MutationResult struct.
Essentially ...
[Error<SomeInputHasWrongFormatException>]
public async Task<SomeResult> DoSomething(string someInput)

This actually is a wrong assumption.
When we talk about known error, or lets say domain errors. Things that are expected with stage 6a then you do not report it as an error et all.
resolverCtx.ReportError(...) is for real GraphQL errors.
Stage 6a is about exposing errors in you schema which we would do by either annotating the exceptions that are domain errors or using the MutationResult struct.
Essentially ...
[Error<SomeInputHasWrongFormatException>]
public async Task<SomeResult> DoSomething(string someInput)

Is there a way to enable stage 6a  on input validation too?

I'm currently running into this wall as well. I, personally, would prefer not to use the 6a convention (because of style preference).
I tried something like:
throw new GraphQLException(new ErrorBuilder().SetCode("AccountAlreadyExists").SetMessage("Account already exists.").Build());

But that doesn't seem to go along well with the apollo client (doesn't expose the errors information to the mutate function). Probably because of the 500 status code?

What about Domain Errors on queries? [Error] seem to work only for mutations.

@nesherhh This is available in v14 previews. (https://github.com/ChilliCream/graphql-platform/pull/6846)

Postman and BCP behaves differently in terms of response http status code with FairyBread. Postman returns 200 whereas BCP returns 500 if there is any input validator fails. The reason is that Postman in GraphQL mode always sends "Accept: application/json" header in the request, which tells HC server to use legacy mode (explained here https://chillicream.com/docs/hotchocolate/v13/server/http-transport). If you add the same header in BCP it doesn't return 500 but returns 200 just like Postman. If you don't want to add the header to client request you can configure the server.
public class CustomValidationErrorsHandler : DefaultValidationErrorsHandler
{
    public const string FairyBreadErrorCode = "VALIDATION_ERROR";

    protected override IErrorBuilder CreateErrorBuilder(
        IMiddlewareContext context,
        string argumentName,
        IValidator validator,
        ValidationFailure failure)
    {
        return base.CreateErrorBuilder(context, argumentName, validator, failure)
            .SetCode(FairyBreadErrorCode); // default is "FairyBread_ValidationError"
    }
}

public class CustomHttpResponseFormatter : DefaultHttpResponseFormatter
{
    public CustomHttpResponseFormatter(HttpResponseFormatterOptions options) : base(options)
    {
    }

    protected override HttpStatusCode OnDetermineStatusCode(IQueryResult result, FormatInfo format, HttpStatusCode? proposedStatusCode)
    {
        if (result.Errors?.Count > 0 &&
            result.Errors.Any(error => error.Code == CustomValidationErrorsHandler.FairyBreadErrorCode))
        {
            return HttpStatusCode.Conflict;
        }

        return base.OnDetermineStatusCode(result, format, proposedStatusCode);
    }
}

services.AddHttpResponseFormatter(_ => new CustomHttpResponseFormatter(new HttpResponseFormatterOptions
{
    HttpTransportVersion = HttpTransportVersion.Legacy,
    Json = new JsonResultFormatterOptions
    {
        Indented = true
    }
}));


Allow use in application extensions

In order to safely use KZPropertyMapper in application extensions, APPLICATION_EXTENSION_API_ONLY needs to be set to YES. This does not have any effect on non-extension bundles.

thanks for contributing :)

Thanks for merging so quickly! :)


Resolved Conflicts

Hi @sanjay-kv,
I have resolved the conflicts into my PR. I hope that you would merge my PR under GSSOC'24 Extd.
Thank You

Hi @murtaza-sadri-19
i wont be able to review or merge any PR or issue on any repositories which im not the admin. if there is any issue regarding lables only i can help me with. you need to tag project admn.

Hi @murtaza-sadri-19 i wont be able to review or merge any PR or issue on any repositories which im not the admin. if there is any issue regarding lables only i can help me with. you need to tag project admn.

okay, I got that. Thanks for responding @sanjay-kv.


⚠ Processors has degraded performance

In 1b39c23, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 47 ms

Resolved: Processors performance has improved in 8420efd.


Moved Ped Euphoria, Tasks and WeaponCollection initializers into thei…

…r respective getters
Added MemoryAccess ReadPadded and WritePadded Vector3 methods
Fixed Global.Read/Write Vector 3 by using the Padded methods above(When scripts write to globals they are padded)

Reminds me that the Global constructor should throw an exception if the passed address is null. Or else it would be possible to read/write to invalid memory (throws a memory exception then, but it's better to catch this clear early).


[Bug] BoxPlot does not support NaN

Version
5.2.2
Link to Minimal Reproduction
No response
Steps to Reproduce
See the additional comments
Current Behavior
The current boxplot does not allow NaN.
Expected Behavior
The current boxplot does not allow NaN.
Environment
No response
Any additional comments?
Assume on the x axis there are 3 ticks, like 1, 2, 3, and I only have box plot data for 1 and 3, currently there is no way to plot like this, due to the lack of support for NaN.

not-a-bug
Why use NaN when an empty array will do the job? Demo Code

@helgasoft thank you! The demo code is really helpful!


feat(zopafooter): allow us to have multiline legal copy in the footer

We need to be able to pass multiline copy, so piggybacking on the additionalCopy implementation to allow us to do this.
Test and Styleguide updated.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zopaUK seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 5.40.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Select Interaction doesn't work well on Cluster Source

Hello,
I've a "bug" here, and my solution would be to simply update the documentation but I think that can be useful to describe the issue here.
Describe the bug
If you try to listen the Select interaction on a Vector layer with a Cluster source, the behaviors of the selected/deselected object received in the event is inconsistent.
To Reproduce - setup

Create a cluster layer
Add some points feature in it.
Add a Select interaction on it (no config needed).

To Reproduce (1st way)

Zoom-in to see clusters feature without aggregation
Select one point
Zoom-out to aggregate this cluster feature with another one.
Zoom-in again to see points without aggregation => feature has changed.
click on this point => you can select it again (because this is not the same object as the previously selected one)

To Reproduce  (2nd way)

Zoom-in to see clusters feature without aggregation
Select one point
Set a property in one of the features of the received selected clusterFeature (like feature.get('features')[0].set('foo', Math.random())); => feature has changed
click on this point => you can select it again (because this is not the same object as the previously selected one).

Expected behavior
The selection behavior must be consistent.
Proposed solution
The problem is on the includes here: https://github.com/openlayers/openlayers/blob/v6.14.1/src/ol/interaction/Select.js#L530 we compare object, and it's not possible with Cluster feature because features are changing.
I think it's not reasonably possible to do something in the code (except maybe be able to providing a includes function as option but it would be... strange). It's more a "dead end" than an issue.
But the documentation should warn the user to avoid trying to use the Select interaction (and loose time on it). I provide a PR here https://github.com/openlayers/openlayers/pull/13668 to update the doc.

I think we should simply document that the Select interaction does not work well with Cluster sources. Working directly with layer.getFeatures() or map.getFeaturesAtPixel() is almost always better than using a Select interaction anyway.

I think we should simply document that the Select interaction does not work well with Cluster sources. Working directly with layer.getFeatures() or map.getFeaturesAtPixel() is almost always better than using a Select interaction anyway.

Yes, but note that map.get map.getFeaturesAtPixel() select ALL the feature if they are stacked to the same place which can be inconvenient in some cases (like mine)

@jeromeBor Then I think your case is different. Would be good to provide the code with context that makes you run into your issue.

We also encountered difficulties while trying to make Cluster work with interactions, including Select.
What we found is that the approach of Cluster replacing the original source makes it hard to style and add interactions. We wanted to have the clusters and original features in two separate layers, which would solve all those problems.
The issue is, we wanted to hide the original features while clustered, which meant updating their style. There are two problems we couldn't solve with the official Cluster implementation:

Restoring the style of a feature once it's not in a cluster anymore
Doing Feature.setStyle() on all features of a cluster in createCluster causes an infinite loop (Cluster.refresh -> createCluster -> Feature.setStyle -> change event on the source -> Cluster.refresh ...)

I ended up rewriting a custom version of Cluster for this purpose. It solves the two problems above by:

Applying a style to all clustered features (default: empty style, to hide them) and keeping track of their original style
Restoring the original style in Cluster.clear()
Using a Cluster.busy flag to avoid reentering Cluster.clear or Cluster.refresh during their execution

The code can be found here: https://github.com/Kayoo-asso/Topogether/blob/db006b55a3d01b1a55094d05f0668bdfae3cbc1d/components/openlayers/extensions/ClusterSource.ts
If this is of interest, I'd be happy to contribute it back to OpenLayers. Also very open to better ways of tackling this problem.
My main concern would be that when the original source has a lot of features, calling Feature.setStyle on all of them in Cluster.refresh would lead to a lot of events and impact performance. This could be solved by only changing the styles of features added & removed from clusters in Cluster.refresh.

I recommend using layer styles instead of feature styles. Like almost everywhere else, it also makes the use cases described here easier.


⚠ Redacted has degraded performance

In 461330f, Redacted ($RED) experienced degraded performance:

HTTP code: 200
Response time: 1226 ms

Resolved: Redacted performance has improved in 4175ebf.


[in progress] generic SQL database plugin

GOAL: create a plugin that will use the following databases:

DB2
Firebird
MySQL
ODBC with specific database driver
Oracle
PostgreSQL
SQLite 3

I recommend you work of the slim branch.

I think ElasticSearch plugin should also be added, how do tou think?

I am thinking that it would be nice a way to load external plugins.


don't work bat file..

I tried to run.bat on command window.
I think.. it doensn't work..
I don't know how can build source code..
Explain some steps to build code.

Hey,
Did you run the run.bat file from the MSVC prompt?
All steps are in the readme file.

yeh.. I tried to.. anyway.. Ill try more.. Let you know result.

Any update?

hey! I can't install icu.. I success installing open-ssl.
build_icu.bat file have problem.

Can you provide some debug output?

It works!  when I installed cygwin , it worked..
sorry late reply.

I failed to build qt source code..
It doesn't show "Installing Qt..."

change icu build like this.
SET _CD=%CD%
SET _PATH=%PATH%
SET ICU_SOURCE=%_CD%\icu\source
SET ICU_DIST=%_CD%\icu\icu-build
//REM Building ICU
RD /s /q %ICU_SOURCE%\lib
RD /s /q %ICU_SOURCE%\bin
RD /s /q %ICU_DIST%
SET PATH=%PATH%;C:\cygwin64\bin
CD /D %ICU_SOURCE%
dos2unix *
dos2unix -f configure
for /F %%P in ('cygpath -u %ICU_DIST%') do bash runConfigureICU Cygwin/MSVC -prefix=%%P
make clean
make && make install
CD /D %_CD%
SET PATH=%_PATH%
SET PATH=%PATH%;%ICU_DIST%\bin;%ICU_DIST%\lib
SET INCLUDE=%INCLUDE%;%ICU_DIST%\include
SET LIB=%LIB%;%ICU_DIST%\lib
I think this worked. I refer this blog.
http://pempek.net/articles/2015/10/18/compiling-qt-5-5-1-with-visual-studio-2015/

anyway options.bat .. I change like this.
@echo off
//i build qt-everywhere-source-code ..
set QTVER=5.6.0
set QTDIR=C:\qt-everywhere-opensource-src-%QTVER%
set QTINSTALLDIR=C:\Qt\Qt%QTVER%\5.6\msvc2015_64
set QTBUILDDIR=%QTDIR%\build
SET QMAKESPEC=win32-msvc2015
set PATH=%PATH%;C:\qt-everywhere-opensource-src-%QTVER%\gnuwin32\bin

setup_qt.bat  I change like this.
echo Configuring Qt...
start /W /BELOWNORMAL %QTDIR%\configure.bat -prefix %QTINSTALLDIR% -opensource -release -confirm-license -opengl dynamic -mp -static -qt-libpng -qt-libjpeg -qt-zlib -qt-pcre -no-angle -no-accessibility -nomake examples -nomake tests
-skip qtwebkit-examples -opensource -openssl -I %SSLINSTALLDIR%\include -L %SSLINSTALLDIR%\lib -icu -I %ICUINSTALLDIR%\include -L %ICUINSTALLDIR%\lib
IF %errorlevel% NEQ 0 exit /b %errorlevel%

It looks like you just have a problem with your path.

really? what  .......OTL

Yes, also the scripts are actually made for MSYS, not Cygwin.

Okey.. I success building qmake .. anyway time to build submodule file.


Introduce Configuration with identical names causes problems with other build logic.

Gradle prevents configurations with the same name for a same project / configuration container. This plugin uses reflection to bypass that. This causes different problems within gradle builds

with build logic relying on unique configuration names:

configurations.all { c -> tasks.create("resolve${c.name}")}

using gradle build scans

@breskeby yep, all of this configuration hackery is a necessary evil to alignment to work. There's no other way for us to have a copy of a configuration resolve exactly the same way of the source, when we have plugins like dependency lock etc. applying resolution rules by configuration name.
We never add these to the configuration container, but the add handlers do get called which is why you can see some side effects. The hoops we have to jump through to do something as simple as alignment in a plug-in is why out current OSP contract is focused on replacing these capabilities with core features.

We can't change this. We have to live with any side-effects until we can express these rules as dependency constraints.


Fix failing tests for AaveV3LeverageStrategyExtension

coverage: 76.259%. remained the same when pulling a7702517eef2c20c97535c8ac4d57b198fd571a9 on ckoopmann/fix-a3lse-tests into e42ba80068c5f5751b3609932a8c256a42d82c9d on snake-poison/aave-v3-leverage-post-deployment-updates.


Make OAuth2 expression handlers available to authorization server config

AuthorizationServerSecurityConfigurer has access Strings which can be used to set the security of the check_token and token_key endpoints.  These currently only have access to the base spring security expression language, and not the OAuth2 expression methods.
A use case I recently ran into was a requirement to only allow principals authenticated through client credentials to hit the check_token endpoint.  This is made difficult by OAuth2 expressions not being enabled by default, and there not being a straightforward way to add them.
An existing workaround is available here

Hi @Fitzoh. I looked at your existing workaround on SO and I'm wondering if that really works?
The reason I'm asking is because the expression #oauth2.isClient() evaluates the call to OAuth2SecurityExpressionMethods.isClient() which checks to see if the current Authentication is of type OAuth2Authentication.
However, an  OAuth2Authentication is created, after a successful authentication, on a Resource Server NOT the Authorization Server through the OAuth2AuthenticationProcessingFilter.
Currently, the OAuth2AuthenticationProcessingFilter is only being used on the Resource Server so it would also need to be setup as a pre-auth filter on the Authorization Server targeted for the check_token endpoint for the expression to actually work. This would require a lot more work than what you have on your SO post.
Can you please confirm if your workaround does work? If so, can you provide me a sample as well?
Thanks.

@jgrandja I'll see what I can dig up (June feels like a looong time ago).
It's possible that it was working for me due to having the Authorization Server and Resource server in the same application.
I can see how that would cause issues for a standalone Auth server.

Hi @Fitzoh. I haven't heard back from you so I'm assuming all is good?
I'm going to close this issue but if you need further help with this I'd be happy to re-open it if you can provide a sample re-producing the issue.
Thanks.


Force webpack resolver to solve node as target for specific package

Lets suppose hypothetically our dependency has the following package.json described as:
{
  "name": "some-dependency",
  "exports": {
    ".": {
      "browser": {
        "import": "...",
        "require": "..."
      },
      "node": {
        "import": "...",
        "require": "..."
      },
    }
  }
}

How can someone force webpack to resolve the node export individually only for some-dependency?.
I thought resolve.conditionNames: ["node", "some-dependency"], would do the trick, but it didn't.

Why you need it? It was not design for this, also it is dangerous, but you can see to use https://webpack.js.org/configuration/resolve/#resolvealias

@alexander-akait I know right and I don't like what I am doing to be honest, but the provider where I host, uses an alternative version of v8 js engine which isn't literally node, so if I wanted to use some nodejs dependency, the target env will be solved to "browser" for some reason. of course, setting the target and bundling individually with some runtime checks, work, but I'm not satisfied with the final solution.

yeah, by design resolve.conditionNames is used for all packages

you can put you condition names in rules.resolve option https://webpack.js.org/configuration/module/#ruleresolve

@Eichenschlaf alternativity you can write own plugin, look at code https://github.com/webpack/enhanced-resolve/blob/main/lib/ConditionalPlugin.js, it is simple, because it is exotic I think it will be the right direction


bug: vim.lsp.util.make_position_params() requires position/offset encoding on Nighly

Did you check docs and existing issues?

[X] I have read all the trouble.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of trouble.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.11.0-dev-1247+g5897994cb7
Operating system/version
Debian Trixie
Describe the bug
On nightly, vim.lsp.util.make_position_params() requires a second argument position_encoding. Otherwise it generates this warning message:

position_encoding param is required in vim.lsp.util.make_position_params. Defaulting to position encoding of the first client.

https://github.com/folke/trouble.nvim/blob/46cf952fc115f4c2b98d4e208ed1e2dce08c9bf6/lua/trouble/sources/lsp.lua#L175
Upstream change: https://github.com/neovim/neovim/pull/31249
I guess client and/or client.offset_encoding has to be propagated.
Steps To Reproduce

Open some buffer that attaches a language server.
Run :Trouble lsp_implementations on some identifier.

Expected Behavior
Expect no warning.
Repro
No response

Is there any workaround for this messages?


Item duplication in the Sortable List demo

Items (color names) are duplicated if you reorder them fast enough in the Sortable list demo.
See the attached image below:

Looks like the DOM isn't guaranteed to be settled when the 'sort' event is fired.  I've switched it to the 'end' event instead.

Yes, it is fixed in the dev branch.
On June 21, 2017 at 3:01:57 PM, Ivan Dubrov<EMAIL_ADDRESS>wrote:
Given that I can still reproduce the issue, I assume that page wasn't
updated yet.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/LeadDyno/intercooler-js/issues/210#issuecomment-310217839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcovzDVF-Ik1YhttsLluCnuHGr4lkchks5sGZLUgaJpZM4OAmU6
.


Get error on Composer install

Hi,
I am getting error on composer install step, can you guide me on it,
here is the screenshot of error
https://i.imgur.com/6q8a3GZ.png
Please advise,
Thanks
Imran

Hi,
I am getting error on composer install step, can you guide me on it,
here is the screenshot of error
https://i.imgur.com/6q8a3GZ.png
Please advise,
Thanks
Imran

Hi @sheensol @big-inc ,
you might have problem with your php version or the .pem file of the SSL, anyway check this link https://gyazo.com/ef952a13bbf04703033b70e66e60047a might help you

Closing this because I managed to install the project.


Remove bigint

Removed all bigint types from TypeScript declarations, in favor of number, since bigint is not widely supported across browsers.
Also fixed doc-generation version number.

:tada: This PR is included in version 1.4.1-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[api-docs] document ephemeral attachments

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/d61166446ec954d2b8f561db0d87701df5de69d9

Done