bug: plugin_config_name is not working in ApisixRoute CRD

Current Behavior
When applying CRD for ApisixPluginConfig and ApisixRoute using plugin_config_name field to bound plugins to route, the bound is not being made after all, so each CRD is applied individually in kubernetes, no errors on that, but the plugin_config_name field is being ignored on route.
This problem is very similar to that one: https://github.com/apache/apisix-ingress-controller/issues/1003, but the solution pointed not worked for me.
Expected Behavior
I expect that ApisixRoute bound with ApisixPluginConfig works when plugin_config_name is correctly added to route.
Error Logs
No errors logs
Steps to Reproduce

Run APISIX in a kubernete cluster using Helm with values bellow:

global:
  imagePullSecrets: []

apisix:
  enabled: true
  enableIPv6: true
  enableServerTokens: true
  setIDFromPodUID: false
  customLuaSharedDicts:
    []
  luaModuleHook:
    enabled: false
    luaPath: ""
    hookPoint: ""
    configMapRef:
      name: ""
      mounts:
        - key: ""
          path: ""

  httpRouter: radixtree_uri

  enableCustomizedConfig: false
  customizedConfig: {}

  image:
    repository: apache/apisix
    pullPolicy: IfNotPresent
    tag: 3.1.0-debian

  kind: Deployment
  replicaCount: 1
  priorityClassName: ""
  podAnnotations: {}
  podSecurityContext:
    {}
  securityContext:
    {}

  podDisruptionBudget:
    enabled: false
    minAvailable: 90%
    maxUnavailable: 1

  resources:
    {}

  hostNetwork: false
  nodeSelector: {}
  tolerations: []
  affinity: {}
  timezone: ""
  extraEnvVars: []

nameOverride: ""
fullnameOverride: ""

serviceAccount:
  create: false
  annotations: {}
  name: ""

rbac:
  create: false

gateway:
  type: LoadBalancer
  externalTrafficPolicy: Cluster
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-type: nlb
  externalIPs: []
  http:
    enabled: true
    servicePort: 80
    containerPort: 9080
  tls:
    enabled: true
    servicePort: 443
    containerPort: 9080
    existingCASecret: ""
    certCAFilename: ""
    http2:
      enabled: true
    sslProtocols: "TLSv1.2 TLSv1.3"
  stream:
    enabled: false
    only: false
    tcp: []
    udp: []
  ingress:
    enabled: false
    annotations:
      {}
    hosts:
      - host: apisix.local
        paths: []
    tls: []

admin:
  enabled: true
  type: ClusterIP
  externalIPs: []
  port: 9180
  servicePort: 9180
  cors: true
  credentials:
    admin: edd1c9f034335f136f87ad84b625c8f1
    viewer: 4054f7cf07e344346cd3f287985e76a2

  allow:
    ipList:
      - <IP_ADDRESS>/24
  ingress:
    enabled: false
    annotations:
      {}
    hosts:
      - host: apisix-admin.local
        paths:
          - "/apisix"
    tls: []

nginx:
  workerRlimitNofile: "20480"
  workerConnections: "10620"
  workerProcesses: auto
  enableCPUAffinity: true
  envs: []

plugins:
  - api-breaker
  - authz-keycloak
  - basic-auth
  - batch-requests
  - consumer-restriction
  - cors
  - echo
  - fault-injection
  - file-logger
  - grpc-transcode
  - hmac-auth
  - http-logger
  - ip-restriction
  - ua-restriction
  - jwt-auth
  - kafka-logger
  - key-auth
  - limit-conn
  - limit-count
  - limit-req
  - node-status
  - openid-connect
  - authz-casbin
  - prometheus
  - proxy-cache
  - proxy-mirror
  - proxy-rewrite
  - redirect
  - referer-restriction
  - request-id
  - request-validation
  - response-rewrite
  - serverless-post-function
  - serverless-pre-function
  - sls-logger
  - syslog
  - tcp-logger
  - udp-logger
  - uri-blocker
  - wolf-rbac
  - zipkin
  - traffic-split
  - gzip
  - real-ip
  - ext-plugin-pre-req
  - ext-plugin-post-req
stream_plugins:
  - mqtt-proxy
  - ip-restriction
  - limit-conn

pluginAttrs: {}

extPlugin:
  enabled: false
  cmd: ["/path/to/apisix-plugin-runner/runner", "run"]

wasmPlugins:
  enabled: false
  plugins: []

customPlugins:
  enabled: false
  luaPath: "/opts/custom_plugins/?.lua"
  plugins:
    - name: ""
      attrs: {}
      configMap:
        name: ""
        mounts:
          - key: ""
            path: ""
          - key: ""
            path: ""

updateStrategy:
  {}

extraVolumes: []

extraVolumeMounts: []

extraInitContainers: []

discovery:
  enabled: false
  registry:
    {}

logs:
  enableAccessLog: true
  accessLog: "/dev/stdout"
  accessLogFormat: '$remote_addr - $remote_user [$time_local] $http_host \"$request\" $status $body_bytes_sent $request_time \"$http_referer\" \"$http_user_agent\" $upstream_addr $upstream_status $upstream_response_time \"$upstream_scheme://$upstream_host$upstream_uri\"'
  accessLogFormatEscape: default
  errorLog: "/dev/stderr"
  errorLogLevel: "warn"

dns:
  resolvers:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - <IP_ADDRESS>
  validity: 30
  timeout: 5

initContainer:
  image: busybox
  tag: 1.28

autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 100
  targetCPUUtilizationPercentage: 80
  targetMemoryUtilizationPercentage: 80

configurationSnippet:
  main: |

  httpStart: |

  httpEnd: |

  httpSrv: |

  httpAdmin: |

  stream: |

serviceMonitor:
  enabled: false
  namespace: ""
  name: ""
  interval: 15s
  path: /apisix/prometheus/metrics
  metricPrefix: apisix_
  containerPort: 9091
  labels:
    {}
  annotations:
    {}
etcd:
  enabled: true
  host:
    - http://etcd.host:2379
  prefix: "/apisix"
  timeout: 30

  auth:
    rbac:
      create: false
      user: ""
      password: ""
    tls:
      enabled: false
      existingSecret: ""
      certFilename: ""
      certKeyFilename: ""
      verify: true
      sni: ""

  service:
    port: 2379

  replicaCount: 3

ingress-controller:
  enabled: true
  config:
    apisix:
      adminAPIVersion: "v3"
      serviceNamespace: apisix

vault:
  enabled: false
  host: ""
  timeout: 10
  token: ""
  prefix: ""

Apply CRD to create ApisixPluginConfig

apiVersion: apisix.apache.org/v2
kind: ApisixPluginConfig
metadata:
  name: public-endpoints
  namespace: apisix
spec:
  plugins:
    - name: cors
      enable: true
      config:
        allow_origins: http://localhost:3000
        allow_credential: true
        allow_methods: "**"
        allow_headers: "**"
        expose_headers: "**"

Apply CRD to create ApisixRoute bounded to ApisixPluginConfig

apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: route-test
  namespace: apisix
spec:
  http:
    - name: rule1
      match:
        hosts:
          - localhost
        paths:
          - /test
        methods:
          - OPTIONS
          - GET
      backends:
        - serviceName: httpbin
          servicePort: 80
      plugin_config_name: public-endpoints

Check if plugins is applied or not.

Environment

