Error: Model with name BERTSeqClassification does not exist

/kind bug
What steps did you take and what happened:
Followed Doc to deploy bert sequence classifier with torchserve on Kserve.
kubectl get pod
NAME                                                              READY   STATUS    RESTARTS   AGE
sklearn-irisv2-predictor-default-00001-deployment-6476cfcdjjpws   2/2     Running   0          3h19m
torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp   2/2     Running   0          9m37s

kubectl describe pod torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp
Name:             torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp
Namespace:        default
Priority:         0
Service Account:  default
Node:             kind-control-plane/<IP_ADDRESS>
Start Time:       Wed, 30 Nov 2022 00:56:33 +0530
Labels:           app=torchserve-bert-v2-predictor-default-00001
                  component=predictor
                  pod-template-hash=5676596ddd
                  service.istio.io/canonical-name=torchserve-bert-v2-predictor-default
                  service.istio.io/canonical-revision=torchserve-bert-v2-predictor-default-00001
                  serviceEnvelope=kservev2
                  serving.knative.dev/configuration=torchserve-bert-v2-predictor-default
                  serving.knative.dev/configurationGeneration=1
                  serving.knative.dev/configurationUID=35c2e5c5-e54b-42ad-98cd-8181f7c304af
                  serving.knative.dev/revision=torchserve-bert-v2-predictor-default-00001
                  serving.knative.dev/revisionUID=09ae5676-7bdf-456f-ac91-a54128317f88
                  serving.knative.dev/service=torchserve-bert-v2-predictor-default
                  serving.knative.dev/serviceUID=84917927-1410-4f13-bb51-3dd81520d7a5
                  serving.kserve.io/inferenceservice=torchserve-bert-v2
Annotations:      autoscaling.knative.dev/class: kpa.autoscaling.knative.dev
                  autoscaling.knative.dev/minScale: 1
                  internal.serving.kserve.io/storage-initializer-sourceuri: gs://first_praveen_bucket/gcp
                  serving.knative.dev/creator: system:serviceaccount:kserve:kserve-controller-manager
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/torchserve-bert-v2-predictor-default-00001-deployment-5676596ddd
Init Containers:
  storage-initializer:
    Container ID:  containerd://0a502498a9a3b0d309ae4c7f9f1e93e4e6c79eb9477ede9edeef127c4e11de63
    Image:         kserve/storage-initializer:v0.9.0-rc0
    Image ID:      docker.io/kserve/storage-initializer@sha256:6cad6a39917c118c08eca833a16d347abf4b96342e00ddaf1535561077808192
    Port:          <none>
    Host Port:     <none>
    Args:
      gs://first_praveen_bucket/gcp
      /mnt/models
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Wed, 30 Nov 2022 00:56:34 +0530
      Finished:     Wed, 30 Nov 2022 00:58:02 +0530
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  1Gi
    Requests:
      cpu:        100m
      memory:     100Mi
    Environment:  <none>
    Mounts:
      /mnt/models from kserve-provision-location (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-k7rbd (ro)
Containers:
  kserve-container:
    Container ID:  containerd://8a3794ffc838712991c43622821bc7cac51d4be6820461f6d54b81c75fe7f7e7
    Image:         index.docker.io/pytorch/torchserve-kfs@sha256:43c1c14b2768c0cd73ce40e23da0a56176532b3c0fcb8b2217c087da3054c372
    Image ID:      docker.io/pytorch/torchserve-kfs@sha256:43c1c14b2768c0cd73ce40e23da0a56176532b3c0fcb8b2217c087da3054c372
    Port:          8080/TCP
    Host Port:     0/TCP
    Args:
      torchserve
      --start
      --model-store=/mnt/models/model-store
      --ts-config=/mnt/models/config/config.properties
    State:          Running
      Started:      Wed, 30 Nov 2022 00:58:02 +0530
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  2Gi
    Requests:
      cpu:     1
      memory:  2Gi
    Environment:
      TS_SERVICE_ENVELOPE:  kservev2
      PORT:                 8080
      K_REVISION:           torchserve-bert-v2-predictor-default-00001
      K_CONFIGURATION:      torchserve-bert-v2-predictor-default
      K_SERVICE:            torchserve-bert-v2-predictor-default
    Mounts:
      /mnt/models from kserve-provision-location (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-k7rbd (ro)
  queue-proxy:
    Container ID:   containerd://a071b637707b0573b27f5ee7e6e1c174c7d4ec9dd79d1de3c7122208ed0f2095
    Image:          gcr.io/knative-releases/knative.dev/serving/cmd/queue@sha256:a40f6e84de1a0d145d27084a94cc7fa221159e75cafde7d332ac8f4f0aed58fb
    Image ID:       gcr.io/knative-releases/knative.dev/serving/cmd/queue@sha256:a40f6e84de1a0d145d27084a94cc7fa221159e75cafde7d332ac8f4f0aed58fb
    Ports:          8022/TCP, 9090/TCP, 9091/TCP, 8012/TCP, 8112/TCP
    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
    State:          Running
      Started:      Wed, 30 Nov 2022 00:58:02 +0530
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:      25m
    Readiness:  http-get http://:8012/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      SERVING_NAMESPACE:                 default
      SERVING_SERVICE:                   torchserve-bert-v2-predictor-default
      SERVING_CONFIGURATION:             torchserve-bert-v2-predictor-default
      SERVING_REVISION:                  torchserve-bert-v2-predictor-default-00001
      QUEUE_SERVING_PORT:                8012
      QUEUE_SERVING_TLS_PORT:            8112
      CONTAINER_CONCURRENCY:             0
      REVISION_TIMEOUT_SECONDS:          300
      SERVING_POD:                       torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp (v1:metadata.name)
      SERVING_POD_IP:                     (v1:status.podIP)
      SERVING_LOGGING_CONFIG:
      SERVING_LOGGING_LEVEL:
      SERVING_REQUEST_LOG_TEMPLATE:      {"httpRequest": {"requestMethod": "{{.Request.Method}}", "requestUrl": "{{js .Request.RequestURI}}", "requestSize": "{{.Request.ContentLength}}", "status": {{.Response.Code}}, "responseSize": "{{.Response.Size}}", "userAgent": "{{js .Request.UserAgent}}", "remoteIp": "{{js .Request.RemoteAddr}}", "serverIp": "{{.Revision.PodIP}}", "referer": "{{js .Request.Referer}}", "latency": "{{.Response.Latency}}s", "protocol": "{{.Request.Proto}}"}, "traceId": "{{index .Request.Header "X-B3-Traceid"}}"}
      SERVING_ENABLE_REQUEST_LOG:        false
      SERVING_REQUEST_METRICS_BACKEND:   prometheus
      TRACING_CONFIG_BACKEND:            none
      TRACING_CONFIG_ZIPKIN_ENDPOINT:
      TRACING_CONFIG_DEBUG:              false
      TRACING_CONFIG_SAMPLE_RATE:        0.1
      USER_PORT:                         8080
      SYSTEM_NAMESPACE:                  knative-serving
      METRICS_DOMAIN:                    knative.dev/internal/serving
      SERVING_READINESS_PROBE:           {"tcpSocket":{"port":8080,"host":"<IP_ADDRESS>"},"successThreshold":1}
      ENABLE_PROFILING:                  false
      SERVING_ENABLE_PROBE_REQUEST_LOG:  false
      METRICS_COLLECTOR_ADDRESS:
      CONCURRENCY_STATE_ENDPOINT:
      CONCURRENCY_STATE_TOKEN_PATH:      /var/run/secrets/tokens/state-token
      HOST_IP:                            (v1:status.hostIP)
      ENABLE_HTTP2_AUTO_DETECTION:       false
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-k7rbd (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  kube-api-access-k7rbd:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
  kserve-provision-location:
    Type:        EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:   <unset>
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  10m                    default-scheduler  Successfully assigned default/torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp to kind-control-plane
  Normal   Pulled     10m                    kubelet            Container image "kserve/storage-initializer:v0.9.0-rc0" already present on machine
  Normal   Created    10m                    kubelet            Created container storage-initializer
  Normal   Started    10m                    kubelet            Started container storage-initializer
  Normal   Pulled     8m56s                  kubelet            Container image "index.docker.io/pytorch/torchserve-kfs@sha256:43c1c14b2768c0cd73ce40e23da0a56176532b3c0fcb8b2217c087da3054c372" already present on machine
  Normal   Created    8m56s                  kubelet            Created container kserve-container
  Normal   Started    8m56s                  kubelet            Started container kserve-container
  Normal   Pulled     8m56s                  kubelet            Container image "gcr.io/knative-releases/knative.dev/serving/cmd/queue@sha256:a40f6e84de1a0d145d27084a94cc7fa221159e75cafde7d332ac8f4f0aed58fb" already present on machine
  Normal   Created    8m56s                  kubelet            Created container queue-proxy
  Normal   Started    8m56s                  kubelet            Started container queue-proxy
  Warning  Unhealthy  8m44s (x4 over 8m54s)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:8012/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Port Forward for testing purpose
INGRESS_GATEWAY_SERVICE=$(kubectl get svc --namespace istio-system --selector="app=istio-ingressgateway" --output jsonpath='{.items[0].metadata.name}')
kubectl port-forward --namespace istio-system svc/${INGRESS_GATEWAY_SERVICE} 8080:80
start another terminal
export INGRESS_HOST=localhost
export INGRESS_PORT=8080
What did you expect to happen:
What's the InferenceService yaml:
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  name: "torchserve-bert-v2"
spec:
  predictor:
    pytorch:
      protocolVersion: v2
      storageUri: <GCP model path>
**GCP model path contains-
├── config
│   ├── config.properties
├── model-store
│   ├── BERTSeqClassification.mar**

Anything else you would like to add:
Request Input file-> bert_v2.json
{
  "id": "d3b15cad-50a2-4eaf-80ce-8b0a428bd298",
  "inputs": [{
    "name": "4b7c7d4a-51e4-43c8-af61-04639f6ef4bc",
    "shape": -1,
    "datatype": "BYTES",
    "data": "{\"text\":\"Bloomberg has decided to publish a new report on the global economy.\", \"target\":1}"
  }
  ]
}

Inference request URL
SERVICE_HOSTNAME=$(kubectl get inferenceservice torchserve-bert-v2 -o jsonpath='{.status.url}' | cut -d "/" -f 3)

curl -v \
  -H "Host: ${SERVICE_HOSTNAME}" \
  -H "Content-Type: application/json" \
  -d @./bert_v2.json \
  http://${INGRESS_HOST}:${INGRESS_PORT}/v2/models/BERTSeqClassification/infer

Response
*   Trying <IP_ADDRESS>:8080...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> POST /v2/models/BERTSeqClassification/infer HTTP/1.1
> Host: torchserve-bert-v2.default.example.com
> User-Agent: curl/7.84.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 271
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< content-length: 66
< content-type: application/json; charset=UTF-8
< date: Tue, 29 Nov 2022 19:34:59 GMT
< server: istio-envoy
< x-envoy-upstream-service-time: 9
<
* Connection #0 to host localhost left intact
{"error": "Model with name BERTSeqClassification does not exist."}%

kubectl logs torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp
Defaulted container "kserve-container" out of: kserve-container, queue-proxy, storage-initializer (init)
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2022-11-29T19:28:20,943 [INFO ] main org.pytorch.serve.servingsdk.impl.PluginsManager - Initializing plugins manager...
2022-11-29T19:28:22,146 [INFO ] main org.pytorch.serve.ModelServer -
Torchserve version: 0.6.0
TS Home: /usr/local/lib/python3.8/dist-packages
Current directory: /home/model-server
Temp directory: /home/model-server/tmp
Number of GPUs: 0
Number of CPUs: 7
Max heap size: 4494 M
Python executable: /usr/bin/python
Config file: /mnt/models/config/config.properties
Inference address: http://<IP_ADDRESS>:8085
Management address: http://<IP_ADDRESS>:8086
Metrics address: http://<IP_ADDRESS>:8082
Model Store: /mnt/models/model-store
Initial Models: N/A
Log dir: /home/model-server/logs
Metrics dir: /home/model-server/logs
Netty threads: 4
Netty client threads: 0
Default workers per model: 7
Blacklist Regex: N/A
Maximum Response Size: 6553500
Maximum Request Size: 6553500
Limit Maximum Image Pixels: true
Prefer direct buffer: false
Allowed Urls: [file://.*|http(s)?://.*]
Custom python dependency for model allowed: false
Metrics report format: prometheus
Enable metrics API: true
Workflow Store: /mnt/models/model-store
Model config: N/A
2022-11-29T19:28:22,256 [INFO ] main org.pytorch.serve.servingsdk.impl.PluginsManager -  Loading snapshot serializer plugin...
2022-11-29T19:28:22,656 [INFO ] main org.pytorch.serve.snapshot.SnapshotManager - Started restoring models from snapshot {"name":"startup.cfg","modelCount":1,"models":{"bert":{"1.0":{"defaultVersion":true,"marName":"BERTSeqClassification.mar","minWorkers":1,"maxWorkers":5,"batchSize":2,"maxBatchDelay":500,"responseTimeout":60}}}}
2022-11-29T19:28:22,850 [INFO ] main org.pytorch.serve.snapshot.SnapshotManager - Validating snapshot startup.cfg
2022-11-29T19:28:22,925 [INFO ] main org.pytorch.serve.snapshot.SnapshotManager - Snapshot startup.cfg validated successfully
[I 221129 19:28:24 __main__:75] Wrapper : Model names ['bert'], inference address http//<IP_ADDRESS>:8085, management address http://<IP_ADDRESS>:8086, model store /mnt/models/model-store
[I 221129 19:28:24 TorchserveModel:54] kfmodel Predict URL set to <IP_ADDRESS>:8085
[I 221129 19:28:24 TorchserveModel:56] kfmodel Explain URL set to <IP_ADDRESS>:8085
[I 221129 19:28:24 TSModelRepository:30] TSModelRepo is initialized
[I 221129 19:28:24 model_server:150] Registering model: bert
[I 221129 19:28:24 model_server:123] Listening on port 8080
[I 221129 19:28:24 model_server:125] Will fork 1 workers
[I 221129 19:28:24 model_server:128] Setting max asyncio worker threads as 11
2022-11-29T19:28:46,328 [DEBUG] main org.pytorch.serve.wlm.ModelVersionedRefs - Adding new version 1.0 for model bert
2022-11-29T19:28:46,330 [DEBUG] main org.pytorch.serve.wlm.ModelVersionedRefs - Setting default version to 1.0 for model bert
2022-11-29T19:28:46,331 [DEBUG] main org.pytorch.serve.wlm.ModelVersionedRefs - Setting default version to 1.0 for model bert
2022-11-29T19:28:46,332 [INFO ] main org.pytorch.serve.wlm.ModelManager - Model bert loaded.
2022-11-29T19:28:46,333 [DEBUG] main org.pytorch.serve.wlm.ModelManager - updateModel: bert, count: 1
2022-11-29T19:28:46,530 [DEBUG] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerLifeCycle - Worker cmdline: [/usr/bin/python, /usr/local/lib/python3.8/dist-packages/ts/model_service_worker.py, --sock-type, unix, --sock-name, /home/model-server/tmp/.ts.sock.9000]
2022-11-29T19:28:46,627 [INFO ] main org.pytorch.serve.ModelServer - Initialize Inference server with: EpollServerSocketChannel.
2022-11-29T19:28:48,722 [INFO ] main org.pytorch.serve.ModelServer - Inference API bind to: http://<IP_ADDRESS>:8085
2022-11-29T19:28:48,725 [INFO ] main org.pytorch.serve.ModelServer - Initialize Management server with: EpollServerSocketChannel.
2022-11-29T19:28:48,733 [INFO ] main org.pytorch.serve.ModelServer - Management API bind to: http://<IP_ADDRESS>:8086
2022-11-29T19:28:48,735 [INFO ] main org.pytorch.serve.ModelServer - Initialize Metrics server with: EpollServerSocketChannel.
2022-11-29T19:28:48,739 [INFO ] main org.pytorch.serve.ModelServer - Metrics API bind to: http://<IP_ADDRESS>:8082
Model server started.
2022-11-29T19:28:52,241 [WARN ] pool-3-thread-1 org.pytorch.serve.metrics.MetricCollector - worker pid is not available yet.
2022-11-29T19:28:53,466 [INFO ] pool-3-thread-1 TS_METRICS - CPUUtilization.Percent:40.0|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:53,523 [INFO ] pool-3-thread-1 TS_METRICS - DiskAvailable.Gigabytes:229.0811767578125|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:53,525 [INFO ] pool-3-thread-1 TS_METRICS - DiskUsage.Gigabytes:38.98243713378906|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:53,527 [INFO ] pool-3-thread-1 TS_METRICS - DiskUtilization.Percent:14.5|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:53,529 [INFO ] pool-3-thread-1 TS_METRICS - MemoryAvailable.Megabytes:13237.20703125|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:53,530 [INFO ] pool-3-thread-1 TS_METRICS - MemoryUsed.Megabytes:4136.36328125|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:53,532 [INFO ] pool-3-thread-1 TS_METRICS - MemoryUtilization.Percent:26.4|#Level:Host|#hostname:torchserve-bert-v2-predictor-default-00001-deployment-5676v48gp,timestamp:1669750133
2022-11-29T19:28:55,315 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Listening on port: /home/model-server/tmp/.ts.sock.9000
2022-11-29T19:28:55,318 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - [PID]59
2022-11-29T19:28:55,322 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Torch worker started.
2022-11-29T19:28:55,323 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Python runtime: 3.8.0
2022-11-29T19:28:55,329 [DEBUG] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - W-9000-bert_1.0 State change null -> WORKER_STARTED
2022-11-29T19:28:55,515 [INFO ] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - Connecting to: /home/model-server/tmp/.ts.sock.9000
2022-11-29T19:28:55,948 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Connection accepted: /home/model-server/tmp/.ts.sock.9000.
2022-11-29T19:28:56,424 [INFO ] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - Flushing req. to backend at:<PHONE_NUMBER>359
2022-11-29T19:28:57,594 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - model_name: bert, batchSize: 2
2022-11-29T19:29:01,332 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - generated new fontManager
2022-11-29T19:29:04,773 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Transformers version 4.11.0
2022-11-29T19:29:04,801 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Backend worker process died.
2022-11-29T19:29:04,802 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - Traceback (most recent call last):
2022-11-29T19:29:04,827 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/usr/local/lib/python3.8/dist-packages/ts/model_service_worker.py", line 210, in <module>
2022-11-29T19:29:04,829 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     worker.run_server()
2022-11-29T19:29:04,832 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/usr/local/lib/python3.8/dist-packages/ts/model_service_worker.py", line 181, in run_server
2022-11-29T19:29:04,834 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     self.handle_connection(cl_socket)
2022-11-29T19:29:04,837 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/usr/local/lib/python3.8/dist-packages/ts/model_service_worker.py", line 139, in handle_connection
2022-11-29T19:29:04,838 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     service, result, code = self.load_model(msg)
2022-11-29T19:29:04,839 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/usr/local/lib/python3.8/dist-packages/ts/model_service_worker.py", line 104, in load_model
2022-11-29T19:29:04,840 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     service = model_loader.load(
2022-11-29T19:29:04,842 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/usr/local/lib/python3.8/dist-packages/ts/model_loader.py", line 151, in load
2022-11-29T19:29:04,843 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     initialize_fn(service.context)
2022-11-29T19:29:04,833 [INFO ] epollEventLoopGroup-5-1 org.pytorch.serve.wlm.WorkerThread - 9000 Worker disconnected. WORKER_STARTED
2022-11-29T19:29:04,846 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/home/model-server/tmp/models/053bb446d6094183a82b99d6f359f99d/Transformer_handler_generalized.py", line 71, in initialize
2022-11-29T19:29:04,847 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     self.model = torch.jit.load(model_pt_path, map_location=self.device)
2022-11-29T19:29:04,922 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -   File "/usr/local/lib/python3.8/dist-packages/torch/jit/_serialization.py", line 162, in load
2022-11-29T19:29:04,924 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG -     cpp_module = torch._C.import_ir_module(cu, str(f), map_location, _extra_files)
2022-11-29T19:29:04,925 [INFO ] W-9000-bert_1.0-stdout MODEL_LOG - RuntimeError: version_ <= kMaxSupportedFileFormatVersionINTERNAL ASSERT FAILED at "../caffe2/serialize/inline_container.cc":147, please report a bug to PyTorch. Attempted to read a PyTorch file with version 10, but the maximum supported version for reading is 9. Your PyTorch installation may be too old.
2022-11-29T19:29:04,945 [DEBUG] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - System state is : WORKER_STARTED
2022-11-29T19:29:04,946 [DEBUG] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - Backend worker monitoring thread interrupted or backend worker process died.
java.lang.InterruptedException: null
   at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2056) ~[?:?]
   at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2133) ~[?:?]
   at java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:432) ~[?:?]
   at org.pytorch.serve.wlm.WorkerThread.run(WorkerThread.java:189) [model-server.jar:?]
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
   at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
   at java.lang.Thread.run(Thread.java:829) [?:?]
2022-11-29T19:29:05,849 [WARN ] W-9000-bert_1.0 org.pytorch.serve.wlm.BatchAggregator - Load model failed: bert, error: Worker died.
2022-11-29T19:29:05,850 [DEBUG] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - W-9000-bert_1.0 State change WORKER_STARTED -> WORKER_STOPPED
2022-11-29T19:29:05,927 [WARN ] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerLifeCycle - terminateIOStreams() threadName=W-9000-bert_1.0-stderr
2022-11-29T19:29:05,929 [WARN ] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerLifeCycle - terminateIOStreams() threadName=W-9000-bert_1.0-stdout
2022-11-29T19:29:05,934 [INFO ] W-9000-bert_1.0 org.pytorch.serve.wlm.WorkerThread - Retry worker: 9000 in 1 seconds.

Environment:

Istio Version:
Knative Version:
KServe Version:
Kubeflow version:
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Minikube/Kind version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

pytorch version mismatch was there. Created pytorch trace model with torch 1.13 and inside kserve torch version was 1.11 so it was creating issue while loading the trace model inside kserve environments.


Add Tablet device type

Add Tablet device type

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

Project coverage is 100.00%. Comparing base (10f7a5c) to head (c955c6e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #384   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          658       659    +1
  Branches        28        28
=========================================
+ Hits           658       659    +1

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


Add cjs config support

Changes
This PR adds support for using snowpack.config.cjs in addition to all of the existing config formats. This was a blocker for me when trying to use snowpack in a project that had "type": "module" specified.
Turns out all that was required was upgrading cosmiconfig to v7 and 1 line of code change.
One important consideration is that cosmiconfig v7 drops support for node 8, now requiring node 10+: https://github.com/davidtheclark/cosmiconfig/blob/master/CHANGELOG.md#700. Looks like snowpack already requires node version >=10.19.0 in engines, so I imagine this might not need to be considered a breaking change, but calling it out just in case we might want to save this for a major version for whatever reason.
I've also updated the appropriate section in the docs to include the new format. Let me know if there's any other changes you'd like to see.
Testing
I tested this manually by building locally and copy pasting the build to the project with snowpack.config.cjs config, and then manually bumping the version of cosmiconfig in that project. Seems to be working great.
Since this functionality is almost entirely handled by cosmiconfig, I didn't feel a new test here would add much value, but happy to add one if folks disagree.

This looks great! I have a question related to how we can document this: Would the config have worked as .js & ESM, if you had defined your config file as ESM?
// snowpack.config.js
// does this work?
export default {
  ...
}

This looks great! I have a question related to how we can document this: Would the config have worked as .js & ESM, if you had defined your config file as ESM?
// snowpack.config.js
// does this work?
export default {
  ...
}

Here's the error I got when I tried this:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: ...\snowpack.config.js
require() of ES modules is not supported.

I believe we'd need some special case handling for "type": "module" projects in cosmiconfig to use import instead of require for this to work, which might not be a trivial change (I haven't looked into their source code yet). In the mean time, this feels like a simple short term solution to unblock usage in "type": "module" projects.


categories page

Update (12 Feb)
Almost done, just a few small styling issues (see comment below)
Acceptance Criteria

[ ] styling should match figma
[x] navigating to /tags should navigate to default tag. This is important for backwards compatibility because https://aisafety.info/tags works on current site.
[x] URLs should be tag/{tag id}/{tag name}

Navigating to tag/{tag id}/anything should navigate to correct tag using id, but will try to append name where possible

@melissasamworth @mruwnik for the article page, issue #382 asks that the links be "aisafety.com/id/current-title-of-article". Would it make sense to also have the category URLs have the name and the id? In the current implementation, the category URLs are /tags/{tag name}. Would it instead make sense to do /tags/{tag id}/{tag name}, similar to the articles?

This tasks probably isn't quite done from a styling standpoint as the sidebar doesn't quite match figma:

It isn't aligned under the "AISafety.info" logo
The green highlight on the selected category isn't correct

Hey @jrhender quick process note: do you think it's best to talk about individual tickets here on Github? I think it probably does, and if so I'll make sure to check this daily (sorry for the lag this time).
The purpose of the IDs with articles is to make it backwards compatible, particularly for links people have shared that are floating out there. I'm not sure how many tag links people have shared. Still, backwards compatibility would be nice. Does your solution solve that problem?

The search input current says "Search articles" but it should say "Filter by keyword"

PR here: https://github.com/StampyAI/stampy-ui/pull/391

Lastly, not sure if it should belong to this issue but the widths of the layout is off. Ideally they should be the following viewport widths

@melissasamworth @buddy-web3
Do you think the change to fix this would be in newRoot.css? https://github.com/StampyAI/stampy-ui/blob/04b76d21a98c0470814a78260a896f8f1e359f59/app/newRoot.css#L408

Storybook version pushed
Still needs to be integrated with article page (Nemo)

Hey @melissasamworth , could you elaborate on this point please:

Storybook version pushed

The storybook version of one of the components was published? By "published" do you mean push to the stampy-redesign branch?

Lastly, not sure if it should belong to this issue but the widths of the layout is off. Ideally they should be the following viewport widths

@melissasamworth @buddy-web3
Do you think the change to fix this would be in newRoot.css?
stampy-ui/app/newRoot.css
Line 408 in 04b76d2
.group-elements {

Not sure but i can take a look soon

Hey @melissasamworth , could you elaborate on this point please:

Storybook version pushed

The storybook version of one of the components was published? By "published" do you mean push to the stampy-redesign branch?

@joy-void-joy Hey I'm sorry, I think I meant to comment this on another issue.
Only thing remaining is "If no article title takes up 2 lines, can you still make them 100% width?" thanks :)

@jrhender I was referring to the widths, but don't worry, Nemo took care of it

Awesome, thanks for taking this across the finish line @mruwnik and @melissasamworth !


_1password-gui: 8.10.6 -> 8.10.7

Description of changes
I didn't update the beta as stable is currently newer.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 235900 run on x86_64-linux 1

1 package built:

_1password-gui


UE 5.1 Support

Hi,
When are you going to update this for ue5.1

Hi! UE5.1 support should be coming in just a couple of days (this weekend). I haven't had the chance to work on the project properly since late November, but this will finally change on Friday with the completion of my exams :) Getting FPS Core to work with UE5.1 will be my top priority!

Should work with 5.1 now!


Graphic of the devos control flow

Note to self: make a graphic for the readme / docs to explain the devos control flow:

modules -> profiles -> suites

suites -> hosts

This seems like a good use case for GitHub's recently-added support for Mermaid syntax in Markdown. I've been meaning to experiment with Mermaid but haven't yet found the time.
https://github.com/mermaid-js/mermaid
https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/


Undefined Variable Referenced without Explanation

Step 5 needs further elaboration:
https://github.com/giantswarm/gitops-template/blob/main/docs/add_wc_instance_capi.md#creating-cluster-based-on-existing-bases
You mention the base path, but then use an undefined variable in the heredoc and don't explain it.

:+1: we have a doc revamp on our way, we'll double check after it's merged if this problem is still there


Significant code repetition between project!(::Stabilizer), project!(::***Stabilizer) and projectX/Y/Z!

cleaned up in 7a3c74a1ea840b2161dec35419396e956dd2f542


fix(setup): authorization_challenge scope has wrong DN

Describe the issue
fix(setup): authorization_challenge scope has wrong DN inum=6D92,ou=scopes,o=jans
o=jans -> o=gluu

Fixed in https://github.com/GluuFederation/gluu4/pull/54


Hide ERR_STATE and remove ERR_get_state for OpenSSL 1.2.0.

It's too late for OpenSSL 1.1.x, but you all probably should hide ERR_STATE in 1.2.0. I don't think anything good can come of folks reaching into those internals. :-)
(I'll send Node a patch to use saner APIs there.)

ERR_get_state was deprecated in #9462

Since its been deprecated, I suppose this should be removed in 4.0


python311Packages.pyhanko: 0.20.0 -> 0.21.0

Diff: https://github.com/MatthiasValvekens/pyHanko/compare/refs/tags/v0.20.0...v0.21.0
Changelog: https://github.com/MatthiasValvekens/pyHanko/blob/v0.21.0/docs/changelog.rst
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 271784 run on x86_64-linux 1

20 packages built:

maigret
maigret.dist
python310Packages.certomancer
python310Packages.certomancer.dist
python310Packages.pyhanko
python310Packages.pyhanko-certvalidator
python310Packages.pyhanko-certvalidator.dist
python310Packages.pyhanko.dist
python310Packages.xhtml2pdf
python310Packages.xhtml2pdf.dist
python311Packages.certomancer
python311Packages.certomancer.dist
python311Packages.pyhanko
python311Packages.pyhanko-certvalidator
python311Packages.pyhanko-certvalidator.dist
python311Packages.pyhanko.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
sasview
sasview.dist


BUG on tf.saved_model.load with large variable

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): mac
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: none
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.0.alpha0
Python version:
Bazel version (if compiling from source): none
GCC/Compiler version (if compiling from source): none
CUDA/cuDNN version: none
GPU model and memory: none

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
It works fine when run this in one console
import tensorflow as tf
import numpy as np

m = tf.Module()
m.v = tf.Variable(np.random.normal(size=(200, 200)).astype(np.float64))
m.f = tf.function(lambda x: x + m.v[0, 0])

tf.saved_model.save(m, "save/model", signatures={
    "predict": m.f.get_concrete_function(tf.constant(3., dtype=tf.float64))
})

and then the other
import tensorflow as tf
m = tf.saved_model.load("save/model")

If you change 200 to 20000, you will see errors on load
import tensorflow as tf
import numpy as np

m = tf.Module()
m.v = tf.Variable(np.random.normal(size=(20000, 20000)).astype(np.float64))
m.f = tf.function(lambda x: x + m.v[0, 0])

tf.saved_model.save(m, "save/model", signatures={
    "predict": m.f.get_concrete_function(tf.constant(3., dtype=tf.float64))
})

import tensorflow as tf
tf.saved_model.load("save/model")
# tensorflow.python.framework.errors_impl.InvalidArgumentError: save/model/variables/variables.data-00000-of-00001; Invalid argument [Op:RestoreV2]

Describe the expected behavior
Should be able to load regardless of the size of variable
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
see above
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@allenlavoie what's wrong with tf.saved_model.load

FWIW I can't reproduce on Linux (on a machine with plenty of memory). It's probably mac-specific; I think someone reported a similar issue for checkpointing that only affected macs. I haven't had a chance to find a mac and debug it yet.

@allenlavoie I tested on ubuntu18.04 and there is no bugs involved.

If it affects macs it is a bug. We do support macs. But possibly a duplicate of https://github.com/tensorflow/tensorflow/issues/18769


fix: Invalid links, reference / spec

Comlink map examples were pointing to the /capabilities/ directory; replaced with commit permalink
I noticed a few links pointing to Comlink spec as "reference"

Thanks to @tmladek for heads up!

replaced with commit permalink

Thanks pray Do you think this might be worth changing globally in all docs pages, e.g. provider guide?

It would be definitely future proof, but at this point I wouldn't invest in small fixes like these if docs are due for complete overhaul...


[sil-arc-code-motion] Properly propagate the atomicity of reference-сounting instructions

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

ARCCodeMotion was not respecting the atomicity of the reference-counting instructions being moved.

@swift-ci Please smoke test

@trentxintong @eeckstein Could you have a look?

@eeckstein I pushed a new version which addresses your comments except for the one about the map, where I think you are wrong.

Closing this out due to age and the fact that the optimization infrastructure we have today cannot accommodate a rebased copy of this patch.  Thanks for your hard work @swiftix!


Ukrainian translation WIP

As title says.
Translation is full but unrevised (by ru-RU only), because I don't have Windows SDK and, therefore resgen.exe to compile resource files.
If someone could advice me how to compile those without Windows SDK, I'll be grateful.
Cheers, хлопці!

Maybe using the Mono resgen works: https://linux.die.net/man/1/resgen.

Maybe using the Mono resgen works: https://linux.die.net/man/1/resgen.

Thanks, @riQQ, I wasn't aware of that.
But either I'm doing something wrong, its not working way I thought it would be.
Using mono resgen you advised:
> resgen /compile D:\projects\HDT-Localization\Strings.uk.resx,HearthstoneDeckTracker.resources.dll
Error: Unknown format in file C:\Users\olloff\HearthstoneDeckTracker.resources.dll

> resgen /compile D:\projects\HDT-Localization\Strings.uk.resx
Read in 878 resources from 'D:\projects\HDT-Localization\Strings.uk.resx'
Writing resource file...  Done.
>mv D:\projects\HDT-Localization\Strings.uk.resources D:\projects\HDT-Localization\HearthstoneDeckTracker.resources.dll

Next I'm trying to replace existing resource file by modified one (in my case - pt-PT). HDT does start without errors, but nothing happens when I'm trying to use Portugal in language selector.
That really annoys me, do I need to build whole app to make change to resource files?

Yes, currently to see your changes you need to build HDT and disable it automatically pulling them from this repo (by deleting these lines).

Thanks for make it clear.
Sadly, its not an option for me for now, could I ask any of you to make a build for me so I can review changes before they go live?

Here you go :) https://github.com/azeier/HDT-Test/releases/tag/v<IP_ADDRESS>-uk