APISIX version (run apisix version): 3.1.0
Operating system (run uname -a): Kubernetes 1.22 in AWS EKS
etcd version, if relevant (run curl http://<IP_ADDRESS>:9090/v1/server_info): 3.5.0
APISIX Dashboard version, if relevant: 2.15.0
Apisix Helm Version: apisix-1.1.1 (Ingress controller installed via the same helm)

@tao12345666333
Same here.
Here's what I've configured.
apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: openapi-alimi-route
  namespace: ingress-apisix
spec:
  http:
  - name: rule-***
    priority: 1
    match:
      hosts:
        {{- include "openapi.hosts" . | indent 8 }}
      paths:
        - ***
    upstreams:
      - name: cv-upstream
    plugin_config_name: openapi-plugin-config

apiVersion: apisix.apache.org/v2
kind: ApisixPluginConfig
metadata:
  name: openapi-plugin-config
  namespace: ingress-apisix
spec:
  plugins:
  - name: forward-auth
    enable: true
    config:
      request_method: GET
      uri: ***
      request_headers: ***
      upstream_headers: ***
  - name: prometheus
    enable: true
    config:
      disable: false
      prefer_name: true
  - name: http-logger
    enable: true
    config:
      uri: ***
  - name: proxy-rewrite
    enable: true
    config:
      uri: ***
      headers:
        ***

When I call check a route using ADMIN API neither plugin_config_name nor plugin_config_id appears.
curl <IP_ADDRESS>:9180/apisix/admin/routes/31ceeb97 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' | jq
{
  "value": {
    "labels": {
      "managed-by": "apisix-ingress-controller"
    },
    "hosts": [
      ***
    ],
    "desc": "Created by apisix-ingress-controller, DO NOT modify it manually",
    "id": "31ceeb97",
    "update_time":<PHONE_NUMBER>,
    "status": 1,
    "create_time":<PHONE_NUMBER>,
    "uris": [
      ***
    ],
    "upstream_id": "281b5cf0",
    "name": "ingress-apisix_openapi-alimi-route_rule-alimi",
    "priority": 1
  },
  "modifiedIndex": 62324,
  "key": "/apisix/routes/31ceeb97",
  "createdIndex": 62188
}

However, when I describe ApisixRoute using kubectl, plugin_config_name appears.
k describe apisixroute openapi-alimi-route
Name:         openapi-alimi-route
Namespace:    ingress-apisix
Labels:       argocd.argoproj.io/instance=dev-apisix
Annotations:  <none>
API Version:  apisix.apache.org/v2
Kind:         ApisixRoute
Metadata:
  Creation Timestamp:  2023-03-23T02:03:16Z
  Generation:          3
  Managed Fields:
    API Version:  apisix.apache.org/v2
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
    Manager:      apisix-ingress-controller
    Operation:    Update
    Time:         2023-03-23T02:03:16Z
    API Version:  apisix.apache.org/v2
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          .:
          f:argocd.argoproj.io/instance:
      f:spec:
        .:
        f:http:
    Manager:         argocd-application-controller
    Operation:       Update
    Time:            2023-03-23T02:03:16Z
  Resource Version:  542685578
  UID:               9be6e2bc-1b42-4942-91cd-fc5118743cfe
Spec:
  Http:
    Match:
      Hosts:
        ***
      Paths:
        ***
    Name:                ***
    plugin_config_name:  openapi-plugin-config
    Priority:            1
    Upstreams:
      Name:  cv-upstream
Status:
  Conditions:
    Message:              Sync Successfully
    Observed Generation:  3
    Reason:               ResourcesSynced
    Status:               True
    Type:                 ResourcesAvailable
Events:
  Type    Reason           Age                   From           Message
  ----    ------           ----                  ----           -------
  Normal  ResourcesSynced  4m32s (x15 over 48m)  ApisixIngress  ApisixIngress synced successfully

Also, when I manually copied configuration in ApisixPluginConfig and pasted it in ApisixRoute, it works fine.

You need to create an ApisixPluginConfig before creating an ApisixRoute, otherwise this may be due to ApisixRoute not being able to find an ApisixPluginConfig, which may not work properly.

@AlinsRan
I've just tried like you suggested (Create ApisixPluginConfig first and then ApisixRoute)
However it isn't working.
Here's what I've tried.
k describe apisixpluginconfig openapi-alimi-plugin-config
Name:         openapi-alimi-plugin-config
Namespace:    ingress-apisix
Labels:       argocd.argoproj.io/instance=dev-apisix
Annotations:  <none>
API Version:  apisix.apache.org/v2
Kind:         ApisixPluginConfig
Metadata:
  Creation Timestamp:  2023-03-23T05:42:39Z # created first.
  Generation:          1
  Managed Fields:
    API Version:  apisix.apache.org/v2
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
    Manager:      apisix-ingress-controller
    Operation:    Update
    Time:         2023-03-23T05:42:39Z
    API Version:  apisix.apache.org/v2
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          .:
          f:argocd.argoproj.io/instance:
      f:spec:
        .:
        f:plugins:
    Manager:         argocd-application-controller
    Operation:       Update
    Time:            2023-03-23T05:42:39Z
  Resource Version:  542795381
  UID:               36adc3ef-1b45-456d-9d08-3d1ce4ba36a5
Spec:
  Plugins:
    Config:
      request_headers:
        ***
      request_method:  GET
      upstream_headers:
        ***
      Uri:   ***
    Enable:  true
    Name:    forward-auth
    Config:
      Disable:      false
      prefer_name:  true
    Enable:         true
    Name:           prometheus
    Config:
      Uri:   http://openapi-logging.openapi-logging.svc.cluster.local:8080/v1/logging
    Enable:  true
    Name:    http-logger
    Config:
      Headers:
        ***
      Uri:                            ***
    Enable:                           true
    Name:                             proxy-rewrite
Status:
  Conditions:
    Message:              Sync Successfully
    Observed Generation:  1
    Reason:               ResourcesSynced
    Status:               True
    Type:                 ResourcesAvailable
Events:
  Type    Reason           Age                 From           Message
  ----    ------           ----                ----           -------
  Normal  ResourcesSynced  2m4s (x4 over 11m)  ApisixIngress  ApisixIngress synced successfully

k describe apisixroute openapi-alimi-route
Name:         openapi-alimi-route
Namespace:    ingress-apisix
Labels:       argocd.argoproj.io/instance=dev-apisix
Annotations:  <none>
API Version:  apisix.apache.org/v2
Kind:         ApisixRoute
Metadata:
  Creation Timestamp:  2023-03-23T05:53:13Z
  Generation:          1
  Managed Fields:
    API Version:  apisix.apache.org/v2
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
    Manager:      apisix-ingress-controller
    Operation:    Update
    Time:         2023-03-23T05:53:13Z
    API Version:  apisix.apache.org/v2
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          .:
          f:argocd.argoproj.io/instance:
      f:spec:
        .:
        f:http:
    Manager:         argocd-application-controller
    Operation:       Update
    Time:            2023-03-23T05:53:13Z
  Resource Version:  542802079
  UID:               b8e9a2e9-29d1-42c6-83c9-a866b52b010e
Spec:
  Http:
    Match:
      Hosts:
        ***
      Paths:
        ***
    Name:                rule-alimi
    plugin_config_name:  openapi-alimi-plugin-config
    Priority:            1
    Upstreams:
      Name:  cv-upstream
Status:
  Conditions:
    Message:              Sync Successfully
    Observed Generation:  1
    Reason:               ResourcesSynced
    Status:               True
    Type:                 ResourcesAvailable
Events:
  Type    Reason           Age                From           Message
  ----    ------           ----               ----           -------
  Normal  ResourcesSynced  29s (x2 over 29s)  ApisixIngress  ApisixIngress synced successfully

Even though ApisixRoute created first, I think it should work normally after ApisixPluginConfig is created.
Also, it would be good if i could know that kind of situation through events or at least logs. I can't find any logs related with that.

@renatomattos2912
I saw that you referenced upstream in ApisixRoute, and I think it's related to this issue.
https://github.com/apache/apisix-ingress-controller/issues/1577

@renatomattos2912 I saw that you referenced upstream in ApisixRoute, and I think it's related to this issue.

bug: PluginConfigId is not assigned to the route in case upstreams used instead of the backends #1577

Great, it is exactly that, but i think the fix was not released yet cause as we can see in ingress controller helm and in docker repo, it is still in version 1.6.0 that is the buggy version:
https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-ingress-controller/values.yaml
https://hub.docker.com/r/apache/apisix-ingress-controller/tags
I hope it will be fixed in version 1.6.1 soon.


Two alpha SLs.

For some reason, there can be multiple squad leaders. Ive seen this multiple times with alpha.

"How many Alpha SLs does it take to push the front?"


Cow: Watch Real[\W_]+Estate[\W_]+Infographics[\W_]*+Services

Cow requests the watch of the watch_keyword Real[\W_]*+Estate[\W_]*+Infographics[\W_]*+Services. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Real[\W_]*+Estate[\W_]*+Infographics[\W_]*+Services has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


CS0118: 'Mediator' is a namespace but is used like a type

for better performance, i chose Mediator instead of IMediator, but i get CS0118: 'Mediator' is a namespace but is used like a type error, so i have to explicitly declare Mediator by "MyNameSpace.Mediator" for every call , do you have better way to solve this ?
example
using Microsoft.Extensions.DependencyInjection;

namespace ConsoleApp1
{
    internal class Program
    {
        private static void Main(string[] args)
        {
            var service = new ServiceCollection()
                .AddMediator(options => options.Namespace = "MyNamespace")
                .BuildServiceProvider();
        }
    }

    public class Test
    {
        private readonly IServiceProvider _service;

        public Test(IServiceProvider service)
        {
            _service = service;
        }

        public void ResolveMediator()
        {
            Mediator mediator = _service.GetRequiredService<Mediator>(); // here i will get cs0018 error
            MyNamespace.Mediator mediator1 = _service.GetRequiredService<MyNamespace.Mediator>(); // this will work, but i wanna know is there any better way to avoid type "MyNamespace." every time
        }
    }
}

Can add an "s" at the end of your namespace. It may be confusing it with Mediator packages.

Ahh, no matter what namespace is configured, the Mediator implementation will always collide with the Mediator namespace from the abstractions package (where IRequest etc is). One option is to create a global alias using global usings: global using MyMediator = MyNamespace.Mediator or similar. I'll have to think about refactoring this without having too many breaking changes... Thanks for bringit it up 👍

I have stumbled upon this one. You can also use Mediator.Mediator instead of just Mediator and it will work properly.

I keep getting a MSBuildLocator error. In the past I fixed this by installing NuGet.Frameworks.


Footer

Hey @Ameer-officials, #17 already does this, tysm for the pr tho!

@jaspermayone Got It!!


sparks

when trying to load it says there a bunch of files missing after adding maps and sparks lua.

It has been a long time since I've loaded and used the addon. It does strictly call for a few helpers, notably:
require('tables')
require('logger')
packets = require('packets')
db = require('map')

These helper files are normally preloaded within the windower addons folder structure. I'm not at my home pc or I could point you towards the location they should live.
Are you getting any other specific notices beyond the above?

oh i think its because i use ashita

As this add-on is intended for windower I'll close this issue.


Bug in Publish python distribution to Azure Artifacts feed

python -m twine upload -r "myTestProject/myTestFeed" --config-file $(PYPIRC_PATH) dist/*.whl

gets the error:
InvalidConfiguration: Missing 'myTestProject/myTestFeed' section from the configuration file
or not a complete URL in --repository-url.

this solves the problem:
python -m twine upload -r myTestFeed --config-file $(PYPIRC_PATH) dist/*.whl

see full trace https://msdata.visualstudio.com/DefaultCollection/AlgorithmsAndDataScience/_build/results?buildId=10828720&view=logs&j=836bd6c2-066c-5c38-d30d-e81e3a76d869&t=d8543af4-8a21-5f05-1956-5ba398eb8383

@miguelgfierro : Thanks for your contribution! The author(s) have been notified to review your proposed change.

cc @juliakm

#sign-off

@mijacobs: I'm sorry - only the author of this article, @chasewilson, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


[Question/Feedback]: Provide guidance & best practices on reacting to recommended alerts

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Description
When monitoring IT systems, it’s a best practice to first identify the events or system properties of interest, then determine the appropriate actions to take when these events or property changes occur. Only after this should monitoring and alerts be configured to ensure these events and changes are observed. This approach reduces alert noise and clarifies the actions needed when a particular alert is triggered. Ultimately, it also allows for automation of these actions, reducing the time to resolution.
My request is to update the documentation to provide additional context for each alert: why is it important, and what are the recommended actions when the alert is fired?
Thank you!

Coming from a System Center Operations Manager (SCOM) background, alert tuning is always a hot topic. SCOM was always delivered with a default set of alert rules and monitored enabled out of the box. After deploying SCOM, you would spend the next several months tuning alerts by running "Top 10" alert reports to see what the top talkers are. You either address the hardware or software issue and/or tune the alerts to a threshold that prevents the alert from firing so often. Other times, you just disable the alert, because it is not relevant to your environment.
Initially, I recommend only enabling Severity 0 alerts to be emailed out via the Action group, and then go into Azure monitor weekly for the top alerts firing, and address/remediate each alert.
I like having all the alerts firing initially, because I can go into Azure monitor and get an overall health of the environment by seeing the alerts that are firing. As time goes on, you will be adjusting thresholds and windows, and alert severities to match what is supportable in your environment. There is no one size fits all set of alerts or configuration...


Add Zeroize impl for SigningKey

Feature gated in case this is somehow controversial. Happy to remove if not.

ping @hdevalence wdyt?

@kim Hey, sorry I missed this. Not at all controversial, this looks great. Removing the feature flag and doing it unconditionally would be even better.

Thanks!


Use glob in datasets instead of walk_files

Replace walk_files+filter in datasets by globing, e.g. paths = [str(p) for p in Path(self._path).glob('*/*_no_hash_*.wav')]

[ ] librispeech
[ ] libritts
[ ] speechcommands
[ ] tedlium
[ ] vctk
[ ] yesno

Once this is done, we can deprecate torchaudio.datasets.utils.walk_files.
cc #910

Shouldn't the globs be sorted for reproducibility reasons?

Yes, tests should catch if the order is not consistent, see also comment.

Closed by #1109


chore(main): release homestar 0.3.0

:robot: I have created a release beep boop
0.3.0 (2023-11-09)
Features

base64 variants (0d6a60a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fission-codes/stack/releases/tag/homestar-v0.3.0 :sunflower:


setting the size of the frequency grid

Hello @andreatramacere,
I would like to generate an SED with a fixed grid in nu, now if I try to set a value lower than 200 it is just ignored and
an SED of 200 points is returned.
Here a snippet:
from jetset.jet_model import Jet

pwl_jet = Jet(name="", electron_distribution="pl")
pwl_jet.set_nu_grid_size(50)
pwl_jet.show_model()
pwl_jet.eval()
pwl_synch_sed = pwl_jet.get_spectral_component_by_name("Sync").get_SED_points()
# check how many SED points the we get
print(len(pwl_synch_sed[0]))

I get
200

despite in the show_model overview 50 is correctly reported
SED info:
 nu grid size :50
 nu mix (Hz): 1.000000e+06
 nu max (Hz): 1.000000e+30

Is 200 a hardcoded minimum you set?
Thank you!

Hi @cosimoNigro :),
no it is not hardcoded. The grid is the grid used in the python interface to interpolate the values from all the components, in such a way that you can sum them without any problem.  But there are two grids, one at level of the C code, and one at level of the python interface. the pwl_synch_sed = pwl_jet.get_spectral_component_by_name("Sync").get_SED_points()  is returning the synch from the C code, evaluated over seed photons grid size=100 and interpolated over the full C-level grid of 200. To get the SED  interpolated over python code use pwl_jet.spectral_components.Sync.SED.nu.
from jetset.jet_model import Jet

pwl_jet = Jet(name="", electron_distribution="pl")
pwl_jet.set_nu_grid_size(50)
pwl_jet.show_model()
pwl_jet.eval()
pwl_synch_sed = pwl_jet.get_spectral_component_by_name("Sync").get_SED_points()
# check how many SED points the we get
print(len(pwl_synch_sed[0]))
print(len(pwl_jet.spectral_components.Sync.SED.nu))`

you get
size of C-grid array 200
size of python-grid 50

The method .get_SED_points() is not reported in the documentation and I should move it as protected, because it should be used only internally to the code.

Ok perfect, this is what I wanted.
Thanks! You can close the issue.


Implement Centralized App Settings Page

This feature aims to provide users with a single, user-friendly interface where they can configure and customize various aspects of the application to suit their preferences and requirements. Develop a centralized App Settings Page component that can be seamlessly integrated into different apps. This component should be designed to work cohesively with various DXP elements.

closing this task since we are instead making individual cards and settings that can actually be implemented in any screen


ua-parser vulnerability

So ua-parser is one of the packages required by azure-mobile-apps, but GitHub says that is a high-severity vulnerability.
This is what the security alert reads:
"CVE-2017-16086
high severity
Vulnerable versions: <= 0.3.5
Patched version: No fix
ua-parser is a port of Browserscope's user agent parser. ua-parser is vulnerable to a ReDoS (Regular Expression Denial of Service) attack when given a specially crafted UserAgent header. Consider using a different package such as useragent."
GitHub also finds an issue with the hoek version being used (2.16.3) and suggests using >=4.2.1 instead.
Not sure how this may affect our backend code, but I would like to know if there are plans to switch to a package without this vulnerability, or if there is anything we can do to solve this.

Hey, thanks for the mention, we fixed this in the new release!


New option in server config: DisableMulticastLoopback.

Setting this option to false (default) sets the IP_MULTICAST_LOOP socket option
to true on the multicast sockets opened by the mDNS server.  This is necessary
for other sockets on the same machine to receive packets sent by the server and
thus discover the service.

Did you even look at the code before submitting this?

The merge conflict is accidental. I thought I had rebased against your branch, but actually I had rebased against the original upstream master (hashicorp). PTAL at the new merge request.


Identify question answered on scorex

If question/answer bonuses are used in a rally, the scorex should include positive identification that question was answered, rightly or wrongly.

Answered questions are now flagged with dagger symbol


should files be sorted before operating on them

Many onyo commands allow multiple files as input.
While writting a test case for onyo set (onyo set --recursive RAM=10 to update all assets) I noticed that the local tests are successful, while after pushing the tests failed. This was caused through the different order git looped over the assets while creating the diff like output, and solved with sorting the assets directly at the beginning when checking the input (the prepare arguments function, which exists in some form for all commands).
While this fix with sorting the input assets was done to make sure the new tests will work reliably, I am now wondering, if not all commands that can run over multiple assets/directories should sort them alphabetically.
The contra is obviously that a lot of internal sorting, especially when working with a lot of assets would impact run time.
the positive thing would mainly be to guarantee that onyo commands on the same assets would always work the same.
To be clear: the other commands/tests are not effected by any ordering problems, but I wanted to put out this question for thought.

I see this a bit differently, though related: the issue you're trying to resolve is whether files are operated on in a /predictable/ manner, not whether they are sorted.
IMO, when possible, the order specified by the user should be honored. e.g. if a user runs onyo cat b a, then they should be printed in the order of b and then a.
If a user specifies a folder, then I do see the /contents/ of that folder being sorted alphabetically (so that inode order isn't used). The user's intent is not clear, so us doing something predictable makes sense here (and, I would argue, is what a user would intuitively expect).

Because we use now different functions and classes, the inputs and assets are used in a predictable (e.g. alphabetical) order. I will close this, and if there are other order-related topics a more specific issue should be opened.


Establish an email system to automatically notify users with their temporary access credentials.

It won't be done; we don't have an SMTP server available. Also, the user can already view their password in Vault!"


npm run main fails.

Thank you for sharing the amazing piece of your work,
I followed your well explained steps to reach here, but i couldn't npm run main to the backend.
I am continuously receiving the error,
TypeError: Cannot read property 'legs' of undefined

As suggested by few fellow programmers, i upgraded the npm version to 6.2 but still couldn't get any solution then i even downgraded to the version 4.6.1 still i am not getting anywhere.
Any help will be highly appreciated. Thank You

I am also getting same error, were you able to fix this?

legs is supposed to be an attribute of the returned data, the fact that it is absent is indicative of there being no routes available. I should really add some error handling.

@domesticmouse  -  does it mean we are good with backend setup? How to confirm the same?

Have you gone through the transport tracker codelabs?

const ptt = this.directionsResponseForTrip(returnValue.next_trip.trip);

I faced same issue. If you print ptt, it's return message This API project is not authorized to use this API. I've resolved this issue by changing Maps API key in tracker_configuration.js from API Key to Server Key. I realized that The Getting Started (https://developers.google.com/maps/solutions/transport-tracker/start) is guide me to copy the API Key instead of Server Key.

Hi @hynra where can I get the "Server Key" that you mention, thanks for you answer.

@hynra The Server Key (from firebase) is giving out errors?

The project uses Directions API. Enable the API, then it will work.
https://github.com/googlemaps/transport-tracker/blob/0146b3ec8246b808536a3cfbbf721d1a51444a5f/backend/time_table.js#L205-L206
Server Key is just a credential name generated by Google Service. For testing purposes, just ensure that the used API key doesn't have restrictions.


Updates to the threat intelligence indicators beta article

Purpose of this pull request
This pull request makes minor updates to the following article before the beta release:
https://help.sumologic.com/docs/platform-services/threat-intelligence-indicators

Issue: Asana ticket "Document Unified Threat Intelligence - beta"
Select the type of change:

[x] Minor Changes - Typos, formatting, slight revisions, .clabot
[ ] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

@kimsauce, could you take a quick look at this PR? We'd like to get it published by the end of today so it's ready to go on Tuesday when the beta starts.

@kimsauce, could you take a quick look at this PR? We'd like to get it published by the end of today so it's ready to go on Tuesday when the beta starts.

thanks for the nudge - sorry I missed this one

Thanks, @kimsauce!


Encoded params from RKURLs getting extra 25's.

When I built from master I was getting the following failure.
Test Case '-[RKURLSpec testShouldEscapeQueryParameters]' started.
/Users/rayfix/projects/pelfunc/3rd-party/RestKit/Specs/Network/RKURLSpec.m:46: error: -[RKURLSpec testShouldEscapeQueryParameters] : Expected "http://restkit.org/test?answer=john2restkit                                -1.99743mail.com&question=What             4260671s2our2231       2.546734e-273-mail0.000000", but was "http://restkit.org/test?answer=john2restkit mail.com&question=What                                                                                s2our225231                                                                                -mail                                                                                0.000000"
Test Case '-[RKURLSpec testShouldEscapeQueryParameters]' failed (0.003 seconds).

Looks like that change was recently introduced in a pull request. I think there's a better fix for his issue, so I am merging this and will take a swing at a more focused fix.


Can't install on M1 Mac (problem in triangle library)

Describe the bug
sectionproperties cannot be installed on an M1 Mac because of this bug in triangle. It's on the C side of things, it seems.
I'm just wondering if anyone here has figured out a work-around or if there's a way to go back to the older mesh library (I saw the discussion over in "Discussions" about the port). Or maybe an older version of sectionproperties can be installed?
To Reproduce
Steps to reproduce the behaviour:

pip install sectionproperties
see failure message

Desktop (please complete the following information):

OS: MacOS on M1-pro
Version 12.3.1 (21E258)
Python: 3.10.2 installed via pyenv (compiled for M1)

Additional context
Add any other context about the problem here.

Hi @mfeif,
Sorry to hear you're having trouble installing triangle. Have you tried running a virtual environment with either python 3.8 or 3.9?
In the meantime, you could try running an older version of sectionproperties as you've suggested. triangle was adopted in v2.x.x so you could run with v1.0.8 which uses MeshPy, you can find the docs for that version here.
Hopefully the issue with triangle gets resolved soon!

Closed as not a sectionproperties issue.

@mfeif, if you're still around, sectionproperties v3.3.0 can be able to be installed on computers with Apple Silicon processors as we are now using CyTriangle.

Amazing. Thank you for the heads-up!


[debt] selection model and rendering is coupled in SelectionManagerService

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Affected packages and versions
dev
Steps to reproduce
.
Expected behavior
.
Actual behavior
.
Runtime
No response
OS
No response
Build and bundle tools
No response

Closing this issue. I am going to open a ticket that seeks to refactor the whole sheet selection management.


Add "loose" search mode to scan for latest matches only

Give the user control over the search by introducing a "loose" mode that, after identifying a certain number of repetitive matches, will stop searching for others.

Supported in latest commits.


Removes transcript comp. Refactors Academics UI.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.343%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
246

Relevant Lines:
429

💛  - Coveralls


API previews / accept headers

Some API endpoints such as the new Checks API require an Accept header to be set, e.g. in this case Accept: application/vnd.github.antiope-preview+json
It would be great if we could:

Find all applicable preview headers for each endpoint
Set a custom default accept header while a new endpoint is still in preview

this is now blocking https://github.com/octokit/rest.js/pull/1043 so I’ll be looking into it


[API-DRAFT] [MERGE] Merge api-draft to dev branch

Purpose of this pull request
Merge api-draft to dev branch. Let SeaTunnel new API come to main branch

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

And there are so many sonor bugs, we may need to solve this.

And there are so many sonor bugs, we may need to solve this.

Yes, we need solve bug and remove many duplicate code

LGTM, Hive Sink Connector is a temporary implementation. I will rewrite this connector after this pr merged.


fix(es/minifier): ignore member expr with obj lit in assign position

Description:

BREAKING CHANGE:

Related issue (if exists):
closes #5343

Can you update the tests?


Datagrid Numeric Filter

Summary
Data-grid columns with numeric values should have a dedicated numeric filter. We plan to build this for our team but since it is such a common feature we felt like we should propose a contribution so that more people can benefit from it and not have to write the same filter over and over again.
Use case
Numeric data-grid columns will make use of the filter. Since it is specific to numbers, the filter can provide comparison options like = equals, > greater than, < less than, between, etc.
API
The filter can be implemented as an angular component and then be used inside <clr-dg-filter> tags:
<clr-datagrid>
    <clr-dg-column clrDgField="numericField">
        <clr-dg-filter>
            <clr-numeric-filter></clr-numeric-filter>
        </clr-dg-filter>
    </clr-dg-column>
</clr-datagrid>

@IoannesBracciano -- I'm also interested in this, and if there's anything I can do to help with this please let me know.

Greetings,
I have been a bit busy the last days but I took some time today to create a simple template of how we imagine the filter would look like.

That is the simplest idea, featuring a select box to choose the appropriate operator and a numeric input next to it. This will work well for most conventional comparison operators (equals, greater than, etc.), but the layout does not fit operators like between or not between since in these cases we need two numeric inputs.
I had another bolder idea to use a numeric line instead of standard inputs, on which the user could select numbers or ranges easier and more intuitively. It is not 100% thought through though and I do not have time right now to creating a working PoC, but if someone else has some time to spend on it I could work out the details with them!

I prefer your first idea of allowing the user to input ranges by typing in numbers over having a range slider.  I think they work OK in some cases, but having numbers distributed over a large range (or even having a few outliers) makes them very difficult to use.
I think a simple implementation would be to provide the user with two numeric inputs that provide a range, perhaps with a format like
___ <= x <= ___

or
[ ___, ___ ]

where the blanks are numeric inputs.  This would still allow the user to filter to a specific value with an input like [ 0, 0 ].
Is your mockup above available somewhere?  If not I can set another one up.  Cheers -A

I'm working on this now -- could someone on the Clarity side please create a topic branch?  (I'm trying to follow the instructions here).
The rough idea is to make an analog to the existing string filters for numeric contents, closely following the existing framework for string filters.  Rather than a single string input value the numeric filters will include two inputs for low and high limits (which may be +Inf or -Inf which doesn't set a limit).  The built-in numeric filter will always filter items that can't be converted to number, but users will be able to create their own numeric filters with custom filter functions.

@amellnik (and anyone else who was planning on contributing for this): I just created the topic/datagrid-numeric-filter branch off of latest master: https://github.com/vmware/clarity/tree/topic/datagrid-numeric-filter
Please make sure to commit your changes on top of this branch (so don't include future commits for now, we'll handle the rebasing), and submit your PRs against that branch.

One more question -- is there any consensus about how generic this should be?  A minimal approach would be to just follow the documentation for custom filters but that would run into https://github.com/vmware/clarity/issues/2513 and users would always need to specify the column name when constructing the filter.
A more invasive change would be to put it on equal footing with the string filters, perhaps by attaching an @Input up to the _field property of the datagrid column, and reproducing all the same stuff for numeric filters that exists for string filters (except for possibly the custom filter functions?)

I'd be okay with a clrType input next to clrDgField, that allows you to specify the data type of the property on the obejcts. It would be string by default, and you could use clrType="number" to get the numeric filter. You'd still have to offer them as custom filters for flexibility.

We need to stay with a simple solution. The most basic would be the 'between' paradigm with 2 numeric inputs. The only UX issue I am concerned about with this is clarification of the purpose of the 2 fields - this may be as simple as the hint text saying something like 'from' and 'to' - otherwise the fields would need to be labeled.
A variation would be to allow the 1st field to be an operator select as in the example above. Since #1632 will replace this in the near future, we want to limit this to either the between solution, or add the operator option at most.
Quick wireframe:

@colinreedmiller Did you mean to not include the x close icon that the existing string filter has?  I don't feel strongly either way, but we should probably make them match.

@amellnik The image above is just a quick wireframe to illustrate the text above it.


Add checksum to datasets

All datasets that download an archive should have a checksum when downloading from the default address, see comment.
md5 would be enough for capturing obvious archive corruption.

[ ] VCTK: 45e8dede780278ef5541fde0b82ac292
[ ] YesNo:
[ ] LibriSpeech:
[ ] SpeechCommands:
[ ] LJSpeech:
[ ] CommonVoice:

speech_commands_v0.02 -> 6b74f3901214cb2c2934e98196829835


React / Redux design spike

Expected Behavior
Work up an MVP implementation of a React/Redux app.
Context
Proof of concept for reusable components and architecture that will benefit development moving forward.

https://react.rocks/
http://vizuly.io/product/radial-progress/?demo=d3js
http://www.bitjuice.com.au/research/#hierarchicalclassificationexample

Findings were discussed during team sync today and documented at: https://docs.google.com/document/d/1KAp-USJf8COdH__w6mVolPuri_fZMupaSu-WAAlWAwU/edit


storage: return start TS of mismatching lock in TxnNotFound

What problem does this PR solve?
Issue Number: ref #11148
To resolve another case of optimistic deadlock. See #11148 for details.
What is changed and how it works?
When CheckTxnStatus or TxnHeartbeat encounters a mismatching lock, return the lock TS in the TxnNotFound error.
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Avoid deadlock in optimistic transactions.

Close because we change the way of resolving the issue.


Update EDMF parameter notation.

Updates the naming convention for one of the EDMF parameters, following the parameter table in Cohen et al (2020). It also fixes the default value of static_stab_coefficient c_b.

For now, I included c_γ in the src/ClimaParams.jl script in TC.jl, so I was able to merge the change. Is this still a breaking change after I removed c_t from the TC.jl codebase @charleskawczynski ?

For now, I included c_γ in the src/ClimaParams.jl script in TC.jl, so I was able to merge the change. I think this will not break TC.jl after I removed c_t from the TC.jl codebase @charleskawczynski ?

Yes, but will it break any other packages? Several other packages use CLIMAParameters (e.g., CloudMicrophysics.jl).

My idea is to first create a release of TC.jl, then of ClimaParameters.jl, so that the update does not break the code of users after they update TC.jl. But yes this will require a breaking release.

For pre 1.0.0, nothing will automatically break if we bump the minor version (0.2.3 = major.minor.patch) because ] up will only auto update the patch version. For pre 1.0.0, Minor versions need to be updated manually, allowing us to merge / release this PR, then merge/release TC.jl

bors r+

bors r+


Feature: Find datadicts matching a set of conditions

This pull request adds a method plottr.data.datadict_storage.search_datadicts, which returns an iterator over datadicts matching a set of conditions.
The following conditions are currently supported:

since: Date (and time) in the format YYYY-mm-dd (or YYYY-mm-ddTHHMMSS).
until: Date (and time) in the format YYYY-mm-dd (or YYYY-mm-ddTHHMMSS). If not given, default to until = since.
name: Name of the dataset (if not given, match all datasets).

For convenience, I've also added a method plottr.data.datadict_storage.search_datadict, which asserts that there is only one matching datadict.

Resulved a merge conflict with #375

I really like this feature! But at the moment if the search encounters any invalid data (the writer always creates a file even if the nothing is inside of it) the whole search fails. Because of this, it is hard to test on my end.
I am also a little unsure if its a good idea that the search_datadicts returns the generator instead of a list with all the matching datadicts. It is a good idea to have the generator since the datadicts might be big, but having both the generators and a function that returns a list might be a good idea too and shouldn't take much effort. @wpfff what do you think?

Thanks! I think I've resolved the error you encountered by fixing a bug in datadict_from_hdf5. Could you test this again?

Added the following search conditions:

only_complete: Only return datadicts tagged as complete. Defaults to True.
skip_trash: Skip datadicts tagged as trash. Defaults to True.

No worries! Sorry about flooding you with many pull requests recently, I don't mean to rush you at all.
Here's a usage example:
from plottr.data.datadict_storage import DataDict, DDH5Writer, search_datadicts, search_datadict

basedir = "C:\\plottr-data"

# create two datasets
data = DataDict(x=dict(), y=dict(axes=["x"]))
with DDH5Writer(data, basedir, name="test") as writer:
    writer.add_data(x=[1, 2, 3], y=[1, 2, 3])
data = DataDict(x=dict(), y=dict(axes=["x"]))
with DDH5Writer(data, basedir, name="test") as writer:
    writer.add_data(x=[1, 2, 3], y=[3, 2, 1])

# print all datasets named "test" from today
for foldername, datadict in search_datadicts(basedir, "2023-03-17", name="test"):
    print(foldername, datadict["x"]["values"], datadict["y"]["values"])

# print just the newest one
foldername, datadict = search_datadict(basedir, "2023-03-17", name="test", newest=True)
print(foldername, datadict["x"]["values"], datadict["y"]["values"])

# print the one with specific date and time
foldername, datadict = search_datadict(basedir, "2023-03-17T200540", name="test")
print(foldername, datadict["x"]["values"], datadict["y"]["values"])

@yoshi74ls181 off-topic, but i couldn't find a way to message you in a different way :)
it was great meeting you at the APS meeting! could you maybe let me know your email address? (you can email me directly at wpfaff at illinois dot edu)

@wpfff Have you received my email? I'm worried that it might have ended up in your spam folder because I sent it from my personal gmail account (I lost access to my university email when I graduated). No worries if it's just that you've been busy.

this function is useful, and we have a similar one in our lab code -- but i'm not sure it should be part of plottr itself.
there's  a few conceptual issues:

it's hard to make this useable from the monitr gui
it assumes a particular way of data naming/storing, which we don't want to enforce in the package (currently you can easily change how naming works by making your own data writer, and everything else will keep working)

we're currently thinking on how to filter better in monitr, but we're not sure yet on the correct approach.
I'm closing this for now, and we can re-open if needed.


Add yes/no dialog for high score reset

To avoid accidentally clearing the high score.

I can't seem to trigger the easter egg anymore.
Anyway, going to merge since your PR is more useful than getting a Rick Roll after some button clicks.


Add PHP client

Description
Add PHP client docs
Issues Resolved
#282
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

anything missing here? 😅

@ashwinkumar12345 can this be merged and deployed as well?


Handle future year reforms for checkboxes

There's one provision in TCJA Senate Modified Mark's proposal that introduces "stack[ing] the dependent credit before the child tax credit" in 2018, and then repeals it starting 2026.
Currently, this boolean parameter _DependentCredit_before_CTC is handled using a checkbox on TaxBrain: checked box indicates true while unchecked one represents false, which I believe is a concise way of integrating such boolean parameters. It seems that, however, such format won't allow users to specify any further reforms for future years.
Since it would be desirable to handle both House and Senate reforms in TaxBain's GUI, we might want to modify, at least for _DependentCredit_before_CTC parameter, the way of handling boolean fields to allow future year reforms. However, I haven't come up with an ideal way to deal with it.
Any comments, concerns or remarks would be helpful. @martinholmer @MattHJensen @hdoupe

Do you think we should add a "Byrd Rule" switch that reverts changes to the default after 10 years?  We could present it the same way as the cpi buttons.

@hdoupe said:

Do you think we should add a "Byrd Rule" switch that reverts changes to the default after 10 years?

I don't know what the "Byrd Rule" is.  Exactly how would it help resolve issue #765?
The fundamental problem @GoFroggyRun pointed out in #765 is that any policy parameter represented in TaxBrain with a check box has no time dimension.  So, unlike in Tax-Calculator, it can't be turned off or on in any year.  As far as I can see, the only way for TaxBrain to have the same flexibility as Tax-Calculator has in changing policy parameters year by year, would be for TaxBrain to convert all check boxes to text boxes just like all the other one-dimensional parameters like _II_em or _SS_Earnings_c.

Sorry, I shouldn't have used Byrd Rule. I don't really know what it means.  I just hear it in conjunction with policy changes that are reverted back to the default after 10 years or so.  This seems like a common maneuver to satisfy budget rules.  I was thinking that we could have a switch similar to the CPI button that reverts these changes back after 10 years.
However, this isn't a very good solution.  It would be best for the user to have the flexibility to turn switches on or off after x years.  x being 3 or 10 shouldn't matter.
@martinholmer  said

As far as I can see, the only way for TaxBrain to have the same flexibility as Tax-Calculator has in changing policy parameters year by year, would be for TaxBrain to convert all check boxes to text boxes just like all the other one-dimensional parameters like _II_em or _SS_Earnings_c.

This could work, and I can't think of another solution either.  My only objection is that it may not be obvious whether the user is supposed to enter a binary value such as 0/1 or True/False, or a numeric value.

@hdoupe:

This could work, and I can't think of another solution either.

Agreed.

My only objection is that it may not be obvious whether the user is supposed to enter a binary value such as 0/1 or True/False, or a numeric value.

I suppose we'd have to update the user instructions at the top of the page. The user would also see the default value, so that would be a strong hint.

@MattHJensen said

I suppose we'd have to update the user instructions at the top of the page. The user would also see the default value, so that would be a strong hint.

Ok, that makes sense.
Converting the checkbox parameters to text box parameters should be an easy change to make.  The only part that I am worried about is that we have to change the data type for these parameters in the database.  Given my previous misadventures with altering the database, I plan to proceed with caution while doing this.

I'm going to keep #765 open until all of the boolean parameters are presented in a comma separated format.

Closed via #822

Closed via #822


Delete "bad" characters in the auto-generated id field

We can take out all non-alphanumeric characters. At least we want to get rid of :


Is there a custom vision endpoint in a non-US region e.g. Europe?

I have searched and searched, been directed to marketing by Azure, asked on stackoverflow, am not sure whether this is the right place to ask, but:
What are the custom vision endpoints apart from southcentralus?
If they are not yet available, when will they be?
Thanks

@areddish please? :)

Closing, since the question is answered. Thanks @areddish !


[feat] Implement OP_SUB opcode

Implement the OP_SUB opcode using the opcodeSub reference implementation from btcd
References
Guide on how to add an opcode in shinigami

hi @b-j-roberts  , may i be assigned to this issue? :)

For sure, @TAdev0 . Glad to have you on the project!


a filter / limit / range function that works at the aggregate level in the table

hide , decorate rows that meet certain conditions


[SPARK-44272][YARN] Path Inconsistency when Operating statCache within Yarn Client

What changes were proposed in this pull request?

Change statCache.getOrElse to statCache.getOrElseUpdate so that the corresponding FileStatus can be cached into statCache
Change the Path parameter isPublic,  checkPermissionOfOther, and ancestorsHaveExecutePermissions to URI.
Add getParentURI method when we construct the parent URI.

Why are the changes needed?

We should not use uri.getPath() when constructing the Path which will not retain information like scheme. This means that statCache is not really taking any effect.
For example, if uri is "file:/foo.invalid.com:8080/tmp/testing", then
uri.getPath -> /foo.invalid.com:8080/tmp/testing
uri.toString -> file:/foo.invalid.com:8080/tmp/testing

Please also see more details from JIRA ticket.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Add additional UT to validate the FileStatus is cached as expected.

cc: @mridulm @otterc  @zhouyejoe @xkrogen  Thanks.

Can you fix the linter issues ? Please do update to latest master, which should help with some of them

Merged to master and branch-3.5.
Thanks for working on this @shuwang21 !
FYI @xuanyuanking, who is RM for 3.5


Does not work with webpack, react-native

See #36 for the relevant PR
This module works great with in server-side and browserify (haven't tested it myself though) but I want to use this module in my webpack based project and in my react-native project.
Right now this module use of the core node library require('fs') is incompatible with these environments without additional configuration, like btfs. I want to replace usage of fs by requiring the text modules directly if possible.
I'd like to make this change in two steps.

Move all the code that reads the text files to a new file

Use require() to read those data files. A downside here is that we need to wrap the files with some ES6 javascript to load the string properly. This is easy enough to accomplish with a node script I wrote or shell one-liner.

I'm happy to rebase this commit https://github.com/zurawiki/Hanzi/commit/af3af629356ee2cb3ab9ca01fc08caea0917dc69 if you would accept a pull request.

In my nextgen branch https://github.com/zurawiki/Hanzi/tree/nextgen I made a number of structural changes including

consolidating all the data files into one directory
consolidating and organizing test code
adding tooling for the non module that allows developer to write more modern, succinct ES6+ JavaScript
integrate linting and other common code formatting tools to the repo
setting up continuous integration testing over a variety of node.js version (with browser environments planned)

Let me know if you would want to merge any of these changes and I'm happy to send the pull requests your way!

Woah @zurawiki!
Amazing ideas here! Hanzi definitely needs some updating to catch up with modern JS. Let me look through your code and think through a few things here and I'll get back to you soon.

Heya @zurawiki,
so sorry for my delay. Would like to keep the momentum here.
I wonder, if we could break these into different PRs. The ones I'm most excited about & thinking about how to split this up:

Moving to requiring files instead of using fs.
Updating things to ES6.
Linting + improved testing environment + continuous integration
Script to update the CC-CEDICT data
Consolidating all data files

I wonder if it's possible to create separate PRs for those? I might be a tricky I imagine. What do you think? I'm happy to take in any combination here to make pulling your amazing work easier for you. For example, consolidating the data files might be easy to add another PR.
Again, thanks for all these amazing improvements! Excited for this.

Any updates on this @nieldlr?
Thanks!

Heya @Dans-io, this should be on master at the moment (merged here: https://github.com/nieldlr/Hanzi/pull/36). I haven't quite fully run the tests for these in webpack/react-native setups. Feel free to give it a try. 👍 It should be all smooth.
I still to publish these updates to npm if that might what you're looking for?

Oh got it. Yes I was asking because it got it from NPM earlier today and the issue was still there. Thank you so much for building this, it's really great.

@Dans-io awesome. I'll see if I can publish a new version sometime today.
Thanks for the kind words!

Heya @Dans-io, it should now be published under v2.0.0. Have fun! Let me know if there's anything else you need.


[cleanup][broker]Cleanup getNamespacePolicies when update TopicPolicies

Motivation
No need to get namespace policies when update topic policies, Because we have used HierarchyTopicPolicies
Modifications
Remove  getNamespacePolicies
Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] no-need-doc
(Please explain why)

/pulsarbot run-failure-checks


added an option 'byAction' to perform clipboard cut, default is true

Added an option byAction to perform clipboard cut operation, default is true
The cut action is implemented by #451

Looks alright to me! :)


Question about x11vnc version

Hi Doro!
I have another question. I notice that your container is using a newer version of x11vnc server (0.9.14) from your own Ubuntu PPA rather than the official version (0.9.13) from the repository.
Why did you make this choice?
Would your container still work with version 0.9.13?
Does 0.9.14 offer better performance? Or maybe better compatibility with novnc or better managment of web sockets?
Thank you!
jerome

@jeromecc
0.9.13 failed to start if the kernel do not support IPv6 well.


Maintenance of PandasMethodsComponent class that is component of IntroToPandasGuide

The goal of the issue is to review and/or improve the class that implements report component within guides.en.py module,

Component has been reviewed and approved.


fix(package): update validator to version 10.1.0

Closes #73

Coverage remained the same at 97.535% when pulling b338fc2315abb181db0db832d168d1cec046a5f8 on greenkeeper/validator-10.1.0 into fb55785df24eae971a17370ace23b98a8e5fbb6f on master.


show a link to the created issue so it can be reviewed and edited if needed

last bit missing for finishing up step 2 of https://github.com/hoodiehq/camp/issues/105

already done, I just missed the link :)


[bug] LLC flag --show-models

when I run autorest --version=3.4.5 --python --track2 --use=D:\dev5\autorest.python --use=<EMAIL_ADDRESS>--python-sdks-folder=D:\dev5\azure-sdk-for-python\sdk --python-mode=update   D:\dev2\azure-rest-api-specs\specification\datadog\resource-manager\readme.md   --low-level-client  --show-models --show-operations, the following error happened:

I think the reason is here : https://github.com/Azure/autorest.python/blob/33e3bec3177d5ab3a21fc43f472e247c5aaa3657/autorest/codegen/init.py#L255-L263
I find it could work when using --show-models=msrest. But it seems very strange.
more test:
--show-models=true : same error
--show-models=True : same error
--show-models=false : same error
--show-models=False : same error

Hey @msyyc this is by design, the current values are msrest and false (we’re hoping to add more version tolerant models later)

hey @msyyc want to circle back to this issue and say thanks!
Even though the behavior wasn't technically a bug, your issue made me think that --show-models can be confusing bc it sounds like the value should be a True / False value. We're thinking of switching it over to --models-mode=msrest|False, what are your thoughts?

If there will be more values for model, I think --models-mode is better. And also,  False seems not a good mode name.

@msyyc do you have another suggestion for no having models? I agree it does sound weird, but having a hard time improving on it. Idk if we can do better because we are using the flag to represent both whether you want models or not, and also what kind of models you want

How about --models-mode=null or --models-mode=none? I think it is easier to understand than False

@msyyc love those ideas, going to go with --models-mode=none since none is more pythonic than null. Thanks so much for the great suggestion!


add disclaimer modal to landing page

Create a disclaimer modal to open before proceeding to next page to log in or sign up.
Disclaimer will read: "Please note that The contents InnerPattern, such as text, graphics, images, and other material or links contained on the IBPF Site are for informational purposes only. The Content is not intended to be a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of your physician or other qualified health provider with any questions you may have regarding a medical condition. Never disregard professional medical advice or delay in seeking it because of something you have read on the InnerPattern site.


Online experiment error

Hi,
First of all thank you for developing a very useful library with a good documentation guide.
I am using this library for a EEG classification and was really interested in trying the online code which is given.
I am getting an error as shown in below image when I run the code.
Could you please let me know what's the issue
Thank you

hey,
I don't know if you already figured out the problem or are still interested but it might be helpful for other people to know what was up.
So apparently in the package version of libmushu that you installed, the configure() method doesn't expect a keyword argument "blocksize_samples". Could you try to install libmushu manually as it is explained here: https://github.com/bbci/mushu and see if it works then ?
Because looking at the source code on the github page, the configure() method should take such an argument, at least in the case of an replayamp (https://github.com/bbci/mushu/blob/master/libmushu/driver/replayamp.py#L14).

The arguments for the configure method are entirely dependent on the amplifier (driver) that is used. In your case the blocksize_samples is not supported (see the definition of the confiugre method)


No loading of configuration after reimport of SQL dump

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? -> xes
Are you sure you're not using someone else's docker image? -> yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? -> yes

Describe the bug

after a restore of the configuration (db entries) all SSL Certificates and Configuration is back. But it is not functional. I have to open a configuration an simply save it without any edit and now the SSL configuration is working.

To Reproduce
Steps to reproduce the behavior:
after a restore (docker exec -it db bash -c "mysql -uXXX -pYYYY nginx < /var/www/html/interface/nginx/nginx-backup.sql")  of the configuration (db entries) all SSL Certificates and Configuration is back. But it is not functional. I have to open a proxy host configuration and simply save it without any edit and now the SSL configuration is working.
Without these "edit" I get a NET::ERR_CERT_INVALID error message.
Is there any way to do these edit via script?
Expected behavior
After loading the backup everything working without editing and saving each entry of host proxy configuration.
Operating System

Docker in Mac OS (latest versions)

Additional context

Chrome and Safari

When you restored the SQL backup, did you also restore all the configuration files that are stored in the /data volume?
Nginx doesn't read its configurations from the database, it loads the files stored in /data. It sounds like you've restored the database but not the configuration files. Re-saving the hosts will re-generate the Nginx configs and reload Nginx so it picks up the changes.

That was the missing hint. After saving and restoring the folder /data/nginx together with a database dump and restore now everting is back and ready to work.


⚠ Bofrost.at has degraded performance

In 8b84c44, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1513 ms

Resolved: Bofrost.at performance has improved in 539f3f2 after 306 days, 7 hours, 27 minutes.


[UI] Android logs tab doesn't auto-refresh when entering text in log search filter

If you enter search text in the android logs tab, the logs don't refresh until you attempt to scroll the logs, or take some other action that would normally cause that section of the UI to redraw. If there are not enough logs in the tab for a scroll bar to appear then this workaround can't be used.
This reproduces on Canary and Autopush (v48.1), but not on Stable (v47).
How to reproduce:

open the android_log.pb from the test data in the perfetto git repo: ./tools/open_trace_in_ui test/data/android_log.pb
enter text in the field labeled "Search logs..."
mouse wheel scroll down in the logs.
Observe the search filter is only applied once you start scrolling instead of immediately

https://github.com/user-attachments/assets/9b937daf-2cbf-4c6c-8c61-b38fd2e5582c

Thanks for filing. https://r.android.com/3326027 should fix.


Fix for problem outputting style elements

I found that the content of the style elements was being escaped as if it were an HTML text node.  This causes problems with things like background-image: url('my.png') which are then output as background-image: url('my.png').  Script tags were already being exempted from this escaping, so I've added style tags to that conditional as well and added a test case for this.

Coverage remained the same at 100.0% when pulling 5967b0a337ed416882d5e26ccc5df7b470b30b73 on lightman76:dont_escape_style_element_content into 77b635e88765ee4e7414d5bc2763ffc7c31d7925 on nthtran:master.

Thanks! Released as 2.3.1.


Compat tf v1.x version

Thank you for submitting a pull request! Please provide the following information for code review:
Pull Request Summary
SATT
fix #135
fix #143
#142
Test Plan
run all unit test and dpl scripts.

Didn't quite look into this, but LGTM at first sight :)


Attach release file and ignore edit release message

I want to attach files to a release from bash script but when I run hub release edit $RELEASE_TAG -a $FILE_PATH hub always forces to edit release message in vi/vim.
Can you parametrize that does not require the editing of the message? This would facilitate the use of hub in scripts

From hub help release:

To re-use existing title and body unchanged, pass -m "".

But I agree, this is not optimal. Maybe this will change in a future release. Thanks for writing in!


createHierarchy segfault

preprocessing data from input file great_britain.osrm using STL serial mode
Importing n = 8291624 nodes ... and 8732334 edges ...ok
initializing contractor ...Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
ok
removed 15822 edges of 17464658
Contractor is using 2 threads
initializing elimination PQ ...ok
preprocessing .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
[contractor] checking sanity of generated data ...ok
[contractor] max level: 95
sorting level info
writing level info
Scanning for useless shortcuts
Removing edges
Removed 1894 useless shortcuts
Serializing edges . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
writing node map ...ok
[STXXL-MSG] STXXL v1.2.1 (release)
[STXXL-ERRMSG] Warning: no config file found.
[STXXL-ERRMSG] Using default disk configuration.
[STXXL-MSG] 1 disks are allocated, total space: 1000 MB
building grid .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
sorting grid data consisting of 9423259 edges...ok in 16.9068s
writing data .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
finished
Segmentation fault (core dumped)```

Where is the core dump data saved to for inspection?

Are you using stxxl 1.2.x? If so, please switch to 1.3.1.
You should be on the safe side ignoring this error, because once
createHierarchy says "finished" it has finished writing all data to
disk. Previous versions of stxxl had a non-serious bug where this
segfault may happen.
Am 09.11.2011 17:21, schrieb Sam Tuke:

preprocessing data from input file great_britain.osrm using STL serial mode
Importing n = 8291624 nodes ... and 8732334 edges ...ok
initializing contractor ...Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
Edge Weight too large -> May lead to invalid CH
ok
removed 15822 edges of 17464658
Contractor is using 2 threads
initializing elimination PQ ...ok
preprocessing .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
[contractor] checking sanity of generated data ...ok
[contractor] max level: 95
sorting level info
writing level info
Scanning for useless shortcuts
Removing edges
Removed 1894 useless shortcuts
Serializing edges . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
writing node map ...ok
[STXXL-MSG] STXXL v1.2.1 (release)
[STXXL-ERRMSG] Warning: no config file found.
[STXXL-ERRMSG] Using default disk configuration.
[STXXL-MSG] 1 disks are allocated, total space: 1000 MB
building grid .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
sorting grid data consisting of 9423259 edges...ok in 16.9068s
writing data .... 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
finished
Segmentation fault (core dumped)```

Where is the core dump data saved to for inspection?

---
Reply to this email directly or view it on GitHub:
https://github.com/DennisOSRM/Project-OSRM/issues/24

--
Karlsruher Institut für Technologie (KIT)
Institut für Theoretische Informatik
Dennis Luxen
Wissenschaftler
Am Fasanengarten 5
Gebäude 50.34, Zimmer 220
76131 Karlsruhe
Telefon: +49<PHONE_NUMBER>1
Fax:     +49<PHONE_NUMBER>8
E-Mail<EMAIL_ADDRESS>KIT - Universität des Landes Baden-Württemberg und nationales
Großforschungszentrum in der Helmholtz-Gemeinschaft

Thanks for the feedback.
I am using 1.2. Good to know the error isn't fatal.
no .names file has been generated however; I assumed this was due to the segfault - is this in fact unrelated? routed will not start due to missing .names file.
Sam.

I have also tried using a .names file from another instance of OSRM on another machine (using the same .osrm map data file however), and get another segfault, this time from routed:
[server] starting up engines, saved at Wed Nov  9 13:03:50 2011
[server] http 1.1 compression handled by zlib version 1.2.5
[objects] loading query data structures ...Segmentation fault (core dumped)```

Not sure why no names files has been generated. Tested twice on
different test sets and it works fine every time.

Thanks for the feedback.
I am using 1.2. Good to know the error isn't fatal.
no .names file has been generated however; I assumed this was due to the segfault - is this in fact unrelated? routed will not start due to missing .names file.
Sam.

Reply to this email directly or view it on GitHub:
https://github.com/DennisOSRM/Project-OSRM/issues/24#issuecomment-2683823

I refreshed the repository and recompiled, the routed segfault has disappeared, so closing this issue.

Thanks for the feedback


Mocked object loses the mock

Describe the bug
When I inject a mocked object on a object generated by fixture monkey the mock is lost.
I tried using the MockitoPlugin as well but made no difference.
Your environment
0.4.11
Java 17
Steps to reproduce
Run the mockTest() located here:
https://github.com/esfomeado/fixture-monkey-bug/blob/master/src/test/java/com/example/bug/FixtureMonkeyTest.java
Expected behaviour
The generated object should retain the mock
Actual behaviour
The mock is lost.

I was under the impression that fixture monkey would replace the object but instead it seems that it copies the properties so this seems to be impossible since fixture monkey performs a copy instead of replacing the object.
Correct me if I´m wrong.

@esfomeado
Thank you for finding an issue.
We are going to enhance supporting mockito since 0.5.
This issue would be resolves in 0.5
Let me know If you are in a hurry. It would be fixed in 0.4.14 then.
Please make a comment for any other good ideas with mockito.
https://github.com/naver/fixture-monkey/issues/529

@seongahjo Take your time.
I did a workaround in the meantime.
Once you release 0.5 I will go back and fix it.

@esfomeado
0.5.1 is released!
You could set mocked object by set("expression", Values.just(mockedObject)


Release 0.3

Codecov Report

Merging #20 (17241ae) into main (b0cfb75) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   78.08%   78.08%
=======================================
  Files           5        5
  Lines          73       73
  Branches        4        4
=======================================
  Hits           57       57
  Misses         15       15
  Partials        1        1

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 b0cfb75...17241ae. Read the comment docs.


Why does setattr(self, f"xyz_encoding_{i+1}", layer)

As what is described in the  title, I'm confused by the code :
setattr(self, f"xyz_encoding_{i+1}", layer)
in the 69th line of  ./models/nerf.py.
What does xyz_encoding_{i+1} mean? And why do you use it there? It's not an attribute of the Class Nerf.
Thank you for your reply.

I have solved it, thank you.


use mppi instead of dwb path follower

Mppi seems to perform way better than dwb even with these basic settings.

btw, the controller is not part of the current nav2 bundle in my copr, you can install the ros2-nav2_mppi_controller package if you want to play around it on your machine.
Thanks for the swift review!


Add new Snitch type

Add a snitch that's a diamond block, identical in behavior to juke box but cuboid of 20 and it's own expiry time config option.

@drjawa What do you think.  Going to assign you for discussion.

What is the goal of this change?
On Jun 20, 2015 1:38 AM, "rourke750"<EMAIL_ADDRESS>wrote:

@drjawa https://github.com/drjawa What do you think. Going to assign
you for discussion.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113712816.

Not against but want to understand purpose.
On Jun 20, 2015 1:39 AM, "Andrew Jawa"<EMAIL_ADDRESS>wrote:

What is the goal of this change?
On Jun 20, 2015 1:38 AM, "rourke750"<EMAIL_ADDRESS>wrote:

@drjawa https://github.com/drjawa What do you think. Going to assign
you for discussion.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113712816.

Looks like only a larger snitch field. Is the current 11 block 'radius'
insufficient to hide the snitch from X-Ray with the current orebfuscator?
On Fri, Jun 19, 2015 at 10:42 PM, Dr. Andrew Jawa<EMAIL_ADDRESS>wrote:

Not against but want to understand purpose.
On Jun 20, 2015 1:39 AM, "Andrew Jawa"<EMAIL_ADDRESS>wrote:

What is the goal of this change?
On Jun 20, 2015 1:38 AM, "rourke750"<EMAIL_ADDRESS>wrote:

@drjawa https://github.com/drjawa What do you think. Going to assign
you for discussion.
—
Reply to this email directly or view it on GitHub
<https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113712816
.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113712897.

Well currently snitches aren't being obfuscated at all due to oreobfuscator
being borked. Adding jukes and noteblocks to list does not with spigots ofc.

_>

Maybe we should just convert snitches to be blocks that we can properly
obfuscate (Though that is the lazy and bad way out).
On Sat, Jun 20, 2015 at 5:53 AM, erocs<EMAIL_ADDRESS>wrote:

Looks like only a larger snitch field. Is the current 11 block 'radius'
insufficient to hide the snitch from X-Ray with the current orebfuscator?
On Fri, Jun 19, 2015 at 10:42 PM, Dr. Andrew Jawa <
<EMAIL_ADDRESS>wrote:

Not against but want to understand purpose.
On Jun 20, 2015 1:39 AM, "Andrew Jawa"<EMAIL_ADDRESS>wrote:

What is the goal of this change?
On Jun 20, 2015 1:38 AM, "rourke750"<EMAIL_ADDRESS>wrote:

@drjawa https://github.com/drjawa What do you think. Going to
assign
you for discussion.
—
Reply to this email directly or view it on GitHub
<
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113712816
.

—
Reply to this email directly or view it on GitHub
<https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113712897
.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113713129.

either way why larger radius snitches? I guess lower matience at much higher cost, which I guess is reasonable, but even a factor of 9 is pretty affordable to some people.
Does increase the theft chance though.
Wait, how do we keep all placed diamond blocks from becoming snitches by default?

The way we do the other blocks.
Its larger and nore expensive to make snitching large areas easier, at the
cist of less efficiency
On 20 Jun 2015 14:20, "ttk2"<EMAIL_ADDRESS>wrote:

either way why larger radius snitches? I guess lower matience at much
higher cost, which I guess is reasonable, but even a factor of 9 is pretty
affordable to some people.
Does increase the theft chance though.
Wait, how do we keep all placed diamond blocks from becoming snitches by
default?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113773469.

I can get the argument, what do you mean the same way we do for other blocks? The old crouch while you place thing?

You really haven't played civcraft in a while have you.
Certain blocks when reinforced automatically become snitches on placement
On 21 Jun 2015 21:15, "ttk2"<EMAIL_ADDRESS>wrote:

I can get the argument, what do you mean the same way we do for other
blocks? The old crouch while you place thing?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113960672.

I am aware, but people use DIamond blocks in decorative purposes, or for beacons, should they just automatically make a beacon of snitches?

/ja mute the group
On Sun, Jun 21, 2015 at 9:36 PM, ttk2<EMAIL_ADDRESS>wrote:

I am aware, but people use DIamond blocks in decorative purposes, or for
beacons, should they just automatically make a beacon of snitches?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113962575.

That's a horrible solution. Crouch placing is probably the way to go.
On Mon, Jun 22, 2015, 2:27 AM Goldmattress<EMAIL_ADDRESS>wrote:

/ja mute the group
On Sun, Jun 21, 2015 at 9:36 PM, ttk2<EMAIL_ADDRESS>wrote:

I am aware, but people use DIamond blocks in decorative purposes, or for
beacons, should they just automatically make a beacon of snitches?
—
Reply to this email directly or view it on GitHub
<https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113962575
.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-114027052.

No one is complaining about the current system, it's completely fine we've
been doing it this way for 2+ years now.
 Crouch placing is probably the way to go.
On Mon, Jun 22, 2015, 2:27 AM Goldmattress<EMAIL_ADDRESS>wrote:

/ja mute the group
On Sun, Jun 21, 2015 at 9:36 PM, ttk2<EMAIL_ADDRESS>wrote:

I am aware, but people use DIamond blocks in decorative purposes, or
for
beacons, should they just automatically make a beacon of snitches?
—
Reply to this email directly or view it on GitHub
<
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-113962575
.

—
Reply to this email directly or view it on GitHub
<https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-114027052
.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-114084286.

Could just have if you don't give it a name via /janame then it doesn't record / is inert.

Nooo, I've forgotten to name thousands of snitches and I know a lot of
people never bother, just make a command so that when you break the block
it removes the snitch but keeps the block and reinforcement.
It is so much more common to be using these blocks in the context of JA
that it should be assumed that that is what the player is doing.
On Mon, Jun 22, 2015 at 8:04 PM, Daniel Boston<EMAIL_ADDRESS>wrote:

Could just have if you don't give it a name via /janame then it doesn't
record / is inert.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-114241575.

I buy it. Can't think of the last time I used a Dblock as decoration.

very well then, I agree on everything except maybe having members refresh them, if we can think of a better mechanic maybe we should do that.
Having incentive to need to trust more people to help maintain such a network is very nice IHMO.

Well if your set on that a longer time till cull should do the same in the
long run
On 22 Jun 2015 22:35, "ttk2"<EMAIL_ADDRESS>wrote:

very well then, I agree on everything except maybe having members refresh
them, if we can think of a better mechanic maybe we should do that.
Having incentive to need to trust more people to help maintain such a
network is very nice IHMO.
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/JukeAlert/issues/29#issuecomment-114288122.

sounds good.

Anyone have time to do this at some point?

I don't think anyone sees this as a priority.

No not at all, I'm just wondering before I write better documentation for JA.

skip it for now.

This feature is no longer desired and the general idea should rather be part of a refactor to allow more dynamic snitch configurations


Change seeder prints to be useful and consistent

Currently running the seeder causes a bunch a random prints.
A consistent printing system would be better

Did do this.


Our app is crashing on launch

How frequently does the bug occur?
Sometimes
Description
We were using Realm version 10.24 and getting the same crash then we reverted back to 10.20 and the crash was consistent. We are not able to reproduce this issue on our side but our customers are reporting the crash. Any help or suggestion will be appreciated. This is happening on almost all of the devices and OS versions so it is hard to guess the reason on our side. Also, not all of our users are facing the crash though.
Stacktrace & log output
Date/Time:           2022-04-24 07:35:12.9428 -0600
Launch Time:         2022-04-24 07:35:12.8429 -0600
OS Version:          iPhone OS 15.4 (19E241)
Release Type:        User
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Triggered by Thread:  0

Thread 0 name:
Thread 0 Crashed:
0   libsystem_kernel.dylib        	0x00000001b7357b78 __pthread_kill + 8
1   libsystem_pthread.dylib       	0x00000001f03a43bc pthread_kill + 268 (pthread.c:1668)
2   libsystem_c.dylib             	0x000000018b6ed51c abort + 168 (abort.c:118)
3   Realm                         	0x0000000102bb66a0 please_report_this_issue_in_github_realm_realm_core + 12
4   Realm                         	0x0000000102bb69a0 realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 328
5   Realm                         	0x0000000102bb6b18 realm::util::terminate(char const*, char const*, long, std::initializer_list<realm::util::Printable>&&) + 328
6   Realm                         	0x0000000102919608 void realm::util::terminate_with_info<char const&, unsigned long&>(char const*, int, char const*, char const*, char const&, unsigned long&) + 366088 (terminate.hpp:51)
7   Realm                         	0x0000000102a1c234 realm::Array::set(unsigned long, long long) + 236
8   Realm                         	0x0000000102ade8e4 realm::Node::do_copy_on_write(unsigned long) + 232
9   Realm                         	0x0000000102a1bc78 realm::Array::move(unsigned long, unsigned long, unsigned long) + 120
10  Realm                         	0x0000000102cfffc4 realm::ArrayTimestamp::erase(unsigned long) + 112
11  Realm                         	0x0000000102a457d8 void realm::Cluster::do_erase<realm::ArrayTimestamp>(unsigned long, realm::ColKey) + 108
12  Realm                         	0x0000000102a44bd8 realm::util::FunctionRef<bool (realm::ColKey)>::FunctionRef<realm::Cluster::erase(realm::ObjKey, realm::CascadeState&)::$_3&>(realm::Cluster::erase(realm::ObjKey, realm::CascadeState&)::$_3&)::'lam... + 2316
13  Realm                         	0x0000000102b8c9e8 realm::TableClusterTree::for_each_and_every_column(realm::util::FunctionRef<bool (realm::ColKey)>) const + 84
14  Realm                         	0x0000000102a3ee88 realm::Cluster::erase(realm::ObjKey, realm::CascadeState&) + 160
15  Realm                         	0x0000000102a4d084 realm::ClusterNodeInner::erase(realm::ObjKey, realm::CascadeState&)::$_3::operator()(realm::ClusterNode*, realm::ClusterNodeInner::ChildInfo&) const + 68
16  Realm                         	0x0000000102a48dc4 realm::ClusterNodeInner::erase(realm::ObjKey, realm::CascadeState&) + 240
17  Realm                         	0x0000000102a4bc20 realm::ClusterTree::erase+ 1621024 (realm::ObjKey, realm::CascadeState&) + 128
18  Realm                         	0x0000000102b80dd8 realm::Table::remove_object(realm::ObjKey) + 268
19  Realm                         	0x0000000102ae3f98 realm::Obj::remove() + 44
20  Realm                         	0x00000001029186cc RLMDeleteObjectFromRealm + 112 (RLMObjectStore.mm:189)
21  RealmSwift                    	0x0000000103378c64 Realm.delete<A>(_:) + 429156 (<compiler-generated>:0)
22  Stitcher                      	0x000000010099c118 specialized DB.cleanUp() + 7892 (Database.swift:1433)
23  Stitcher                      	0x0000000100a15ec0 DB.cleanUp() + 4 (<compiler-generated>:0)
24  Stitcher                      	0x0000000100a15ec0 StitcherCore.cleanup() + 4 (StitcherCoreInterface.swift:416)
25  Stitcher                      	0x0000000100a15ec0 specialized StitcherCore.init(db:network:user:downloadManager:settingsManager:) + 2044 (StitcherCoreInterface.swift:202)
26  Stitcher                      	0x0000000100a16a4c specialized StitcherCore.init(db:network:user:downloadManager:settingsManager:) + 28 (<compiler-generated>:0)
27  Stitcher                      	0x0000000100a16a4c StitcherCore.init(db:network:user:downloadManager:settingsManager:) + 28 (StitcherCoreInterface.swift:178)
28  Stitcher                      	0x0000000100a16a4c specialized StitcherCore.__allocating_init(db:network:user:downloadManager:settingsManager:) + 28 (<compiler-generated>:178)
29  Stitcher                      	0x0000000100a16a4c StitcherCore.__allocating_init(db:network:user:downloadManager:settingsManager:) + 28 (AppDelegate.swift:79)
30  Stitcher                      	0x0000000100a16a4c specialized AppDelegate.application(_:willFinishLaunchingWithOptions:) + 1812
31  Stitcher                      	0x0000000100a10efc @objc AppDelegate.application(_:willFinishLaunchingWithOptions:) + 144
32  UIKitCore                     	0x0000000182d06f00 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 204 (UIApplication.m:2323)
33  UIKitCore                     	0x0000000182eedda4 -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 3572 (UIApplication.m:2754)
34  UIKitCore                     	0x0000000182ed6958 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1180 (UIApplication.m:4491)
35  UIKitCore                     	0x0000000182d34590 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 152 (_UISceneLifecycleMultiplexer.m:450)
36  UIKitCore                     	0x0000000182b8ec44 _UIScenePerformActionsWithLifecycleActionMask + 104 (_UISceneLifecycleState.m:109)
37  UIKitCore                     	0x0000000182cb95ec __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke + 216 (_UISceneLifecycleMultiplexer.m:563)
38  UIKitCore                     	0x0000000182dd92fc -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:] + 248 (_UISceneLifecycleMultiplexer.m:512)
39  UIKitCore                     	0x0000000183017fa4 -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 772 (_UISceneLifecycleMultiplexer.m:562)
40  UIKitCore                     	0x0000000182fa3554 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:] + 340 (_UISceneLifecycleMultiplexer.m:468)
41  UIKitCore                     	0x0000000182b8fa30 __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block... + 196 (_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction.m:73)
42  UIKitCore                     	0x0000000182c4f934 +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:] + 892 (BSAnimationSettings+UIKit.m:50)
43  UIKitCore                     	0x0000000182b91934 _UISceneSettingsDiffActionPerformChangesWithTransitionContext + 276 (_UISceneSettingsDiffAction.m:23)
44  UIKitCore                     	0x0000000182c7baa0 -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 384 (_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction.m:58)
45  UIKitCore                     	0x0000000183100564 __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke.615 + 776 (UIScene.m:1825)
46  UIKitCore                     	0x0000000182bbfd14 -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 256 (UIScene.m:1526)
47  UIKitCore                     	0x0000000182c03528 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 288 (UIScene.m:1792)
48  UIKitCore                     	0x0000000182d39394 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 584 (UIApplication.m:3955)
49  UIKitCore                     	0x0000000182c79d64 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 388 (UIApplicationSceneClientAgent.m:45)
50  FrontBoardServices            	0x0000000192789294 -[FBSScene _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 440 (FBSScene.m:439)
51  FrontBoardServices            	0x00000001927af090 __94-[FBSWorkspaceScenesClient createWithSceneID:groupID:parameters:transitionContext:completion:]_block_invoke.215 + 128 (FBSWorkspaceScenesClient.m:384)
52  FrontBoardServices            	0x000000019276a308 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 240 (FBSWorkspace.m:352)
53  FrontBoardServices            	0x000000019276b958 __94-[FBSWorkspaceScenesClient createWithSceneID:groupID:parameters:transitionContext:completion:]_block_invoke + 372 (FBSWorkspaceScenesClient.m:383)
54  libdispatch.dylib             	0x0000000180271a2c _dispatch_client_callout + 20 (object.m:560)
55  libdispatch.dylib             	0x00000001802754e0 _dispatch_block_invoke_direct + 264 (queue.c:501)
56  FrontBoardServices            	0x000000019276bc70 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 48 (FBSSerialQueue.m:157)
57  FrontBoardServices            	0x000000019276b040 -[FBSSerialQueue _targetQueue_performNextIfPossible] + 220 (FBSSerialQueue.m:181)
58  FrontBoardServices            	0x000000019276f700 -[FBSSerialQueue _performNextFromRunLoopSource] + 28 (FBSSerialQueue.m:194)
59  CoreFoundation                	0x000000018062cf04 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1972)
60  CoreFoundation                	0x000000018063dc90 __CFRunLoopDoSource0 + 208 (CFRunLoop.c:2016)
61  CoreFoundation                	0x00000001805771e8 __CFRunLoopDoSources0 + 368 (CFRunLoop.c:2061)
62  CoreFoundation                	0x000000018057cb4c __CFRunLoopRun + 828 (CFRunLoop.c:2951)
63  CoreFoundation                	0x00000001805906b8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268)
64  GraphicsServices              	0x000000019c62a374 GSEventRunModal + 164 (GSEvent.c:2200)
65  UIKitCore                     	0x0000000182ef5e88 -[UIApplication _run] + 1100 (UIApplication.m:3511)
66  UIKitCore                     	0x0000000182c775ec UIApplicationMain + 364 (UIApplication.m:5064)
67  Stitcher                      	0x000000010098beb8 main + 68 (AppDelegate.swift:22)
68  dyld                          	0x00000001014cdce4 start + 520 (dyldMain.cpp:879)