uk translation should be considered as complete now, still there are issues, tho.
Please, accept this alongside with https://github.com/HearthSim/Hearthstone-Deck-Tracker/pull/3109


Fixing page sequence

This fixes the pages sequences (see #185)

Thank you for your interest and contribution! :)


IndexError: list index out of range while deploying new rack

In order to subnet the datacenter v4 networks for each rack environment, NetworkAPI gets environment configuration from ip_config and EnvironmentConfig (populated by datacenter feature for the room).
While deploying new rack, it is trying to statically allocate /18 network for the rack (networkapi.api_rack.facede.py:664 - "prefixo_inicial"). As such, when the environment is configured to smaller networks, it is raising an error index out of range error.
There is a need to let it dynamically allocate the rack network according to the environment config.

In order to subnet the datacenter v4 networks for each rack environment, NetworkAPI gets environment configuration from ip_config and EnvironmentConfig (populated by datacenter feature for the room).
While deploying new rack, it is trying to statically allocate /18 network for the rack (networkapi.api_rack.facede.py:664 - "prefixo_inicial"). As such, when the environment is configured to smaller networks, it is raising an error index out of range error.
There is a need to let it dynamically allocate the rack network according to the environment config.

can i work on it?


wsk api should create an API and successfully invoke that API FAILED

Per the dev list, the commit from #335 is suspected of breaking the build. Here's a log from the apigw container when running the test:
==> /var/log/api-gateway/access.log <==
<IP_ADDRESS> - remote_user="-" [28/May/2019:18:18:26 +0000] request_method="GET" request_uri="/v2/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/apis?limit=undefined&skip=undefined&basePath=%2FAPIGW_HEALTHTEST1_bp" request_protocol="HTTP/1.1" status=500 bbs=199 rl=407 rt=0.002 hr="-" ua="OpenWhisk-apimgmt/1.0.0 akka-http/10.1.8 akka-http/10.1.8 akka-http/10.1.8" xfwdf="-"
<IP_ADDRESS> - remote_user="-" [28/May/2019:18:18:27 +0000] request_method="GET" request_uri="/v2/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/apis?limit=undefined&skip=undefined&basePath=%2FAPIGW_HEALTHTEST1_bp" request_protocol="HTTP/1.1" status=500 bbs=199 rl=390 rt=0.001 hr="-" ua="OpenWhisk-apimgmt/1.0.0 akka-http/10.1.8 akka-http/10.1.8" xfwdf="-"
<IP_ADDRESS> - remote_user="-" [28/May/2019:18:18:27 +0000] request_method="GET" request_uri="/v2/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/apis?limit=undefined&skip=undefined&basePath=%2FAPIGW_HEALTHTEST1_bp" request_protocol="HTTP/1.1" status=500 bbs=199 rl=424 rt=0.002 hr="-" ua="OpenWhisk-apimgmt/1.0.0 akka-http/10.1.8 akka-http/10.1.8 akka-http/10.1.8 akka-http/10.1.8" xfwdf="-"

==> /var/log/api-gateway/management.log <==
2019/05/28 18:18:26 [error] 36#0: *18 lua entry thread aborted: runtime error: /etc/api-gateway/scripts/lua/management/lib/tenants.lua:130: attempt to compare nil with number
stack traceback:
coroutine 0:
	/etc/api-gateway/scripts/lua/management/lib/tenants.lua: in function 'getTenantAPIs'
	/etc/api-gateway/scripts/lua/management/routes/apis.lua:62: in function 'getAPIs'
	/etc/api-gateway/scripts/lua/management/routes/apis.lua:41: in function 'requestHandler'
	access_by_lua(management_apis.conf:36):5: in function <access_by_lua(management_apis.conf:36):1>, client: <IP_ADDRESS>, server: management_gw, request: "GET /v2/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/apis?limit=undefined&skip=undefined&basePath=%2FAPIGW_HEALTHTEST1_bp HTTP/1.1", host: "<IP_ADDRESS>:9000"
2019/05/28 18:18:27 [error] 36#0: *20 lua entry thread aborted: runtime error: /etc/api-gateway/scripts/lua/management/lib/tenants.lua:130: attempt to compare nil with number
stack traceback:
coroutine 0:
	/etc/api-gateway/scripts/lua/management/lib/tenants.lua: in function 'getTenantAPIs'
	/etc/api-gateway/scripts/lua/management/routes/apis.lua:62: in function 'getAPIs'
	/etc/api-gateway/scripts/lua/management/routes/apis.lua:41: in function 'requestHandler'
	access_by_lua(management_apis.conf:36):5: in function <access_by_lua(management_apis.conf:36):1>, client: <IP_ADDRESS>, server: management_gw, request: "GET /v2/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/apis?limit=undefined&skip=undefined&basePath=%2FAPIGW_HEALTHTEST1_bp HTTP/1.1", host: "<IP_ADDRESS>:9000"
2019/05/28 18:18:27 [error] 36#0: *22 lua entry thread aborted: runtime error: /etc/api-gateway/scripts/lua/management/lib/tenants.lua:130: attempt to compare nil with number
stack traceback:
coroutine 0:
	/etc/api-gateway/scripts/lua/management/lib/tenants.lua: in function 'getTenantAPIs'
	/etc/api-gateway/scripts/lua/management/routes/apis.lua:62: in function 'getAPIs'
	/etc/api-gateway/scripts/lua/management/routes/apis.lua:41: in function 'requestHandler'
	access_by_lua(management_apis.conf:36):5: in function <access_by_lua(management_apis.conf:36):1>, client: <IP_ADDRESS>, server: management_gw, request: "GET /v2/23bc46b1-71f6-4ed5-8c54-816aa4f8c502/apis?limit=undefined&skip=undefined&basePath=%2FAPIGW_HEALTHTEST1_bp HTTP/1.1", host: "<IP_ADDRESS>:9000"
2019/05/28 18:18:31 Executing sync cmd: echo ''
2019/05/28 18:18:31 done
2019/05/28 18:18:41 Executing sync cmd: echo ''
sync stdout | ''
2019/05/28 18:18:41 done

with the error tenants.lua:130: attempt to compare nil with number emitted multiple times. I'm not sure if that's the root cause.
The implicated lines:
https://github.com/apache/incubator-openwhisk-apigateway/blob/1f46de9d2f7a9420e48c533af7a4b1b6118aa130/scripts/lua/management/lib/tenants.lua#L129-L130

the value of limit (and skip) are the string "undefined" and that's why the predicate fails at runtime --- the guards check against nil earlier.

Fix merged.


[Bug] Notepads is broken after trying to paste huge text

The bug

Notepads doesn't work anymore.

What happened

I copied a huge text and pasted inside Notepads;
The app froze. I waited for several minutes, nothing happened;
I decided to close the app on Task Manager;
I tried to open Notepads again;
The app window opens, but it's empty. Tabs from last session have disappeared;
App is unresponsive, althought you can see it on Task Manager consuming more than 30% of CPU resources.

To reproduce

Try copying a huge text and pasting on Notepads.

Expected behavior

I expected Notepads worked again after being reopened.
Is there a way to recover last session tabs? Some of those tabs had not been saved, since I activated session snapshot and therefore the user should not worry about saving tabs.
Where are the app "temp" files located? Is it possible to tweak them in order to have the app working again?

Desktop

OS: Windows 10 Pro 21H2 19044.1415
Notepads v<IP_ADDRESS>

The app is actually loading the text from your last session but since there are too much text to render, it feels slow and unresponsive. This is a problem with the WinRT's RichEdit control used in this app and I cannot fix it.

@JasonStein, thanks for your reply.
Is there a way to delete (or edit manually) last session file(s), so I can reset Notepads?

@JasonStein, thanks for your reply. Is there a way to delete (or edit manually) last session file(s), so I can reset Notepads?

If you don't care about your last session at all, you could just go to Settings->Apps->Apps & features ->Notepads->Reset
So simply right click on Notepads icon and click "App Settings".


Replace get_object_owned_by_object with get_dynamic_fields

Summary
This PR adds dynamic field support to Sui's JSON-RPC APIs.
Notable changes

added dynamic_field_index to AuthorityPerpetualTables storing all object owned dynamic field object info
owner_index now only stores address owned object
new get_dynamic_field_object method for retrieving object using parent object id and dynamic field name.
SuiDataStore now implement GetModule trait, this is needed to parse the dynamic field MoveObject within the datastore.

Examples
the first object is nfts::marketplace::Marketplace, second object is nfts::geniteam::Player
Requests
curl --location --request POST '<IP_ADDRESS>:9000' \
--header 'Content-Type: application/json' \
--data-raw '[
    {
        "jsonrpc": "2.0",
        "id": 1,
        "method": "sui_getDynamicFields",
        "params": [
            "0xc404264ae29f8f5d5a9e0da0213cddb64228575f"
        ]
    },
    {
        "jsonrpc": "2.0",
        "id": 2,
        "method": "sui_getDynamicFields",
        "params": [
            "0x1f6a5b789f31c0511ff3f0cbe7e2d9fda0ea10da"
        ]
    }
]'