Can you reproduce the bug?
Not yet
Reproduction Steps
Not able to reproduce on our side.
Version
10.20
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 10.15.4
Build environment
Xcode version: 13.2.1
Dependency manager and version: Cocoapods 1.10.2

@ericjordanmossman without a reproduction it is difficult to say what the cause is of a stack trace like this. To me, it looks like the assertion is about an array index out of bounds while updating from a parent which can be caused by corruption which has happened some time in the past. Perhaps the underlying issue is fixed by https://github.com/realm/realm-core/pull/5334 but it is hard to say.

@ericjordanmossman @ironage One point to mention is to try to fix this we rolled back our realm version from 10.24 to 10.20 but the crash is still the same. We just thought maybe there is any bug introduced in the new version so rollback may fix that. I forgot to mention it in the issue description above.

We are having the exact same issue - never crashed on our side, and the app got past app review; We were on Realm 10.24, and can't even cause the app to crash on our end.
 Does 10.25 fix it?

@ritesh-kanchi It may be too early for me to report if this worked but we released a new build with 10.25 and some of our users are reporting that the crash is fixed but they had to uninstall/install the new build. We are monitoring the release to see how many users are reporting the fix and based on that I can say anything with certainty.

@ayush-ttn We thought our problem was with Realm, but really had to do with type initializers and data type conversions... Some devices weren't unable to unwrap the conversions, thus crashing the app.
Your error seemed familiar to mine, so I assumed Realm - but it wasn't the case.

@ritesh-kanchi That's an interesting find. I'll keep an eye on such a thing on our side as well if the update turns out to be a downer.

Hi @ayush-ttn, do you have any updates on the issue? Does info from @ritesh-kanchi helps you?

Hey @pavel-ship-it , no the info by @ritesh-kanchi was not the case with my code. I updated to the most recent version(10.25.2) though and it seems to have fix the problem

Thank you @ayush-ttn. I close the issue then.


Clean up error handling & PB testing

This PR contains the initial sketch of the propery-based testing for endpoints as well as some cleanups in error handling.

Current coverage is 93.25%

Merging #429 into master will decrease coverage by -0.81% as of b8d50f0

Powered by Codecov. Updated on successful CI builds.