Response
[
    {
        "jsonrpc": "2.0",
        "result": {
            "data": [
                {
                    "name": "0x2::object::ID {bytes: 0xbbbb096cc9145afb1df64546d3b64b1160ba284f}",
                    "type": {
                        "DynamicField": {
                            "wrappedObjectId": "0xbbbb096cc9145afb1df64546d3b64b1160ba284f"
                        }
                    },
                    "objectType": "0x2d5da76aaa9ea52407ba16a1c22c443f53d19963::marketplace::Listing<0x2::coin::Coin<0x2::sui::SUI>, 0x2::sui::SUI>",
                    "objectId": "0x16632ab5a8f7455d01c32507ba2ce0fc86dd3625",
                    "version": 1,
                    "digest": "1m9qSQd9zwSpEU50qV4UqOVyUfHcUUgsztfAwfKPLfQ="
                }
            ],
            "nextCursor": null
        },
        "id": 1
    },
    {
        "jsonrpc": "2.0",
        "result": {
            "data": [
                {
                    "name": "0x2::typed_id::TypedID<0x2d5da76aaa9ea52407ba16a1c22c443f53d19963::geniteam::Farm> {id: 0x2::object::ID {bytes: 0xa2811c9063490d8bb2535917f4585fe8294863e0}}",
                    "type": "DynamicObject",
                    "objectType": "0x2d5da76aaa9ea52407ba16a1c22c443f53d19963::geniteam::Farm",
                    "objectId": "0xa2811c9063490d8bb2535917f4585fe8294863e0",
                    "version": 1,
                    "digest": "B63S7la6PzJFDfzf024k/bYof6YoDMN2gCHMY8ZqRWY="
                }
            ],
            "nextCursor": null
        },
        "id": 2
    }
]

Remaining Tasks:

[x] Testing
[ ] Docs
[ ] Migration guide

TODOs:

https://github.com/MystenLabs/sui/issues/6372
https://github.com/MystenLabs/sui/issues/6370
https://github.com/MystenLabs/sui/issues/6371
https://github.com/MystenLabs/sui/issues/6373

@ronny-mysten thanks for all the doc fixes!

I'm thinking we should move owner indexer and the new dynamic field tables into indexes.rs.
It does not seem the owner info has to be in the critical path, or even live in validator's storage. After some quick look, the only place that validators may look at the owner table is make_account_info which will be called by handle_account_info_request. Today the only callsite is get_all_owned_objects and sync_all_owned_objects, which iiuc, is now deprecated with gateway gone. @lxfind wdyt?
The long term plan is to move all indices to indexer. cc @mystenmark

I think we will still need owner_index for make_account_info, however dynamic_field_index should definitely move to the index storage.
I will make that changes.

Correct. owner_index should not belong to validator store.

Sorry for the late reply!

One question I have is do we still support object owning objects in Move? i.e. transferring ownership to an object without using dynamic field. This PR assumes an object can only own another object using DF, is this the right assumption?

Correct. Within Move, you can only make an object own another object through dynamic fields (in particular dynamic object fields)

I'm thinking we should move owner indexer and the new dynamic field tables into indexes.rs.
It does not seem the owner info has to be in the critical path, or even live in validator's storage. After some quick look, the only place that validators may look at the owner table is make_account_info which will be called by handle_account_info_request. Today the only callsite is get_all_owned_objects and sync_all_owned_objects, which iiuc, is now deprecated with gateway gone. @lxfind wdyt?
The long term plan is to move all indices to indexer. cc @mystenmark

I think we will still need owner_index for make_account_info, however dynamic_field_index should definitely move to the index storage.
I will make that changes.

Iiuc, make_account_info is obsolete after gateway deprecation

I have moved owner indexing to the IndexStore, will remove the old owner_index table in a subsequence PR to keep this PR small.
This PR is ready for re-review.

Is it ok to call the methods get_dynamic_fields? If dynamic_field is a Move implementation details maybe we can name it get_child_objects instead in public API.
Thoughts?  @tnowacki @sblackshear

Is it ok to call the methods get_dynamic_fields? If dynamic_field is a Move implementation details maybe we can name it get_child_objects instead in public API.

My 2c -- "child objects" are the implementation detail, and "dynamic fields" are the public-facing terminology, so it's probably better to prefer referring to dynamic fields instead of children/parents/child objects in the API.

Is it ok to call the methods get_dynamic_fields? If dynamic_field is a Move implementation details maybe we can name it get_child_objects instead in public API.

My 2c -- "child objects" are the implementation detail, and "dynamic fields" are the public-facing terminology, so it's probably better to prefer referring to dynamic fields instead of children/parents/child objects in the API.

Ah, it's the other way round... thanks for the clarification.

Anyone still reviewing this PR? I would like to merge soon.


script error when meleeing any kind of entity

might be a TFA issue
[ERROR] gamemodes/nzombies-unlimited/gamemode/health.lua:28: Tried to use a NULL entity!
  1. GetPos - [C]:-1
   2. unknown - gamemodes/nzombies-unlimited/gamemode/health.lua:28
    3. DispatchTraceAttack - [C]:-1
     4. ApplyDamage - lua/weapons/tfa_melee_base/shared.lua:255
      5. Strike - lua/weapons/tfa_melee_base/shared.lua:627
       6. StrikeThink - lua/weapons/tfa_melee_base/shared.lua:515
        7. Think2 - lua/weapons/tfa_melee_base/shared.lua:429
         8. Think2 - lua/weapons/tfa_ins2_melee_base.lua:82
          9. PlayerThink - lua/weapons/tfa_gun_base/shared.lua:723
           10. fn - lua/tfa/modules/tfa_hooks.lua:47
            11. unknown - lua/ulib/shared/hook.lua:109

Using the KA-BAR from https://steamcommunity.com/sharedfiles/filedetails/?id=1376312181
Have all dependencies installed.

I'd like to add on to this even though this isn't directly connected.
Could we possibly get some kind of automatic support for the TFA and CW melee bases? So that any weapon using them would automatically get moved to the V slot. That way we can make proper melee upgrades once weapon stat editing is a thing, and we can also use actual knives.


Large program opens a defined strings window will be stuck

Large program opens a defined strings window will be stuck
I tried to analyze a 14MB ELF program. After a long wait and analysis, I tried to open the defined strings window. When the progress bar went to about 10%, the program will get stuck.
To Reproduce
Steps to reproduce the behavior:

Import the "wlAR-5382u_CTL.o_save" file in the attachment and analyze it.
Waiting for analysis to complete.
Open the defined strings window.
Waiting for get stuck.

Expected behavior
Open the defined strings window normally.
Attachments
wlAR-5382u_CTL.zip
Environment (please complete the following information):

OS: [Windows 10 18.03]
Java Version: [11.0.5]
Ghidra Version: [9.1]

Is the entire GUI locked-up?   If so, then please run tthe jstack command from a terminal and provide the output to us.

Is the entire GUI locked-up? If so, then please run tthe jstack command from a terminal and provide the output to us.

jstack.log

From the given trace, the tool is not in a deadlock state.  It sounds like the GUI is effectively frozen while the Defined Strings window is loading.
If you let it run long enough, will it ever finish loading?
As an alternative, you can use the Search->For Strings... feature to find strings based upon  restrictive search criteria.  Not only can you restrict the scope of the results, the table that appears will load incrementally, showing results as they are discovered.  Given the potential number of strings in a binary, the Defined Strings widget should probably also load incrementally.

After running for a long time, the loading was completed once.
However, during the loading process, the entire window is in a deadlock state. Unable to close the window.


Add book option to our ammonite integration

Fixed in #42. The book format is the default and it's not possible to get the REPL session  formatting. REPL session formatting doesn't make sense for script semantics, for example companion objects don't work as expected in the REPL


Question: Progressive JPEG vs WebP vs URLs of varying quality

Hi
First of all - thanks for this really really amazing library!
I'd like to ask a question please:
In my app most of image are ones which are uploaded by the client - via the users themselves.
I would like to use one of options which are supported by this library for combatting slow connections.
My question relates to the fact that I'm not sure which of the 3 options would work out best for me.
I searched on Google, but could not find a good compression of all 3.
Would love if someone would be able to explain the advantages & disadvantages of each method.
Thanks!

WebP is more expensive to decode on device because there's no dedicated hardware. I think WebP may have a progressive option, but PINRemoteImage doesn't support it. Smaller download than JPEG, but bigger on device cost. Choosing this over JPEG depends on the network conditions of your users and the types of device they predominantly use.
Progressive JPEG is pretty awesome.
URLs of varying quality could be used in conjunction with progressive JPEGs. The idea behind it is to download a different version depending on network conditions. You'd still benefit from progressive.

@garrettmoon - thanks for your detailed answer!
One last question - does every JPEG supports Progressive, or when I decode and upload the image it should already be done for that purpose (i.e., in the way which supports it)?

@oferRounds not every JPEG supports progressive, it depends on how it's encoded.

Got you - thanks again!


Avoid to import matplotlib to set its backend Agg in code like chainer

Refs https://github.com/chainer/chainer/pull/3043

Codecov Report

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

@@            Coverage Diff            @@
##             master     #976   +/-   ##
=========================================
  Coverage          ?   89.06%
=========================================
  Files             ?      107
  Lines             ?     5807
  Branches          ?        0
=========================================
  Hits              ?     5172
  Misses            ?      635
  Partials          ?        0

Continue to review full report at Codecov.

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

This PR is blocked by test script issue.

Thank you for your reviewing.
@vilyaair Cloud you fix?

Definitely, my pleasure.
Initially, I want to keep the README.md  more consistent with that in the chainer. I think that neither Linux nor non-GUI environment is a precise term. A typical situation is Python embedded distribution on Windows, which does not contain TkInter. Therefore, it also requires to set the environment variable MPLBACKEND to Agg. I feel that it is more accurate to use environment without appropriate renderers, but it is not intuitive.

@vilyaair Thanks for the insights.
How about saying like on environment without matplotlib renderers (e.g., non-GUI environment)?

Jenkins, test this please.

@kmaehashi The test was passed.

LGTM!


docker start -i fails to attach to stdin

Steps To Reproduce

Create an image using the following Dockerfile source:

    FROM	   ubuntu:12.04
    RUN echo "dlw_sshserver">/root/ComponentName.txt
    ENTRYPOINT  /bin/bash

The above essentially creates a bash command shell.

Test 1

Execute image:  'docker run <imageGUID>.' Container 'X' is created and since STDIN wasn't left open with '-i' option, the bash process terminates and the container transitions to the stopped state.
Now start newly created container 'X' requesting interactive mode:  'docker start -i <XGUID>.' Container executes but fails to connect its STDIN to current terminal session and then transitions to the stopped state.

Test 2

Execute image but this time enable interactive option:  'docker run -i <imageGUID>.' Container 'Y' is created and since STDIN is open with '-i' option, the current command terminal connects to the container's executing bash process.  The container remains running and responsive.
Stop running the 'Y' container:  'docker stop <YGUID>.' The 'Y' container transitions to the stopped state.
Start running the 'Y' container requesting interactive mode:  'docker start -i <YGUID>.' Under these circumstances and in opposition to the behavior of 'Test 1', the start command connects the Y container's STDIN and the container remains running and responsive.

Environment

Using docker version 1.3.1.
Ubuntu  12.04.4 LTS

Behavior Assessment
Why the different behavior between the 'start' command of 'Test 1' vs the 'start' of 'Test 2'? After reviewing the image meta data for both 'X' and 'Y' containers using the docker inspect command, the differing behavior between the containers seems related to the Config.OpenStdin option. The boolean setting for this 'Y' container field is 'true', as established by the docker run command, while 'X's value is 'false'. This boolean setting not only advertises the capability of the container, but also determines its availability. Specifying the availability of a container option must be what's conveyed by the phrase "...final control to the operator who starts the container from the image." that appears in the docker run documentation.
Since run options of '-i' and '-a' are also accepted by start, unlike other options that are immutable, like the volumes option -v, it's not apparent that the availability of these options is controlled by the run command and that the '-a' and '-i' options of the start command can only affect the values of these options made accessible by run. There's nothing mentioned by reading the documentation of of start that alerts readers to this intentionally designed behavior. Besides augmenting the 'start' command's documentation, perhaps a more descriptive explanation of 'final control' could be incorporated into the run documentation.

I think the AttachStdin option is the meta data of a container, it only can be changed by docker create and docker run is equal to docker create + docker start. Though docker start has the option -i -a, but it only work when the contain created with -i

I was able to replicate what @WhisperingChaos said but I think @coolljt0725 is right. The docker start has the option -i -a, but it only work when the contain created with -i.

Thank you @coolljt0725 and @aanm for your review of this submitted issue!
I imagine my discussion in the "Behavior Assessment" section wasn't clear.  I agree with both of you: the -i & -a options implemented by docker create & docker run control the option values assignable to the  -i & -a options that can be specified by the docker start command.  There's no dispute that this is the intended behavior.  The issue is with the docker start documentation not the command itself.
I simply want the docker start documentation to convey the dependency between its option values and docker create and docker run because:

Unlike other immutable options, such as -v for host volume binding that cannot be specified as an option for docker start, the -i & -a options do appear as options for this command.  Since they can be specified, it suggests that all combinations of their values can be applied by docker start, as the restrictions imposed by docker create or docker run are omitted from docker start's definition.
The following sentence appears in the docker create documentation: " Note that volumes set by create may be over-ridden by options set with start."  Although the documentation states that the 'volumes' option '-v' can be changed by docker start, the 'volumes' option isn't defined for start.  Also, I've attempted using -v option with Docker version 1.3.1 and it rejects this option.  However, on the same page, there's an example immediately below this statement that illustrates docker start overriding the -i & -a options specified by a preceding docker create.  Therefore, one could reasonably conclude from this bug in the documentation that -i & -a options specified by docker start can fully replace the ones specified by both docker run and docker create, as there's no stated restriction, expressed by the documentation, that limits the extent of 'over-ridden'.

To summarize:

Augment the documentation for docker start to include notation explaining its dependence on docker create and docker run.
Explain in greater detail what's meant by the statement: "..final control to the operator who starts the container from the image." that appears in the docker run documentation.
Correct either the docker start definition to include the 'volume' option, if its now supported in versions after 1.3.1 or the reference by docker create which states that docker start supports this option.

PR #10549  is going to add some docs for this.

Actually, I'm not sure there is any reason this can't be remedied.  A hack to prefer command line over reading the inspect (container.Config) output makes it work properly with a quick test.  Given all the right--in fact the same--setup happens for tty and stdin/stdout/stderr in run and start (because they are both using attach under the covers), I can't come up with a reason that this couldn't be resolved.

@WhisperingChaos It has been detected that this issue has not received any activity in over 1 year.
Could you please let us know if it is still relevant? For example:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?


What is the format for bounties?

https://img.shields.io/bountysource/team/awesome-badges/activity.svg - how do the org, repo and issue factor in here?
I posted a $100 bounty for https://github.com/linuxmint/Cinnamon/issues/3883 at https://www.bountysource.com/issues/8351500-cinnamon-should-support-hotkeys-window-shortcuts-for-selecting-existing-windows, and I'm surprised that Bountysource doesn't make it easy to add a badge.

I have no clue. Ask them maybe! 💃

Well, I saw "bounties" in the README. Not clear what the purpose of this repo is - badges you'd like to keep handy? Sorry to intrude then :)
Anyway, the Markdown is
[![Bountysource][1]][2]
[1]:http://bountysource.com/badge/issue?issue_id=8351500
[2]:https://www.bountysource.com/issues/8351500-cinnamon-should-support-hotkeys-window-shortcuts-for-selecting-existing-windows

No need for shields.io.

There's absolutely no purpose for this repo, just a list of badges you could use. Sorry for the confusion!


Make transaction pool size configurable

@garyschulte to add details

Current list of things that are configurable about the Transaction can be found here, and it seems max size (in transactions) is already configurable with a default of 4K.
I'm guessing we're actually talking about a worker pool or something else?

--tx-pool-max-size and --tx-pool-hashes-max-size both exist and are honored via the command line and environment vars. I'll check the documentation to make sure it is captured correctly.

documentation and command line help both show how to set these values:
https://besu.hyperledger.org/en/stable/Reference/CLI/CLI-Syntax/#tx-pool-max-size


'get' method bug using ATT&CK TAXII server

Hello!
I am trying to pull data from the ATT&CK TAXII server, and I'm following the recipe code from their github:
https://github.com/mitre/cti/blob/master/USAGE.md#access-from-the-attck-taxii-server
This is the code I'm running:
from stix2 import TAXIICollectionSource
from taxii2client.v20 import Collection # only specify v20 if your installed version is >= 2.0.0

collections = {
    "enterprise_attack": "95ecc380-afe9-11e4-9b6c-751b66dd541e",
    "pre_attack": "062767bd-02d2-4b72-84ba-56caef0f8658",
    "mobile_attack": "2f669986-b40b-4423-b720-4396ca6a462b"
}

collection = Collection(f"https://cti-taxii.mitre.org/stix/collections/{collections['enterprise_attack']}/")
src = TAXIICollectionSource(collection)

src.get('x-mitre-tactic--ffd5bcee-6e16-4dd2-8eca-7b3beedf33ca')

But I'm getting this error:
  File "C:\Users\MY_USERNAME\AppData\Local\Programs\Python\Python39\lib\site-packages\stix2\datastore\taxii.py", line 213, in get
    if stix_obj.id != stix_id:
AttributeError: 'dict' object has no attribute 'id'

When I'm trying to use a local filesystem, it works fine. IE:
import stix2
src = stix2.FileSystemSource(r"C:\Git\cti\enterprise-attack")
src.get('x-mitre-tactic--ffd5bcee-6e16-4dd2-8eca-7b3beedf33ca')

Is this a bug or am I missing something?
Thanks :)

Hi @sparrow-k, this issue has been resolved on the cti-python-stix2 repo. The reason why you see this behavior happen in the TAXIICollectionSource and not the FileSystemSource is because each DataStore class implements their own methods for the abstract class they subclass. You can read a bit more about it in the issue referenced below. I will be closing this since the fix is already present on master and will be available in the next release.
I should note that for awareness that the client also implements a similar .get() method. Since you opened the issue on the client repo :)
from taxii2client.v20 import Collection # only specify v20 if your installed version is >= 2.0.0

collections = {
    "enterprise_attack": "95ecc380-afe9-11e4-9b6c-751b66dd541e",
    "pre_attack": "062767bd-02d2-4b72-84ba-56caef0f8658",
    "mobile_attack": "2f669986-b40b-4423-b720-4396ca6a462b"
}

collection = Collection(f"https://cti-taxii.mitre.org/stix/collections/{collections['enterprise_attack']}/")
collection.get_object("x-mitre-tactic--ffd5bcee-6e16-4dd2-8eca-7b3beedf33ca")

duplicate oasis-open/cti-python-stix2#459


Dynamic array collection data  - Uncaught Error: Syntax error, unrecognized expression

Dynamic json data is not working.Tested with below code it is throwing error
Uncaught Error: Syntax error, unrecognized expression: [{"id":"1","parent":"#","text":"test"}]

$(document).ready(function () {
  var tree = {
	    nodes: []
	};
    tree.nodes.push({
          id :  1 ,
          parent: '#' ,
          text : 'test'
    });

$('#jstree_demo_div').jstree({
'core': {
'data': JSON.stringify(tree.nodes)
}
});
})

Please read the docs - jstree expects an array, or an AJAX config, or a function, not a string. You are passing in a string.
Best regards,
Ivan

vakata . Thank you very much for clarification


Provide link to the Oracle Instant Client

I think this may be the package that Microsoft recommends.  If so, it would be helpful to include a link.

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

#sign-off

@Marklannucci Hi, Thank you for creating this helpful Pull Request.


Bump ClamAV to 0.103.1-17354

While there: Extract that version into a variable, and remove the unneeded duplication
of it in the output file of curl(1).

Mostly as explanation for the "VERSION" thing: On the one hand I think this might make it easier to test out new versions (clear where to change what, and actually could be exposed through the Makefile. On the other hand this simplifies a change I'm not yet sure about: For performance reasons I'm looking into spawning clamd right now, and having a single point of version would ensure things to not get out-of-sync that easily.
As such: If you think only bumping the version is a better approach, I could also update the PR to that.

@ankon thanks for the high quality PRs! I invited you to the repo, you are welcome to merge improvements as you see fit, and I'm happy to try and review anything you want a second set of eyes on.

@statik thanks a lot! I cannot promise I'll be always as quick as you in replying/reviewing, but I'll try my best :D


Document little things

This long-lived issue will track some little things that need documenting, that aren't worth their own issue.

[ ] Document the need to exit VSCode in order to run setup.ps1 when .venv already exists.

[ ] Even though the related PEP is rejected, keep using flit dynamic version to avoid template bumps resetting the version number

Or, consider just a Jinja include step to compose pyproject.toml.


Update intertools version

Codecov Report

Merging #156 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #156   +/-   ##
=======================================
  Coverage   84.63%   84.63%
=======================================
  Files          11       11
  Lines         371      371
=======================================
  Hits          314      314
  Misses         57       57

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 cd1c3b7...3f34681. Read the comment docs.


Support doc values in document tab

New features to doc values support.
If doc values for fields are available,

Show doc values data in document tab and pop up window.
Allow users to copy doc values data to clip board.
Allow users to save doc values data to local file in the same manner as field data.

Screen shots
"Doc Values" column data in document tab:

Pop up window to show details:

Other fixes:

Update java version to 1.8.0
Remove norm type from flags (this was removed at Lucene 5)
Disable add/reconstruct document feature (for now, they are broken and dangerous...)

This looks very exciting @mocobeta! Thanks for taking care of DocValues. Would you like to do the honors and merge this to master as well?

@DmitryKey Yes, I'll investigate master branch to support doc values as well!

thanks @mocobeta ! I have just tested on the solr example index techproducts. DocValues are read and displayed correctly. One visual glitch is in the DocValues dialog:

can it be related to the table's column width?

Thank you for testing, I'll check it soon.

@DmitryKey Fixed at #54 . Thanks!

Thanks for quick fix @mocobeta  !


feat(loaders): Allow alt loaders like fnl or tl

I'm playing with https://github.com/folke/lazy.nvim/issues/978
So here's the thing. This is working for me, but I'm not 100% sure of why it's working. It's not hitting most of the code I touched since I didn't modify anything to touch that code. It is my suspicion that what I've done is make lazy.nvim more flexible at the cost of breaking LazyVim, which I don't use. So now I think the best course of action is to pull LazyVim and configure it to use this alternate loaders code to see how it falls over

vim.tbl_contains and vim.split exist fyi

I'm not interested in adding fnl support. This would also break when using Neovim nightly and the new loader there, since fennel is not supported bny neovim's loader


[bug] delete is broken

The delete action receives the list as "upcoming" instead of an actual list of videos, so it doesn't remove the video you wanted to delete.
Remove the quotes here: https://github.com/jgthms/juketube/blob/master/index.html#L39

just found this problem.
is this project still mantained?

It is not.


Use different source than Model

Hi, nice project. I've been heavily use this in my project. However, i can't find anywhere in the doc the way to build a grid from an IEnumerable that i queried and put into ViewBag. Is it event possible?
Thanks in advance.
Edit: Something like this
@(Html.Grid(ViewBag.MyItemList).....)

Just cast it back to an enumerable, before passing it to the grid.

Yes, i tried to used (List)ViewBag.MyItemList and it let me do that, but then i don't know what to used to replace the "model" in columns builder. I could have checked the source but i don't really familiar with C#. So please bare with me. Thanks!

List is non-generic construct, you probably created that list somewhere inside the controller, so you can copy a generic version of that here (List<MyModel>)ViewBag.MyItemList or use a .Cast<MyModel> on List.

Oops, my bad. What i tried to use is exactly what you just  replied Grid((List<MyModel>)ViewBag.MyItemList).
Then i don't know what to put in columns Add() instead of  model. I guess i have to do something to type cast it in the view too ?
.Build(columns =>
    {
        columns.Add(model => model.Name).Titled("Name");

You mean you don't know what properties are used inside your model?

It works now. That was my mistake that i wrote this
@(Html.Grid((List<MyModel>)ViewBag.MyItemList)         .Build(columns =>         {             columns.Add(mm => mm.Name).Titled(Html.DisplayNameFor(mm => mm.Name);         })         .Empty("No data") )
The Html.DisplayNameFor only work for the @model of the view. Thought that i can use that for any Item( Or can i? Still trying to learn, i was not really familiar with ASP.NET and C# as a whole...)
Thank for your very fast response!

Yes, it only works for the @model, you could check out how the .DisplayNameFor(...) get's it's value and make a call to a helper function or use static resx classes.

Thank you. I believe my question now off-topic. Greatly thank for your help.


Translations for Version 1

This will be a running issue to let you know how to contribute translations

This can be a huge task. Please don't take it all on by yourself. It does not need to be done by any one person. Ask for help.
You may translate to any language you are fluent in. Yes yes, that means if you can and want to, you may even translate to Esperanto or even Klingon.
File Name
You'll create a new markdown file and give it the name checklist_language.md. However, you'll replace "language" with the language's language code. If you don't know it, click the link to find it. Here are some example file names:
checklist_pt-br.md
checklist_ja.md
checklist_hu.md

Proposed workflow:

Fork this repo
In the site/versions/1 folder, create a new file checklist_language.md and have fun translating site/versions/1/checklist.md
Once you are done and checked for typos, commit it & push your work to your fork
Submit a PR against this repo and reference this issue

Someone, fluent in that language, will look it over and give tell us it is good. Once we hear it is good, we will merge your PR.
Thanks for contributing! ♥

I take care of translating it into French !

I take care of translating into German.


Allow querying a negative condition

Currently in the empty template we're jumping through a lot of hoops because we can't query a negative:
 - !<Move>
    condition: "${useWorker}"
    from: "worker/src/worker/*"
    to: "worker/src/jsMain/kotlin/${packagePath}/worker"
    description: "Rearranging worker source to conform to the user's package"
  - !<Move>
    condition: "${useWorker}"
    from: "worker/*"
    to: "donotdeleteworker"
    description: "Moving worker files to a safe location before cleanup"
  - !<Delete>
    files: "worker/*"
    description: "Removing unused worker files (if any)"
  - !<Move>
    condition: "${useWorker}"
    from: "donotdeleteworker/*"
    to: "worker"
    description: "Finalizing worker files"

This should just be:
 - !<Move>
    condition: "${useWorker}"
    from: "worker/src/worker/*"
    to: "worker/src/jsMain/kotlin/${packagePath}/worker"
    description: "Rearranging worker source to conform to the user's package"
  - !<Delete>
    condition: "${!useWorker}"
    files: "worker/*"
    description: "Removing unused worker files (if any)"

but I remember earlier when trying to get that to work, it was failing.

Solved this by adding a not method. Maybe there's a vanilla freemarker way to do this but this seems easy enough for now.
So, we should change the code to
- !<Move>
    condition: "${useWorker}"
    from: "worker/src/worker/*"
    to: "worker/src/jsMain/kotlin/${packagePath}/worker"
    description: "Rearranging worker source to conform to the user's package"
  - !<Delete>
    condition: "${not(useWorker)}"
    files: "worker/*"
    description: "Removing unused worker files (if any)"

However, we should wait some amount of time (2-3 weeks?) after releasing 0.9.13 before updating the empty template, allowing people to update their Kobweb CLIs. We should ALSO add the minimum version of "0.9.13" to the empty template to prevent this change from crashing older CLIs that didn't update.


ezunlock: Add version 0.1

A simple GUI application for deleting stuck/stale/undeletable files, open sourced alternative to IOBit Unlocker. https://github.com/demberto/EzUnlock

[x] I have read the Contributing Guide.

$dir\EzUnlock.exe.config and $dir\Helper.exe.config stores build settings of the app. They are not involved with user config.
(This is just a reminder. No need to modify anything regard to this.)

Thank you, surprisingly it worked in testing though

/verify


Add Docker /v2/_catalog endpoint (#20469)

Backport #20469

Added properties for packages.
Fixed authenticate header format.
Added _catalog endpoint.
Check owner visibility.
Extracted condition.
Added test for _catalog.

Yep, works in 1.17.


[WIP] Kill submodules

This PR removes the use of git submodules for managing external Ansible role dependencies. Instead it uses Ansible role requirements files introduced in Ansible 1.8. Since Ansible 1.8 is not yet released, please do not merge this PR yet.
I've tested the functionality in this PR by using the latest Ansible source which contains the necessary 1.8 functionality for role requirements files.
Fixes #753.

Ansible 1.8 has been out since November 2014. Should we revisit this PR? We'll also need a rebase.

:+1: on revisiting this. I'm happy to assist.


Better error diagnostics on targets without std.

Provides a warning if a docker command fails and rust-std is not installed for the target. For example, for x86_64-unknown-dragonfly, the added output would be:
[cross] warning: rust-std is not installed for x86_64-unknown-dragonfly
[cross] note: you may need to use `build-std`

This is done solely if the command fails and if the target is a built-in, so we don't get misleading warnings for custom targets, and there is no overhead if the build succeeds.
Closes #94.
Closes #167.

An example of the new error diagnostics is as follows. We can't remove the cargo output without basically recreating it, and trying to tee/capture it would run into issues with terminal coloring, etc. However, the resulting messages are quite nice:

If we have an unknown target, we get:
$ cross build --target x86_64-unknown-dragonfly1
[cross] note: Falling back to `cargo` on the host.
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --target x86_64-unknown-dragonfly1 --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "x86_64-unknown-dragonfly1". Run `rustc --print target-list` for a list of built-in targets

And if the component is installed but does not support the standard library, we get:
$ cross build --target thumbv6m-none-eabi

   Compiling hello v0.1.0 (/project)
error[E0463]: can't find crate for `std`
  |
  = note: the `thumbv6m-none-eabi` target may not support the standard library
  = note: `std` is required by `hello` because it does not declare `#![no_std]`

error: cannot find macro `println` in this scope
 --> src/main.rs:2:5
  |
2 |     println!("Hello, world!");
  |     ^^^^^^^

error: `#[panic_handler]` function required, but not found

For more information about this error, try `rustc --explain E0463`.
error: could not compile `hello` due to 3 previous errors

I'm not sure this is the correct approach, specifically the wording. If I don't require libstd this message would still always be shown.

We could specific to use -Z build-std=<components> (which we could change once we've implemented #896), so we can make it clear that libstd (it might be core, alloc, etc.) isn't required but may be an issue?

What about making component_is_installed returning an enum (or Option<bool>), signaling a component is installed, available but not installed, and not available. Then if not available, signal to use build-std

I've updated the error messages to make it clear std itself is not needed, and how build-std may be used.


MQTT keep alive ping is not working for RP2040W (Pico W)

Pico W SDK: 1.4.0
IDE: CLion on Ubuntu 22.04 running on a PC:
GCC: 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
MQTT broker/server: Mosquitto 2.0.15 running on Ubuntu 22.04.
Issue: MQTT keep alive ping is not working for RP2040W (Pico W).
mqtt_cyclic_timer() is never called. It seems that timeouts::sys_timeout() never fires. The keep alive ping is never sent to the server thus causing the server to disconnect the client due to inactivity.
I added additional debugging output in apps/mqtt/mqtt.c to the following two functions:
static err_t mqtt_tcp_connect_cb( void *arg, struct altcp_pcb *tpcb, err_t err )
{
...
  /* Start cyclic timer */
  sys_timeout( MQTT_CYCLIC_TIMER_INTERVAL * 1000, mqtt_cyclic_timer, client );
  client->cyclic_tick = 0;
  LWIP_DEBUGF( MQTT_DEBUG_TRACE, ( "mqtt_tcp_connect_cb: mqtt_cyclic_timer: started\n" ) );
...
}

static void mqtt_cyclic_timer( void *arg )
{
  LWIP_DEBUGF( MQTT_DEBUG_TRACE, ( "mqtt_cyclic_timer: called\n" ) );
...
  if ( restart_timer )
  {
    sys_timeout( MQTT_CYCLIC_TIMER_INTERVAL * 1000, mqtt_cyclic_timer, arg );
    LWIP_DEBUGF( MQTT_DEBUG_TRACE, ( "mqtt_cyclic_timer: restarted\n" ) );
  }
}

I set the keep alive to 15 seconds:
....
  /* Initialize and configure the client info structure */
  struct mqtt_connect_client_info_t clientInfo;
  clientInfo.client_id = MQTT_CLIENT_ID;
  clientInfo.client_user = MQTT_USER;
  clientInfo.client_pass = MQTT_USER_PASSWD;
  clientInfo.keep_alive = 15;
  clientInfo.will_topic = NULL; /* set to NULL if will is not to be used, will_msg, will_qos and will retain are then ignored */
  clientInfo.will_msg = NULL;
  clientInfo.will_qos = 0;
  clientInfo.will_retain = 0;

  err = mqtt_client_connect(
    client,
    &brokerAddr,
    MQTT_PORT,
    mqttConnectionCallback,
    NULL,
    &clientInfo
  );
....

I get the following output when I run a simple MQTT client (built using the MQTT documentation provided) on the PICO W with debug enabled,  You will note that the new debug messages added to mqtt_cyclic_timer() never appear.
Version: 7.95.49 (2271bb6 CY) CRC: b7a28ef3 Date: Mon 2021-11-29 22:50:27 PST Ucode Ver: 1043.2162 FWID 01-c51d9400
cyw43 loaded ok, mac 28:cd:c1:04:94:65
API: 12.2
Data: RaspberryPi.PicoW
Compiler: 1.29.4
ClmImport: 1.47.1
Customization: v5 22/06/24
Creation: 2022-06-24 06:55:08
connect status: joining
connect status: no ip
connect status: link up
mqtt_client_connect: Connecting to host: <IP_ADDRESS> at port:1883
mqtt_tcp_connect_cb: TCP connection established to server
mqtt_tcp_connect_cb: mqtt_cyclic_timer: started <<<<< NOTE THIS ENTRY (added by me)
mqtt_output_send: tcp_sndbuf: 11680 bytes, ringbuf_linear_available: 33, get 0, put 33
mqtt_parse_incoming: Remaining length after fixed header: 2
mqtt_parse_incoming: msg_idx: 4, cpy_len: 2, remaining 0
mqtt_message_received: Connect response code 0
mqtt_sub_unsub: Client (un)subscribe to topic "mqtt/test/in", id: 1
mqtt_output_send: tcp_sndbuf: 11680 bytes, ringbuf_linear_available: 19, get 33, put 52
mqtt_parse_incoming: Remaining length after fixed header: 3
mqtt_parse_incoming: msg_idx: 5, cpy_len: 3, remaining 0
mqtt_message_received: SUBACK response with id 1
mqtt_tcp_recv_cb: Recv pbuf=NULL, remote has closed connection
mqtt_client_connect: Connecting to host: <IP_ADDRESS> at port:1883
mqtt_tcp_connect_cb: TCP connection established to server
mqtt_tcp_connect_cb: mqtt_cyclic_timer: started <<<<< NOTE THIS ENTRY (added by me)
mqtt_output_send: tcp_sndbuf: 11680 bytes, ringbuf_linear_available: 33, get 0, put 33
mqtt_parse_incoming: Remaining length after fixed header: 2
mqtt_parse_incoming: msg_idx: 4, cpy_len: 2, remaining 0
mqtt_message_received: Connect response code 0
mqtt_sub_unsub: Client (un)subscribe to topic "mqtt/test/in", id: 1
mqtt_output_send: tcp_sndbuf: 11680 bytes, ringbuf_linear_available: 19, get 33, put 52
mqtt_parse_incoming: Remaining length after fixed header: 3
mqtt_parse_incoming: msg_idx: 5, cpy_len: 3, remaining 0
mqtt_message_received: SUBACK response with id 1
mqtt_tcp_recv_cb: Recv pbuf=NULL, remote has closed connection
mqtt_client_connect: Connecting to host: <IP_ADDRESS> at port:1883
mqtt_tcp_connect_cb: TCP connection established to server
mqtt_tcp_connect_cb: mqtt_cyclic_timer: started <<<<< NOTE THIS ENTRY (added by me)
mqtt_output_send: tcp_sndbuf: 11680 bytes, ringbuf_linear_available: 33, get 0, put 33
mqtt_parse_incoming: Remaining length after fixed header: 2
mqtt_parse_incoming: msg_idx: 4, cpy_len: 2, remaining 0
mqtt_message_received: Connect response code 0
....

The following log messages keep repeating on the Mosquitto broker/server:
1666607350: New connection from <IP_ADDRESS>:52868 on port 1883.
1666607350: New client connected from <IP_ADDRESS>:52868 as picow (p2, c1, k15, u'test').
1666607375: Client picow has exceeded timeout, disconnecting.
1666607380: New connection from <IP_ADDRESS>:52869 on port 1883.
1666607380: New client connected from <IP_ADDRESS>:52869 as picow (p2, c1, k15, u'test').
1666607405: Client picow has exceeded timeout, disconnecting.

ping @peterharperuk

Same issue here, any updates on the topic? My Pico doesn't seem to receive any messages from the broker after successfully subscribing in addition to the missing keep alive pings.

This just works for me using lwip in the pico-sdk. Suggest you don't use pico-extras for lwip


karavictl validations for input flags when creating and updating resources

Description
This PR updates all create/update commands for tenant/role/rolebinding/storage to check for valid, non-empty inputs and display appropriate error messages if input is not valid.
Issues
List the issues impacted by this PR:

Issue ID

#78

Checklist:

[x] I have performed a self-review of my own changes.

@sharmilarama: Thank you for submitting your pull request!
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at<EMAIL_ADDRESS>

e2e pass


rfc-0003: A pod with utilities for better developer experience

supersedes rfc-0001.

@sbawaska I think the default should maybe be "from latest". FWIW that's the default for the kafka-console-consumer which has a --from-beginning flag instead.

I know that message payload encoding was discussed in RFC-0001 here and here, but i just want to confirm the desired behavior.
I.e. If a specific message payload was published as application/json, then users running subscribe <stream-name> --payload-as-string will receive stringified json as the payload for that message, rather than json embedded as the value of the payload key.
E.g. if the original payload was published with content-type: application/json and a value of {"foo":1, "bar":["abc",1,2,3]} the output will be:
{"payload":"{\\"foo\\":1,\\"bar\\":[\\"abc\\",1,2,3]}"}
instead of
{"payload":{"foo":1,"bar":["abc",1,2,3]}}
is my understanding right?

For examples (from the cloudevents spec) of json with embedded binary, text, and json payloads see:
https://github.com/cloudevents/spec/blob/master/json-format.md#32-examples

Trying to bring this in for a landing. These are a few changes we can make to simplify and clarify the RFC:

remove the core/knative invoke commands, curl will be available in the pod
add a --payload-base64 flag for encoded binary data that is mutually exclusive with --payload (which only handles text)
clarify that subscribe runs until canceled (SIGINT)
subscribe output is LD JSON with base64 encoded payloads
jq and base64 will be available in the pod for decoding messages (or do it on your own machine)
clarify that each pod is only expected to operate on resources within the same namespace (create a new pod to interact with resource in another namespace)
clarify that a serviceaccount and rolebinding should be created to give the pod access to the api server (the implementation should provide advice as to the RBAC permissions needed)
other commands and improvements can be defined in future RFCs

@sbawaska @markfisher @jldec @glyn @ericbottard I'd like to get this approved and merged tomorrow. We descoped a good bit that was leading to ambiguities or could be tricky to implement. Future commands and behavior can be defined by future RFCs.
Please open suggestions for typos and grammatical fixes, but hold off on scope changes.


gigE camera what are the arguments to start the node?

how do we run nvidia apriltags humble docker with GigE camera on Jetson orin?

You can try a ROS 2 package for GigE GenICam support (quick search yielded this) to access your camera and then send the frames through lens distortion correction, image color conversion, and then into Isaac ROS Apriltag.

Thank you for your reply
Somehow within the container we got these two topics
admin@ubuntu:/workspaces/isaac_ros-dev$ ros2 topic hz /color/image_raw
average rate: 6.085
	min: 0.050s max: 0.451s std dev: 0.13842s window: 7
^Cadmin@ubuntu:/workspaces/isaac_ros-dev$ ros2 topic hz /color/camera_info
average rate: 1.363
	min: 0.352s max: 0.949s std dev: 0.27064s window: 3

which launch file to use? which arguments to edit/ pass? thanks

do these inputs seem sufficient to run nvapriltags? how do we run it?
could you render sample line, please?
it will start with ros2 launch isaac_ros_apriltag but what will be the rest of the line?

@hemalshahNV
any update?

@AndreV84 , you will need to write your own launch file that brings up your cameras and feeds appropriate images into the isaac_ros_apriltag::ApriltagNode node. The interface to this node are listed in documentation which include as input rectified (=lens distortion correction for a monocam) images as sensor_msgs::Image and the intrinsic calibration as sensor_msgs::CameraInfo so that the Apriltag node can determine a 3D pose. The examples provided should have all of the information you need to make this work for your application.

there is no easy way to just run the cameras node separately manually then somehow start existing nvapriltags templates saying them to subscripbe to two specific topic names from already running node, e.g. run nvapriltags to subscribe to inputs
/color/camera_info
/color/image_raw

Thanks
AV

how do we convert to a supported type?
component_container_mt-1] [ERROR] [1675965639.925155779] [NitrosImage]: [convert_to_custom] Unsupported encoding from ROS [bayer_rggb8

@hemalshahNV
I have found in camera settings several pixel formats
which do we use so it will get processed/ supported by nvapriltag node?
Thanks
AV

will BGR8 be sufficient for direct processing for NVApriltags?

The BGR8 format can be turned into RGB8 using the Isaac ROS Image Proc image_format_converter node. Then, that converted image can be sent to the Isaac ROS AprilTag isaac_ros_apriltag node.

after changing the type
to BRG8
it would result in
[component_container_mt-1] [INFO] [1676336759.377062965] [apriltag]: [NitrosSubscriber] Received a message but the application receiver's pointer is not yet set.
[component_container_mt-1] [ERROR] [1676336759.391618695] [NitrosImage]: [convert_to_custom] Unsupported encoding from ROS [INVALID].
[component_container_mt-1] terminate called after throwing an instance of 'std::runtime_error'
[component_container_mt-1]   what():  [convert_to_custom] Unsupported encoding from ROS.
[ERROR] [component_container_mt-1]: process has died [pid 1466086, exit code -6, cmd

@hemalshahNV can NV apriltags process any of the formats without conversion?
from the list?
or the Image Proc is necessarily required?

RGB8 is what Isaac ROS Apriltag is expecting. Please convert to this color format and retest.

thank you for following up
devs were able to manage the conversion
let me check with my team then get back to you

@hemalshahNV
seems there is data but no length so no detection
, length: 0>'
---
header:
  stamp:
    sec:<PHONE_NUMBER>
    nanosec: 973769197
  frame_id: blackfly_0

seems the issue been addressed somehow reducing the resolution
could you extend if nvapriltag supports large resolutions somehow?
what are the largest supported resolutions? is there a supported list of resolutions?
@hemalshahNV